[jira] Created: (MEV-626) Missing POM for Apache "neethi"
Missing POM for Apache "neethi"
---
Key: MEV-626
URL: http://jira.codehaus.org/browse/MEV-626
Project: Maven Evangelism
Issue Type: Bug
Components: Invalid POM
Reporter: Trevor L. Torrez
Seems this was opened (and rejected) under the maven-upload project
(MAVENUPLOAD-1823). The lack of a POM was, however, causing our build to fail
in certain situations; I'm not sure what situations, but it has something to do
with it being either a transitive dependency or a direct dependency.
This also affects version 2.0.1; curiously 2.0.3 and 2.0.4 don't have a
{{maven-metadata.xml}} file, but I don't know if that would also cause problems.
--
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-3017) Profile activation by file fails when maven is run outside the pom's directory
[ http://jira.codehaus.org/browse/MNG-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177514#action_177514 ] Trevor L. Torrez commented on MNG-3017: --- I added another vote. I'm using maven 2.0.9; when a child project has a profile activated by a missing file, the profile is always active when run from the parent folder because the file is never created in the parent folder. > Profile activation by file fails when maven is run outside the pom's directory > -- > > Key: MNG-3017 > URL: http://jira.codehaus.org/browse/MNG-3017 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 2.0.6 > Environment: Darwin Kernel Version 8.9.1 > java version "1.6.0-dp" > Java(TM) SE Runtime Environment (build 1.6.0-dp-b88-34) > Java HotSpot(TM) Client VM (build 1.6.0-b88-17-release, mixed mode, sharing) >Reporter: Jean-Luc Wasmer > Fix For: 2.2.x > > Attachments: maven-test.tgz > > > When calling maven outside the pom's directory, the profile activation fails: > macb:~/Development/maven-test/parent jl$ mvn install > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] Example parent > [INFO] Example module1 > [INFO] Example module2 > [INFO] > > > macb:~/Development/maven-test jl$ mvn -f parent/pom.xml install > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] Example parent > [INFO] Example module1 > [INFO] > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-302) mvn install site-deploy does not follow the reactor build sequence
[ http://jira.codehaus.org/browse/MSITE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142791#action_142791 ] Trevor L. Torrez commented on MSITE-302: Thanks :) Setting the version of the javadoc plugin to 2.4 in the parent pom reporting section (and deleting "false" from all poms) works, even without specifying the version of the site plugin. I could not however just specify the version in the pluginManagement section of the parent pom. Is this a bug or is it supposed to be that way? How does the site plugin know what version of the javadoc plugin to use? > mvn install site-deploy does not follow the reactor build sequence > -- > > Key: MSITE-302 > URL: http://jira.codehaus.org/browse/MSITE-302 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: Ramon Havermans > Attachments: msite302-maven-logs.zip, msite302.zip, > OvereenkomstService_site-OvereenkomstService_site.1006-build.log > > > We have a multi pom project. We have one parent, one EJB and one Impl > project. The EJB project uses the Impl. The reactor sequence is Parent, EJB, > Impl. When first doing "mvn install" and then "mvn site-deploy" the build is > succesful. When doing "mvn install site-deploy" (on clean repository) the > build fails because it first builds the Ejb instead of the Impl. It won't > build because it is missing the installed Impl 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: (MSITE-302) mvn install site-deploy does not follow the reactor build sequence
[ http://jira.codehaus.org/browse/MSITE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor L. Torrez updated MSITE-302: --- Attachment: msite302-maven-logs.zip I added "maven-site-plugin2.0-beta-7" to the pluginManagement section; separate invocations work, single invocation still fails. Attached are the results (mvn -X ...) > mvn install site-deploy does not follow the reactor build sequence > -- > > Key: MSITE-302 > URL: http://jira.codehaus.org/browse/MSITE-302 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: Ramon Havermans > Attachments: msite302-maven-logs.zip, msite302.zip, > OvereenkomstService_site-OvereenkomstService_site.1006-build.log > > > We have a multi pom project. We have one parent, one EJB and one Impl > project. The EJB project uses the Impl. The reactor sequence is Parent, EJB, > Impl. When first doing "mvn install" and then "mvn site-deploy" the build is > succesful. When doing "mvn install site-deploy" (on clean repository) the > build fails because it first builds the Ejb instead of the Impl. It won't > build because it is missing the installed Impl 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: (MSITE-302) mvn install site-deploy does not follow the reactor build sequence
[ http://jira.codehaus.org/browse/MSITE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor L. Torrez updated MSITE-302: --- Attachment: msite302.zip I managed to replicate this using maven 2.0.9; build succeeds with "mvn clean install; mvn site site-deploy" but fails with "mvn clean install site-deploy" due to missing artifact (the upstream project in the reactor). be sure to "rm -rf $M2_REPO/info/beltorak/example/maven/msite302" before each run > mvn install site-deploy does not follow the reactor build sequence > -- > > Key: MSITE-302 > URL: http://jira.codehaus.org/browse/MSITE-302 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: Ramon Havermans > Attachments: msite302.zip, > OvereenkomstService_site-OvereenkomstService_site.1006-build.log > > > We have a multi pom project. We have one parent, one EJB and one Impl > project. The EJB project uses the Impl. The reactor sequence is Parent, EJB, > Impl. When first doing "mvn install" and then "mvn site-deploy" the build is > succesful. When doing "mvn install site-deploy" (on clean repository) the > build fails because it first builds the Ejb instead of the Impl. It won't > build because it is missing the installed Impl 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] Created: (MEV-586) Maven 1.x POM in repository for flatpack - specifies pomVersion 3
Maven 1.x POM in repository for flatpack - specifies pomVersion 3 - Key: MEV-586 URL: http://jira.codehaus.org/browse/MEV-586 Project: Maven Evangelism Issue Type: Bug Components: Invalid POM Reporter: Trevor L. Torrez "flatpack" is a maven 1.x project. The pom in the maven2 repository specifies pomVersion as 3 instead of 4.0.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
