[jira] Updated: (MNG-3957) For artifact {stax:stax-api:null:jar}: The version cannot be empty.
[
http://jira.codehaus.org/browse/MNG-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3957:
---
Attachment: pom.xml
Running "mvn compile" on the attached POM using Maven 3.x worked for me. Can
you provide a minimal test project or at least your debug logs?
> For artifact {stax:stax-api:null:jar}: The version cannot be empty.
>
>
> Key: MNG-3957
> URL: http://jira.codehaus.org/browse/MNG-3957
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 3.0-alpha-1
>Reporter: Jorg Heymans
> Attachments: pom.xml
>
>
> A module in my build includes a dep to spring-ws:
> {code}
>
> org.springframework.ws
> spring-ws-core
> 1.5.5
>
>
> org.springframework
> spring-context
>
>
> org.springframework
> spring-aop
>
>
> org.springframework
> spring-web
>
>
> org.springframework
> spring-webmvc
>
>
> org.springframework
> spring-core
>
>
> org.springframework
> spring-beans
>
>
>
> {code}
> doing clean install i get this exception:
> {code}
> constituent[0]: file:/d:/tools/maven2/lib/bcpg-jdk15-140.jar
> constituent[1]: file:/d:/tools/maven2/lib/bcprov-jdk15-140.jar
> constituent[2]: file:/d:/tools/maven2/lib/commons-cli-1.0.jar
> constituent[3]: file:/d:/tools/maven2/lib/commons-logging-api-1.1.jar
> constituent[4]: file:/d:/tools/maven2/lib/doxia-sink-api-1.0-alpha-9.jar
> constituent[5]: file:/d:/tools/maven2/lib/google-collect-snapshot-20080530.jar
> constituent[6]: file:/d:/tools/maven2/lib/jetty-6.1.12.jar
> constituent[7]: file:/d:/tools/maven2/lib/jetty-client-6.1.12.jar
> constituent[8]: file:/d:/tools/maven2/lib/jetty-sslengine-6.1.12.jar
> constituent[9]: file:/d:/tools/maven2/lib/jetty-util-6.1.12.jar
> constituent[10]: file:/d:/tools/maven2/lib/jsch-0.1.38.jar
> constituent[11]: file:/d:/tools/maven2/lib/log4j-1.2.12.jar
> constituent[12]: file:/d:/tools/maven2/lib/maven-compat-3.0-alpha-1.jar
> constituent[13]: file:/d:/tools/maven2/lib/maven-core-3.0-alpha-1.jar
> constituent[14]: file:/d:/tools/maven2/lib/maven-distribution-3.0-alpha-1.jar
> constituent[15]: file:/d:/tools/maven2/lib/maven-embedder-3.0-alpha-1.jar
> constituent[16]: file:/d:/tools/maven2/lib/maven-lifecycle-3.0-alpha-1.jar
> constituent[17]: file:/d:/tools/maven2/lib/maven-mercury-3.0-alpha-1.jar
> constituent[18]: file:/d:/tools/maven2/lib/maven-model-3.0-alpha-1.jar
> constituent[19]: file:/d:/tools/maven2/lib/maven-plugin-api-3.0-alpha-1.jar
> constituent[20]: file:/d:/tools/maven2/lib/maven-project-3.0-alpha-1.jar
> constituent[21]:
> file:/d:/tools/maven2/lib/maven-project-builder-3.0-alpha-1.jar
> constituent[22]: file:/d:/tools/maven2/lib/maven-reporting-api-3.0-alpha-1.jar
> constituent[23]: file:/d:/tools/maven2/lib/maven-toolchain-3.0-alpha-1.jar
> constituent[24]: file:/d:/tools/maven2/lib/mercury-artifact-1.0.0-alpha-2.jar
> constituent[25]:
> file:/d:/tools/maven2/lib/mercury-crypto-api-1.0.0-alpha-2.jar
> constituent[26]:
> file:/d:/tools/maven2/lib/mercury-crypto-basic-1.0.0-alpha-2.jar
> constituent[27]: file:/d:/tools/maven2/lib/mercury-event-1.0.0-alpha-2.jar
> constituent[28]: file:/d:/tools/maven2/lib/mercury-external-1.0.0-alpha-2.jar
> constituent[29]: file:/d:/tools/maven2/lib/mercury-logging-1.0.0-alpha-2.jar
> constituent[30]: file:/d:/tools/maven2/lib/mercury-md-sat-1.0.0-alpha-2.jar
> constituent[31]: file:/d:/tools/maven2/lib/mercury-md-shared-1.0.0-alpha-2.jar
> constituent[32]: file:/d:/tools/maven2/lib/mercury-plexus-1.0.0-alpha-2.jar
> constituent[33]: file:/d:/tools/maven2/lib/mercury-repo-api-1.0.0-alpha-2.jar
> constituent[34]:
> file:/d:/tools/maven2/lib/mercury-repo-cache-fs-1.0.0-alpha-2.jar
> constituent[35]:
> file:/d:/tools/maven2/lib/mercury-repo-local-m2-1.0.0-alpha-2.jar
> constituent[36]:
> file:/d:/tools/maven2/lib/mercury-repo-remote-m2-1.0.0-alpha-2.jar
> constituent[37]:
> file:/d:/tools/maven2/lib/mercury-repo-virtual-1.0.0-alpha-2.jar
> constituent[38]:
> file:/d:/tools/maven2/lib/mercury-transport-api-1.0.0-alpha-2.jar
> constituent[39]:
> file:/d:/tools/maven2/lib/mercury-transport-http-1.0.0-alpha-2.jar
> constituent[40]: file:/d:/tools/maven2/lib/mercury-util-1.0.0-alpha-2.jar
> constituent[41]: file:/d:/tools/maven2/lib/model-builder-1.0.jar
> constituent[42]: file:/d:/tools/maven2/lib/nekohtml-1.9.6.2.jar
> constituent[43]: file:/d:/tools/maven2/lib/org.sat4j.core-2.0.4.jar
> constituent[44]: file:/d:/tools/maven2/lib/org.sat4j.pb-2.0.4.jar
> constituent[45]:
> file:/d:/tools/maven2/lib/plexus-component-annotations-1.0-beta-3.0.1.jar
> constituent[46]:
> file:/d
[jira] Commented: (MNG-3958) no NOTICE file
[ http://jira.codehaus.org/browse/MNG-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159937#action_159937 ] Brett Porter commented on MNG-3958: --- it is labeled NOTICE.txt, in the root of the binary distribution > no NOTICE file > -- > > Key: MNG-3958 > URL: http://jira.codehaus.org/browse/MNG-3958 > Project: Maven 2 > Issue Type: Bug > Components: General >Affects Versions: 2.0.9 >Reporter: Torsten Werner > > Most files ship with a license header: > "Licensed to the Apache Software Foundation (ASF) under one > or more contributor license agreements. See the NOTICE file > distributed with this work for additional information > regarding copyright ownership." > ... but there is no NOTICE file anywhere. -- 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-2323) Upload of FDS-API 1.04
Upload of FDS-API 1.04 -- Key: MAVENUPLOAD-2323 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2323 Project: Maven Upload Requests Issue Type: Wish Reporter: Edouard Hue Attachments: fdsapi-1.0.4-bundle.jar This is not a Maven project. The author (Steve Souza) isn't currently intersted in migrating fdsapi to Maven. This bundle was generated from the 1_04 release available at http://sourceforge.net/project/showfiles.php?group_id=87044&package_id=90549&release_id=317647 using the repository plugin. Thanks for uploading ! -- 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] Moved: (MNG-3959) Per-execution inherited flag ignored
[
http://jira.codehaus.org/browse/MNG-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann moved MANTRUN-103 to MNG-3959:
Affects Version/s: (was: 1.3)
Complexity: Intermediate
Key: MNG-3959 (was: MANTRUN-103)
Project: Maven 2 (was: Maven 2.x Antrun Plugin)
> Per-execution inherited flag ignored
>
>
> Key: MNG-3959
> URL: http://jira.codehaus.org/browse/MNG-3959
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Reporter: Dave Syer
>
> Per-execution inherited flag ignored. E.g.
> {code}
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> test
> initialize
> false
> ...
> {code}
> If you move the inherited element up to the plugin level it works, but then
> that applies to all executions, which isn't what is needed.
--
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: (MNG-3958) no NOTICE file
no NOTICE file -- Key: MNG-3958 URL: http://jira.codehaus.org/browse/MNG-3958 Project: Maven 2 Issue Type: Bug Components: General Affects Versions: 2.0.9 Reporter: Torsten Werner Most files ship with a license header: "Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership." ... but there is no NOTICE file anywhere. -- 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: (MCOMPILER-90) Classifier doesn't load the good jar when use with reactor
[
http://jira.codehaus.org/browse/MCOMPILER-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159958#action_159958
]
pkernevez commented on MCOMPILER-90:
I can't correct my issue.
You should understand at the end of my issue:
But when I run it in the reactor with the common project I have 2 times the
same jar
{code}
[DEBUG] Output directory: C:\dev\JMonitoring\framework\tests\target\classes
[DEBUG] Classpath:
[DEBUG] C:\dev\JMonitoring\framework\tests\target\classes
[DEBUG] C:\local-repo\junit\junit\4.4\junit-4.4.jar
[DEBUG] C:\dev\JMonitoring\framework\common\target\classes
[DEBUG] C:\dev\JMonitoring\framework\common\target\classes
{code}
And my build fail during the compilation.
> Classifier doesn't load the good jar when use with reactor
> --
>
> Key: MCOMPILER-90
> URL: http://jira.codehaus.org/browse/MCOMPILER-90
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 2.0.2
>Reporter: pkernevez
>
> I have a project named _common_ that is build with the goal _test-jar_ for
> making a jar with the test classe.
> It produce :
> * one jar with only the _main_ classes (common-2.0.jar)
> * one jat with only the tests classes (common-2.0-tests.jar)
> I have another project (named _tests_ that need the _test_ for building its
> main classes.
> So I had this dependencies to its pom as I need both _main_ and _test_
> classes:
> {code}
>
> com.octo.opensource.jmonitoring
> common
> 2.0-SNAPSHOT
> tests
>
>
> com.octo.opensource.jmonitoring
> common
> 2.0-SNAPSHOT
>
> {code}
> When I run only my _tests_ project, there is no problem, according to that
> the plugin use this classe path:
> {code}
> [DEBUG] Output directory:
> C:\dev\JMonitoring\framework\tests\target\test-classes
> [DEBUG] Classpath:
> [DEBUG] C:\dev\JMonitoring\framework\tests\target\test-classes
> [DEBUG] C:\dev\JMonitoring\framework\tests\target\classes
> [DEBUG] C:\local-repo\junit\junit\4.4\junit-4.4.jar
> [DEBUG]
> C:\local-repo\com\octo\opensource\jmonitoring\common\2.0-SNAPSHOT\common-2.0-SNAPSHOT-tests.jar
> [DEBUG]
> C:\local-repo\com\octo\opensource\jmonitoring\common\2.0-SNAPSHOT\common-2.0-SNAPSHOT.jar
> {code}
> But when I run it in the reactor with the _common_ project I have 2 times the
> same jar
> {code}
> [DEBUG] Output directory: C:\dev\JMonitoring\framework\tests\target\classes
> [DEBUG] Classpath:
> [DEBUG] C:\dev\JMonitoring\framework\tests\target\classes
> [DEBUG] C:\local-repo\junit\junit\4.4\junit-4.4.jar
> [DEBUG]
> C:\local-repo\com\octo\opensource\jmonitoring\common\2.0-SNAPSHOT\common-2.0-SNAPSHOT-tests.jar
> [DEBUG]
> C:\local-repo\com\octo\opensource\jmonitoring\common\2.0-SNAPSHOT\common-2.0-SNAPSHOT.jar
> {code}
> And my build fail during the compilation.
--
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: (MCOMPILER-90) Classifier doesn't load the good jar when use with reactor
Classifier doesn't load the good jar when use with reactor
--
Key: MCOMPILER-90
URL: http://jira.codehaus.org/browse/MCOMPILER-90
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Affects Versions: 2.0.2
Reporter: pkernevez
I have a project named _common_ that is build with the goal _test-jar_ for
making a jar with the test classe.
It produce :
* one jar with only the _main_ classes (common-2.0.jar)
* one jat with only the tests classes (common-2.0-tests.jar)
I have another project (named _tests_ that need the _test_ for building its
main classes.
So I had this dependencies to its pom as I need both _main_ and _test_ classes:
{code}
com.octo.opensource.jmonitoring
common
2.0-SNAPSHOT
tests
com.octo.opensource.jmonitoring
common
2.0-SNAPSHOT
{code}
When I run only my _tests_ project, there is no problem, according to that the
plugin use this classe path:
{code}
[DEBUG] Output directory: C:\dev\JMonitoring\framework\tests\target\test-classes
[DEBUG] Classpath:
[DEBUG] C:\dev\JMonitoring\framework\tests\target\test-classes
[DEBUG] C:\dev\JMonitoring\framework\tests\target\classes
[DEBUG] C:\local-repo\junit\junit\4.4\junit-4.4.jar
[DEBUG]
C:\local-repo\com\octo\opensource\jmonitoring\common\2.0-SNAPSHOT\common-2.0-SNAPSHOT-tests.jar
[DEBUG]
C:\local-repo\com\octo\opensource\jmonitoring\common\2.0-SNAPSHOT\common-2.0-SNAPSHOT.jar
{code}
But when I run it in the reactor with the _common_ project I have 2 times the
same jar
{code}
[DEBUG] Output directory: C:\dev\JMonitoring\framework\tests\target\classes
[DEBUG] Classpath:
[DEBUG] C:\dev\JMonitoring\framework\tests\target\classes
[DEBUG] C:\local-repo\junit\junit\4.4\junit-4.4.jar
[DEBUG]
C:\local-repo\com\octo\opensource\jmonitoring\common\2.0-SNAPSHOT\common-2.0-SNAPSHOT-tests.jar
[DEBUG]
C:\local-repo\com\octo\opensource\jmonitoring\common\2.0-SNAPSHOT\common-2.0-SNAPSHOT.jar
{code}
And my build fail during the compilation.
--
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-3959) Per-execution inherited flag ignored
[
http://jira.codehaus.org/browse/MNG-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3959:
---
Component/s: Inheritance and Interpolation
> Per-execution inherited flag ignored
>
>
> Key: MNG-3959
> URL: http://jira.codehaus.org/browse/MNG-3959
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Reporter: Dave Syer
>
> Per-execution inherited flag ignored. E.g.
> {code}
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> test
> initialize
> false
> ...
> {code}
> If you move the inherited element up to the plugin level it works, but then
> that applies to all executions, which isn't what is needed.
--
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: (MANTRUN-103) Per-execution inherited flag ignored
Per-execution inherited flag ignored
Key: MANTRUN-103
URL: http://jira.codehaus.org/browse/MANTRUN-103
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Affects Versions: 1.3
Reporter: Dave Syer
Per-execution inherited flag ignored. E.g.
{code}
org.apache.maven.plugins
maven-antrun-plugin
test
initialize
false
...
{code}
If you move the inherited element up to the plugin level it works, but then
that applies to all executions, which isn't what is needed.
--
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: (MNG-3957) For artifact {stax:stax-api:null:jar}: The version cannot be empty.
For artifact {stax:stax-api:null:jar}: The version cannot be empty.
Key: MNG-3957
URL: http://jira.codehaus.org/browse/MNG-3957
Project: Maven 2
Issue Type: Bug
Affects Versions: 3.0-alpha-1
Reporter: Jorg Heymans
A module in my build includes a dep to spring-ws:
{code}
org.springframework.ws
spring-ws-core
1.5.5
org.springframework
spring-context
org.springframework
spring-aop
org.springframework
spring-web
org.springframework
spring-webmvc
org.springframework
spring-core
org.springframework
spring-beans
{code}
doing clean install i get this exception:
{code}
constituent[0]: file:/d:/tools/maven2/lib/bcpg-jdk15-140.jar
constituent[1]: file:/d:/tools/maven2/lib/bcprov-jdk15-140.jar
constituent[2]: file:/d:/tools/maven2/lib/commons-cli-1.0.jar
constituent[3]: file:/d:/tools/maven2/lib/commons-logging-api-1.1.jar
constituent[4]: file:/d:/tools/maven2/lib/doxia-sink-api-1.0-alpha-9.jar
constituent[5]: file:/d:/tools/maven2/lib/google-collect-snapshot-20080530.jar
constituent[6]: file:/d:/tools/maven2/lib/jetty-6.1.12.jar
constituent[7]: file:/d:/tools/maven2/lib/jetty-client-6.1.12.jar
constituent[8]: file:/d:/tools/maven2/lib/jetty-sslengine-6.1.12.jar
constituent[9]: file:/d:/tools/maven2/lib/jetty-util-6.1.12.jar
constituent[10]: file:/d:/tools/maven2/lib/jsch-0.1.38.jar
constituent[11]: file:/d:/tools/maven2/lib/log4j-1.2.12.jar
constituent[12]: file:/d:/tools/maven2/lib/maven-compat-3.0-alpha-1.jar
constituent[13]: file:/d:/tools/maven2/lib/maven-core-3.0-alpha-1.jar
constituent[14]: file:/d:/tools/maven2/lib/maven-distribution-3.0-alpha-1.jar
constituent[15]: file:/d:/tools/maven2/lib/maven-embedder-3.0-alpha-1.jar
constituent[16]: file:/d:/tools/maven2/lib/maven-lifecycle-3.0-alpha-1.jar
constituent[17]: file:/d:/tools/maven2/lib/maven-mercury-3.0-alpha-1.jar
constituent[18]: file:/d:/tools/maven2/lib/maven-model-3.0-alpha-1.jar
constituent[19]: file:/d:/tools/maven2/lib/maven-plugin-api-3.0-alpha-1.jar
constituent[20]: file:/d:/tools/maven2/lib/maven-project-3.0-alpha-1.jar
constituent[21]: file:/d:/tools/maven2/lib/maven-project-builder-3.0-alpha-1.jar
constituent[22]: file:/d:/tools/maven2/lib/maven-reporting-api-3.0-alpha-1.jar
constituent[23]: file:/d:/tools/maven2/lib/maven-toolchain-3.0-alpha-1.jar
constituent[24]: file:/d:/tools/maven2/lib/mercury-artifact-1.0.0-alpha-2.jar
constituent[25]: file:/d:/tools/maven2/lib/mercury-crypto-api-1.0.0-alpha-2.jar
constituent[26]:
file:/d:/tools/maven2/lib/mercury-crypto-basic-1.0.0-alpha-2.jar
constituent[27]: file:/d:/tools/maven2/lib/mercury-event-1.0.0-alpha-2.jar
constituent[28]: file:/d:/tools/maven2/lib/mercury-external-1.0.0-alpha-2.jar
constituent[29]: file:/d:/tools/maven2/lib/mercury-logging-1.0.0-alpha-2.jar
constituent[30]: file:/d:/tools/maven2/lib/mercury-md-sat-1.0.0-alpha-2.jar
constituent[31]: file:/d:/tools/maven2/lib/mercury-md-shared-1.0.0-alpha-2.jar
constituent[32]: file:/d:/tools/maven2/lib/mercury-plexus-1.0.0-alpha-2.jar
constituent[33]: file:/d:/tools/maven2/lib/mercury-repo-api-1.0.0-alpha-2.jar
constituent[34]:
file:/d:/tools/maven2/lib/mercury-repo-cache-fs-1.0.0-alpha-2.jar
constituent[35]:
file:/d:/tools/maven2/lib/mercury-repo-local-m2-1.0.0-alpha-2.jar
constituent[36]:
file:/d:/tools/maven2/lib/mercury-repo-remote-m2-1.0.0-alpha-2.jar
constituent[37]:
file:/d:/tools/maven2/lib/mercury-repo-virtual-1.0.0-alpha-2.jar
constituent[38]:
file:/d:/tools/maven2/lib/mercury-transport-api-1.0.0-alpha-2.jar
constituent[39]:
file:/d:/tools/maven2/lib/mercury-transport-http-1.0.0-alpha-2.jar
constituent[40]: file:/d:/tools/maven2/lib/mercury-util-1.0.0-alpha-2.jar
constituent[41]: file:/d:/tools/maven2/lib/model-builder-1.0.jar
constituent[42]: file:/d:/tools/maven2/lib/nekohtml-1.9.6.2.jar
constituent[43]: file:/d:/tools/maven2/lib/org.sat4j.core-2.0.4.jar
constituent[44]: file:/d:/tools/maven2/lib/org.sat4j.pb-2.0.4.jar
constituent[45]:
file:/d:/tools/maven2/lib/plexus-component-annotations-1.0-beta-3.0.1.jar
constituent[46]:
file:/d:/tools/maven2/lib/plexus-container-default-1.0-beta-3.0.1.jar
constituent[47]:
file:/d:/tools/maven2/lib/plexus-interactivity-api-1.0-alpha-6.jar
constituent[48]: file:/d:/tools/maven2/lib/plexus-interpolation-1.1.jar
constituent[49]: file:/d:/tools/maven2/lib/plexus-lang-1.1.jar
constituent[50]: file:/d:/tools/maven2/lib/plexus-plugin-manager-1.0-alpha-1.jar
constituent[51]: file:/d:/tools/maven2/lib/plexus-utils-1.5.6.jar
constituent[52]: file:/d:/tools/maven2/lib/servlet-api-2.5-6.1.12.jar
constituent[53]: file:/d:/tools/maven2/lib/slf4j-api-1.5.3.jar
constituent[54]: file:/d:/too
[jira] Created: (MNG-3960) cannot build projects which use plexus-maven-plugin with 3.0-alpha-1
cannot build projects which use plexus-maven-plugin with 3.0-alpha-1
Key: MNG-3960
URL: http://jira.codehaus.org/browse/MNG-3960
Project: Maven 2
Issue Type: Bug
Components: Class Loading
Affects Versions: 3.0-alpha-1
Reporter: Olivier Lamy
When building projects with mvn 3.0-alpha-1 which plexus-maven-plugin (release
project in mvn svn, some plugins maven-changes-plugin, continuum, archiva), I
have the following exception (java.lang.ClassNotFoundException) :
{code}
Exception in thread "main" java.lang.NoClassDefFoundError
at
org.codehaus.plexus.cdc.gleaner.QDoxComponentGleaner.class$(QDoxComponentGleaner.java:231)
at
org.codehaus.plexus.cdc.gleaner.QDoxComponentGleaner.(QDoxComponentGleaner.java:230)
at
org.codehaus.plexus.maven.plugin.SourceComponentDescriptorExtractor.extract(SourceComponentDescriptorExtractor.java:57)
at
org.codehaus.plexus.maven.plugin.AbstractDescriptorMojo.generateDescriptor(AbstractDescriptorMojo.java:131)
at
org.codehaus.plexus.maven.plugin.PlexusDescriptorMojo.execute(PlexusDescriptorMojo.java:60)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:631)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:492)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:259)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:201)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:164)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:207)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:846)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
Caused by: java.lang.ClassNotFoundException:
org.codehaus.plexus.personality.plexus.lifecycle.phase.Suspendable
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
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.strategy.ForeignStrategy.loadClass(ForeignStrategy.java:39)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:207)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
at
org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:73)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:207)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
... 22 more
{code}
--
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: (MCOMPILER-41) recompiling behaves differently when build.sourceDirectory is not set to the default path src/main/java/
[ http://jira.codehaus.org/browse/MCOMPILER-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159948#action_159948 ] Kelly Davis commented on MCOMPILER-41: -- I did some playing with the source for the plexus-compiler-api to see what was happening. Basically the issue appears to be a result of specifying multiple source roots. If I specify a sourceDirectory as src and in src I actually have 2 (or more) source directories, everything compiles fine, but the mapping between source and target files are screwed up (because I really have multiple source directories). So when the scanner checks to see if the file(s) need to be compiled, they aren't there. I fixed the sourceDirectory to specify just one of my source directories under src, and then use the buildhelper plugin to add the additional source directories, and it is now detecting changes properly. The only potential issue here, I guess, is that it would be nice if it would detect and give a warning when you specify multiple source directories. > recompiling behaves differently when build.sourceDirectory is not set to the > default path src/main/java/ > > > Key: MCOMPILER-41 > URL: http://jira.codehaus.org/browse/MCOMPILER-41 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug > Environment: Linux, Windox XP >Reporter: akinokaze >Assignee: Olivier Lamy > Attachments: MavenWebTest.zip, MCOMPILER-41.zip > > > the default build.sourceDirectory is at src/man/java > When our code is located in this default directory, the first time we run mvn > compile all the source codes will be compiled as expected. > When we run mvn compile again without any changes to the src code, the > message > "Nothing to compile - all classes are up to date", which is also the expected > behaviour. > If we set build.sourceDirectory to another directory, the behaviour is > different. > The first time we run mvn compile all the source codes will be compiled as > expected. > But when we run mvn compile again without any changes to the src code, all > the source codes are compiled again. > This will increase the rebuild time significantly. -- 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-3004) Allow build lifecycle to execute tasks in parallel
[ http://jira.codehaus.org/browse/MNG-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159982#action_159982 ] Nigel Magnay commented on MNG-3004: --- My original intent was so that all activities could run in parallel, to the granularity of a particular project. I.E if projects A B and C all depend on project X (and nothing else), then after 'mvn install' finishes on 'X', 'mvn install' can be executed, in parallel, on each of A, B and C. I stopped trying to get it to work when I realised that the biggest problem is that the local repository isn't safe to be accessed from multiple threads (or even multiple processes for that matter). I think that's a known issue too - I'm guessing that the ability to somehow lock/unlock repository objects (or perhaps use some kind of smarter local repository) is a dependency to getting this to work. > Allow build lifecycle to execute tasks in parallel > -- > > Key: MNG-3004 > URL: http://jira.codehaus.org/browse/MNG-3004 > Project: Maven 2 > Issue Type: Improvement > Components: Bootstrap & Build, General, Performance >Affects Versions: 2.0.6 >Reporter: Nigel Magnay > Fix For: 2.1.0-M3 > > Attachments: parallel-builds.patch > > > One of the great advantages with maven over scripted build environments is > that it can calculate the dependencies of the build, and it could execute > items that are independent of each other in parallel. > Unfortunately it currently doesn't do this, which would be a big win over > tools such as 'ant'. It also means that multicore machines have lots of idle > capacity when running a serial build that could be utilised. > I had a quick shot at seeing what might be required. Bear in mind this is the > first time I have looked at maven internally, and I was just trying to feel > my way around and build a POC. I got some of the way there, but my build > threads don't seem to have the correct classpath - I think this is something > to do with plexus / classworlds - but I don't know enough. > It'd be great to get this feature in a future version, or a way of running my > hack (figuring out why in a thread has not the plexus stuff) in the interim. -- 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: (MANTTASKS-124) Setting dependencies with the provided scope does not work
[ http://jira.codehaus.org/browse/MANTTASKS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159985#action_159985 ] Trevor Leach commented on MANTTASKS-124: Thank you for your suggestion. This will approach will work for me in the short term. For others implementing this work around, I'll list some things to think about. 1) The POM published with your artifacts isn't being truthful with its dependencies. Any dependent projects may not end up with everything they need in their classpaths. 2) The build scripts will need to exclude the runtime scoped dependencies when generating the WEB-INF/lib dir, which would normally be included. 3) This solution will not work if the project has real runtime dependencies. > Setting dependencies with the provided scope does not work > -- > > Key: MANTTASKS-124 > URL: http://jira.codehaus.org/browse/MANTTASKS-124 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: dependencies task >Affects Versions: 2.0.9 > Environment: OS X 10.4.11, Java 5, Ant 1.7.0, Ant 1.6.5 >Reporter: John Gibson > > If you use the provided scope to pull in dependences like this: > filesetId="osgi.provided.fileset" verbose="true" useScope="provided"> > > > > Then the result classpath and fileset are empty despite the POM containing > definitions like this: > ... > > > org.osgi > osgi-compendium > 4.1.0 > provided > > > org.osgi > osgi-core > 4.1.0 > provided > > ... > > I would expect to have the path/fileset contain at least those two jars (I'm > not sure about transitive dependencies, however). > Other users have encountered this issue, see here: > http://www.nabble.com/maven-ant-tasks-and-the-provided-scope-td19662878.html -- 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-3872) Profiles not being activated for relocated POMs
[ http://jira.codehaus.org/browse/MNG-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3872: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Profiles not being activated for relocated POMs > --- > > Key: MNG-3872 > URL: http://jira.codehaus.org/browse/MNG-3872 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.0-alpha-1 >Reporter: Shane Isbell >Assignee: Shane Isbell >Priority: Minor > Fix For: 3.0-alpha-3 > > > Profiles are not being activated for relocated POMs. This causes certain POMs > to throw a validation error. -- 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-3850) Integrate new Profile Activators
[ http://jira.codehaus.org/browse/MNG-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3850: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Integrate new Profile Activators > > > Key: MNG-3850 > URL: http://jira.codehaus.org/browse/MNG-3850 > Project: Maven 2 > Issue Type: Task > Components: Profiles >Affects Versions: 3.0-alpha-2 >Reporter: Brian Fox >Assignee: Shane Isbell > Fix For: 3.0-alpha-3 > > > This is a complete replacement for the old profile activators. The new > framework uses maven-shared-model component, with model containers, model > data source and model properties for determining active profiles. -- 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-2766) Refactor DefaultLifecycleExecutor
[ http://jira.codehaus.org/browse/MNG-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2766: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Refactor DefaultLifecycleExecutor > - > > Key: MNG-2766 > URL: http://jira.codehaus.org/browse/MNG-2766 > Project: Maven 2 > Issue Type: Task > Components: Plugins and Lifecycle >Affects Versions: 3.0-alpha-1 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > Another large beast that needs to be broken up. -- 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-3854) switch dependency plugin to use Mercury
[ http://jira.codehaus.org/browse/MNG-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3854: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > switch dependency plugin to use Mercury > > > Key: MNG-3854 > URL: http://jira.codehaus.org/browse/MNG-3854 > Project: Maven 2 > Issue Type: Task > Components: Dependencies >Affects Versions: 3.0-alpha-1 > Environment: all >Reporter: Oleg Gusakov > Fix For: 3.0-alpha-3 > > > As a step towards integrating Mercury into Maven - replace dependency > resolution layer in dep. plugin with Mercury APIs -- 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-3856) Fix interpolation to correctly treat all interpolated variables
[
http://jira.codehaus.org/browse/MNG-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3856:
---
Fix Version/s: (was: 3.0-alpha-2)
3.0-alpha-3
> Fix interpolation to correctly treat all interpolated variables
> ---
>
> Key: MNG-3856
> URL: http://jira.codehaus.org/browse/MNG-3856
> Project: Maven 2
> Issue Type: Bug
>Reporter: Oleg Gusakov
> Fix For: 3.0-alpha-3
>
>
> There are several dependencies that have non-replaced variables, coming from
> maven-mercury implementation:
> {code}
> ==> org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for
> org.apache.maven.scm:maven-scm-api:${maven-scm.version}::jar <==
> org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
>
> ==> org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for
> org.apache.maven:maven-artifact:${maven.version}::jar <==
> org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
>
> ==> org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
>
> ==> org.apache.maven.plugins:maven-ear-plugin:2.3.1::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
> <== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar <==
> org.apache.maven:maven-core:2.0.6::jar <==
> org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
>
> ==> org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for
> org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar <==
> org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
>
>
> ==> org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for
> org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar <==
> org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
>
> ==> org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
> <== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar <==
> org.apache.maven:maven-core:2.0.5::jar <==
> org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
>
>
> ==> org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
> <== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar <==
> org.apache.maven:maven-core:2.0.6::jar <==
> org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
> {code}
--
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-3917) Complete the POM construction tests which will be the validation for the specification
[ http://jira.codehaus.org/browse/MNG-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3917: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Complete the POM construction tests which will be the validation for the > specification > -- > > Key: MNG-3917 > URL: http://jira.codehaus.org/browse/MNG-3917 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > -- 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-3935) Get the Maven Integration Testing Hudson plugin installed on the grid
[ http://jira.codehaus.org/browse/MNG-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3935: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Get the Maven Integration Testing Hudson plugin installed on the grid > - > > Key: MNG-3935 > URL: http://jira.codehaus.org/browse/MNG-3935 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: John Casey > Fix For: 3.0-alpha-3 > > > I want to use this plugin to swap in new versions of Maven so I can build all > the real-world projects and touchstones projects. I know from testing > manually everything is working except Nexus Pro, but I'm ready to add XWiki > and CXF and this will be beyond manual tracking shortly. This needs to be > setup before the alpha-1 rolls 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] Updated: (MNG-3932) Remove all mirror, authentication, and proxy handling out of WagonManager and into a neutral Maven implementation
[ http://jira.codehaus.org/browse/MNG-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3932: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Remove all mirror, authentication, and proxy handling out of WagonManager and > into a neutral Maven implementation > - > > Key: MNG-3932 > URL: http://jira.codehaus.org/browse/MNG-3932 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > We need to protect ourselves from the underlying transport implementation. > Mercury will only touch Maven inside one component, so this is what I'm going > to create on a branch where Wagon only touches Maven inside one component. I > can't really implement the plugin manager properly without hardcoding because > I can't get the correct mirror information to Mercury without wiring in the > WagonManager which I'm not going to do. I'm just going to do it properly. We > won't have extension support in alpha-1. Oh well. -- 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-3862) Remove all plugin configuration manipulation from the plugin manager
[ http://jira.codehaus.org/browse/MNG-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3862: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Remove all plugin configuration manipulation from the plugin manager > - > > Key: MNG-3862 > URL: http://jira.codehaus.org/browse/MNG-3862 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > All of this work is being done by the new model framework and the rules for > manipulating the model properties. All of the requirements for plugin > configuration inheriting and merging are taken care of. We need to detangle > the plugin configuration from execution. This will pave the way to use the > new plexus plugin manager to load and execute plugins. -- 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-2765) Refactor DefaultPluginManager
[ http://jira.codehaus.org/browse/MNG-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2765: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Refactor DefaultPluginManager > - > > Key: MNG-2765 > URL: http://jira.codehaus.org/browse/MNG-2765 > Project: Maven 2 > Issue Type: Task > Components: Plugins and Lifecycle >Affects Versions: 3.0-alpha-1 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > This beast needed to be broken down and the call graph simplified. We could > also create a lookup( role[-hint], configuration ) in plexus to keep from > exposing configurators. -- 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-3913) Figure out why MavenEmbedderExampleTest fails on the grid and reenable when fixed.
[ http://jira.codehaus.org/browse/MNG-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3913: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Figure out why MavenEmbedderExampleTest fails on the grid and reenable when > fixed. > -- > > Key: MNG-3913 > URL: http://jira.codehaus.org/browse/MNG-3913 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > -- 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-3903) Create a Maven specific abstraction for Artifact use within Maven
[ http://jira.codehaus.org/browse/MNG-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3903: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Create a Maven specific abstraction for Artifact use within Maven > - > > Key: MNG-3903 > URL: http://jira.codehaus.org/browse/MNG-3903 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl > Fix For: 3.0-alpha-3 > > > There's no point in just flipping all references from Maven Artifact to > Mercury without protecting ourselves from this sort of thing in the future. > This will also allow us to remove the few straggling bits in Mercury that are > Maven specific like scopes and classifiers. > Once this is created then we can seriously consider plugging in Mercury > behind it. We have a complete and total clusterfuck as it stands as the > components for artifact manipulation and the use of Artifact are just used > scatter shot through out the whole codebase. A direct transition to Mercury > would make for a goat fuck we can avoid. -- 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-3901) Merge all project building code into a single component
[ http://jira.codehaus.org/browse/MNG-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3901: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Merge all project building code into a single component > --- > > Key: MNG-3901 > URL: http://jira.codehaus.org/browse/MNG-3901 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > Right now we have the new project builder being used by the old project > builder code. We need to collapse everything into the one new component and > remove all dead components. I can see that the pathTranslator isn't being > used any more. There are probably references to some other dead bits that > need to be cleaned up. -- 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-3858) Use new plexus plugin manager component to load extensions
[ http://jira.codehaus.org/browse/MNG-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3858: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Use new plexus plugin manager component to load extensions > -- > > Key: MNG-3858 > URL: http://jira.codehaus.org/browse/MNG-3858 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > I have created a generalized component for loading extensions/plugins in > plexus-based applications which works in conjunction with the changes that we > have made to plexus to simplify dynamically loading and executing components. -- 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-3281) Revisit backwards compat of extensions (IT 0114)
[ http://jira.codehaus.org/browse/MNG-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3281: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Revisit backwards compat of extensions (IT 0114) > > > Key: MNG-3281 > URL: http://jira.codehaus.org/browse/MNG-3281 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 3.0-alpha-1 >Reporter: Brett Porter >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > currently, it 0114 doesn't pass due to the removal of extension support > we need to either: > - restore some form of backwards compat by loading the extension into the > expected place > - provide a graceful failure instead -- 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: (MNG-3961) Update the version of the XSD
Update the version of the XSD - Key: MNG-3961 URL: http://jira.codehaus.org/browse/MNG-3961 Project: Maven 2 Issue Type: Bug Components: POM Affects Versions: 3.0-alpha-1 Reporter: Vincent Siveton Fix For: 3.0-alpha-2 Since the model adds new field (ActivationCustom), I think the xsd version should be 4.0.1 or 5.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] Updated: (MNG-3961) Update the version of the XSD
[ http://jira.codehaus.org/browse/MNG-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MNG-3961: - Fix Version/s: 3.0-alpha-2 > Update the version of the XSD > - > > Key: MNG-3961 > URL: http://jira.codehaus.org/browse/MNG-3961 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 3.0-alpha-1 >Reporter: Vincent Siveton > Fix For: 3.0-alpha-2 > > > Since the model adds new field (ActivationCustom), I think the xsd version > should be 4.0.1 or 5.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] Updated: (MNG-3954) Remove the RuntimeInfo required in the setting.mdo
[ http://jira.codehaus.org/browse/MNG-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3954: --- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 > Remove the RuntimeInfo required in the setting.mdo > -- > > Key: MNG-3954 > URL: http://jira.codehaus.org/browse/MNG-3954 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > This addition to the code segments was required to make the release plugin > work. Until plugins are refactored not to require the direct use of settings > we will need to keep this around. -- 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-3960) cannot build projects which use plexus-maven-plugin with 3.0-alpha-1
[
http://jira.codehaus.org/browse/MNG-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MNG-3960:
--
Fix Version/s: 3.0-alpha-2
> cannot build projects which use plexus-maven-plugin with 3.0-alpha-1
>
>
> Key: MNG-3960
> URL: http://jira.codehaus.org/browse/MNG-3960
> Project: Maven 2
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.0-alpha-1
>Reporter: Olivier Lamy
> Fix For: 3.0-alpha-2
>
>
> When building projects with mvn 3.0-alpha-1 which plexus-maven-plugin
> (release project in mvn svn, some plugins maven-changes-plugin, continuum,
> archiva), I have the following exception (java.lang.ClassNotFoundException) :
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError
> at
> org.codehaus.plexus.cdc.gleaner.QDoxComponentGleaner.class$(QDoxComponentGleaner.java:231)
> at
> org.codehaus.plexus.cdc.gleaner.QDoxComponentGleaner.(QDoxComponentGleaner.java:230)
> at
> org.codehaus.plexus.maven.plugin.SourceComponentDescriptorExtractor.extract(SourceComponentDescriptorExtractor.java:57)
> at
> org.codehaus.plexus.maven.plugin.AbstractDescriptorMojo.generateDescriptor(AbstractDescriptorMojo.java:131)
> at
> org.codehaus.plexus.maven.plugin.PlexusDescriptorMojo.execute(PlexusDescriptorMojo.java:60)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:631)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:492)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:259)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:201)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:164)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:207)
> at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:846)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
> 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
> Caused by: java.lang.ClassNotFoundException:
> org.codehaus.plexus.personality.plexus.lifecycle.phase.Suspendable
> at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> 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.strategy.ForeignStrategy.loadClass(ForeignStrategy.java:39)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:207)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
> at
> org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:73)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:207)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:164)
> ... 22 more
> {code}
--
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: (MINSTALL-57) Default generatePom to true
Default generatePom to true
---
Key: MINSTALL-57
URL: http://jira.codehaus.org/browse/MINSTALL-57
Project: Maven 2.x Install Plugin
Issue Type: Improvement
Affects Versions: 2.2
Reporter: Benjamin Bentmann
Priority: Minor
{code:java}
// TODO: check if it exists first, and default to true if not
if ( generatePom )
{
}
{code}
+1
Otherwise users easily wonder why Maven keeps trying to download the POM on
each build.
--
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: (MINSTALL-57) Default generatePom to true
[
http://jira.codehaus.org/browse/MINSTALL-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MINSTALL-57.
-
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.3
Done in [r731716|http://svn.eu.apache.org/viewvc?view=rev&revision=731716].
> Default generatePom to true
> ---
>
> Key: MINSTALL-57
> URL: http://jira.codehaus.org/browse/MINSTALL-57
> Project: Maven 2.x Install Plugin
> Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 2.3
>
>
> {code:java}
> // TODO: check if it exists first, and default to true if not
> if ( generatePom )
> {
>
> }
> {code}
> +1
> Otherwise users easily wonder why Maven keeps trying to download the POM on
> each build.
--
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: (MINSTALL-49) install-file with javadoc and sources
[ http://jira.codehaus.org/browse/MINSTALL-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MINSTALL-49. - Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.3 Added new parameters in [r731740|http://svn.eu.apache.org/viewvc?view=rev&revision=731740]. > install-file with javadoc and sources > - > > Key: MINSTALL-49 > URL: http://jira.codehaus.org/browse/MINSTALL-49 > Project: Maven 2.x Install Plugin > Issue Type: New Feature >Reporter: Andreas Höhmann >Assignee: Benjamin Bentmann > Fix For: 2.3 > > > I have a external jar + javadoc + sources ... how can i install these 3 files > in one step? > mvn install:install-file -Dfile=your-artifact-1.0.jar > -Djavadoc=file=your-artifact-1.0-javadoc.jar > -Dsources=your-artifact-1.0-sources.jar -- 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-3903) Create a Maven specific abstraction for Artifact use within Maven
[ http://jira.codehaus.org/browse/MNG-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3903: --- Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-2 > Create a Maven specific abstraction for Artifact use within Maven > - > > Key: MNG-3903 > URL: http://jira.codehaus.org/browse/MNG-3903 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl > Fix For: 3.0-alpha-2 > > > There's no point in just flipping all references from Maven Artifact to > Mercury without protecting ourselves from this sort of thing in the future. > This will also allow us to remove the few straggling bits in Mercury that are > Maven specific like scopes and classifiers. > Once this is created then we can seriously consider plugging in Mercury > behind it. We have a complete and total clusterfuck as it stands as the > components for artifact manipulation and the use of Artifact are just used > scatter shot through out the whole codebase. A direct transition to Mercury > would make for a goat fuck we can avoid. -- 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: (MNG-3962) Allow a Maven runtime to update itself
Allow a Maven runtime to update itself -- Key: MNG-3962 URL: http://jira.codehaus.org/browse/MNG-3962 Project: Maven 2 Issue Type: Improvement Reporter: Jason van Zyl -- 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-3962) Allow a Maven runtime to update itself
[ http://jira.codehaus.org/browse/MNG-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3962: --- Fix Version/s: 3.0-alpha-2 > Allow a Maven runtime to update itself > -- > > Key: MNG-3962 > URL: http://jira.codehaus.org/browse/MNG-3962 > Project: Maven 2 > Issue Type: Improvement >Reporter: Jason van Zyl > Fix For: 3.0-alpha-2 > > -- 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: (MINSTALL-28) Error in Project Attempting to Use maven-install-plugin with 'lib' Packaging
[
http://jira.codehaus.org/browse/MINSTALL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160029#action_160029
]
Dan Tran commented on MINSTALL-28:
--
I think we should close this as a wont fix since user does not do it right. The
correct way is to use build-helper-maven-plugin to deploy it
> Error in Project Attempting to Use maven-install-plugin with 'lib' Packaging
>
>
> Key: MINSTALL-28
> URL: http://jira.codehaus.org/browse/MINSTALL-28
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: Win2003, running mvn 2.04 in Cygwin bash shell
> Locally built version maven-install-plugin 2.2-SNAPSHOT
>Reporter: Brad Harper
>
> I'm using M2 'maven-native-plugin' to build C++ libraries and apps. Within the
> overall project structure I have a module to handle a set of 3rd-party
> (library) artifacts. Some of these are native libraries (without source) and
> some are
> built from open source.
> I'd like to run
>% mvn install
> in the 3rd-party module and have the pre-built libraries simply copied
> into the local repository with an that can be expressed in
> the part elsewhere.
> The POM descriptor for one of these native library sub-modules contains
> {code:xml}
> lib
>
>
>
> maven-install-plugin
>
>
> install-library
> install
>
> com-epsiia-dxr-third-party
>
> dxr-third-party-com-emc-centera-fplibrary-WINDOWS-X86
> 2.0SP1
> lib
> FPLibrary.lib
>
>
>
>
>
>
> {code}
> but maven complains
> {noformat}
> [ERROR] BUILD ERROR
> [INFO]
> [INFO] Cannot find lifecycle mapping for packaging: 'lib'
> Component descriptor cannot be found in the component repository:
> org.apache.maven.lifecyle.mapping.LifecycleMappinglib.
> {noformat}
> The 'maven-native-plugin' is supplied by codehaus.org and the plugin's
> use is declared in an ancestor POM descriptor. In modules where C++
> source is compiled/linked, the 'install' goal moves the resulting
> artifact into the repository.
> Shouldn't this work?
--
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: (MNG-3963) Specifying how profiles should work
Specifying how profiles should work --- Key: MNG-3963 URL: http://jira.codehaus.org/browse/MNG-3963 Project: Maven 2 Issue Type: Task Reporter: Jason van Zyl Fix For: 3.0-alpha-2 -- 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-3963) Specifying how profiles should work
[ http://jira.codehaus.org/browse/MNG-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3963: --- Fix Version/s: 3.0-alpha-2 > Specifying how profiles should work > --- > > Key: MNG-3963 > URL: http://jira.codehaus.org/browse/MNG-3963 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl > Fix For: 3.0-alpha-2 > > -- 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-3856) Fix interpolation to correctly treat all interpolated variables
[
http://jira.codehaus.org/browse/MNG-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3856:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-2
> Fix interpolation to correctly treat all interpolated variables
> ---
>
> Key: MNG-3856
> URL: http://jira.codehaus.org/browse/MNG-3856
> Project: Maven 2
> Issue Type: Bug
>Reporter: Oleg Gusakov
> Fix For: 3.0-alpha-2
>
>
> There are several dependencies that have non-replaced variables, coming from
> maven-mercury implementation:
> {code}
> ==> org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for
> org.apache.maven.scm:maven-scm-api:${maven-scm.version}::jar <==
> org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
>
> ==> org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for
> org.apache.maven:maven-artifact:${maven.version}::jar <==
> org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
>
> ==> org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
>
> ==> org.apache.maven.plugins:maven-ear-plugin:2.3.1::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
> <== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar <==
> org.apache.maven:maven-core:2.0.6::jar <==
> org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
>
> ==> org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for
> org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar <==
> org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
>
>
> ==> org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for
> org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar <==
> org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
>
> ==> org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
> <== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar <==
> org.apache.maven:maven-core:2.0.5::jar <==
> org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
>
>
> ==> org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
> org.apache.maven.mercury.metadata.MetadataTreeException: did not find
> non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
> <== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar <==
> org.apache.maven:maven-core:2.0.6::jar <==
> org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
> {code}
--
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-3961) Update the version of the XSD
[ http://jira.codehaus.org/browse/MNG-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160031#action_160031 ] Jason van Zyl commented on MNG-3961: Do you know when this was added and for what? > Update the version of the XSD > - > > Key: MNG-3961 > URL: http://jira.codehaus.org/browse/MNG-3961 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 3.0-alpha-1 >Reporter: Vincent Siveton > Fix For: 3.0-alpha-2 > > > Since the model adds new field (ActivationCustom), I think the xsd version > should be 4.0.1 or 5.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] Updated: (MNG-3866) [regression] Plugin definitions from child and parent are not merged when version differs
[
http://jira.codehaus.org/browse/MNG-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3866:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-2
> [regression] Plugin definitions from child and parent are not merged when
> version differs
> -
>
> Key: MNG-3866
> URL: http://jira.codehaus.org/browse/MNG-3866
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
> Fix For: 3.0-alpha-2
>
> Attachments: plugin-model-container.patch
>
>
> Parent POM snippet
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
>
>
> PASSED
>
>
>
> {code}
> Child POM snippet:
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
> 2.1-SNAPSHOT
>
>
> {code}
> Effective child POM:
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
> 2.1-SNAPSHOT
>
>
> {code}
> i.e. the configuration from the parent POM is completely lost.
--
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-3937) [regression] Goals inherited from parent are lost when merging with child execution
[
http://jira.codehaus.org/browse/MNG-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3937:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-2
> [regression] Goals inherited from parent are lost when merging with child
> execution
> ---
>
> Key: MNG-3937
> URL: http://jira.codehaus.org/browse/MNG-3937
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0-alpha-2
>
>
> Parent POM snippet:
> {code:xml}
>
> org.apache.maven.its.plugins
> maven-it-plugin-a
>
>
>
> parent
>
>
>
>
> {code}
> Child POM snippet:
> {code:xml}
>
> org.apache.maven.its.plugins
> maven-it-plugin-a
>
>
>
> child
>
>
>
>
> {code}
> Effective child POM in Maven 2.x:
> {code:xml}
>
> org.apache.maven.its.plugins
> maven-it-plugin-a
>
>
>
> child
> parent
>
>
>
>
> {code}
> i.e. both the goal from the child and the goal from the parent (in that
> order) will be executed. In Maven 3.x however, only the child's goal is
> present.
--
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-3938) [regression] Plugin executions with default id are not always merged
[
http://jira.codehaus.org/browse/MNG-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3938:
---
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-2
> [regression] Plugin executions with default id are not always merged
>
>
> Key: MNG-3938
> URL: http://jira.codehaus.org/browse/MNG-3938
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
>Priority: Minor
> Fix For: 3.0-alpha-2
>
>
> Plugin executions using the default id are not merged during inheritance if
> a) the parent POM defines the plugin via plugin management
> b) the parent POM omits the {{}} for the plugin execution
> c) the child POM uses {{default}} for the plugin execution
> This causes Maven 3.x to fail with a validation error (duplicate execution
> ids)
--
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-3937) [regression] Goals inherited from parent are lost when merging with child execution
[
http://jira.codehaus.org/browse/MNG-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3937:
---
Assignee: Shane Isbell
> [regression] Goals inherited from parent are lost when merging with child
> execution
> ---
>
> Key: MNG-3937
> URL: http://jira.codehaus.org/browse/MNG-3937
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
>Priority: Minor
> Fix For: 3.0-alpha-2
>
>
> Parent POM snippet:
> {code:xml}
>
> org.apache.maven.its.plugins
> maven-it-plugin-a
>
>
>
> parent
>
>
>
>
> {code}
> Child POM snippet:
> {code:xml}
>
> org.apache.maven.its.plugins
> maven-it-plugin-a
>
>
>
> child
>
>
>
>
> {code}
> Effective child POM in Maven 2.x:
> {code:xml}
>
> org.apache.maven.its.plugins
> maven-it-plugin-a
>
>
>
> child
> parent
>
>
>
>
> {code}
> i.e. both the goal from the child and the goal from the parent (in that
> order) will be executed. In Maven 3.x however, only the child's goal is
> present.
--
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: (MNG-3964) Specify execution id container rules
Specify execution id container rules Key: MNG-3964 URL: http://jira.codehaus.org/browse/MNG-3964 Project: Maven 2 Issue Type: Task Reporter: Jason van Zyl Fix For: 3.0-alpha-2 -- 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-3964) Specify execution id container rules
[ http://jira.codehaus.org/browse/MNG-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3964: --- Fix Version/s: 3.0-alpha-2 > Specify execution id container rules > > > Key: MNG-3964 > URL: http://jira.codehaus.org/browse/MNG-3964 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-2 > > -- 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: (MNG-3965) shade plugin error when compiling Mercury trunk
shade plugin error when compiling Mercury trunk --- Key: MNG-3965 URL: http://jira.codehaus.org/browse/MNG-3965 Project: Maven 2 Issue Type: Bug Affects Versions: 3.0-alpha-1 Reporter: Oleg Gusakov Cannot compile Mercury trunk with 3.0-alpha-1 Attached is the -X output. To duplicate: * check out mercury from http://svn.apache.org/repos/asf/maven/mercury/trunk/ * mvn clean install -X -- 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-3965) shade plugin error when compiling Mercury trunk
[ http://jira.codehaus.org/browse/MNG-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3965: -- Attachment: shade-error.txt > shade plugin error when compiling Mercury trunk > --- > > Key: MNG-3965 > URL: http://jira.codehaus.org/browse/MNG-3965 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov > Fix For: 3.0-alpha-2 > > Attachments: shade-error.txt > > > Cannot compile Mercury trunk with 3.0-alpha-1 > Attached is the -X output. > To duplicate: > * check out mercury from http://svn.apache.org/repos/asf/maven/mercury/trunk/ > * mvn clean install -X -- 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-3965) shade plugin error when compiling Mercury trunk
[ http://jira.codehaus.org/browse/MNG-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3965: -- Fix Version/s: 3.0-alpha-2 > shade plugin error when compiling Mercury trunk > --- > > Key: MNG-3965 > URL: http://jira.codehaus.org/browse/MNG-3965 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov > Fix For: 3.0-alpha-2 > > Attachments: shade-error.txt > > > Cannot compile Mercury trunk with 3.0-alpha-1 > Attached is the -X output. > To duplicate: > * check out mercury from http://svn.apache.org/repos/asf/maven/mercury/trunk/ > * mvn clean install -X -- 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: (MNG-3966) Requirements (User Story)
Requirements (User Story) - Key: MNG-3966 URL: http://jira.codehaus.org/browse/MNG-3966 Project: Maven 2 Issue Type: Sub-task Components: Artifacts and Repositories Affects Versions: 3.0-alpha-1 Reporter: Oleg Gusakov -- 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-3966) Requirements (User Story)
[ http://jira.codehaus.org/browse/MNG-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3966: -- Description: * standalone application * maintains a set of "maven distributions" on user disk * allows user to ** list local "installed" distributions (inventory function) ** list available remote ditributions > Requirements (User Story) > - > > Key: MNG-3966 > URL: http://jira.codehaus.org/browse/MNG-3966 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov > > * standalone application > * maintains a set of "maven distributions" on user disk > * allows user to > ** list local "installed" distributions (inventory function) > ** list available remote ditributions -- 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-3966) Requirements (User Story)
[ http://jira.codehaus.org/browse/MNG-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3966: -- Description: *Delta Manager* story: * standalone library * CLI wrapper * starts for a particular maven instance on disk * lists all the available "compatible" versions (like 3.0.* family) * allows to up / down grade current instance to any of available "compatible" version * works on binaries only ( the ./lib folder), all other files presumed installed and compatible *Installer* story: * standalone library * CLI wrapper * maintains a set of "maven distributions" on user disk * allows user to ** list local "installed" distributions (inventory function) ** list available remote distributions ** install a version ** remove a version ** switch was: * standalone application * maintains a set of "maven distributions" on user disk * allows user to ** list local "installed" distributions (inventory function) ** list available remote ditributions > Requirements (User Story) > - > > Key: MNG-3966 > URL: http://jira.codehaus.org/browse/MNG-3966 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov > > *Delta Manager* story: > * standalone library > * CLI wrapper > * starts for a particular maven instance on disk > * lists all the available "compatible" versions (like 3.0.* family) > * allows to up / down grade current instance to any of available "compatible" > version > * works on binaries only ( the ./lib folder), all other files presumed > installed and compatible > *Installer* story: > * standalone library > * CLI wrapper > * maintains a set of "maven distributions" on user disk > * allows user to > ** list local "installed" distributions (inventory function) > ** list available remote distributions > ** install a version > ** remove a version > ** switch -- 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-3966) Requirements (User Story)
[ http://jira.codehaus.org/browse/MNG-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3966: -- Description: *Delta Manager* story: * standalone library * CLI wrapper * is run for a particular maven instance on disk ** lists all the available "compatible" versions (like 3.0.* family) ** allows to up / down grade current instance to any of available "compatible" version ** works on binaries only ( the ./lib folder), all other files presumed installed and compatible *Installer* story: * standalone library * CLI wrapper * maintains a set of "maven distributions" on user disk * allows user to ** list local "installed" distributions (inventory function) ** list available remote distributions ** install a version ** remove a version ** switch was: *Delta Manager* story: * standalone library * CLI wrapper * starts for a particular maven instance on disk * lists all the available "compatible" versions (like 3.0.* family) * allows to up / down grade current instance to any of available "compatible" version * works on binaries only ( the ./lib folder), all other files presumed installed and compatible *Installer* story: * standalone library * CLI wrapper * maintains a set of "maven distributions" on user disk * allows user to ** list local "installed" distributions (inventory function) ** list available remote distributions ** install a version ** remove a version ** switch > Requirements (User Story) > - > > Key: MNG-3966 > URL: http://jira.codehaus.org/browse/MNG-3966 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov > > *Delta Manager* story: > * standalone library > * CLI wrapper > * is run for a particular maven instance on disk > ** lists all the available "compatible" versions (like 3.0.* family) > ** allows to up / down grade current instance to any of available > "compatible" version > ** works on binaries only ( the ./lib folder), all other files presumed > installed and compatible > *Installer* story: > * standalone library > * CLI wrapper > * maintains a set of "maven distributions" on user disk > * allows user to > ** list local "installed" distributions (inventory function) > ** list available remote distributions > ** install a version > ** remove a version > ** switch -- 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-3961) Update the version of the XSD
[ http://jira.codehaus.org/browse/MNG-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160035#action_160035 ] Paul Benedict commented on MNG-3961: What about aligning the XSD version jump with Maven's major version? Maven 2 -> XSD 4.0 Maven 2.1 -> XSD 4.1 Maven 3 -> XSD 5.0 > Update the version of the XSD > - > > Key: MNG-3961 > URL: http://jira.codehaus.org/browse/MNG-3961 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 3.0-alpha-1 >Reporter: Vincent Siveton > Fix For: 3.0-alpha-2 > > > Since the model adds new field (ActivationCustom), I think the xsd version > should be 4.0.1 or 5.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] Updated: (MNG-3966) Requirements (User Story)
[ http://jira.codehaus.org/browse/MNG-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3966: -- Description: *Delta Manager* story: * standalone library * CLI wrapper * is run for a particular maven instance on disk ** lists all the available "compatible" versions (like 3.0.* family) ** allows to up / down grade current instance to any of available "compatible" version ** works on binaries only ( the ./lib folder), all other files presumed installed and compatible *Installer* story: * standalone library * CLI wrapper * maintains a set of "maven distributions" on user disk * allows user to ** list local "installed" distributions (inventory function) ** list available remote distributions ** install a version ** remove a version ** switch First deliverable shall provide *Delta Manager* implementation was: *Delta Manager* story: * standalone library * CLI wrapper * is run for a particular maven instance on disk ** lists all the available "compatible" versions (like 3.0.* family) ** allows to up / down grade current instance to any of available "compatible" version ** works on binaries only ( the ./lib folder), all other files presumed installed and compatible *Installer* story: * standalone library * CLI wrapper * maintains a set of "maven distributions" on user disk * allows user to ** list local "installed" distributions (inventory function) ** list available remote distributions ** install a version ** remove a version ** switch > Requirements (User Story) > - > > Key: MNG-3966 > URL: http://jira.codehaus.org/browse/MNG-3966 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov > > *Delta Manager* story: > * standalone library > * CLI wrapper > * is run for a particular maven instance on disk > ** lists all the available "compatible" versions (like 3.0.* family) > ** allows to up / down grade current instance to any of available > "compatible" version > ** works on binaries only ( the ./lib folder), all other files presumed > installed and compatible > *Installer* story: > * standalone library > * CLI wrapper > * maintains a set of "maven distributions" on user disk > * allows user to > ** list local "installed" distributions (inventory function) > ** list available remote distributions > ** install a version > ** remove a version > ** switch > First deliverable shall provide *Delta Manager* implementation -- 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: (MNG-3967) Design
Design -- Key: MNG-3967 URL: http://jira.codehaus.org/browse/MNG-3967 Project: Maven 2 Issue Type: Sub-task Reporter: Oleg Gusakov Assignee: Oleg Gusakov -- 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-3967) Design
[ http://jira.codehaus.org/browse/MNG-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3967: -- Description: First deliverable shall * be designed as part of a more complex provisioning system ** provide APIs to be later used by that system * implement *Delta Management" requirements from [MNG-3966] When started with a pointer to a maven instance, it shall: * find *maven-distribution-xx.jar* in ./lib to use for *current version* * retrieve all existing versions of the "same family" (3.0.xx) for *org.apache.maven:maven-distribution:3.0.xx* * let user supply a version to up / down grade to * calculate ** runtime scoped classpath for "current" pom.xml ** runtime scoped classpath for selected version's pom.xml ** retrieve the binary diff to local repo * make ./lib reflect the "new" runtime classpath ** remove replaced binaries ** copy in missing binaries Fix Version/s: 3.0-alpha-2 Component/s: Artifacts and Repositories > Design > -- > > Key: MNG-3967 > URL: http://jira.codehaus.org/browse/MNG-3967 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > > First deliverable shall > * be designed as part of a more complex provisioning system > ** provide APIs to be later used by that system > * implement *Delta Management" requirements from [MNG-3966] > When started with a pointer to a maven instance, it shall: > * find *maven-distribution-xx.jar* in ./lib to use for *current version* > * retrieve all existing versions of the "same family" (3.0.xx) for > *org.apache.maven:maven-distribution:3.0.xx* > * let user supply a version to up / down grade to > * calculate > ** runtime scoped classpath for "current" pom.xml > ** runtime scoped classpath for selected version's pom.xml > ** retrieve the binary diff to local repo > * make ./lib reflect the "new" runtime classpath > ** remove replaced binaries > ** copy in missing binaries -- 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-3967) Design
[ http://jira.codehaus.org/browse/MNG-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3967: -- Description: First deliverable shall * be designed as part of a more complex provisioning system ** provide APIs to be later used by that system * implement *Delta Management* requirements from [MNG-3966] When started with a pointer to a maven instance, it shall: * find *maven-distribution-xx.jar* in ./lib to use for *current version* * retrieve all existing versions of the "same family" (a'la 3.0.xx) for *org.apache.maven:maven-distribution:3.0.xx* * let user supply a version to up / down grade to * calculate ** runtime scoped classpath for "current" pom.xml ** runtime scoped classpath for selected version's pom.xml ** retrieve the binary diff to local repo * make ./lib reflect the "new" runtime classpath ** remove replaced binaries ** copy in missing binaries was: First deliverable shall * be designed as part of a more complex provisioning system ** provide APIs to be later used by that system * implement *Delta Management* requirements from [MNG-3966] When started with a pointer to a maven instance, it shall: * find *maven-distribution-xx.jar* in ./lib to use for *current version* * retrieve all existing versions of the "same family" (3.0.xx) for *org.apache.maven:maven-distribution:3.0.xx* * let user supply a version to up / down grade to * calculate ** runtime scoped classpath for "current" pom.xml ** runtime scoped classpath for selected version's pom.xml ** retrieve the binary diff to local repo * make ./lib reflect the "new" runtime classpath ** remove replaced binaries ** copy in missing binaries > Design > -- > > Key: MNG-3967 > URL: http://jira.codehaus.org/browse/MNG-3967 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > > First deliverable shall > * be designed as part of a more complex provisioning system > ** provide APIs to be later used by that system > * implement *Delta Management* requirements from [MNG-3966] > When started with a pointer to a maven instance, it shall: > * find *maven-distribution-xx.jar* in ./lib to use for *current version* > * retrieve all existing versions of the "same family" (a'la 3.0.xx) for > *org.apache.maven:maven-distribution:3.0.xx* > * let user supply a version to up / down grade to > * calculate > ** runtime scoped classpath for "current" pom.xml > ** runtime scoped classpath for selected version's pom.xml > ** retrieve the binary diff to local repo > * make ./lib reflect the "new" runtime classpath > ** remove replaced binaries > ** copy in missing binaries -- 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-3960) cannot build projects which use plexus-maven-plugin with 3.0-alpha-1
[
http://jira.codehaus.org/browse/MNG-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160040#action_160040
]
Jason van Zyl commented on MNG-3960:
This is result of cleaning out some code in Plexus, no one has ever implemented
the Suspendable interface but it won't hurt to restore them and then this
problem will go away.
> cannot build projects which use plexus-maven-plugin with 3.0-alpha-1
>
>
> Key: MNG-3960
> URL: http://jira.codehaus.org/browse/MNG-3960
> Project: Maven 2
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.0-alpha-1
>Reporter: Olivier Lamy
>Assignee: Jason van Zyl
> Fix For: 3.0-alpha-2
>
>
> When building projects with mvn 3.0-alpha-1 which plexus-maven-plugin
> (release project in mvn svn, some plugins maven-changes-plugin, continuum,
> archiva), I have the following exception (java.lang.ClassNotFoundException) :
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError
> at
> org.codehaus.plexus.cdc.gleaner.QDoxComponentGleaner.class$(QDoxComponentGleaner.java:231)
> at
> org.codehaus.plexus.cdc.gleaner.QDoxComponentGleaner.(QDoxComponentGleaner.java:230)
> at
> org.codehaus.plexus.maven.plugin.SourceComponentDescriptorExtractor.extract(SourceComponentDescriptorExtractor.java:57)
> at
> org.codehaus.plexus.maven.plugin.AbstractDescriptorMojo.generateDescriptor(AbstractDescriptorMojo.java:131)
> at
> org.codehaus.plexus.maven.plugin.PlexusDescriptorMojo.execute(PlexusDescriptorMojo.java:60)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:631)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:492)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:259)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:201)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:164)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:207)
> at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:846)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
> 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
> Caused by: java.lang.ClassNotFoundException:
> org.codehaus.plexus.personality.plexus.lifecycle.phase.Suspendable
> at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> 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.strategy.ForeignStrategy.loadClass(ForeignStrategy.java:39)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:207)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
> at
> org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:73)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:207)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:164)
> ... 22 more
> {code}
--
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 in
[jira] Updated: (MNG-3967) Design
[ http://jira.codehaus.org/browse/MNG-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3967: -- Description: First deliverable shall * be designed as part of a more complex provisioning system ** provide APIs to be later used by that system * implement *Delta Management* requirements from [MNG-3966] When started with a pointer to a maven instance, it shall: * find *maven-distribution-xx.jar* in ./lib to use for *current version* * retrieve all existing versions of the "same family" (3.0.xx) for *org.apache.maven:maven-distribution:3.0.xx* * let user supply a version to up / down grade to * calculate ** runtime scoped classpath for "current" pom.xml ** runtime scoped classpath for selected version's pom.xml ** retrieve the binary diff to local repo * make ./lib reflect the "new" runtime classpath ** remove replaced binaries ** copy in missing binaries was: First deliverable shall * be designed as part of a more complex provisioning system ** provide APIs to be later used by that system * implement *Delta Management" requirements from [MNG-3966] When started with a pointer to a maven instance, it shall: * find *maven-distribution-xx.jar* in ./lib to use for *current version* * retrieve all existing versions of the "same family" (3.0.xx) for *org.apache.maven:maven-distribution:3.0.xx* * let user supply a version to up / down grade to * calculate ** runtime scoped classpath for "current" pom.xml ** runtime scoped classpath for selected version's pom.xml ** retrieve the binary diff to local repo * make ./lib reflect the "new" runtime classpath ** remove replaced binaries ** copy in missing binaries > Design > -- > > Key: MNG-3967 > URL: http://jira.codehaus.org/browse/MNG-3967 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > > First deliverable shall > * be designed as part of a more complex provisioning system > ** provide APIs to be later used by that system > * implement *Delta Management* requirements from [MNG-3966] > When started with a pointer to a maven instance, it shall: > * find *maven-distribution-xx.jar* in ./lib to use for *current version* > * retrieve all existing versions of the "same family" (3.0.xx) for > *org.apache.maven:maven-distribution:3.0.xx* > * let user supply a version to up / down grade to > * calculate > ** runtime scoped classpath for "current" pom.xml > ** runtime scoped classpath for selected version's pom.xml > ** retrieve the binary diff to local repo > * make ./lib reflect the "new" runtime classpath > ** remove replaced binaries > ** copy in missing binaries -- 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-3967) Design
[ http://jira.codehaus.org/browse/MNG-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3967: -- Description: First deliverable shall * be designed as part of a more complex provisioning system ** provide APIs to be later used by that system * implement *Delta Management* requirements from [MNG-3966] When started with a pointer to a maven instance, it shall: * find *maven-distribution-xx.jar* in ./lib to use for *current version* * retrieve all existing versions of the "same family" (a'la 3.0.xx) for *org.apache.maven:maven-distribution:3.0.xx* * let user supply a version to up / down grade to * calculate, using Mercury APIs ** runtime scoped classpath for "current" pom.xml ** runtime scoped classpath for selected version's pom.xml ** retrieve the binary diff to local repo * make ./lib reflect the "new" runtime classpath ** remove replaced binaries ** copy in missing binaries was: First deliverable shall * be designed as part of a more complex provisioning system ** provide APIs to be later used by that system * implement *Delta Management* requirements from [MNG-3966] When started with a pointer to a maven instance, it shall: * find *maven-distribution-xx.jar* in ./lib to use for *current version* * retrieve all existing versions of the "same family" (a'la 3.0.xx) for *org.apache.maven:maven-distribution:3.0.xx* * let user supply a version to up / down grade to * calculate ** runtime scoped classpath for "current" pom.xml ** runtime scoped classpath for selected version's pom.xml ** retrieve the binary diff to local repo * make ./lib reflect the "new" runtime classpath ** remove replaced binaries ** copy in missing binaries > Design > -- > > Key: MNG-3967 > URL: http://jira.codehaus.org/browse/MNG-3967 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > > First deliverable shall > * be designed as part of a more complex provisioning system > ** provide APIs to be later used by that system > * implement *Delta Management* requirements from [MNG-3966] > When started with a pointer to a maven instance, it shall: > * find *maven-distribution-xx.jar* in ./lib to use for *current version* > * retrieve all existing versions of the "same family" (a'la 3.0.xx) for > *org.apache.maven:maven-distribution:3.0.xx* > * let user supply a version to up / down grade to > * calculate, using Mercury APIs > ** runtime scoped classpath for "current" pom.xml > ** runtime scoped classpath for selected version's pom.xml > ** retrieve the binary diff to local repo > * make ./lib reflect the "new" runtime classpath > ** remove replaced binaries > ** copy in missing binaries -- 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: (MNG-3968) Implement APIs
Implement APIs -- Key: MNG-3968 URL: http://jira.codehaus.org/browse/MNG-3968 Project: Maven 2 Issue Type: Sub-task Components: Artifacts and Repositories Affects Versions: 3.0-alpha-1 Reporter: Oleg Gusakov -- 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: (MNG-3969) replace maven-ant with mercury-ant in the bootstrap
replace maven-ant with mercury-ant in the bootstrap --- Key: MNG-3969 URL: http://jira.codehaus.org/browse/MNG-3969 Project: Maven 2 Issue Type: Improvement Components: Bootstrap & Build Affects Versions: 3.0-alpha-1 Reporter: Oleg Gusakov Fix For: 3.0-alpha-2 -- 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-3969) replace maven-ant with mercury-ant in the bootstrap
[ http://jira.codehaus.org/browse/MNG-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3969: -- Fix Version/s: 3.0-alpha-2 > replace maven-ant with mercury-ant in the bootstrap > --- > > Key: MNG-3969 > URL: http://jira.codehaus.org/browse/MNG-3969 > Project: Maven 2 > Issue Type: Improvement > Components: Bootstrap & Build >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov > Fix For: 3.0-alpha-2 > > -- 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-3968) Implement APIs
[ http://jira.codehaus.org/browse/MNG-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3968: -- Assignee: Oleg Gusakov Fix Version/s: 3.0-alpha-2 > Implement APIs > -- > > Key: MNG-3968 > URL: http://jira.codehaus.org/browse/MNG-3968 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > -- 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-3966) Requirements (User Story)
[ http://jira.codehaus.org/browse/MNG-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3966: -- Fix Version/s: 3.0-alpha-2 > Requirements (User Story) > - > > Key: MNG-3966 > URL: http://jira.codehaus.org/browse/MNG-3966 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > > *Delta Manager* story: > * standalone library > * CLI wrapper > * is run for a particular maven instance on disk > ** lists all the available "compatible" versions (like 3.0.* family) > ** allows to up / down grade current instance to any of available > "compatible" version > ** works on binaries only ( the ./lib folder), all other files presumed > installed and compatible > *Installer* story: > * standalone library > * CLI wrapper > * maintains a set of "maven distributions" on user disk > * allows user to > ** list local "installed" distributions (inventory function) > ** list available remote distributions > ** install a version > ** remove a version > ** switch > First deliverable shall provide *Delta Manager* implementation -- 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-3968) Deployment Descriptor
[ http://jira.codehaus.org/browse/MNG-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3968: -- Summary: Deployment Descriptor (was: Implement APIs) Implement Modello-based POC descriptor. Include provisions for future inclusion into provisioning system > Deployment Descriptor > - > > Key: MNG-3968 > URL: http://jira.codehaus.org/browse/MNG-3968 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > -- 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
