1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
|
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.aspectj</groupId>
<artifactId>aspectj-parent</artifactId>
<version>1.9.7.BUILD-SNAPSHOT</version>
</parent>
<artifactId>aspectjweaver</artifactId>
<name>AspectJ Weaver</name>
<properties>
<!-- By default, do not deploy artifacts - but deploy this public one -->
<maven.deploy.skip>false</maven.deploy.skip>
</properties>
<build>
<plugins>
<!-- Skip creation of main + test JARs -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<id>default-jar</id>
<phase>none</phase>
</execution>
<execution>
<id>test-jar</id>
<phase>none</phase>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>unzip-dependency-sources</id>
<goals>
<goal>unpack-dependencies</goal>
</goals>
<phase>prepare-package</phase>
<configuration>
<classifier>sources</classifier>
<!--<failOnMissingClassifierArtifact>false</failOnMissingClassifierArtifact>-->
<includeGroupIds>org.ow2.asm</includeGroupIds>
<includeArtifactIds>asm</includeArtifactIds>
<outputDirectory>${project.build.directory}/unzipped-sources</outputDirectory>
<!-- Avoid accidentally shading test-scoped dependencies like JUnit -->
<includeScope>runtime</includeScope>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<executions>
<execution>
<id>aspectjweaver-assembly</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<finalName>aspectjweaver-${project.version}</finalName>
<appendAssemblyId>false</appendAssemblyId>
<archive>
<manifestEntries>
<Automatic-Module-Name>org.aspectj.weaver</Automatic-Module-Name>
<Premain-Class>org.aspectj.weaver.loadtime.Agent</Premain-Class>
<Agent-Class>org.aspectj.weaver.loadtime.Agent</Agent-Class>
<Can-Redefine-Classes>true</Can-Redefine-Classes>
</manifestEntries>
<manifestSections>
<manifestSection>
<name>org/aspectj/weaver/</name>
<manifestEntries>
<Specification-Title>AspectJ Weaver Classes</Specification-Title>
<Specification-Version>${project.version}</Specification-Version>
<Specification-Vendor>https://www.eclipse.org/aspectj/</Specification-Vendor>
<Implementation-Title>org.aspectj.weaver</Implementation-Title>
<Implementation-Version>${project.version}</Implementation-Version>
<Implementation-Vendor>https://www.eclipse.org/aspectj/</Implementation-Vendor>
<Bundle-Name>AspectJ Weaver</Bundle-Name>
<Bundle-Version>${project.version}</Bundle-Version>
<!--
WARNING: Please avoid line breaks in manifest values! They are passed on like this:
Assembly Plugin -> Plexus Archiver -> JRE java.util.jar.Manifest.write(OutputStream).
The JRE Manifest class inserts hard line breaks always after 72 characters, no matter if those
72 characters contain line feeds, tabs or spaces. Hence, it can happen that unwanted blank lines
end up in the middle of a manifest section, making the manifest invalid. Calls like e.g.
'java -cp aspectjtools.jar org.aspectj.tools.ajc.Main' can then fail with the absolutely
unexpected error 'Could not find or load main class org.aspectj.tools.ajc.Main'.
Alexander Kriegisch created this bug ticket:
https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8263924
In IntelliJ IDEA you can deactivate wrapping text inside XML tags like this:
File | Settings | Editor | Code Style | XML | Wrap text -> deactivate
-->
<Bundle-Copyright>(C) Copyright 1999-2001 Xerox Corporation, 2002 Palo Alto Research Center, Incorporated (PARC), 2003-2020 Contributors. All Rights Reserved</Bundle-Copyright>
</manifestEntries>
</manifestSection>
</manifestSections>
</archive>
<descriptors>
<descriptor>aspectjweaver-assembly.xml</descriptor>
</descriptors>
</configuration>
</execution>
<execution>
<id>aspectjweaver-sources-assembly</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<!-- The assembly ID 'sources' becomes the artifact classifier, exactly what we want -->
<appendAssemblyId>true</appendAssemblyId>
<archive>
</archive>
<descriptors>
<descriptor>aspectjweaver-sources-assembly.xml</descriptor>
</descriptors>
</configuration>
</execution>
</executions>
</plugin>
<!--
Relocate ASM from 'org.objectweb.asm' to 'aj.org.objectweb.asm'
TODO: Using Maven Shade after Maven Assembly instead of creating uber JAR and relocating package names at the
same time is suboptimal and maybe slower than doing both at the same time. Migrating from Assembly to Shade
requires all dependencies to produce source JARs, though, which currently is not the case. Because we also
want to create a complete source JAR, for now we keep Assembly around, because it manually copies project
sources from their respective directories before zipping them up.
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<configuration>
<createSourcesJar>true</createSourcesJar>
<createDependencyReducedPom>false</createDependencyReducedPom>
<shadedArtifactAttached>false</shadedArtifactAttached>
</configuration>
<executions>
<execution>
<id>asm-relocate</id>
<phase>package</phase>
<goals>
<goal>shade</goal>
</goals>
<configuration>
<minimizeJar>false</minimizeJar>
<shadeSourcesContent>true</shadeSourcesContent>
<artifactSet>
<includes>
<include>${project.groupId}:${project.artifactId}</include>
</includes>
</artifactSet>
<relocations>
<relocation>
<pattern>org.objectweb.asm</pattern>
<shadedPattern>aj.org.objectweb.asm</shadedPattern>
</relocation>
</relocations>
</configuration>
</execution>
</executions>
</plugin>
<!-- Caveat: Attaching the flattened POM needs packaging=jar, so do not use packaging=pom for this module -->
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>flatten-maven-plugin</artifactId>
<executions>
<!-- Remove dependencies declared in this POM (if any) from uber JAR and strip down POM -->
<execution>
<id>flatten</id>
<phase>process-resources</phase>
<goals>
<goal>flatten</goal>
</goals>
<configuration>
<flattenMode>oss</flattenMode>
<pomElements>
<dependencies>remove</dependencies>
<repositories>remove</repositories>
</pomElements>
<outputDirectory>${project.build.directory}</outputDirectory>
<flattenedPomFilename>flattened-pom.xml</flattenedPomFilename>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>org.aspectj</groupId>
<artifactId>weaver</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.ow2.asm</groupId>
<artifactId>asm</artifactId>
</dependency>
</dependencies>
</project>
|
