[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag
[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290268#comment-290268 ] Robert Scholte commented on MRELEASE-719: - This might be a svn server-side issue. I can confirm that this can go wrong at codehaus, but I've installed a complete system on a laptop and here the release stops if the tag already exists. > No error when release:prepare with an already existing scm tag > -- > > Key: MRELEASE-719 > URL: https://jira.codehaus.org/browse/MRELEASE-719 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.2.1 >Reporter: Tony Chemit >Assignee: Olivier Lamy > Fix For: 2.3 > > > When releasing the mojo-parent (codehaus), I had to do the release twice but > I forgot to remove the scm tag. > The release:prepare did not complain about it (should have). -- 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-662) Performing a release with localCheckout fail on Windows
[
https://jira.codehaus.org/browse/SCM-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte moved MRELEASE-624 to SCM-662:
-
Complexity: Intermediate
Component/s: (was: perform)
maven-scm-provider-git
Affects Version/s: (was: 2.1)
1.6
Key: SCM-662 (was: MRELEASE-624)
Project: Maven SCM (was: Maven 2.x Release Plugin)
> Performing a release with localCheckout fail on Windows
> ---
>
> Key: SCM-662
> URL: https://jira.codehaus.org/browse/SCM-662
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.6
> Environment: Windows Vista, msysgit, Maven 3.0.0
>Reporter: Daniel Spilker
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitScmProviderRepository.patch
>
>
> When trying to perform a release on a Windows machine with localCheckout set
> to true, I get the following error message. The path
> 'C:\Users\daspilker\workspaces\myproject' is a git repository.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.1:perform (default-cli) on
> project warp:
> Unable to checkout from SCM
> [ERROR] Provider message:
> [ERROR] The git-clone command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'C\Users\daspilker\workspaces\myproject' does not appear to be
> a git repository
> [ERROR] fatal: The remote end hung up unexpectedly
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :myproject
> {code}
--
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-662) Performing a release with localCheckout fail on Windows
[
https://jira.codehaus.org/browse/SCM-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed SCM-662.
--
Resolution: Duplicate
Assignee: Robert Scholte (was: Mark Struberg)
Duplicate of SCM-637
> Performing a release with localCheckout fail on Windows
> ---
>
> Key: SCM-662
> URL: https://jira.codehaus.org/browse/SCM-662
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.6
> Environment: Windows Vista, msysgit, Maven 3.0.0
>Reporter: Daniel Spilker
>Assignee: Robert Scholte
>Priority: Minor
> Attachments: GitScmProviderRepository.patch
>
>
> When trying to perform a release on a Windows machine with localCheckout set
> to true, I get the following error message. The path
> 'C:\Users\daspilker\workspaces\myproject' is a git repository.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.1:perform (default-cli) on
> project warp:
> Unable to checkout from SCM
> [ERROR] Provider message:
> [ERROR] The git-clone command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'C\Users\daspilker\workspaces\myproject' does not appear to be
> a git repository
> [ERROR] fatal: The remote end hung up unexpectedly
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :myproject
> {code}
--
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-637) parsing of git urls fails on windows
[ https://jira.codehaus.org/browse/SCM-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290275#comment-290275 ] Robert Scholte commented on SCM-637: Patch as provided by MRELEASE-624 doesn't work anymore, the test fails. > parsing of git urls fails on windows > > > Key: SCM-637 > URL: https://jira.codehaus.org/browse/SCM-637 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.5 >Reporter: Felix Simmendinger >Priority: Blocker > > please fix this issue raised in the release plugin > http://jira.codehaus.org/browse/MRELEASE-624 -- 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] (SUREFIRE-823) Surefire needs distinct (from failsafe) test skip
James Nord created SUREFIRE-823: --- Summary: Surefire needs distinct (from failsafe) test skip Key: SUREFIRE-823 URL: https://jira.codehaus.org/browse/SUREFIRE-823 Project: Maven Surefire Issue Type: Improvement Reporter: James Nord If you use both surefire and failsafe in the same project there is no way to skip unit tests but run failsafe tests (as the surefire -DskipTests=true flag is also used by failsafe). The only way around this is to override the default surefire plugin configuration to change the skipTets property to use a different property - however this is combersome and the project may not belong to you (so each time you need to edit the project locally). It would be beneficial if you could somehow bypass surefire unit tests but still run failsafe integration tests via the lifecycle. (ie not using the goals directly as there may be some code gen or other that is needed in an eralier phase) -- 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] (MWAR-267) Maven WAR plugin does not copy dependencies of type "bundle" into WEB-INF/lib
[
https://jira.codehaus.org/browse/MWAR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290287#comment-290287
]
Thomas Vandahl commented on MWAR-267:
-
I thought this was too much to ask...
This is actually a potential (and in our case substantial) reason for serious
headache. Would some developer please care to comment.
> Maven WAR plugin does not copy dependencies of type "bundle" into WEB-INF/lib
> -
>
> Key: MWAR-267
> URL: https://jira.codehaus.org/browse/MWAR-267
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
>Affects Versions: 2.1.1
> Environment: Any
>Reporter: Thomas Vandahl
>
> A WAR project has transitive dependencies of type "bundle" (mina-core, ...).
> These dependencies do not end up in the WAR file structure under WEB-INF/lib
> as they are supposed to.
> My guess would be the method ArtifactsPackagingTask.performPackaging(), where
> only known types of dependencies are handled, AFAICS. Could the type "bundle"
> be added there? Like:
> {code}
> else if ( "jar".equals( type ) || "ejb".equals( type ) ||
> "ejb-client".equals( type )
> || "test-jar".equals( type ) || "bundle".equals( type ))
> {
> copyFile( id, context, artifact.getFile(), LIB_PATH + targetFileName );
> }
> {code}
--
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-5235) Profiles not activated according to property values
Jérôme Verstrynge created MNG-5235: -- Summary: Profiles not activated according to property values Key: MNG-5235 URL: https://jira.codehaus.org/browse/MNG-5235 Project: Maven 2 & 3 Issue Type: Bug Components: Profiles Affects Versions: 3.0.3 Environment: Windows 7 Reporter: Jérôme Verstrynge Attachments: pom.xml I am trying to activate profiles according to properties defined in the pom.xml. Unfortunately, the profiles are never activated, no matter what value is set for the defined property. I double-checked my pom.xml with existing documentation. The attached example contains two profiles who echo the property value. These are never displayed in the output. However, documentation says a profile should be invoked if the activation section property values are met. There is also something unclear in the existing documentation. Is it possible to enable multiple profiles with properties in a single run or is only one profile selected at most in a single run? -- 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-5235) Profiles not activated according to property values
[ https://jira.codehaus.org/browse/MNG-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290293#comment-290293 ] Jérôme Verstrynge commented on MNG-5235: The pom.xml contains false statements I forgot to remove. > Profiles not activated according to property values > --- > > Key: MNG-5235 > URL: https://jira.codehaus.org/browse/MNG-5235 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.0.3 > Environment: Windows 7 >Reporter: Jérôme Verstrynge > Attachments: pom.xml > > > I am trying to activate profiles according to properties defined in the > pom.xml. Unfortunately, the profiles are never activated, no matter what > value is set for the defined property. I double-checked my pom.xml with > existing documentation. > The attached example contains two profiles who echo the property value. These > are never displayed in the output. However, documentation says a profile > should be invoked if the activation section property values are met. > There is also something unclear in the existing documentation. Is it possible > to enable multiple profiles with properties in a single run or is only one > profile selected at most in a single run? > -- 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-5235) Profiles not activated according to property values
[ https://jira.codehaus.org/browse/MNG-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290303#comment-290303 ] Joerg Schaible commented on MNG-5235: - This is by design. Properties are explicitly not mentioned in [How can a profile be triggered? How does this vary according to the type of profile being used?|http://maven.apache.org/guides/introduction/introduction-to-profiles.html]. Profiles are the first thing evaluated *before* anything else to determine the effective POM. > Profiles not activated according to property values > --- > > Key: MNG-5235 > URL: https://jira.codehaus.org/browse/MNG-5235 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.0.3 > Environment: Windows 7 >Reporter: Jérôme Verstrynge > Attachments: pom.xml > > > I am trying to activate profiles according to properties defined in the > pom.xml. Unfortunately, the profiles are never activated, no matter what > value is set for the defined property. I double-checked my pom.xml with > existing documentation. > The attached example contains two profiles who echo the property value. These > are never displayed in the output. However, documentation says a profile > should be invoked if the activation section property values are met. > There is also something unclear in the existing documentation. Is it possible > to enable multiple profiles with properties in a single run or is only one > profile selected at most in a single run? > -- 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
