[ http://jira.codehaus.org/browse/MASSEMBLY-103?page=comments#action_67146
]
Chris Chen commented on MASSEMBLY-103:
--------------------------------------
I'm getting building errors when I run "mvn compile" with your patch. Also,
the AssemblyMojoTest.java also gets patch problems, which isn't too difficult
to resolve. I checked out the same revision that your patch is diff'ed against
and I am still having problems.
{noformat}
java.lang.ArrayIndexOutOfBoundsException: 0
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.getJavaClass(JavaMojoDescriptorExtractor.java:467)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:486)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:69)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:99)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
{noformat}
> More powerful includes/excludes stuff in DependencySets in descriptors
> ----------------------------------------------------------------------
>
> Key: MASSEMBLY-103
> URL: http://jira.codehaus.org/browse/MASSEMBLY-103
> Project: Maven 2.x Assembly Plugin
> Type: New Feature
> Versions: 2.1
> Reporter: Richard van der Hoff
> Attachments: maven-assembly-plugin-filters.patch,
> maven-assembly-plugin-filters.v2.patch
>
>
> A couple of other issues - http://jira.codehaus.org/browse/MASSEMBLY-90,
> http://jira.codehaus.org/browse/MASSEMBLY-41 - have pointed out the need for
> more powerful filtering of dependency sets in assembly descriptors. I wanted
> to take this further, so as to allow quite powerful boolean expressions for
> the description of dependencies. For example, the assembly extract below will
> include anything which is not a "zip" in the org.apache.maven.* or
> org.codehaus.* groups.
> The attachment contains an implementation of this, and a couple of testcases
> for the new functionality.
> <dependencySet>
> <filter>
> <negate>false</negate>
> <subfilters>
> <filter>
> <matchAll>false</matchAll>
> <matchers>
> <matcher>
> <group>org.apache.maven.*</group>
> </matcher>
> <matcher>
> <group>org.codehaus.*</group>
> </matcher>
> </matchers>
> </filter>
> </subfilters>
> <matchers>
> <matcher>
> <type>zip</type>
> </matcher>
> </matchers>
> </filter>
> </dependencySet>
--
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
