[jira] (MJARSIGNER-14) Keystore password should be entered in an interactive way

2012-02-01 Thread Eric TOURNIER (JIRA) 

[ 
https://jira.codehaus.org/browse/MJARSIGNER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290486#comment-290486
 ] 

Eric TOURNIER commented on MJARSIGNER-14:
-

Here is a second patch which asks the user for both storepass and keypass 
without echoing them.

 Keystore password should be entered in an interactive way
 -

 Key: MJARSIGNER-14
 URL: https://jira.codehaus.org/browse/MJARSIGNER-14
 Project: Maven 2.x Jar Signer Plugin
  Issue Type: Improvement
Affects Versions: 1.2
Reporter: Eric TOURNIER
Priority: Minor
 Attachments: MJARSIGNER-14-maven-jarsigner-plugin.patch


 For security reasons, it could be useful not to configure keystore password 
 in the {{pom.xml}} file. Then, when these informations are missing, the 
 plugin should ask the user to enter this password in an interactive way.

--
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] Issue Comment Edited: (MJARSIGNER-14) Keystore password should be entered in an interactive way

2011-04-07 Thread Eric TOURNIER (JIRA) 

[ 
http://jira.codehaus.org/browse/MJARSIGNER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=262674#action_262674
 ] 

Eric TOURNIER edited comment on MJARSIGNER-14 at 4/7/11 4:07 AM:
-

This patch asks the user for a keystore password if it is not configured in 
pom.xml
The case of a missing key password is not included in this patch

  was (Author: eric_t):
This patch asks the user for a keystore password if it not configured in 
pom.xml
The case of a missing key password is not included in this patch
  
 Keystore password should be entered in an interactive way
 -

 Key: MJARSIGNER-14
 URL: http://jira.codehaus.org/browse/MJARSIGNER-14
 Project: Maven 2.x Jar Signer Plugin
  Issue Type: Improvement
Affects Versions: 1.2
Reporter: Eric TOURNIER
Priority: Minor
 Attachments: MJARSIGNER-14-maven-jarsigner-plugin.patch


 For security reasons, it could be useful not to configure keystore password 
 in the {{pom.xml}} file. Then, when these informations are missing, the 
 plugin should ask the user to enter this password in an interactive way.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (MJARSIGNER-14) Keystore password should be entered in an interactive way

2011-04-06 Thread Eric TOURNIER (JIRA) 
Keystore password should be entered in an interactive way
-

 Key: MJARSIGNER-14
 URL: http://jira.codehaus.org/browse/MJARSIGNER-14
 Project: Maven 2.x Jar Signer Plugin
  Issue Type: Improvement
Affects Versions: 1.2
Reporter: Eric TOURNIER
Priority: Minor


For security reasons, it could be useful not to configure keystore password in 
the {{pom.xml}} file. Then, when these informations are missing, the plugin 
should ask the user to enter this password in an interactive way.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (MJARSIGNER-14) Keystore password should be entered in an interactive way

2011-04-06 Thread Eric TOURNIER (JIRA) 

 [ 
http://jira.codehaus.org/browse/MJARSIGNER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric TOURNIER updated MJARSIGNER-14:


Attachment: MJARSIGNER-14-maven-jarsigner-plugin.patch

This patch asks the user for a keystore password if it not configured in pom.xml
The case of a missing key password is not included in this patch

 Keystore password should be entered in an interactive way
 -

 Key: MJARSIGNER-14
 URL: http://jira.codehaus.org/browse/MJARSIGNER-14
 Project: Maven 2.x Jar Signer Plugin
  Issue Type: Improvement
Affects Versions: 1.2
Reporter: Eric TOURNIER
Priority: Minor
 Attachments: MJARSIGNER-14-maven-jarsigner-plugin.patch


 For security reasons, it could be useful not to configure keystore password 
 in the {{pom.xml}} file. Then, when these informations are missing, the 
 plugin should ask the user to enter this password in an interactive way.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MNG-3704) NPE in DefaultLIfecycleExecutor when run from within Hudson builds

2009-02-27 Thread Eric TOURNIER (JIRA) 

[ 
http://jira.codehaus.org/browse/MNG-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=167302#action_167302
 ] 

Eric TOURNIER commented on MNG-3704:


I confirm, this is still the case.
I'm using 2.1.0-M1 with Hudson-1.285 and Cobertura Maven Plugin 2.2. When the 
plugin is not used, everything works well, but as soon as the 
{{plugin.../plugin}} section is activated, I got the NullPointerException, 
which is slighlty different from the preceding (the method where it occurs was 
not {{restoreDynamicState}} but {{calculateConcreteConfiguration}}) :\\
\\
{code}
[INFO] Preparing cobertura:cobertura
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[WARNING] Removing: cobertura from forked lifecycle, to prevent recursive 
invocation.
[HUDSON] Archiving (...)\pom.xml to (...)\pom.xml
[HUDSON] Archiving (...)\target\sequoia-security-impl-2.4.0-SNAPSHOT.jar to 
(...)\sequoia-security-impl-2.4.0-SNAPSHOT.jar
[HUDSON] Archiving 
(...)\target\sequoia-security-impl-2.4.0-SNAPSHOT-sources.jar to 
(...)\sequoia-security-impl-2.4.0-SNAPSHOT-sources.jar
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] null
[INFO] 
[INFO] Trace
java.lang.NullPointerException
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateConcreteConfiguration(DefaultLifecycleExecutor.java:759)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:538)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1177)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1018)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:625)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:538)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:517)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:369)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:330)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at 
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
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:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:158)
{code}

 NPE in DefaultLIfecycleExecutor when run from within Hudson builds
 --

 Key: MNG-3704
 URL: http://jira.codehaus.org/browse/MNG-3704
 Project: Maven 2
  Issue Type: Bug
  Components: Plugins and Lifecycle
Affects Versions: 2.0.10
Reporter: John Casey
Assignee: John Casey
Priority: Blocker
 Fix For: 2.1.0-M1


 {noformat}
 [INFO] [clean:clean]
 [HUDSON] Archiving /home/j2ee-hudson/.hudson/jobs/CXF/workspace/trunk/pom.xml 
 to 
 /home/j2ee-hudson/.hudson/jobs/CXF/modules/org.apache.cxf$cxf/builds/2008-08-11_16-49-47/archive/org.apache.cxf/cxf/2.1.2-SNAPSHOT/pom.xml
 [INFO] 
 
 [ERROR] FATAL ERROR
 [INFO] 
 
 [INFO] null
 [INFO] 
 
 [INFO] Trace
 java.lang.NullPointerException
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.restoreDynamicState(DefaultLifecycleExecutor.java:779)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:636)
   at