[jira] [Reopened] (MNG-5522) properties project.parent.xxx not supported under Linux

2015-09-26 Thread Pavel (JIRA)

 [ 
https://issues.apache.org/jira/browse/MNG-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel reopened MNG-5522:


Honestly I do not completely understand your answer about root project find 
problem, but there still inconsistent behaviour on different platforms on some 
way.

Did you try run provided reproduce project?

> properties project.parent.xxx not supported under Linux
> ---
>
> Key: MNG-5522
> URL: https://issues.apache.org/jira/browse/MNG-5522
> Project: Maven
>  Issue Type: Bug
>  Components: Bootstrap & Build, POM
>Affects Versions: 3.0.5
> Environment: Few Linuxes tested, work under Windows
>Reporter: Pavel
> Attachments: maven-MNG-5522.zip
>
>
> Initially it was there: 
> https://jira.codehaus.org/browse/MRM-1772#comment-333654 . But It is maven 
> problem itself.
> It is reproducible on two our Linux machines (Fedora and Gentoo), so it may 
> be Linux relative. On all our colleagues on windows it does not reproduced.
> Some details.
> Parent pom among others have:
> {code}
>   1.5.300-SNAPSHOT
>   imus
> ...
>   
>   2.5.6
>   3.2.2.RELEASE
>   2.1.1
>   1.7.0
>   windows-1251
>   none
>   1.7
>   1.7
>   ${basedir}
>   QWERTY
>   
> {code}
> First child module:
> {code}
>   
>   
>   
>   org.apache.maven.plugins
>   maven-antrun-plugin
>   1.1
>   
>   
>   validate
>   
>   run
>   
>   
>   
>   
> [project.parent.rootProjectPath]: 
> ${project.parent.rootProjectPath}
>   
> [project.parent.getRootProjectPath()]: 
> ${project.parent.getRootProjectPath()}
>   
> [project.parent.rootProjectPath1]: 
> ${project.parent.rootProjectPath1}
>   
> [project.parent.spring3.version]: 
> ${project.parent.spring3.version}
>   
> [project.parent.properties.spring3.version]: 
> ${project.parent.properties.spring3.version}
>   
> [project.parent.properties.rootProjectPath]: 
> ${project.parent.properties.rootProjectPath}
>   
> [project.parent.properties.rootProjectPath1]: 
> ${project.parent.properties.rootProjectPath1}
>   
> [project.parent.name]: ${project.parent.name}
>   
> [project.parent.properties]: ${project.parent.properties}
>   
>   
>   
>   
>   
>   
>   
> {code}
> *In out I see what project.parent.name resolved and even 
> project.parent.properties, but not any property in collection (f.e. 
> project.parent.rootProjectPath or project.parent.properties.rootProjectPath) 
> as it should [by documentation|http://maven.apache.org/pom.html#Properties]*:
> {code}
> [INFO] --- maven-antrun-plugin:1.1:run (default) @ antinform-lib-parent ---
> [INFO] Executing tasks
>  [echo] [project.parent.rootProjectPath]: 
> ${project.parent.rootProjectPath}
>  [echo] [project.parent.getRootProjectPath()]: 
> ${project.parent.getRootProjectPath()}
>  [echo] [project.parent.rootProjectPath1]: 
> ${project.parent.rootProjectPath1}
>  [echo] [project.parent.spring3.version]: 
> ${project.parent.spring3.version}
>  [echo] [project.parent.properties.spring3.version]: 
> ${project.parent.properties.spring3.version}
>  [echo] [project.parent.properties.rootProjectPath]: 
> ${project.parent.properties.rootProjectPath}
>  [echo] [project.parent.properties.rootProjectPath1]: 
> ${project.parent.properties.rootProjectPath1}
>  [echo] [project.parent.name]: imus
>  [echo] [project.parent.properties]: {rootProjectPath1=QWERTY, 
> spring3.version=3.2.2.RELEASE, mule.version=2.1.1, aspectj.version=1.7.0, 
> maven.compiler.target=1.7, source.encoding=windows-1251, 
> maven.t

[jira] [Commented] (MNG-5522) properties project.parent.xxx not supported under Linux

2015-09-26 Thread Pavel (JIRA)

[ 
https://issues.apache.org/jira/browse/MNG-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909486#comment-14909486
 ] 

Pavel commented on MNG-5522:


How it works on windows then??

> properties project.parent.xxx not supported under Linux
> ---
>
> Key: MNG-5522
> URL: https://issues.apache.org/jira/browse/MNG-5522
> Project: Maven
>  Issue Type: Bug
>  Components: Bootstrap & Build, POM
>Affects Versions: 3.0.5
> Environment: Few Linuxes tested, work under Windows
>Reporter: Pavel
> Attachments: maven-MNG-5522.zip
>
>
> Initially it was there: 
> https://jira.codehaus.org/browse/MRM-1772#comment-333654 . But It is maven 
> problem itself.
> It is reproducible on two our Linux machines (Fedora and Gentoo), so it may 
> be Linux relative. On all our colleagues on windows it does not reproduced.
> Some details.
> Parent pom among others have:
> {code}
>   1.5.300-SNAPSHOT
>   imus
> ...
>   
>   2.5.6
>   3.2.2.RELEASE
>   2.1.1
>   1.7.0
>   windows-1251
>   none
>   1.7
>   1.7
>   ${basedir}
>   QWERTY
>   
> {code}
> First child module:
> {code}
>   
>   
>   
>   org.apache.maven.plugins
>   maven-antrun-plugin
>   1.1
>   
>   
>   validate
>   
>   run
>   
>   
>   
>   
> [project.parent.rootProjectPath]: 
> ${project.parent.rootProjectPath}
>   
> [project.parent.getRootProjectPath()]: 
> ${project.parent.getRootProjectPath()}
>   
> [project.parent.rootProjectPath1]: 
> ${project.parent.rootProjectPath1}
>   
> [project.parent.spring3.version]: 
> ${project.parent.spring3.version}
>   
> [project.parent.properties.spring3.version]: 
> ${project.parent.properties.spring3.version}
>   
> [project.parent.properties.rootProjectPath]: 
> ${project.parent.properties.rootProjectPath}
>   
> [project.parent.properties.rootProjectPath1]: 
> ${project.parent.properties.rootProjectPath1}
>   
> [project.parent.name]: ${project.parent.name}
>   
> [project.parent.properties]: ${project.parent.properties}
>   
>   
>   
>   
>   
>   
>   
> {code}
> *In out I see what project.parent.name resolved and even 
> project.parent.properties, but not any property in collection (f.e. 
> project.parent.rootProjectPath or project.parent.properties.rootProjectPath) 
> as it should [by documentation|http://maven.apache.org/pom.html#Properties]*:
> {code}
> [INFO] --- maven-antrun-plugin:1.1:run (default) @ antinform-lib-parent ---
> [INFO] Executing tasks
>  [echo] [project.parent.rootProjectPath]: 
> ${project.parent.rootProjectPath}
>  [echo] [project.parent.getRootProjectPath()]: 
> ${project.parent.getRootProjectPath()}
>  [echo] [project.parent.rootProjectPath1]: 
> ${project.parent.rootProjectPath1}
>  [echo] [project.parent.spring3.version]: 
> ${project.parent.spring3.version}
>  [echo] [project.parent.properties.spring3.version]: 
> ${project.parent.properties.spring3.version}
>  [echo] [project.parent.properties.rootProjectPath]: 
> ${project.parent.properties.rootProjectPath}
>  [echo] [project.parent.properties.rootProjectPath1]: 
> ${project.parent.properties.rootProjectPath1}
>  [echo] [project.parent.name]: imus
>  [echo] [project.parent.properties]: {rootProjectPath1=QWERTY, 
> spring3.version=3.2.2.RELEASE, mule.version=2.1.1, aspectj.version=1.7.0, 
> maven.compiler.target=1.7, source.encoding=windows-1251, 
> maven.test.include=none, maven.compiler.source=1.7, spring.version=2.5.6, 
> rootProjectPath=/home/pasha/imus/IdeaProjects/imus-

[jira] (MNG-5522) properties project.parent.xxx not supported under Linux

2014-02-08 Thread Pavel (JIRA)

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

Pavel updated MNG-5522:
---

Attachment: maven-MNG-5522.zip

You are right, sorry.
I've provide minimal project to show problem.
The idea recursively define rootProject.path to do not redefine it manually in 
dozens of submodules. That property then used to run checkstyle plugin 
automatically on each.

Attached project consist of two modules only. And works just fine on windows 
platform (mvn clean install) on version:
{noformat}
D:\imus\temp\maven-MNG-5522\submodule>mvn -version
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 
19:22:22+0400)
Maven home: D:\imus\bin\build\apache-maven-3.1.1\bin\..
Java version: 1.7.0_21, vendor: Oracle Corporation
Java home: d:\imus\bin\jdk\jre
Default locale: en_US, platform encoding: Cp1251
OS name: "windows server 2008 r2", version: "6.1", arch: "amd64", family: 
"windows"
{noformat}
but fails on my linux machine when I run _mvn clean install_ in submodule with:
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.10:check (checkstyle) on 
project test-proj-submodule: Failed during checkstyle execution: Unable to find 
configuration file at location 
${project.parent.rootProject.path}/../checkstyle.xml: Could not find resource 
'${project.parent.rootProject.path}/../checkstyle.xml'. -> [Help 1]
{noformat}

Version of maven:
{noformat}
$ mvn -version
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true 
-Dsun.java2d.pmoffscreen=false -XX:+UseCompressedOops
Apache Maven 3.1.1 (NON-CANONICAL_2013-11-08_14-32_mockbuild; 2013-11-08 
18:32:41+0400)
Maven home: /usr/share/maven
Java version: 1.7.0_45, vendor: Oracle Corporation
Java home: /usr/java/jdk1.7.0_45/jre
Default locale: ru_RU, platform encoding: UTF-8
OS name: "linux", version: "3.12.9-301.fc20.x86_64", arch: "amd64", family: 
"unix"
{noformat}

> properties project.parent.xxx not supported under Linux
> ---
>
> Key: MNG-5522
> URL: https://jira.codehaus.org/browse/MNG-5522
> Project: Maven 2 & 3
>  Issue Type: Bug
>  Components: Bootstrap & Build, POM
>Affects Versions: 3.0.5
> Environment: Few Linuxes tested, work under Windows
>Reporter: Pavel
> Attachments: maven-MNG-5522.zip
>
>
> Initially it was there: 
> https://jira.codehaus.org/browse/MRM-1772#comment-333654 . But It is maven 
> problem itself.
> It is reproducible on two our Linux machines (Fedora and Gentoo), so it may 
> be Linux relative. On all our colleagues on windows it does not reproduced.
> Some details.
> Parent pom among others have:
> {code}
>   1.5.300-SNAPSHOT
>   imus
> ...
>   
>   2.5.6
>   3.2.2.RELEASE
>   2.1.1
>   1.7.0
>   windows-1251
>   none
>   1.7
>   1.7
>   ${basedir}
>   QWERTY
>   
> {code}
> First child module:
> {code}
>   
>   
>   
>   org.apache.maven.plugins
>   maven-antrun-plugin
>   1.1
>   
>   
>   validate
>   
>   run
>   
>   
>   
>   
> [project.parent.rootProjectPath]: 
> ${project.parent.rootProjectPath}
>   
> [project.parent.getRootProjectPath()]: 
> ${project.parent.getRootProjectPath()}
>   
> [project.parent.rootProjectPath1]: 
> ${project.parent.rootProjectPath1}
>   
> [project.parent.spring3.version]: 
> ${project.parent.spring3.version}
>   
> [project.parent.properties.spring3.version]: 
> ${project.parent.properties.spring3.version}
>   
> [project.parent.properties.rootProjectPath]: 
> ${project.parent.properties.rootProjectPath}
>   
> [project.parent.properties.rootProjectPath1]: 
> ${project.parent.properties.rootProjectPath1}
>   
> [project.parent.name]: ${project.parent.name}
>   
> [project.parent.

[jira] (MEAR-177) Jars from previous execution are copied into ear

2013-11-20 Thread Pavel (JIRA)

[ 
https://jira.codehaus.org/browse/MEAR-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=336049#comment-336049
 ] 

Pavel commented on MEAR-177:


Thanks, using custom working directories works.
But with custom directories application.xml generation does not work, because 
it generates into default output directory and can't find it during package. 
Using custom application.xml solves this.

> Jars from previous execution are copied into ear
> 
>
> Key: MEAR-177
> URL: https://jira.codehaus.org/browse/MEAR-177
> Project: Maven Ear Plugin
>  Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Pavel
> Attachments: mear-177.zip
>
>
> If several executions for ear plugn configured and each contain own jarModule 
> than every next execution will contain jar from previous.
> For example following project (see attachment):
> {code}
> root/
>  - ear
>  - jar1
>  - jar2
> {code}
> Ear contain two executions
> {code}
> 
>   jar1
>   package
>   
>   jar1
>   
>   
>   example
>   jar1
>   
>   
>   
>   ear
> 
> 
>   jar2
>   package
>   
>   jar2
>   
>   
>   example
>   jar2
>   
>   
>   
>   ear
> 
> {code}
> But resulting ear-0.0.1-SNAPSHOT-jar2.ear contain both jar1.jar and jar2.jar

--
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] (MEAR-177) Jars from previous execution are copied into ear

2013-11-20 Thread Pavel (JIRA)
Pavel created MEAR-177:
--

 Summary: Jars from previous execution are copied into ear
 Key: MEAR-177
 URL: https://jira.codehaus.org/browse/MEAR-177
 Project: Maven Ear Plugin
  Issue Type: Bug
Affects Versions: 2.8
Reporter: Pavel
 Attachments: mear-177.zip

If several executions for ear plugn configured and each contain own jarModule 
than every next execution will contain jar from previous.
For example following project (see attachment):
{code}
root/
 - ear
 - jar1
 - jar2
{code}
Ear contain two executions
{code}

jar1
package

jar1


example
jar1



ear


jar2
package

jar2


example
jar2



ear

{code}

But resulting ear-0.0.1-SNAPSHOT-jar2.ear contain both jar1.jar and jar2.jar


--
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] (MEAR-177) Jars from previous execution are copied into ear

2013-11-20 Thread Pavel (JIRA)

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

Pavel updated MEAR-177:
---

Attachment: mear-177.zip

> Jars from previous execution are copied into ear
> 
>
> Key: MEAR-177
> URL: https://jira.codehaus.org/browse/MEAR-177
> Project: Maven Ear Plugin
>  Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Pavel
> Attachments: mear-177.zip
>
>
> If several executions for ear plugn configured and each contain own jarModule 
> than every next execution will contain jar from previous.
> For example following project (see attachment):
> {code}
> root/
>  - ear
>  - jar1
>  - jar2
> {code}
> Ear contain two executions
> {code}
> 
>   jar1
>   package
>   
>   jar1
>   
>   
>   example
>   jar1
>   
>   
>   
>   ear
> 
> 
>   jar2
>   package
>   
>   jar2
>   
>   
>   example
>   jar2
>   
>   
>   
>   ear
> 
> {code}
> But resulting ear-0.0.1-SNAPSHOT-jar2.ear contain both jar1.jar and jar2.jar

--
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-5522) properties project.parent.xxx not supported under Linux

2013-10-06 Thread Pavel (JIRA)
Pavel created MNG-5522:
--

 Summary: properties project.parent.xxx not supported under Linux
 Key: MNG-5522
 URL: https://jira.codehaus.org/browse/MNG-5522
 Project: Maven 2 & 3
  Issue Type: Bug
  Components: Bootstrap & Build, POM
Affects Versions: 3.0.5
 Environment: Few Linuxes tested, work under Windows
Reporter: Pavel


Initially it was there: 
https://jira.codehaus.org/browse/MRM-1772#comment-333654 . But It is maven 
problem itself.

It is reproducible on two our Linux machines (Fedora and Gentoo), so it may be 
Linux relative. On all our colleagues on windows it does not reproduced.

Some details.

Parent pom among others have:
{code}
1.5.300-SNAPSHOT
imus
...

2.5.6
3.2.2.RELEASE
2.1.1
1.7.0
windows-1251
none
1.7
1.7
${basedir}
QWERTY

{code}

First child module:
{code}



org.apache.maven.plugins
maven-antrun-plugin
1.1


validate

run




[project.parent.rootProjectPath]: ${project.parent.rootProjectPath}

[project.parent.getRootProjectPath()]: 
${project.parent.getRootProjectPath()}

[project.parent.rootProjectPath1]: 
${project.parent.rootProjectPath1}

[project.parent.spring3.version]: ${project.parent.spring3.version}

[project.parent.properties.spring3.version]: 
${project.parent.properties.spring3.version}

[project.parent.properties.rootProjectPath]: 
${project.parent.properties.rootProjectPath}

[project.parent.properties.rootProjectPath1]: 
${project.parent.properties.rootProjectPath1}

[project.parent.name]: ${project.parent.name}

[project.parent.properties]: ${project.parent.properties}







{code}

*In out I see what project.parent.name resolved and even 
project.parent.properties, but not any property in collection (f.e. 
project.parent.rootProjectPath or project.parent.properties.rootProjectPath) as 
it should [by documentation|http://maven.apache.org/pom.html#Properties]*:
{code}
[INFO] --- maven-antrun-plugin:1.1:run (default) @ antinform-lib-parent ---
[INFO] Executing tasks
 [echo] [project.parent.rootProjectPath]: ${project.parent.rootProjectPath}
 [echo] [project.parent.getRootProjectPath()]: 
${project.parent.getRootProjectPath()}
 [echo] [project.parent.rootProjectPath1]: 
${project.parent.rootProjectPath1}
 [echo] [project.parent.spring3.version]: ${project.parent.spring3.version}
 [echo] [project.parent.properties.spring3.version]: 
${project.parent.properties.spring3.version}
 [echo] [project.parent.properties.rootProjectPath]: 
${project.parent.properties.rootProjectPath}
 [echo] [project.parent.properties.rootProjectPath1]: 
${project.parent.properties.rootProjectPath1}
 [echo] [project.parent.name]: imus
 [echo] [project.parent.properties]: {rootProjectPath1=QWERTY, 
spring3.version=3.2.2.RELEASE, mule.version=2.1.1, aspectj.version=1.7.0, 
maven.compiler.target=1.7, source.encoding=windows-1251, 
maven.test.include=none, maven.compiler.source=1.7, spring.version=2.5.6, 
rootProjectPath=/home/pasha/imus/IdeaProjects/imus-1.5}
{code}

Version is 3.0.5:
{code}
$ mvn --version
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
Apache Maven 3.0.5 (rNON-CANONICAL_2013-03-12_12-47_mockbuild; 2013-03-12 
16:47:10+0400)
Maven home: /usr/share/maven
Java version: 1.7.0_25, vendor: Oracle Corporation
Java home: /usr/java/jdk1.7.0_25/jre
Default locale: ru_RU, platform encoding: UTF-8
OS name: "linux", version: