[jira] (WAGON-411) Enhance merge-maven-repos to work with SNAPSHOT builds
[
https://jira.codehaus.org/browse/WAGON-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341789#comment-341789
]
Karl Heinz Marbaise commented on WAGON-411:
---
Got the information someone has created a [patch for
this|https://github.com/wolfs/wagon-maven-plugin/commit/3393e8fc247d7b3f99aa569032456b9fbe713db3].
should be checked and be integrated.
> Enhance merge-maven-repos to work with SNAPSHOT builds
> --
>
> Key: WAGON-411
> URL: https://jira.codehaus.org/browse/WAGON-411
> Project: Maven Wagon
> Issue Type: Improvement
>Affects Versions: 1.0-beta-3
> Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 02:44:56-0600)
> Maven home: D:\maven\apache-maven-3.0.4\bin\..
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: D:\j2sdk1.6.0_24\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
>Reporter: Jim McCaskey
>
> According to Dan Tran the merge-maven-repos goal does not work with
> SNAPSHOTS. I could not find an issue open for that so here we go.
> Here is a link to my original e-mail with Dan's response.
> http://mail-archives.apache.org/mod_mbox/maven-users/201303.mbox/%3CCAPCjjnGNu2%3DV0ZZ4_tT8%2B-4O0Uq%3DmnD8spE5LSLLEdYD7agU_A%40mail.gmail.com%3E
> FWIW, it appears to me that there is a problem with the maven-metadata.xml
> files that get merged. Here is an example of a badly merged file.
> {code}
>
>
> myGroup
> MyArtifact
> 10.2.6-SNAPSHOT
>
>
> 20130313.165705
> 1
>
> 20130313165705
>
>
> MyClassifier
> zip
> 10.2.6-20130311.175410-1
> 20130311175410
>
>
> pom
> 10.2.6-20130311.175410-1
> 20130311175410
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (WAGON-411) Enhance merge-maven-repos to work with SNAPSHOT builds
[
https://jira.codehaus.org/browse/WAGON-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise moved MOJO-1913 to WAGON-411:
-
Complexity: (was: Intermediate)
Component/s: (was: wagon)
Affects Version/s: (was: wagon-maven-plugin-1.0-beta-3)
1.0-beta-3
Issue Type: Improvement (was: New Feature)
Key: WAGON-411 (was: MOJO-1913)
Project: Maven Wagon (was: Mojo)
> Enhance merge-maven-repos to work with SNAPSHOT builds
> --
>
> Key: WAGON-411
> URL: https://jira.codehaus.org/browse/WAGON-411
> Project: Maven Wagon
> Issue Type: Improvement
>Affects Versions: 1.0-beta-3
> Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 02:44:56-0600)
> Maven home: D:\maven\apache-maven-3.0.4\bin\..
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: D:\j2sdk1.6.0_24\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
>Reporter: Jim McCaskey
>
> According to Dan Tran the merge-maven-repos goal does not work with
> SNAPSHOTS. I could not find an issue open for that so here we go.
> Here is a link to my original e-mail with Dan's response.
> http://mail-archives.apache.org/mod_mbox/maven-users/201303.mbox/%3CCAPCjjnGNu2%3DV0ZZ4_tT8%2B-4O0Uq%3DmnD8spE5LSLLEdYD7agU_A%40mail.gmail.com%3E
> FWIW, it appears to me that there is a problem with the maven-metadata.xml
> files that get merged. Here is an example of a badly merged file.
> {code}
>
>
> myGroup
> MyArtifact
> 10.2.6-SNAPSHOT
>
>
> 20130313.165705
> 1
>
> 20130313165705
>
>
> MyClassifier
> zip
> 10.2.6-20130311.175410-1
> 20130311175410
>
>
> pom
> 10.2.6-20130311.175410-1
> 20130311175410
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341779#comment-341779 ] Stephen Connolly commented on MNG-5207: --- When adding the delegate vertex to the app node, as the delegate is 1-SNAPSHOT which is outside the reactor there is no edge added to the app node... we should be considering the transitive dependencies of app not just the immediate dependencies in constructing the graph. > [Regression] Maven 3 fails to calculate proper build order with dependencies > with classifiers > - > > Key: MNG-5207 > URL: https://jira.codehaus.org/browse/MNG-5207 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Reactor and workspace >Affects Versions: 3.0.3 >Reporter: Jörg Schaible >Assignee: Jason van Zyl >Priority: Critical > Fix For: Issues to be reviewed for 4.x > > Attachments: mng5207-it.tgz, mng-5207-minimal.tar.gz, MNG-5207.tgz > > > Maven 3.0.3 and 3.0.4 RC1 fails to build the projects of the reactor in > proper order, if a transitive dependency (that is part of the reactor build) > is overruled in the dependencyManagement section with the current SNAPSHOT > version. Build order is perfectly calculated with Maven 2.2.1. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341778#comment-341778 ] Stephen Connolly commented on MNG-5207: --- So what I'm seeing when I step through with the debugger is that the app:2-SNAPSHOT vertex has no child nodes, hence it is first as it is the first and it has no dependencies... not sure why it doesn't have any children > [Regression] Maven 3 fails to calculate proper build order with dependencies > with classifiers > - > > Key: MNG-5207 > URL: https://jira.codehaus.org/browse/MNG-5207 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Reactor and workspace >Affects Versions: 3.0.3 >Reporter: Jörg Schaible >Assignee: Jason van Zyl >Priority: Critical > Fix For: Issues to be reviewed for 4.x > > Attachments: mng5207-it.tgz, mng-5207-minimal.tar.gz, MNG-5207.tgz > > > Maven 3.0.3 and 3.0.4 RC1 fails to build the projects of the reactor in > proper order, if a transitive dependency (that is part of the reactor build) > is overruled in the dependencyManagement section with the current SNAPSHOT > version. Build order is perfectly calculated with Maven 2.2.1. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5207: -- Attachment: mng-5207-minimal.tar.gz Minimal test case constructed from mng5207-it with a lot of the properties based cruft removed and the poms stripped back to the minimum. Confirmed that from a clean repo, passes with maven 2.2.1 and fails for maven 3.2.1 > [Regression] Maven 3 fails to calculate proper build order with dependencies > with classifiers > - > > Key: MNG-5207 > URL: https://jira.codehaus.org/browse/MNG-5207 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Reactor and workspace >Affects Versions: 3.0.3 >Reporter: Jörg Schaible >Assignee: Jason van Zyl >Priority: Critical > Fix For: Issues to be reviewed for 4.x > > Attachments: mng5207-it.tgz, mng-5207-minimal.tar.gz, MNG-5207.tgz > > > Maven 3.0.3 and 3.0.4 RC1 fails to build the projects of the reactor in > proper order, if a transitive dependency (that is part of the reactor build) > is overruled in the dependencyManagement section with the current SNAPSHOT > version. Build order is perfectly calculated with Maven 2.2.1. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1058) TestSetFailedException trying to use maven-surefire-plugin + regular expressions for TestNG groups
[
https://jira.codehaus.org/browse/SUREFIRE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341773#comment-341773
]
Tracey Ruark commented on SUREFIRE-1058:
We've been testing this for a few days now and it looks like we're up and
running and good-to-go. Thanks so much for working on this issue Andreas!
> TestSetFailedException trying to use maven-surefire-plugin + regular
> expressions for TestNG groups
> --
>
> Key: SUREFIRE-1058
> URL: https://jira.codehaus.org/browse/SUREFIRE-1058
> Project: Maven Surefire
> Issue Type: Improvement
> Components: TestNG support
>Affects Versions: 2.16
>Reporter: Tracey Ruark
>Assignee: Andreas Gudian
> Fix For: 2.17
>
> Attachments: Surefire1058BugExample_new.zip,
> Surefire1058BugExample.zip
>
>
> I have a Maven project with parent -> child poms. Each child project has
> TestNG tests. What I'd like to be able to do is use regular expressions on
> the TestNG group and execute tests across projects which match the given
> regex.
> Running TestNG tests using a non-regular expression group across projects
> works just fine. For example this works:
> {noformat}mvn test -DargLine="-Denvironment=test"
> -Dgroups="foo.bar.something"{noformat}
> This runs the correct test methods which have that exact tag across all my
> child projects.
> However if I do something like this:
> {noformat}mvn test -DargLine="-Denvironment=test"
> -Dgroups="foo.bar.*"{noformat}
> I get this exception:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test)
> on project test-automation-ui: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test failed: There was an
> error in the forked process
> [ERROR] org.apache.maven.surefire.testset.TestSetFailedException: null;
> nested exception is java.lang.reflect.InvocationTargetException: null
> [ERROR] java.lang.reflect.InvocationTargetException
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:601)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGExecutor.getGroupMatchingSelector(TestNGExecutor.java:172)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:66)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> [ERROR] Caused by: org.apache.maven.surefire.group.parse.TokenMgrError:
> Lexical error at line 1, column 13. Encountered: after : ""
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParserTokenManager.getNextToken(GroupMatcherParserTokenManager.java:468)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_scan_token(GroupMatcherParser.java:527)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_7(GroupMatcherParser.java:274)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_3(GroupMatcherParser.java:287)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_3(GroupMatcherParser.java:279)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_1(GroupMatcherParser.java:320)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_1(GroupMatcherParser.java:335)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_2_1(GroupMatcherParser.java:179)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.expr(GroupMatcherParser.java:63)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.parse(GroupMatcherParser.java:56)
> [ERROR] at
> org.apache.maven.surefire.testng.utils.GroupMatcherMethodSelector.setGroups(GroupMatcherMethodSelector.java:83)
> [ERROR] ... 12 more
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using t
[jira] (SUREFIRE-1064) Provide a way to run only failed tests
Pascal Schumacher created SUREFIRE-1064: --- Summary: Provide a way to run only failed tests Key: SUREFIRE-1064 URL: https://jira.codehaus.org/browse/SUREFIRE-1064 Project: Maven Surefire Issue Type: New Feature Components: Maven Failsafe Plugin Reporter: Pascal Schumacher We use maven for end-to-end tests of a highly asynchronous system (which includes third-party software we can not modify). Sometimes only 1-3 out of hundreds of test fail. It would be nice if there were a way to rerun these failed test only. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1058) TestSetFailedException trying to use maven-surefire-plugin + regular expressions for TestNG groups
[
https://jira.codehaus.org/browse/SUREFIRE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341757#comment-341757
]
Alex Gray commented on SUREFIRE-1058:
-
Forget my previous comment. Everything is fine. Thanks for fixing this!
> TestSetFailedException trying to use maven-surefire-plugin + regular
> expressions for TestNG groups
> --
>
> Key: SUREFIRE-1058
> URL: https://jira.codehaus.org/browse/SUREFIRE-1058
> Project: Maven Surefire
> Issue Type: Improvement
> Components: TestNG support
>Affects Versions: 2.16
>Reporter: Tracey Ruark
>Assignee: Andreas Gudian
> Fix For: 2.17
>
> Attachments: Surefire1058BugExample_new.zip,
> Surefire1058BugExample.zip
>
>
> I have a Maven project with parent -> child poms. Each child project has
> TestNG tests. What I'd like to be able to do is use regular expressions on
> the TestNG group and execute tests across projects which match the given
> regex.
> Running TestNG tests using a non-regular expression group across projects
> works just fine. For example this works:
> {noformat}mvn test -DargLine="-Denvironment=test"
> -Dgroups="foo.bar.something"{noformat}
> This runs the correct test methods which have that exact tag across all my
> child projects.
> However if I do something like this:
> {noformat}mvn test -DargLine="-Denvironment=test"
> -Dgroups="foo.bar.*"{noformat}
> I get this exception:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test)
> on project test-automation-ui: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test failed: There was an
> error in the forked process
> [ERROR] org.apache.maven.surefire.testset.TestSetFailedException: null;
> nested exception is java.lang.reflect.InvocationTargetException: null
> [ERROR] java.lang.reflect.InvocationTargetException
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:601)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGExecutor.getGroupMatchingSelector(TestNGExecutor.java:172)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:66)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> [ERROR] Caused by: org.apache.maven.surefire.group.parse.TokenMgrError:
> Lexical error at line 1, column 13. Encountered: after : ""
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParserTokenManager.getNextToken(GroupMatcherParserTokenManager.java:468)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_scan_token(GroupMatcherParser.java:527)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_7(GroupMatcherParser.java:274)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_3(GroupMatcherParser.java:287)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_3(GroupMatcherParser.java:279)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_1(GroupMatcherParser.java:320)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_1(GroupMatcherParser.java:335)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_2_1(GroupMatcherParser.java:179)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.expr(GroupMatcherParser.java:63)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.parse(GroupMatcherParser.java:56)
> [ERROR] at
> org.apache.maven.surefire.testng.utils.GroupMatcherMethodSelector.setGroups(GroupMatcherMethodSelector.java:83)
> [ERROR] ... 12 more
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> {noformat}
> If I use the b
[jira] (MNG-5522) properties project.parent.xxx not supported under Linux
[
https://jira.codehaus.org/browse/MNG-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341751#comment-341751
]
Henrik Brautaset Aronsen edited comment on MNG-5522 at 2/20/14 7:26 AM:
I'm seeing this issue as well. Annoying.
was (Author: henrik242):
I'm seeing this issue as well.
> 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.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.encodi
[jira] (MNG-5522) properties project.parent.xxx not supported under Linux
[
https://jira.codehaus.org/browse/MNG-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341751#comment-341751
]
Henrik Brautaset Aronsen commented on MNG-5522:
---
I'm seeing this issue as well.
> 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.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
[jira] (MCHECKSTYLE-211) allow inline configuration for checkstyle plugin
[
https://jira.codehaus.org/browse/MCHECKSTYLE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341742#comment-341742
]
Mark Struberg commented on MCHECKSTYLE-211:
---
great idea. That way one can enable the checkstyle rules directly in the master
pom.
Will review and apply.
> allow inline configuration for checkstyle plugin
>
>
> Key: MCHECKSTYLE-211
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-211
> Project: Maven Checkstyle Plugin
> Issue Type: New Feature
>Reporter: Romain Manni-Bucau
> Attachments: CHECKSTYLE-inlineCDATA.patch,
> CHECKSTYLE-inlineCDATA.patch, CHECKSTYLE-inline.patch
>
>
> Make possible to not rely on an external module or file:
> {code}
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
> @pom.version@
>
>
> check
> process-resources
>
> check
>
>
>
>
>
> Checker
>
>
> TreeWalker
>
>
> EmptyBlock
>
>
>
>
>
>
>
> {code}
> or (better) this one:
> {code}
>
> true
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
