[jira] (MANTTASKS-177) artifact:dependencies ignores settings-security.xml and sends password hash to repository
[
https://jira.codehaus.org/browse/MANTTASKS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292720#comment-292720
]
SebbASF edited comment on MANTTASKS-177 at 2/24/12 7:16 PM:
Still seems to be broken in 2.1.3 - for deploy at least
was (Author: sebbasf):
Still seems to be broken in 2.1.3
> 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
>
> I have a mirror repository configured in .m2/settings.xml, and its
> entry uses an encrypted password in , 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
>
>
>
> paytronix-public
>
> https://greylock.corp.paytronix.com/nexus/content/groups/public
> *
>
>
>
>
> paytronix-public
> rmellgren
>
>
>
>
> 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:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-177) artifact:dependencies ignores settings-security.xml and sends password hash to repository
[
https://jira.codehaus.org/browse/MANTTASKS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292720#comment-292720
]
SebbASF commented on MANTTASKS-177:
---
Still seems to be broken in 2.1.3
> 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
>
> I have a mirror repository configured in .m2/settings.xml, and its
> entry uses an encrypted password in , 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
>
>
>
> paytronix-public
>
> https://greylock.corp.paytronix.com/nexus/content/groups/public
> *
>
>
>
>
> paytronix-public
> rmellgren
>
>
>
>
> 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:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-240) NullPointerException thrown during Dependencies report
Coda Hale created MPIR-240:
--
Summary: NullPointerException thrown during Dependencies report
Key: MPIR-240
URL: https://jira.codehaus.org/browse/MPIR-240
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: dependencies
Affects Versions: 2.4
Environment: MacOS 10.7.3, Oracle JDK 7u4 Preview, Maven 3.0.4,
maven-site-plugin 3.0
Reporter: Coda Hale
This POM:
{code:title=pom.xml}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
com.example
maven-dependencies-bug
0.0.1-SNAPSHOT
com.sun.jersey
jersey-server
1.12
org.apache.maven.plugins
maven-site-plugin
3.0
org.apache.maven.plugins
maven-project-info-reports-plugin
2.4
{code}
Throws this exception:
{noformat}
$ mvn -e clean site
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building maven-dependencies-bug 0.0.1-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
maven-dependencies-bug ---
[INFO] Deleting /private/tmp/maven-jersey-poop/target
[INFO]
[INFO] --- maven-site-plugin:3.0:site (default-site) @ maven-dependencies-bug
---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.4
[WARNING] No project URL defined - decoration links will not be relativized!
[INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0
skin.
[INFO] Generating "Distribution Management" report---
maven-project-info-reports-plugin:2.4
[INFO] Generating "About" report--- maven-project-info-reports-plugin:2.4
[INFO] Generating "Dependencies" report---
maven-project-info-reports-plugin:2.4
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.978s
[INFO] Finished at: Fri Feb 24 14:05:06 PST 2012
[INFO] Final Memory: 13M/75M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project
maven-dependencies-bug: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.0:site failed.
NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project
maven-dependencies-bug: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.0:site failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
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:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
[jira] (SUREFIRE-844) "test" parameter no longer working with JUnit in 2.12 (worked in 2.9 - 2.11)
Mark Ziesemer created SUREFIRE-844: -- Summary: "test" parameter no longer working with JUnit in 2.12 (worked in 2.9 - 2.11) Key: SUREFIRE-844 URL: https://jira.codehaus.org/browse/SUREFIRE-844 Project: Maven Surefire Issue Type: Bug Components: Junit 4.x support Affects Versions: 2.12 Environment: JDK 1.7.0_02, Windows 7. Reporter: Mark Ziesemer Maven is configured with JUnit 4.10. Assume a 'MyTest' class with public, non-static, 0-arg methods annotated with org.junit.Test. This was working with Surefire 2.9, 2.10, and 2.11 (and probably earlier): org.apache.maven.plugins maven-surefire-plugin 2.11 com.example.MyTest With only updating the Surefire version from 2.11 to 2.12, the tests no longer execute: --- T E S T S --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 I don't see anything in the release announcement that should account for this. If I remove the 'test' parameter entirely, it will again successfully run - but will run all tests that it finds instead of what I'm expecting it to run. I can't attach any additional details from what I'm currently working on, but will work on providing a proper minimal test case over the weekend. -- 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] (MSITE-596) inheritedReports IT fails
[ https://jira.codehaus.org/browse/MSITE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292705#comment-292705 ] Karl M. Davis commented on MSITE-596: - Please note that some folks (me, for example) are now relying on the Maven 3 behavior to exclude reports in child projects. If you change this behavior, a number of my projects would break as I need a way to exclude reports occasionally. > inheritedReports IT fails > - > > Key: MSITE-596 > URL: https://jira.codehaus.org/browse/MSITE-596 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: inheritance, Maven 3 >Affects Versions: 3.0-beta-3 >Reporter: Herve Boutemy > Fix For: 3.1 > > > as discovered in MSITE-595: > - with M2, each report is added: child has 2 reports generated = index+summary > - with M3, each report replaces previous one: child has 1 report = summary > What is the expected behaviour? I'd say M2 is buggy, since POM inheritance > logic usually replaces instead adding > Should we try to stick with M2 behaviour? (if feasible, I still didn't check) -- 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] (MRESOURCES-153) Usage of copy-resources changes testResources copying behaviour
[
https://jira.codehaus.org/browse/MRESOURCES-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292693#comment-292693
]
Myron commented on MRESOURCES-153:
--
ok, i think i found my "problem"
When the configuration is on plugin level, then this behaviour occurs.
Since i wanted to have an extra execution, i do the additional configuration
within the execution tag.
This seems to work; not overriding the plugin config.
> Usage of copy-resources changes testResources copying behaviour
> ---
>
> Key: MRESOURCES-153
> URL: https://jira.codehaus.org/browse/MRESOURCES-153
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: copy
>Affects Versions: 2.4.2, 2.5
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: C:\Program Files\apache-maven-3.0.3\bin\..
> Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_26\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Myron
> Attachments: resources-debug.txt
>
>
> Create a dummy project, add foo.txt to src/test/resources
> do a "mvn clean package"
> foo.txt appears in target/test-classes/foo.txt and is not in packaged jar (as
> supposed)
> Add build step to copy some additonal files to classpath/jar and again do a
> "mvn clean package"
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-resources-plugin
> 2.5
>
>
>
> copy-resources
>
> process-resources
>
>
>
>
>
> src/main/additional
>
>
>
> ${project.build.outputDirectory}
>
>
>
> {code}
> now what happens:
> the files in "additional" are copied to target/classes (as supposed) but the
> foo.txt AS WELL (not supposed)
> target/test-classes is now empty and all the test resources are packaged into
> jar
> So specifying the copy-resource goal results in an reconfiguration of the
> test-resources copy operation?!
> [DEBUG] copy C:\Users\myron\workspace\test\src\test\resources\foo.txt to
> C:\Users\myron\workspace\test\target\classes\foo.txt
> complete debug attached
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292636#comment-292636
]
Stephane Nicoll commented on MEAR-141:
--
There was some confusion at the beginning but the issue is coming from Maven 2,
not linux (probably some plexus dependency chain nightmare).
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stephane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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-276) packagingIncludes should be case insensitive with file types
ToM created MWAR-276: Summary: packagingIncludes should be case insensitive with file types Key: MWAR-276 URL: https://jira.codehaus.org/browse/MWAR-276 Project: Maven 2.x WAR Plugin Issue Type: Improvement Components: filtering Affects Versions: 2.2 Environment: All Reporter: ToM I used the packagingIncludes mechanism and got an exception. After some research i realized that **/*.png missed a file which was named *.PNG This behaviour should be improved. Thanks -- 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] (MCOMPILER-140) Compiler error messages do not contain drive letter on windows
[ https://jira.codehaus.org/browse/MCOMPILER-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292626#comment-292626 ] Kristian Rosenvold commented on MCOMPILER-140: -- And r1293132 for compiler-plugin > Compiler error messages do not contain drive letter on windows > --- > > Key: MCOMPILER-140 > URL: https://jira.codehaus.org/browse/MCOMPILER-140 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.1, 2.2, 2.3, 2.3.1, 2.3.2 > Environment: Maven 2.2.1, Windows >Reporter: Anton Makeev >Assignee: Kristian Rosenvold > Attachments: MCOMPILER-140.diff, WidgetCore.zip > > > See original bug request: http://youtrack.jetbrains.net/issue/IDEA-59521 > User description: > I tried it with a toy project and it worked as you say. The errors in the > console for the toy project had the complete path in the error: > [INFO] Compilation failure > C:\projects\java\eclipseOnly\WidgetCore\src\main\java\com\acme\core\CoreClass.java:[6,8] > not a statement > C:\projects\java\eclipseOnly\WidgetCore\src\main\java\com\acme\core\CoreClass.java:[6,14] > ';' expected > In my non-toy project where I'm seeing the error, the C: is not there. > [ERROR] COMPILATION ERROR : > [INFO] > [ERROR] > \projects\java\eclipseproj\MyProj\unittests\com\acme\messaging\configuration\ConfigurationTest.java:[12,8] > not a statement > [ERROR] > \projects\java\eclipseproj\MyProj\unittests\com\acme\messaging\configuration\ConfigurationTest.java:[12,14] > ';' expected -- 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
