[jira] (MNG-5559) upgrade to last wagon 2.6
[ https://jira.codehaus.org/browse/MNG-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MNG-5559. - Resolution: Fixed fixed https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=60437a28 > upgrade to last wagon 2.6 > - > > Key: MNG-5559 > URL: https://jira.codehaus.org/browse/MNG-5559 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 3.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] (MNG-5559) upgrade to last wagon 2.6
[ https://jira.codehaus.org/browse/MNG-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned MNG-5559: - Assignee: Olivier Lamy > upgrade to last wagon 2.6 > - > > Key: MNG-5559 > URL: https://jira.codehaus.org/browse/MNG-5559 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Reporter: Olivier Lamy >Assignee: Olivier Lamy > -- 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] (MNG-5559) upgrade to last wagon 2.6
[ https://jira.codehaus.org/browse/MNG-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MNG-5559: -- Fix Version/s: 3.2 > upgrade to last wagon 2.6 > - > > Key: MNG-5559 > URL: https://jira.codehaus.org/browse/MNG-5559 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 3.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] (MNG-5559) upgrade to last wagon 2.6
Olivier Lamy created MNG-5559: - Summary: upgrade to last wagon 2.6 Key: MNG-5559 URL: https://jira.codehaus.org/browse/MNG-5559 Project: Maven 2 & 3 Issue Type: Bug Components: Dependencies Reporter: Olivier Lamy -- 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] (MNG-5454) cvc-complex-type.3.2.2: Attribute 'combine.self' is not allowed to appear in element 'executions'.
[ https://jira.codehaus.org/browse/MNG-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338337#comment-338337 ] Matthew Hall commented on MNG-5454: --- Why are you closing it as "Not a Bug" with no explanation why it is not a bug? The XML schema does not specify that "combine.*" attributes are allowed, and using them causes a schema validation failure. This is a bug in Maven's XML schema for POMs. > cvc-complex-type.3.2.2: Attribute 'combine.self' is not allowed to appear in > element 'executions'. > -- > > Key: MNG-5454 > URL: https://jira.codehaus.org/browse/MNG-5454 > Project: Maven 2 & 3 > Issue Type: Bug > Components: POM >Affects Versions: 3.0.4 > Environment: springsource3.2.0_with_Juno3.8.2 >Reporter: Sebastien Tardif >Assignee: Robert Scholte > > This generate an error: > > > maven-antrun-plugin >combine.self="override" > > > > default-cli > > > run > > > > > > > > > > > > > > -- 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-406) Support of velocity expressions for user-defined properties
[
https://jira.codehaus.org/browse/ARCHETYPE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338336#comment-338336
]
Mark Jeffcoat commented on ARCHETYPE-406:
-
I've attached a proposed fix. I generated the patch from the trunk, but it
should also apply cleanly to 2.2.
The reason this didn't work (consistently) before is that the order in which it
attempted to resolve properties was arbitrary; if a user-defined property was
already in the Context, it could be used by later Velocity expressions; if it
wasn't already in the Context, any reference to it would be interpreted
literally. The arbitrary order of evaluation is why the examples in the
comments are so confusing.
This patch forces the archetype generator to keep trying to resolve things that
look like Velocity expressions until it can no longer make any further
progress. It Works For Me, but I'd appreciate any comments.
> Support of velocity expressions for user-defined properties
> ---
>
> Key: ARCHETYPE-406
> URL: https://jira.codehaus.org/browse/ARCHETYPE-406
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.x
>Reporter: Bue Pierre-Christophe
> Attachments: ARCHETYPE-406.patch, sample-archetype406.tar.gz
>
>
> Standard properties (artifactId, groupId, ...) are supported in Velocity
> expressiosn, but still does not work with user defined properties. For
> example:
>
> ${artifactId}.substring(0,1).toUpperCase()
>
> with artifactId=toto will give a=T, but
>
>
> ${b}.substring(0,1).toUpperCase()
>
> with b=toto will give a=${b}.substring(0,1).toUpperCase()
--
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] (MNG-5411) Missing file activation only works with hard coded vales
[
https://jira.codehaus.org/browse/MNG-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MNG-5411.
---
Resolution: Not A Bug
Assignee: Robert Scholte
This is by design, see also http://maven.apache.org/pom.html#Activation
> Missing file activation only works with hard coded vales
>
>
> Key: MNG-5411
> URL: https://jira.codehaus.org/browse/MNG-5411
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0.4
> Environment: Fedora 17 x86_64, Java 1.7.0_09-icedtea
>Reporter: Bill Riemers
>Assignee: Robert Scholte
>Priority: Minor
>
> {code:xml}
> ...
> {code}
> Only works when the file name is hard coded between the missing tags to
> activate a profile. If instead the file name is listed as a property (or
> properties) the profile is always active.
> e.g.
> {code:xml}
> ...
>
> example.txt
> ${project.build.directory}/example.txt
>
> ...
>
>
>
> ${exampleDirectory}/${exampleFile}
>
> ...
>
> ...
>
> ...
> {code}
> The profile here will be active regardless if the wsdlFile exists. However,
> if instead one hard codes the value like so:
> {code:xml} target/example.txt {code}
> then the profile is only active when example.txt does not exist.
> I'm guessing this is a chicken and egg problem. The properties section is
> probably not evaluated until after deciding what profiles should be active.
> In which case, the code itself is working as designed, it is just either that
> design needs to be documented or updated to work the way one would expect.
--
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] (MNG-5411) Missing file activation only works with hard coded vales
[
https://jira.codehaus.org/browse/MNG-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MNG-5411:
Description:
{code:xml}
...
{code}
Only works when the file name is hard coded between the missing tags to
activate a profile. If instead the file name is listed as a property (or
properties) the profile is always active.
e.g.
{code:xml}
...
example.txt
${project.build.directory}/example.txt
...
${exampleDirectory}/${exampleFile}
...
...
...
{code}
The profile here will be active regardless if the wsdlFile exists. However,
if instead one hard codes the value like so:
{code:xml} target/example.txt {code}
then the profile is only active when example.txt does not exist.
I'm guessing this is a chicken and egg problem. The properties section is
probably not evaluated until after deciding what profiles should be active. In
which case, the code itself is working as designed, it is just either that
design needs to be documented or updated to work the way one would expect.
was:
...
Only works when the file name is hard coded between the missing tags to
activate a profile. If instead the file name is listed as a property (or
properties) the profile is always active.
e.g.
...
example.txt
${project.build.directory}/example.txt
...
${exampleDirectory}/${exampleFile}
...
...
...
The profile here will be active regardless if the wsdlFile exists. However,
if instead one hard codes the value like so:
target/example.txt
then the profile is only active when example.txt does not exist.
I'm guessing this is a chicken and egg problem. The properties section is
probably not evaluated until after deciding what profiles should be active. In
which case, the code itself is working as designed, it is just either that
design needs to be documented or updated to work the way one would expect.
> Missing file activation only works with hard coded vales
>
>
> Key: MNG-5411
> URL: https://jira.codehaus.org/browse/MNG-5411
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0.4
> Environment: Fedora 17 x86_64, Java 1.7.0_09-icedtea
>Reporter: Bill Riemers
>Priority: Minor
>
> {code:xml}
> ...
> {code}
> Only works when the file name is hard coded between the missing tags to
> activate a profile. If instead the file name is listed as a property (or
> properties) the profile is always active.
> e.g.
> {code:xml}
> ...
>
> example.txt
> ${project.build.directory}/example.txt
>
> ...
>
>
>
> ${exampleDirectory}/${exampleFile}
>
> ...
>
> ...
>
> ...
> {code}
> The profile here will be active regardless if the wsdlFile exists. However,
> if instead one hard codes the value like so:
> {code:xml} target/example.txt {code}
> then the profile is only active when example.txt does not exist.
> I'm guessing this is a chicken and egg problem. The properties section is
> probably not evaluated until after deciding what profiles should be active.
> In which case, the code itself is working as designed, it is just either that
> design needs to be documented or updated to work the way one would expect.
--
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-406) Support of velocity expressions for user-defined properties
[
https://jira.codehaus.org/browse/ARCHETYPE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Jeffcoat updated ARCHETYPE-406:
Attachment: ARCHETYPE-406.patch
> Support of velocity expressions for user-defined properties
> ---
>
> Key: ARCHETYPE-406
> URL: https://jira.codehaus.org/browse/ARCHETYPE-406
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.x
>Reporter: Bue Pierre-Christophe
> Attachments: ARCHETYPE-406.patch, sample-archetype406.tar.gz
>
>
> Standard properties (artifactId, groupId, ...) are supported in Velocity
> expressiosn, but still does not work with user defined properties. For
> example:
>
> ${artifactId}.substring(0,1).toUpperCase()
>
> with artifactId=toto will give a=T, but
>
>
> ${b}.substring(0,1).toUpperCase()
>
> with b=toto will give a=${b}.substring(0,1).toUpperCase()
--
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] (MNG-5454) cvc-complex-type.3.2.2: Attribute 'combine.self' is not allowed to appear in element 'executions'.
[ https://jira.codehaus.org/browse/MNG-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-5454. --- Resolution: Not A Bug Assignee: Robert Scholte See also http://blog.sonatype.com/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/ > cvc-complex-type.3.2.2: Attribute 'combine.self' is not allowed to appear in > element 'executions'. > -- > > Key: MNG-5454 > URL: https://jira.codehaus.org/browse/MNG-5454 > Project: Maven 2 & 3 > Issue Type: Bug > Components: POM >Affects Versions: 3.0.4 > Environment: springsource3.2.0_with_Juno3.8.2 >Reporter: Sebastien Tardif >Assignee: Robert Scholte > > This generate an error: > > > maven-antrun-plugin >combine.self="override" > > > > default-cli > > > run > > > > > > > > > > > > > > -- 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] (MNG-5458) Missing newline when using -V
[
https://jira.codehaus.org/browse/MNG-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MNG-5458:
Description:
When using mvn -V, there's a small difference in the output:
With m3.0.4:
{noformat}
$ mvn -V clean verify
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: /home/tiste/tools/Mavens/maven
Java version: 1.6.0_37, vendor: Sun Microsystems Inc.
Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux", version: "3.5.0-26-generic", arch: "amd64", family: "unix"
[INFO] Scanning for projects...
[INFO]
{noformat}
With m3.1.0-alpha-1:
{noformat}
$ mvn -V clean verify
Apache Maven 3.1.0-alpha-1 (262b9bb1ef91d1414e5162d9dd0f5522e7186202;
2013-03-30 22:38:49+0100)
Maven home: /home/tiste/tools/Mavens/maven
Java version: 1.6.0_37, vendor: Sun Microsystems Inc.
Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux", version: "3.5.0-26-generic", arch: "amd64", family:
"unix"[INFO] Scanning for projects...
[INFO]
{noformat}
was:
When using mvn -V, there's a small difference in the output:
With m3.0.4:
$ mvn -V clean verify
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: /home/tiste/tools/Mavens/maven
Java version: 1.6.0_37, vendor: Sun Microsystems Inc.
Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux", version: "3.5.0-26-generic", arch: "amd64", family: "unix"
[INFO] Scanning for projects...
[INFO]
With m3.1.0-alpha-1:
$ mvn -V clean verify
Apache Maven 3.1.0-alpha-1 (262b9bb1ef91d1414e5162d9dd0f5522e7186202;
2013-03-30 22:38:49+0100)
Maven home: /home/tiste/tools/Mavens/maven
Java version: 1.6.0_37, vendor: Sun Microsystems Inc.
Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux", version: "3.5.0-26-generic", arch: "amd64", family:
"unix"[INFO] Scanning for projects...
[INFO]
> Missing newline when using -V
> -
>
> Key: MNG-5458
> URL: https://jira.codehaus.org/browse/MNG-5458
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.1.0-alpha-1
> Environment: linux x64, jdk
>Reporter: Baptiste Mathus
>Assignee: Arnaud Heritier
>Priority: Minor
> Fix For: 3.1.0
>
>
> When using mvn -V, there's a small difference in the output:
> With m3.0.4:
> {noformat}
> $ mvn -V clean verify
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: /home/tiste/tools/Mavens/maven
> Java version: 1.6.0_37, vendor: Sun Microsystems Inc.
> Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre
> Default locale: fr_FR, platform encoding: UTF-8
> OS name: "linux", version: "3.5.0-26-generic", arch: "amd64", family: "unix"
> [INFO] Scanning for projects...
> [INFO]
>
> {noformat}
> With m3.1.0-alpha-1:
> {noformat}
> $ mvn -V clean verify
> Apache Maven 3.1.0-alpha-1 (262b9bb1ef91d1414e5162d9dd0f5522e7186202;
> 2013-03-30 22:38:49+0100)
> Maven home: /home/tiste/tools/Mavens/maven
> Java version: 1.6.0_37, vendor: Sun Microsystems Inc.
> Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre
> Default locale: fr_FR, platform encoding: UTF-8
> OS name: "linux", version: "3.5.0-26-generic", arch: "amd64", family:
> "unix"[INFO] Scanning for projects...
> [INFO]
> {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] (MNG-5458) Missing newline when using -V
[ https://jira.codehaus.org/browse/MNG-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-5458. --- Resolution: Fixed Fix Version/s: 3.1.0 Assignee: Arnaud Heritier (Already) fixed in http://git-wip-us.apache.org/repos/asf/maven/commit/4e24edbc > Missing newline when using -V > - > > Key: MNG-5458 > URL: https://jira.codehaus.org/browse/MNG-5458 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.1.0-alpha-1 > Environment: linux x64, jdk >Reporter: Baptiste Mathus >Assignee: Arnaud Heritier >Priority: Minor > Fix For: 3.1.0 > > > When using mvn -V, there's a small difference in the output: > With m3.0.4: > $ mvn -V clean verify > Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) > Maven home: /home/tiste/tools/Mavens/maven > Java version: 1.6.0_37, vendor: Sun Microsystems Inc. > Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre > Default locale: fr_FR, platform encoding: UTF-8 > OS name: "linux", version: "3.5.0-26-generic", arch: "amd64", family: "unix" > [INFO] Scanning for projects... > [INFO] > > With m3.1.0-alpha-1: > $ mvn -V clean verify > Apache Maven 3.1.0-alpha-1 (262b9bb1ef91d1414e5162d9dd0f5522e7186202; > 2013-03-30 22:38:49+0100) > Maven home: /home/tiste/tools/Mavens/maven > Java version: 1.6.0_37, vendor: Sun Microsystems Inc. > Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre > Default locale: fr_FR, platform encoding: UTF-8 > OS name: "linux", version: "3.5.0-26-generic", arch: "amd64", family: > "unix"[INFO] Scanning for projects... > [INFO] -- 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] (JXR-107) Line number anchor names have changed in an incompatible way.
Christian Schulte created JXR-107: - Summary: Line number anchor names have changed in an incompatible way. Key: JXR-107 URL: https://jira.codehaus.org/browse/JXR-107 Project: Maven JXR Issue Type: Bug Components: maven2 jxr plugin Affects Versions: 2.4 Reporter: Christian Schulte Upgrading the 'maven-jxr-plugin' to version 2.4 breaks reports generated by other reporting plugins due to the line number anchor names changing from e.g. '#1' to '#L1'. The old anchor names should be generated again instead. -- 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-34) The 'verify' goal of the plugin is passing '-keystore' but not '-storetype'.
Christian Schulte created MJARSIGNER-34:
---
Summary: The 'verify' goal of the plugin is passing '-keystore'
but not '-storetype'.
Key: MJARSIGNER-34
URL: https://jira.codehaus.org/browse/MJARSIGNER-34
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.3.1
Reporter: Christian Schulte
Priority: Blocker
Upgrading the 'maven-jarsigner-plugin' from version 1.2 to version 1.3.1, the
plugin stops working. In version 1.2, the 'verify' goal did not pass
'-keystore' to 'jarsigner'. As of version 1.3, the 'verify' goal passes
'-keystore' to 'jarsigner' but does not pass '-storetype' which makes the
'verify' goal fail with:
jarsigner error: keystore load: Invalid keystore format
due to
{xml}
pkcs12
{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] (SUREFIRE-1052) Use "project.build.sourceEncoding"-Property by default for forked jvm
Dieter König created SUREFIRE-1052:
--
Summary: Use "project.build.sourceEncoding"-Property by default
for forked jvm
Key: SUREFIRE-1052
URL: https://jira.codehaus.org/browse/SUREFIRE-1052
Project: Maven Surefire
Issue Type: Bug
Components: classloading, Maven Surefire Plugin, process forking
Affects Versions: 2.16, 2.10
Reporter: Dieter König
Attachments: pom.xml, SurefireEncodingTestCase.java
maven-surefire-plugin is ignoring "project.build.sourceEncoding"-property when
forking jvm for testcase execution.
The attached testcase fails with surefire for a project configured as UTF-8 but
is successful when executed in eclipse.
Known Workaround:
Configure surefire in the following way
-Dfile.encoding=${project.build.sourceEncoding}
P.S.: Unfortunately the oracle jvm itself is also unsafe. Executing the
testcase with java.exe (without file.encoding-argument) gives AssertionError,
executing with javaw.exe (without file.encoding-argument) is successful.
--
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
