headers
Tuure Laurinolli (JIRA | 23 May 2013 08:41

[jira] (MRELEASE-796) Add AbstractScmReleaseMojo


    [
https://jira.codehaus.org/browse/MRELEASE-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325449#comment-325449
] 

Tuure Laurinolli commented on MRELEASE-796:
-------------------------------------------

This broke release:perform on a specific tag. The perform mojo should probably inherit
AbstractScmReleaseMojo. See also MRELEASE-839.

> Add AbstractScmReleaseMojo
> --------------------------
>
>                 Key: MRELEASE-796
>                 URL: https://jira.codehaus.org/browse/MRELEASE-796
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>             Fix For: 2.4
>
>
> There are several goals which have nothing to do with the SCM, but do get these SCM-related parameters from
the {{AbstractReleaseMojo}}. Especially for the {{update-versions}}-goal it's confusing, since it
says it doesn't require SCM.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tuure Laurinolli (JIRA | 23 May 2013 08:33

[jira] (MRELEASE-839) Unable to supply tag to release for release:perform

Tuure Laurinolli created MRELEASE-839:
-----------------------------------------

             Summary: Unable to supply tag to release for release:perform
                 Key: MRELEASE-839
                 URL: https://jira.codehaus.org/browse/MRELEASE-839
             Project: Maven 2.x Release Plugin
          Issue Type: Bug
          Components: perform
    Affects Versions: 2.4.1
            Reporter: Tuure Laurinolli

The documentation at
http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html
and http://maven.apache.org/maven-release/maven-release-plugin/plugin-info.html claims that
releases can be ma de of a specific tag, but no mechanism for this is specified.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 0 comments |
headers
Kurt T Stam (JIRA | 23 May 2013 02:00

[jira] (MJARSIGNER-13) signing in multi-module project fails on windows


    [
https://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325442#comment-325442
] 

Kurt T Stam commented on MJARSIGNER-13:
---------------------------------------

This issue pretty much kills this plugin on windows.

[INFO] Processing C:\test\juddi\juddi-gui-dsig\target\juddi-gui-dsig-3.2.0-SNAPS
HOT.jar
[DEBUG] 'cmd.exe /X /C ""C:\Program Files\Java\jdk1.6.0_43\jre\..\bin\jarsigner.
exe" -verbose -keystore signing.keystore -storepass '*****' -keypass '*****' C:\
test\juddi\juddi-gui-dsig\target\juddi-gui-dsig-3.2.0-SNAPSHOT.jar '*****'"'
[INFO]  updating: META-INF/MANIFEST.MF
[INFO]    adding: META-INF/APPLET.SF
[INFO]    adding: META-INF/APPLET.DSA
[INFO]    adding: org/
[INFO]    adding: org/apache/
[INFO]    adding: org/apache/juddi/
[INFO]    adding: org/apache/juddi/gui/
[INFO]    adding: org/apache/juddi/gui/dsig/
[INFO]   signing: org/apache/juddi/gui/dsig/XmlSignatureApplet$1.class
[INFO]   signing: org/apache/juddi/gui/dsig/XmlSignatureApplet$2.class
[INFO]   signing: org/apache/juddi/gui/dsig/XmlSignatureApplet.class
[INFO] jarsigner: attempt to rename C:\test\juddi\juddi-gui-dsig\target\juddi-gu
i-dsig-3.2.0-SNAPSHOT.jar to C:\test\juddi\juddi-gui-dsig\target\juddi-gui-dsig-
3.2.0-SNAPSHOT.jar.orig failed
[INFO] ------------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andreas Gudian (JIRA | 22 May 2013 22:47

[jira] (SUREFIRE-973) add properties to classpathDependencyExcludes and additionalClasspathElements parameters


     [
https://jira.codehaus.org/browse/SUREFIRE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Gudian closed SUREFIRE-973.
-----------------------------------

    Resolution: Fixed

Milos, thanks again for your patch. I wasn't able to use it as-is because of the Maven 2 compatibility issue
that you already noticed with the ITs. 
But I kept your suggested property names ;).

Pls give it a spin to check if it does what you expected. While at that, perhaps you find an IT to extend :)

> add properties to classpathDependencyExcludes and additionalClasspathElements parameters
> ----------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-973
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-973
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.14
>            Reporter: Milos Kleint
>            Assignee: Andreas Gudian
>             Fix For: 2.15
>
>         Attachments: surefire.patch
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Scholte (JIRA | 22 May 2013 22:41

[jira] (SCM-709) REGRESSION: git status doesn't work if repository root is not the working directory


    [
https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325429#comment-325429
] 

Robert Scholte commented on SCM-709:
------------------------------------

There are indeed more places where this needs to be fixed. I'll try to refactor the code a bit, so this logic
can stay at one place.
I've just checked out the project in a folder with spaces and that causes several tests to fail, so I need to
make those tests space-safe too.

> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>
>                 Key: SCM-709
>                 URL: https://jira.codehaus.org/browse/SCM-709
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-git
>    Affects Versions: 1.8, 1.8.1
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>            Priority: Blocker
>         Attachments: 0001-use-new-File-.toURI-to-fix-handling-of-paths-with-sp.patch
>
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result language independend.
> Without the {{--porcelain}} option files were listed relative to the working directory, but with
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andreas Gudian (JIRA | 22 May 2013 21:47

[jira] (SUREFIRE-973) add properties to classpathDependencyExcludes and additionalClasspathElements parameters


     [
https://jira.codehaus.org/browse/SUREFIRE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Gudian reassigned SUREFIRE-973:
---------------------------------------

    Assignee: Andreas Gudian

> add properties to classpathDependencyExcludes and additionalClasspathElements parameters
> ----------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-973
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-973
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.14
>            Reporter: Milos Kleint
>            Assignee: Andreas Gudian
>             Fix For: 2.15
>
>         Attachments: surefire.patch
>
>
> currently classpathDependencyExcludes and additionalClasspathElements parameters don't have
properties defined to declare on cmd line. The attached patch includes them.
> I would like to use these properties in Netbeans. With multiple projects enabling Compile on Save
feature, I would need these properties to replace outside project's jar artifacts from local repository
with their project's output directory dynamically.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Koch (JIRA | 22 May 2013 20:15

[jira] (SCM-709) REGRESSION: git status doesn't work if repository root is not the working directory


    [
https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325425#comment-325425
] 

Michael Koch commented on SCM-709:
----------------------------------

Thanks for taking the time to look at this. I think that even with your fix there is still a problem where the
{{Git*Command}} classes calculate the {{relativeRepositoryPath}} if the repository root path (i. e.
the output of {{git rev-parse --show-toplevel}}) contains spaces.

> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>
>                 Key: SCM-709
>                 URL: https://jira.codehaus.org/browse/SCM-709
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-git
>    Affects Versions: 1.8, 1.8.1
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>            Priority: Blocker
>         Attachments: 0001-use-new-File-.toURI-to-fix-handling-of-paths-with-sp.patch
>
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result language independend.
> Without the {{--porcelain}} option files were listed relative to the working directory, but with
{{--porcelain}} files are listed relative to the repository root. In most cases these are the same, but
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bryan Kelly (JIRA | 22 May 2013 19:51

[jira] (WAGON-391) Error installing artifact's metadata: Error while deploying metadata: Authentication failed: Cannot connect. Reason: verify: false


    [
https://jira.codehaus.org/browse/WAGON-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325424#comment-325424
] 

Bryan Kelly commented on WAGON-391:
-----------------------------------

This is good news.  Is there a way to update the jsch version that the wagon-ssh extension would be using or
will it require a code release of the wagon-ssh?

>  Error installing artifact's metadata: Error while deploying metadata: Authentication failed: Cannot
connect. Reason: verify: false
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WAGON-391
>                 URL: https://jira.codehaus.org/browse/WAGON-391
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-ssh
>    Affects Versions: 2.3
>            Reporter: Bryan Kelly
>
> When attempting to publish an artifact to an ssh server we get the following exception intermittently: 
> Error installing artifact's metadata: Error while deploying metadata: Authentication failed: Cannot
connect. Reason: verify: false
> Other consumers of the jsch library have had a similar issue [1], their fix was to add retry logic while
attempting to make the connection to the ssh server.
> [1] https://github.com/int128/gradle-ssh-plugin/issues/11
(Continue reading)

Permalink | Reply | 0 comments |
headers
Laura Llewellyn (JIRA | 22 May 2013 18:22

[jira] (MINVOKER-155) Invoker plugin does not allow multiple environment variables to be set


    [
https://jira.codehaus.org/browse/MINVOKER-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325421#comment-325421
] 

Laura Llewellyn commented on MINVOKER-155:
------------------------------------------

Originally asked on the [Maven user's
group|http://mail-archives.apache.org/mod_mbox/maven-users/201305.mbox/%3CCAMFVGuSrgYVbWhyo1oKb%2B5otX55YNLcj9%2BjKe4B%3DTUnmEdeThg%40mail.gmail.com%3E].
 I'm reporting as a bug at Stephen Connolly's request.  Attached test case includes the POM with invoker
plugin configuration and an integration test that verifies the environment variables specified in the
plugin configuration are defined.

I looked at the source code for the maven-invoker-plugin and the shared
Invoker component.  The AbstractInvokerMojo.runBuild method has this code:

{code}
final InvocationRequest request = new DefaultInvocationRequest();
....
if ( environmentVariables != null )
{
   for ( Map.Entry<String, String> variable : environmentVariables.entrySet() )
   {
      request.addShellEnvironment( variable.getKey(), variable.getValue());
   }
}
{code}

InvocationRequest is in the [shared Invoker plugin code|http://svn.apache.org/viewvc/maven/shared/tags/maven-invoker-2.1.1/src/main/java/org/apache/maven/shared/invoker/DefaultInvocationRequest.java?view=markup].
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Scholte (JIRA | 22 May 2013 18:20

[jira] (MINVOKER-155) Invoker plugin does not allow multiple environment variables to be set


     [
https://jira.codehaus.org/browse/MINVOKER-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte reassigned MINVOKER-155:
---------------------------------------

    Assignee: Robert Scholte

> Invoker plugin does not allow multiple environment variables to be set
> ----------------------------------------------------------------------
>
>                 Key: MINVOKER-155
>                 URL: https://jira.codehaus.org/browse/MINVOKER-155
>             Project: Maven 2.x Invoker Plugin
>          Issue Type: Bug
>    Affects Versions: 1.8
>         Environment: Observed with Maven 3.0.4, both Windows 7 and RedHat Linux
>            Reporter: Laura Llewellyn
>            Assignee: Robert Scholte
>         Attachments: maven-env-test.zip
>
>
> Multiple environment variables may be specified using the {{environmentVariables}} parameter as
shown below.  However, only one of the variables is actually passed to the test cases.
> {code:title=Plugin Configuration}
> <environmentVariables>
>    <A_PROP>white</A_PROP>
>    <Z_PROP>blue</Z_PROP>
> </environmentVariables>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Laura Llewellyn (JIRA | 22 May 2013 18:15

[jira] (MINVOKER-155) Invoker plugin does not allow multiple environment variables to be set

Laura Llewellyn created MINVOKER-155:
----------------------------------------

             Summary: Invoker plugin does not allow multiple environment variables to be set
                 Key: MINVOKER-155
                 URL: https://jira.codehaus.org/browse/MINVOKER-155
             Project: Maven 2.x Invoker Plugin
          Issue Type: Bug
    Affects Versions: 1.8
         Environment: Observed with Maven 3.0.4, both Windows 7 and RedHat Linux
            Reporter: Laura Llewellyn
         Attachments: maven-env-test.zip

Multiple environment variables may be specified using the {{environmentVariables}} parameter as shown
below.  However, only one of the variables is actually passed to the test cases.

{code:title=Plugin Configuration}
<environmentVariables>
   <A_PROP>white</A_PROP>
   <Z_PROP>blue</Z_PROP>
</environmentVariables>
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 0 comments |

Gmane