[jira] (MANTTASKS-177) artifact:dependencies ignores settings-security.xml and sends password hash to repository

2013-07-17 Thread cforce (JIRA)

[ 
https://jira.codehaus.org/browse/MANTTASKS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=328787#comment-328787
 ] 

cforce commented on MANTTASKS-177:
--

Are there any beta build artefact`s for download?
Will this ever be released??
How can a MAJOR bug be on track this 5 MONTHS!!!

 artifact:dependencies ignores settings-security.xml and sends password hash 
 to repository
 -

 Key: MANTTASKS-177
 URL: https://jira.codehaus.org/browse/MANTTASKS-177
 Project: Maven 2.x Ant Tasks
  Issue Type: Bug
  Components: dependencies task
Affects Versions: 2.1.0
 Environment: Mac OS X, Ant 1.7.1, Maven 2.2.1, maven-ant-tasks 2.1.0, 
 Sonatype Nexus Open Source Edition 1.5.0
Reporter: Ross Mellgren
Assignee: Olivier Lamy
 Fix For: 3.0.0-beta-1

 Attachments: decrypt.patch


 I have a mirror repository configured in .m2/settings.xml, and its server 
 entry uses an encrypted password in password, using the master password set 
 in .m2/settings-security.xml.
 I followed this guide:
 http://maven.apache.org/guides/mini/guide-encryption.html
 I get authentication errors every time i use
 {code:xml}
 ?xml version=1.0 ?
 settings
 mirrors
 mirror
 idpaytronix-public/id
 
 urlhttps://greylock.corp.paytronix.com/nexus/content/groups/public/url
 mirrorOf*/mirrorOf
 /mirror
 /mirrors
 servers
 server
 idpaytronix-public/id
 usernamermellgren/username
 !-- password element omitted --
 /server
 /servers
 /settings
 {code}
 I switched to http and then used tcpdump to watch the request, then decoded 
 the Authorization header. The {mumblemumble} password hash was sent not the 
 decrypted password.
 Looking into maven-ant-tasks.jar, I see a META-INF/plexus/components.xml 
 which does not include plexus-sec-dispatcher from maven-core. I tried 
 spinning my own copy of maven-ant-tasks with the appropriate component for 
 plexus-sec-dispatcher added, but it didn't work, so I think I'm out of my 
 depth in the troubleshooting/rectification department.

--
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] (SUREFIRE-996) system-out and system-err content of junit xml report are not escaped

2013-07-17 Thread Todor Todorov (JIRA)

[ 
https://jira.codehaus.org/browse/SUREFIRE-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=328792#comment-328792
 ] 

Todor Todorov commented on SUREFIRE-996:


Since this issue has already been closed, I am not sure what to do?! Should I 
open another issue like Wrong XML illegal characters escape in system-out 
and system-err content, or there is a way to reopen it. The patch I 
submitted is based on the last development version. Please let me know if you 
need patch based on version 2.15.

 system-out and system-err content of junit xml report are not escaped
 -

 Key: SUREFIRE-996
 URL: https://jira.codehaus.org/browse/SUREFIRE-996
 Project: Maven Surefire
  Issue Type: Bug
  Components: Junit 4.7+ (parallel) support
Affects Versions: 2.15
 Environment: maven 3.0.4
 surefire 2.15-SNAPSHOT (from apache snashot repo)
Reporter: Julien Vermillard
Assignee: Kristian Rosenvold
Priority: Blocker
 Fix For: 2.15

 Attachments: 0001-added-test-case-for-SUREFIRE-996.patch, 
 extended-test-case-for-SUREFIRE-996.patch


 Some of my junit xml report are not correctly generated :
 {code}
 system-out15:24:59.565 [pool-1-thread-5] INFO  
 c.s.a.i.c.s.api.PartnerServicesUtils - Profile null 
 /system-out
 {code}
 The  and  in null are not escaped.
 If I look at 
 maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/StatelessXmlReporter.java
 code, I think the bug is here :
 {code}
 addOutputStreamElement( outputStreamWriter, fw, eos, ppw, 
 report.getStdout(), system-out );
 addOutputStreamElement( outputStreamWriter, fw, eos, ppw, 
 report.getStdErr(), system-err );
 ppw.endElement(); // test element
 }
 private void addOutputStreamElement( OutputStreamWriter 
 outputStreamWriter, OutputStream fw, EncodingOutputStream eos, XMLWriter 
 xmlWriter, DeferredFileOutputStream stdOut,
  String name )
 {
 if ( stdOut != null  stdOut.getByteCount()  0 )
 {
 xmlWriter.startElement( name );
 try
 {
 xmlWriter.writeText(  ); // Cheat sax to emit element
 outputStreamWriter.flush();
 stdOut.close();
 stdOut.writeTo( eos );
 eos.flush();
 }
 catch ( IOException e )
 {
 throw new ReporterException( When writing xml report 
 stdout/stderr, e );
 }
 xmlWriter.endElement();
 }
 }
 {code}
 and probably introduced by this commit : 
 commit 33e110fc46aa43d10b38a93b3db74c09be6bc6d5
 Author: Kristian Rosenvold krosenv...@apache.org
 Date:   Thu May 2 20:53:27 2013 +0200
 [SUREFIRE-938] Removed memory binding for stdout/stderr capture.

--
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] (MSITE-695) java.lang.NullPointerException in org.apache.maven.plugins.site.SiteStageDeployMojo.getTopMostParentWithSameStagingSiteURL

2013-07-17 Thread Gary Gregory (JIRA)
Gary Gregory created MSITE-695:
--

 Summary: java.lang.NullPointerException in 
org.apache.maven.plugins.site.SiteStageDeployMojo.getTopMostParentWithSameStagingSiteURL
 Key: MSITE-695
 URL: https://jira.codehaus.org/browse/MSITE-695
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Bug
  Components: site:stage(-deploy)
Affects Versions: 3.3, 3.2
 Environment: Apache Maven 3.0.5 
(r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 08:51:28-0500)
Maven home: C:\Java\apache-maven-3.0.5\bin\..
Java version: 1.7.0_25, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_25\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: windows

and

C:\vcs\svn\apache\log4j2\trunkC:\Java\apache-maven-3.1.0\bin\mvn.bat -version
Apache Maven 3.1.0 (893ca28a1da9d5f51ac03827af98bb730128f9f2; 2013-06-27 
22:15:32-0400)
Maven home: C:\Java\apache-maven-3.1.0\bin\..
Java version: 1.7.0_25, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_25\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: windows
Reporter: Gary Gregory


Checkout log4j 2 from:

https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk 

The HEAD of trunk is currently revision 1504131.

Run: 

mvn clean site

Get:

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 3.724s
[INFO] Finished at: Wed Jul 17 12:43:47 EDT 2013
[INFO] Final Memory: 22M/213M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy (default-cli) on 
project log4j: Execution default-cli of goal 
org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy failed. NullPoint
erException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy (default-cli) on 
project log4j: Execution default-cli of goal org.apache.maven.plugins:mave
n-site-plugin:3.3:stage-deploy failed.
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
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:318)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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:414)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy 
failed.
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: java.lang.NullPointerException
at 
org.apache.maven.plugins.site.SiteStageDeployMojo.getTopMostParentWithSameStagingSiteURL(SiteStageDeployMojo.java:144)
at 
org.apache.maven.plugins.site.SiteStageDeployMojo.determineTopDistributionManagementSiteUrl(SiteStageDeployMojo.java:102)
at 
org.apache.maven.plugins.site.AbstractDeployMojo.getTopDistributionManagementSiteUrl(AbstractDeployMojo.java:207)
at 

[jira] (MSITE-695) java.lang.NullPointerException in org.apache.maven.plugins.site.SiteStageDeployMojo.getTopMostParentWithSameStagingSiteURL

2013-07-17 Thread Herve Boutemy (JIRA)

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

Herve Boutemy updated MSITE-695:


Description: 
Checkout log4j 2 from:

https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk 

The HEAD of trunk is currently revision 1504131.

Run: 

mvn clean site

Get:

{noformat}[INFO] 

[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 3.724s
[INFO] Finished at: Wed Jul 17 12:43:47 EDT 2013
[INFO] Final Memory: 22M/213M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy (default-cli) on 
project log4j: Execution default-cli of goal 
org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy failed. 
NullPointerException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy (default-cli) on 
project log4j: Execution default-cli of goal 
org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy failed.
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
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:318)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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:414)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy 
failed.
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: java.lang.NullPointerException
at 
org.apache.maven.plugins.site.SiteStageDeployMojo.getTopMostParentWithSameStagingSiteURL(SiteStageDeployMojo.java:144)
at 
org.apache.maven.plugins.site.SiteStageDeployMojo.determineTopDistributionManagementSiteUrl(SiteStageDeployMojo.java:102)
at 
org.apache.maven.plugins.site.AbstractDeployMojo.getTopDistributionManagementSiteUrl(AbstractDeployMojo.java:207)
at 
org.apache.maven.plugins.site.AbstractDeployMojo.getDeployModuleDirectory(AbstractDeployMojo.java:249)
at 
org.apache.maven.plugins.site.AbstractDeployMojo.deploy(AbstractDeployMojo.java:320)
at 
org.apache.maven.plugins.site.AbstractDeployMojo.deployTo(AbstractDeployMojo.java:281)
at 
org.apache.maven.plugins.site.AbstractDeployMojo.execute(AbstractDeployMojo.java:163)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
... 20 more
[ERROR]
[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/PluginExecutionException{noformat}

Version 3.0 is fine.


  was:
Checkout log4j 2 from:

https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk 

The HEAD of trunk is currently revision 1504131.

Run: 

mvn clean site

Get:

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO]