[
http://jira.codehaus.org/browse/MASPECTJ-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Gianni updated MASPECTJ-16:
----------------------------------
Attachment: MASPECTJ-16.diff
A patch introducing type and classifier checking for module->dependency
resolution.
Also adds two specific tests.
The part that actually searches for the right artifact has been expanded, so it
could be worth eventually moving it somewhere else (eventually inside Module
itself) cause it is duplicated.
There is no specific flag, so I explicitly grant all the rights for inclusion
of this patch under the MIT license.
> <aspectLibrary> must support <type> (and <classifier>)
> ------------------------------------------------------
>
> Key: MASPECTJ-16
> URL: http://jira.codehaus.org/browse/MASPECTJ-16
> Project: Mojo AspectJ Plugin
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: René Zanner
> Priority: Blocker
> Attachments: MASPECTJ-16.diff
>
>
> When defining <aspectLibraries> in my plugin configuration, I can only use
> <groupId> and <artifactId> to specify dependencies from my POM. When I have
> two dependencies with the same coordinates but a different type, the plugin
> ignores the JAR type dependency because of failing with the other typed
> dependency.
> Example:
> <project>
> <dependency>
> <groupId>group</groupId>
> <artifactId>artifact</artifactId>
> </dependency>
> <dependency>
> <groupId>group</groupId>
> <artifactId>artifact</artifactId>
> <!-- specify a different artifact - not to be weaved - by <type> and
> <classifier> -->
> <classifier>mda</classifier>
> <type>xmi</type>
> </dependency>
> ...
> <plugins>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>aspectj-maven-plugin</artifactId>
> <configuration>
> <aspectLibraries>
> <aspectLibrary>
> <groupId>group</groupId>
> <artifactId>artifact</artifactId>
> <!-- cannot specify <type> "jar" (or <classifier>) here -->
> </aspectLibrary>
> </aspectLibraries>
> </configuration>
> </plugin>
> ...
> </plugins>
> ...
> </project>
> This is not weaving with the JAR type dependency because of the following
> warning:
> [WARNING] build config error: skipping missing, empty or corrupt aspectpath
> entry: ...\.m2\repository\group\artifact\1.83.0\artifact-1.83.0-mda.xmi
> Beforehand, the debug message
> [DEBUG] Adding -aspectpath:
> ...\.m2\repository\group\artifact\1.83.0\artifact-1.83.0-mda.xmi
> lets assume that the JAR type dependency was not even added to the
> aspectpath, so nothing is weaved at all.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
