You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

pom.xml 6.2KB

5 years ago
5 years ago
5 years ago
3 years ago
5 years ago
5 years ago
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>
3 years ago
5 years ago
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>
3 years ago
5 years ago
5 years ago
5 years ago
5 years ago
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>
3 years ago
5 years ago
2 years ago
5 years ago
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  3. xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  4. <modelVersion>4.0.0</modelVersion>
  5. <parent>
  6. <groupId>org.aspectj</groupId>
  7. <artifactId>aspectj-parent</artifactId>
  8. <version>1.9.20-SNAPSHOT</version>
  9. </parent>
  10. <artifactId>installer</artifactId>
  11. <name>AspectJ Installer</name>
  12. <description>
  13. The AspectJ installer is an executable JAR capable of installing a full AspectJ distribution consisting of libraries
  14. (AspectJ runtime, weaver and tools/compiler) and API Javadoc.
  15. </description>
  16. <url>https://www.eclipse.org/aspectj/</url>
  17. <licenses>
  18. <license>
  19. <name>Eclipse Public License - v 2.0</name>
  20. <url>https://www.eclipse.org/org/documents/epl-2.0/EPL-2.0.txt</url>
  21. <distribution>repo</distribution>
  22. </license>
  23. </licenses>
  24. <developers>
  25. <developer>
  26. <id>aclement</id>
  27. <name>Andy Clement</name>
  28. <email>aclement@vmware.com</email>
  29. </developer>
  30. <developer>
  31. <id>kriegaex</id>
  32. <name>Alexander Kriegisch</name>
  33. <email>kriegaex@aspectj.dev</email>
  34. </developer>
  35. </developers>
  36. <scm>
  37. <url>https://github.com/eclipse/org.aspectj</url>
  38. <connection>scm:git:https://github.com/eclipse/org.aspectj.git</connection>
  39. <developerConnection>scm:git:ssh://git@github.com:eclipse/org.aspectj.git</developerConnection>
  40. </scm>
  41. <properties>
  42. <!--
  43. TODO: Decide whether to publish this artifact on Maven Central or not. For now, skip the deployment until a final
  44. decision was made. If we do decide to publish, we need to add source and javadoc JARs. I suggest to re-use the
  45. ones from aspectjtools, because the installer contains runtime, weaver and tools and the latter one is a
  46. superset of the former two.
  47. -->
  48. <!-- By default, do not deploy artifacts - but deploy this public one -->
  49. <!--<maven.deploy.skip>false</maven.deploy.skip>-->
  50. <!-- By default, do not sign artifacts - but sign this public one -->
  51. <!--<maven.gpg.skip>false</maven.gpg.skip>-->
  52. </properties>
  53. <dependencies>
  54. <!-- Uber JARs to add to the installer archive: runtime, weaver, tools -->
  55. <dependency>
  56. <groupId>org.aspectj</groupId>
  57. <artifactId>aspectjrt</artifactId>
  58. <version>${project.version}</version>
  59. </dependency>
  60. <dependency>
  61. <groupId>org.aspectj</groupId>
  62. <artifactId>aspectjweaver</artifactId>
  63. <version>${project.version}</version>
  64. </dependency>
  65. <dependency>
  66. <groupId>org.aspectj</groupId>
  67. <artifactId>aspectjtools</artifactId>
  68. <version>${project.version}</version>
  69. </dependency>
  70. <!-- Executable JAR installer classes -->
  71. <dependency>
  72. <groupId>org.aspectj</groupId>
  73. <artifactId>build</artifactId>
  74. <version>${project.version}</version>
  75. </dependency>
  76. <!-- AspectJ documentation, created by Ant job in aj-build/dist/docs -->
  77. <dependency>
  78. <groupId>org.aspectj</groupId>
  79. <artifactId>docs</artifactId>
  80. <version>${project.version}</version>
  81. </dependency>
  82. <!-- Runtime javadocs - TODO: use full tools javadocs instead -->
  83. <dependency>
  84. <groupId>org.aspectj</groupId>
  85. <artifactId>runtime</artifactId>
  86. <version>${project.version}</version>
  87. </dependency>
  88. </dependencies>
  89. <build>
  90. <plugins>
  91. <!-- Skip creation of main + test JARs -->
  92. <plugin>
  93. <groupId>org.apache.maven.plugins</groupId>
  94. <artifactId>maven-jar-plugin</artifactId>
  95. <executions>
  96. <execution>
  97. <id>default-jar</id>
  98. <phase>none</phase>
  99. </execution>
  100. <execution>
  101. <id>test-jar</id>
  102. <phase>none</phase>
  103. </execution>
  104. </executions>
  105. </plugin>
  106. <plugin>
  107. <groupId>org.apache.maven.plugins</groupId>
  108. <artifactId>maven-assembly-plugin</artifactId>
  109. <executions>
  110. <execution>
  111. <id>aspectjinstaller-assembly</id>
  112. <phase>package</phase>
  113. <goals>
  114. <goal>single</goal>
  115. </goals>
  116. <configuration>
  117. <finalName>aspectj-${project.version}</finalName>
  118. <appendAssemblyId>false</appendAssemblyId>
  119. <archive>
  120. <manifestEntries>
  121. <Main-Class>$installer$.org.aspectj.Main</Main-Class>
  122. </manifestEntries>
  123. </archive>
  124. <descriptors>
  125. <descriptor>aspectjinstaller-assembly.xml</descriptor>
  126. </descriptors>
  127. </configuration>
  128. </execution>
  129. </executions>
  130. </plugin>
  131. <!-- Caveat: Attaching the flattened POM needs packaging=jar, so do not use packaging=pom for this module -->
  132. <plugin>
  133. <groupId>org.codehaus.mojo</groupId>
  134. <artifactId>flatten-maven-plugin</artifactId>
  135. <executions>
  136. <!-- Remove dependencies declared in this POM (if any) from uber JAR and strip down POM -->
  137. <execution>
  138. <id>flatten</id>
  139. <phase>process-resources</phase>
  140. <goals>
  141. <goal>flatten</goal>
  142. </goals>
  143. <configuration>
  144. <flattenMode>oss</flattenMode>
  145. <pomElements>
  146. <dependencies>remove</dependencies>
  147. <repositories>remove</repositories>
  148. </pomElements>
  149. <outputDirectory>${project.build.directory}</outputDirectory>
  150. <flattenedPomFilename>flattened-pom.xml</flattenedPomFilename>
  151. </configuration>
  152. </execution>
  153. </executions>
  154. </plugin>
  155. </plugins>
  156. <pluginManagement>
  157. <plugins>
  158. <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
  159. <plugin>
  160. <groupId>org.eclipse.m2e</groupId>
  161. <artifactId>lifecycle-mapping</artifactId>
  162. <version>1.0.0</version>
  163. <configuration>
  164. <lifecycleMappingMetadata>
  165. <pluginExecutions>
  166. <pluginExecution>
  167. <pluginExecutionFilter>
  168. <groupId>
  169. org.codehaus.mojo
  170. </groupId>
  171. <artifactId>
  172. flatten-maven-plugin
  173. </artifactId>
  174. <versionRange>
  175. [1.2.2,)
  176. </versionRange>
  177. <goals>
  178. <goal>flatten</goal>
  179. </goals>
  180. </pluginExecutionFilter>
  181. <action>
  182. <ignore></ignore>
  183. </action>
  184. </pluginExecution>
  185. </pluginExecutions>
  186. </lifecycleMappingMetadata>
  187. </configuration>
  188. </plugin>
  189. </plugins>
  190. </pluginManagement>
  191. </build>
  192. </project>