[jira] (MRELEASE-128) SCM properties being replaced during release:perform
[
https://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294609#comment-294609
]
Gabriele commented on MRELEASE-128:
---
I've just tryed the 2.3-SNAPSHOT, it does work for scm URL under svn when
executing prepare goal:
scm:svn:${project.scm.url}trunk
${project.scm.connection}
but when executing perform goal:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3
-SNAPSHOT:perform (default-cli) on project BatchSistemaInformativo: An error is
occurred in the checkout process: Exception while executing SCM command. Error w
hile executing command. Error inside systemOut parser: String index out of range
: -1 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal o
rg.apache.maven.plugins:maven-release-plugin:2.3-SNAPSHOT:perform (default-cli)
on project BatchSistemaInformativo: An error is occurred in the checkout process
: Exception while executing SCM command.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred
in the checkout process: Exception while executing SCM command.
at
org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:153)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.maven.shared.release.ReleaseExecutionException: An error
is occurred in the checkout process: Exception while executing SCM command.
at
org.apache.maven.shared.release.phase.CheckoutProjectFromScm.execute(CheckoutProjectFromScm.java:133)
at
org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:421)
at
org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:373)
at
org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:149)
... 21 more
Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM
command.
at
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63)
at
org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmProvider.java:356)
at
org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.checkout(AbstractSvnScmProvider.java:292)
at
org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:480)
at
org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:453)
at
org.apache.maven.shared.release.phase.CheckoutProjectFromScm.performCheckout(CheckoutProjectFromScm.java:208)
at
org.apache.maven.shared.release.phase.CheckoutProjectFromScm.execute(CheckoutProjectFromScm.java:125)
... 24 more
Caused by: org.apache.maven.scm.ScmException: Error while executing command.
at
org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnCheckOutCommand.executeCheckOutCommand(SvnCheckOutCommand.java:95)
at
org.apache.maven.s
[jira] (MNG-5264) When using maven.test.skip it should skip downloading plugins which will not be run
Carlo de Wolf created MNG-5264:
--
Summary: When using maven.test.skip it should skip downloading
plugins which will not be run
Key: MNG-5264
URL: https://jira.codehaus.org/browse/MNG-5264
Project: Maven 2 & 3
Issue Type: Improvement
Reporter: Carlo de Wolf
Priority: Minor
Given the following section:
{noformat}
org.scala-tools
maven-scala-plugin
src/test/scala
scala-test-compile
process-test-resources
testCompile
{noformat}
Maven will try to download the plugin irrespective of setting maven.test.skip
or skipTests.
{noformat}
[ERROR] Plugin org.scala-tools:maven-scala-plugin:2.15.2 or one of its
dependencies could not be resolved: Failed to read artifact descriptor for
org.scala-tools:maven-scala-plugin:jar:2.15.2: The repository system is offline
but the artifact org.scala-tools:maven-scala-plugin:pom:2.15.2 is not available
in the local repository. -> [Help 1]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (WAGON-371) for security reason preemptive must be off by default for GET
Olivier Lamy created WAGON-371: -- Summary: for security reason preemptive must be off by default for GET Key: WAGON-371 URL: https://jira.codehaus.org/browse/WAGON-371 Project: Maven Wagon Issue Type: Bug Components: wagon-http, wagon-http-lightweight Affects Versions: 2.2 Reporter: Olivier Lamy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (WAGON-371) for security reason preemptive must be off by default for GET
[ https://jira.codehaus.org/browse/WAGON-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated WAGON-371: --- Fix Version/s: 2.3 Assignee: Olivier Lamy > for security reason preemptive must be off by default for GET > - > > Key: WAGON-371 > URL: https://jira.codehaus.org/browse/WAGON-371 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-http, wagon-http-lightweight >Affects Versions: 2.2 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-128) SCM properties being replaced during release:perform
[
https://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte reopened MRELEASE-128:
-
> SCM properties being replaced during release:perform
>
>
> Key: MRELEASE-128
> URL: https://jira.codehaus.org/browse/MRELEASE-128
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
>Reporter: Craig Dickson
>Assignee: Robert Scholte
>Priority: Critical
> Labels: properties
> Fix For: 2.3
>
> Attachments: after-release-perform-pom.xml,
> after-release-prepre-pom.xml, MNG-128-maven-release-manager.patch,
> MRELEASE-128_cvs_hack_RewritePomsForDevelopmentPhase.java.patch,
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (WAGON-371) for security reason preemptive must be off by default for GET
[ https://jira.codehaus.org/browse/WAGON-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294660#comment-294660 ] Jason van Zyl commented on WAGON-371: - Off by default period. It simply cannot be on by default. No credentials should ever be exchanged without explicit configuration. > for security reason preemptive must be off by default for GET > - > > Key: WAGON-371 > URL: https://jira.codehaus.org/browse/WAGON-371 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-http, wagon-http-lightweight >Affects Versions: 2.2 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-128) SCM properties being replaced during release:perform
[
https://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294665#comment-294665
]
Robert Scholte commented on MRELEASE-128:
-
Hi Gabriele,
Thanks for testing! Could you do me a favour and surround your logmessage with
\{noformat} to make it easier to read.
You hit SCM-618 (which I already fixed), so that has nothing to do with my
adjustment here.
My plan is to release this plugin with the next scm-version (1.7), so you
shouldn't hit this problem by then.
> SCM properties being replaced during release:perform
>
>
> Key: MRELEASE-128
> URL: https://jira.codehaus.org/browse/MRELEASE-128
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
>Reporter: Craig Dickson
>Assignee: Robert Scholte
>Priority: Critical
> Labels: properties
> Fix For: 2.3
>
> Attachments: after-release-perform-pom.xml,
> after-release-prepre-pom.xml, MNG-128-maven-release-manager.patch,
> MRELEASE-128_cvs_hack_RewritePomsForDevelopmentPhase.java.patch,
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-667) mvn release:prepare fails for hierarchical multi-module project on Windows 7 using msysgit with "is outside repository"
[
https://jira.codehaus.org/browse/SCM-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294666#comment-294666
]
Robert Scholte commented on SCM-667:
Mirko, this seems to be a gif-diff. Could you attach a svn-diff?
> mvn release:prepare fails for hierarchical multi-module project on Windows 7
> using msysgit with "is outside repository"
> ---
>
> Key: SCM-667
> URL: https://jira.codehaus.org/browse/SCM-667
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.6
> Environment: c:\ws\testlink-junit2>mvn --version
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: c:\tools\apache-maven-3\bin\..
> Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_29\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> c:\ws\testlink-junit2>git --version
> git version 1.7.8.msysgit.1
> c:\ws\testlink-junit2>git remote -v
> origin git://github.com/1and1/testlink-junit.git (fetch)
> origin git://github.com/1and1/testlink-junit.git (push)
>Reporter: Mirko Friedenhagen
>Priority: Critical
> Attachments: SCM-667.patch, SCM-667-with-test.patch
>
>
> Steps to reproduce (provided Maven, Java and Git are installed on your
> Windows-Machine):
> # Run: {code}
> git clone git://github.com/1and1/testlink-junit.git testlink-junit2
> cd testlink-junit2
> mvn -DpushChanges=false -e -B release:prepare
> {code}
> Console output: {code}
> [INFO] Checking in modified POMs...
> [INFO] Executing: cmd.exe /X /C "git add -- pom.xml
> C:\ws\testlink-junit2\tljunit-surefire\pom.xml
> C:\ws\testlink-junit2\tljunit-eclipse\pom.xml"
> [INFO] Working directory: c:\ws\testlink-junit2
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] tljunit parent FAILURE [22.561s]
> [INFO] tljunit surefire RunListeners . SKIPPED
> [INFO] tljunit sample project for running tests from eclipse. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 24.879s
> [INFO] Finished at: Wed Feb 29 17:58:15 CET 2012
> [INFO] Final Memory: 13M/177M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) on
> project tljunit-parent: Unable to commit files
> [ERROR] Provider message:
> [ERROR] The git-add command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'C:\ws\testlink-junit2\tljunit-surefire\pom.xml' is outside
> repository
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare
> (default-cli) on project tljunit-parent: Unable to commit files
> Provider message:
> The git-add command failed.
> Command output:
> fatal: 'C:\ws\testlink-junit2\tljunit-surefire\pom.xml' is outside repository
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> 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:597)
> at
> org.codeha
[jira] (SCM-667) mvn release:prepare fails for hierarchical multi-module project on Windows 7 using msysgit with "is outside repository"
[
https://jira.codehaus.org/browse/SCM-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirko Friedenhagen updated SCM-667:
---
Attachment: SCM-667-with-test-svn-format.patch
Hello Robert,
a svn-diff for the git-provider :-). I checked out
https://svn.apache.org/repos/asf/maven/scm/trunk at revision 1303136, ran {{mvn
clean install}} (on MacOSX) successfully and applied the git patch with:
{code}
patch -p1 < SCM-667-with-test.patch
{code}
Afterwards I ran:
{code}
svn add
maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/GitCommandLineUtilsAddTargetTest.java
{code}, ran {{mvn clean install}}
and now attach the outcome of {{svn diff}}.
Regards
Mirko
> mvn release:prepare fails for hierarchical multi-module project on Windows 7
> using msysgit with "is outside repository"
> ---
>
> Key: SCM-667
> URL: https://jira.codehaus.org/browse/SCM-667
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.6
> Environment: c:\ws\testlink-junit2>mvn --version
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: c:\tools\apache-maven-3\bin\..
> Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_29\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> c:\ws\testlink-junit2>git --version
> git version 1.7.8.msysgit.1
> c:\ws\testlink-junit2>git remote -v
> origin git://github.com/1and1/testlink-junit.git (fetch)
> origin git://github.com/1and1/testlink-junit.git (push)
>Reporter: Mirko Friedenhagen
>Priority: Critical
> Attachments: SCM-667.patch, SCM-667-with-test.patch,
> SCM-667-with-test-svn-format.patch
>
>
> Steps to reproduce (provided Maven, Java and Git are installed on your
> Windows-Machine):
> # Run: {code}
> git clone git://github.com/1and1/testlink-junit.git testlink-junit2
> cd testlink-junit2
> mvn -DpushChanges=false -e -B release:prepare
> {code}
> Console output: {code}
> [INFO] Checking in modified POMs...
> [INFO] Executing: cmd.exe /X /C "git add -- pom.xml
> C:\ws\testlink-junit2\tljunit-surefire\pom.xml
> C:\ws\testlink-junit2\tljunit-eclipse\pom.xml"
> [INFO] Working directory: c:\ws\testlink-junit2
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] tljunit parent FAILURE [22.561s]
> [INFO] tljunit surefire RunListeners . SKIPPED
> [INFO] tljunit sample project for running tests from eclipse. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 24.879s
> [INFO] Finished at: Wed Feb 29 17:58:15 CET 2012
> [INFO] Final Memory: 13M/177M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) on
> project tljunit-parent: Unable to commit files
> [ERROR] Provider message:
> [ERROR] The git-add command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'C:\ws\testlink-junit2\tljunit-surefire\pom.xml' is outside
> repository
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare
> (default-cli) on project tljunit-parent: Unable to commit files
> Provider message:
> The git-add command failed.
> Command output:
> fatal: 'C:\ws\testlink-junit2\tljunit-surefire\pom.xml' is outside repository
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> a
[jira] (SCM-667) mvn release:prepare fails for hierarchical multi-module project on Windows 7 using msysgit with "is outside repository"
[
https://jira.codehaus.org/browse/SCM-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed SCM-667.
--
Resolution: Fixed
Fix Version/s: 1.7
Assignee: Robert Scholte
Fixed in [rev. 1303172|http://svn.apache.org/viewvc?rev=1303172&view=rev]
Thanks!
> mvn release:prepare fails for hierarchical multi-module project on Windows 7
> using msysgit with "is outside repository"
> ---
>
> Key: SCM-667
> URL: https://jira.codehaus.org/browse/SCM-667
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.6
> Environment: c:\ws\testlink-junit2>mvn --version
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: c:\tools\apache-maven-3\bin\..
> Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_29\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> c:\ws\testlink-junit2>git --version
> git version 1.7.8.msysgit.1
> c:\ws\testlink-junit2>git remote -v
> origin git://github.com/1and1/testlink-junit.git (fetch)
> origin git://github.com/1and1/testlink-junit.git (push)
>Reporter: Mirko Friedenhagen
>Assignee: Robert Scholte
>Priority: Critical
> Fix For: 1.7
>
> Attachments: SCM-667.patch, SCM-667-with-test.patch,
> SCM-667-with-test-svn-format.patch
>
>
> Steps to reproduce (provided Maven, Java and Git are installed on your
> Windows-Machine):
> # Run: {code}
> git clone git://github.com/1and1/testlink-junit.git testlink-junit2
> cd testlink-junit2
> mvn -DpushChanges=false -e -B release:prepare
> {code}
> Console output: {code}
> [INFO] Checking in modified POMs...
> [INFO] Executing: cmd.exe /X /C "git add -- pom.xml
> C:\ws\testlink-junit2\tljunit-surefire\pom.xml
> C:\ws\testlink-junit2\tljunit-eclipse\pom.xml"
> [INFO] Working directory: c:\ws\testlink-junit2
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] tljunit parent FAILURE [22.561s]
> [INFO] tljunit surefire RunListeners . SKIPPED
> [INFO] tljunit sample project for running tests from eclipse. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 24.879s
> [INFO] Finished at: Wed Feb 29 17:58:15 CET 2012
> [INFO] Final Memory: 13M/177M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) on
> project tljunit-parent: Unable to commit files
> [ERROR] Provider message:
> [ERROR] The git-add command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'C:\ws\testlink-junit2\tljunit-surefire\pom.xml' is outside
> repository
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare
> (default-cli) on project tljunit-parent: Unable to commit files
> Provider message:
> The git-add command failed.
> Command output:
> fatal: 'C:\ws\testlink-junit2\tljunit-surefire\pom.xml' is outside repository
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingM
[jira] (WAGON-371) for security reason preemptive must be off by default for GET
[ https://jira.codehaus.org/browse/WAGON-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed WAGON-371. -- Resolution: Fixed fixed [rev 1303212|http://svn.apache.org/viewvc?rev=1303212&view=rev] > for security reason preemptive must be off by default for GET > - > > Key: WAGON-371 > URL: https://jira.codehaus.org/browse/WAGON-371 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-http, wagon-http-lightweight >Affects Versions: 2.2 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5265) enforce repository url verification for passing authz
Olivier Lamy created MNG-5265:
-
Summary: enforce repository url verification for passing authz
Key: MNG-5265
URL: https://jira.codehaus.org/browse/MNG-5265
Project: Maven 2 & 3
Issue Type: Improvement
Components: Settings
Affects Versions: 3.0.4, 3.0.3, 3.0.2, 2.2.1, 2.0.10
Reporter: Olivier Lamy
Related discussion: http://markmail.org/message/7pswshucxc7qwtef
in your settings you have:
{code}
olamy
reallycomplicatedpassword
foo.org
{code}
During dependencies resolution, you get a pom with a repository.
{code}
foo.org
http://yourpasswordwillbehacked.org/
{code}
Idea id in settings must contains the target hostname.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5265) enforce repository url verification for passing authz
[
https://jira.codehaus.org/browse/MNG-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MNG-5265:
--
Fix Version/s: 3.0.5
print a warning in 3.0.5
> enforce repository url verification for passing authz
> -
>
> Key: MNG-5265
> URL: https://jira.codehaus.org/browse/MNG-5265
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Settings
>Affects Versions: 2.0.10, 2.2.1, 3.0.2, 3.0.3, 3.0.4
>Reporter: Olivier Lamy
> Fix For: 3.0.5
>
>
> Related discussion: http://markmail.org/message/7pswshucxc7qwtef
> in your settings you have:
> {code}
>
> olamy
> reallycomplicatedpassword
> foo.org
>
> {code}
> During dependencies resolution, you get a pom with a repository.
> {code}
>
> foo.org
> http://yourpasswordwillbehacked.org/
>
> {code}
> Idea id in settings must contains the target hostname.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-112) New property to enable shading the java text inside the sources artifact (not just shading the java source file locations)
Trask Stalnaker created MSHADE-112: -- Summary: New property to enable shading the java text inside the sources artifact (not just shading the java source file locations) Key: MSHADE-112 URL: https://jira.codehaus.org/browse/MSHADE-112 Project: Maven 2.x Shade Plugin Issue Type: New Feature Affects Versions: 1.6 Reporter: Trask Stalnaker Attachments: shade-sources-content.patch The existing createSourcesJar property shades the source file locations, but it doesn't shade their content. This makes debugging (when using a shaded artifact) a little painful (at least in Eclipse) since the source files that Eclipse finds don't match up with the package names in the runtime environment. The attached patch performs a rather naive regular expression search/replace throughout the java source files when building the shaded sources artifact. The patch also makes the assumption that the source files are all UTF-8 encoded. This latter issue seems especially problematic, and for this reason I have made this feature a new option (shadeSourcesContent) as opposed to making it the default behavior when createSourcesJar=true. It looks like there are a couple of java libraries that attempt to do encoding detection, if something like this is required to get this patch committed I can investigate this further, or if anyone has other ideas how to handle this please let me know. Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
