[jira] (MNGSITE-168) http://maven.apache.org/maven-v4_0_0.xsd not accessible

[ https://jira.codehaus.org/browse/MNGSITE-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317213#comment-317213 ] Mathieu Baudier commented on MNGSITE-168: - In Maven 1.x documentation:

[jira] (MNGSITE-168) http://maven.apache.org/maven-v4_0_0.xsd not accessible

[ https://jira.codehaus.org/browse/MNGSITE-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mathieu Baudier reopened MNGSITE-168: - As per comment

[jira] (MNGSITE-168) http://maven.apache.org/maven-v4_0_0.xsd not accessible

[ https://jira.codehaus.org/browse/MNGSITE-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNGSITE-168. -- Resolution: Fixed The number of references it too huge to simply ignore. I've added a redirect

[jira] (MNGSITE-168) http://maven.apache.org/maven-v4_0_0.xsd not accessible

[ https://jira.codehaus.org/browse/MNGSITE-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317221#comment-317221 ] Mathieu Baudier commented on MNGSITE-168: - Thanks a lot! The warning disappered in

[jira] (SCM-572) CVS checkout using maven-scm-plugin is not working

[ https://jira.codehaus.org/browse/SCM-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-572: --- Component/s: maven-scm-provider-cvs Description: I am using {{maven-scm-plugin}} plugin and using

[jira] (SCM-572) CVS checkout using maven-scm-plugin is not working

[ https://jira.codehaus.org/browse/SCM-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed SCM-572. -- Resolution: Cannot Reproduce Assignee: Robert Scholte See http://maven.apache.org/scm/cvs.html for all

[jira] (SCM-580) Maven SCM plugin configuration ignored if executions are used.

[ https://jira.codehaus.org/browse/SCM-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-580: --- Component/s: maven-plugin Description: When utilizing the embedded configuration tag, everything is

[jira] (SCM-580) Maven SCM plugin configuration ignored if executions are used.

[ https://jira.codehaus.org/browse/SCM-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed SCM-580. -- Resolution: Not A Bug Assignee: Robert Scholte Maven SCM plugin configuration ignored if executions

[jira] (SCM-585) repository cannot be null on ScmManager.makeProviderScmRepository(String, File)

[ https://jira.codehaus.org/browse/SCM-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-585: --- Component/s: maven-scm-api Description: I want to update a subversion with maven-scm. Therefore I get

[jira] (SCM-657) SvnExeExportCommand with revision malfunctions for moved/deleted files

[ https://jira.codehaus.org/browse/SCM-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-657: --- Component/s: maven-scm-provider-svn Description: According to

[jira] (SCM-661) Initial checkout in clearcase ucm needs activity

[ https://jira.codehaus.org/browse/SCM-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-661: --- Component/s: maven-scm-provider-clearcase Description: My Jenkins job is configured to create a

[jira] (SCM-614) scm plugin does not respect maven aggregation specifications

[ https://jira.codehaus.org/browse/SCM-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-614: --- Component/s: maven-plugin Description: Good morning, According to

[jira] (SCM-565) scm:validate should not fork the build

[ https://jira.codehaus.org/browse/SCM-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-565: --- Component/s: maven-plugin Description: {{scm:validate}} invokes the lifecycle validate prior to calling

[jira] (SCM-565) scm:validate should not fork the build

[ https://jira.codehaus.org/browse/SCM-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317228#comment-317228 ] Robert Scholte commented on SCM-565: Looking at the current state of the

[jira] (SCM-665) TfsChangeLogCommand does not display the change log for directories

[ https://jira.codehaus.org/browse/SCM-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-665: --- Component/s: maven-scm-provider-tfs Description: The {{TfsChangeLogCommand}} can get change log of

[jira] (SCM-267) Branches setting is being used as a tag

[ https://jira.codehaus.org/browse/SCM-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-267: --- Component/s: maven-scm-provider-svn maven-plugin Description: Using pom build of :

[jira] (SCM-666) TfsEditCommand should not report error if the file is also checked out by others

[ https://jira.codehaus.org/browse/SCM-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-666: --- Component/s: maven-scm-provider-tfs Description: While checking out a file for editing, the

[jira] (SCM-710) Use of encrypted password in pom.xml confiuration is ignored

[ https://jira.codehaus.org/browse/SCM-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-710: --- Component/s: maven-plugin Use of encrypted password in pom.xml confiuration is ignored

[jira] (SCM-423) when I try to checkout file from perforce with maven, I get an exception Perforce password (P4PASSWD) invalid or unset.

[ https://jira.codehaus.org/browse/SCM-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-423: --- Description: Hi all, I'm using {{maven scm plugin 1.1}} and Perforce for building, when I try to

[jira] (SCM-423) when I try to checkout file from perforce with maven, I get an exception Perforce password (P4PASSWD) invalid or unset.

[ https://jira.codehaus.org/browse/SCM-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-423: --- Component/s: maven-scm-provider-perforce when I try to checkout file from perforce with maven, I get an

[jira] (SCM-426) Got an issue in Maven plugin with perforce passowrd,suddenely now build is failing as it started to ask passowrd for scm plugin by throwing an Exception while running SCM command

[ https://jira.codehaus.org/browse/SCM-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-426: --- Component/s: maven-scm-provider-perforce Description: Looking for step by step process to tackle this.

[jira] (SUREFIRE-569) There should be a way to run unit tests from a dependency jar.

[ https://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317229#comment-317229 ] Aslak Knutsen commented on SUREFIRE-569: I have a fix for this here:

[jira] (SUREFIRE-569) There should be a way to run unit tests from a dependency jar.

[ https://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317230#comment-317230 ] Kristian Rosenvold commented on SUREFIRE-569: - There's almost always some

[jira] (SUREFIRE-950) ClassNotFoundException org.apache.xerces.parsers.SAXParser not found

[ https://jira.codehaus.org/browse/SUREFIRE-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-950: Fix Version/s: 2.14 Assignee: Kristian Rosenvold ClassNotFoundException

[jira] (SUREFIRE-950) ClassNotFoundException org.apache.xerces.parsers.SAXParser not found

[ https://jira.codehaus.org/browse/SUREFIRE-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317231#comment-317231 ] Kristian Rosenvold commented on SUREFIRE-950: - This issue can be worked around by

[jira] (SUREFIRE-569) There should be a way to run unit tests from a dependency jar.

[ https://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated SUREFIRE-569: --- Attachment: SUREFIRE-569.patch git diff attached. Need some other format? I'm not going to

[jira] (SUREFIRE-569) There should be a way to run unit tests from a dependency jar.

[ https://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317234#comment-317234 ] Aslak Knutsen commented on SUREFIRE-569: I attempted to change as little existing code as

[jira] (SUREFIRE-569) There should be a way to run unit tests from a dependency jar.

[ https://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317235#comment-317235 ] Kristian Rosenvold commented on SUREFIRE-569: - Currently it's just for legal reasons,

[jira] (MRELEASE-819) preparationGoals parameter supoorted before version 2.4

[ https://jira.codehaus.org/browse/MRELEASE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-819. --- Resolution: Fixed Fix Version/s: 2.4.1 Assignee: Robert Scholte Fixed in

[jira] (SUREFIRE-569) There should be a way to run unit tests from a dependency jar.

[ https://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317237#comment-317237 ] Aslak Knutsen commented on SUREFIRE-569: Yea, assumed it was for legal reasons. You need

[jira] (MRELEASE-814) Property interpolation of developerConnection broken when inheritting from parent

[ https://jira.codehaus.org/browse/MRELEASE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-814: Priority: Critical (was: Blocker) Lowering to critical, since there's a workaround.

[jira] (MRELEASE-814) Property interpolation of developerConnection broken when inheritting from parent

[ https://jira.codehaus.org/browse/MRELEASE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317239#comment-317239 ] Robert Scholte commented on MRELEASE-814: - By extending I mean that the folder-path to a

[jira] (MRELEASE-813) Ability to specify tag for release:perform

[ https://jira.codehaus.org/browse/MRELEASE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317240#comment-317240 ] Robert Scholte commented on MRELEASE-813: - This is something which first need to be fixed

[jira] (MRELEASE-814) Property interpolation of developerConnection broken when inheritting from parent

[ https://jira.codehaus.org/browse/MRELEASE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317241#comment-317241 ] Fred Cooke commented on MRELEASE-814: - You could have each module in a git repo (nested

[jira] (MSITE-669) site:stage creates incorrect structure when module paths contains sets of ../

[ https://jira.codehaus.org/browse/MSITE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lennart Jörelid updated MSITE-669: -- Attachment: msite_669.patch Added a patch for the situation, including IT and documentation changes.

[jira] (MRELEASE-813) Ability to specify tag for release:perform

[ https://jira.codehaus.org/browse/MRELEASE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317243#comment-317243 ] Gili commented on MRELEASE-813: --- I'm all for it. Can you reassign this issue to the appropriate

[jira] (MRELEASE-814) Property interpolation of developerConnection broken when inheritting from parent

[ https://jira.codehaus.org/browse/MRELEASE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317244#comment-317244 ] Robert Scholte commented on MRELEASE-814: - Commit by project is supported:

[jira] (SUREFIRE-943) Failing tests in TEST-*.xml file contain currupt information

[ https://jira.codehaus.org/browse/SUREFIRE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317245#comment-317245 ] Falko Modler commented on SUREFIRE-943: --- bq. That totally messes up my Hudson report and is

[jira] (MCOMPILER-197) dependencies no more at classpath

Romain manni-Bucau created MCOMPILER-197: Summary: dependencies no more at classpath Key: MCOMPILER-197 URL: https://jira.codehaus.org/browse/MCOMPILER-197 Project: Maven 2.x Compiler Plugin

[jira] (SUREFIRE-943) Failing tests in TEST-*.xml file contain currupt information

[ https://jira.codehaus.org/browse/SUREFIRE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-943. --- Resolution: Fixed Fix Version/s: 2.14 Assignee: Kristian Rosenvold

[jira] (DOXIASITETOOLS-78) Velocity's ContextTool fails to configure

Michael Osipov created DOXIASITETOOLS-78: Summary: Velocity's ContextTool fails to configure Key: DOXIASITETOOLS-78 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-78 Project: Maven Doxia

[jira] (DOXIASITETOOLS-78) Velocity's ContextTool fails to configure

[ https://jira.codehaus.org/browse/DOXIASITETOOLS-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed DOXIASITETOOLS-78. Resolution: Duplicate Assignee: Robert Scholte Considering this as a

[jira] (DOXIASITETOOLS-67) Velocity ToolManager doesn't work for skins and custom templates

[ https://jira.codehaus.org/browse/DOXIASITETOOLS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317250#comment-317250 ] Michael Osipov commented on DOXIASITETOOLS-67: -- Great, issue is open for more

[jira] (MNG-2423) Prerequisites are not inherited

[ https://jira.codehaus.org/browse/MNG-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317251#comment-317251 ] Michael Osipov commented on MNG-2423: - Just stumbled upon this problem too. Can we add this to

[jira] (MNG-2423) Prerequisites are not inherited

[ https://jira.codehaus.org/browse/MNG-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317251#comment-317251 ] Michael Osipov edited comment on MNG-2423 at 1/13/13 3:37 PM: -- Just

[jira] (MASSEMBLY-640) Artifact data added to path when lineEnding tag set in dependencySet

Yuri Samsoniuk created MASSEMBLY-640: Summary: Artifact data added to path when lineEnding tag set in dependencySet Key: MASSEMBLY-640 URL: https://jira.codehaus.org/browse/MASSEMBLY-640 Project:

[jira] (MRELEASE-742) Regression in 2.2.2 related to maven-gpg-plugin

[ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317257#comment-317257 ] Gili commented on MRELEASE-742: --- I can confirm this regression. The problem is caused by the fact

[jira] (MRELEASE-742) Regression in 2.2.2 related to maven-gpg-plugin

[ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317257#comment-317257 ] Gili edited comment on MRELEASE-742 at 1/13/13 11:54 PM: - I can confirm

[jira] (MRELEASE-742) Regression in 2.2.2 related to maven-gpg-plugin

[ https://jira.codehaus.org/browse/MRELEASE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317257#comment-317257 ] Gili edited comment on MRELEASE-742 at 1/13/13 11:56 PM: - I can confirm

[jira] (MRELEASE-820) Upgrade Plexus Utils dependency

Gili created MRELEASE-820: - Summary: Upgrade Plexus Utils dependency Key: MRELEASE-820 URL: https://jira.codehaus.org/browse/MRELEASE-820 Project: Maven 2.x Release Plugin Issue Type: Improvement