[jira] (ARCHETYPE-443) User defined properties are asked for in alphabetical order
Mikael Ståldal created ARCHETYPE-443: Summary: User defined properties are asked for in alphabetical order Key: ARCHETYPE-443 URL: https://jira.codehaus.org/browse/ARCHETYPE-443 Project: Maven Archetype Issue Type: Bug Components: Generator Environment: Maven 3.0.5 Reporter: Mikael Ståldal Priority: Minor I have an archetype with some properties which Maven asks for when instantiating the archetype. From archetype-metadata.xml: requiredProperties requiredProperty key=domain/ requiredProperty key=username/ requiredProperty key=password/ /requiredProperties The problem is that it asks for the properties in another order than specified in the file, it seems to be in alphabetical order. I expect it to ask for the properties in the same order as specified in archetype-metadata.xml. -- 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] (ARCHETYPE-444) Ask for user defined property without echoing on console
Mikael Ståldal created ARCHETYPE-444: Summary: Ask for user defined property without echoing on console Key: ARCHETYPE-444 URL: https://jira.codehaus.org/browse/ARCHETYPE-444 Project: Maven Archetype Issue Type: New Feature Reporter: Mikael Ståldal Given this archetype-metadata.xml: requiredProperties requiredProperty key=domain/ requiredProperty key=username/ requiredProperty key=password/ /requiredProperties I would like to be able to specify that the password property should be asked for in a secure way so that it is not echoed on console. This can be done using java.io.Console.readPassword(). -- 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] (MENFORCER-156) Upgrading maven-enforcer-plugin from 1.2 to 1.3 breaks maven-assembly-plugin
Wolf Geldmacher created MENFORCER-156: - Summary: Upgrading maven-enforcer-plugin from 1.2 to 1.3 breaks maven-assembly-plugin Key: MENFORCER-156 URL: https://jira.codehaus.org/browse/MENFORCER-156 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Affects Versions: 1.3 Environment: Ubuntu 12.04 fully patched / Maven 3.0.5 / Oracle Java 1.7.0_25 Reporter: Wolf Geldmacher Attachments: extjars.xml, pom.xml After upgrading m-e-p from 1.2 to 1.3 the maven-assembly-plugin generates the following error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single (assemble) on project extjars: Execution assemble of goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed. NullPointerException - [Help 1] Downgrading to m-e-p 1.2 makes the assembly work again. Sample pom assembly that expose the error attached. When called via: mvn -Dplugins.maven-enforcer-plugin.version=1.2 a zip file is generated as expected, when called via mvn -Dplugins.maven-enforcer-plugin.version=1.3 (or without argument) you will get the NPE. -- 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] (MDEP-423) Can not unpack dependencies from identified dependent POM without specifying version
Eric Miles created MDEP-423:
---
Summary: Can not unpack dependencies from identified dependent POM
without specifying version
Key: MDEP-423
URL: https://jira.codehaus.org/browse/MDEP-423
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: unpack
Affects Versions: 2.8
Reporter: Eric Miles
Even if the dependency from the included POM is in the dependency tree, I can
not unpack it unless I specify the version...which defeats the purpose of an
aggregator POM.
aggregator-pom.xml
{noformat}
...
groupIdmycompany.com/groupId
artifactIdaggregator-pom/artifactId
version1.0.0/version
packagingpom/packaging
...
dependency
groupIdsomegroup/groupId
artifactIdsomeartifact/artifactId
version1.2.3/version
/dependency
...
{noformat}
pom-to-do-unpacking.xml
{noformat}
...
dependency
groupIdmycompany.com/groupId
artifactIdaggregator-pom/artifactId
version1.0.0/version
packagingpom/packaging
/dependency
...
plugin
artifactIdmaven-dependency-plugin
goals
goalunpack/goal
/goal
configuration
artifactItems
artifactItem
groupIdsomegroup/groupId
artifactIdsomeartifact/artifactId
!-- Will not work without version
specified -
/artifactItem
/artifactItems
/configuration
...
/plugin
...
{noformat}
--
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] (MENFORCER-156) Upgrading maven-enforcer-plugin from 1.2 to 1.3 breaks maven-assembly-plugin
[ https://jira.codehaus.org/browse/MENFORCER-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MENFORCER-156: Assignee: Robert Scholte Upgrading maven-enforcer-plugin from 1.2 to 1.3 breaks maven-assembly-plugin Key: MENFORCER-156 URL: https://jira.codehaus.org/browse/MENFORCER-156 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Affects Versions: 1.3 Environment: Ubuntu 12.04 fully patched / Maven 3.0.5 / Oracle Java 1.7.0_25 Reporter: Wolf Geldmacher Assignee: Robert Scholte Attachments: extjars.xml, pom.xml After upgrading m-e-p from 1.2 to 1.3 the maven-assembly-plugin generates the following error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single (assemble) on project extjars: Execution assemble of goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed. NullPointerException - [Help 1] Downgrading to m-e-p 1.2 makes the assembly work again. Sample pom assembly that expose the error attached. When called via: mvn -Dplugins.maven-enforcer-plugin.version=1.2 a zip file is generated as expected, when called via mvn -Dplugins.maven-enforcer-plugin.version=1.3 (or without argument) you will get the NPE. -- 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-1007) Inconsisten encoding with large standard output
[ https://jira.codehaus.org/browse/SUREFIRE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=327929#comment-327929 ] Kristian Rosenvold commented on SUREFIRE-1007: -- I'll be changing something in this area soon. Unsure what effect this will have wrt this issue, but hopefully it might fix something :) I'm assuming this is bascally a bug in the jdk, but we are probably behaving a bit oddly too, so a change on our end might be beneficial. i'll ping back on this issue once an updated snapshot is available. The only workaround would probably to downgrade to something like version 2.6 or so. Inconsisten encoding with large standard output --- Key: SUREFIRE-1007 URL: https://jira.codehaus.org/browse/SUREFIRE-1007 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Report Plugin, xml generation Affects Versions: 2.14.1, 2.15 Reporter: Yves Langisch Attachments: ibm-jdk7.log, ora-jdk7.log, surefire-encoding-test.zip, TEST-net.test.surefireencodingtest.EncodingTest.xml When having a lot of standard output in a failing test, the encoding of the resulting surefire-report XML is not consistent. The attached project shows that the encoding in 'TEST-net.test.surefireencodingtest.EncodingTest.xml' in the element system-out suddenly switches from UTF-8 to ISO-8859-1. Any workaround is highly appreciated... -- 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] (MENFORCER-156) Upgrading maven-enforcer-plugin from 1.2 to 1.3 breaks maven-assembly-plugin
[
https://jira.codehaus.org/browse/MENFORCER-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=327935#comment-327935
]
Robert Scholte commented on MENFORCER-156:
--
MENFORCER-42 is an important improvement, it seems to have a side-effect: even
though dependencies are now calculated instead of gathered, the artifact is
still marked as {{resolved}} afterwards. The assembly-plugin checks if the
artifacts is resolved, otherwise i'll search the local and remote repositories
for the files. ( The NPE is caused by the {{artifact.getFile()}} ).
I think the assumption of the assembly-plugin is correct, so I have to figure
out why the new [Maven Dependency
Tree|http://maven.apache.org/shared/maven-dependency-tree/] marks those
artifacts as resolved.
Upgrading maven-enforcer-plugin from 1.2 to 1.3 breaks maven-assembly-plugin
Key: MENFORCER-156
URL: https://jira.codehaus.org/browse/MENFORCER-156
Project: Maven 2.x Enforcer Plugin
Issue Type: Bug
Affects Versions: 1.3
Environment: Ubuntu 12.04 fully patched / Maven 3.0.5 / Oracle Java
1.7.0_25
Reporter: Wolf Geldmacher
Assignee: Robert Scholte
Attachments: extjars.xml, pom.xml
After upgrading m-e-p from 1.2 to 1.3 the maven-assembly-plugin generates the
following error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (assemble) on
project extjars: Execution assemble of goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
NullPointerException - [Help 1]
Downgrading to m-e-p 1.2 makes the assembly work again.
Sample pom assembly that expose the error attached.
When called via:
mvn -Dplugins.maven-enforcer-plugin.version=1.2
a zip file is generated as expected, when called via
mvn -Dplugins.maven-enforcer-plugin.version=1.3
(or without argument) you will get the NPE.
--
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
