[jira] Closed: (MNG-2228) Classloader problem loading jars from build extensions
[ http://jira.codehaus.org/browse/MNG-2228?page=all ] Brett Porter closed MNG-2228. - Resolution: Fixed > Classloader problem loading jars from build extensions > -- > > Key: MNG-2228 > URL: http://jira.codehaus.org/browse/MNG-2228 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4 >Reporter: Carlos Sanchez > Assigned To: Brett Porter >Priority: Blocker > Fix For: 2.0.5 > > Attachments: MNG-2228.tgz > > > When running "mvn install" and "mvn testwagonscm:test" in the attached test > case you get a ClassCastException although the Class to assign to and the > assigned one are the same. The problem seems to be that they come from > different classloaders. This problem makes the project-info-report:scm goal > fail. > Same as MNG-2225, but using build extensions instead of jars in M2_HOME -- 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-2692) Classworlds launcher can't be found
[ http://jira.codehaus.org/browse/MNG-2692?page=all ] Brett Porter closed MNG-2692. - Assignee: Brett Porter Resolution: Fixed Fix Version/s: 2.1 applied, thanks > Classworlds launcher can't be found > --- > > Key: MNG-2692 > URL: http://jira.codehaus.org/browse/MNG-2692 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1 > Environment: Windows XP >Reporter: Mike Henry > Assigned To: Brett Porter > Fix For: 2.1 > > Attachments: MNG.patch > > > My *first ever* bug report to an open source project! (be gentle, please :-) > Having built Maven 2.1-SNAPSHOT using Maven and a clean repository, I get the > following error: > C:\maven\components\maven-cli>mvn -v > Exception in thread "main" java.lang.NoClassDefFoundError: > org/codehaus/plexus/classworlds/launcher/Launcher > Resolved to change reference to classworlds jar in mvn.bat to > plexus-classwords jar. Patch to mvn.bat included. > Unsure as the priority of this issue. As it is Maven 2.1 can't be run on > Windows without this change. Is this considered a "blocker"? -- 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-2699) 2.1 mvn.bat is broken because classworlds was renamed (patch attached)
[ http://jira.codehaus.org/browse/MNG-2699?page=all ] Brett Porter closed MNG-2699. - Assignee: Brett Porter Resolution: Fixed > 2.1 mvn.bat is broken because classworlds was renamed (patch attached) > -- > > Key: MNG-2699 > URL: http://jira.codehaus.org/browse/MNG-2699 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.1 >Reporter: Brian Fox > Assigned To: Brett Porter >Priority: Blocker > Attachments: mvnbat.patch > > > No karma in core, only plugins so here's the patch. The line was looking for > classworlds-* when it's now plexus-classworlds-* -- 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-2700) Exception in thread "main" java.lang.NoClassDefFoundError: org/codehaus/plexus/classworlds/launcher/Launcher
[ http://jira.codehaus.org/browse/MNG-2700?page=all ] Brett Porter closed MNG-2700. - Resolution: Duplicate > Exception in thread "main" java.lang.NoClassDefFoundError: > org/codehaus/plexus/classworlds/launcher/Launcher > > > Key: MNG-2700 > URL: http://jira.codehaus.org/browse/MNG-2700 > Project: Maven 2 > Issue Type: Bug > Components: Bootstrap & Build >Affects Versions: 2.1 > Environment: Windows XP - Sun JDK 1.5.09 >Reporter: Francesco Tinti >Priority: Blocker > > trying to use mvn give the exception message reported in summay. after a > bootstrap build of code with Ant (subversion revision number 486140). -- 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-2740) maven-core has compile errors under src/test
maven-core has compile errors under src/test Key: MNG-2740 URL: http://jira.codehaus.org/browse/MNG-2740 Project: Maven 2 Issue Type: Bug Components: Bootstrap & Build Affects Versions: 2.1 Environment: -r492039 Reporter: Franz Allan Valencia See I tried building with both maven-2.0.4 and maven-2.1-SNAPSHOT to no avail [INFO] [compiler:testCompile] Compiling 5 source files to D:\sources\maven\components\maven-core\target\test-classes [INFO] Error for project: Maven Core (during install) [INFO] [INFO] Compilation failure D:\sources\maven\components\maven-core\src\test\java\org\apache\maven\plugin\PluginParameterExpressionEvaluatorTest.java:[202,33] cannot find symbol symbol : constructor ReactorManager(java.util.List) location: class org.apache.maven.execution.ReactorManager -- 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-1105) Duplicate email notifications with notifier in pom.xml
Duplicate email notifications with notifier in pom.xml -- Key: CONTINUUM-1105 URL: http://jira.codehaus.org/browse/CONTINUUM-1105 Project: Continuum Issue Type: Bug Components: Notifier - Mail Affects Versions: 1.1 Reporter: Wendy Smoak When there is a notifier in the pom, and a group of projects (such as maven/plugins/trunk/pom.xml) is added under the groupId in the pom, the notifier shows up at the project group level, and on each project. This causes every notification email to be duplicated. 20070102 IRC conversation about adding maven/plugins/trunk/pom.xml under various groupIds: what could make continuum send duplicate emails? I've added and deleted all of maven/plugins/trunk/pom.xml a few times under different project groups. When I add it under the pom default org.apache.maven.plugins group, I get duplicate emails for every build. wsmoak, have you verified that there are not duplicate entries for emails in the build defs? I used to get duplicates when I belonged to an distribution-list and a direct email address. joakim: there is only the default build definition, and admin is the only member of the group wsmoak: I think we look at project group notifiers too when we look at project notifier, so we get the project group notifier twice when we send the mail it only happens when I add the projects under the pom default group id. If I delete and re-add it to some other group, I only get one email. yes, because, when you use the default project group, project notifiers are moved to the project group but I think they aren't removed in the project okay. and it's only happening with maven/plugins because struts, etc. doesn't have notifiers in the pom. >From the log file (email addresses changed...): INFO | jvm 1| 2007/01/02 20:16:39 | 2007-01-02 20:16:39,831 [pool-1-thread-1] INFO ShellCommandHelper:default - Executing: mvn --batch-mode --non-recursive clean install INFO | jvm 1| 2007/01/02 20:16:39 | 2007-01-02 20:16:39,831 [pool-1-thread-1] INFO ShellCommandHelper:default - Working directory: /opt/continuum-1.1-r490629-SNAPSHOT/apps/continuum/webapp/WEB-INF/working-directory/7 INFO | jvm 1| 2007/01/02 20:16:41 | 2007-01-02 20:16:41,660 [pool-1-thread-1] INFO ContinuumBuildExecutor:maven2 - Exit code: 1 INFO | jvm 1| 2007/01/02 20:16:41 | 2007-01-02 20:16:41,944 [pool-1-thread-1] INFO BuildController:default- Performing action deploy-artifact INFO | jvm 1| 2007/01/02 20:16:42 | 2007-01-02 20:16:42,072 [pool-1-thread-1] INFO Notifier:mail - Sending message: From '"[EMAIL PROTECTED]" <[EMAIL PROTECTED]>'. INFO | jvm 1| 2007/01/02 20:16:42 | 2007-01-02 20:16:42,072 [pool-1-thread-1] INFO Notifier:mail - Recipient: To '<[EMAIL PROTECTED]>'. INFO | jvm 1| 2007/01/02 20:16:42 | 2007-01-02 20:16:42,337 [pool-1-thread-1] INFO Notifier:mail - Sending message: From '"[EMAIL PROTECTED]" <[EMAIL PROTECTED]>'. INFO | jvm 1| 2007/01/02 20:16:42 | 2007-01-02 20:16:42,337 [pool-1-thread-1] INFO Notifier:mail - Recipient: To '<[EMAIL PROTECTED]>'. Either * the 'add project' logic should remove the notifier from projects if it is added at the group level, or * Continuum should filter out duplicate recipients before sending. -- 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: (CONTINUUM-841) Notifier get duplicated during builds
[ http://jira.codehaus.org/browse/CONTINUUM-841?page=comments#action_83881 ] Wendy Smoak commented on CONTINUUM-841: --- Looks like a duplicate of CONTINUUM-678 (and I do not see this behavior in 1.1-SNAPSHOT) > Notifier get duplicated during builds > - > > Key: CONTINUUM-841 > URL: http://jira.codehaus.org/browse/CONTINUUM-841 > Project: Continuum > Issue Type: Bug > Components: Notification Subsystem >Affects Versions: 1.0.3 > Environment: maven 1.1-beta3 on Windows 2000 / JDK 5 >Reporter: nicolas de loof > Fix For: 1.1 > > Attachments: wrapper.log > > > I receive my failure mail 12 times. Looking at the project configuration in > continuum, my notifier eMail is registered 12 times. I delete all and > register a fresh new email account. After some (failed) builds, it gets > duplicated as notifier. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-128) SCM properties being replaced during release:perform
[ http://jira.codehaus.org/browse/MRELEASE-128?page=comments#action_83880 ]
Baerrach bonDierne commented on MRELEASE-128:
-
I'm experiencing the same problem but with ${user.name}
{noformat}
scm:cvs:pserver:[EMAIL PROTECTED]:/cvs/CVS_ROOT:PROJECT_DIR
{noformat}
where the tagged release value is correct but the transformed version for the
next snapshot is incorrect as $[user.name}
has been expanded to be the current users name.
This doesn't look like it is fixed by reading the patch attached to
MRELEASE-114.
> SCM properties being replaced during release:perform
>
>
> Key: MRELEASE-128
> URL: http://jira.codehaus.org/browse/MRELEASE-128
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
>Reporter: Craig Dickson
> Assigned To: Jason van Zyl
> Fix For: 2.0-beta-5
>
> Attachments: after-release-perform-pom.xml,
> after-release-prepre-pom.xml, original-pom.xml
>
>
> The section of a pom in CVS for a pom archetype project looks like this
> prior to executing release:prepare :
>
> ${base.cvs.url}:commons-maven/uber-pom
>
> ${base.cvs.url}:commons-maven/uber-pom
> ${base.viewcvs.url}/commons-maven/uber-pom
>
> Then after executing release:prepare, the pom in CVS looks like this (new
> tag is only difference):
>
> ${base.cvs.url}:commons-maven/uber-pom
>
> ${base.cvs.url}:commons-maven/uber-pom
> ${base.viewcvs.url}/commons-maven/uber-pom
> R-1_7
>
> Then after executing release:perform, the pom looks like this in CVS:
>
>
> scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom
>
> scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom
>
> http://behrcvs.masco-coatings.com/cgi-bin/viewcvs.cgi/commons-maven/uber-pom
>
> Notice that the properties that were there for the base URLs for CVS and
> ViewCVS have been replaced with literal values.
> No other properties in the POM are being replaced
--
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: (DOXIA-29) APT - local anchor doesn't work
[ http://jira.codehaus.org/browse/DOXIA-29?page=comments#action_83876 ]
Brian Fox commented on DOXIA-29:
I see this too. The section isn't an anchor and {{anchor}} generates a link to
/site/anchor instead of /site/page#anchor. {{#anchor}} does work however.
> APT - local anchor doesn't work
> ---
>
> Key: DOXIA-29
> URL: http://jira.codehaus.org/browse/DOXIA-29
> Project: doxia
> Issue Type: Bug
>Affects Versions: 1.0-alpha-5
> Environment: Using maven 2.0 on windows XP
>Reporter: Olivier Berlanger
> Assigned To: Emmanuel Venisse
>Priority: Minor
> Fix For: 1.0-alpha-8
>
>
> In APT documents, the local anchor definition {anchor} and references
> {{anchor}} are not correctly processed.
> Also, there is no anchor generated automatically for section titles (as
> mentionned in APT doc)
> Sample page : http://doxia.codehaus.org/format.html
> --> try to click on the only internal link named "document structure" it has
> been generated as an external link.
--
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: (CONTINUUM-1030) Build for official release leaves a dirty working copy if it fails
[ http://jira.codehaus.org/browse/CONTINUUM-1030?page=all ] Work on CONTINUUM-1030 started by Edwin Punzalan. > Build for official release leaves a dirty working copy if it fails > -- > > Key: CONTINUUM-1030 > URL: http://jira.codehaus.org/browse/CONTINUUM-1030 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Assigned To: Edwin Punzalan >Priority: Critical > Fix For: 1.1 > > > if release breaks after modyfing the pom the working copy is left dirty, with > a modified pom and you can't release again, it complains with "pom is not > snapshot" -- 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: (MDEP-52) excludeScope="provided" is not working correctly
[ http://jira.codehaus.org/browse/MDEP-52?page=all ] Brian Fox updated MDEP-52: -- Fix Version/s: 2.0-alpha-1 > excludeScope="provided" is not working correctly > > > Key: MDEP-52 > URL: http://jira.codehaus.org/browse/MDEP-52 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug >Affects Versions: 2.0-alpha-1 >Reporter: Chris Love > Assigned To: Brian Fox > Fix For: 2.0-alpha-1 > > Attachments: patch.txt, ut-patch.txt > > > The option excludeScope="provided" does not filter correctly. Please see > attached patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MDEP-52) excludeScope="provided" is not working correctly
[ http://jira.codehaus.org/browse/MDEP-52?page=all ] Brian Fox closed MDEP-52. - Resolution: Fixed Fixed. I found where the scopefilter test was deficient and failed that and added tests to cover excluding all the scopes in both copy and unpack. > excludeScope="provided" is not working correctly > > > Key: MDEP-52 > URL: http://jira.codehaus.org/browse/MDEP-52 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug >Affects Versions: 2.0-alpha-1 >Reporter: Chris Love > Assigned To: Brian Fox > Attachments: patch.txt, ut-patch.txt > > > The option excludeScope="provided" does not filter correctly. Please see > attached patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPXDOC-203) New 'Built by Maven' logos - default changed
[ http://jira.codehaus.org/browse/MPXDOC-203?page=all ] Arnaud Heritier closed MPXDOC-203. -- Resolution: Fixed Done > New 'Built by Maven' logos - default changed > > > Key: MPXDOC-203 > URL: http://jira.codehaus.org/browse/MPXDOC-203 > Project: maven-xdoc-plugin > Issue Type: Improvement >Affects Versions: 1.10 >Reporter: Arnaud Heritier > Assigned To: Arnaud Heritier >Priority: Trivial > Fix For: 1.10.1 > > Attachments: mavenlogo_builtby_b.png, mavenlogo_builtby_w.png > > > New logos are taken from m2 (DOXIA-84). -- 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: (MPXDOC-203) New 'Built by Maven' logos - default changed
[ http://jira.codehaus.org/browse/MPXDOC-203?page=all ] Arnaud Heritier updated MPXDOC-203: --- Attachment: (was: mavenlogo_builtby_t.png) > New 'Built by Maven' logos - default changed > > > Key: MPXDOC-203 > URL: http://jira.codehaus.org/browse/MPXDOC-203 > Project: maven-xdoc-plugin > Issue Type: Improvement >Affects Versions: 1.10 >Reporter: Arnaud Heritier > Assigned To: Arnaud Heritier >Priority: Trivial > Fix For: 1.10.1 > > Attachments: mavenlogo_builtby_b.png, mavenlogo_builtby_w.png > > > New logos are taken from m2 (DOXIA-84). -- 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: (MPXDOC-203) New 'Built by Maven' logos - default changed
[ http://jira.codehaus.org/browse/MPXDOC-203?page=all ] Arnaud Heritier updated MPXDOC-203: --- Attachment: mavenlogo_builtby_w.png 90 by 30 pixels - white > New 'Built by Maven' logos - default changed > > > Key: MPXDOC-203 > URL: http://jira.codehaus.org/browse/MPXDOC-203 > Project: maven-xdoc-plugin > Issue Type: Improvement >Affects Versions: 1.10 >Reporter: Arnaud Heritier > Assigned To: Arnaud Heritier >Priority: Trivial > Fix For: 1.10.1 > > Attachments: mavenlogo_builtby_b.png, mavenlogo_builtby_t.png, > mavenlogo_builtby_w.png > > > New logos are taken from m2 (DOXIA-84). -- 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: (MPXDOC-203) New 'Built by Maven' logos - default changed
[ http://jira.codehaus.org/browse/MPXDOC-203?page=all ] Arnaud Heritier updated MPXDOC-203: --- Attachment: mavenlogo_builtby_t.png 90 by 30 pixels - transparent > New 'Built by Maven' logos - default changed > > > Key: MPXDOC-203 > URL: http://jira.codehaus.org/browse/MPXDOC-203 > Project: maven-xdoc-plugin > Issue Type: Improvement >Affects Versions: 1.10 >Reporter: Arnaud Heritier > Assigned To: Arnaud Heritier >Priority: Trivial > Fix For: 1.10.1 > > Attachments: mavenlogo_builtby_b.png, mavenlogo_builtby_t.png > > > New logos are taken from m2 (DOXIA-84). -- 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: (MPXDOC-203) New 'Built by Maven' logos - default changed
[ http://jira.codehaus.org/browse/MPXDOC-203?page=all ] Arnaud Heritier updated MPXDOC-203: --- Attachment: mavenlogo_builtby_b.png 90 by 30 pixels - black > New 'Built by Maven' logos - default changed > > > Key: MPXDOC-203 > URL: http://jira.codehaus.org/browse/MPXDOC-203 > Project: maven-xdoc-plugin > Issue Type: Improvement >Affects Versions: 1.10 >Reporter: Arnaud Heritier > Assigned To: Arnaud Heritier >Priority: Trivial > Fix For: 1.10.1 > > Attachments: mavenlogo_builtby_b.png, mavenlogo_builtby_t.png > > > New logos are taken from m2 (DOXIA-84). -- 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: (MPXDOC-203) New 'Built by Maven' logos - default changed
New 'Built by Maven' logos - default changed Key: MPXDOC-203 URL: http://jira.codehaus.org/browse/MPXDOC-203 Project: maven-xdoc-plugin Issue Type: Improvement Affects Versions: 1.10 Reporter: Arnaud Heritier Assigned To: Arnaud Heritier Priority: Trivial Fix For: 1.10.1 New logos are taken from m2 (DOXIA-84). -- 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: (MDEP-52) excludeScope="provided" is not working correctly
[ http://jira.codehaus.org/browse/MDEP-52?page=all ] Chris Love updated MDEP-52: --- Attachment: ut-patch.txt This test case should show the symptoms of the patch > excludeScope="provided" is not working correctly > > > Key: MDEP-52 > URL: http://jira.codehaus.org/browse/MDEP-52 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug >Affects Versions: 2.0-alpha-1 >Reporter: Chris Love > Assigned To: Brian Fox > Attachments: patch.txt, ut-patch.txt > > > The option excludeScope="provided" does not filter correctly. Please see > attached patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-52) excludeScope="provided" is not working correctly
excludeScope="provided" is not working correctly Key: MDEP-52 URL: http://jira.codehaus.org/browse/MDEP-52 Project: Maven 2.x Dependency Plugin Issue Type: Bug Affects Versions: 2.0-alpha-1 Reporter: Chris Love Assigned To: Brian Fox Attachments: patch.txt The option excludeScope="provided" does not filter correctly. Please see attached patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1104) Allow user to choose multiple projects for deletion and delete in one step.
Allow user to choose multiple projects for deletion and delete in one step. --- Key: CONTINUUM-1104 URL: http://jira.codehaus.org/browse/CONTINUUM-1104 Project: Continuum Issue Type: Improvement Components: Web - UI, Web interface Affects Versions: 1.0.3 Reporter: Rahul Thakur Have checkbox controls for each of the listed pojects (and subject to user/role permissions) to allow deleting multiple projects in one shot. -- 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: (DOXIA-84) Update of Maven Generated Sites to use 'Built by Maven' logo
[ http://jira.codehaus.org/browse/DOXIA-84?page=comments#action_83863 ] Arnaud Heritier commented on DOXIA-84: -- Ok, thanks a lot Natalie. I'll add them to m1 (I find them very nice) > Update of Maven Generated Sites to use 'Built by Maven' logo > > > Key: DOXIA-84 > URL: http://jira.codehaus.org/browse/DOXIA-84 > Project: doxia > Issue Type: Task >Reporter: Natalie Burdick > Attachments: mavenlogo_builtby_b.gif, mavenlogo_builtby_w.gif > > > Attached are some sample images, they would need to be resized to 90 by 30 > pixels 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] Commented: (DOXIA-84) Update of Maven Generated Sites to use 'Built by Maven' logo
[ http://jira.codehaus.org/browse/DOXIA-84?page=comments#action_83860 ] Natalie Burdick commented on DOXIA-84: -- Arnaud, Maven 1 is fine - thanks for asking > Update of Maven Generated Sites to use 'Built by Maven' logo > > > Key: DOXIA-84 > URL: http://jira.codehaus.org/browse/DOXIA-84 > Project: doxia > Issue Type: Task >Reporter: Natalie Burdick > Attachments: mavenlogo_builtby_b.gif, mavenlogo_builtby_w.gif > > > Attached are some sample images, they would need to be resized to 90 by 30 > pixels 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] Created: (CONTINUUM-1103) Build Fresh checkbox doesn't stay checked
Build Fresh checkbox doesn't stay checked - Key: CONTINUUM-1103 URL: http://jira.codehaus.org/browse/CONTINUUM-1103 Project: Continuum Issue Type: Bug Components: Web - UI Affects Versions: 1.1 Reporter: Wendy Smoak To reproduce: Project Groups -> [any group] -> Build Definitions tab 1. Edit a build definition 2. check the 'Build Fresh' checkbox 3. Save 4. Edit the same build definition The checkbox should remain checked, but it 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] Commented: (MRM-221) Webdav upload is not working
[ http://jira.codehaus.org/browse/MRM-221?page=comments#action_83850 ]
Joakim Erdfelt commented on MRM-221:
The URL in is invalid.
it should be in the format
dav:${protocol}://${hostname}:${port}/${archivaContext}/repository/${repositoryId}
So, assuming you have archiva installed as context '/archiva', the url above
should read as dav:http://localhost:9091/archiva/repository/maven_repository
See the webdav url and POM snippet in the managed repository for the proper URL
to be using.
( example found in the last image link on this blog
http://coderoshi.blogspot.com/2006/12/apache-archiva-part-one.html )
> Webdav upload is not working
>
>
> Key: MRM-221
> URL: http://jira.codehaus.org/browse/MRM-221
> Project: Archiva
> Issue Type: Bug
> Components: WebDAV interface
>Affects Versions: 1.0
> Environment: Mac OS X using the default jetty container. Jetty
> started with mvn jetty:run
>Reporter: Greg Luck
> Fix For: 1.0
>
>
> MRM-172 added webdav support. This is not working.
> I have everything working scping to the repository. webdav via Archiva does
> not work.
> When I use
>
>
>
>
>
> url="dav://localhost:9091/repository/maven_repository">
> password="###"/>
>
>
>
> I get
> upload-to-repository:
> [artifact:install-provider] Installing provider:
> org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-1
> [artifact:install-provider] Installing provider:
> org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-1
> [artifact:install] [INFO] Installing
> /Users/gluck/work/ehcache/trunk/target/dist/ehcache-1.2.4.jar to
> /m2repository/net/sf/ehcache/ehcache/1.2.4/ehcache-1.2.4.jar
> [artifact:deploy] Deploying to
> dav://localhost:9091/repository/maven_repository
> [artifact:deploy] WAGON_VERSION: 1.0-beta-1
> BUILD FAILED
> /Users/gluck/work/ehcache/trunk/build.xml:364:
> java.lang.IllegalArgumentException: id is null
> If I click on the webdav link from archiva I get:
> Error 404 Not Found
> Resource in error: http://localhost:9091/repository/LOCAL/maven_repository
> Exception details:
> it.could.webdav.DAVException: Not found
> at it.could.webdav.methods.HEAD.process(HEAD.java:52)
> at it.could.webdav.methods.GET.process(GET.java:58)
> at it.could.webdav.DAVProcessor.process(DAVProcessor.java:79)
> at
> org.apache.maven.archiva.web.servlet.repository.RepositoryAccess.servletRequest(RepositoryAccess.java:223)
> at
> org.apache.maven.archiva.web.servlet.PlexusComponentServlet.service(PlexusComponentServlet.java:126)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1049)
> at
> com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040)
> at
> com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
> at
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040)
> at
> com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:352)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:230)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
> at org.mortbay.jetty.Server.handle(Server.java:286)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:444)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:701)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:203)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:340)
> at
> org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the adminis
[jira] Closed: (CONTINUUM-1081) From build results, clicking Project Group Summary tab results in error
[ http://jira.codehaus.org/browse/CONTINUUM-1081?page=all ] Emmanuel Venisse closed CONTINUUM-1081. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1 > From build results, clicking Project Group Summary tab results in error > --- > > Key: CONTINUUM-1081 > URL: http://jira.codehaus.org/browse/CONTINUUM-1081 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1 >Reporter: Wendy Smoak > Assigned To: Emmanuel Venisse > Fix For: 1.1 > > Attachments: continuum-project-group-summary-tab-error.jpg > > > If you're viewing a build result, clicking on the 'Project Group Summary' tab > results in: > Error Occurred > org.apache.maven.continuum.ContinuumException: invalid group id > Show/hide Stack Trace > org.apache.maven.continuum.ContinuumException: invalid group id > at > org.apache.maven.continuum.DefaultContinuum.getProjectGroup(DefaultContinuum.java:213) > at > org.apache.maven.continuum.web.action.ProjectGroupAction.summary(ProjectGroupAction.java:108) > 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 > com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:364) > at > com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:216) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) > at > com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:168) > at > com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) > at > com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115) > at > com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) > at > org.apache.maven.continuum.web.interceptor.ForceContinuumConfigurationInterceptor.intercept(ForceContinuumConfigurationInterceptor.java:58) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) > at > org.codehaus.plexus.security.ui.web.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:157) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) > at > org.codehaus.plexus.security.ui.web.interceptor.AutoLoginInterceptor.intercept(AutoLoginInterceptor.java:83) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) > at > org.codehaus.plexus.security.ui.web.interceptor.ForceAdminUserInterceptor.intercept(ForceAdminUserInterceptor.java:61) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) > at > org.codehaus.plexus.security.ui.web.interceptor.EnvironmentCheckInterceptor.intercept(EnvironmentCheckInterceptor.java:123) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) > at > org.codehaus.plexus.xwork.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:62) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) > at > com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:168) > at > com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) > at > com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115) > at > com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) > at > com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) > at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) > at > com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) >
[jira] Closed: (CONTINUUM-1102) Navigation from "Build" and "Working Copy" page to "Project Group Summary" page does not work
[ http://jira.codehaus.org/browse/CONTINUUM-1102?page=all ] Emmanuel Venisse closed CONTINUUM-1102. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1 Applied > Navigation from "Build" and "Working Copy" page to "Project Group Summary" > page does not work > - > > Key: CONTINUUM-1102 > URL: http://jira.codehaus.org/browse/CONTINUUM-1102 > Project: Continuum > Issue Type: Bug > Components: Web interface, Web - UI >Affects Versions: 1.1 >Reporter: Franz Allan Valencia See > Assigned To: Emmanuel Venisse > Fix For: 1.1 > > Attachments: CONTINUUM-1102-continuum-webapp.patch > > > Steps to Reproduce: > 1. Log-in as admin > 2. Go to a project view page > 3. Go to the "Builds" page or "Working Copy" page ( by clicking on the > "Builds" or the "Working Copy" link ) > 4. Go to the "Project Group Summary" page ( by clicking on the "Project Group > Summary" link ) > Expected Result: > * User would be brought to the "Project Group Summary" page > Actual Result: > * An error page with the following error message - > "org.apache.maven.continuum.ContinuumException: invalid group id" -- 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: (CONTINUUM-1092) Test failures in DataManagementToolTest
[ http://jira.codehaus.org/browse/CONTINUUM-1092?page=comments#action_83814 ] thierry lach commented on CONTINUUM-1092: - It looks to me that the difference is in the line terminators. > Test failures in DataManagementToolTest > --- > > Key: CONTINUUM-1092 > URL: http://jira.codehaus.org/browse/CONTINUUM-1092 > Project: Continuum > Issue Type: Bug > Components: Testing >Affects Versions: 1.1 > Environment: WinXP, Cygwin, Continuum r490404 >Reporter: Wendy Smoak > Attachments: > org.apache.maven.continuum.management.DataManagementToolTest.txt, > org.apache.maven.continuum.management.DataManagementToolTest.txt > > > Seems like Brett fixed a similar problem in Modello, and I could build > Continuum for a while, but now something is wrong again. > --- > T E S T S > --- > Running org.apache.maven.continuum.management.DataManagementToolTest > Tests run: 3, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 6.734 sec <<< > FAILURE! > Results : > Tests run: 3, Failures: 2, Errors: 0, Skipped: 0 > [INFO] > > [ERROR] BUILD FAILURE > [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: (CONTINUUM-1092) Test failures in DataManagementToolTest
[ http://jira.codehaus.org/browse/CONTINUUM-1092?page=all ] thierry lach updated CONTINUUM-1092: Attachment: org.apache.maven.continuum.management.DataManagementToolTest.txt Latest failure > Test failures in DataManagementToolTest > --- > > Key: CONTINUUM-1092 > URL: http://jira.codehaus.org/browse/CONTINUUM-1092 > Project: Continuum > Issue Type: Bug > Components: Testing >Affects Versions: 1.1 > Environment: WinXP, Cygwin, Continuum r490404 >Reporter: Wendy Smoak > Attachments: > org.apache.maven.continuum.management.DataManagementToolTest.txt, > org.apache.maven.continuum.management.DataManagementToolTest.txt > > > Seems like Brett fixed a similar problem in Modello, and I could build > Continuum for a while, but now something is wrong again. > --- > T E S T S > --- > Running org.apache.maven.continuum.management.DataManagementToolTest > Tests run: 3, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 6.734 sec <<< > FAILURE! > Results : > Tests run: 3, Failures: 2, Errors: 0, Skipped: 0 > [INFO] > > [ERROR] BUILD FAILURE > [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: (CONTINUUM-1099) Consistency in confirmation message
[ http://jira.codehaus.org/browse/CONTINUUM-1099?page=all ] Emmanuel Venisse closed CONTINUUM-1099. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1 Applied. Thanks. > Consistency in confirmation message > --- > > Key: CONTINUUM-1099 > URL: http://jira.codehaus.org/browse/CONTINUUM-1099 > Project: Continuum > Issue Type: Improvement > Components: Web interface > Environment: Linux FC4, JDK1.5, Maven2.0.4 >Reporter: Napoleon Esmundo C. Ramirez > Assigned To: Emmanuel Venisse >Priority: Minor > Fix For: 1.1 > > Attachments: CONTINUUM-1099-continuum-webapp.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2739) Repository entries are not validated and NPE will occur
[ http://jira.codehaus.org/browse/MNG-2739?page=all ] Jason van Zyl updated MNG-2739: --- Description: Using something like the following has no id and an incorrect file url: cbuilds /Users/jvanzyl/js/org/codehaus/mojo/trunk/mojo/mojo-sandbox/c-builds/test-cpkg/m2-repo java.lang.NullPointerException at org.apache.maven.wagon.repository.Repository.hashCode(Repository.java:239) at java.util.HashMap.hash(HashMap.java:264) at java.util.HashMap.put(HashMap.java:382) at java.util.HashSet.add(HashSet.java:194) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:665) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:416) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:192) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) was: Using something like the following which has an incorrect file url. It could just default to file or validate: cbuilds /Users/jvanzyl/js/org/codehaus/mojo/trunk/mojo/mojo-sandbox/c-builds/test-cpkg/m2-repo java.lang.NullPointerException at org.apache.maven.wagon.repository.Repository.hashCode(Repository.java:239) at java.util.HashMap.hash(HashMap.java:264) at java.util.HashMap.put(HashMap.java:382) at java.util.HashSet.add(HashSet.java:194) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:665) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:416) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:192) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Summary: Repository entries are not validated and NPE will occur (was: Repository urls are not validated and NPE will occur) > Repository entries are not validated and NPE will occur > --- > > Key: MNG-2739 > URL: http://jira.codehaus.org/browse/MNG-2739 > Project: Maven 2 > Issue Type: Bug > Components: Repositories >Reporter: Jason van Zyl > > Using something like the following has no id and an incorrect file url: > > cbuilds > > > > /Users/jvanzyl/js/org/codehaus/mojo/trunk/mojo/mojo-sandbox/c-builds/test-cpkg/m2-repo > > > > java.lang.NullPointerException > at > org.apache.maven.wagon.repository.Repository.hashCode(Repository.java:239) > at java.util.HashMap.hash(HashMap.java:264) > at java.util.HashMap.put(HashMap.java:382) > at java.u
[jira] Created: (MNG-2739) Repository urls are not validated and NPE will occur
Repository urls are not validated and NPE will occur Key: MNG-2739 URL: http://jira.codehaus.org/browse/MNG-2739 Project: Maven 2 Issue Type: Bug Components: Repositories Reporter: Jason van Zyl Using something like the following which has an incorrect file url. It could just default to file or validate: cbuilds /Users/jvanzyl/js/org/codehaus/mojo/trunk/mojo/mojo-sandbox/c-builds/test-cpkg/m2-repo java.lang.NullPointerException at org.apache.maven.wagon.repository.Repository.hashCode(Repository.java:239) at java.util.HashMap.hash(HashMap.java:264) at java.util.HashMap.put(HashMap.java:382) at java.util.HashSet.add(HashSet.java:194) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:665) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:416) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:192) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1098) Cannot upload a Maven 2 Project with modules
[ http://jira.codehaus.org/browse/CONTINUUM-1098?page=all ] Emmanuel Venisse updated CONTINUUM-1098: Issue Type: Improvement (was: Bug) Summary: Cannot upload a Maven 2 Project with modules (was: Cannot add a Maven 2 Project with modules) > Cannot upload a Maven 2 Project with modules > > > Key: CONTINUUM-1098 > URL: http://jira.codehaus.org/browse/CONTINUUM-1098 > Project: Continuum > Issue Type: Improvement > Components: Core system, Web interface, Web - UI >Affects Versions: 1.1 > Environment: -r490655 >Reporter: Franz Allan Valencia See > Attachments: error logs.txt, error page.JPG > > -- 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-2738) 1-char profile names cannot be activated with -P
1-char profile names cannot be activated with -P
Key: MNG-2738
URL: http://jira.codehaus.org/browse/MNG-2738
Project: Maven 2
Issue Type: Bug
Components: Command Line
Affects Versions: 2.1
Reporter: Kenney Westerhof
Priority: Minor
'mvn install -Uc' gives;
{noformat}
Unable to parse command line options: no argument for:P
usage: mvn [options] [] []
Options:
...etc...
{noformat}
(same for mvn -Pc [whatever])
--
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: (MAVENUPLOAD-1282) PMD 3.9 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1282?page=comments#action_83806 ] Tom Copeland commented on MAVENUPLOAD-1282: --- Hm... not sure... but we're definitely using beta 10 at the moment: $ ls -l lib/jaxen-1.1-beta-10.jar -rw-r--r-- 1 tom tom 239001 Oct 2 21:27 lib/jaxen-1.1-beta-10.jar Maybe I've got something wrong in the POM or some such? > PMD 3.9 bundle > -- > > Key: MAVENUPLOAD-1282 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1282 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tom Copeland > Assigned To: Carlos Sanchez > > PMD is a Java source code analyzer. It finds unused variables, empty catch > blocks, unnecessary object creation, and so forth. -- 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: (MAVENUPLOAD-1282) PMD 3.9 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1282?page=comments#action_83805 ] Anthony Whitford commented on MAVENUPLOAD-1282: --- Why does http://repo1.maven.org/maven/pmd/poms/pmd-3.9.pom list Jaxen 1.1-beta-10 as a dependency instead of 1.1? > PMD 3.9 bundle > -- > > Key: MAVENUPLOAD-1282 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1282 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tom Copeland > Assigned To: Carlos Sanchez > > PMD is a Java source code analyzer. It finds unused variables, empty catch > blocks, unnecessary object creation, and so forth. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MWAR-88) typos in documentation
typos in documentation -- Key: MWAR-88 URL: http://jira.codehaus.org/browse/MWAR-88 Project: Maven 2.x War Plugin Issue Type: Bug Reporter: Tomasz Pik Priority: Trivial Attachments: adding-filtering-webresources.apt.diff http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html contains typos in examples (related to excludes). Patch attached -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1098) Cannot add a Maven 2 Project with modules
[ http://jira.codehaus.org/browse/CONTINUUM-1098?page=comments#action_83804 ] Emmanuel Venisse commented on CONTINUUM-1098: - It isn't possible actually. This feature need some design before implementation. Approach b seems to be the best but we need to implement the possibility to look at modules list and see if sub-modules are already in continuum. With this, all new modules will can be added in continuum automatically. > Cannot add a Maven 2 Project with modules > - > > Key: CONTINUUM-1098 > URL: http://jira.codehaus.org/browse/CONTINUUM-1098 > Project: Continuum > Issue Type: Bug > Components: Core system, Web interface, Web - UI >Affects Versions: 1.1 > Environment: -r490655 >Reporter: Franz Allan Valencia See > Attachments: error logs.txt, error page.JPG > > -- 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: (MPLUGIN-26) Parsing issue due to qdox regression
Parsing issue due to qdox regression Key: MPLUGIN-26 URL: http://jira.codehaus.org/browse/MPLUGIN-26 Project: Maven 2.x Plugin Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Jerome Lacoste Priority: Blocker The webstart plugin build broke as the latest qdox (1.6.1) doesn't parse valid code. See QDOX-107 -- 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: (WAGONSSH-55) Although a password is given in the settings.xml for a scp url, a password prompt still appears
[ http://jira.codehaus.org/browse/WAGONSSH-55?page=comments#action_83802 ] Thomas Fischer commented on WAGONSSH-55: Added documentation patch to the getting started guide in MNG-2737 > Although a password is given in the settings.xml for a scp url, a password > prompt still appears > --- > > Key: WAGONSSH-55 > URL: http://jira.codehaus.org/browse/WAGONSSH-55 > Project: wagon-ssh > Issue Type: Wish >Affects Versions: 1.0-alpha-7 > Environment: ssh client on Windows XP, ssh server on SUSE Linux > Enterprise Server 10 >Reporter: Thomas Fischer >Priority: Minor > > I want to deploy an artifact on a remote repository using scp (not scpexe) by > issuing the command mvn deploy. In the settings.xml, I have specified an > username and the correct password for the user, and I made sure that the > settings file is read by maven. Still, wagon prompts me for a password when > establishing the ssh connection for every ssh access (6 times for deploying a > plugin). If I enter the correct password 6 times, deployment works but typing > the password so often is very tedious. > I tried to look into the code and although I am not familiar with ssh and > jsch, it appears to me that the problem occurs if the ssh server sends back > the authentication method should be "keyboard-interactive" (see jsch's > Session.connect(int) method). Then Jsch does not use the provided password > but tries to prompt it from console. This ends up in Wagon's > UserInfoUIKeyboardInteractiveProxy.promptKeybordInteractive() method. > If I replace the code in the method promptKeyboardInteractive, which was > originally > return interactive.promptKeyboardInteractive( destination, name, > instruction, prompt, echo ); > by > String[] result = new String[prompt.length]; > result[0] = userInfo.getPassword(); > return result; > (which is a bad hack in my opinion), then the authentication works without > having to type in the password. I did not dig deep enough into the wagon code > to see if there is a clean way to solve this, but perhaps somebody else has > an idea. > I'd be happy to test any other solutions if it is difficult to reproduce the > problem on another Linux Sytem. -- 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-2737) Improved section about deploying to remote repository in the getting started guide
Improved section about deploying to remote repository in the getting started guide -- Key: MNG-2737 URL: http://jira.codehaus.org/browse/MNG-2737 Project: Maven 2 Issue Type: Improvement Components: Documentation: Guides Environment: Maven Website, getting started guide Rev. 478765 Reporter: Thomas Fischer Priority: Minor Attachments: getting-started-guide-deployment-patch.txt I had difficulties deploying to a remote repository using the configuration in the getting started guide. It turned out that a setting in the ssh server made deployment difficult. I have attached a patch to the getting started guide describing this behaviour. One could argue that this information is too specific to be included in the getting started guide. But then, settings in the getting started guide should be fool-proof, and it should be documented when they cannot be used if this is not obvious. Please feel free to change the wording and/or the location of the information given in this patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1281) JFacets profile-based framework bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1281?page=comments#action_83797 ] Remi VANKEISBELCK commented on MAVENUPLOAD-1281: Oooops ! Just corrected the pom so that it now references groovy instead of groovy-all, as suggested. Sorry for that. I've recreated the bundle and dropped it there : http://jfacets.rvkb.com/pub/jfacets-1.3.6-bundle.jar Thanks ! Cheers Remi - and a happy new year > JFacets profile-based framework bundle > -- > > Key: MAVENUPLOAD-1281 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1281 > Project: maven-upload-requests > Issue Type: Task >Reporter: Remi VANKEISBELCK > > http://jfacets.rvkb.com/pub/jfacets-1.3.6-bundle.jar > http://jfacets.rvkb.com > http://sf.net/projects/jfacets > JFacets is a framework that allows to build profile-based applications > easier, when you display and interact in a customized fashion with end-users > based on their roles via "facets". > Upload please ! > Thanks > Remi - remi 'at' rvkb.com > PS : It's my first maven repo upload, so apologies in advance if something > isn't right in here ! -- 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: (WAGONSSH-55) Although a password is given in the settings.xml for a scp url, a password prompt still appears
[ http://jira.codehaus.org/browse/WAGONSSH-55?page=comments#action_83793 ] Thomas Fischer commented on WAGONSSH-55: I checked the PasswordAuthentication setting and it is set to "no" in sshd_config. Setting it to "yes" stops the prompts for the password. In my particular case, this solves the problem. Maybe this should be documented in the maven docs (e.g. in the "getting started" guide, section "How do I deploy my jar in my remote repository?"). I'd be happy to provide a docs patch. I was not aware that the ssh server could ask for something else than a password. How would an agent know which answer should be sent to which question ? > Although a password is given in the settings.xml for a scp url, a password > prompt still appears > --- > > Key: WAGONSSH-55 > URL: http://jira.codehaus.org/browse/WAGONSSH-55 > Project: wagon-ssh > Issue Type: Wish >Affects Versions: 1.0-alpha-7 > Environment: ssh client on Windows XP, ssh server on SUSE Linux > Enterprise Server 10 >Reporter: Thomas Fischer >Priority: Minor > > I want to deploy an artifact on a remote repository using scp (not scpexe) by > issuing the command mvn deploy. In the settings.xml, I have specified an > username and the correct password for the user, and I made sure that the > settings file is read by maven. Still, wagon prompts me for a password when > establishing the ssh connection for every ssh access (6 times for deploying a > plugin). If I enter the correct password 6 times, deployment works but typing > the password so often is very tedious. > I tried to look into the code and although I am not familiar with ssh and > jsch, it appears to me that the problem occurs if the ssh server sends back > the authentication method should be "keyboard-interactive" (see jsch's > Session.connect(int) method). Then Jsch does not use the provided password > but tries to prompt it from console. This ends up in Wagon's > UserInfoUIKeyboardInteractiveProxy.promptKeybordInteractive() method. > If I replace the code in the method promptKeyboardInteractive, which was > originally > return interactive.promptKeyboardInteractive( destination, name, > instruction, prompt, echo ); > by > String[] result = new String[prompt.length]; > result[0] = userInfo.getPassword(); > return result; > (which is a bad hack in my opinion), then the authentication works without > having to type in the password. I did not dig deep enough into the wagon code > to see if there is a clean way to solve this, but perhaps somebody else has > an idea. > I'd be happy to test any other solutions if it is difficult to reproduce the > problem on another Linux Sytem. -- 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: (CONTINUUM-1098) Cannot add a Maven 2 Project with modules
[ http://jira.codehaus.org/browse/CONTINUUM-1098?page=comments#action_83782 ] Franz Allan Valencia See commented on CONTINUUM-1098: - Carlos, Yes, it is via upload pom. It doesn't seem to have any problems with POM Url. Do you have any suggestion how to fix this? Right now I can think of only two approaches: a. Ask the user to upload every pom.xml, and b. Read the scm of the uploaded pom.xml, and use that as the base directory for the modules. With approach a, it is a pretty safe approach, but very tiresome for the user if it involves several modules, and might be impratical for a really huge project. And for approach b, we may need to ask for credentials as well ( I don't think requiring an scm url would be much of an issue, since currently, continuum _does_ require the poms to have an scm url ). Cheers, Franz > Cannot add a Maven 2 Project with modules > - > > Key: CONTINUUM-1098 > URL: http://jira.codehaus.org/browse/CONTINUUM-1098 > Project: Continuum > Issue Type: Bug > Components: Core system, Web interface, Web - UI >Affects Versions: 1.1 > Environment: -r490655 >Reporter: Franz Allan Valencia See > Attachments: error logs.txt, error page.JPG > > -- 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
