[jira] Commented: (MNG-3586) jaxws mojo wsgen failure with maven 2.1
[ http://jira.codehaus.org/browse/MNG-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140592#action_140592 ] Brett Porter commented on MNG-3586: --- I can't reproduce this because the sources compiled in the initialize phase don't compile > jaxws mojo wsgen failure with maven 2.1 > > > Key: MNG-3586 > URL: http://jira.codehaus.org/browse/MNG-3586 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1 > Environment: Windows XP / Java 5 or 6 >Reporter: Henri Gomez > Fix For: 2.1-alpha-2 > > Attachments: sample-wsgen.zip > > > I can build jar projects using the jaxws wsgen mojo (1.9) under maven > 2.0.x but it failed under m2eclipse (0.9.3) when using maven 2.1 > embedded (it works if I switch m2eclipse to use the maven 2.0.9 on my > system). > I tried with various JVM (Sun and IBM 5 and 6) but still got the > problem with maven 2.1 embedded (maven 2.1-620417 and 2.1-655675): > error is : > From file: C:\workspace\xxx-er-go\pom.xml > Reason: Failed to execute wsgen > java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$100(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174) > at > org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) > at > org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:91) > at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) > at > org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) > at > org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:903) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) > at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:52) > Any idea or fixes ? > my pom.xml wsgen is standard : > > > > maven-compiler-plugin > > 1.5 > 1.5 > > > > compile > > compile > > initialize > > > > > > > org.codehaus.mojo > jaxws-maven-plugin > > > go
[jira] Updated: (MASSEMBLY-336) Flag to inline POM dependencies in DependencySets
[ http://jira.codehaus.org/browse/MASSEMBLY-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MASSEMBLY-336: - Attachment: MASSEMBLY-336-1.patch Updated patch. The last one assumed that the current project is of packaging type "pom" which is an unnecessary requirement. Also I've cleaned up the white spaces (removed tabs) in the patch. Although the patch was generated against the tagged version 2.2-beta-2 it can be applied flawlessly to trunk (svn 673932). > Flag to inline POM dependencies in DependencySets > - > > Key: MASSEMBLY-336 > URL: http://jira.codehaus.org/browse/MASSEMBLY-336 > Project: Maven 2.x Assembly Plugin > Issue Type: New Feature >Affects Versions: 2.2-beta-2 >Reporter: Joerg Schaible > Attachments: MASSEMBLY-336-1.patch, MASSEMBLY-336.patch > > > We use the assembly plugin to generate a general distribution of our product > by packaging a lot of "final" artifacts non-transitively. Works fine. > However, for some project specific distributions we need to drop some of the > artifacts and add some others. However, in this case we must now repeat the > complete unchanged dependencies in the project specific version. > We came up with a solution using the POM as dependency to get all the > standard artifacts and declare a runtime dep to this POM in the project > specific distribution (with exclusions). Unfortunately in this case we can > now use neither a DependencySet without transitive dependencies (then we will > include the dependent POM only) nor with complete transitive deps, since then > we will not only include the "final" deps of the general distribution, but > their transitive dependencies also. > Therefore we patched the assembly plugin to support a new flag > "inlinePomDependencies" that forces the plugin to handle a POM dependency as > if the dependencies of the dependent POM had been declared directly in the > current one. If the DependencySet is collecting all transitive deps, the > resulting archive will simply not contain all dependent artifacts of type > "pom", if the DependencySet is collecting direct dependencies only, it will > also include all direct dependencies of the transitive dependencies of type > "pom". -- 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
[jira] Commented: (MNG-3586) jaxws mojo wsgen failure with maven 2.1
[ http://jira.codehaus.org/browse/MNG-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140596#action_140596 ] Henri Gomez commented on MNG-3586: -- Something change in this mojo recently, I'll track it down and fix the pom > jaxws mojo wsgen failure with maven 2.1 > > > Key: MNG-3586 > URL: http://jira.codehaus.org/browse/MNG-3586 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1 > Environment: Windows XP / Java 5 or 6 >Reporter: Henri Gomez > Fix For: 2.1-alpha-2 > > Attachments: pom.xml, sample-wsgen.zip > > > I can build jar projects using the jaxws wsgen mojo (1.9) under maven > 2.0.x but it failed under m2eclipse (0.9.3) when using maven 2.1 > embedded (it works if I switch m2eclipse to use the maven 2.0.9 on my > system). > I tried with various JVM (Sun and IBM 5 and 6) but still got the > problem with maven 2.1 embedded (maven 2.1-620417 and 2.1-655675): > error is : > From file: C:\workspace\xxx-er-go\pom.xml > Reason: Failed to execute wsgen > java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$100(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174) > at > org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) > at > org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:91) > at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) > at > org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) > at > org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:903) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) > at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:52) > Any idea or fixes ? > my pom.xml wsgen is standard : > > > > maven-compiler-plugin > > 1.5 > 1.5 > > > > compile > > compile > > initialize > > > > > > > org.codehaus.mojo > jaxws-maven-plugin > > > go-wsgen >
[jira] Updated: (MNG-3586) jaxws mojo wsgen failure with maven 2.1
[ http://jira.codehaus.org/browse/MNG-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milos Kleint updated MNG-3586: -- Attachment: pom.xml i've had to change the pom.xml config according to the help from https://jax-ws-commons.dev.java.net/jaxws-maven-plugin/usage.html then it built correctly for me using the latest embedded maven (3/7/2008) and latest mevenide/netbeans sourcebase. Not sure if it works in released mevenide as well. > jaxws mojo wsgen failure with maven 2.1 > > > Key: MNG-3586 > URL: http://jira.codehaus.org/browse/MNG-3586 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1 > Environment: Windows XP / Java 5 or 6 >Reporter: Henri Gomez > Fix For: 2.1-alpha-2 > > Attachments: pom.xml, sample-wsgen.zip > > > I can build jar projects using the jaxws wsgen mojo (1.9) under maven > 2.0.x but it failed under m2eclipse (0.9.3) when using maven 2.1 > embedded (it works if I switch m2eclipse to use the maven 2.0.9 on my > system). > I tried with various JVM (Sun and IBM 5 and 6) but still got the > problem with maven 2.1 embedded (maven 2.1-620417 and 2.1-655675): > error is : > From file: C:\workspace\xxx-er-go\pom.xml > Reason: Failed to execute wsgen > java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$100(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174) > at > org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) > at > org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:91) > at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) > at > org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) > at > org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:903) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) > at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:52) > Any idea or fixes ? > my pom.xml wsgen is standard : > > > > maven-compiler-plugin > > 1.5 > 1.5 > > > > compile > > compile > > initialize > > > > > > > o
[jira] Commented: (MASSEMBLY-76) [assembly plugin] improve or clarify inheriting/reusing descriptors
[ http://jira.codehaus.org/browse/MASSEMBLY-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140598#action_140598 ] Joerg Schaible commented on MASSEMBLY-76: - ... but maven-assembly-artifact-types has not been released with 2.2-beta-2. Note that this seems pure oversight. The tagged version of the maven-assembly-plugin-2.2-beta-2 contains the sub module for maven-assembly-artifact-types which declares its version still as 2.2-beta-2-SNAPSHOT (and so does trunk)! > [assembly plugin] improve or clarify inheriting/reusing descriptors > --- > > Key: MASSEMBLY-76 > URL: http://jira.codehaus.org/browse/MASSEMBLY-76 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Reporter: Jacob Robertson > Fix For: 2.2 > > > I want to declare a new reusable assembly descriptor. Then, in my parent pom > I can reference that descriptor, and all children projects will be able to do > assembly:assembly without specifying the descriptor. This actually works > halfway, but then the assembly plugin can't find the descriptor - because it > doesn't live inside of the child project. I was trying to play around with > putting the descriptor in the parent project, but since the packaging has to > be "pom" that of course wouldn't work. > Unless I misunderstand, the way this currently works, I'd have to declare the > descriptor for each and every child project. Which would be very > unfortunate, since the 3 supplied predefined descriptors don't meet my needs. > If there is a way to do this, then the improvement request is to improve the > documentation for this since I couldn't figure it out... -- 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
[jira] Closed: (MNG-3586) jaxws mojo wsgen failure with maven 2.1
[ http://jira.codehaus.org/browse/MNG-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-3586. - Assignee: Brett Porter Resolution: Cannot Reproduce Fix Version/s: (was: 2.1-alpha-2) 2.1-alpha-1 same here from the command line (as long as I'm using Java 6.0, both versions work. I suspect the sample hasn't even been tested on Java 5 since it doesn't include the JARs that provide javax.jws...) > jaxws mojo wsgen failure with maven 2.1 > > > Key: MNG-3586 > URL: http://jira.codehaus.org/browse/MNG-3586 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1 > Environment: Windows XP / Java 5 or 6 >Reporter: Henri Gomez >Assignee: Brett Porter > Fix For: 2.1-alpha-1 > > Attachments: pom.xml, sample-wsgen.zip > > > I can build jar projects using the jaxws wsgen mojo (1.9) under maven > 2.0.x but it failed under m2eclipse (0.9.3) when using maven 2.1 > embedded (it works if I switch m2eclipse to use the maven 2.0.9 on my > system). > I tried with various JVM (Sun and IBM 5 and 6) but still got the > problem with maven 2.1 embedded (maven 2.1-620417 and 2.1-655675): > error is : > From file: C:\workspace\xxx-er-go\pom.xml > Reason: Failed to execute wsgen > java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$100(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174) > at > org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) > at > org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:91) > at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) > at > org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) > at > org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:903) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) > at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:52) > Any idea or fixes ? > my pom.xml wsgen is standard : > > > > maven-compiler-plugin > > 1.5 > 1.5 > > > > compile > > compile > > initialize > > > > > >
[jira] Updated: (MNG-3628) When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository
[ http://jira.codehaus.org/browse/MNG-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3628: -- Fix Version/s: 2.0.x > When running offline, snapshot artifcats cannot be resolved even if they have > previously be dowloaded from a repository > --- > > Key: MNG-3628 > URL: http://jira.codehaus.org/browse/MNG-3628 > Project: Maven 2 > Issue Type: Bug >Reporter: Marc Harris > Fix For: 2.0.x > > Attachments: maven-offline-snapshot-problem.tar > > > When running offline, snapshot artifcats cannot be resolved even if they have > previously be dowloaded from a repository. This happens when attempting to > depend on a snapshot version of a module downloaded from a repository. If the > snapshot version of the module is built and installed locally, the problem > goes away. > I will attach two projects (in a tar file) that have minimal external > dependencies, and the debug output of trying to build. Here are the steps to > reproduce: > Environment: > Maven 2.0.8 > Linux 2.6.18 > Artifactory 1.2.5 (rev. 1154) > (this has also been reproduced by a colleague on a Windows machine). > Preliminary steps: > 1) Modify the pom files to refer to your actual repository instead of > http://localhost:8081/artifactory/jumptap-snapshots > 2) Build maven-test-project1 > 3) Upload the pom and jar for maven-test-project1 to your repository. > Steps that cause the error to happen: > 1) Delete maven-test-project1 from the local repository. > 2) Build maven-test-project2 without the offline flag (mvn install). This > build is successful (and downloads maven-test-project1 to the local > repository). > 3) Build maven-test-project2 with the offline flag (mvn -o install). This > build fails, unable to resolve the maven-test-project1 artifact. > Steps that cause the error not to happen > 1) Build maven-test-project1 locally. This build is successful. > 2) Build maven-test-project2 without the offline flag (mvn install). This > build is successful. > 3) Build maven-test-project2 with the offline flag (mvn -o install). This > build is successful. -- 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
[jira] Closed: (MNG-3627) Maven complains for the lack of a test dependency even when skipping tests
[
http://jira.codehaus.org/browse/MNG-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-3627.
-
Assignee: Brett Porter
Resolution: Won't Fix
I understand this might be confusing, but there are other feature requests open
for improved skipping of phases that would accommodate this. As is, using the
skip parameter it is "by design" :)
> Maven complains for the lack of a test dependency even when skipping tests
> --
>
> Key: MNG-3627
> URL: http://jira.codehaus.org/browse/MNG-3627
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.0.9
>Reporter: Andrea Aime
>Assignee: Brett Porter
>
> Trying to build GeoServer trunk without tests (-Dmaven.test.skip=true) we're
> getting an error message stating that some jars marked as test dependencies
> are not found. In particular, these are the tests jar of another module in
> the build, which is not getting built because of the test.skip setting and
> it's not already available on the repository.
> Yet mvn dependency:tree does report the following:
> {panel}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'dependency'.
> [INFO]
>
> [INFO] Building Web Coverage Service 1.1.1 Module
> [INFO]task-segment: [dependency:tree]
> [INFO]
>
> [INFO] [dependency:tree]
> [INFO] org.geoserver:wcs1_1:jar:1.8.0-SNAPSHOT
> [INFO] +- org.geoserver:main:jar:1.8.0-SNAPSHOT:compile
> [INFO] | +- org.geoserver:data:jar:1.8.0-SNAPSHOT:compile
> [INFO] | | +- org.geoserver:platform:jar:1.8.0-SNAPSHOT:compile
> [INFO] | | | +- javax.media:jai_core:jar:1.1.3:compile
> [INFO] | | | +- javax.media:jai_codec:jar:1.1.3:compile
> [INFO] | | | \- javax.media:jai_imageio:jar:1.1:compile
> [INFO] | | +- org.geotools:gt-epsg-hsql:jar:2.5-SNAPSHOT:compile
> [INFO] | | +- org.geotools:gt-h2:jar:2.5-SNAPSHOT:compile
> [INFO] | | | +- org.h2database:h2:jar:1.0-SNAPSHOT:compile
> [INFO] | | | +- org.openplans:spatialdbbox:jar:1.0-SNAPSHOT:compile
> [INFO] | | | \- mysql:mysql-connector-java:jar:5.1.5:compile
> [INFO] | | +- org.geotools:gt-property:jar:2.5-SNAPSHOT:compile
> [INFO] | | +- org.geotools.xsd:gt-xsd-gml2:jar:2.5-SNAPSHOT:compile
> [INFO] | | \- xml-apis:xml-apis-xerces:jar:2.7.1:compile
> [INFO] | +- org.geoserver:ows:jar:1.8.0-SNAPSHOT:compile
> [INFO] | | +- org.acegisecurity:acegi-security:jar:1.0.3:compile
> [INFO] | | | +- org.springframework:spring-jdbc:jar:2.5.2:compile (version
> managed from 1.2.8)
> [INFO] | | | | \- org.springframework:spring-tx:jar:2.5.2:compile
> [INFO] | | | \- commons-codec:commons-codec:jar:1.3:compile
> [INFO] | | +- commons-lang:commons-lang:jar:2.1:compile
> [INFO] | | +- org.geotools.xsd:gt-xsd-core:jar:2.5-SNAPSHOT:compile
> [INFO] | | \- xpp3:xpp3:jar:1.1.3.4.O:compile
> [INFO] | +- javax.servlet:servlet-api:jar:2.4:compile
> [INFO] | +- org.restlet:org.restlet:jar:1.0.8:compile (version managed from
> 1.0.5)
> [INFO] | +- org.restlet:org.restlet.ext.freemarker:jar:1.0.8:compile
> (version managed from 1.0.5)
> [INFO] | +-
> com.noelios.restlet:com.noelios.restlet.ext.servlet:jar:1.0.8:compile
> (version managed from 1.0.5)
> [INFO] | | \- com.noelios.restlet:com.noelios.restlet:jar:1.0.8:compile
> [INFO] | +- net.sf.json-lib:json-lib:jar:jdk13:2.1:compile
> [INFO] | | +- commons-collections:commons-collections:jar:3.1:compile
> [INFO] | | \- net.sf.ezmorph:ezmorph:jar:1.0.3:compile
> [INFO] | +- struts:struts:jar:1.2.9:compile
> [INFO] | | \- antlr:antlr:jar:2.7.2:compile
> [INFO] | +- xml-apis:xml-apis:jar:1.0.b2:compile
> [INFO] | +- xerces:xercesImpl:jar:2.6.2:compile
> [INFO] | +- xalan:xalan:jar:2.7.0:compile
> [INFO] | +- commons-beanutils:commons-beanutils:jar:1.7.0:compile
> [INFO] | +- commons-digester:commons-digester:jar:1.7:compile
> [INFO] | +- commons-fileupload:commons-fileupload:jar:1.2.1:compile
> [INFO] | +- commons-io:commons-io:jar:1.3.2:compile
> [INFO] | +- commons-httpclient:commons-httpclient:jar:2.0:compile
> [INFO] | +- commons-validator:commons-validator:jar:1.1.4:compile
> [INFO] | +- org.freemarker:freemarker:jar:2.3.13:compile
> [INFO] | +- oro:oro:jar:2.0.8:compile
> [INFO] | +- org.geotools:gt-cql:jar:2.5-SNAPSHOT:compile
> [INFO] | +- log4j:log4j:jar:1.2.14:compile
> [INFO] | +- org.geotools:gt-coverage:jar:2.5-SNAPSHOT:compile
> [INFO] | +- org.geotools:gt-validation:jar:2.5-SNAPSHOT:compile
> [INFO] | | \- org.geotools:gt-graph:jar:2.5-SNAPSHOT:compile
> [INFO] | +- org.geotools:gt-data:jar:2.5-SNAPSHOT:compile
> [INFO] | +- org.geotools:gt-jdbc:jar:2.5-S
[jira] Commented: (MNG-3556) XML entity not supported in Maven 2
[
http://jira.codehaus.org/browse/MNG-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140604#action_140604
]
Manuel EVENO commented on MNG-3556:
---
Related to this proposal :
http://docs.codehaus.org/display/MAVENUSER/Optional+support+for+splitting+up+pom.xml+in+multiple+files
I known it would allow us to create POMs that are no longer self contained but
maintaining huge parent pom is a mess.
When you have dependencyManagement + pluginManagement + build + reporting ...
fully configured, parent pom is really hard to maintain.
The solution we have, is to create an artificial hierarchy to split the pom
* common-build
** common-dependencyManagement (with maybe pluginManagement too)
** common-reporting
So, in this case, the fact is we already split the pom to be able to maintain
it.
Perhaps you could allow pom splitting only for project of 'pom' packaging type
> XML entity not supported in Maven 2
> ---
>
> Key: MNG-3556
> URL: http://jira.codehaus.org/browse/MNG-3556
> Project: Maven 2
> Issue Type: Bug
> Components: General
>Reporter: Dan Fabulich
> Fix For: 2.x
>
> Attachments: pom.xml
>
>
> The attached XML file defines and uses an XML entity called "&blah;". It
> validates in FF and in other XML parsers, but when I attempt to load it up in
> Maven, I get the fellowing exception:
> {code}
> [INFO] Scanning for projects...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] Error building POM (may not be this project's POM).
> Project ID: unknown
> POM Location: C:\blah\pom.xml
> Reason: Parse error reading POM. Reason: could not resolve entity named
> 'blah' (position: START_TAG seen ...\r\n &blah;... @11:15)
> for project unknown at C:\blah\pom.xml
> [INFO]
>
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Parse error reading POM.
> Reason: could not resolve entity named 'blah' (position: START_TAG seen
> ...\r\n &blah;... @11:15) for project unknown at
> C:\blah\pom.xml
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:376)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:289)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> 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:597)
> 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)
> Caused by: org.apache.maven.project.InvalidProjectModelException: Parse error
> reading POM. Reason: could not resolve entity named 'blah' (position:
> START_TAG seen ...\r\n &blah;... @11:15) for project
> unknown at C:\blah\pom.xml
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1416)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1377)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:474)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:548)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:458)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:362)
> ... 11 more
> Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: could
> not resolve entity named 'blah' (position: START_TAG seen ...\r\n
> &blah;... @11:15)
> at
> org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1282)
> at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1093)
> at
> org.codehaus.plexus.util.xml.pull.MXParser.nextText(MXParser.java:1058)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2050)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4422)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.readMod
[jira] Updated: (MNG-3629) mvn install-file suggestion wrong?
[ http://jira.codehaus.org/browse/MNG-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3629: -- Fix Version/s: 2.0.x > mvn install-file suggestion wrong? > -- > > Key: MNG-3629 > URL: http://jira.codehaus.org/browse/MNG-3629 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9 >Reporter: Marvin Froeder > Fix For: 2.0.x > > > Hi, > On flex-mojos, I have one type where type != extension: > > > org.apache.maven.artifact.handler.ArtifactHandler > resource-bundle > > org.apache.maven.artifact.handler.DefaultArtifactHandler > > resource-bundle > swc > > > But, when this artifact is missing, maven show this: > [INFO] Failed to resolve artifact. > Missing: > -- > 1) com.adobe.flex.sdk:framework:resource-bundle:asdas:3.0.0.477 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=com.adobe.flex.sdk > -DartifactId=framework -Dversion=3.0.0.477 -Dclassifier=asdas > -Dpackaging=resource-bundle -Dfile= > /path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=com.adobe.flex.sdk > -DartifactId=framework -Dversion=3.0.0.477 -Dclassifier=asdas > -Dpackaging=resource-bundle -Dfile=/p > ath/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) com.datasul.test:optimization:swf:1.0-SNAPSHOT > 2) com.adobe.flex.sdk:framework:resource-bundle:asdas:3.0.0.477 > -- > 1 required artifact is missing. > If I install following this, the artifact on repository will be wrong. > I need to install like this: > mvn install:install-file -DgroupId=com.adobe.flex.sdk -DartifactId=framework > -Dversion=3.0.0.477 -Dclassifier=asdas -Dpackaging=swc -Dfile=/path/to/file > The packaging suggested by maven is wrong. > VELO -- 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
[jira] Commented: (MNG-3586) jaxws mojo wsgen failure with maven 2.1
[ http://jira.codehaus.org/browse/MNG-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140605#action_140605 ] Henri Gomez commented on MNG-3586: -- Right I missing deps (dam'nt Java 6) com.sun.xml.ws jaxws-rt 2.1.4 javax.annotation jsr250-api 1.0 javax.jws jsr181-api 1.0-MR1 Attached the corrected sample > jaxws mojo wsgen failure with maven 2.1 > > > Key: MNG-3586 > URL: http://jira.codehaus.org/browse/MNG-3586 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1 > Environment: Windows XP / Java 5 or 6 >Reporter: Henri Gomez >Assignee: Brett Porter > Fix For: 2.1-alpha-1 > > Attachments: pom.xml, sample-wsgen.zip > > > I can build jar projects using the jaxws wsgen mojo (1.9) under maven > 2.0.x but it failed under m2eclipse (0.9.3) when using maven 2.1 > embedded (it works if I switch m2eclipse to use the maven 2.0.9 on my > system). > I tried with various JVM (Sun and IBM 5 and 6) but still got the > problem with maven 2.1 embedded (maven 2.1-620417 and 2.1-655675): > error is : > From file: C:\workspace\xxx-er-go\pom.xml > Reason: Failed to execute wsgen > java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$100(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174) > at > org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) > at > org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:91) > at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) > at > org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) > at > org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:903) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) > at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:52) > Any idea or fixes ? > my pom.xml wsgen is standard : > > > > maven-compiler-plugin > > 1.5 > 1.5 > > > > compile > > compile > >
[jira] Updated: (MNG-3586) jaxws mojo wsgen failure with maven 2.1
[ http://jira.codehaus.org/browse/MNG-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Gomez updated MNG-3586: - Attachment: sample-wsgen-fixed.zip This one is with corrected POM > jaxws mojo wsgen failure with maven 2.1 > > > Key: MNG-3586 > URL: http://jira.codehaus.org/browse/MNG-3586 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1 > Environment: Windows XP / Java 5 or 6 >Reporter: Henri Gomez >Assignee: Brett Porter > Fix For: 2.1-alpha-1 > > Attachments: pom.xml, sample-wsgen-fixed.zip, sample-wsgen.zip > > > I can build jar projects using the jaxws wsgen mojo (1.9) under maven > 2.0.x but it failed under m2eclipse (0.9.3) when using maven 2.1 > embedded (it works if I switch m2eclipse to use the maven 2.0.9 on my > system). > I tried with various JVM (Sun and IBM 5 and 6) but still got the > problem with maven 2.1 embedded (maven 2.1-620417 and 2.1-655675): > error is : > From file: C:\workspace\xxx-er-go\pom.xml > Reason: Failed to execute wsgen > java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$100(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174) > at > org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) > at > org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:91) > at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) > at > org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) > at > org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:903) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) > at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:52) > Any idea or fixes ? > my pom.xml wsgen is standard : > > > > maven-compiler-plugin > > 1.5 > 1.5 > > > > compile > > compile > > initialize > > > > > > > org.codehaus.mojo > jaxws-maven-plugin > > > go-wsge
[jira] Commented: (MNG-3586) jaxws mojo wsgen failure with maven 2.1
[ http://jira.codehaus.org/browse/MNG-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140607#action_140607 ] Brett Porter commented on MNG-3586: --- this now gives: Exception in thread "main" java.lang.NoClassDefFoundError: javax/jws/WebService at com.sun.tools.ws.wscompile.WsgenOptions.validateEndpointClass(WsgenOptions.java:198) Under both 2.1-SNAPSHOT and 2.0.9. But it works under Java 1.5. > jaxws mojo wsgen failure with maven 2.1 > > > Key: MNG-3586 > URL: http://jira.codehaus.org/browse/MNG-3586 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1 > Environment: Windows XP / Java 5 or 6 >Reporter: Henri Gomez >Assignee: Brett Porter > Fix For: 2.1-alpha-1 > > Attachments: pom.xml, sample-wsgen-fixed.zip, sample-wsgen.zip > > > I can build jar projects using the jaxws wsgen mojo (1.9) under maven > 2.0.x but it failed under m2eclipse (0.9.3) when using maven 2.1 > embedded (it works if I switch m2eclipse to use the maven 2.0.9 on my > system). > I tried with various JVM (Sun and IBM 5 and 6) but still got the > problem with maven 2.1 embedded (maven 2.1-620417 and 2.1-655675): > error is : > From file: C:\workspace\xxx-er-go\pom.xml > Reason: Failed to execute wsgen > java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$100(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174) > at > org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) > at > org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:91) > at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) > at > org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) > at > org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:903) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) > at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:52) > Any idea or fixes ? > my pom.xml wsgen is standard : > > > > maven-compiler-plugin > > 1.5 > 1.5 > > > > compile > > compile > > initialize > > > > > >
[jira] Commented: (MNG-3586) jaxws mojo wsgen failure with maven 2.1
[ http://jira.codehaus.org/browse/MNG-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140609#action_140609 ] Henri Gomez commented on MNG-3586: -- With IBM JDK 1.5 and maven 2.0.9 : [DEBUG] jaxws:wsgen args: [-d, C:\Documents and Settings\gomezhe\Bureau\sample-wsgen\target\classes, -cp, C:\Documents and Settings\gomezhe\Bureau\sample-wsgen\target\classes;c:\maven-repository\com\sun\xml\ws\jaxws-rt\2.1.4\jaxws-rt-2.1.4.jar;c:\maven-repository\javax\xml\ws\jaxws-api\2.1\jaxws-api-2.1.jar;c:\maven-repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar;c:\maven-repository\javax\xml\stream\stax-api\1.0\stax-api-1.0.jar;c:\maven-repository\javax\activation\activation\1.1\activation-1.1.jar;c:\maven-repository\javax\xml\soap\saaj-api\1.3\saaj-api-1.3.jar;c:\maven-repository\javax\annotation\jsr250-api\1.0\jsr250-api-1.0.jar;c:\maven-repository\javax\jws\jsr181-api\1.0-MR1\jsr181-api-1.0-MR1.jar;c:\maven-repository\com\sun\xml\bind\jaxb-impl\2.1.7\jaxb-impl-2.1.7.jar;c:\maven-repository\com\sun\xml\messaging\saaj\saaj-impl\1.3.1\saaj-impl-1.3.1.jar;c:\maven-repository\com\sun\xml\stream\buffer\streambuffer\0.7\streambuffer-0.7.jar;c:\maven-repository\org\jvnet\staxex\stax-ex\1.2\stax-ex-1.2.jar;c:\maven-repository\junit\junit\3.8\junit-3.8.jar;c:\maven-repository\com\sun\xml\stream\sjsxp\1.0.1\sjsxp-1.0.1.jar;c:\maven-repository\com\sun\org\apache\xml\internal\resolver\20050927\resolver-20050927.jar;c:\maven-repository\org\jvnet\mimepull\1.2\mimepull-1.2.jar;c:\maven-repository\com\sun\xml\ws\jaxws-tools\2.1.3\jaxws-tools-2.1.3.jar;c:\maven-repository\com\sun\xml\ws\jaxws-rt\2.1.3\jaxws-rt-2.1.3.jar;c:\maven-repository\javax\xml\ws\jaxws-api\2.1\jaxws-api-2.1.jar;c:\maven-repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar;c:\maven-repository\javax\xml\stream\stax-api\1.0\stax-api-1.0.jar;c:\maven-repository\javax\activation\activation\1.1\activation-1.1.jar;c:\maven-repository\javax\xml\soap\saaj-api\1.3\saaj-api-1.3.jar;c:\maven-repository\javax\annotation\jsr250-api\1.0\jsr250-api-1.0.jar;c:\maven-repository\javax\jws\jsr181-api\1.0-MR1\jsr181-api-1.0-MR1.jar;c:\maven-repository\com\sun\xml\bind\jaxb-impl\2.1.6\jaxb-impl-2.1.6.jar;c:\maven-repository\com\sun\xml\messaging\saaj\saaj-impl\1.3\saaj-impl-1.3.jar;c:\maven-repository\com\sun\xml\stream\buffer\streambuffer\0.7\streambuffer-0.7.jar;c:\maven-repository\org\jvnet\staxex\stax-ex\1.2\stax-ex-1.2.jar;c:\maven-repository\com\sun\xml\stream\sjsxp\1.0\sjsxp-1.0.jar;c:\maven-repository\com\sun\org\apache\xml\internal\resolver\20050927\resolver-20050927.jar;c:\maven-repository\org\jvnet\mimepull\1.1\mimepull-1.1.jar;c:\maven-repository\com\sun\xml\bind\jaxb-xjc\2.1.6\jaxb-xjc-2.1.6.jar;c:\maven-repository\org\codehaus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar;C:\maven\lib\maven-2.0.9-uber.jar;C:\maven\lib\maven-2.0.9-uber.jar, -wsdl, -r, C:\Documents and Settings\gomezhe\Bureau\sample-wsgen\target\classes\com\mycorp\resources\wsdl, samplewsgen.SampleService] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to execute wsgen Embedded error: com.sun.tools.apt.Main [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute wsgen at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) 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(Launch
[jira] Created: (MRRESOURCES-35) ClassCastException
ClassCastException -- Key: MRRESOURCES-35 URL: http://jira.codehaus.org/browse/MRRESOURCES-35 Project: Maven 2.x Remote Resources Plugin Issue Type: Bug Affects Versions: 1.0 Reporter: Christian Schulte Priority: Blocker Having a dependency with RELEASE gives ClassCastException. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.model.Repository [INFO] [INFO] Trace java.lang.ClassCastException: org.apache.maven.model.Repository at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.mergeMetadata(DefaultRepositoryMetadataManager.java:193) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:166) at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:65) at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.transformForResolve(ReleaseArtifactTransformation.java:49) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForResolve(DefaultArtifactTransformationManager.java:57) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:129) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:557) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:250) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.getProjects(ProcessRemoteResourcesMojo.java:505) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.configureVelocityContext(ProcessRemoteResourcesMojo.java:665) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:413) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:466) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:127) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) 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) -- 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
[jira] Updated: (MRRESOURCES-35) ClassCastException
[ http://jira.codehaus.org/browse/MRRESOURCES-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MRRESOURCES-35: - Attachment: MRRESOURCES-35.patch The following patch fixes the ClassCastException for me. > ClassCastException > -- > > Key: MRRESOURCES-35 > URL: http://jira.codehaus.org/browse/MRRESOURCES-35 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Christian Schulte >Priority: Blocker > Attachments: MRRESOURCES-35.patch > > > Having a dependency with RELEASE gives ClassCastException. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] org.apache.maven.model.Repository > [INFO] > > [INFO] Trace > java.lang.ClassCastException: org.apache.maven.model.Repository > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.mergeMetadata(DefaultRepositoryMetadataManager.java:193) > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:166) > at > org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:65) > at > org.apache.maven.artifact.transform.ReleaseArtifactTransformation.transformForResolve(ReleaseArtifactTransformation.java:49) > at > org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForResolve(DefaultArtifactTransformationManager.java:57) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:129) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74) > at > org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:557) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:250) > at > org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.getProjects(ProcessRemoteResourcesMojo.java:505) > at > org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.configureVelocityContext(ProcessRemoteResourcesMojo.java:665) > at > org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:413) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:466) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:127) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) > 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) -- 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
[jira] Commented: (MASSEMBLY-76) [assembly plugin] improve or clarify inheriting/reusing descriptors
[ http://jira.codehaus.org/browse/MASSEMBLY-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140616#action_140616 ] Grégory Joseph commented on MASSEMBLY-76: - I second that. Had to keep my home-built snapshot for that :/ > [assembly plugin] improve or clarify inheriting/reusing descriptors > --- > > Key: MASSEMBLY-76 > URL: http://jira.codehaus.org/browse/MASSEMBLY-76 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Reporter: Jacob Robertson > Fix For: 2.2 > > > I want to declare a new reusable assembly descriptor. Then, in my parent pom > I can reference that descriptor, and all children projects will be able to do > assembly:assembly without specifying the descriptor. This actually works > halfway, but then the assembly plugin can't find the descriptor - because it > doesn't live inside of the child project. I was trying to play around with > putting the descriptor in the parent project, but since the packaging has to > be "pom" that of course wouldn't work. > Unless I misunderstand, the way this currently works, I'd have to declare the > descriptor for each and every child project. Which would be very > unfortunate, since the 3 supplied predefined descriptors don't meet my needs. > If there is a way to do this, then the improvement request is to improve the > documentation for this since I couldn't figure it out... -- 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
[jira] Closed: (MARTIFACT-26) Maven truncates the final "." from versionId 1.0.0.-SNAPSHOT
[ http://jira.codehaus.org/browse/MARTIFACT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MARTIFACT-26. - Assignee: Brett Porter Resolution: Fixed > Maven truncates the final "." from versionId 1.0.0.-SNAPSHOT > - > > Key: MARTIFACT-26 > URL: http://jira.codehaus.org/browse/MARTIFACT-26 > Project: Maven Artifact > Issue Type: Bug >Affects Versions: 3.0-alpha-1 >Reporter: Dave Syer >Assignee: Brett Porter >Priority: Minor > Fix For: 3.0-alpha-1 > > > Maven truncates the final "." from versionId 1.0.0.-SNAPSHOT. This appears > to be a regression, since it works OK in 2.0.8, but not in 2.0.6 or 2.1. > To reproduce: > 1. set up a Maven project with versionId 1.0.0.-SNAPSHOT (or X.X.-SNAPSHOT). > 2. run "mvn install" > 3. Look in the local repository for the artifact, and find it in a directory > called "1.0.0". -- 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
[jira] Commented: (MARTIFACT-26) Maven truncates the final "." from versionId 1.0.0.-SNAPSHOT
[ http://jira.codehaus.org/browse/MARTIFACT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140628#action_140628 ] Brett Porter commented on MARTIFACT-26: --- note that the fix is actually different to the cause - it appears it changed from using the straight string for version construction to using a parsed version / range. Both should behave consistently now. > Maven truncates the final "." from versionId 1.0.0.-SNAPSHOT > - > > Key: MARTIFACT-26 > URL: http://jira.codehaus.org/browse/MARTIFACT-26 > Project: Maven Artifact > Issue Type: Bug >Affects Versions: 3.0-alpha-1 >Reporter: Dave Syer >Assignee: Brett Porter >Priority: Minor > Fix For: 3.0-alpha-1 > > > Maven truncates the final "." from versionId 1.0.0.-SNAPSHOT. This appears > to be a regression, since it works OK in 2.0.8, but not in 2.0.6 or 2.1. > To reproduce: > 1. set up a Maven project with versionId 1.0.0.-SNAPSHOT (or X.X.-SNAPSHOT). > 2. run "mvn install" > 3. Look in the local repository for the artifact, and find it in a directory > called "1.0.0". -- 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
[jira] Commented: (MNG-3422) [regression] deploy:deploy-file does not work
[ http://jira.codehaus.org/browse/MNG-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140633#action_140633 ] Jason van Zyl commented on MNG-3422: This is not an active collection problem, it's a the wrong classloader being used by the active collection so no components are returned. Now I can fix it. > [regression] deploy:deploy-file does not work > - > > Key: MNG-3422 > URL: http://jira.codehaus.org/browse/MNG-3422 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter > Fix For: 2.1-alpha-1 > > > mvn deploy:deploy-file -Dfile=test.sh -DrepositoryId=testing > -DartifactId=artifactId -DgroupId=groupId -Dversion=1.0 -Dpackaging=jar > -Durl=http://vesuvius.devzuz.com/private/devzuz/releases > [INFO] Searching repository for plugin with prefix: 'deploy'. > [INFO] Attempting to resolve a version for plugin: > org.apache.maven.plugins:maven-deploy-plugin using meta-version: LATEST > [INFO] Using version: 2.3 of plugin: > org.apache.maven.plugins:maven-deploy-plugin > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Maven Default Project > [INFO] > [INFO] Id: org.apache.maven:super-pom:jar:2.1 > [INFO] task-segment: [deploy:deploy-file] (aggregator-style) > [INFO] > > [INFO] [deploy:deploy-file] > [INFO] artifact groupId:artifactId: checking for updates from testing > --- > constituent[0]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/aspectjrt-1.5.3.jar > constituent[1]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/backport-util-concurrent-3.0.jar > constituent[2]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/commons-cli-1.0.jar > constituent[3]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/doxia-sink-api-1.0-alpha-9.jar > constituent[4]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/jsch-0.1.27.jar > constituent[5]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/jtidy-4aug2000r7-dev.jar > constituent[6]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-artifact-3.0-SNAPSHOT.jar > constituent[7]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-core-2.1-SNAPSHOT.jar > constituent[8]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-embedder-2.1-SNAPSHOT.jar > constituent[9]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-lifecycle-2.1-SNAPSHOT.jar > constituent[10]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-model-2.1-SNAPSHOT.jar > constituent[11]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-plugin-api-2.1-SNAPSHOT.jar > constituent[12]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-profile-2.1-SNAPSHOT.jar > constituent[13]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-project-2.1-SNAPSHOT.jar > constituent[14]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-reporting-api-2.1-SNAPSHOT.jar > constituent[15]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-container-default-1.0-alpha-44.jar > constituent[16]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-interactivity-api-1.0-alpha-6.jar > constituent[17]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-utils-1.5.1.jar > constituent[18]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/retrotranslator-runtime-1.2.1.jar > constituent[19]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-file-1.0-beta-2.jar > constituent[20]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-http-lightweight-1.0-beta-2.jar > constituent[21]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-http-shared-1.0-beta-2.jar > constituent[22]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-provider-api-1.0-beta-2.jar > constituent[23]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-1.0-beta-2.jar > constituent[24]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-common-1.0-beta-2.jar > constituent[25]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-external-1.0-beta-2.jar > --- > java.lang.NullPointerException > at > org.apache.maven.artifact.repository.DefaultArtifactRepository.pathOfRemoteRepositoryMetadata(DefaultArtifactRepository.java:123) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:390) > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolveAlways(De
[jira] Commented: (MNG-3623) [regression] it0081 and it0065 fail since the xbean migration
[ http://jira.codehaus.org/browse/MNG-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140636#action_140636 ] Jason van Zyl commented on MNG-3623: it0065 only refers to mojos it creates it0081 doesn't use any test mojos and only uses fixed versions What test mojos are you referring to? > [regression] it0081 and it0065 fail since the xbean migration > - > > Key: MNG-3623 > URL: http://jira.codehaus.org/browse/MNG-3623 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter > Fix For: 2.1-alpha-1 > > > both contain errors similar to: > Caused by: org.apache.xbean.recipe.ConstructionException: Type class could > not be found: org.apache.maven.plugin.coreit.TestBasedirMojo > at org.apache.xbean.recipe.ObjectRecipe.getType(ObjectRecipe.java:351) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:262) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) > at > org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:122) > ... 28 more -- 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
[jira] Commented: (MNG-3609) xbean breaks embedding within netbeans by using java.beans.PropertyEditorManager.registerEditor
[ http://jira.codehaus.org/browse/MNG-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140637#action_140637 ] Jason van Zyl commented on MNG-3609: I've ping Dain and David to look at the patch, and if they don't mind I'll patch XBR and update Plexus/Maven. > xbean breaks embedding within netbeans by using > java.beans.PropertyEditorManager.registerEditor > --- > > Key: MNG-3609 > URL: http://jira.codehaus.org/browse/MNG-3609 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1 > Environment: netbeans 6.1, mevenide 3.1.2+ >Reporter: Milos Kleint >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > Attachments: xbean.patch > > > The xbean binary shipping with maven in 2.1 is registering PropertyEditors > via java.beans.PropertyEditorManager.registerEditor() > that's wracking havoc in the IDE's own code that relies on it's own property > editors with customizer ui to be present. > http://www.netbeans.org/issues/show_bug.cgi?id=135868 is the obvious error > everyone noticed, there's more subtle ones as well, like being unable to edit > properties, or broken form GUI editor that's not processing real numbers > correctly. > I've hotfixed the issue by commenting out the property editor registration in > xbean (attached) -- 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
[jira] Commented: (MNG-3609) xbean breaks embedding within netbeans by using java.beans.PropertyEditorManager.registerEditor
[ http://jira.codehaus.org/browse/MNG-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140638#action_140638 ] Milos Kleint commented on MNG-3609: --- the patch is just a hotfix I've done. It effectively disables the troubling behaviour. I'm not sure if there are any sideeffects in terms of functioning of xbean. I haven't noticed any when running maven though.. > xbean breaks embedding within netbeans by using > java.beans.PropertyEditorManager.registerEditor > --- > > Key: MNG-3609 > URL: http://jira.codehaus.org/browse/MNG-3609 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1 > Environment: netbeans 6.1, mevenide 3.1.2+ >Reporter: Milos Kleint >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > Attachments: xbean.patch > > > The xbean binary shipping with maven in 2.1 is registering PropertyEditors > via java.beans.PropertyEditorManager.registerEditor() > that's wracking havoc in the IDE's own code that relies on it's own property > editors with customizer ui to be present. > http://www.netbeans.org/issues/show_bug.cgi?id=135868 is the obvious error > everyone noticed, there's more subtle ones as well, like being unable to edit > properties, or broken form GUI editor that's not processing real numbers > correctly. > I've hotfixed the issue by commenting out the property editor registration in > xbean (attached) -- 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
[jira] Commented: (MNG-3579) REGRESSION: Using ${project.version} in version tag of extension invalidates pom
[
http://jira.codehaus.org/browse/MNG-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140640#action_140640
]
Jason van Zyl commented on MNG-3579:
Provide an example so that we can validate, or better yet a sample project.
> REGRESSION: Using ${project.version} in version tag of extension invalidates
> pom
>
>
> Key: MNG-3579
> URL: http://jira.codehaus.org/browse/MNG-3579
> Project: Maven 2
> Issue Type: Bug
> Components: Bootstrap & Build
>Affects Versions: 2.1
> Environment: XP, JDK 1.6.0_06, Maven Embedder 2.1 Early Access,
> Mevenide 3.1.1, NB 6.1
>Reporter: Daniel Mutch
> Fix For: 2.1-alpha-1
>
>
> It isn't possible to user ${project.version} in version tag of an extension.
> This is a regression as it works fine in 2.0.7
--
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
[jira] Commented: (MNG-3623) [regression] it0081 and it0065 fail since the xbean migration
[ http://jira.codehaus.org/browse/MNG-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140641#action_140641 ] Brett Porter commented on MNG-3623: --- Sorry, since the names of the mojos are the same as the shared ones I thought that was what they were using. it0081 uses one it builds too, giving this error: Root cause: Type class could not be found: org.apache.maven.plugin.coreit.CoreItMojo org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'null', implementation: 'org.apache.maven.plugin.coreit.CoreItMojo', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:138) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:92) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:135) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:45) at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:147) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:492) So they have in common that they use plugins they build. I know the plugin manager used to have some reloading logic to accommodate that - though if that weren't working you'd expect more consistent failures on these. Beyond that, I'm not sure of the cause yet. > [regression] it0081 and it0065 fail since the xbean migration > - > > Key: MNG-3623 > URL: http://jira.codehaus.org/browse/MNG-3623 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter > Fix For: 2.1-alpha-1 > > > both contain errors similar to: > Caused by: org.apache.xbean.recipe.ConstructionException: Type class could > not be found: org.apache.maven.plugin.coreit.TestBasedirMojo > at org.apache.xbean.recipe.ObjectRecipe.getType(ObjectRecipe.java:351) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:262) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) > at > org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:122) > ... 28 more -- 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
[jira] Commented: (MNG-3623) [regression] it0081 and it0065 fail since the xbean migration
[ http://jira.codehaus.org/browse/MNG-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140643#action_140643 ] Jason van Zyl commented on MNG-3623: Reference for the last Hudson build: https://ci.sonatype.org/view/Maven%202.1x/job/Maven-2.1.x-ITs/159/console > [regression] it0081 and it0065 fail since the xbean migration > - > > Key: MNG-3623 > URL: http://jira.codehaus.org/browse/MNG-3623 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter > Fix For: 2.1-alpha-1 > > > both contain errors similar to: > Caused by: org.apache.xbean.recipe.ConstructionException: Type class could > not be found: org.apache.maven.plugin.coreit.TestBasedirMojo > at org.apache.xbean.recipe.ObjectRecipe.getType(ObjectRecipe.java:351) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:262) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) > at > org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:122) > ... 28 more -- 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
[jira] Commented: (MNG-3623) [regression] it0081 and it0065 fail since the xbean migration
[ http://jira.codehaus.org/browse/MNG-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140642#action_140642 ] Jason van Zyl commented on MNG-3623: No errors in Hudson, or on my machine. So not sure what's up with your machine. I consider these working. > [regression] it0081 and it0065 fail since the xbean migration > - > > Key: MNG-3623 > URL: http://jira.codehaus.org/browse/MNG-3623 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter > Fix For: 2.1-alpha-1 > > > both contain errors similar to: > Caused by: org.apache.xbean.recipe.ConstructionException: Type class could > not be found: org.apache.maven.plugin.coreit.TestBasedirMojo > at org.apache.xbean.recipe.ObjectRecipe.getType(ObjectRecipe.java:351) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:262) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) > at > org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:122) > ... 28 more -- 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
[jira] Commented: (MNG-3623) [regression] it0081 and it0065 fail since the xbean migration
[ http://jira.codehaus.org/browse/MNG-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140645#action_140645 ] Brett Porter commented on MNG-3623: --- Like I said, intermittent on my mac, fine on windows, pretty consistently failing on vmbuild (which is what made me think it isn't "just me"). I'm happy to push these out for later review until it can be reproduced with some consistency. I also get your two hudson errors locally (and two more), but not on windows or vmbuild. > [regression] it0081 and it0065 fail since the xbean migration > - > > Key: MNG-3623 > URL: http://jira.codehaus.org/browse/MNG-3623 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter > Fix For: 2.1-alpha-1 > > > both contain errors similar to: > Caused by: org.apache.xbean.recipe.ConstructionException: Type class could > not be found: org.apache.maven.plugin.coreit.TestBasedirMojo > at org.apache.xbean.recipe.ObjectRecipe.getType(ObjectRecipe.java:351) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:262) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) > at > org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:122) > ... 28 more -- 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
[jira] Commented: (MNG-3623) [regression] it0081 and it0065 fail since the xbean migration
[ http://jira.codehaus.org/browse/MNG-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140647#action_140647 ] Jason van Zyl commented on MNG-3623: Is vmbuild Solaris? I'll get an instance of Hudson setup on vmbuild so we can build up our consistency across platforms until the big iron shows up at Contegix. > [regression] it0081 and it0065 fail since the xbean migration > - > > Key: MNG-3623 > URL: http://jira.codehaus.org/browse/MNG-3623 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter > Fix For: 2.1-alpha-1 > > > both contain errors similar to: > Caused by: org.apache.xbean.recipe.ConstructionException: Type class could > not be found: org.apache.maven.plugin.coreit.TestBasedirMojo > at org.apache.xbean.recipe.ObjectRecipe.getType(ObjectRecipe.java:351) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:262) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) > at > org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:122) > ... 28 more -- 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
[jira] Updated: (MNG-3623) [regression] it0081 and it0065 fail since the xbean migration
[ http://jira.codehaus.org/browse/MNG-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3623: --- Affects Version/s: (was: 2.1-alpha-1) 2.1-alpha-2 When we can consistency run the same system across OS X, Solaris, Linux and Windows we'll leave this open. > [regression] it0081 and it0065 fail since the xbean migration > - > > Key: MNG-3623 > URL: http://jira.codehaus.org/browse/MNG-3623 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1-alpha-2 >Reporter: Brett Porter > Fix For: 2.1-alpha-1 > > > both contain errors similar to: > Caused by: org.apache.xbean.recipe.ConstructionException: Type class could > not be found: org.apache.maven.plugin.coreit.TestBasedirMojo > at org.apache.xbean.recipe.ObjectRecipe.getType(ObjectRecipe.java:351) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:262) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) > at > org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:122) > ... 28 more -- 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
[jira] Commented: (MNG-3623) [regression] it0081 and it0065 fail since the xbean migration
[ http://jira.codehaus.org/browse/MNG-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140649#action_140649 ] Jason van Zyl commented on MNG-3623: I've also asked Contegix to grab a MAC Mini and modify it so that it can sit in the rack and run Hudson. > [regression] it0081 and it0065 fail since the xbean migration > - > > Key: MNG-3623 > URL: http://jira.codehaus.org/browse/MNG-3623 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1-alpha-2 >Reporter: Brett Porter > Fix For: 2.1-alpha-1 > > > both contain errors similar to: > Caused by: org.apache.xbean.recipe.ConstructionException: Type class could > not be found: org.apache.maven.plugin.coreit.TestBasedirMojo > at org.apache.xbean.recipe.ObjectRecipe.getType(ObjectRecipe.java:351) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:262) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) > at > org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:122) > ... 28 more -- 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
[jira] Closed: (MNG-3503) Shade MX* classes from plexus-utils
[
http://jira.codehaus.org/browse/MNG-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MNG-3503.
---
Assignee: John Casey
Resolution: Fixed
Fix Version/s: 2.1-alpha-1
> Shade MX* classes from plexus-utils
> ---
>
> Key: MNG-3503
> URL: http://jira.codehaus.org/browse/MNG-3503
> Project: Maven 2
> Issue Type: Improvement
>Affects Versions: 2.0.8
>Reporter: Benjamin Bentmann
>Assignee: John Casey
>Priority: Minor
> Fix For: 2.0.10, 2.1-alpha-1
>
> Attachments: shade-mx-classes.patch
>
>
> The Maven uber JAR currently ships with unshaded {{MXParser}} and
> {{MXSerializer}}, preventing plugins from using their recent implementations
> from plexus-utils. My initial question on the [dev
> list|http://www.nabble.com/Shade-MX*-classes-from-plexus-utils--tc16080800s177.html]
> showed now immediate objections and the core ITs also smile so here we go
> with the proposed patch.
--
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
[jira] Created: (MWAR-161) Overridden artifact finalName ist ignored by the war plugin.
Overridden artifact finalName ist ignored by the war plugin.
Key: MWAR-161
URL: http://jira.codehaus.org/browse/MWAR-161
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Environment: Maven 2.0.9, JDK 6, WinXP SP2
Reporter: Michael Osipov
Attachments: example.png
I have a multimodule project.
groupId: net.fckeditor
Parent ArtifactId: fckeditor-java
1. module ArtifactId: java-core; finalName "fckeditor-${artifactId}-${version}"
though => e.g. fckeditor-java-core-2.4-SNAPSHOT
2. module ArtifactId: java-demo; finalName "fckeditor-${artifactId}-${version}"
though
module one is a jar artifact, module 2 a war artifact which has a dependency on
module 2.
the final WAR file contains all dependencies included the java-core but the jar
name is not fckeditor-java-core-2.4-SNAPSHOT.jar but java-core-2.4-SNAPSHOT.jar
An example picture is attached and the project can be checked out at our
[trac|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk] and the
[SVN|http://svn.fckeditor.net/FCKeditor.Java/trunk/] directly.
--
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
[jira] Commented: (MWAR-161) Overridden artifact finalName ist ignored by the war plugin.
[
http://jira.codehaus.org/browse/MWAR-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140660#action_140660
]
Michael Osipov commented on MWAR-161:
-
A correction.
module one is a jar artifact, module 2 a war artifact. The war depends on the
jar.
> Overridden artifact finalName ist ignored by the war plugin.
>
>
> Key: MWAR-161
> URL: http://jira.codehaus.org/browse/MWAR-161
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.1-alpha-1
> Environment: Maven 2.0.9, JDK 6, WinXP SP2
>Reporter: Michael Osipov
> Attachments: example.png
>
>
> I have a multimodule project.
> groupId: net.fckeditor
> Parent ArtifactId: fckeditor-java
> 1. module ArtifactId: java-core; finalName
> "fckeditor-${artifactId}-${version}" though => e.g.
> fckeditor-java-core-2.4-SNAPSHOT
> 2. module ArtifactId: java-demo; finalName
> "fckeditor-${artifactId}-${version}" though
> module one is a jar artifact, module 2 a war artifact which has a dependency
> on module 2.
> the final WAR file contains all dependencies included the java-core but the
> jar name is not fckeditor-java-core-2.4-SNAPSHOT.jar but
> java-core-2.4-SNAPSHOT.jar
> An example picture is attached and the project can be checked out at our
> [trac|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk] and the
> [SVN|http://svn.fckeditor.net/FCKeditor.Java/trunk/] directly.
--
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
[jira] Issue Comment Edited: (MWAR-161) Overridden artifact finalName ist ignored by the war plugin.
[
http://jira.codehaus.org/browse/MWAR-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140660#action_140660
]
sgfan edited comment on MWAR-161 at 7/4/08 1:42 PM:
-
Correction:
module one is a jar artifact, module 2 a war artifact. The war depends on the
jar.
was (Author: sgfan):
A correction.
module one is a jar artifact, module 2 a war artifact. The war depends on the
jar.
> Overridden artifact finalName ist ignored by the war plugin.
>
>
> Key: MWAR-161
> URL: http://jira.codehaus.org/browse/MWAR-161
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.1-alpha-1
> Environment: Maven 2.0.9, JDK 6, WinXP SP2
>Reporter: Michael Osipov
> Attachments: example.png
>
>
> I have a multimodule project.
> groupId: net.fckeditor
> Parent ArtifactId: fckeditor-java
> 1. module ArtifactId: java-core; finalName
> "fckeditor-${artifactId}-${version}" though => e.g.
> fckeditor-java-core-2.4-SNAPSHOT
> 2. module ArtifactId: java-demo; finalName
> "fckeditor-${artifactId}-${version}" though
> module one is a jar artifact, module 2 a war artifact which has a dependency
> on module 2.
> the final WAR file contains all dependencies included the java-core but the
> jar name is not fckeditor-java-core-2.4-SNAPSHOT.jar but
> java-core-2.4-SNAPSHOT.jar
> An example picture is attached and the project can be checked out at our
> [trac|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk] and the
> [SVN|http://svn.fckeditor.net/FCKeditor.Java/trunk/] directly.
--
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
[jira] Created: (MASSEMBLY-338) Overridden artifact finalName is ignored by the assembly plugin.
Overridden artifact finalName is ignored by the assembly plugin.
Key: MASSEMBLY-338
URL: http://jira.codehaus.org/browse/MASSEMBLY-338
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-1
Environment: Maven 2.0.9, JDK 6, WinXP SP2
Reporter: Michael Osipov
Attachments: assemblyMapping.png
I have a multimodule project.
groupId: net.fckeditor
Parent ArtifactId: fckeditor-java
1. module ArtifactId: java-core; finalName "fckeditor-${artifactId}-${version}"
though => e.g. fckeditor-java-core-2.4-SNAPSHOT
2. module ArtifactId: java-demo; finalName "fckeditor-${artifactId}-${version}"
though
I did create a bin assembly. The assembly contains the jars but their names do
not correspond to the overridden finalNames.
An example picture is attached and the project can be checked out at our
[trac|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk] and the
[SVN|http://svn.fckeditor.net/FCKeditor.Java/trunk/] directly.
Checkout the
[bin.xml|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk/src/main/assembly/bin.xml]
and comment out the first outputFileNameMapping and run "mvn clean site
package assembly:assembly".
You should be able to reproduce the problem.
I did find a workaround for the problem by defining the outputFileNameMapping
as same as in the modules poms. This works just because all modules have the
same finalName remapping.
--
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
[jira] Commented: (MNG-1323) Plugin extensions (dependencies) not resolved in reactor build
[ http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140717#action_140717 ] John Casey commented on MNG-1323: - This, along with different plugin versions used in different POMs within a single multimodule build, is something I addressed for trunk (2.1). To make it work, I had to setup a realm manager to track plugins using a key that's based on groupId:artifactId:version, PLUS a hash of the dependency-id's it uses. This allows naming of the plugin realm accordingly, and helps to retrieve the correct realm for use when a plugin is executed. The problem is, it requires use of the new lookupRealm(..) functionality of later plexus-container-default releases (> ~1.0-alpha-16, IIRC), and upgrading Maven 2.0.x to a compatible plexus version may well break other things. It may be that this issue cannot be resolved in a satisfactory manner until 2.1 is released. The good news is, it should work in the first alpha of 2.1. > Plugin extensions (dependencies) not resolved in reactor build > -- > > Key: MNG-1323 > URL: http://jira.codehaus.org/browse/MNG-1323 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0 >Reporter: Kenney Westerhof > Fix For: 2.0.10 > > Attachments: MNG-1323-components-2.0.x.diff, > MNG-1323-core-integration-testing-2.diff, > MNG-1323-core-integration-testing.diff, > MNG-1323-core-integration-tests-3.diff, MNG-1323-core-integration-tests.diff, > MNG1323-maven-core-2.1.diff, two-antruns.zip > > > I've added a dependency on an Ant Task in > project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/ > and run that anttask using the antrun plugin. > When run from the project dir itself it runs fine. > When running from the root of the project tree (reactor build, project one > level below root), > antrun bails out because the taskdef can't be found (not on classpath). > It looks like the dependency isn't resolved, or not added to the plugins' > classrealm. -- 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
[jira] Updated: (MNG-1323) Plugin extensions (dependencies) not resolved in reactor build
[ http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-1323: Fix Version/s: (was: 2.0.10) 2.1-alpha-1 I'm moving this off to 2.1-alpha-1, since that's the closest release we can reasonably expect a solution at present. Fixing this in 2.0.x will require some very large changes that will certainly have rippling effects on other features. > Plugin extensions (dependencies) not resolved in reactor build > -- > > Key: MNG-1323 > URL: http://jira.codehaus.org/browse/MNG-1323 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0 >Reporter: Kenney Westerhof > Fix For: 2.1-alpha-1 > > Attachments: MNG-1323-components-2.0.x.diff, > MNG-1323-core-integration-testing-2.diff, > MNG-1323-core-integration-testing.diff, > MNG-1323-core-integration-tests-3.diff, MNG-1323-core-integration-tests.diff, > MNG1323-maven-core-2.1.diff, two-antruns.zip > > > I've added a dependency on an Ant Task in > project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/ > and run that anttask using the antrun plugin. > When run from the project dir itself it runs fine. > When running from the root of the project tree (reactor build, project one > level below root), > antrun bails out because the taskdef can't be found (not on classpath). > It looks like the dependency isn't resolved, or not added to the plugins' > classrealm. -- 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
[jira] Created: (MPIR-108) Add validation of SCM urls
Add validation of SCM urls -- Key: MPIR-108 URL: http://jira.codehaus.org/browse/MPIR-108 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Components: scm Affects Versions: 2.1 Reporter: Vincent Siveton MPIR-63 allows to specify a given SCM connection. To prevent errors on the URL format like describe in MPIR-78 we need to add a validation mechanism for SCM connection urls. -- 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
[jira] Created: (MASSEMBLY-339) Overridden artifact finalName with classifier is ignored by the assembly plugin.
Overridden artifact finalName with classifier is ignored by the assembly plugin.
Key: MASSEMBLY-339
URL: http://jira.codehaus.org/browse/MASSEMBLY-339
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-1
Environment: Maven 2.0.9, JDK 6, WinXP SP2
Reporter: Michael Osipov
Attachments: assemblyClassifierMapping.png
I have a multimodule project.
groupId: net.fckeditor
Parent ArtifactId: fckeditor-java
1. module ArtifactId: java-core; finalName "fckeditor-${artifactId}-${version}"
though => e.g. fckeditor-java-core-2.4-SNAPSHOT
2. module ArtifactId: java-demo; finalName "fckeditor-${artifactId}-${version}"
though
I did create a bin assembly. The assembly contains the javadoc jars but their
names do not correspond to the overridden finalNames.
The javadoc:jar genereation is bound to the package phase.
An example picture is attached and the project can be checked out at our
[trac|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk] and the
[SVN|http://svn.fckeditor.net/FCKeditor.Java/trunk/] directly.
Checkout the
[bin.xml|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk/src/main/assembly/bin.xml]
and comment out the second outputFileNameMapping and run "mvn clean site
package assembly:assembly".
You should be able to reproduce the problem.
I did find a workaround for the problem by defining the outputFileNameMapping
as same as in the modules poms. This works just because all modules have the
same finalName remapping.
--
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
[jira] Closed: (MPIR-108) Add validation of SCM urls
[ http://jira.codehaus.org/browse/MPIR-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-108. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.1 fixed in r674123 > Add validation of SCM urls > -- > > Key: MPIR-108 > URL: http://jira.codehaus.org/browse/MPIR-108 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: scm >Affects Versions: 2.1 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.1 > > > MPIR-63 allows to specify a given SCM connection. To prevent errors on the > URL format like describe in MPIR-78 we need to add a validation mechanism for > SCM connection urls. -- 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
[jira] Created: (MAVENUPLOAD-2134) Request to sync derquinsej
Request to sync derquinsej -- Key: MAVENUPLOAD-2134 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2134 Project: Maven Upload Requests Issue Type: Wish Reporter: Andres Rodriguez "net.sf.derquinsej","[EMAIL PROTECTED]:/home/groups/d/de/derquinsej/htdocs/maven2","rsync_ssh","Andres Rodriguez","[EMAIL PROTECTED]",, Sourceforge project Thank you very much. -- 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
[jira] Closed: (MPIR-78) Unable to exclude scm anonymous access info
[
http://jira.codehaus.org/browse/MPIR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPIR-78.
---
Assignee: Vincent Siveton
Resolution: Not A Bug
Yes you could do it if you leave empty scm.connection tag ie:
{noformat}
...
scm:svn:https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-project-info-reports-plugin/
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-project-info-reports-plugin/
...
{noformat}
BUT it doesn't work using an empty tag due to Plexus
constraints.
I updated the doc in r674128
> Unable to exclude scm anonymous access info
> ---
>
> Key: MPIR-78
> URL: http://jira.codehaus.org/browse/MPIR-78
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Components: scm
>Affects Versions: 2.0.1
> Environment: WinXP SP2 fully patched, jdk 1.6.0_03, Maven 2.0.8,
> Continuum 1.1
>Reporter: creyle
>Assignee: Vincent Siveton
>Priority: Minor
>
> Currently there's no way to exclude the information, about anonymous access
> to the source repository, from the scm report.
> In the doc [1] it says, the anonymousConnection defaults to
> project.scm.connection in POM, but explicitly setting a blank
> configuration element just has no effect, as discussed
> in the maven user list [2], while setting it to a invalid value e.g.
> foo still has no effect with
> 2.0.1, but will cause "horrible" problems with 2.1-SNAPSHOT.
> [1]
> http://maven.apache.org/plugins/maven-project-info-reports-plugin/scm-mojo.html#anonymousConnection
> [2] http://www.nabble.com/forum/ViewPost.jtp?post=14413537&framed=y&skin=177
--
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
[jira] Closed: (MPIR-97) Provide a way of hiding developer/contributer email addresses
[ http://jira.codehaus.org/browse/MPIR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-97. --- Assignee: Vincent Siveton Resolution: Won't Fix I don't think it is a good use case so I closed it as wont fix. But I added a faq entry in r674129 about your point. > Provide a way of hiding developer/contributer email addresses > - > > Key: MPIR-97 > URL: http://jira.codehaus.org/browse/MPIR-97 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: New Feature > Components: project-team >Affects Versions: 2.0.1 >Reporter: Kristian Andersen >Assignee: Vincent Siveton >Priority: Minor > Attachments: TeamListReport.java.patch > > > Even in these GMail times it would be nice to be able to hide email addresses > using services such as reCAPTCHA Mailhide [http://mailhide.recaptcha.net/] > One way of achieving this is to tell the team-list report generator to treat > the contents of as HTML, making it possible to include links etc. > Example: > > ... > > ... > > The attached patch does this using a configuration parameter. -- 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
[jira] Commented: (MNG-3422) [regression] deploy:deploy-file does not work
[ http://jira.codehaus.org/browse/MNG-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140731#action_140731 ] Jason van Zyl commented on MNG-3422: Just an update that I have this fixed in Plexus, the wrong realm was being grabbed and so the right place for the components wasn't being used. I'm going to test m2e and then I'll check it all in. > [regression] deploy:deploy-file does not work > - > > Key: MNG-3422 > URL: http://jira.codehaus.org/browse/MNG-3422 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > mvn deploy:deploy-file -Dfile=test.sh -DrepositoryId=testing > -DartifactId=artifactId -DgroupId=groupId -Dversion=1.0 -Dpackaging=jar > -Durl=http://vesuvius.devzuz.com/private/devzuz/releases > [INFO] Searching repository for plugin with prefix: 'deploy'. > [INFO] Attempting to resolve a version for plugin: > org.apache.maven.plugins:maven-deploy-plugin using meta-version: LATEST > [INFO] Using version: 2.3 of plugin: > org.apache.maven.plugins:maven-deploy-plugin > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Maven Default Project > [INFO] > [INFO] Id: org.apache.maven:super-pom:jar:2.1 > [INFO] task-segment: [deploy:deploy-file] (aggregator-style) > [INFO] > > [INFO] [deploy:deploy-file] > [INFO] artifact groupId:artifactId: checking for updates from testing > --- > constituent[0]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/aspectjrt-1.5.3.jar > constituent[1]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/backport-util-concurrent-3.0.jar > constituent[2]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/commons-cli-1.0.jar > constituent[3]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/doxia-sink-api-1.0-alpha-9.jar > constituent[4]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/jsch-0.1.27.jar > constituent[5]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/jtidy-4aug2000r7-dev.jar > constituent[6]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-artifact-3.0-SNAPSHOT.jar > constituent[7]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-core-2.1-SNAPSHOT.jar > constituent[8]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-embedder-2.1-SNAPSHOT.jar > constituent[9]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-lifecycle-2.1-SNAPSHOT.jar > constituent[10]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-model-2.1-SNAPSHOT.jar > constituent[11]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-plugin-api-2.1-SNAPSHOT.jar > constituent[12]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-profile-2.1-SNAPSHOT.jar > constituent[13]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-project-2.1-SNAPSHOT.jar > constituent[14]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/maven-reporting-api-2.1-SNAPSHOT.jar > constituent[15]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-container-default-1.0-alpha-44.jar > constituent[16]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-interactivity-api-1.0-alpha-6.jar > constituent[17]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/plexus-utils-1.5.1.jar > constituent[18]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/retrotranslator-runtime-1.2.1.jar > constituent[19]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-file-1.0-beta-2.jar > constituent[20]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-http-lightweight-1.0-beta-2.jar > constituent[21]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-http-shared-1.0-beta-2.jar > constituent[22]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-provider-api-1.0-beta-2.jar > constituent[23]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-1.0-beta-2.jar > constituent[24]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-common-1.0-beta-2.jar > constituent[25]: > file:/Applications/maven/apache-maven-2.1-SNAPSHOT/lib/wagon-ssh-external-1.0-beta-2.jar > --- > java.lang.NullPointerException > at > org.apache.maven.artifact.repository.DefaultArtifactRepository.pathOfRemoteRepositoryMetadata(DefaultArtifactRepository.java:123) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:390) > at > org.apache.maven
[jira] Closed: (MPIR-102) Locale should be taken from maven-site-plugin
[ http://jira.codehaus.org/browse/MPIR-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-102. Assignee: Vincent Siveton Resolution: Duplicate MSITE-243 provides the Czeck translation in 2.1 and I replaced some characters by unicode in r674135 > Locale should be taken from maven-site-plugin > - > > Key: MPIR-102 > URL: http://jira.codehaus.org/browse/MPIR-102 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Reporter: Petr Ferschmann >Assignee: Vincent Siveton > > In my pom.xml I have this configuration for site plugin: > > org.apache.maven.plugins > maven-site-plugin > > cs > > > But project-info-reports are still in english. It would be great if the > locale is taken from site plugin. -- 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
[jira] Commented: (MPIR-85) Refactoring of dependency and dependency management report
[ http://jira.codehaus.org/browse/MPIR-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140735#action_140735 ] Vincent Siveton commented on MPIR-85: - Hi Nick, I am working to prepare the release of the MPIR. Could you send us a one-in-one patch? Tx > Refactoring of dependency and dependency management report > -- > > Key: MPIR-85 > URL: http://jira.codehaus.org/browse/MPIR-85 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies, dependency-management >Affects Versions: 2.1 >Reporter: Nick Stolwijk > Attachments: comparators.patch, refactor.patch, refactor.patch > > > I've tried to refactor the code from MPIR-83 a bit, because it used a lot of > copied code. > Important improvements: > - Created a AbstractProjectInfoRenderer and AbstractDependencyRenderer. > If this patch is accepted, I want to write all the renderers out of the > inforeports in separate classes, with more code sharing. This is a start of > that. > - I changed the unit tests, because the expected and actual were reversed. > This is the case in many of the info report unit tests. > Please tell me what you think of it. I know it is only a start. -- 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
[jira] Commented: (MNG-3623) [regression] it0081 and it0065 fail since the xbean migration
[ http://jira.codehaus.org/browse/MNG-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140744#action_140744 ] Brett Porter commented on MNG-3623: --- vmbuild is ubuntu linux. > [regression] it0081 and it0065 fail since the xbean migration > - > > Key: MNG-3623 > URL: http://jira.codehaus.org/browse/MNG-3623 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1-alpha-2 >Reporter: Brett Porter > Fix For: 2.1-alpha-1 > > > both contain errors similar to: > Caused by: org.apache.xbean.recipe.ConstructionException: Type class could > not be found: org.apache.maven.plugin.coreit.TestBasedirMojo > at org.apache.xbean.recipe.ObjectRecipe.getType(ObjectRecipe.java:351) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:262) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) > at > org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:122) > ... 28 more -- 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
[jira] Commented: (MSITE-294) Can't escape ${project.version} as plain text inside apt +---- section, on *.apt.vm files
[
http://jira.codehaus.org/browse/MSITE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140752#action_140752
]
Lukas Theussl commented on MSITE-294:
-
The following works:
{source}
+
This project version is ${project.version} and comes from the
\${project.version} property.
+
{source}
I don't think that this is a bug even if it's not very intuitive. If you use
slashes inside apt verbatim text they will render as-is (that's what verbatim
text is supposed to do), so all you need is prevent velocity from filtering the
property, which you do by escaping the $.
> Can't escape ${project.version} as plain text inside apt + section, on
> *.apt.vm files
> -
>
> Key: MSITE-294
> URL: http://jira.codehaus.org/browse/MSITE-294
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-6
> Environment: *.apt.vm files, and +- escaped section.
>Reporter: Andrew Hughes
>Priority: Critical
>
> You can reproduce this the following way.
> ./src/site/index.apt.vm (start)
> --
> This will appear without the backslashes
> {noformat}$\{project.version\}{noformat} and that's excellent. But you can't
> get this output in the escaped apt text section below.
> {noformat}
> +---
> However this apt escaped section still shows the backslashes inside this
> section $\{project.version\} and there is no known way the text can be shown
> as above.
> To make matters worse, when you put this in without the backslashes, you get
> the properties value (like a filter). See: ${project.version} not the desired
> string as above
> +---
> {noformat}
> -
> ./src/site/index.apt.vm (start)
--
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
[jira] Issue Comment Edited: (MSITE-294) Can't escape ${project.version} as plain text inside apt +---- section, on *.apt.vm files
[
http://jira.codehaus.org/browse/MSITE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140752#action_140752
]
lukas edited comment on MSITE-294 at 7/5/08 12:52 AM:
--
The following works:
{noformat}
+
This project version is ${project.version} and comes from the
\${project.version} property.
+
{noformat}
I don't think that this is a bug even if it's not very intuitive. If you use
slashes inside apt verbatim text they will render as-is (that's what verbatim
text is supposed to do), so all you need is prevent velocity from filtering the
property, which you do by escaping the $.
was (Author: lukas):
The following works:
{source}
+
This project version is ${project.version} and comes from the
\${project.version} property.
+
{source}
I don't think that this is a bug even if it's not very intuitive. If you use
slashes inside apt verbatim text they will render as-is (that's what verbatim
text is supposed to do), so all you need is prevent velocity from filtering the
property, which you do by escaping the $.
> Can't escape ${project.version} as plain text inside apt + section, on
> *.apt.vm files
> -
>
> Key: MSITE-294
> URL: http://jira.codehaus.org/browse/MSITE-294
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-6
> Environment: *.apt.vm files, and +- escaped section.
>Reporter: Andrew Hughes
>Priority: Critical
>
> You can reproduce this the following way.
> ./src/site/index.apt.vm (start)
> --
> This will appear without the backslashes
> {noformat}$\{project.version\}{noformat} and that's excellent. But you can't
> get this output in the escaped apt text section below.
> {noformat}
> +---
> However this apt escaped section still shows the backslashes inside this
> section $\{project.version\} and there is no known way the text can be shown
> as above.
> To make matters worse, when you put this in without the backslashes, you get
> the properties value (like a filter). See: ${project.version} not the desired
> string as above
> +---
> {noformat}
> -
> ./src/site/index.apt.vm (start)
--
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
