[jira] Updated: (CONTINUUM-1427) Ability to choose the build definition for 'Build all projects'
[ http://jira.codehaus.org/browse/CONTINUUM-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak updated CONTINUUM-1427: --- Description: Currently the default build definition is used when the 'Build all projects' button is clicked. It should be possible to choose a different build definition. Show in the 'Group Actions' section, so only group-level build definitions should be shown. Place a drop down list right next to the 'Build all projects' button was:Show in the 'Group Actions' section, so only group-level build definitions should be shown. Affects Version/s: 1.1-beta-2 Component/s: Web interface Summary: Ability to choose the build definition for 'Build all projects' (was: Place a drop down list right next to the 'Build all projects' button) Edited based on the irc conversation that prompted this issue being opened. > Ability to choose the build definition for 'Build all projects' > --- > > Key: CONTINUUM-1427 > URL: http://jira.codehaus.org/browse/CONTINUUM-1427 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.1-beta-2 >Reporter: George Gastaldi > > Currently the default build definition is used when the 'Build all projects' > button is clicked. > It should be possible to choose a different build definition. > Show in the 'Group Actions' section, so only group-level build definitions > should be shown. > Place a drop down list right next to the 'Build all projects' button -- 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: (CONTINUUM-1427) Place a drop down list right next to the 'Build all projects' button
Place a drop down list right next to the 'Build all projects' button Key: CONTINUUM-1427 URL: http://jira.codehaus.org/browse/CONTINUUM-1427 Project: Continuum Issue Type: Improvement Reporter: George Gastaldi Show in the 'Group Actions' section, so only group-level build definitions should be shown. -- 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-2771) Provide a means of loading custom substitute components instead of default Maven components
[ http://jira.codehaus.org/browse/MNG-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106259 ] Jason van Zyl commented on MNG-2771: Ok, I would have to put a container in the path of the default container so that custom components can be loaded. Or make a small change to plexus to allow overriding of existing registered components but this would require the extensions be scoped to the POM for the build at hand. So not terribly difficult but using the m2_home/extensions is the only way right now which preempts any loading of components and is global. > Provide a means of loading custom substitute components instead of default > Maven components > --- > > Key: MNG-2771 > URL: http://jira.codehaus.org/browse/MNG-2771 > Project: Maven 2 > Issue Type: New Feature > Components: General >Affects Versions: 2.0.4 >Reporter: John Casey >Assignee: Kenney Westerhof > Fix For: 2.1-alpha-1 > > > At times, it is necessary to use different mechanisms for resolving > artifacts, building projects, etc. Since Maven is built on component-oriented > technology, it should be possible to substitute the component implementation > used for these tasks. Yet this is currently impossible. > We need a mechanism for specifying, resolving, loading, and using custom > components during the build process. -- 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-3160) IT 126 is failing on trunk and maven-2.0.x branch
[ http://jira.codehaus.org/browse/MNG-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106258 ] Piotr Tabor commented on MNG-3160: -- This bug is caused by not released version of Maven Jar Plugin. The sufficient patch (Connected to MJAR-75) was applied, by Maven Jar Plugin has not been released. It will work with maven-jar-plugin-2.2(-snapshot). If it tests can depend on SNAPSHOT version of plugins to correct the problem you need to add: org.apache.maven.plugins maven-jar-plugin 2.2-SNAPSHOT to core-integration-testing/core-integration-tests/src/test/resources/it0126-testJarDependency/pom.xml > IT 126 is failing on trunk and maven-2.0.x branch > - > > Key: MNG-3160 > URL: http://jira.codehaus.org/browse/MNG-3160 > Project: Maven 2 > Issue Type: Bug > Components: integration tests >Affects Versions: 2.0.8, 2.1-alpha-1 >Reporter: Brett Porter >Priority: Blocker > Fix For: 2.0.x > > > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > Missing: > -- > 1) org.apache.maven.its.it0126:model:test-jar:tests:1.0-SNAPSHOT > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.maven.its.it0126 > -DartifactId=model \ > -Dversion=1.0-SNAPSHOT -Dclassifier=tests -Dpackaging=test-jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file there: > mvn deploy:deploy-file -DgroupId=org.apache.maven.its.it0126 > -DartifactId=model \ > -Dversion=1.0-SNAPSHOT -Dclassifier=tests -Dpackaging=test-jar > -Dfile=/path/to/file \ >-Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.apache.maven.its.it0126:client:jar:1.0-SNAPSHOT > 2) org.apache.maven.its.it0126:model:test-jar:tests:1.0-SNAPSHOT > -- > 1 required artifact is missing. > for artifact: > org.apache.maven.its.it0126:client:jar:1.0-SNAPSHOT > from the specified remote repositories: > central (http://repo1.maven.org/maven2) -- 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: (CONTINUUM-1426) Provide RSS Feeds for build monitoring
[ http://jira.codehaus.org/browse/CONTINUUM-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Gastaldi closed CONTINUUM-1426. -- Resolution: Duplicate Duplicate of CONTINUUM-418 > Provide RSS Feeds for build monitoring > -- > > Key: CONTINUUM-1426 > URL: http://jira.codehaus.org/browse/CONTINUUM-1426 > Project: Continuum > Issue Type: Wish > Components: Notification Subsystem >Reporter: George Gastaldi > > Provide RSS Feeds for build monitoring. User may monitor build activities > without requiring a mail account. -- 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: (CONTINUUM-1426) Provide RSS Feeds for build monitoring
Provide RSS Feeds for build monitoring -- Key: CONTINUUM-1426 URL: http://jira.codehaus.org/browse/CONTINUUM-1426 Project: Continuum Issue Type: Wish Components: Notification Subsystem Reporter: George Gastaldi Provide RSS Feeds for build monitoring. User may monitor build activities without requiring a mail account. -- 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: (CONTINUUM-1425) URL in Company Pom should open in a new Window
URL in Company Pom should open in a new Window -- Key: CONTINUUM-1425 URL: http://jira.codehaus.org/browse/CONTINUUM-1425 Project: Continuum Issue Type: Improvement Components: Web - UI Reporter: George Gastaldi Priority: Trivial The URL provided in the company POM should open in a new browser window. -- 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-2771) Provide a means of loading custom substitute components instead of default Maven components
[ http://jira.codehaus.org/browse/MNG-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106256 ] Jason van Zyl commented on MNG-2771: Only method 1) works and that was the only thing that was planned at the time but using extensions (at first blush) would probably be fine as you want to use them globally across all your builds. > Provide a means of loading custom substitute components instead of default > Maven components > --- > > Key: MNG-2771 > URL: http://jira.codehaus.org/browse/MNG-2771 > Project: Maven 2 > Issue Type: New Feature > Components: General >Affects Versions: 2.0.4 >Reporter: John Casey >Assignee: Kenney Westerhof > Fix For: 2.1-alpha-1 > > > At times, it is necessary to use different mechanisms for resolving > artifacts, building projects, etc. Since Maven is built on component-oriented > technology, it should be possible to substitute the component implementation > used for these tasks. Yet this is currently impossible. > We need a mechanism for specifying, resolving, loading, and using custom > components during the build process. -- 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-2902) long build startup times due to frequent network access for SNAPSHOT resolving
[ http://jira.codehaus.org/browse/MNG-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2902: --- Fix Version/s: (was: 2.1-alpha-1) 2.1-alpha-2 > long build startup times due to frequent network access for SNAPSHOT resolving > -- > > Key: MNG-2902 > URL: http://jira.codehaus.org/browse/MNG-2902 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 2.0.x >Reporter: Jorg Heymans >Assignee: Jason van Zyl >Priority: Blocker > Fix For: 2.1-alpha-2 > > > IRC log: > jorg: is it normal that between 'Scanning for projects' and the first actual > build output it takes about 1 minute ? > [20:45] jvanzyl: jorg > [20:45] jvanzyl: probably network > [20:45] jvanzyl: you have snapshots? > [20:46] jorg: snapshot of what ? > [20:46] jorg: oh in general you mean > [20:46] jvanzyl: in 2.1 i'm trying to scour the code to make sure it never > touches the network if everything is local > [20:46] jvanzyl: it doesn't do that very well right now > [20:46] jvanzyl: yah > [20:46] jorg: well not on external dependencies no ... > [20:47] jvanzyl: yah, we need to track the pull during a sessions which we > don't > [20:47] jorg: our own modules are however all snapshots ... perhaps that's > what it's trying to resolve > [20:47] jvanzyl: can you put that in a jira and i will assign to 2.1-alpha-1 > [20:47] jorg: ok but the behaviour is expected as is .. that's all i wanted > to make sure then > [20:47] jvanzyl: and then assign to me so i don't forget and i will look at it > [20:47] jvanzyl: it shouldn't do that, but obviously it does > [20:47] jorg: shall i paste the full output of -X or just the start ? > [20:47] jvanzyl: it's doing it for each module > [20:48] jvanzyl: just the start is fine > [20:48] jvanzyl: i get the idea > [20:48] jvanzyl: yah, that's really annoying > [20:48] jorg: ok thanks for the feedback jason, i'll create an issue for it > [20:49] jvanzyl: great, thanks > [20:50] jvanzyl: just paste the issue here > [20:50] jvanzyl: and i'll change the fix version and assign it to me > --- BUILD OUTPUT > jorg:~/src/cocoon-trunk jheymans$ mvn clean install -Dmaven.test.skip=true > -Pallblocks -X > + Error stacktraces are turned on. > Maven version: 2.0.6-SNAPSHOT > [DEBUG] Building Maven user-level plugin registry from: > '/Users/jheymans/.m2/plugin-registry.xml' > [DEBUG] Building Maven global-level plugin registry from: > '/Users/jheymans/tools/maven2/conf/plugin-registry.xml' > [INFO] Scanning for projects... > [DEBUG] Searching for parent-POM: org.apache:apache::4 of project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT in relative path: ../pom.xml > [DEBUG] Invalid parent-POM referenced by relative path '../pom.xml' in parent > specification in org.apache.cocoon:cocoon:pom:4-SNAPSHOT: > Specified: org.apache:apache::4 > Found: org.apache.excalibur:excalibur:pom:1 > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache.cocoon:cocoon:pom:4-SNAPSHOT from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: > org.apache
[jira] Closed: (MNG-1992) CLI -D should override properties in settings.xml
[ http://jira.codehaus.org/browse/MNG-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-1992. -- Resolution: Fixed Put the processing of CLI properties (executionProperties) first. > CLI -D should override properties in settings.xml > - > > Key: MNG-1992 > URL: http://jira.codehaus.org/browse/MNG-1992 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.2 > Environment: xp >Reporter: Brian Fox >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > I have a mojo that takes a parameter as an expression, simple boolean. If I > set it to true in my settings.xml, setting it to false with -D doesn't have > any effect. The CLI should have the final say. -- 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-2967) Uber embedder contains wrong manifest
[ http://jira.codehaus.org/browse/MNG-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2967: --- Affects Version/s: (was: 2.1-alpha-1) 2.1.x Fix Version/s: (was: 2.1-alpha-1) 2.1-alpha-2 > Uber embedder contains wrong manifest > - > > Key: MNG-2967 > URL: http://jira.codehaus.org/browse/MNG-2967 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1.x >Reporter: Carlos Sanchez > Fix For: 2.1-alpha-2 > > > Seems that shade puts a manifest from a random jar instead of the one from > the project 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-3181) JDOM artifact filtering is causing problems
JDOM artifact filtering is causing problems --- Key: MNG-3181 URL: http://jira.codehaus.org/browse/MNG-3181 Project: Maven 2 Issue Type: Bug Affects Versions: 2.1.x Reporter: Jason van Zyl Fix For: 2.1-alpha-1 For example in the release plug that requires JDOM which uses Jaxen. We are cutting off resolution of Jaxen so the release plugin fails. Anything that requires Jaxen via JDOM will fail. -- 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-3181) JDOM artifact filtering is causing problems
[ http://jira.codehaus.org/browse/MNG-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3181: --- Fix Version/s: 2.1-alpha-1 > JDOM artifact filtering is causing problems > --- > > Key: MNG-3181 > URL: http://jira.codehaus.org/browse/MNG-3181 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1.x >Reporter: Jason van Zyl > Fix For: 2.1-alpha-1 > > > For example in the release plug that requires JDOM which uses Jaxen. We are > cutting off resolution of Jaxen so the release plugin fails. Anything that > requires Jaxen via JDOM will fail. -- 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-3180) IT0095 is failing
[ http://jira.codehaus.org/browse/MNG-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3180: --- Affects Version/s: (was: 2.1-alpha-1) 2.1.x Fix Version/s: 2.1-alpha-1 > IT0095 is failing > - > > Key: MNG-3180 > URL: http://jira.codehaus.org/browse/MNG-3180 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1.x >Reporter: Jason van Zyl > Fix For: 2.1-alpha-1 > > -- 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-3180) IT0095 is failing
IT0095 is failing - Key: MNG-3180 URL: http://jira.codehaus.org/browse/MNG-3180 Project: Maven 2 Issue Type: Bug Affects Versions: 2.1-alpha-1 Reporter: Jason van Zyl Fix For: 2.1-alpha-1 -- 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: (MECLIPSE-213) more jee support for wtp
[ http://jira.codehaus.org/browse/MECLIPSE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MECLIPSE-213: --- Assignee: Brian Fox Patch Submitted: [Yes] Rich, I applied the patch along with the new files to a branch: http://svn.apache.org/repos/asf/maven/plugins/branches/maven-eclipse-plugin-MECLIPSE-213 Take a look and try out the plugin to make sure everything works as you expect. The code builds and all the tests pass so it looks good so far. > more jee support for wtp > > > Key: MECLIPSE-213 > URL: http://jira.codehaus.org/browse/MECLIPSE-213 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.3 > Environment: linux suse 10.0 eclipse 3.2.1 and wtp 1.5.1 java 1.5.0_8 >Reporter: Richard van Nieuwenhoven >Assignee: Brian Fox > Attachments: maven-eclipse-plugin-2.3-CFC-2007-03-08.patch, > maven-eclipse-plugin-2.3-PATCH-2007-03-08.tgz, > maven-eclipse-plugin-R494407.patch, maven-eclipse-plugin.patch > > > I tried the new release 2.3 of the eclipse plugin and noteted that not alle > of my paches where included. > I re-pached the 2.3 version again this time i made my changes configurable so > they can be turned on and off. > my changes: > - prohibit dupicate entries in the classpath > provided system paths in combination with log4j/commons-logging/xerces > can easely create such problems > - system paths are only included in ears and war when they are inside the > project >bether behavior would be to exclude all system paths because the war and > ear plugin also ignore these > - an application.xml specialy for eclipse-wtp >this makes wtp ears function correctly it includes the eclipse project > modules instead of the maven generated jars > - manifest generation for wtp >wtp needs manifest files, but not the ones maven creates because they have > version names for all modules etc >this generates a wtp manifest that will be in a ons eclipse source > directory that is ignored my maven itself > use the parameters -Declipse.wtpmanifest=true > -Declipse.wtpapplicationxml=true to acivate the patch. > The manifest generator could be combined with the RadManifestWriter in the > future, they are almost the same. > regards, > Ritchie -- 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] Work started: (MRM-438) broken images in the download box on the artifact page
[ http://jira.codehaus.org/browse/MRM-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-438 started by Maria Odea Ching. > broken images in the download box on the artifact page > -- > > Key: MRM-438 > URL: http://jira.codehaus.org/browse/MRM-438 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter >Assignee: Maria Odea Ching > Fix For: 1.0-beta-2 > > > these don't appear to work at all in the latest version - it isn't noticeable > in firefox but in ie you get the big white square with an X in it. -- 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-3158) IT 108 success remains sporadic
[ http://jira.codehaus.org/browse/MNG-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3158: -- Assignee: Brett Porter Description: I get occasionally failures on this due to timing issues. (was: I get occasionaly failures on this due to timing issues.) Fix Version/s: 2.0.x commenting out in the mean time > IT 108 success remains sporadic > --- > > Key: MNG-3158 > URL: http://jira.codehaus.org/browse/MNG-3158 > Project: Maven 2 > Issue Type: Bug > Components: integration tests >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 2.0.x > > > I get occasionally failures on this due to timing issues. -- 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-2938) Build error is ignored at the end of the build
[ http://jira.codehaus.org/browse/MNG-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2938. -- Resolution: Fixed It will now stop, the lifecycle executor exception was not being propagated soon enough. The lifecycle executor should have a public method validate the goals so that we don't want to prin the reactor projects first. The lifecycle executor fires after we show the projects, but it's only inside the lifecycle executor where the phase/goal is validated. Not very helpful. > Build error is ignored at the end of the build > -- > > Key: MNG-2938 > URL: http://jira.codehaus.org/browse/MNG-2938 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.1.x >Reporter: Carlos Sanchez > Fix For: 2.1-alpha-1 > > > On a build error you get "BUILD ERROR" and then "BUILD SUCCESSFUL" > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to construct build plan for: > org.apache.maven.its.it0020:maven-it-it0020:maven-plugin:1.0-SNAPSHOT ( > task-segment: [clean:clean, install, > ... > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Thu Apr 05 16:27:47 PDT 2007 > [INFO] Final Memory: 6M/11M > [INFO] > > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Thu Apr 05 16:27:47 PDT 2007 > [INFO] Final Memory: 6M/11M > [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] Updated: (MNG-3160) IT 126 is failing on trunk and maven-2.0.x branch
[ http://jira.codehaus.org/browse/MNG-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3160: -- Priority: Blocker (was: Major) Fix Version/s: 2.0.x > IT 126 is failing on trunk and maven-2.0.x branch > - > > Key: MNG-3160 > URL: http://jira.codehaus.org/browse/MNG-3160 > Project: Maven 2 > Issue Type: Bug > Components: integration tests >Affects Versions: 2.0.8, 2.1-alpha-1 >Reporter: Brett Porter >Priority: Blocker > Fix For: 2.0.x > > > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > Missing: > -- > 1) org.apache.maven.its.it0126:model:test-jar:tests:1.0-SNAPSHOT > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.maven.its.it0126 > -DartifactId=model \ > -Dversion=1.0-SNAPSHOT -Dclassifier=tests -Dpackaging=test-jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file there: > mvn deploy:deploy-file -DgroupId=org.apache.maven.its.it0126 > -DartifactId=model \ > -Dversion=1.0-SNAPSHOT -Dclassifier=tests -Dpackaging=test-jar > -Dfile=/path/to/file \ >-Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.apache.maven.its.it0126:client:jar:1.0-SNAPSHOT > 2) org.apache.maven.its.it0126:model:test-jar:tests:1.0-SNAPSHOT > -- > 1 required artifact is missing. > for artifact: > org.apache.maven.its.it0126:client:jar:1.0-SNAPSHOT > from the specified remote repositories: > central (http://repo1.maven.org/maven2) -- 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-2871) Subartifact (ejb-client for example) are not reselved as active project artifacts
[ http://jira.codehaus.org/browse/MNG-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2871. -- Resolution: Fixed Patch applied to maven-project and the ITs. > Subartifact (ejb-client for example) are not reselved as active project > artifacts > - > > Key: MNG-2871 > URL: http://jira.codehaus.org/browse/MNG-2871 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4, 2.0.5 > Environment: Not platform dependent >Reporter: Piotr Tabor >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > Attachments: MavenProject.java, > MNG-2871-core-integration-testing-2.diff, > MNG-2871-core-integration-tests.diff, > MNG-2871-maven-project-2.1-SNAPSHOT.diff, MNG-2871-maven-project.diff, > root.tar > > > I have prepared simple project to show the bug. > It contains three artifacts: > |-root > \--- ejb3 > \--- client > Client depends on ejb3 with ejb-client. > The local and remote repository must not contain those artifacts. > When I do "mvn -X compile" (or even integration-tests) on root project I will > get those errors: > ... > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' --> > [DEBUG] (f) filters = [] > [DEBUG] (f) outputDirectory = /home/ptab/m2/bug/root/client/target/classes > [DEBUG] (f) project = [EMAIL PROTECTED] > [DEBUG] (f) resources = [EMAIL PROTECTED] > [DEBUG] -- end configuration -- > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [DEBUG] pl.waw.tabor:client:jar:1.0-SNAPSHOT (selected for null) > [DEBUG] junit:junit:jar:3.8.1:test (selected for test) > [DEBUG] pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT:compile (selected > for compile) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Skipping disabled repository central > [DEBUG] ejb3: using locally installed snapshot > [DEBUG] Trying repository Newitech-snapshots-repository > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Trying repository Newitech-publiczne > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne//pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/) > [DEBUG] Trying repository Maven Snapshots > Downloading: > http://people.apache.org/maven-snapshot-repository/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Maven > Snapshots (http://people.apache.org/maven-snapshot-repository) > [DEBUG] Trying repository codehausSnapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2) > [DEBUG] Skipping disabled repository central > [DEBUG] Unable to download the artifact from any repository > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=pl.waw.tabor -DartifactId=ejb3 \ > -Dversion=1.0-SNAPSHOT -Dpackaging=ejb-client -Dfile=/path/to/file > Path to dependency: > 1) pl.waw.tabor:client:jar:1.0-SNAPSHOT > 2) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT > pl.waw.tabor:ejb3:ejb-client:1.0-SNAPSHOT > from the specified remote repositories: > Maven Snapshots (http://people.apache.org/maven-snapshot-repository), > central (http://repo1.maven.org/maven2), > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2), > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots), > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/), > Newitech-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > Missing: >
[jira] Closed: (MNG-2851) The artifact handlers must be loaded upfront for all operations
[ http://jira.codehaus.org/browse/MNG-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2851. -- Resolution: Fixed Milos has fixed this in the embedder. > The artifact handlers must be loaded upfront for all operations > --- > > Key: MNG-2851 > URL: http://jira.codehaus.org/browse/MNG-2851 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 2.1.x >Reporter: Jason van Zyl > Fix For: 2.1-alpha-1 > > > check the test I've added to MavenEmbedderTest. Without this loading > of project (without deps) the artifact handlers don't get taken into > account when loading the project. > the artifact handlers are added somewhere in lifecycle executor which > is not even touched on readProjectWithDependencies(). > Milos > On 2/27/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > Hey, > Just wondering about reading the project twice in read project with > dependencies. Why are you trying to find the artifact handlers once > and then reading the project again? > Just wondering if you copied this stuff from internal components why > it's not working. Is this for the case where you've added new ones > after the embedder has started? -- 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-2851) The artifact handlers must be loaded upfront for all operations
[ http://jira.codehaus.org/browse/MNG-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106248 ] Jason van Zyl commented on MNG-2851: Milos, this has effectively been done in the embedder for now which is fine with me. We can add tests and improve it as we go. John, they are needed when not executing but using the readProjectWithDependencies in the embedder. It's how IDE integration loads/imports projects and updates the POM without executing a goal/phase. > The artifact handlers must be loaded upfront for all operations > --- > > Key: MNG-2851 > URL: http://jira.codehaus.org/browse/MNG-2851 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 2.1.x >Reporter: Jason van Zyl > Fix For: 2.1-alpha-1 > > > check the test I've added to MavenEmbedderTest. Without this loading > of project (without deps) the artifact handlers don't get taken into > account when loading the project. > the artifact handlers are added somewhere in lifecycle executor which > is not even touched on readProjectWithDependencies(). > Milos > On 2/27/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > Hey, > Just wondering about reading the project twice in read project with > dependencies. Why are you trying to find the artifact handlers once > and then reading the project again? > Just wondering if you copied this stuff from internal components why > it's not working. Is this for the case where you've added new ones > after the embedder has started? -- 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-2589) Inherit transitive dependencies with runtime scope
[ http://jira.codehaus.org/browse/MNG-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106247 ] Jason van Zyl commented on MNG-2589: Maybe this could be another enforcer rule? Brian? > Inherit transitive dependencies with runtime scope > -- > > Key: MNG-2589 > URL: http://jira.codehaus.org/browse/MNG-2589 > Project: Maven 2 > Issue Type: Improvement > Components: Dependencies >Affects Versions: 2.0.4 >Reporter: Joerg Schaible > Fix For: 2.1-alpha-1 > > > Transitive dependencies of scope "compile" should be inherited with scope > "compile" only. This would avoid unwanted usage of 3rd party packages and > make explicit dependencies visible. It should be possible at least to run > Maven in such a mode. -- 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-2871) Subartifact (ejb-client for example) are not reselved as active project artifacts
[ http://jira.codehaus.org/browse/MNG-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Tabor updated MNG-2871: - Attachment: MNG-2871-maven-project-2.1-SNAPSHOT.diff Patch for trunk (2.1-SNAPSHOT) (rev. 572195) > Subartifact (ejb-client for example) are not reselved as active project > artifacts > - > > Key: MNG-2871 > URL: http://jira.codehaus.org/browse/MNG-2871 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4, 2.0.5 > Environment: Not platform dependent >Reporter: Piotr Tabor >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > Attachments: MavenProject.java, > MNG-2871-core-integration-testing-2.diff, > MNG-2871-core-integration-tests.diff, > MNG-2871-maven-project-2.1-SNAPSHOT.diff, MNG-2871-maven-project.diff, > root.tar > > > I have prepared simple project to show the bug. > It contains three artifacts: > |-root > \--- ejb3 > \--- client > Client depends on ejb3 with ejb-client. > The local and remote repository must not contain those artifacts. > When I do "mvn -X compile" (or even integration-tests) on root project I will > get those errors: > ... > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' --> > [DEBUG] (f) filters = [] > [DEBUG] (f) outputDirectory = /home/ptab/m2/bug/root/client/target/classes > [DEBUG] (f) project = [EMAIL PROTECTED] > [DEBUG] (f) resources = [EMAIL PROTECTED] > [DEBUG] -- end configuration -- > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [DEBUG] pl.waw.tabor:client:jar:1.0-SNAPSHOT (selected for null) > [DEBUG] junit:junit:jar:3.8.1:test (selected for test) > [DEBUG] pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT:compile (selected > for compile) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Skipping disabled repository central > [DEBUG] ejb3: using locally installed snapshot > [DEBUG] Trying repository Newitech-snapshots-repository > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Trying repository Newitech-publiczne > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne//pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/) > [DEBUG] Trying repository Maven Snapshots > Downloading: > http://people.apache.org/maven-snapshot-repository/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Maven > Snapshots (http://people.apache.org/maven-snapshot-repository) > [DEBUG] Trying repository codehausSnapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2) > [DEBUG] Skipping disabled repository central > [DEBUG] Unable to download the artifact from any repository > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=pl.waw.tabor -DartifactId=ejb3 \ > -Dversion=1.0-SNAPSHOT -Dpackaging=ejb-client -Dfile=/path/to/file > Path to dependency: > 1) pl.waw.tabor:client:jar:1.0-SNAPSHOT > 2) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT > pl.waw.tabor:ejb3:ejb-client:1.0-SNAPSHOT > from the specified remote repositories: > Maven Snapshots (http://people.apache.org/maven-snapshot-repository), > central (http://repo1.maven.org/maven2), > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2), > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots), > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/), > Newitech-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to res
[jira] Commented: (MNG-3138) MavenIT0114ExtensionThatProvidesResources fails on trunk only
[ http://jira.codehaus.org/browse/MNG-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106244 ] Brett Porter commented on MNG-3138: --- I think this was fixed by applying Eric's patch earlier today. Thanks! > MavenIT0114ExtensionThatProvidesResources fails on trunk only > - > > Key: MNG-3138 > URL: http://jira.codehaus.org/browse/MNG-3138 > Project: Maven 2 > Issue Type: Bug > Components: integration tests >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Can't find it0114_rule_set.xml on classpath!! > [INFO] > > [INFO] Trace > org.apache.maven.BuildFailureException: Can't find it0114_rule_set.xml on > classpath!! > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:296) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:112) > at > org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:911) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:367) > 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: org.apache.maven.lifecycle.LifecycleExecutionException: Can't find > it0114_rule_set.xml on classpath!! > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:379) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:255) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:141) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) > ... 11 more > Caused by: org.apache.maven.plugin.MojoExecutionException: Can't find > it0114_rule_set.xml on classpath!! > at org.apache.maven.plugin.It0014Mojo.execute(It0014Mojo.java:26) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:647) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:354) > ... 14 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3179) [regression] incorrect handling of build errors in the reactor
[regression] incorrect handling of build errors in the reactor -- Key: MNG-3179 URL: http://jira.codehaus.org/browse/MNG-3179 Project: Maven 2 Issue Type: Bug Components: Command Line, Reactor and workspace Affects Versions: 2.1-alpha-1 Reporter: Brett Porter Priority: Minor Fix For: 2.1.x example: introduce an error into the Maven trunk build (I removed the jdom dependency from maven-model to cause compile failures), and run "mvn clean install". You get the error in the project, then the list of reactor projects with success/fail/not built, then the errors again, then: [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] BUILD ERRORS [INFO] [INFO] Total time: 6 seconds [INFO] Finished at: Mon Sep 03 10:18:07 EST 2007 [INFO] Final Memory: 20M/37M [INFO] FATAL ERROR: Unable to configure the Maven application For more information, run with the -e flag I expect that: * the build failures should only be output once in the --fail-fast mode * it should be BUILD FAILURES, not BUILD ERRORS * the FATAL ERROR message should not be present at the end -- 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-3179) [regression] incorrect handling of build errors in the reactor
[ http://jira.codehaus.org/browse/MNG-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3179: -- Fix Version/s: 2.1.x > [regression] incorrect handling of build errors in the reactor > -- > > Key: MNG-3179 > URL: http://jira.codehaus.org/browse/MNG-3179 > Project: Maven 2 > Issue Type: Bug > Components: Command Line, Reactor and workspace >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter >Priority: Minor > Fix For: 2.1.x > > > example: introduce an error into the Maven trunk build (I removed the jdom > dependency from maven-model to cause compile failures), and run "mvn clean > install". > You get the error in the project, then the list of reactor projects with > success/fail/not built, then the errors again, then: > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] BUILD ERRORS > [INFO] > > [INFO] Total time: 6 seconds > [INFO] Finished at: Mon Sep 03 10:18:07 EST 2007 > [INFO] Final Memory: 20M/37M > [INFO] > > FATAL ERROR: Unable to configure the Maven application > For more information, run with the -e flag > I expect that: > * the build failures should only be output once in the --fail-fast mode > * it should be BUILD FAILURES, not BUILD ERRORS > * the FATAL ERROR message should not be present at the end -- 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-3054) [regression] maven reports build success even on error.
[ http://jira.codehaus.org/browse/MNG-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-3054. - Assignee: Brett Porter Resolution: Duplicate Fix Version/s: (was: 2.1-alpha-1) > [regression] maven reports build success even on error. > --- > > Key: MNG-3054 > URL: http://jira.codehaus.org/browse/MNG-3054 > Project: Maven 2 > Issue Type: Bug > Components: Errors >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter >Assignee: Brett Porter >Priority: Critical > > See linked issue for an example. > The output is something like this: > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to construct build plan for: > test:exec-phase-binding-test:jar:1.0-SNAPSHOT ( task-segment: [install] ). > Reason: No phase specified for goal: aspectj-report in plugin: > org.codehaus.mojo:aspectj-maven-plugin from POM: > test:exec-phase-binding-test:jar:1.0-SNAPSHOT > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: < 1 second > [INFO] Finished at: Thu Jun 14 11:50:42 EST 2007 > [INFO] Final Memory: 2M/5M > [INFO] > > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: < 1 second > [INFO] Finished at: Thu Jun 14 11:50:42 EST 2007 > [INFO] Final Memory: 2M/5M > [INFO] > > In addition, the exit code is 0, instead of 1 as desired. -- 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] Reopened: (MNG-2938) Build error is ignored at the end of the build
[ http://jira.codehaus.org/browse/MNG-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reopened MNG-2938: --- on any reactor project, type "mvn MNG-2938" :) (I did it on components/trunk). It seems to only be a problem in the reactor. > Build error is ignored at the end of the build > -- > > Key: MNG-2938 > URL: http://jira.codehaus.org/browse/MNG-2938 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.1.x >Reporter: Carlos Sanchez > Fix For: 2.1-alpha-1 > > > On a build error you get "BUILD ERROR" and then "BUILD SUCCESSFUL" > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to construct build plan for: > org.apache.maven.its.it0020:maven-it-it0020:maven-plugin:1.0-SNAPSHOT ( > task-segment: [clean:clean, install, > ... > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Thu Apr 05 16:27:47 PDT 2007 > [INFO] Final Memory: 6M/11M > [INFO] > > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Thu Apr 05 16:27:47 PDT 2007 > [INFO] Final Memory: 6M/11M > [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] Closed: (MNG-2938) Build error is ignored at the end of the build
[ http://jira.codehaus.org/browse/MNG-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2938. -- Resolution: Fixed I don't believe this happens, and there's no command to try. Re-open with an example if you find this is still the case. > Build error is ignored at the end of the build > -- > > Key: MNG-2938 > URL: http://jira.codehaus.org/browse/MNG-2938 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.1.x >Reporter: Carlos Sanchez > Fix For: 2.1-alpha-1 > > > On a build error you get "BUILD ERROR" and then "BUILD SUCCESSFUL" > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to construct build plan for: > org.apache.maven.its.it0020:maven-it-it0020:maven-plugin:1.0-SNAPSHOT ( > task-segment: [clean:clean, install, > ... > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Thu Apr 05 16:27:47 PDT 2007 > [INFO] Final Memory: 6M/11M > [INFO] > > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Thu Apr 05 16:27:47 PDT 2007 > [INFO] Final Memory: 6M/11M > [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] Closed: (MNG-1138) remove use of exclusions through m2
[ http://jira.codehaus.org/browse/MNG-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-1138. -- Resolution: Fixed Looks pretty up-to-date, it's only the core, embedder, and project. > remove use of exclusions through m2 > --- > > Key: MNG-1138 > URL: http://jira.codehaus.org/browse/MNG-1138 > Project: Maven 2 > Issue Type: Bug > Components: Bootstrap & Build >Reporter: Brett Porter >Priority: Trivial > Fix For: 2.1-alpha-1 > > -- 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-2871) Subartifact (ejb-client for example) are not reselved as active project artifacts
[ http://jira.codehaus.org/browse/MNG-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106240 ] Jason van Zyl commented on MNG-2871: Piotr is preparing the patch for trunk, and I will apply it. > Subartifact (ejb-client for example) are not reselved as active project > artifacts > - > > Key: MNG-2871 > URL: http://jira.codehaus.org/browse/MNG-2871 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4, 2.0.5 > Environment: Not platform dependent >Reporter: Piotr Tabor >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > Attachments: MavenProject.java, > MNG-2871-core-integration-testing-2.diff, > MNG-2871-core-integration-tests.diff, MNG-2871-maven-project.diff, root.tar > > > I have prepared simple project to show the bug. > It contains three artifacts: > |-root > \--- ejb3 > \--- client > Client depends on ejb3 with ejb-client. > The local and remote repository must not contain those artifacts. > When I do "mvn -X compile" (or even integration-tests) on root project I will > get those errors: > ... > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' --> > [DEBUG] (f) filters = [] > [DEBUG] (f) outputDirectory = /home/ptab/m2/bug/root/client/target/classes > [DEBUG] (f) project = [EMAIL PROTECTED] > [DEBUG] (f) resources = [EMAIL PROTECTED] > [DEBUG] -- end configuration -- > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [DEBUG] pl.waw.tabor:client:jar:1.0-SNAPSHOT (selected for null) > [DEBUG] junit:junit:jar:3.8.1:test (selected for test) > [DEBUG] pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT:compile (selected > for compile) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Skipping disabled repository central > [DEBUG] ejb3: using locally installed snapshot > [DEBUG] Trying repository Newitech-snapshots-repository > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Trying repository Newitech-publiczne > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne//pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/) > [DEBUG] Trying repository Maven Snapshots > Downloading: > http://people.apache.org/maven-snapshot-repository/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Maven > Snapshots (http://people.apache.org/maven-snapshot-repository) > [DEBUG] Trying repository codehausSnapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2) > [DEBUG] Skipping disabled repository central > [DEBUG] Unable to download the artifact from any repository > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=pl.waw.tabor -DartifactId=ejb3 \ > -Dversion=1.0-SNAPSHOT -Dpackaging=ejb-client -Dfile=/path/to/file > Path to dependency: > 1) pl.waw.tabor:client:jar:1.0-SNAPSHOT > 2) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT > pl.waw.tabor:ejb3:ejb-client:1.0-SNAPSHOT > from the specified remote repositories: > Maven Snapshots (http://people.apache.org/maven-snapshot-repository), > central (http://repo1.maven.org/maven2), > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2), > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots), > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/), > Newitech-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > Missing: > -- > 1) pl.waw.tabor:ejb
[jira] Updated: (MNG-2608) configure a repository as the 'preferred' download location for certain artifactIds or groupIds
[ http://jira.codehaus.org/browse/MNG-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2608: --- Fix Version/s: (was: 2.1-alpha-1) 2.1.x > configure a repository as the 'preferred' download location for certain > artifactIds or groupIds > --- > > Key: MNG-2608 > URL: http://jira.codehaus.org/browse/MNG-2608 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories >Reporter: Jorg Heymans > Fix For: 2.1.x > > > ivy has this feature where you can tell it where an artifact is located. > During dependency resolution, this avoids a lot of unnecessary http lookups > to the configured repositories while searching for the artifact because it > will go straight to the correct one. > in pom speak: > > > > > > > > > > > > > > > > > org.apache.cocoon > my.special.artifact > > > If the groupid or artifactid was not found on the 'preferred' server then you > could still try and contact the other configured repositories ofcourse. > As an example: output of artifact resolution in cocoon while looking for an > updated snapshot > [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-M2-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-M2-SNAPSHOT: > checking for updates from reinhard-m2-snapshot-repository > [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-M2-SNAPSHOT: > checking for updates from central > [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-M2-SNAPSHOT: > checking for updates from apache.snapshot > [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-M2-SNAPSHOT: > checking for updates from apache-cvs > [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-M2-SNAPSHOT: > checking for updates from apache.snapshots -- 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-2836) Remove all optimizations so we can get a solid baseline and measure improvements
[ http://jira.codehaus.org/browse/MNG-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2836. -- Resolution: Fixed The project builder, plugin instances (class realms) in the plugin manager, and in artifact resolution but we're deal with all of these individually. > Remove all optimizations so we can get a solid baseline and measure > improvements > > > Key: MNG-2836 > URL: http://jira.codehaus.org/browse/MNG-2836 > Project: Maven 2 > Issue Type: Task > Components: General >Affects Versions: 2.1-alpha-1 >Reporter: Jason van Zyl > Fix For: 2.1-alpha-1 > > > I would like to remove all optimizations from the core, and then look for > ways to improve after we have benchmarked the baseline. -- 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-2915) No way to avoid adding artifactId to site urls
[
http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-2915:
---
Fix Version/s: (was: 2.1-alpha-1)
2.1.x
> No way to avoid adding artifactId to site urls
> --
>
> Key: MNG-2915
> URL: http://jira.codehaus.org/browse/MNG-2915
> Project: Maven 2
> Issue Type: Improvement
> Components: Sites & Reporting
>Affects Versions: 2.0.5
>Reporter: Richard van der Hoff
>Priority: Minor
> Fix For: 2.1.x
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override
> the relevant settings), both project.url and
> project.distributionManagement.site.url have the name of the child artifact
> appended.
> It would be nice to be able to have something like
> :code:
> scpexe://host/blah/${project.artifactId}/${project.version}
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects,
> with useful settings such as distributionManagement, and I'd like to be able
> to deploy their sites to a single directory and have Apache generate me a
> directory listing for all the child projects. However, I curently have no way
> of releasing the parent project without obliterating the list of child
> projects.
--
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-2753) trunk needs to support passing system properties and environment variables through the CLI into the embedder
[ http://jira.codehaus.org/browse/MNG-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2753. -- Resolution: Fixed Support turned back on, IT reactivated for 2.1. > trunk needs to support passing system properties and environment variables > through the CLI into the embedder > > > Key: MNG-2753 > URL: http://jira.codehaus.org/browse/MNG-2753 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.1.x >Reporter: Brett Porter >Assignee: Jason van Zyl >Priority: Blocker > Fix For: 2.1-alpha-1 > > > handling was wisely removed from maven-project itself, but for backwards > compatibility we need to still support the population of properties from > system properties and environment variables at the CLI level. These variables > should be passed in to the embedder. -- 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] Work stopped: (MNG-2753) trunk needs to support passing system properties and environment variables through the CLI into the embedder
[ http://jira.codehaus.org/browse/MNG-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-2753 stopped by Jason van Zyl. > trunk needs to support passing system properties and environment variables > through the CLI into the embedder > > > Key: MNG-2753 > URL: http://jira.codehaus.org/browse/MNG-2753 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.1.x >Reporter: Brett Porter >Assignee: Jason van Zyl >Priority: Blocker > Fix For: 2.1-alpha-1 > > > handling was wisely removed from maven-project itself, but for backwards > compatibility we need to still support the population of properties from > system properties and environment variables at the CLI level. These variables > should be passed in to the embedder. -- 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-3040) Failure to construct build plan fatal error on trunk r545155
[ http://jira.codehaus.org/browse/MNG-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-3040. - Resolution: Fixed Fix Version/s: (was: 2.1.x) 2.1-alpha-1 John fixed it (the error is a bit confusing, but it's better than the exception :) > Failure to construct build plan fatal error on trunk r545155 > > > Key: MNG-3040 > URL: http://jira.codehaus.org/browse/MNG-3040 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter >Assignee: John Casey > Fix For: 2.1-alpha-1 > > Attachments: exec-phase-binding-test.zip, pom.xml > > > see attached pom which causes this: > mcbrett:~/scm/maven/sandbox/continuum/continuum-data-upgrade brett$ mvn clean > install -e > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Unnamed - > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT > [INFO] task-segment: [clean, install] > [INFO] > > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to construct build plan for: > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT ( > task-segment: [clean, install] ). Reason: No phase specified for goal: exec > in plugin: org.codehaus.mojo:exec-maven-plugin from POM: > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT > [INFO] > > [INFO] Trace > org.apache.maven.BuildFailureException: Failed to construct build plan for: > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT ( > task-segment: [clean, install] ). Reason: No phase specified for goal: exec > in plugin: org.codehaus.mojo:exec-maven-plugin from POM: > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:296) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:112) > at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:906) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:367) > 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: org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > construct build plan for: > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT ( > task-segment: [clean, install] ). Reason: No phase specified for goal: exec > in plugin: org.codehaus.mojo:exec-maven-plugin from POM: > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindings(DefaultLifecycleExecutor.java:305) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:246) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:141) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) > ... 11 more > Caused by: org.apache.maven.lifecycle.LifecycleSpecificationException: No > phase specified for goal: exec in plugin: org.codehaus.mojo:exec-maven-plugin > from POM: org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT > at > org.apache.maven.lifecycle.binding.DefaultLifecycleBindingManager.getProjectCustomBindings(DefaultLifecycleBindingManager.java:295) > > at > org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan(DefaultBuildPlanner.java:54) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindings(DefaultLifecycleExecutor.java:294) > > ... 14 more > [INFO] > > [INFO] Total time: < 1 second > [INFO] Finished at: Thu Jun 07 22:40:57 EST 2007 > [INFO] Final Memory: 2M/5M > [INFO
[jira] Closed: (MNG-2968) Forbid dots in artifactId
[ http://jira.codehaus.org/browse/MNG-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2968. -- Resolution: Won't Fix We simply can't do this for backward compatibility reasons. It's just too much pain for users. > Forbid dots in artifactId > - > > Key: MNG-2968 > URL: http://jira.codehaus.org/browse/MNG-2968 > Project: Maven 2 > Issue Type: Improvement > Components: POM >Affects Versions: 2.0.6, 2.1-alpha-1 >Reporter: Carlos Sanchez > Fix For: 2.1-alpha-1 > > > artifactIds with dots are potential trouble. They prevent using > groupId.artifactId as identifier and later parse it back -- 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-2968) Forbid dots in artifactId
[ http://jira.codehaus.org/browse/MNG-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106235 ] Jason van Zyl commented on MNG-2968: I don't think we can do this. You are going to tank tons and tons of builds. We allowed this so it's like the envars where we didn't do this up front so now we have to live with. Something like this so fundamental can't change. We just have to suck it up. > Forbid dots in artifactId > - > > Key: MNG-2968 > URL: http://jira.codehaus.org/browse/MNG-2968 > Project: Maven 2 > Issue Type: Improvement > Components: POM >Affects Versions: 2.0.6, 2.1-alpha-1 >Reporter: Carlos Sanchez > Fix For: 2.1-alpha-1 > > > artifactIds with dots are potential trouble. They prevent using > groupId.artifactId as identifier and later parse it back -- 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-3040) Failure to construct build plan fatal error on trunk r545155
[ http://jira.codehaus.org/browse/MNG-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106234 ] Jason van Zyl commented on MNG-3040: Did you guys sort this out? > Failure to construct build plan fatal error on trunk r545155 > > > Key: MNG-3040 > URL: http://jira.codehaus.org/browse/MNG-3040 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter >Assignee: John Casey > Fix For: 2.1.x > > Attachments: exec-phase-binding-test.zip, pom.xml > > > see attached pom which causes this: > mcbrett:~/scm/maven/sandbox/continuum/continuum-data-upgrade brett$ mvn clean > install -e > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Unnamed - > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT > [INFO] task-segment: [clean, install] > [INFO] > > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to construct build plan for: > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT ( > task-segment: [clean, install] ). Reason: No phase specified for goal: exec > in plugin: org.codehaus.mojo:exec-maven-plugin from POM: > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT > [INFO] > > [INFO] Trace > org.apache.maven.BuildFailureException: Failed to construct build plan for: > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT ( > task-segment: [clean, install] ). Reason: No phase specified for goal: exec > in plugin: org.codehaus.mojo:exec-maven-plugin from POM: > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:296) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:112) > at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:906) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:367) > 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: org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > construct build plan for: > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT ( > task-segment: [clean, install] ). Reason: No phase specified for goal: exec > in plugin: org.codehaus.mojo:exec-maven-plugin from POM: > org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindings(DefaultLifecycleExecutor.java:305) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:246) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:141) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) > ... 11 more > Caused by: org.apache.maven.lifecycle.LifecycleSpecificationException: No > phase specified for goal: exec in plugin: org.codehaus.mojo:exec-maven-plugin > from POM: org.apache.maven.continuum:continuum-data-upgrade:jar:1.1-SNAPSHOT > at > org.apache.maven.lifecycle.binding.DefaultLifecycleBindingManager.getProjectCustomBindings(DefaultLifecycleBindingManager.java:295) > > at > org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan(DefaultBuildPlanner.java:54) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindings(DefaultLifecycleExecutor.java:294) > > ... 14 more > [INFO] > > [INFO] Total time: < 1 second > [INFO] Finished at: Thu Jun 07 22:40:57 EST 2007 > [INFO] Final Memory: 2M/5M > [INFO] > > [INFO] >
[jira] Commented: (MNG-2878) NPE when run with Maven 2.1-SNAPSHOT
[
http://jira.codehaus.org/browse/MNG-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106233
]
Jason van Zyl commented on MNG-2878:
Vincent, what version of checkstyle? I'll just assume the latest release.
> NPE when run with Maven 2.1-SNAPSHOT
>
>
> Key: MNG-2878
> URL: http://jira.codehaus.org/browse/MNG-2878
> Project: Maven 2
> Issue Type: Bug
> Components: Sites & Reporting
>Affects Versions: 2.1-alpha-1
> Environment: Maven 2.1 built from trunk on 15 March 2007, 10:00AM
> Checkstyle plugin built from trunk on 15 March 2007, 11:20
>Reporter: Vincent Massol
>Assignee: Jason van Zyl
> Fix For: 2.1-alpha-1
>
>
> I get:
> {code}
> [INFO] An error has occurred in Checkstyle report generation.
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred
> in Checkstyle report generation.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:524)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:862)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:699)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:470)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:440)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:419)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:271)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:238)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:146)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:303)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
> at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:907)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:369)
> 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: org.apache.maven.plugin.MojoExecutionException: An error has
> occurred in Checkstyle report generation.
> at
> org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:79)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:598)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:499)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at java.io.Reader.(Reader.java:61)
> at java.io.InputStreamReader.(InputStreamReader.java:55)
> at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:248)
> at org.codehaus.plexus.util.IOUtil.toString(IOUtil.java:307)
> at org.codehaus.plexus.util.IOUtil.toString(IOUtil.java:295)
> at
> org.apache.maven.reporting.AbstractMavenReport.getSiteDescriptor(AbstractMavenReport.java:134)
> at
> org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:70)
> ... 22 more
> {code}
> The POM I used:
> {code}
>
>
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki
> xwiki-build-verifications
> 1.0-SNAPSHOT
>
>
>
>
> **/Api.java,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java
>
>
>
>
>
> {code}
> Thanks
> -Vincent
--
This message is automatically generate
[jira] Created: (MSITE-255) Executing the site-site goal fails prior to executing the site-deploy goal on a clean maven install (Could be due to dependencies)
Executing the site-site goal fails prior to executing the site-deploy goal on a
clean maven install (Could be due to dependencies)
--
Key: MSITE-255
URL: http://jira.codehaus.org/browse/MSITE-255
Project: Maven 2.x Site Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-5
Environment: Windows XP, Java 1.5, Intel Pentium 4
Reporter: Sahand
When running {{mvn site:site}} from a clean maven install I get FATAL ERROR
caused by a NullPointerException. (*Trace log below*)
This was resolved by running {{mvn site:deploy}} which seemed to retrieve a
series of dependent libraries. After which, running {{mvn site:site}} would
execute successfully.
I will test it again when I get the time to narrow down the dependency that is
required for execution and is not being retrieved.
{quote}
[ERROR] FATAL ERROR
[INFO] -
---
[INFO] null
[INFO] -
---
[INFO] Trace
java.lang.NullPointerException
at org.apache.maven.doxia.module.fml.FmlParser.createSink(FmlParser.java
:270)
at org.apache.maven.doxia.module.fml.FmlParser.parse(FmlParser.java:61)
at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:52)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocumen
t(DefaultSiteRenderer.java:264)
at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocum
ent(DoxiaDocumentRenderer.java:43)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(
DefaultSiteRenderer.java:239)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(Defaul
tSiteRenderer.java:115)
at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124
)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:443)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:480)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:459)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:311)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] -
---
[INFO] Total time: 26 seconds
[INFO] Finished at: Wed Aug 29 12:49:50 EST 2007
[INFO] Final Memory: 25M/44M
[INFO] -
{quote}
--
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-2935) settings.xml errors are ignored
[ http://jira.codehaus.org/browse/MNG-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2935. -- Resolution: Fixed The build will stop if the settings are bad. User and global. > settings.xml errors are ignored > --- > > Key: MNG-2935 > URL: http://jira.codehaus.org/browse/MNG-2935 > Project: Maven 2 > Issue Type: Bug > Components: Settings >Affects Versions: 2.1.x >Reporter: Carlos Sanchez >Assignee: Jason van Zyl >Priority: Minor > Fix For: 2.1-alpha-1 > > > when there's a parsing error on settings.xml the build continues ignoring it > $ mvn clean -X > + Error stacktraces are turned on. > Maven version: 2.1-SNAPSHOT > [ERROR] Failed to read settings from: xxx\.m2\settings.xml. Throwing > XmlPullParserException... > [DEBUG] Registering at plexus.core: > org.apache.maven.wagon.providers.ssh.jsch.interactive.PrompterUIKeyboardInteractive > (object realm: [EMAIL PROTECTED]), lookuprealm=plexus.core > [INFO] Scanning for projects... -- 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] Work stopped: (MNG-2935) settings.xml errors are ignored
[ http://jira.codehaus.org/browse/MNG-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-2935 stopped by Jason van Zyl. > settings.xml errors are ignored > --- > > Key: MNG-2935 > URL: http://jira.codehaus.org/browse/MNG-2935 > Project: Maven 2 > Issue Type: Bug > Components: Settings >Affects Versions: 2.1.x >Reporter: Carlos Sanchez >Assignee: Jason van Zyl >Priority: Minor > Fix For: 2.1-alpha-1 > > > when there's a parsing error on settings.xml the build continues ignoring it > $ mvn clean -X > + Error stacktraces are turned on. > Maven version: 2.1-SNAPSHOT > [ERROR] Failed to read settings from: xxx\.m2\settings.xml. Throwing > XmlPullParserException... > [DEBUG] Registering at plexus.core: > org.apache.maven.wagon.providers.ssh.jsch.interactive.PrompterUIKeyboardInteractive > (object realm: [EMAIL PROTECTED]), lookuprealm=plexus.core > [INFO] Scanning for projects... -- 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] Reopened: (CONTINUUM-358) User Authentication via LDAP
[ http://jira.codehaus.org/browse/CONTINUUM-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell reopened CONTINUUM-358: --- details details... > User Authentication via LDAP > > > Key: CONTINUUM-358 > URL: http://jira.codehaus.org/browse/CONTINUUM-358 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Reporter: Frank Zhao >Assignee: Jesse McConnell > Fix For: 1.1-beta-3 > > > Please add LDAP support for the user authentication in Continuum user > management function. -- 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] Work started: (MNG-2753) trunk needs to support passing system properties and environment variables through the CLI into the embedder
[ http://jira.codehaus.org/browse/MNG-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-2753 started by Jason van Zyl. > trunk needs to support passing system properties and environment variables > through the CLI into the embedder > > > Key: MNG-2753 > URL: http://jira.codehaus.org/browse/MNG-2753 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.1.x >Reporter: Brett Porter >Assignee: Jason van Zyl >Priority: Blocker > Fix For: 2.1-alpha-1 > > > handling was wisely removed from maven-project itself, but for backwards > compatibility we need to still support the population of properties from > system properties and environment variables at the CLI level. These variables > should be passed in to the embedder. -- 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-45) abilitiy to create an ear/war/zip from site
[ http://jira.codehaus.org/browse/MSITE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MSITE-45: -- Patch Submitted: [Yes] > abilitiy to create an ear/war/zip from site > --- > > Key: MSITE-45 > URL: http://jira.codehaus.org/browse/MSITE-45 > Project: Maven 2.x Site Plugin > Issue Type: New Feature >Reporter: Brett Porter > Attachments: MSITE-45-maven-site-plugin.patch, patch.txt > > > I think they should be standalone goals, like in m1 > site:ear -> create ear > site:war -> create war > site:zip -> create zip > I think this one might be a lower priority. I will postpone it. -- 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-242) remove plexus utils sources from site plugin sources since it is a dependency
[ http://jira.codehaus.org/browse/MSITE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSITE-242: Fix Version/s: (was: 2.0-beta-6) 2.0-beta-7 > remove plexus utils sources from site plugin sources since it is a dependency > - > > Key: MSITE-242 > URL: http://jira.codehaus.org/browse/MSITE-242 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Herve Boutemy >Assignee: Dennis Lundberg > Fix For: 2.0-beta-7 > > > the dependency has been uncommented, but the source code copy hasn't been > removed -- 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: (SCM-339) Need documentation on how to configure path to ss.exe for VSS provider
[ http://jira.codehaus.org/browse/SCM-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allan Lang updated SCM-339: --- Attachment: SCM-339-maven-scm-site.patch Attached patch file adding basic VSS provider configuration information to SCM site. > Need documentation on how to configure path to ss.exe for VSS provider > -- > > Key: SCM-339 > URL: http://jira.codehaus.org/browse/SCM-339 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-site >Affects Versions: 1.0 > Environment: N/A >Reporter: Allan Lang > Attachments: SCM-339-maven-scm-site.patch > > > The Maven SCM website currently has no information on how to set the path of > the ss.exe executable for use by the VSS provider. This should be added. -- 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-242) remove plexus utils sources from site plugin sources since it is a dependency
[ http://jira.codehaus.org/browse/MSITE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106229 ] Herve Boutemy commented on MSITE-242: - you're right, I didn't understand this consequence no problem to let this issue open and wait for a later release > remove plexus utils sources from site plugin sources since it is a dependency > - > > Key: MSITE-242 > URL: http://jira.codehaus.org/browse/MSITE-242 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Herve Boutemy >Assignee: Dennis Lundberg > Fix For: 2.0-beta-6 > > > the dependency has been uncommented, but the source code copy hasn't been > removed -- 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: (SCM-339) Need documentation on how to configure path to ss.exe for VSS provider
Need documentation on how to configure path to ss.exe for VSS provider -- Key: SCM-339 URL: http://jira.codehaus.org/browse/SCM-339 Project: Maven SCM Issue Type: Improvement Components: maven-scm-site Affects Versions: 1.0 Environment: N/A Reporter: Allan Lang The Maven SCM website currently has no information on how to set the path of the ss.exe executable for use by the VSS provider. This should be added. -- 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: (MIDEA-80) Transitive dependencies in a of a module in a multiproject should be exported
[ http://jira.codehaus.org/browse/MIDEA-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106227 ] Kohsuke Kawaguchi commented on MIDEA-80: I tried the patch but I think it is incomplete. When module X depends on Y, this patch only excludes Y's direct dependencies from X, whereas the expected behavior is to exclude all the transitive dependencies of Y from X. > Transitive dependencies in a of a module in a multiproject should be exported > - > > Key: MIDEA-80 > URL: http://jira.codehaus.org/browse/MIDEA-80 > Project: Maven 2.x IDEA Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Michael Mekaail > Attachments: MIDEA-80-maven-idea-plugin.patch, > MIDEA-80-maven-idea-plugin.patch > > > Currently the maven-idea-plugin treats all dependencies the same in that it > just adds all of them to each module > But what I would like is that if I have dependencies that are transative as a > result of it depending upon another module in my multimodule project then I > would like the module to be dependent only upon its upper module and this > upper module to export all its dependencies. > This stops cluttering of alot of dependencies being put in for each module > when they can all just be exported from the top level dependency. -- 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] Work started: (MNG-2935) settings.xml errors are ignored
[ http://jira.codehaus.org/browse/MNG-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-2935 started by Jason van Zyl. > settings.xml errors are ignored > --- > > Key: MNG-2935 > URL: http://jira.codehaus.org/browse/MNG-2935 > Project: Maven 2 > Issue Type: Bug > Components: Settings >Affects Versions: 2.1.x >Reporter: Carlos Sanchez >Assignee: Jason van Zyl >Priority: Minor > Fix For: 2.1-alpha-1 > > > when there's a parsing error on settings.xml the build continues ignoring it > $ mvn clean -X > + Error stacktraces are turned on. > Maven version: 2.1-SNAPSHOT > [ERROR] Failed to read settings from: xxx\.m2\settings.xml. Throwing > XmlPullParserException... > [DEBUG] Registering at plexus.core: > org.apache.maven.wagon.providers.ssh.jsch.interactive.PrompterUIKeyboardInteractive > (object realm: [EMAIL PROTECTED]), lookuprealm=plexus.core > [INFO] Scanning for projects... -- 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] Work stopped: (MNG-3138) MavenIT0114ExtensionThatProvidesResources fails on trunk only
[ http://jira.codehaus.org/browse/MNG-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3138 stopped by Jason van Zyl. > MavenIT0114ExtensionThatProvidesResources fails on trunk only > - > > Key: MNG-3138 > URL: http://jira.codehaus.org/browse/MNG-3138 > Project: Maven 2 > Issue Type: Bug > Components: integration tests >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Can't find it0114_rule_set.xml on classpath!! > [INFO] > > [INFO] Trace > org.apache.maven.BuildFailureException: Can't find it0114_rule_set.xml on > classpath!! > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:296) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:112) > at > org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:911) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:367) > 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: org.apache.maven.lifecycle.LifecycleExecutionException: Can't find > it0114_rule_set.xml on classpath!! > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:379) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:255) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:141) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) > ... 11 more > Caused by: org.apache.maven.plugin.MojoExecutionException: Can't find > it0114_rule_set.xml on classpath!! > at org.apache.maven.plugin.It0014Mojo.execute(It0014Mojo.java:26) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:647) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:354) > ... 14 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3138) MavenIT0114ExtensionThatProvidesResources fails on trunk only
[ http://jira.codehaus.org/browse/MNG-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-3138. -- Resolution: Fixed Works fine. > MavenIT0114ExtensionThatProvidesResources fails on trunk only > - > > Key: MNG-3138 > URL: http://jira.codehaus.org/browse/MNG-3138 > Project: Maven 2 > Issue Type: Bug > Components: integration tests >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Can't find it0114_rule_set.xml on classpath!! > [INFO] > > [INFO] Trace > org.apache.maven.BuildFailureException: Can't find it0114_rule_set.xml on > classpath!! > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:296) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:112) > at > org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:911) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:367) > 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: org.apache.maven.lifecycle.LifecycleExecutionException: Can't find > it0114_rule_set.xml on classpath!! > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:379) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:255) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:141) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) > ... 11 more > Caused by: org.apache.maven.plugin.MojoExecutionException: Can't find > it0114_rule_set.xml on classpath!! > at org.apache.maven.plugin.It0014Mojo.execute(It0014Mojo.java:26) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:647) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:354) > ... 14 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2937) it0013 and it0020 fail with missing plugins
[ http://jira.codehaus.org/browse/MNG-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2937. -- Resolution: Fixed Fixed. > it0013 and it0020 fail with missing plugins > --- > > Key: MNG-2937 > URL: http://jira.codehaus.org/browse/MNG-2937 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1.x > Environment: XP >Reporter: Carlos Sanchez >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > Attachments: it0013-log.txt, it0020-log.txt > > -- 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: (SCM-338) NullPointerException when using -DvssDirectory to set ss.exe path
[
http://jira.codehaus.org/browse/SCM-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allan Lang updated SCM-338:
---
Attachment: SCM-338-[02]-maven-scm-provider-vss.patch
Updated patch {{SCM-338-[02]-maven-scm-provider-vss.patch}} includes a new test
case for the {{VssCommandLineUtils}}, which previously didn't have one.
The test needs to manipulate the {{~\.scm\vss-settings.xml}} file on disk,
which may be a bit suspect depending on how the project is build in CI, so
please take a look at what's going on in {{VssCommandLineUtilsTest}}.
> NullPointerException when using -DvssDirectory to set ss.exe path
> -
>
> Key: SCM-338
> URL: http://jira.codehaus.org/browse/SCM-338
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-vss
>Affects Versions: 1.0
> Environment: Windows XP, JRE 1.4.2
>Reporter: Allan Lang
>Priority: Minor
> Attachments: SCM-338-[02]-maven-scm-provider-vss.patch,
> SCM-338-maven-scm-provider-vss.patch, vssproviderbug.zip
>
>
> NullPointerException occurs with any SCM operation when there is no
> ~/.scm/vss-settings.xml file, and when the vssDirectory system property is
> set:
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.scm.provider.vss.commands.VssCommandLineUtils.getSettings(VssCommandLineUtils.java:137)
> at
> org.apache.maven.scm.provider.vss.commands.VssCommandLineUtils.getSsDir(VssCommandLineUtils.java:145)
> at
> org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.buildCmdLine(VssHistoryCommand.java:91)
> at
> org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.executeChangeLogCommand(VssHistoryCommand.java:53)
> at
> org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand(AbstractChangeLogCommand.java:101)
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58)
> ... 21 more
> {code}
> This error is easily replicated using the attached project
> vssproviderbug.zip. Unzip the archive and run
> {code}
> mvn scm:changelog -DvssDirectory=something -e
> {code}
> Assuming the file ~/.scm/vss-settings.xml does not exist, you should see the
> above error in the stack traces. Note that you don't need VSS installed (or
> even to be on Windows) in order to replicate the error - Maven doesn't
> actually get as far as making a call to ss.exe.
--
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-143) SCP works for deploy goal, but not for site-deploy
[ http://jira.codehaus.org/browse/MSITE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106221 ] Dennis Lundberg commented on MSITE-143: --- There are currently 949 open issues for Maven 2 plugins alone. Many of us working on Maven do it in our spare time. Unfortunately there never seems to be enough spare time. > SCP works for deploy goal, but not for site-deploy > -- > > Key: MSITE-143 > URL: http://jira.codehaus.org/browse/MSITE-143 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: site:deploy >Affects Versions: 2.0-beta-5 >Reporter: Jacob Robertson > Attachments: patch-MSITE-143.txt > > > The linux admins did everything necessary to get the deploy goal to work, and > now I have to go back to them and try and figure out why the "site-deploy" > goal says "Auth failed". Why does deploy work just fine with scp, but not > site-deploy? My environment is such that my deploy repository and my deploy > site directories are in the same parent directory, and have the exact same > permissions. But one goal fails to upload, and the other doesn't... -- 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-143) SCP works for deploy goal, but not for site-deploy
[ http://jira.codehaus.org/browse/MSITE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106218 ] Brill Pappin commented on MSITE-143: This issue is over a year old. Why is there not even anyone assigned to it? There seems to be ample descriptions of the problem and even a patch or two. > SCP works for deploy goal, but not for site-deploy > -- > > Key: MSITE-143 > URL: http://jira.codehaus.org/browse/MSITE-143 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: site:deploy >Affects Versions: 2.0-beta-5 >Reporter: Jacob Robertson > Attachments: patch-MSITE-143.txt > > > The linux admins did everything necessary to get the deploy goal to work, and > now I have to go back to them and try and figure out why the "site-deploy" > goal says "Auth failed". Why does deploy work just fine with scp, but not > site-deploy? My environment is such that my deploy repository and my deploy > site directories are in the same parent directory, and have the exact same > permissions. But one goal fails to upload, and the other doesn't... -- 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-247) Site generation does not inherit element from parent site.xml
[ http://jira.codehaus.org/browse/MSITE-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106216 ] Benjamin Bentmann commented on MSITE-247: - Indeed, I just downloaded 2.0-beta-6-20070902.014222-2 and the gets inherited as intended. However, I noticed a lot of warnings like bq. [WARNING] Velocimacro : VM addition rejected : : inline not allowed to replace existing VM If this is unusual for the SNAPSHOT version, just let me know and I will provide more Maven output. > Site generation does not inherit element from parent site.xml > --- > > Key: MSITE-247 > URL: http://jira.codehaus.org/browse/MSITE-247 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: inheritance >Affects Versions: 2.0-beta-5 > Environment: WinXP-SP2, JDK 1.5.0_12, Maven 2.0.7 >Reporter: Benjamin Bentmann >Priority: Minor > > I have a parent project of a multi-module project whose site.xml contains > > > The element is properly inherited by the site descriptors of > the module POMs, but the element gets dropped so that one needs to > manually add it to each site.xml for the modules. -- 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: (MJAR-30) Allow inludes/excludes definition
[ http://jira.codehaus.org/browse/MJAR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johan Kindgren updated MJAR-30: --- Attachment: mjar-30.patch This patch should fix MJAR-30 and MJAR-80. Added integration tests for the include/exclude functionality. > Allow inludes/excludes definition > - > > Key: MJAR-30 > URL: http://jira.codehaus.org/browse/MJAR-30 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Reporter: Michael Böckling > Attachments: mjar-30.patch > > > Allow the definition of includes / excludes, so the Jars content can be > customized. -- 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: (ARCHETYPE-91) create is prompting for a package
[ http://jira.codehaus.org/browse/ARCHETYPE-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106213 ] Brian Fox commented on ARCHETYPE-91: Yes that sounds like a good idea. Anything we can do to make it more user (newbie) friendly. > create is prompting for a package > - > > Key: ARCHETYPE-91 > URL: http://jira.codehaus.org/browse/ARCHETYPE-91 > Project: Maven Archetype > Issue Type: Bug > Components: Generator >Reporter: Brian Fox >Assignee: Raphaël Piéroni > Fix For: NG-1.0-alpha-1 > > > shouldn't the package type of the created project be the same as the one in > the archetype? It doesn't make sense to take a war, make an archetype and > then allow the user to generate it as a 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] Work started: (MNG-3178) Talk with list about distributionManagement/status. What is this actually for?
[
http://jira.codehaus.org/browse/MNG-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MNG-3178 started by Jason van Zyl.
> Talk with list about distributionManagement/status. What is this actually for?
> --
>
> Key: MNG-3178
> URL: http://jira.codehaus.org/browse/MNG-3178
> Project: Maven 2
> Issue Type: Task
>Reporter: Jason van Zyl
>Assignee: Jason van Zyl
>
> After pushing more exceptions up to the top this chunk of code is failing:
> if ( checkDistributionManagementStatus )
> {
> if ( ( project.getDistributionManagement() != null ) && (
> project.getDistributionManagement().getStatus() != null ) )
> {
> String projectId = safeVersionlessKey( project.getGroupId(),
> project.getArtifactId() );
> throw new ProjectBuildingException( projectId,
> "Invalid project file: distribution status must not be
> specified for a project outside of the repository" );
> }
> }
> And I don't think it's 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-3178) Talk with list about distributionManagement/status. What is this actually for?
Talk with list about distributionManagement/status. What is this actually for?
--
Key: MNG-3178
URL: http://jira.codehaus.org/browse/MNG-3178
Project: Maven 2
Issue Type: Task
Reporter: Jason van Zyl
After pushing more exceptions up to the top this chunk of code is failing:
if ( checkDistributionManagementStatus )
{
if ( ( project.getDistributionManagement() != null ) && (
project.getDistributionManagement().getStatus() != null ) )
{
String projectId = safeVersionlessKey( project.getGroupId(),
project.getArtifactId() );
throw new ProjectBuildingException( projectId,
"Invalid project file: distribution status must not be
specified for a project outside of the repository" );
}
}
And I don't think it's 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] Updated: (MSITE-227) site:deploy -> wrong links in ${modules} when artifactId=module's directory
[
http://jira.codehaus.org/browse/MSITE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MSITE-227:
--
Component/s: multi module
> site:deploy -> wrong links in ${modules} when artifactId=module's directory
> ---
>
> Key: MSITE-227
> URL: http://jira.codehaus.org/browse/MSITE-227
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 2.0-beta-5
> Environment: Eclipse IDE
>Reporter: Guimiot Isabelle
>
> I have a problem in the ${modules} part when I run the site:deploy goal.
> my project contains a root module and 2 sub-modules, at the same directory
> depth (I'm using Eclipse) :
> workspace/myRoot/
> workspace/myModule1/
> workspace/myModule2/
> my root pom contains this module declaration :
>
> ../myModule1
> ../myModule1
>
> the site:deploy goal gives this structure :
> [deploydir]/myRoot/index.html --> root's index
> [deploydir]/myRoot/myModule1/index.html --> first module's index
> [deploydir]/myRoot/myModule2/index.html --> second module's index
> when the project name (directory name in the workspace) and the artifactId
> are exactly the same, I have wrong links, both in root and in sub-modules
> pages :
> - in the root page, my links to submodules are like this :
> Modules
>
>
>myModule1
>
>
>myModule2
>
>
> - and in both modules pages, my link to the parent project is like this :
> Parent project
>
>
>myRoot
>
>
> The weirdest thing is that everything is fine when the artefactId and the
> eclipse project name (directory) are different !!! the problem appears only
> when they are identical...
> Thanks for your help !
--
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-143) SCP works for deploy goal, but not for site-deploy
[ http://jira.codehaus.org/browse/MSITE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-143: -- Component/s: site:deploy > SCP works for deploy goal, but not for site-deploy > -- > > Key: MSITE-143 > URL: http://jira.codehaus.org/browse/MSITE-143 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: site:deploy >Affects Versions: 2.0-beta-5 >Reporter: Jacob Robertson > Attachments: patch-MSITE-143.txt > > > The linux admins did everything necessary to get the deploy goal to work, and > now I have to go back to them and try and figure out why the "site-deploy" > goal says "Auth failed". Why does deploy work just fine with scp, but not > site-deploy? My environment is such that my deploy repository and my deploy > site directories are in the same parent directory, and have the exact same > permissions. But one goal fails to upload, and the other doesn't... -- 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: (ARCHETYPE-91) create is prompting for a package
[ http://jira.codehaus.org/browse/ARCHETYPE-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106211 ] Brian Fox commented on ARCHETYPE-91: For me, "java package" would be more clear. > create is prompting for a package > - > > Key: ARCHETYPE-91 > URL: http://jira.codehaus.org/browse/ARCHETYPE-91 > Project: Maven Archetype > Issue Type: Bug > Components: Generator >Reporter: Brian Fox >Assignee: Raphaël Piéroni > Fix For: NG-1.0-alpha-1 > > > shouldn't the package type of the created project be the same as the one in > the archetype? It doesn't make sense to take a war, make an archetype and > then allow the user to generate it as a 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-232) Deploy multi module site to windows share
[ http://jira.codehaus.org/browse/MSITE-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-232: -- Component/s: site:deploy > Deploy multi module site to windows share > - > > Key: MSITE-232 > URL: http://jira.codehaus.org/browse/MSITE-232 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: site:deploy >Affects Versions: 2.0-beta-4, 2.0-beta-5 > Environment: windows xp sp 2 >Reporter: Yves Van Steen > > I was unable to deploy the sites of my submodules to my windows share. the > windows share is one that is under a web path to my apache webserver. > For the record some other posted bugs on the JIRA about deploy to windows > share did'nt expect this kind of behaviour (the double backslash way, > file:\\\...). I did. Don't really find it odd. > It only works when you have a single module build. When you have a reactor > build (pom with modules) it only deploys the root (or top pom) but sub > projects don't get deployed because maven starts to use slashes and not > backslashes. > Example : > Deploy top = file://\\vam7225\repo\www\orbisbe (=> works) > Deploy subproject = file://\\vam7225\repo\www\orbisbe/component1 (=> No > deploy) > Deploy subproject = file://\\vam7225\repo\www\orbisbe/component2 (=> No > deploy) > But It does NOT report a failure on the sub projects. And you can see the use > of the normal slash above. > Is there a fix available for this ?? > Thanx for any help -- 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-30) site:deploy incompatibilities with m1.02
[ http://jira.codehaus.org/browse/MSITE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-30: - Component/s: site:deploy > site:deploy incompatibilities with m1.02 > > > Key: MSITE-30 > URL: http://jira.codehaus.org/browse/MSITE-30 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: site:deploy > Environment: All >Reporter: Paul Spencer > Fix For: 2.0-beta-7 > > > Deploying a site in m2 has changed since m1. > 1) m1 used the "tar" and "gunzip" command on the remote site, where m2 uses > the "unzip" command. This poses a problem for be since my remote site does > not support the "unzip" command, thus making the "priority" of this issue > major > 1.1) Their may be desire to deploy without the use of tools like tar and zip > on some site. The deploy would esentailly be a recersive copy > 2) No equivelent to m1 property maven.site.chmod.mode. I use this to allow > other member is the group update and delete permission > 3) No equivelent to m1 property maven.site.publish.clean > Their are other properties for the m1.02 not mentioned above, but I suspect > the they can be calculated from m2 files, i.e. pom.xml and settings.xml. > Paul Spencer -- 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-10) add rsync deploy to site
[ http://jira.codehaus.org/browse/MSITE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-10: - Component/s: site:deploy > add rsync deploy to site > > > Key: MSITE-10 > URL: http://jira.codehaus.org/browse/MSITE-10 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: site:deploy >Reporter: Brett Porter > -- 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-211) Can't deploy site using site:deploy due to a ProxyHTTP error
[ http://jira.codehaus.org/browse/MSITE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-211: -- Description: When I execute the site deployment (with version that comes with maven 2.0.5) "mvn site:deploy " I got an error see log en debug mode below. This used to work correctly with maven version 2.04 (so maybe site plugin version 2.0-beta-4 : [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error uploading site Embedded error: Cannot connect. Reason: ProxyHTTP: java.io.IOException: proxy error: Forbidden [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) 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:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading site at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:184) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more Caused by: org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: ProxyHTTP: java.io.IOException: proxy error: Forbidden at org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnection(AbstractJschWagon.java:186) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:149) ... 18 more Caused by: com.jcraft.jsch.JSchException: ProxyHTTP: java.io.IOException: proxy error: Forbidden at com.jcraft.jsch.ProxyHTTP.connect(Unknown Source) at com.jcraft.jsch.Session.connect(Unknown Source) at com.jcraft.jsch.Session.connect(Unknown Source) at org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnection(AbstractJschWagon.java:158) ... 20 more [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Wed Feb 21 12:00:41 CET 2007 [INFO] Final Memory: 3M/7M [INFO] was: When I execute the site deployment (with version that comes with maven 2.0.5) "mvn site:deploy " I got an error see log en debug mode below. This used to work correctly with maven version 2.04 (so maybe site plugin version 2.0-beta-4 : [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error uploading site Embedded error: Cannot connect. Reason: ProxyHTTP: java.io.IOException: proxy error: Forbidden [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.Defa
[jira] Updated: (MSITE-213) site:deploy to support tar gzip
[ http://jira.codehaus.org/browse/MSITE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-213: -- Component/s: site:deploy > site:deploy to support tar gzip > --- > > Key: MSITE-213 > URL: http://jira.codehaus.org/browse/MSITE-213 > Project: Maven 2.x Site Plugin > Issue Type: Wish > Components: site:deploy >Reporter: Greg Luck > > Hi > I am using sourceforge to host my site. > They just removed unzip. Not sure if it is coming back. > Wagon relies on unzip. > It would be good if it could also use gzip by creating acrhives such as are > created using "tar -zcf arhive_name dir" > That way it would work in more environments. > Thanks > Greg -- 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-141) Possible security hole when deploying site
[ http://jira.codehaus.org/browse/MSITE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-141: -- Component/s: site:deploy > Possible security hole when deploying site > -- > > Key: MSITE-141 > URL: http://jira.codehaus.org/browse/MSITE-141 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: site:deploy >Affects Versions: 2.0-beta-5 > Environment: Linux gentoo 2.6.16 64bit, maven 2.0.2 >Reporter: Martin Vysny >Priority: Critical > Fix For: 2.0-beta-7 > > > When the site is deployed into a directory /foo/bar, the following command is > issued over a ssh: > chmod -Rf g+w /foo/bar/ > it was intended to use g+r I presume? :-) -- 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-238) multi project default URL is wrong
[ http://jira.codehaus.org/browse/MSITE-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-238: -- Component/s: multi module > multi project default URL is wrong > -- > > Key: MSITE-238 > URL: http://jira.codehaus.org/browse/MSITE-238 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module >Reporter: Paul Sundling >Priority: Trivial > > In multi module projects the default URL if non is included is > //target/site//index.html , but it > should be ///target/site/index.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: (MSITE-215) creates broken links for parents parent
[ http://jira.codehaus.org/browse/MSITE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-215: -- Component/s: multi module > creates broken links for parents parent > --- > > Key: MSITE-215 > URL: http://jira.codehaus.org/browse/MSITE-215 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module >Reporter: Jörg Hohwiller > > In a multi-project environment with modules that again have modules > (project/module1/module1A) the not only creates the > direct parent but all parents (see issue MSITE-136) what seems perfect to me. > Anyways only the link of the direct parent works for me. All other links are > broken. I use "mvn site:stage -DstagingDirectory=". > If I use -DstagingDirectory=/foo/bar then the link for "module1" is > "/foo/bar//module1/index.html" what is correct. But the link > for "project" is "/foo//index.html" but it should be > "/foo/bar//index.html". > Besides I do NOT want to have the "" what is automatically > produced from the "" of the POM, but is required for > site:stage to 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] Updated: (MSITE-199) Add publishDate position "none"
[ http://jira.codehaus.org/browse/MSITE-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-199: -- Component/s: site descriptor > Add publishDate position "none" > --- > > Key: MSITE-199 > URL: http://jira.codehaus.org/browse/MSITE-199 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Components: site descriptor >Affects Versions: 2.0-beta-5 >Reporter: Jukka Zitting >Priority: Trivial > > The current examples/sitedescriptor page only documents the values left, > right, navigation-top, navigation-bottom, and bottom for the "position" > option of the element. It would be nice to also be able to > disable the publish date. > It turns out that the current default template in doxia-site-renderer will > work perfectly if given the position option "none", since it doesn't match > any of the predefined alternatives. > > I'd like to propose documenting this behaviour in examples/sitedescriptor and > adding a note about the option in the doxia source. -- 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-236) multi module reporting - main page doesn't show links to contained modules
[ http://jira.codehaus.org/browse/MSITE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-236: -- Component/s: multi module > multi module reporting - main page doesn't show links to contained modules > -- > > Key: MSITE-236 > URL: http://jira.codehaus.org/browse/MSITE-236 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module >Reporter: Jan Vissers > > In a multi module project, the "site" generates a main page index.html, which > has the contained modules on the upper left hand corner in bold face. These > should be hyperlinks to the actual module's index.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: (MSITE-210) DoxiaFilter does not set output encoding
[
http://jira.codehaus.org/browse/MSITE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MSITE-210:
--
Component/s: encoding
> DoxiaFilter does not set output encoding
>
>
> Key: MSITE-210
> URL: http://jira.codehaus.org/browse/MSITE-210
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: encoding
>Affects Versions: 2.0-beta-5, 2.0-beta-6
>Reporter: Darius
> Attachments: MSITE-DoxiaFilter-patch.txt
>
>
> As mentioned in [MSITE-19|/browse/MSITE-19#action_75188] DoxiaFilter does not
> set any output encoding. In my situation this makes {{site:run}} goal pretty
> much useless.
> Attaching a patch for trunk.
--
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-169) links to modules where not working if a modules dir is used
[ http://jira.codehaus.org/browse/MSITE-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-169: -- Component/s: multi module > links to modules where not working if a modules dir is used > --- > > Key: MSITE-169 > URL: http://jira.codehaus.org/browse/MSITE-169 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module >Affects Versions: 2.0-beta-4, 2.0-beta-5, 2.0-beta-6 >Reporter: Mathias Brökelmann > Attachments: MNG-MSITE-169-maven-site-plugin.patch > > > I've to place the modules into a separate directory: > root/ > ..pom.xml > ..modules/ > module1 > module2 > this is supported by maven through > > modules/module1 > modules/module2 > > in pom. > but the site generation seems to be broken: > if mvn site-deploy is used the links to the modules contain > modules/module1/index.html which is ok but unfortunately the generated site > structure will be generated as follows: > root/ > ..module1 > ..module2 > The result is that the links do not work. > If I run mvn site-stage everything looks ok. The links doesn't contain > modules dir anymore and eveything is working. -- 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-131) Not inheriting the site settings for distributionManagement from a super pom
[ http://jira.codehaus.org/browse/MSITE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-131: -- Component/s: inheritance > Not inheriting the site settings for distributionManagement from a super pom > > > Key: MSITE-131 > URL: http://jira.codehaus.org/browse/MSITE-131 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: inheritance >Reporter: Malcolm Wong Ho > -- 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-184) Provide possibility to expand Project Reports menu
[ http://jira.codehaus.org/browse/MSITE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-184: -- Component/s: site descriptor > Provide possibility to expand Project Reports menu > -- > > Key: MSITE-184 > URL: http://jira.codehaus.org/browse/MSITE-184 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Components: site descriptor >Reporter: Damien Lecan > > By default, "Project Reports" menu is collapsed. > The site.xml file could allow user to specify if this menu has to be > collapsed or not : > > This will expand "Project Reports" and "Project Information" together. > Doxia doesn't seem to provide a such feature (MenuItem can be collapsed, but > "reports" is a Menu, not a MenuItem) -- 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-162) maven -N site does not generate index.html
[ http://jira.codehaus.org/browse/MSITE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-162: -- Component/s: multi module > maven -N site does not generate index.html > -- > > Key: MSITE-162 > URL: http://jira.codehaus.org/browse/MSITE-162 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module > Environment: solaris 8 >Reporter: Andrew Williams >Assignee: Brett Porter > > when using maven -N (through continuum) I run the site goal (and site:deploy) > but it fails to generate index.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: (MSITE-3) site adds relative paths to css, etc, but doesn't work for error documents
[ http://jira.codehaus.org/browse/MSITE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-3: Component/s: relative links > site adds relative paths to css, etc, but doesn't work for error documents > -- > > Key: MSITE-3 > URL: http://jira.codehaus.org/browse/MSITE-3 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Reporter: Brett Porter > Fix For: 2.0-beta-7 > > > we should possibly use the absolute urls for these anyway. -- 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-209) populateModulesMenu() logic results in invalid modules list if projects share artifactIds
[
http://jira.codehaus.org/browse/MSITE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MSITE-209:
--
Component/s: multi module
> populateModulesMenu() logic results in invalid modules list if projects share
> artifactIds
> -
>
> Key: MSITE-209
> URL: http://jira.codehaus.org/browse/MSITE-209
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 2.0-beta-5, 2.0-beta-6
>Reporter: John Allen
>Priority: Critical
> Attachments: site-patch.diff, site-patch.diff
>
>
> populateModulesMenu() logic should compare groupIds as well as artifactIds.
> Failure to do so can result in invalid modules list being generated when the
> reactorProject.getParent().getArtifectId() is the same as the current project
> but is not of the same group. Logic should be (dont have the code available
> as its on my laptop), oh go on then Ill HTTP the source
> private void populateModulesMenuItemsFromReactorProjects( Menu menu )
> {
> [SNIP]
> if ( reactorProject != null && reactorProject.getParent() !=
> null &&
> project.getArtifactId().equals(
> reactorProject.getParent().getArtifactId() ) )
> {
> String reactorUrl = reactorProject.getUrl();
> String name = reactorProject.getName();
> appendMenuItem( menu, name, reactorUrl,
> reactorProject.getArtifactId() );
> }
> }
> }
> }
> Comparison should also check that the groupId of the reactorProject's parent
> matches our groupId.
> Clear?.. Sorry, the patch on my laptop too...
--
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-174) Default bundle used not correct
[
http://jira.codehaus.org/browse/MSITE-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MSITE-174:
--
Component/s: internationalization
> Default bundle used not correct
> ---
>
> Key: MSITE-174
> URL: http://jira.codehaus.org/browse/MSITE-174
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: internationalization
> Environment: trunk, french os
>Reporter: Vincent Siveton
>
> Using this configuration, MSITE produces only french reports:
> {code:xml}
>
> fr,en
>
> {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: (MSITE-237) Empty modules list generated when using '--non-recursive' flag for single module projects
[
http://jira.codehaus.org/browse/MSITE-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MSITE-237:
--
Component/s: multi module
> Empty modules list generated when using '--non-recursive' flag for single
> module projects
> -
>
> Key: MSITE-237
> URL: http://jira.codehaus.org/browse/MSITE-237
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 2.0-beta-5
>Reporter: Fernando Lindner
>Priority: Critical
> Attachments: sample-project.zip
>
>
> Using '--non-recursive' flag for a single module project causes site's
> modules list to be empty.
> When starting a new project it's usual to have just one module for a while.
> It seems to be a problem in *org.apache.maven.plugins.site.AbstractSiteMojo"
> class, inside {{populateModulesMenuItemsFromModels}} method, when
> {{models.size()}} is checked.
> {code:title=AbstractSiteMojo.java|borderStyle=solid}
> ...
> private void populateModulesMenuItemsFromModels( List models, Menu menu )
> {
> if ( models != null && models.size() > 1 )
> {
> Iterator reactorItr = models.iterator();
> while ( reactorItr.hasNext() )
> {
> Model model = (Model) reactorItr.next();
> String reactorUrl = model.getUrl();
> String name = model.getName();
> appendMenuItem( menu, name, reactorUrl, model.getArtifactId()
> );
> }
> }
> }
> ...
> {code}
> A single project is attached, for testing purposes.
> No errors when omitting '--non-recursive' flag:
> {{mvn clean site}}
--
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-3176) Create a separate method in Maven component to create a topo sorted list of projects
[ http://jira.codehaus.org/browse/MNG-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-3176. -- Resolution: Fixed DefaultMaven has been changed to provide a method to give the reactor manager. > Create a separate method in Maven component to create a topo sorted list of > projects > > > Key: MNG-3176 > URL: http://jira.codehaus.org/browse/MNG-3176 > Project: Maven 2 > Issue Type: Task > Components: Embedding >Affects Versions: 2.1.x >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > This method would then be used for execution and for use in the embedder's > buildWithDependencies method. This helps IDE integrators by getting the set > of projects that can be imported by grabbing a parent POM but also gives them > the correct order to process them. In IDEA a module must exist before it can > be referenced by another during creation. So having the sort order is > necessary not only for execution and building, but for operations like > importing a set of new projects. -- 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-3176) Create a separate method in Maven component to create a topo sorted list of projects
[ http://jira.codehaus.org/browse/MNG-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106209 ] Jason van Zyl commented on MNG-3176: For the time being I've changed this to a method to give me the ReactorManager as the ReactorManager is doing to many things. It doesn't need to have the build success reported to it as this can be done with the session. The reactor manager should go no further then DefaultMaven. It doesn't need to manage blacklists or build times. Again the session can do this. All we need is execute( session). > Create a separate method in Maven component to create a topo sorted list of > projects > > > Key: MNG-3176 > URL: http://jira.codehaus.org/browse/MNG-3176 > Project: Maven 2 > Issue Type: Task > Components: Embedding >Affects Versions: 2.1.x >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > This method would then be used for execution and for use in the embedder's > buildWithDependencies method. This helps IDE integrators by getting the set > of projects that can be imported by grabbing a parent POM but also gives them > the correct order to process them. In IDEA a module must exist before it can > be referenced by another during creation. So having the sort order is > necessary not only for execution and building, but for operations like > importing a set of new projects. -- 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-118) Provide a schema for site.xml
[ http://jira.codehaus.org/browse/MSITE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-118: -- Component/s: site descriptor > Provide a schema for site.xml > - > > Key: MSITE-118 > URL: http://jira.codehaus.org/browse/MSITE-118 > Project: Maven 2.x Site Plugin > Issue Type: Wish > Components: site descriptor >Affects Versions: 2.0-beta-5 >Reporter: Wendy Smoak >Assignee: Dennis Lundberg >Priority: Minor > Fix For: 2.0-beta-7 > > > Brett mentioned that a schema for site.xml will be available with > maven-site-plugin 2.0 final. Just logging a reminder issue as I don't see it > in svn or at http://maven.apache.org/xsd/ . > http://mail-archives.apache.org/mod_mbox/maven-users/200602.mbox/[EMAIL > PROTECTED] -- 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-195) Module navigation entries point to index.html not /index.html
[ http://jira.codehaus.org/browse/MSITE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-195: -- Component/s: multi module > Module navigation entries point to index.html not /index.html > - > > Key: MSITE-195 > URL: http://jira.codehaus.org/browse/MSITE-195 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module > Environment: Intel box running Windows XP >Reporter: Dale Chapman >Priority: Minor > > I am using Maven version 2.0.4 > I am experimenting with Maven to see if it will suit my organizations needs > and I have created a simple example that looks like the following: > App1Pom > + App1Ear > + App1Jar > (pom.xml snippet) > > App1Ear > App1Jar > > When I generate the site using mvn site, the "About" page for App1Pom shows > the two modules in the module section of the navigation, but neither has an > anchor. When I navigate to another section, both module entries will now > contain an anchor that points to index.html. > (index.html snippet) > Modules > > > > App1Ear > > > > App1Jar > > > (project-info.html snippet) > Modules > > > > App1Ear > > > > App1Jar > > > When I generate the site using mvn site:stage, the navigation section > contains the correct entries of App1Ear/index.html and App1Jar/index.html. > (index.html snippet) > Modules > > > > App1Ear > > > > App1Jar > > > I have tried to review the current bug list to see if this problem has > already been reported, but I was not able to see an entry that describes this > situation. If I have a usage problem please point me to some documentation > that can help me understand. > Thanks. > Dale Chapman. -- 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-129) modules list empty if modules don't use this project as parent in reactor build
[
http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MSITE-129:
--
Component/s: multi module
> modules list empty if modules don't use this project as parent in reactor
> build
> ---
>
> Key: MSITE-129
> URL: http://jira.codehaus.org/browse/MSITE-129
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 2.0-beta-5
>Reporter: Kenney Westerhof
>Assignee: Kenney Westerhof
>Priority: Minor
> Fix For: 2.0-beta-7
>
>
> The code in the AbstractSiteRenderingMojo does the following:
> - if it's running in a reactor build (i.e. more than 1 project in the reactor
> projects) it scans all
> projects to see if it's parent project equals the current project. If so,
> it's marked as a module.
> - if it's running on a single project, the project.build.modules is consulted
> and those modules
> are marked as modules.
> I've got a 'fake' root pom, for utility purposes: it lists all projects as
> modules so that I can easily
> built everything and generate a site. However, this fake root pom is never
> used as a parent - there's
> a /pom/pom.xml project for that.
> The result of this is that the modules list is empty.
> A workaround is to first run 'mvn site' and then 'mvn site -N'.
> I'm not sure what the correct solution should be - basically now 2 site
> layouts are implemented:
> - a physical layout where the modules match the section of the pom,
> reflecting filesystem layout,
> - a project hierarchy layout based on
> and one or the other is used depending on wheter the build contains more than
> 1 project or not.
> My first feeling is that since the tag is called ${modules} (or ref="modules"/>) that
> the site should use the , not the .
> It should also take into consideration, that IF a reactor build is running,
> it should only use the modules that are also
> in the reactor (so you can use -r -Dmaven.reactor.excludes=.. to generate a
> site with not all projects in it).
> Thoughts?
--
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-123) Output encoding is UTF-8 despite outputEncoding is set to ISO-8859-1
[ http://jira.codehaus.org/browse/MSITE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-123: -- Component/s: encoding > Output encoding is UTF-8 despite outputEncoding is set to ISO-8859-1 > > > Key: MSITE-123 > URL: http://jira.codehaus.org/browse/MSITE-123 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: encoding > Environment: SuSE Linux 10.0. LANG=sv_SE.ISO-8859-1 >Reporter: Anders Heintz >Priority: Minor > > When I generate the site containing xdocs with swedish characters (åäö), the > browser shows corrupted characters, and after investigation I found that the > output HTML-files are actually encoded using UTF-8. > If I change the outputEncoding to UTF-8, it works ok. Since all documentation > states that default encoding for everything(?) is ISO-8859-1, it should > perhaps be corrected. -- 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-229) Links in site.xml get translated to ../../../
[ http://jira.codehaus.org/browse/MSITE-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-229: -- Component/s: relative links > Links in site.xml get translated to ../../../ > - > > Key: MSITE-229 > URL: http://jira.codehaus.org/browse/MSITE-229 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 2.0-beta-5 > Environment: Linux FC6 Sun Java (build 1.5.0_10-b03, mixed mode, > sharing) >Reporter: Mykel Alvis >Priority: Minor > Attachments: site.xml > > > In Site.xml for a project (that has a parent POM) > > http://sirdsite.dsths.ad.dstcorp.net/"; /> > http://www.apache.org/"; /> > http://maven.apache.org/maven2/"/> > > Gets rendered as > > SIRD Site > | > http://www.apache.org/";>Apache > | > http://maven.apache.org/maven2/";>Maven 2 > > " http://sirdsite.dsths.ad.dstcorp.net/"; != "../../.." -- 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-224) [PATCH] please make UTF-8 the default encoding
[ http://jira.codehaus.org/browse/MSITE-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-224: -- Component/s: encoding > [PATCH] please make UTF-8 the default encoding > -- > > Key: MSITE-224 > URL: http://jira.codehaus.org/browse/MSITE-224 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Components: encoding > Environment: Gentoo Linux, UTF-8 encoded pom files >Reporter: Petr Kozelka >Priority: Minor > Attachments: site-plugin-UTF8-encoding.patch > > > UTF-8 is already widely supported and used by tools, there is hardly a reason > to keep with ISO-8859-1 found through the code. > In my usecases, it typically makes troubles with developer names containing > accented letters. > Attached patch changes the default input and output encoding in > maven-site-plugin which is the most important piece. -- 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-251) tr locale support
[ http://jira.codehaus.org/browse/MSITE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-251: -- Component/s: localization > tr locale support > - > > Key: MSITE-251 > URL: http://jira.codehaus.org/browse/MSITE-251 > Project: Maven 2.x Site Plugin > Issue Type: New Feature > Components: localization > Environment: Windows XP >Reporter: gulcan yalcinkaya >Priority: Trivial > Attachments: project-info-report_tr.properties, > site-plugin_tr.properties > > -- 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-197) poweredBy Logo links don't work
[ http://jira.codehaus.org/browse/MSITE-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-197: -- Component/s: relative links > poweredBy Logo links don't work > --- > > Key: MSITE-197 > URL: http://jira.codehaus.org/browse/MSITE-197 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 2.0-beta-5 >Reporter: Henning Schmiedehausen >Priority: Minor > > I added the following poweredBy Item to my site: > >href="http://velocity.apache.org"; > img="/images/pbv90x30.png" /> > > This gets rendered out to > > src="images/pbv90x30.png" /> > > > The href link is empty. When debugging, it seems that any URL given to the > logo href attribute gets silently removed. Using href="foobar" works, > href="http://www.apache.org/"; does not. -- 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-226) Missing escaping of ${project.name} for default site descriptor
[
http://jira.codehaus.org/browse/MSITE-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MSITE-226:
--
Component/s: site descriptor
> Missing escaping of ${project.name} for default site descriptor
> ---
>
> Key: MSITE-226
> URL: http://jira.codehaus.org/browse/MSITE-226
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.0-beta-6
> Environment: linux, maven-2.0.6
>Reporter: Petr Kozelka
>Priority: Minor
>
> It seems that when using the default site descriptor, no xml escaping is
> performed for name (and maybe other values).
> Excerpt from {{pom.xml}}:
> {quote}
> ...
> Module "MyMod-1.0"
> ...
> {quote}
> Excerpt from build log:
> {quote}
> ...
> [INFO] Error parsing site descriptor
> Embedded error: expected = after attribute name (position: START_DOCUMENT
> seen ...ations\nunder the License.\n-->\n\n [INFO]
>
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error parsing site
> descriptor
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> ...
> {quote}
--
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-247) Site generation does not inherit element from parent site.xml
[ http://jira.codehaus.org/browse/MSITE-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-247: -- Component/s: inheritance > Site generation does not inherit element from parent site.xml > --- > > Key: MSITE-247 > URL: http://jira.codehaus.org/browse/MSITE-247 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: inheritance >Affects Versions: 2.0-beta-5 > Environment: WinXP-SP2, JDK 1.5.0_12, Maven 2.0.7 >Reporter: Benjamin Bentmann >Priority: Minor > > I have a parent project of a multi-module project whose site.xml contains > > > The element is properly inherited by the site descriptors of > the module POMs, but the element gets dropped so that one needs to > manually add it to each site.xml for the modules. -- 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
