[jira] Commented: (MRELEASE-628) Subversion --trust-server-cert option
[ http://jira.codehaus.org/browse/MRELEASE-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260858#action_260858 ] Dominik Bartholdi commented on MRELEASE-628: is the solution some how documented? how can I pass this option to subversion? > Subversion --trust-server-cert option > - > > Key: MRELEASE-628 > URL: http://jira.codehaus.org/browse/MRELEASE-628 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: perform, prepare >Affects Versions: 2.1 >Reporter: John Turner >Assignee: Olivier Lamy > Fix For: 2.2 > > > It would be useful to be able to pass the --trust-server-cert option to the > svn command. -- 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: (MJAVADOC-313) unable to generate java docs along with docCheck docs for a project, i am getting only doccheck reports
[ http://jira.codehaus.org/browse/MJAVADOC-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260860#action_260860 ] MOHAN RAO CHALLAGONDA commented on MJAVADOC-313: Can any one help on this > unable to generate java docs along with docCheck docs for a project, i am > getting only doccheck reports > > > Key: MJAVADOC-313 > URL: http://jira.codehaus.org/browse/MJAVADOC-313 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.7 > Environment: windows xp,maven 2 and jdk 1.5 >Reporter: MOHAN RAO CHALLAGONDA > > In My project i need check the javadoc commments missing and also generate > javadoc for sroucre i.e. i need docCheck reports and javadoc reports but i am > getting only doccheck Reports. > Here is i am my pom.xml piece of code. > > > > org.apache.maven.plugins > maven-javadoc-plugin > 2.7 > > > com.sun.tools.doclets.doccheck.DocCheck > > > com.sun.tools.doclets > > doccheck > 1.2b2 > > doccheck > -d > . > DocCheck > DocCheck > documentation. > > false > > > > -- 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-5045) SnapshotTransformation class missing in maven 3.0.* series
SnapshotTransformation class missing in maven 3.0.* series -- Key: MNG-5045 URL: http://jira.codehaus.org/browse/MNG-5045 Project: Maven 2 & 3 Issue Type: Bug Components: Bootstrap & Build, Class Loading, Dependencies, Errors Affects Versions: 3.0.3, 3.0.2, 3.0.1 Environment: Linux (Ubuntu) most likely all platforms Reporter: bryan hunt Priority: Blocker The class org/apache/maven/artifact/transform/SnapshotTransformation was originally (apache-maven-2.2.1) bundled in maven-2.2.1-uber.jar However this is now missing from maven 3.0.* releases. As a result, one of the flex-mojo's sonatype project goals breaks when run under maven 3.0.* series. The bug report is here. https://issues.sonatype.org/browse/FLEXMOJOS-397 It's been marked as Fixed as the developer is adamant that API compatability is supposed to be maintained between Maven 2 and 3 series but is very much still active. There are no more releases planned in that series but it is depended upon by many developers. Best Regards, Bryan Hunt -- 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: (MRELEASE-628) Subversion --trust-server-cert option
[ http://jira.codehaus.org/browse/MRELEASE-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260869#action_260869 ] Olivier Lamy commented on MRELEASE-628: --- the file ~/.scm/svn-settings.xml will have a xml element useAuthCache (default value will false). it's not yet released and will be available in scm 1.5 > Subversion --trust-server-cert option > - > > Key: MRELEASE-628 > URL: http://jira.codehaus.org/browse/MRELEASE-628 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: perform, prepare >Affects Versions: 2.1 >Reporter: John Turner >Assignee: Olivier Lamy > Fix For: 2.2 > > > It would be useful to be able to pass the --trust-server-cert option to the > svn command. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-88) Wrong homepage link in project-summary.html when processing staging
[ http://jira.codehaus.org/browse/MPIR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260893#action_260893 ] Lukas Theussl commented on MPIR-88: --- This seems fixed with site-plugin-2.3. > Wrong homepage link in project-summary.html when processing staging > --- > > Key: MPIR-88 > URL: http://jira.codehaus.org/browse/MPIR-88 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: summary >Affects Versions: 2.1 >Reporter: Vincent Siveton > Attachments: maven-plugin-plugin-2.4.PNG > > > See the screenshot > http://maven.apache.org/plugin-tools/maven-plugin-tools-api/project-summary.html > http://maven.apache.org/plugin-tools/maven-plugin-tools-api-2.4/project-summary.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] Created: (MAVENUPLOAD-2814) Please upload umlgraph-5.4.
Please upload umlgraph-5.4. --- Key: MAVENUPLOAD-2814 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2814 Project: Maven Upload Requests Issue Type: Wish Reporter: Christian Schulte Attachments: doclet-5.4-bundle.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: (MNG-5046) Remove $Id$ from sources
Remove $Id$ from sources
Key: MNG-5046
URL: http://jira.codehaus.org/browse/MNG-5046
Project: Maven 2 & 3
Issue Type: Task
Components: General
Affects Versions: 3.0.3
Reporter: Jesse Glick
Priority: Minor
Attachments: no-id.diff
The use of {{$Id$}} in Maven sources causes a checkout of the Git mirror to
always appear modified to {{org.eclipse.jgit-0.11.3}}, which is an annoyance.
Since there is no particular reason to use {{@version}} when source artifacts
are strictly versioned anyway, it would be better to just remove these.
Attaching patch against current Subversion trunk which removes all occurrences
of {{$Id$}} and one {{$Revision}}. ({{target/generated-sources/modello}}
contains {{$Revision$ $Date$}} but this should not matter.)
--
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-5047) Child of child without scm causes NPE
Child of child without scm causes NPE - Key: MNG-5047 URL: http://jira.codehaus.org/browse/MNG-5047 Project: Maven 2 & 3 Issue Type: Bug Components: Inheritance and Interpolation Affects Versions: 3.0 Environment: mvn -v Apache Maven 3.0-alpha-7 (r921173; 2010-03-09 22:31:07+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_GB, platform encoding: UTF-8 OS name: "linux" version: "2.6.32-30-generic" arch: "amd64" Family: "unix" Reporter: Tim Pizey Priority: Minor Attachments: debug.log A grandchild pom, ie a pom with a parent with a parent throws an NPE. The NPE seems to be due to an assumption that the SCM will be 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] Commented: (MNG-5047) Child of child without scm causes NPE
[ http://jira.codehaus.org/browse/MNG-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260906#action_260906 ] Tim Pizey commented on MNG-5047: I added an scm element and got an error which told me I am not allowed to do what I want to do: [ERROR] Invalid packaging for parent POM org.atombeat:atombeat-integration-tests:0.2-alpha-10-SNAPSHOT, must be "pom" but is "jar" @ org.atombeat:atombeat-integration-tests:0.2-alpha-10-SNAPSHOT I would have expected to be able to extend a "jar" pom, so as to override a property for example. > Child of child without scm causes NPE > - > > Key: MNG-5047 > URL: http://jira.codehaus.org/browse/MNG-5047 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 3.0 > Environment: mvn -v > Apache Maven 3.0-alpha-7 (r921173; 2010-03-09 22:31:07+) > Java version: 1.6.0_24 > Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "linux" version: "2.6.32-30-generic" arch: "amd64" Family: "unix" >Reporter: Tim Pizey >Priority: Minor > Attachments: debug.log > > > A grandchild pom, ie a pom with a parent with a parent throws an NPE. > The NPE seems to be due to an assumption that the SCM will be 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] Closed: (MNG-5047) Child of child without scm causes NPE
[ http://jira.codehaus.org/browse/MNG-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-5047. -- Resolution: Incomplete Assignee: Benjamin Bentmann Looking at the stack trace, the error is likely fixed since Maven 3.0-beta-1, but without an example project not verfifyable. That said, you do realize that the latest release version of Maven 3.x is 3.0.3? > Child of child without scm causes NPE > - > > Key: MNG-5047 > URL: http://jira.codehaus.org/browse/MNG-5047 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 3.0 > Environment: mvn -v > Apache Maven 3.0-alpha-7 (r921173; 2010-03-09 22:31:07+) > Java version: 1.6.0_24 > Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "linux" version: "2.6.32-30-generic" arch: "amd64" Family: "unix" >Reporter: Tim Pizey >Assignee: Benjamin Bentmann >Priority: Minor > Attachments: debug.log > > > A grandchild pom, ie a pom with a parent with a parent throws an NPE. > The NPE seems to be due to an assumption that the SCM will be 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: (MSITE-571) "Testcase" for maven-site-plugin 3.0-beta-3
"Testcase" for maven-site-plugin 3.0-beta-3 --- Key: MSITE-571 URL: http://jira.codehaus.org/browse/MSITE-571 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: site:deploy, site:stage(-deploy) Affects Versions: 3.0-beta-3 Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200) Java version: 1.6.0_20 Java home: /usr/local/jdk1.6.0_20/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux" version: "2.6.38-6-generic" arch: "amd64" Family: "unix" Reporter: Jörg Hohwiller Attachments: site-testcase.zip I created a simple maven project that exposes some bugs in maven-site-plugin. I wanted to reproduce more of them but my time was running out and since the test-case is now untouched for about a month I decided to better contribute it now. Hopefully this makes it easy for developers of site plugin and according ecosystem to reproduce and fix things quickly. Just extract the attached ZIP and invoke "mvn site:stage" using maven 3.0. If you open the result in target/stating, you will see a bullet list describing the actual problems. I suppose this issue is sort of a duplicate to existing individual issues. Proceed as you prefer with it. If these issues are going to be fixed, I will find more time and motivation to provide more test-cases to reproduce bugs as I still have many more of them in my actual project :) -- 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-571) "Testcase" for maven-site-plugin 3.0-beta-3
[ http://jira.codehaus.org/browse/MSITE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-571: -- Description: I created a simple maven project that exposes some bugs in maven-site-plugin. I wanted to reproduce more of them but my time was running out and since the test-case is now untouched for about a month I decided to better contribute it now. Hopefully this makes it easy for developers of site plugin and according ecosystem to reproduce and fix things quickly. Just extract the attached ZIP and invoke "mvn site:stage" using maven 3.0. If you open the result in target/stating, you will see a bullet list describing the actual problems: * The menu "General Information" is duplicated in child modules * The logic that makes the paths relative is buggy as you can see by the top-left logo (if present, go to a child module of a child module). * During the build I get this error: java.util.zip.ZipException: error in opening zip file * During the build surefire reports this even though jxr is active: Unable to locate Test Source XRef to link to - DISABLED * If no distributionManagement is present, mvn site:stage fails. Why? If it is present, then in target staging wired subfolders are created - what for? See MSITE-132 I suppose this issue is sort of a duplicate to existing individual issues. Proceed as you prefer with it. If these issues are going to be fixed, I will find more time and motivation to provide more test-cases to reproduce bugs as I still have many more of them in my actual project :) was: I created a simple maven project that exposes some bugs in maven-site-plugin. I wanted to reproduce more of them but my time was running out and since the test-case is now untouched for about a month I decided to better contribute it now. Hopefully this makes it easy for developers of site plugin and according ecosystem to reproduce and fix things quickly. Just extract the attached ZIP and invoke "mvn site:stage" using maven 3.0. If you open the result in target/stating, you will see a bullet list describing the actual problems. I suppose this issue is sort of a duplicate to existing individual issues. Proceed as you prefer with it. If these issues are going to be fixed, I will find more time and motivation to provide more test-cases to reproduce bugs as I still have many more of them in my actual project :) > "Testcase" for maven-site-plugin 3.0-beta-3 > --- > > Key: MSITE-571 > URL: http://jira.codehaus.org/browse/MSITE-571 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site:deploy, site:stage(-deploy) >Affects Versions: 3.0-beta-3 > Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200) > Java version: 1.6.0_20 > Java home: /usr/local/jdk1.6.0_20/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.38-6-generic" arch: "amd64" Family: "unix" >Reporter: Jörg Hohwiller > Attachments: site-testcase.zip > > > I created a simple maven project that exposes some bugs in maven-site-plugin. > I wanted to reproduce more of them but my time was running out and since the > test-case is now untouched for about a month I decided to better contribute > it now. > Hopefully this makes it easy for developers of site plugin and according > ecosystem to reproduce and fix things quickly. > Just extract the attached ZIP and invoke "mvn site:stage" using maven 3.0. If > you open the result in target/stating, you will see a bullet list describing > the actual problems: > * The menu "General Information" is duplicated in child modules > * The logic that makes the paths relative is buggy as you can see by the > top-left logo (if present, go to a child module of a child module). > * During the build I get this error: java.util.zip.ZipException: error in > opening zip file > * During the build surefire reports this even though jxr is active: Unable to > locate Test Source XRef to link to - DISABLED > * If no distributionManagement is present, mvn site:stage fails. Why? If it > is present, then in target staging wired subfolders are created - what for? > See MSITE-132 > I suppose this issue is sort of a duplicate to existing individual issues. > Proceed as you prefer with it. > If these issues are going to be fixed, I will find more time and motivation > to provide more test-cases to reproduce bugs as I still have many more of > them in my actual project :) -- 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-571) "Testcase" for maven-site-plugin 3.0-beta-3
[ http://jira.codehaus.org/browse/MSITE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260926#action_260926 ] Dennis Lundberg commented on MSITE-571: --- The duplicated menu is tracked in MSITE-519. The left banner logo link is tracked in MSITE-273 and has been fixed in 3.0-beta-4-SNAPSHOT. ZipException has to do with the Dependency Report in Maven Project Info Reports Plugin. Please open an issue for that in the MPIR JIRA project. The warning from the Surefire Report Plugin might be because there is no test source to generate the JXR for. The distribution management requirement has been fixed in 3.0-beta-4-SNAPSHOT. > "Testcase" for maven-site-plugin 3.0-beta-3 > --- > > Key: MSITE-571 > URL: http://jira.codehaus.org/browse/MSITE-571 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site:deploy, site:stage(-deploy) >Affects Versions: 3.0-beta-3 > Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200) > Java version: 1.6.0_20 > Java home: /usr/local/jdk1.6.0_20/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.38-6-generic" arch: "amd64" Family: "unix" >Reporter: Jörg Hohwiller > Attachments: site-testcase.zip > > > I created a simple maven project that exposes some bugs in maven-site-plugin. > I wanted to reproduce more of them but my time was running out and since the > test-case is now untouched for about a month I decided to better contribute > it now. > Hopefully this makes it easy for developers of site plugin and according > ecosystem to reproduce and fix things quickly. > Just extract the attached ZIP and invoke "mvn site:stage" using maven 3.0. If > you open the result in target/stating, you will see a bullet list describing > the actual problems: > * The menu "General Information" is duplicated in child modules > * The logic that makes the paths relative is buggy as you can see by the > top-left logo (if present, go to a child module of a child module). > * During the build I get this error: java.util.zip.ZipException: error in > opening zip file > * During the build surefire reports this even though jxr is active: Unable to > locate Test Source XRef to link to - DISABLED > * If no distributionManagement is present, mvn site:stage fails. Why? If it > is present, then in target staging wired subfolders are created - what for? > See MSITE-132 > I suppose this issue is sort of a duplicate to existing individual issues. > Proceed as you prefer with it. > If these issues are going to be fixed, I will find more time and motivation > to provide more test-cases to reproduce bugs as I still have many more of > them in my actual project :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MSITE-571) "Testcase" for maven-site-plugin 3.0-beta-3
[ http://jira.codehaus.org/browse/MSITE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260926#action_260926 ] Dennis Lundberg edited comment on MSITE-571 at 3/21/11 4:24 PM: The duplicated menu is tracked in MSITE-519. The left banner logo link is tracked in MSITE-273 and has been fixed in 3.0-beta-4-SNAPSHOT. ZipException has to do with the Dependency Report in Maven Project Info Reports Plugin. Please open an issue for that in the MPIR JIRA project. The warning from the Surefire Report Plugin might be because there is no test source to generate the JXR for. The distribution management is still a requirement. It is used as a default value for the staging directory tree. was (Author: dennislundberg): The duplicated menu is tracked in MSITE-519. The left banner logo link is tracked in MSITE-273 and has been fixed in 3.0-beta-4-SNAPSHOT. ZipException has to do with the Dependency Report in Maven Project Info Reports Plugin. Please open an issue for that in the MPIR JIRA project. The warning from the Surefire Report Plugin might be because there is no test source to generate the JXR for. The distribution management is still requirement. > "Testcase" for maven-site-plugin 3.0-beta-3 > --- > > Key: MSITE-571 > URL: http://jira.codehaus.org/browse/MSITE-571 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site:deploy, site:stage(-deploy) >Affects Versions: 3.0-beta-3 > Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200) > Java version: 1.6.0_20 > Java home: /usr/local/jdk1.6.0_20/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.38-6-generic" arch: "amd64" Family: "unix" >Reporter: Jörg Hohwiller > Attachments: site-testcase.zip > > > I created a simple maven project that exposes some bugs in maven-site-plugin. > I wanted to reproduce more of them but my time was running out and since the > test-case is now untouched for about a month I decided to better contribute > it now. > Hopefully this makes it easy for developers of site plugin and according > ecosystem to reproduce and fix things quickly. > Just extract the attached ZIP and invoke "mvn site:stage" using maven 3.0. If > you open the result in target/stating, you will see a bullet list describing > the actual problems: > * The menu "General Information" is duplicated in child modules > * The logic that makes the paths relative is buggy as you can see by the > top-left logo (if present, go to a child module of a child module). > * During the build I get this error: java.util.zip.ZipException: error in > opening zip file > * During the build surefire reports this even though jxr is active: Unable to > locate Test Source XRef to link to - DISABLED > * If no distributionManagement is present, mvn site:stage fails. Why? If it > is present, then in target staging wired subfolders are created - what for? > See MSITE-132 > I suppose this issue is sort of a duplicate to existing individual issues. > Proceed as you prefer with it. > If these issues are going to be fixed, I will find more time and motivation > to provide more test-cases to reproduce bugs as I still have many more of > them in my actual project :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MSITE-571) "Testcase" for maven-site-plugin 3.0-beta-3
[ http://jira.codehaus.org/browse/MSITE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260926#action_260926 ] Dennis Lundberg edited comment on MSITE-571 at 3/21/11 4:22 PM: The duplicated menu is tracked in MSITE-519. The left banner logo link is tracked in MSITE-273 and has been fixed in 3.0-beta-4-SNAPSHOT. ZipException has to do with the Dependency Report in Maven Project Info Reports Plugin. Please open an issue for that in the MPIR JIRA project. The warning from the Surefire Report Plugin might be because there is no test source to generate the JXR for. The distribution management is still requirement. was (Author: dennislundberg): The duplicated menu is tracked in MSITE-519. The left banner logo link is tracked in MSITE-273 and has been fixed in 3.0-beta-4-SNAPSHOT. ZipException has to do with the Dependency Report in Maven Project Info Reports Plugin. Please open an issue for that in the MPIR JIRA project. The warning from the Surefire Report Plugin might be because there is no test source to generate the JXR for. The distribution management requirement has been fixed in 3.0-beta-4-SNAPSHOT. > "Testcase" for maven-site-plugin 3.0-beta-3 > --- > > Key: MSITE-571 > URL: http://jira.codehaus.org/browse/MSITE-571 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site:deploy, site:stage(-deploy) >Affects Versions: 3.0-beta-3 > Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200) > Java version: 1.6.0_20 > Java home: /usr/local/jdk1.6.0_20/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.38-6-generic" arch: "amd64" Family: "unix" >Reporter: Jörg Hohwiller > Attachments: site-testcase.zip > > > I created a simple maven project that exposes some bugs in maven-site-plugin. > I wanted to reproduce more of them but my time was running out and since the > test-case is now untouched for about a month I decided to better contribute > it now. > Hopefully this makes it easy for developers of site plugin and according > ecosystem to reproduce and fix things quickly. > Just extract the attached ZIP and invoke "mvn site:stage" using maven 3.0. If > you open the result in target/stating, you will see a bullet list describing > the actual problems: > * The menu "General Information" is duplicated in child modules > * The logic that makes the paths relative is buggy as you can see by the > top-left logo (if present, go to a child module of a child module). > * During the build I get this error: java.util.zip.ZipException: error in > opening zip file > * During the build surefire reports this even though jxr is active: Unable to > locate Test Source XRef to link to - DISABLED > * If no distributionManagement is present, mvn site:stage fails. Why? If it > is present, then in target staging wired subfolders are created - what for? > See MSITE-132 > I suppose this issue is sort of a duplicate to existing individual issues. > Proceed as you prefer with it. > If these issues are going to be fixed, I will find more time and motivation > to provide more test-cases to reproduce bugs as I still have many more of > them in my actual project :) -- 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-5048) Optionally include "provided" transitive dependencies on classpath
Optionally include "provided" transitive dependencies on classpath -- Key: MNG-5048 URL: http://jira.codehaus.org/browse/MNG-5048 Project: Maven 2 & 3 Issue Type: New Feature Components: Dependencies Affects Versions: 2.2.1 Reporter: Stephen Cresswell Priority: Minor I want to be able to define a large set of common dependencies in a shared pom. The trouble is this only works if the dependencies are compile scope, but not provided scope. For my situation the dependencies are already present in the server lib directory, so I don't want them bundled with the aar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5048) Optionally include "provided" transitive dependencies on classpath
[ http://jira.codehaus.org/browse/MNG-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-5048. -- Resolution: Duplicate Assignee: Benjamin Bentmann > Optionally include "provided" transitive dependencies on classpath > -- > > Key: MNG-5048 > URL: http://jira.codehaus.org/browse/MNG-5048 > Project: Maven 2 & 3 > Issue Type: New Feature > Components: Dependencies >Affects Versions: 2.2.1 >Reporter: Stephen Cresswell >Assignee: Benjamin Bentmann >Priority: Minor > > I want to be able to define a large set of common dependencies in a shared > pom. The trouble is this only works if the dependencies are compile scope, > but not provided scope. For my situation the dependencies are already present > in the server lib directory, so I don't want them bundled with the aar. -- 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-571) "Testcase" for maven-site-plugin 3.0-beta-3
[ http://jira.codehaus.org/browse/MSITE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260931#action_260931 ] Lukas Theussl commented on MSITE-571: - Please test 3.0-beta-4-SNAPSHOT and report back, we will release it soon. In general, such 'all-encompassing' test cases are not very useful as they tend to never get fixed entirely, it's better to create one ticket for each specific issue (you can always link back to the general test case here for illustration). > "Testcase" for maven-site-plugin 3.0-beta-3 > --- > > Key: MSITE-571 > URL: http://jira.codehaus.org/browse/MSITE-571 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site:deploy, site:stage(-deploy) >Affects Versions: 3.0-beta-3 > Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200) > Java version: 1.6.0_20 > Java home: /usr/local/jdk1.6.0_20/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.38-6-generic" arch: "amd64" Family: "unix" >Reporter: Jörg Hohwiller > Attachments: site-testcase.zip > > > I created a simple maven project that exposes some bugs in maven-site-plugin. > I wanted to reproduce more of them but my time was running out and since the > test-case is now untouched for about a month I decided to better contribute > it now. > Hopefully this makes it easy for developers of site plugin and according > ecosystem to reproduce and fix things quickly. > Just extract the attached ZIP and invoke "mvn site:stage" using maven 3.0. If > you open the result in target/stating, you will see a bullet list describing > the actual problems: > * The menu "General Information" is duplicated in child modules > * The logic that makes the paths relative is buggy as you can see by the > top-left logo (if present, go to a child module of a child module). > * During the build I get this error: java.util.zip.ZipException: error in > opening zip file > * During the build surefire reports this even though jxr is active: Unable to > locate Test Source XRef to link to - DISABLED > * If no distributionManagement is present, mvn site:stage fails. Why? If it > is present, then in target staging wired subfolders are created - what for? > See MSITE-132 > I suppose this issue is sort of a duplicate to existing individual issues. > Proceed as you prefer with it. > If these issues are going to be fixed, I will find more time and motivation > to provide more test-cases to reproduce bugs as I still have many more of > them in my actual project :) -- 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: (MJAVADOC-275) Creation of Javadoc attachments fails in multi-module project where modules have never been installed/deployed
[
http://jira.codehaus.org/browse/MJAVADOC-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260932#action_260932
]
John Casey commented on MJAVADOC-275:
-
what about 2.8? can we close this issue now that MJAVADOC-284 is closed? I
haven't seen it, unless you're talking about the case where the javadoc plugin
forks a new build in order to produce javadocs for dependencies...for which
there is a flag to skip that, and I'm assuming MJAVADOC-284 has fixed in a more
permanent way.
> Creation of Javadoc attachments fails in multi-module project where modules
> have never been installed/deployed
> --
>
> Key: MJAVADOC-275
> URL: http://jira.codehaus.org/browse/MJAVADOC-275
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Benjamin Bentmann
>Assignee: John Casey
>Priority: Critical
> Fix For: 2.7
>
> Attachments: MJAVADOC-275.zip
>
>
> Running the commands
> {noformat}
> mvn clean
> mvn verify
> {noformat}
> will fail on the attached demo project with
> {noformat}
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc'
> has not be previously called for the project:
> 'org.apache.maven.its.javadoc:mod-b:jar:0.1'.
> Trying to invoke it...
> [ERROR] MavenInvocationException: Error when invoking Maven, consult the
> invoker log file:
> M:\MJAVADOC\mod-a\target\invoker\maven-javadoc-plugin625147587.txt
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] MavenReportException: Error while creating archive:
> Error when invoking Maven, consult the invoker log file:
> M:\MJAVADOC\mod-a\target\invoker\maven-javadoc-plugin625147587.txt
> {noformat}
> The command {{mvn clean verify}} as usually used during releases will also
> fail, but starts working after repeated invocations.
--
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: (MGPG-34) Allow to define an alternative pomFile when sign (gpg:sign) the project artifact
[ http://jira.codehaus.org/browse/MGPG-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MGPG-34: -- Affects Version/s: (was: 1.2) 1.1 > Allow to define an alternative pomFile when sign (gpg:sign) the project > artifact > > > Key: MGPG-34 > URL: http://jira.codehaus.org/browse/MGPG-34 > Project: Maven 2.x GPG Plugin > Issue Type: Improvement >Affects Versions: 1.1 >Reporter: Laszlo Hordos > Attachments: maven-gpg-plugin.patch > > > This small modification allow to specify an alternative pomFile to sign > instead of the default project file. It's very useful when a custom pom file > has been generated during the build process. I'm using a complex build > configuration for a framework where I need to create custom pom files. I'm > able create a release from my CI and publish it to the central repository the > gpg:sign signs the wrong pom file. -- 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
