[
http://jira.codehaus.org/browse/MASPECTJ-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262109#action_262109
]
Robert Scholte commented on MASPECTJ-94:
----------------------------------------
{quote}Anyway, even if it makes sense to keep weaveDependency or aspectLibrary,
they both should be unpacked and included as source folder.{quote}
Not by default, maybe as an option because it's an expensive and unusual
operation (using the jars often works as required). And you'll need to keep the
classloading-order in mind.
If the m-dependency-p solutions works, it's maybe better to change this to a
minor wish and adjust the title of the issue.
> <excludes> could also filter aspects included in <aspectLibrary>
> ----------------------------------------------------------------
>
> Key: MASPECTJ-94
> URL: http://jira.codehaus.org/browse/MASPECTJ-94
> Project: Mojo AspectJ Plugin
> Issue Type: Improvement
> Affects Versions: 1.3.1
> Environment: all
> Reporter: nodje
> Attachments: AcpectLibraryExclusionsAntStyle.zip
>
>
> I was trying to exclude an aspect contained in spring-aspects library, that I
> was specifying as <aspectLibrary> in the config, when I realized it couldn't
> be filtered.
> I've created a test that fails when aspectLibrary aspect are woven despite
> their exclusion. It is to be added to the src/it tests.
> It's not very clean as it's based on an external aspect library
> (spring-aspects), but it shows what is expected clearly I believe.
> Let me know if I'm being unclear.
--
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
