[jira] (SUREFIRE-1041) JUnit47 provider: Exception in JUnit Runner can crash test run without visible stack trace
[
https://jira.codehaus.org/browse/SUREFIRE-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Gudian updated SUREFIRE-1041:
-
Fix Version/s: 2.17
> JUnit47 provider: Exception in JUnit Runner can crash test run without
> visible stack trace
> --
>
> Key: SUREFIRE-1041
> URL: https://jira.codehaus.org/browse/SUREFIRE-1041
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Dan Fabulich
> Fix For: 2.17
>
> Attachments: SUREFIRE-1041.patch, SUREFIRE-1041-testcase.zip
>
>
> Run the attached Maven project. Surefire is configured to use the JUnit47
> provider. There's one test, marked with @RunWith(BadRunner.class); the
> BadRunner class throws a NullPointerException in its "run" method.
> Expected: The tests should fail with a visible stacktrace; that's what
> happens when you don't use the JUnit47 provider.
> Actual: The tests fail with this unhelpful error:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on
> project test: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test failed:
> java.lang.RuntimeException: null,null,null,null,null: source is null -> [Help
> 1]
> {code}
> I'm also attaching a patch that fixes this problem: SimpleReportEntry should
> not throw a NPE with a null source/name, but should instead just accept them
> and convert them to the string "null." This allows the test to fail naturally
> and render the stacktrace in the console output and in surefire reports.
--
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
[jira] (MRELEASE-855) Plugin does not support multiple SVN repositories
[
https://jira.codehaus.org/browse/MRELEASE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Renato Del Gaudio updated MRELEASE-855:
---
Description:
I have a multi modules project that uses several different repositories.
e.g.
Repository 1: https://hostname/svn/A
Repository 2: https://hostname/svn/B
Repository 3: https://hostname/svn/C
Module A (Master build): https://hostname/svn/A/moduleA
Module B: https://hostname/svn/B/moduleB
Module C: https://hostname/svn/C/moduleC
IMPORTANT:
# Each module resided in its own repository with its own revision
# Module B and C are children maven projects of module A
Running *release:prepare* the plugin fails while trying to tag the repositories
because it tries to use the *same revision number* (the one from the last
module) for all.
The plugin is configured centrally in the parent pom in a paremetric way.
The property software.id is the key that differentiate the repository within
the *scm* section that is the only part overwritten in the single child projects
{code:xml}
A
scm:svn:${scm.baseurl}/${software.id}/${scm.connection.version}/${project.artifactId}
${scm.baseurl}/${software.id}/${scm.connection.version}/${project.artifactId}
scm:svn:${scm.baseurl}/${software.id}/${scm.connection.version}/${project.artifactId}
org.apache.maven.plugins
maven-release-plugin
2.4
true
false
clean
MyProject_@{project.version}
javasvn
com.google.code.maven-scm-provider-svnjava
maven-scm-provider-svnjava
2.0.5
org.tmatesoft.svnkit
svnkit
1.7.6
org.apache.maven.plugins
maven-scm-plugin
1.8.1
{code}
was:
I have a multi modules project that uses several different repositories.
e.g.
Repository 1: https://hostname/svn/A
Repository 2: https://hostname/svn/B
Repository 3: https://hostname/svn/C
Module A (Master build): https://hostname/svn/A/moduleA
Module B: https://hostname/svn/B/moduleB
Module C: https://hostname/svn/C/moduleC
IMPORTANT:
# Each module resided in its own repository with its own revision
# Module B and C are children maven projects of module A
Running *release:prepare* the plugin fails while trying to tag the repositories
because it tries to use the *same revision number* (the one from the last
module) for all.
I am using the plugin configured as follows:
{code:xml}
org.apache.maven.plugins
maven-release-plugin
2.4
true
false
clean
${scm.baseurl}/A/tags
MyProject_@{project.version}
javasvn
com.google.code.maven-scm-provider-svnjava
maven-scm-provider-svnjava
2.0.5
org.tmatesoft.svnkit
svnkit
1.7.6
org.apache.maven.plugins
maven-scm-plugin
1.8.1
{code}
> Plugin does not support multiple SVN repositories
> -
>
> Key: MRELEASE-855
> URL: https://jira.codehaus.org/browse/MRELEASE-855
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.4.2
>Reporter: Renato Del Gaudio
>
> I have a multi modules project that uses several different repositories.
> e.g.
> Repository 1: https://hostname/svn/A
> Repository 2: https://hostname/svn/B
> Repository 3: https://hostname/svn/C
> Module A (Master build): https://hostname/svn/A/moduleA
> Module B: https://hostname/svn/B/moduleB
> Module C: https://hostname/svn/C/moduleC
> IMPORTANT:
> # Each module resided in its own repository with its own revision
> # Module B and C are children maven projects of module A
> Running *release:prepare* the plugin fails while trying to tag the
> repositories because it tries to use the *same revision number* (the one from
> the last module) for all.
> The plugin is configured centrally in the parent pom in a paremetric way.
> The property software.id is the key that differentiate the repository within
> the *scm* section that is the only part overwritten in the single child
> projects
> {code:xml}
>
> A
>
>
>
> scm:svn:${scm.baseurl}/${software.id}/${scm.connection.version}/${project.artifactId}
>
>
> ${scm.baseurl}/${software.id}/${scm.connection.version}/${project.artifactId}
>
>
> scm:svn:${scm.baseurl}/${
[jira] (MNG-5534) Update to Sisu 0.1.0 and Guice 3.1.6
Mikolaj Izdebski created MNG-5534: - Summary: Update to Sisu 0.1.0 and Guice 3.1.6 Key: MNG-5534 URL: https://jira.codehaus.org/browse/MNG-5534 Project: Maven 2 & 3 Issue Type: Improvement Affects Versions: 3.2 Reporter: Mikolaj Izdebski Attachments: 0001-Update-to-Sisu-0.1.0-and-Guice-3.1.6.patch Please update to Eclipse Sisu 0.1.0 and Sisu Guice 3.1.6. Sisu depends on Guice, but dependency scope changed from "compile" to "provided" in Sisu 0.1.0. As a Sisu user, Maven needs to have runtime dependency on Guice. -- 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
[jira] (MRELEASE-855) Plugin does not support multiple SVN repositories
[
https://jira.codehaus.org/browse/MRELEASE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-855.
---
Resolution: Duplicate
Assignee: Robert Scholte
> Plugin does not support multiple SVN repositories
> -
>
> Key: MRELEASE-855
> URL: https://jira.codehaus.org/browse/MRELEASE-855
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.4.2
>Reporter: Renato Del Gaudio
>Assignee: Robert Scholte
>
> I have a multi modules project that uses several different repositories.
> e.g.
> Repository 1: https://hostname/svn/A
> Repository 2: https://hostname/svn/B
> Repository 3: https://hostname/svn/C
> Module A (Master build): https://hostname/svn/A/moduleA
> Module B: https://hostname/svn/B/moduleB
> Module C: https://hostname/svn/C/moduleC
> IMPORTANT:
> # Each module resided in its own repository with its own revision
> # Module B and C are children maven projects of module A
> Running *release:prepare* the plugin fails while trying to tag the
> repositories because it tries to use the *same revision number* (the one from
> the last module) for all.
> The plugin is configured centrally in the parent pom in a paremetric way.
> The property software.id is the key that differentiate the repository within
> the *scm* section that is the only part overwritten in the single child
> projects
> {code:xml}
>
> A
>
>
>
> scm:svn:${scm.baseurl}/${software.id}/${scm.connection.version}/${project.artifactId}
>
>
> ${scm.baseurl}/${software.id}/${scm.connection.version}/${project.artifactId}
>
>
> scm:svn:${scm.baseurl}/${software.id}/${scm.connection.version}/${project.artifactId}
>
>
>
> org.apache.maven.plugins
> maven-release-plugin
> 2.4
>
> true
> false
> clean
> MyProject_@{project.version}
>
> javasvn
>
>
>
>
> com.google.code.maven-scm-provider-svnjava
> maven-scm-provider-svnjava
> 2.0.5
>
>
> org.tmatesoft.svnkit
> svnkit
> 1.7.6
>
>
> org.apache.maven.plugins
> maven-scm-plugin
> 1.8.1
>
>
>
> {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
[jira] (MSHARED-304) Create a API for java tool
Tony Chemit created MSHARED-304: --- Summary: Create a API for java tool Key: MSHARED-304 URL: https://jira.codehaus.org/browse/MSHARED-304 Project: Maven Shared Components Issue Type: New Feature Affects Versions: maven-shared-utils-0.4 Reporter: Tony Chemit While using the commandline API to invoke java tool (*jarsigner*, *keytool*, *javadoc*), we always write the same boilerplate code: - find the java tool executable location - build a new command line - invoke it and deal with invocation errors - ... Let's have a simple API for this! As a first improvement then let's add to it also the support for toolchain (asked in maven-jarsigner-plugin). I will put the code in package *org.apache.maven.shared.utils.cli.javatool*. -- 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
[jira] (MSHARED-304) Create a API for java tool
[ https://jira.codehaus.org/browse/MSHARED-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-304: Assignee: Tony Chemit > Create a API for java tool > -- > > Key: MSHARED-304 > URL: https://jira.codehaus.org/browse/MSHARED-304 > Project: Maven Shared Components > Issue Type: New Feature >Affects Versions: maven-shared-utils-0.4 >Reporter: Tony Chemit >Assignee: Tony Chemit > > While using the commandline API to invoke java tool (*jarsigner*, *keytool*, > *javadoc*), we always write the same boilerplate code: > - find the java tool executable location > - build a new command line > - invoke it and deal with invocation errors > - ... > Let's have a simple API for this! As a first improvement then let's add to it > also the support for toolchain (asked in maven-jarsigner-plugin). > I will put the code in package *org.apache.maven.shared.utils.cli.javatool*. -- 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
[jira] (MSHARED-304) Create a API for java tool
[ https://jira.codehaus.org/browse/MSHARED-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-304. --- Resolution: Fixed Fix Version/s: maven-shared-utils-0.5 > Create a API for java tool > -- > > Key: MSHARED-304 > URL: https://jira.codehaus.org/browse/MSHARED-304 > Project: Maven Shared Components > Issue Type: New Feature >Affects Versions: maven-shared-utils-0.4 >Reporter: Tony Chemit >Assignee: Tony Chemit > Fix For: maven-shared-utils-0.5 > > > While using the commandline API to invoke java tool (*jarsigner*, *keytool*, > *javadoc*), we always write the same boilerplate code: > - find the java tool executable location > - build a new command line > - invoke it and deal with invocation errors > - ... > Let's have a simple API for this! As a first improvement then let's add to it > also the support for toolchain (asked in maven-jarsigner-plugin). > I will put the code in package *org.apache.maven.shared.utils.cli.javatool*. -- 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
[jira] (MSHARED-305) Use maven-shared-utils javatool API
Tony Chemit created MSHARED-305: --- Summary: Use maven-shared-utils javatool API Key: MSHARED-305 URL: https://jira.codehaus.org/browse/MSHARED-305 Project: Maven Shared Components Issue Type: Task Affects Versions: maven-jarsigner-1.1 Reporter: Tony Chemit -- 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
[jira] (MSHARED-305) Use maven-shared-utils javatool API
[ https://jira.codehaus.org/browse/MSHARED-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-305: Assignee: Tony Chemit > Use maven-shared-utils javatool API > --- > > Key: MSHARED-305 > URL: https://jira.codehaus.org/browse/MSHARED-305 > Project: Maven Shared Components > Issue Type: Task >Affects Versions: maven-jarsigner-1.1 >Reporter: Tony Chemit >Assignee: Tony Chemit > -- 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
[jira] (MSHARED-306) keystore and alias parameters can be used for both sign and verify jarsigner tool
Tony Chemit created MSHARED-306: --- Summary: keystore and alias parameters can be used for both sign and verify jarsigner tool Key: MSHARED-306 URL: https://jira.codehaus.org/browse/MSHARED-306 Project: Maven Shared Components Issue Type: Improvement Affects Versions: maven-jarsigner-1.1 Reporter: Tony Chemit -- 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
[jira] (MSHARED-306) keystore and alias parameters can be used for both sign and verify jarsigner tool
[ https://jira.codehaus.org/browse/MSHARED-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit reassigned MSHARED-306: --- Assignee: Tony Chemit > keystore and alias parameters can be used for both sign and verify jarsigner > tool > - > > Key: MSHARED-306 > URL: https://jira.codehaus.org/browse/MSHARED-306 > Project: Maven Shared Components > Issue Type: Improvement >Affects Versions: maven-jarsigner-1.1 >Reporter: Tony Chemit >Assignee: Tony Chemit > -- 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
[jira] (MSHARED-305) Use maven-shared-utils javatool API
[ https://jira.codehaus.org/browse/MSHARED-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335666#comment-335666 ] Tony Chemit commented on MSHARED-305: - To use maven-toolchain, we need now mavenVersion up to 2.1.0 (was 2.0.6). > Use maven-shared-utils javatool API > --- > > Key: MSHARED-305 > URL: https://jira.codehaus.org/browse/MSHARED-305 > Project: Maven Shared Components > Issue Type: Task >Affects Versions: maven-jarsigner-1.1 >Reporter: Tony Chemit >Assignee: Tony Chemit > Fix For: maven-jarsigner-1.2 > > -- 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
[jira] (MSHARED-305) Use maven-shared-utils javatool API
[ https://jira.codehaus.org/browse/MSHARED-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-305. --- Resolution: Fixed Fix Version/s: maven-jarsigner-1.2 > Use maven-shared-utils javatool API > --- > > Key: MSHARED-305 > URL: https://jira.codehaus.org/browse/MSHARED-305 > Project: Maven Shared Components > Issue Type: Task >Affects Versions: maven-jarsigner-1.1 >Reporter: Tony Chemit >Assignee: Tony Chemit > Fix For: maven-jarsigner-1.2 > > -- 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
[jira] (MJARSIGNER-9) Add toolchain in JarSignMojo.java#getJDKCommandExe()
[ https://jira.codehaus.org/browse/MJARSIGNER-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-9: - Assignee: Tony Chemit > Add toolchain in JarSignMojo.java#getJDKCommandExe() > > > Key: MJARSIGNER-9 > URL: https://jira.codehaus.org/browse/MJARSIGNER-9 > Project: Maven Jar Signer Plugin > Issue Type: Task >Reporter: Vincent Siveton >Assignee: Tony Chemit > > Similar to AbstractJavadocMojo#getJavadocExecutable() -- 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
[jira] (MJARSIGNER-28) verify mojo can also use keystore and alias parameters
Tony Chemit created MJARSIGNER-28: - Summary: verify mojo can also use keystore and alias parameters Key: MJARSIGNER-28 URL: https://jira.codehaus.org/browse/MJARSIGNER-28 Project: Maven Jar Signer Plugin Issue Type: Improvement Affects Versions: 1.2 Reporter: Tony Chemit Priority: Minor -- 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
[jira] (MJARSIGNER-9) Add toolchain in JarSignMojo.java#getJDKCommandExe()
[ https://jira.codehaus.org/browse/MJARSIGNER-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-9. Resolution: Fixed Fix Version/s: 1.3 > Add toolchain in JarSignMojo.java#getJDKCommandExe() > > > Key: MJARSIGNER-9 > URL: https://jira.codehaus.org/browse/MJARSIGNER-9 > Project: Maven Jar Signer Plugin > Issue Type: Task >Reporter: Vincent Siveton >Assignee: Tony Chemit > Fix For: 1.3 > > > Similar to AbstractJavadocMojo#getJavadocExecutable() -- 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
[jira] (MSHARED-306) keystore and alias parameters can be used for both sign and verify jarsigner tool
[ https://jira.codehaus.org/browse/MSHARED-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-306. --- Resolution: Fixed Fix Version/s: maven-jarsigner-1.2 > keystore and alias parameters can be used for both sign and verify jarsigner > tool > - > > Key: MSHARED-306 > URL: https://jira.codehaus.org/browse/MSHARED-306 > Project: Maven Shared Components > Issue Type: Improvement >Affects Versions: maven-jarsigner-1.1 >Reporter: Tony Chemit >Assignee: Tony Chemit > Fix For: maven-jarsigner-1.2 > > -- 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
[jira] (MJARSIGNER-28) verify mojo can also use keystore and alias parameters
[ https://jira.codehaus.org/browse/MJARSIGNER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-28: -- Assignee: Tony Chemit > verify mojo can also use keystore and alias parameters > -- > > Key: MJARSIGNER-28 > URL: https://jira.codehaus.org/browse/MJARSIGNER-28 > Project: Maven Jar Signer Plugin > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Tony Chemit >Assignee: Tony Chemit >Priority: Minor > -- 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
[jira] (MJARSIGNER-29) verbose parameter is not filled in jarsigner requests
Tony Chemit created MJARSIGNER-29: - Summary: verbose parameter is not filled in jarsigner requests Key: MJARSIGNER-29 URL: https://jira.codehaus.org/browse/MJARSIGNER-29 Project: Maven Jar Signer Plugin Issue Type: Bug Reporter: Tony Chemit Priority: Minor -- 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
[jira] (MJARSIGNER-28) verify mojo can also use keystore and alias parameters
[ https://jira.codehaus.org/browse/MJARSIGNER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-28. - Resolution: Fixed Fix Version/s: 1.3 > verify mojo can also use keystore and alias parameters > -- > > Key: MJARSIGNER-28 > URL: https://jira.codehaus.org/browse/MJARSIGNER-28 > Project: Maven Jar Signer Plugin > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Tony Chemit >Assignee: Tony Chemit >Priority: Minor > Fix For: 1.3 > > -- 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
[jira] (MJARSIGNER-29) verbose parameter is not filled in jarsigner requests
[ https://jira.codehaus.org/browse/MJARSIGNER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-29: -- Assignee: Tony Chemit > verbose parameter is not filled in jarsigner requests > - > > Key: MJARSIGNER-29 > URL: https://jira.codehaus.org/browse/MJARSIGNER-29 > Project: Maven Jar Signer Plugin > Issue Type: Bug >Reporter: Tony Chemit >Assignee: Tony Chemit >Priority: Minor > -- 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
[jira] (MJARSIGNER-29) verbose parameter is not filled in jarsigner requests
[ https://jira.codehaus.org/browse/MJARSIGNER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-29. - Resolution: Fixed Fix Version/s: 1.3 > verbose parameter is not filled in jarsigner requests > - > > Key: MJARSIGNER-29 > URL: https://jira.codehaus.org/browse/MJARSIGNER-29 > Project: Maven Jar Signer Plugin > Issue Type: Bug >Reporter: Tony Chemit >Assignee: Tony Chemit >Priority: Minor > Fix For: 1.3 > > -- 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
[jira] (MJARSIGNER-26) Jar Signer does not support protected authentication path
[
https://jira.codehaus.org/browse/MJARSIGNER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335631#comment-335631
]
Tony Chemit edited comment on MJARSIGNER-26 at 11/13/13 3:38 PM:
-
Patch apply, thanks!
Meanwhile you can add this to your configuration:
{noformat}
-protected
{noformat}
I have just deployed a new version of the plugin, you can test it if you like
to.
was (Author: tchemit):
Patch apply, thanks!
Meanwhile you can add this to your configuration:
{noformat}
-protected
{noformat}
I will close the issue when maven-jarsigner 1.2 will be released.
> Jar Signer does not support protected authentication path
> -
>
> Key: MJARSIGNER-26
> URL: https://jira.codehaus.org/browse/MJARSIGNER-26
> Project: Maven Jar Signer Plugin
> Issue Type: Bug
>Affects Versions: 1.2
>Reporter: Michael Gruebsch
>Assignee: Tony Chemit
> Attachments: maven-jarsigner-1.0.patch,
> maven-jarsigner-plugin-1.2.patch
>
>
> The jarsigner tool has an option "-protected" (see
> http://docs.oracle.com/javase/6/docs/technotes/tools/windows/jarsigner.html#Options,
> documentation for option -storetype): a PCKS#11 token may have a protected
> authentication path (such as a dedicated PIN-pad or a biometric reader). In
> such case the -protected option must be specified and no password options can
> be specified.
> The current version does not support this option. Please find patches for
> maven-jarsigner-1.0 and maven-jarsigner-plugin (Version 1.3-SNAPSHOT)
> attached.
> Testcases are left out because a pin reader, a PCKS#11 smart card and human
> interaction would be necessary to test this scenario. However, the patched
> version works fine in my environment.
--
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
[jira] (MJARSIGNER-26) Jar Signer does not support protected authentication path
[ https://jira.codehaus.org/browse/MJARSIGNER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-26. - Resolution: Fixed Fix Version/s: 1.3 > Jar Signer does not support protected authentication path > - > > Key: MJARSIGNER-26 > URL: https://jira.codehaus.org/browse/MJARSIGNER-26 > Project: Maven Jar Signer Plugin > Issue Type: Bug >Affects Versions: 1.2 >Reporter: Michael Gruebsch >Assignee: Tony Chemit > Fix For: 1.3 > > Attachments: maven-jarsigner-1.0.patch, > maven-jarsigner-plugin-1.2.patch > > > The jarsigner tool has an option "-protected" (see > http://docs.oracle.com/javase/6/docs/technotes/tools/windows/jarsigner.html#Options, > documentation for option -storetype): a PCKS#11 token may have a protected > authentication path (such as a dedicated PIN-pad or a biometric reader). In > such case the -protected option must be specified and no password options can > be specified. > The current version does not support this option. Please find patches for > maven-jarsigner-1.0 and maven-jarsigner-plugin (Version 1.3-SNAPSHOT) > attached. > Testcases are left out because a pin reader, a PCKS#11 smart card and human > interaction would be necessary to test this scenario. However, the patched > version works fine in my environment. -- 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
[jira] (MJARSIGNER-12) It should be possible to save the keystore in one location for multi module projects
[ https://jira.codehaus.org/browse/MJARSIGNER-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-12. - Resolution: Won't Fix Fix Version/s: 1.3 Assignee: Tony Chemit I just check and it works well with a url. So then nothing more to be done here. > It should be possible to save the keystore in one location for multi module > projects > > > Key: MJARSIGNER-12 > URL: https://jira.codehaus.org/browse/MJARSIGNER-12 > Project: Maven Jar Signer Plugin > Issue Type: New Feature >Reporter: Sven Kirmess >Assignee: Tony Chemit > Fix For: 1.3 > > > We have a multi module maven setup. The problem is that this plugin requires > us to have the keystore either in the same location on all machines or in the > source code along each and every pom.xml file. > I would like to have one of the following: > - Save the file on one location in Subversion and use something like >svn://svn.example.com/trunk/keystore >and the plugin would have to take care to check out the keystore into > every project as needed. > or > - Put the keystore into a JAR file and save that JAR file on the Nexus > server. Then make the jarsigner plugin depend on this JAR file, download it > for every project and extract the keystore from there. This would be like > what the assembly plugin can do for its descriptors. > http://docs.codehaus.org/display/MAVENUSER/Assembly+Plugin -- 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
[jira] (WAGON-323) CLONE -keyboard-interactive method is used even when password is supplied
[
https://jira.codehaus.org/browse/WAGON-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335670#comment-335670
]
Max Calderoni commented on WAGON-323:
-
same problem verified on my end with beta 7.
Could someone try explain how to fix this, so that people could give it a shot
(i would try)?
This issue is a bit annoying especially in multi-module systems, where it will
ask for password re-prompt for every module.
> CLONE -keyboard-interactive method is used even when password is supplied
> -
>
> Key: WAGON-323
> URL: https://jira.codehaus.org/browse/WAGON-323
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ssh
>Affects Versions: 1.0-beta-4
> Environment: Maven version: 2.0.10-RC8
> Java version: 1.5.0_13
> Default locale: en_US, platform encoding: ISO8859-1
> OS name: "sunos" version: "5.10" arch: "sparc" family: "unix"
>Reporter: Bernd Vogt
>Assignee: Brett Porter
> Fix For: 1.0-beta-5
>
>
> Starting from {{2.0.10-RC8}} deploy (with ssh and password) started to fail -
> I'm getting:
> {noformat}
> [DEBUG] Connecting to repository: 'repo.sandsli.dnb.no' with url:
> 'scp://repo.sandsli.dnb.no/dnb/data/proximity/inhouse.snapshot/storage'.
> Keyboard interactive required, supplied password is ignored
> {noformat}
> event though the pw is in {{settings.xml}}:
> With help from Brett this was added:
> {code:xml}
>
>
>
> org.apache.maven.wagon
> wagon-ssh
> 1.0-beta-2
>
>
> {code}
> which resolved the case.
> Fragment from {{settings.xml}}:
> {code:xml}
>
>
> MyUser
> MySecret
> 777
> 777
> repo.sandsli.dnb.no
>
> {code}
> Fragment from {{pom.xml}}:
> {code:xml}
>
>
> repo.sandsli.dnb.no
> DnBNOR Felles Repository
> scp://repo.sandsli.dnb.no/dnb/data/proximity/inhouse/storage
>
>
> repo.sandsli.dnb.no
> DnBNOR Felles Snapshot Repository
>
> scp://repo.sandsli.dnb.no/dnb/data/proximity/inhouse.snapshot/storage
>
>
> repo.sandsli.dnb.no
>
> scp://repo.sandsli.dnb.no/dnb/prosess/prosjektdok/no.dnbnor.websphere-1.3-SNAPSHOT/websphere-testenvironment
>
>
> {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
[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=335680#comment-335680
]
Tony Chemit commented on MJARSIGNER-13:
---
Hi @Dennis, Have you add your entry in the project FAQ? I don't see it, could
you done it to close this issue efore next release (I hope to do it soon after
releasing maven-shared-utils, maven-jarsinger,...).
Thanks.
> signing in multi-module project fails on windows
>
>
> Key: MJARSIGNER-13
> URL: https://jira.codehaus.org/browse/MJARSIGNER-13
> Project: Maven Jar Signer Plugin
> Issue Type: Bug
>Affects Versions: 1.2
> Environment: Windows XP, android sdk
>Reporter: Anna Gadomska
> Attachments: pom.xml
>
>
> I got multi-module (6 modules) android project with .pom file and "sign"
> profile defined. When I execute with 'sign' profile:
> - in Maven 3.0.1 - it signs 3 modules and fails. when I resume the execution
> (mv -rf) it signs another 3 modules and fails again. The reason for
> failing is: [INFO] jarsigner: attempt to rename xxx.jar to xxx.jar.orig
> failed.
> - in Maven 2.2.1 - it doesn't work at all, even for first module; it returns
> "error code 1"
> However, I tried the same .pom - everything works perfectly in Linux
> (Ubuntu).
> I was afraid that it might be the issue with spaces, so I hardcoded the paths
> - the error I got from maven than was:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign (signing) on project
> MyProject: Failed executing 'cmd.exe /X /C
> "C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore
> "C:\tmp\debug.keystore" -storepass '*' -keypass '*' xxx.jar
> '*'debugkey"' - exitcode 1 -> [Help 1]
> {noformat}
> Attaching pom file which I am using.
> Please help?
--
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
[jira] (MJARSIGNER-18) Support for Jar plugin's "errorWhenNotSigned" option
[ https://jira.codehaus.org/browse/MJARSIGNER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-18: -- Assignee: Tony Chemit > Support for Jar plugin's "errorWhenNotSigned" option > > > Key: MJARSIGNER-18 > URL: https://jira.codehaus.org/browse/MJARSIGNER-18 > Project: Maven Jar Signer Plugin > Issue Type: New Feature >Affects Versions: 1.2 > Environment: n/a >Reporter: Martin Scholl >Assignee: Tony Chemit >Priority: Minor > > It would be nice if the jarsigner plugin could support the > "errorWhenNotSigned" option of the maven2 jar plugin, too. -- 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
[jira] (MJARSIGNER-18) Support for Jar plugin's "errorWhenNotSigned" option
[ https://jira.codehaus.org/browse/MJARSIGNER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335681#comment-335681 ] Tony Chemit commented on MJARSIGNER-18: --- @Martin, the option is now back! By default its value is false to not change the current behaviour. Enjoy. > Support for Jar plugin's "errorWhenNotSigned" option > > > Key: MJARSIGNER-18 > URL: https://jira.codehaus.org/browse/MJARSIGNER-18 > Project: Maven Jar Signer Plugin > Issue Type: New Feature >Affects Versions: 1.2 > Environment: n/a >Reporter: Martin Scholl >Assignee: Tony Chemit >Priority: Minor > Fix For: 1.3 > > > It would be nice if the jarsigner plugin could support the > "errorWhenNotSigned" option of the maven2 jar plugin, too. -- 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
[jira] (MJARSIGNER-18) Support for Jar plugin's "errorWhenNotSigned" option
[ https://jira.codehaus.org/browse/MJARSIGNER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-18. - Resolution: Fixed Fix Version/s: 1.3 > Support for Jar plugin's "errorWhenNotSigned" option > > > Key: MJARSIGNER-18 > URL: https://jira.codehaus.org/browse/MJARSIGNER-18 > Project: Maven Jar Signer Plugin > Issue Type: New Feature >Affects Versions: 1.2 > Environment: n/a >Reporter: Martin Scholl >Assignee: Tony Chemit >Priority: Minor > Fix For: 1.3 > > > It would be nice if the jarsigner plugin could support the > "errorWhenNotSigned" option of the maven2 jar plugin, too. -- 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
