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 10KB

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
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
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
2 years ago
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302
  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>aspectjmatcher</artifactId>
  11. <name>AspectJ Matcher</name>
  12. <description>
  13. The AspectJ matcher can be used for matching pointcuts independently of any AspectJ compilation or weaving steps.
  14. Most notably, this can be used by frameworks such as Spring AOP which utilise the @AspectJ pointcut syntax but
  15. implement aspect weaving in a way independent of AspectJ, e.g. using dynamic proxies.
  16. </description>
  17. <url>https://www.eclipse.org/aspectj/</url>
  18. <licenses>
  19. <license>
  20. <name>Eclipse Public License - v 2.0</name>
  21. <url>https://www.eclipse.org/org/documents/epl-2.0/EPL-2.0.txt</url>
  22. <distribution>repo</distribution>
  23. </license>
  24. </licenses>
  25. <developers>
  26. <developer>
  27. <id>aclement</id>
  28. <name>Andy Clement</name>
  29. <email>aclement@vmware.com</email>
  30. </developer>
  31. <developer>
  32. <id>kriegaex</id>
  33. <name>Alexander Kriegisch</name>
  34. <email>kriegaex@aspectj.dev</email>
  35. </developer>
  36. </developers>
  37. <scm>
  38. <url>https://github.com/eclipse/org.aspectj</url>
  39. <connection>scm:git:https://github.com/eclipse/org.aspectj.git</connection>
  40. <developerConnection>scm:git:ssh://git@github.com:eclipse/org.aspectj.git</developerConnection>
  41. </scm>
  42. <properties>
  43. <!-- By default, do not deploy artifacts - but deploy this public one -->
  44. <maven.deploy.skip>false</maven.deploy.skip>
  45. <!-- By default, do not sign artifacts - but sign this public one -->
  46. <maven.gpg.skip>false</maven.gpg.skip>
  47. </properties>
  48. <build>
  49. <plugins>
  50. <!-- Skip creation of main + test JARs -->
  51. <plugin>
  52. <groupId>org.apache.maven.plugins</groupId>
  53. <artifactId>maven-jar-plugin</artifactId>
  54. <executions>
  55. <execution>
  56. <id>default-jar</id>
  57. <phase>none</phase>
  58. </execution>
  59. <execution>
  60. <id>test-jar</id>
  61. <phase>none</phase>
  62. </execution>
  63. </executions>
  64. </plugin>
  65. <plugin>
  66. <groupId>org.apache.maven.plugins</groupId>
  67. <artifactId>maven-assembly-plugin</artifactId>
  68. <executions>
  69. <execution>
  70. <id>aspectjmatcher-assembly</id>
  71. <phase>package</phase>
  72. <goals>
  73. <goal>single</goal>
  74. </goals>
  75. <configuration>
  76. <finalName>aspectjmatcher-${project.version}</finalName>
  77. <appendAssemblyId>false</appendAssemblyId>
  78. <archive>
  79. <manifestEntries>
  80. <Automatic-Module-Name>org.aspectj.matcher</Automatic-Module-Name>
  81. <!--
  82. <Premain-Class>org.aspectj.weaver.loadtime.Agent</Premain-Class>
  83. <Agent-Class>org.aspectj.weaver.loadtime.Agent</Agent-Class>
  84. <Can-Redefine-Classes>true</Can-Redefine-Classes>
  85. -->
  86. </manifestEntries>
  87. <manifestSections>
  88. <manifestSection>
  89. <name>org/aspectj/matcher/</name>
  90. <manifestEntries>
  91. <Specification-Title>AspectJ Matcher Classes</Specification-Title>
  92. <Specification-Version>${project.version}</Specification-Version>
  93. <Specification-Vendor>https://www.eclipse.org/aspectj/</Specification-Vendor>
  94. <Implementation-Title>org.aspectj.matcher</Implementation-Title>
  95. <Implementation-Version>${project.version}</Implementation-Version>
  96. <Implementation-Vendor>https://www.eclipse.org/aspectj/</Implementation-Vendor>
  97. <Bundle-Name>AspectJ Matcher</Bundle-Name>
  98. <Bundle-Version>${project.version}</Bundle-Version>
  99. <!--
  100. WARNING: Please avoid line breaks in manifest values! They are passed on like this:
  101. Assembly Plugin -> Plexus Archiver -> JRE java.util.jar.Manifest.write(OutputStream).
  102. The JRE Manifest class inserts hard line breaks always after 72 characters, no matter if those
  103. 72 characters contain line feeds, tabs or spaces. Hence, it can happen that unwanted blank lines
  104. end up in the middle of a manifest section, making the manifest invalid. Calls like e.g.
  105. 'java -cp aspectjtools.jar org.aspectj.tools.ajc.Main' can then fail with the absolutely
  106. unexpected error 'Could not find or load main class org.aspectj.tools.ajc.Main'.
  107. Alexander Kriegisch created this bug ticket:
  108. https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8263924
  109. In IntelliJ IDEA you can deactivate wrapping text inside XML tags like this:
  110. File | Settings | Editor | Code Style | XML | Wrap text -> deactivate
  111. -->
  112. <Bundle-Copyright>(C) Copyright 1999-2001 Xerox Corporation, 2002 Palo Alto Research Center, Incorporated (PARC), 2003-2020 Contributors. All Rights Reserved</Bundle-Copyright>
  113. </manifestEntries>
  114. </manifestSection>
  115. </manifestSections>
  116. </archive>
  117. <descriptors>
  118. <descriptor>aspectjmatcher-assembly.xml</descriptor>
  119. </descriptors>
  120. </configuration>
  121. </execution>
  122. <execution>
  123. <id>aspectjmatcher-sources-assembly</id>
  124. <phase>package</phase>
  125. <goals>
  126. <goal>single</goal>
  127. </goals>
  128. <configuration>
  129. <!-- The assembly ID 'sources' becomes the artifact classifier, exactly what we want -->
  130. <appendAssemblyId>true</appendAssemblyId>
  131. <skipAssembly>${maven.source.skip}</skipAssembly>
  132. <archive>
  133. </archive>
  134. <descriptors>
  135. <descriptor>aspectjmatcher-sources-assembly.xml</descriptor>
  136. </descriptors>
  137. </configuration>
  138. </execution>
  139. </executions>
  140. </plugin>
  141. <plugin>
  142. <groupId>org.codehaus.mojo</groupId>
  143. <artifactId>truezip-maven-plugin</artifactId>
  144. <executions>
  145. <execution>
  146. <id>unzip-relocated-sources</id>
  147. <phase>package</phase>
  148. <goals>
  149. <goal>copy</goal>
  150. </goals>
  151. <configuration>
  152. <!--
  153. Skip, if javadoc generation is also meant to be skipped, which is the default unless the 'release'
  154. profile is active or the property is overridden manually to be false. See property definitions in parent
  155. POM for default case and release profile.
  156. -->
  157. <skip>${maven.javadoc.skip}</skip>
  158. <verbose>true</verbose>
  159. <fileset>
  160. <directory>${project.build.directory}/${project.build.finalName}-sources.jar</directory>
  161. <outputDirectory>${project.build.directory}/unpacked-sources</outputDirectory>
  162. </fileset>
  163. </configuration>
  164. </execution>
  165. </executions>
  166. </plugin>
  167. <plugin>
  168. <groupId>org.apache.maven.plugins</groupId>
  169. <artifactId>maven-javadoc-plugin</artifactId>
  170. <executions>
  171. <execution>
  172. <id>javadoc-jar</id>
  173. <phase>package</phase>
  174. <goals>
  175. <goal>jar</goal>
  176. </goals>
  177. <configuration>
  178. <sourcepath>${project.build.directory}/unpacked-sources</sourcepath>
  179. <!-- TODO: Include 'aj' package for ASM-renamed contained in aspectjtools? -->
  180. <subpackages>org.aspectj</subpackages>
  181. <!-- Deactivate doclint checks in order to suppress errors -->
  182. <doclint>none</doclint>
  183. <!-- Generate class use xref, making javadocs considerably bigger, but also more informative -->
  184. <use>true</use>
  185. <!-- FIXME: Why does it fail without this parameter? -->
  186. <javadocVersion>8</javadocVersion>
  187. </configuration>
  188. </execution>
  189. </executions>
  190. </plugin>
  191. <!-- Caveat: Attaching the flattened POM needs packaging=jar, so do not use packaging=pom for this module -->
  192. <plugin>
  193. <groupId>org.codehaus.mojo</groupId>
  194. <artifactId>flatten-maven-plugin</artifactId>
  195. <executions>
  196. <!-- Remove dependencies declared in this POM (if any) from uber JAR and strip down POM -->
  197. <execution>
  198. <id>flatten</id>
  199. <phase>process-resources</phase>
  200. <goals>
  201. <goal>flatten</goal>
  202. </goals>
  203. <configuration>
  204. <flattenMode>oss</flattenMode>
  205. <pomElements>
  206. <dependencies>remove</dependencies>
  207. <repositories>remove</repositories>
  208. </pomElements>
  209. <outputDirectory>${project.build.directory}</outputDirectory>
  210. <flattenedPomFilename>flattened-pom.xml</flattenedPomFilename>
  211. </configuration>
  212. </execution>
  213. </executions>
  214. </plugin>
  215. <!-- Deploy this module to Nexus (Sonatype OSSRH, releases promotable to Maven Central) -->
  216. <plugin>
  217. <groupId>org.sonatype.plugins</groupId>
  218. <artifactId>nexus-staging-maven-plugin</artifactId>
  219. </plugin>
  220. </plugins>
  221. <pluginManagement>
  222. <plugins>
  223. <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
  224. <plugin>
  225. <groupId>org.eclipse.m2e</groupId>
  226. <artifactId>lifecycle-mapping</artifactId>
  227. <version>1.0.0</version>
  228. <configuration>
  229. <lifecycleMappingMetadata>
  230. <pluginExecutions>
  231. <pluginExecution>
  232. <pluginExecutionFilter>
  233. <groupId>
  234. org.codehaus.mojo
  235. </groupId>
  236. <artifactId>
  237. flatten-maven-plugin
  238. </artifactId>
  239. <versionRange>
  240. [1.2.2,)
  241. </versionRange>
  242. <goals>
  243. <goal>flatten</goal>
  244. </goals>
  245. </pluginExecutionFilter>
  246. <action>
  247. <ignore></ignore>
  248. </action>
  249. </pluginExecution>
  250. </pluginExecutions>
  251. </lifecycleMappingMetadata>
  252. </configuration>
  253. </plugin>
  254. </plugins>
  255. </pluginManagement>
  256. </build>
  257. <dependencies>
  258. <dependency>
  259. <groupId>org.aspectj</groupId>
  260. <artifactId>util</artifactId>
  261. <version>${project.version}</version>
  262. </dependency>
  263. <dependency>
  264. <groupId>org.aspectj</groupId>
  265. <artifactId>bridge</artifactId>
  266. <version>${project.version}</version>
  267. </dependency>
  268. <dependency>
  269. <groupId>org.aspectj</groupId>
  270. <artifactId>org.aspectj.matcher</artifactId>
  271. <version>${project.version}</version>
  272. </dependency>
  273. </dependencies>
  274. </project>