diff options
| author | Alexander Kriegisch <Alexander@Kriegisch.name> | 2021-04-26 10:02:15 +0700 |
|---|---|---|
| committer | Alexander Kriegisch <Alexander@Kriegisch.name> | 2021-04-26 10:02:15 +0700 |
| commit | 18f3385e23b13b385edcbcc81dbb52623607dd8f (patch) | |
| tree | 01635f34664ae1ce1baa7de112288ec0a6c5116a /aspectjtools/aspectjtools-assembly.xml | |
| parent | f1f46b4e8bf743c0ade1a26e96591b819108d5af (diff) | |
| download | aspectj-18f3385e23b13b385edcbcc81dbb52623607dd8f.tar.gz aspectj-18f3385e23b13b385edcbcc81dbb52623607dd8f.zip | |
Prepare main artifacts to be deployed via Maven, step 1
This change affects the following modules:
- aspectjmatcher
- aspectjrt
- aspectjtools
- aspectjweaver
- installer
They have in common that they all use Maven Assembly Plugin in order to
create some kind of uber JARs with constituent modules and/or libraries.
Except for the installer, they are all available on Maven Central today,
but I think it would not hurt to deploy the installer to there, too.
Changes made:
- Use Flatten Maven Plugin in order to create simple POMs with only
basic information and - most importantly - without dependencies.
- The new dependency-reduced POM (DRP) or "flattened POM" gets
attached to the build, i.e. it will be installed and deployed as a
replacement of the original POM.
- Attaching the DRP only works for 'jar' type modules, which is why I
changed the packaging type for each module from 'pom' to 'jar'.
- Deactivate generation of the default JAR for each module. This is
necessary now, since we have the 'jar' packaging type.
- Make sure that assembly descriptors using 'dependencySet' entries
have set option 'useProjectArtifact=false' in order to avoid
warnings about the non-existing main artifact.
TODO:
- Explore option to migrate from Maven Assembly to Maven Shade,
because it does not need descriptor files, can also generate source
JARs and can automatically create and attach a DRP which is less
fragmentary than the one created by Flatten Maven, basically the
original JAR minus the dependencies.
- If in the future we want to make sure to only deploy the modules
listed above, e.g. to Maven Central, if simply calling 'mvn deploy'
for the whole project, we could use 'maven.deploy.skip=true' in the
parent POM and override it by 'maven.deploy.skip=false' just in the
few modules which need to be deployed. See also:
https://stackoverflow.com/a/29574812/1082681
Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
Diffstat (limited to 'aspectjtools/aspectjtools-assembly.xml')
| -rw-r--r-- | aspectjtools/aspectjtools-assembly.xml | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/aspectjtools/aspectjtools-assembly.xml b/aspectjtools/aspectjtools-assembly.xml index fbf45c808..9a6777509 100644 --- a/aspectjtools/aspectjtools-assembly.xml +++ b/aspectjtools/aspectjtools-assembly.xml @@ -13,6 +13,8 @@ <dependencySets> <dependencySet> <unpack>true</unpack> + <!-- Avoid warning when trying to add non-existing main artifact JAR --> + <useProjectArtifact>false</useProjectArtifact> <includes> <include>org.aspectj:org.eclipse.jdt.core</include> <include>org.aspectj:asm-renamed</include> |