[jira] Updated: (MNG-4472) [regression] Circular self-referential POM causes network access
[
http://jira.codehaus.org/browse/MNG-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-4472:
---
Priority: Minor (was: Major)
Summary: [regression] Circular self-referential POM causes network access
(was: [regression] Circular POM causes network access)
> [regression] Circular self-referential POM causes network access
>
>
> Key: MNG-4472
> URL: http://jira.codehaus.org/browse/MNG-4472
> Project: Maven 2
> Issue Type: Bug
> Components: Reactor and workspace
>Affects Versions: 3.0-alpha-4
>Reporter: Paul Benedict
>Priority: Minor
> Attachments: MNG-4472.zip
>
>
> If I were to specify a project with itself as a parent, Maven 2.2.1 gives
> this response:
> {code}
> [INFO] Scanning for projects...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] Error building POM (may not be this project's POM).
> Project ID: org.apache.maven.its.mng:test
> Reason: Parent element is a duplicate of the current project for project
> org.apache.maven.its.mng:test
> [INFO]
>
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Parent element is a
> duplicate of the current project for project org.apache.maven.its.mng:test
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.ProjectBuildingException: Parent element
> is a duplicate of the current project for project
> org.apache.maven.its.mng:test
> {code}
> Maven 3 doesn't detect this circularity *immediately*; it tries to download
> the parent by going through my remote repositories. The end result is still a
> failure since it can't find itself, but it's a regression since the network
> is accessed for this use case.
> {code}
> [INFO] Scanning for projects...
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/its/mng/test/0.1/test-0.1.pom
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR] The project org.apache.maven.its.mng:test:0.1
> (D:\patches\MNG-4472\pom.xml) has 2 errors
> [ERROR] The parent element cannot have the same ID as the project.
> [ERROR] Non-resolvable parent POM org.apache.maven.its.mng:test:0.1 for
> org.apache.maven.its.mng:test:0.1: Failed to resolve POM for
> org.apache.maven.its.mng:test:0.1 due to Missing:
> --
> 1) org.apache.maven.its.mng:test:pom:0.1
> --
> 1 required artifact is missing.
> for artifact:
> org.apache.maven.its.mng:test:pom:0.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2, releases=true, snapshots=false)
> -> [Help 2]
> [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]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-4472) [regression] Circular POM causes network access
[
http://jira.codehaus.org/browse/MNG-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-4472:
---
Summary: [regression] Circular POM causes network access (was:
[regression] Circular POM not detected)
> [regression] Circular POM causes network access
> ---
>
> Key: MNG-4472
> URL: http://jira.codehaus.org/browse/MNG-4472
> Project: Maven 2
> Issue Type: Bug
> Components: Reactor and workspace
>Affects Versions: 3.0-alpha-4
>Reporter: Paul Benedict
> Attachments: MNG-4472.zip
>
>
> If I were to specify a project with itself as a parent, Maven 2.2.1 gives
> this response:
> {code}
> [INFO] Scanning for projects...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] Error building POM (may not be this project's POM).
> Project ID: org.apache.maven.its.mng:test
> Reason: Parent element is a duplicate of the current project for project
> org.apache.maven.its.mng:test
> [INFO]
>
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Parent element is a
> duplicate of the current project for project org.apache.maven.its.mng:test
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.ProjectBuildingException: Parent element
> is a duplicate of the current project for project
> org.apache.maven.its.mng:test
> {code}
> Maven 3 doesn't detect this circularity *immediately*; it tries to download
> the parent by going through my remote repositories. The end result is still a
> failure since it can't find itself, but it's a regression since the network
> is accessed for this use case.
> {code}
> [INFO] Scanning for projects...
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/its/mng/test/0.1/test-0.1.pom
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR] The project org.apache.maven.its.mng:test:0.1
> (D:\patches\MNG-4472\pom.xml) has 2 errors
> [ERROR] The parent element cannot have the same ID as the project.
> [ERROR] Non-resolvable parent POM org.apache.maven.its.mng:test:0.1 for
> org.apache.maven.its.mng:test:0.1: Failed to resolve POM for
> org.apache.maven.its.mng:test:0.1 due to Missing:
> --
> 1) org.apache.maven.its.mng:test:pom:0.1
> --
> 1 required artifact is missing.
> for artifact:
> org.apache.maven.its.mng:test:pom:0.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2, releases=true, snapshots=false)
> -> [Help 2]
> [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]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-4472) [regression] Circular POM not detected
[
http://jira.codehaus.org/browse/MNG-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-4472:
---
Attachment: MNG-4472.zip
> [regression] Circular POM not detected
> --
>
> Key: MNG-4472
> URL: http://jira.codehaus.org/browse/MNG-4472
> Project: Maven 2
> Issue Type: Bug
> Components: Reactor and workspace
>Affects Versions: 3.0-alpha-4
>Reporter: Paul Benedict
> Attachments: MNG-4472.zip
>
>
> If I were to specify a project with itself as a parent, Maven 2.2.1 gives
> this response:
> {code}
> [INFO] Scanning for projects...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] Error building POM (may not be this project's POM).
> Project ID: org.apache.maven.its.mng:test
> Reason: Parent element is a duplicate of the current project for project
> org.apache.maven.its.mng:test
> [INFO]
>
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Parent element is a
> duplicate of the current project for project org.apache.maven.its.mng:test
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.ProjectBuildingException: Parent element
> is a duplicate of the current project for project
> org.apache.maven.its.mng:test
> {code}
> Maven 3 doesn't detect this circularity *immediately*; it tries to download
> the parent by going through my remote repositories. The end result is still a
> failure since it can't find itself, but it's a regression since the network
> is accessed for this use case.
> {code}
> [INFO] Scanning for projects...
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/its/mng/test/0.1/test-0.1.pom
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR] The project org.apache.maven.its.mng:test:0.1
> (D:\patches\MNG-4472\pom.xml) has 2 errors
> [ERROR] The parent element cannot have the same ID as the project.
> [ERROR] Non-resolvable parent POM org.apache.maven.its.mng:test:0.1 for
> org.apache.maven.its.mng:test:0.1: Failed to resolve POM for
> org.apache.maven.its.mng:test:0.1 due to Missing:
> --
> 1) org.apache.maven.its.mng:test:pom:0.1
> --
> 1 required artifact is missing.
> for artifact:
> org.apache.maven.its.mng:test:pom:0.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2, releases=true, snapshots=false)
> -> [Help 2]
> [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]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-4472) [regression] Circular POM not detected
[
http://jira.codehaus.org/browse/MNG-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-4472:
---
Description:
If I were to specify a project with itself as a parent, Maven 2.2.1 gives this
response:
{code}
[INFO] Scanning for projects...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: org.apache.maven.its.mng:test
Reason: Parent element is a duplicate of the current project for project
org.apache.maven.its.mng:test
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Parent element is a duplicate
of the current project for project org.apache.maven.its.mng:test
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Parent element is
a duplicate of the current project for project org.apache.maven.its.mng:test
{code}
Maven 3 doesn't detect this circularity *immediately*; it tries to download the
parent by going through my remote repositories. The end result is still a
failure since it can't find itself, but it's a regression since the network is
accessed for this use case.
{code}
[INFO] Scanning for projects...
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/its/mng/test/0.1/test-0.1.pom
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR] The project org.apache.maven.its.mng:test:0.1
(D:\patches\MNG-4472\pom.xml) has 2 errors
[ERROR] The parent element cannot have the same ID as the project.
[ERROR] Non-resolvable parent POM org.apache.maven.its.mng:test:0.1 for
org.apache.maven.its.mng:test:0.1: Failed to resolve POM for
org.apache.maven.its.mng:test:0.1 due to Missing:
--
1) org.apache.maven.its.mng:test:pom:0.1
--
1 required artifact is missing.
for artifact:
org.apache.maven.its.mng:test:pom:0.1
from the specified remote repositories:
central (http://repo1.maven.org/maven2, releases=true, snapshots=false)
-> [Help 2]
[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]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
{code}
was:
If I were to specify a project with itself as a parent, Maven 2.2.1 gives this
response:
{code}
[INFO] Scanning for projects...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: org.apache.maven.its.mng:test
Reason: Parent element is a duplicate of the current project for project
org.apache.maven.its.mng:test
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Parent element is a duplicate
of the current project for project org.apache.maven.its.mng:test
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun
[jira] Created: (MNG-4472) [regression] Circular POM not detected
[regression] Circular POM not detected
--
Key: MNG-4472
URL: http://jira.codehaus.org/browse/MNG-4472
Project: Maven 2
Issue Type: Bug
Components: Reactor and workspace
Affects Versions: 3.0-alpha-4
Reporter: Paul Benedict
If I were to specify a project with itself as a parent, Maven 2.2.1 gives this
response:
{code}
[INFO] Scanning for projects...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: org.apache.maven.its.mng:test
Reason: Parent element is a duplicate of the current project for project
org.apache.maven.its.mng:test
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Parent element is a duplicate
of the current project for project org.apache.maven.its.mng:test
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Parent element is
a duplicate of the current project for project org.apache.maven.its.mng:test
{code}
Maven 3 doesn't detect this circularity; it tries to download the parent by
going through my remote repositories. The end result is still a failure since
it can't find itself, but it's a regression since the error condition is no
longer detected.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-4471) Profile activation fails if contains variables
[
http://jira.codehaus.org/browse/MNG-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199813#action_199813
]
j4zzcat edited comment on MNG-4471 at 11/27/09 6:32 PM:
I can't seem to attach the file, so here's testcase2.xml:
{noformat}
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/maven-v4_0_0.xsd";>
4.0.0
testcase2
testcase2
1.0
.
testcase2
${test.prop}/testcase2.xml
absolute path
./testcase2.xml
{noformat}
was (Author: j4zzcat):
I can't seem to attach the file, so here's testcase2.xml:
{noformat}
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/maven-v4_0_0.xsd";>
4.0.0
testcase2
testcase2
1.0
.
testcase2
${test.prop}/testcase2.xml
absolute path
./testcase2.xml
{noformat}
> Profile activation fails if contains variables
> --
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
>Reporter: j4zzcat
>Assignee: Benjamin Bentmann
> Attachments: pom.xml, testcase.xml, testcase2.xml, testcase2.xml
>
>
> See the attached testcase.
> The profile is not activated when has variables in it:
> ${env.M2_HOME}/bin/mvn
> But when the path is absolute, it works:
> /my/maven/home/bin/mvn
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-4471) Profile activation fails if contains variables
[
http://jira.codehaus.org/browse/MNG-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199813#action_199813
]
J C edited comment on MNG-4471 at 11/27/09 6:12 PM:
I can't seem to attach the file, so here's testcase2.xml:
{noformat}
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/maven-v4_0_0.xsd";>
4.0.0
testcase2
testcase2
1.0
.
testcase2
${test.prop}/testcase2.xml
absolute path
./testcase2.xml
{noformat}
was (Author: j4zzcat):
I can't seem to attach the file, so here's testcase2.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/maven-v4_0_0.xsd";>
4.0.0
testcase2
testcase2
1.0
.
testcase2
${test.prop}/testcase2.xml
absolute path
./testcase2.xml
> Profile activation fails if contains variables
> --
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
>Reporter: J C
>Assignee: Benjamin Bentmann
> Attachments: pom.xml, testcase.xml, testcase2.xml, testcase2.xml
>
>
> See the attached testcase.
> The profile is not activated when has variables in it:
> ${env.M2_HOME}/bin/mvn
> But when the path is absolute, it works:
> /my/maven/home/bin/mvn
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4471) Profile activation fails if contains variables
[
http://jira.codehaus.org/browse/MNG-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199813#action_199813
]
J C commented on MNG-4471:
--
I can't seem to attach the file, so here's testcase2.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/maven-v4_0_0.xsd";>
4.0.0
testcase2
testcase2
1.0
.
testcase2
${test.prop}/testcase2.xml
absolute path
./testcase2.xml
> Profile activation fails if contains variables
> --
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
>Reporter: J C
>Assignee: Benjamin Bentmann
> Attachments: pom.xml, testcase.xml, testcase2.xml, testcase2.xml
>
>
> See the attached testcase.
> The profile is not activated when has variables in it:
> ${env.M2_HOME}/bin/mvn
> But when the path is absolute, it works:
> /my/maven/home/bin/mvn
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-4471) Profile activation fails if contains variables
[
http://jira.codehaus.org/browse/MNG-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
J C updated MNG-4471:
-
Attachment: testcase2.xml
> Profile activation fails if contains variables
> --
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
>Reporter: J C
>Assignee: Benjamin Bentmann
> Attachments: pom.xml, testcase.xml, testcase2.xml, testcase2.xml
>
>
> See the attached testcase.
> The profile is not activated when has variables in it:
> ${env.M2_HOME}/bin/mvn
> But when the path is absolute, it works:
> /my/maven/home/bin/mvn
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-4471) Profile activation fails if contains variables
[
http://jira.codehaus.org/browse/MNG-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
J C updated MNG-4471:
-
Attachment: testcase2.xml
To reproduce:
1. Run "mvn -f testcase2.xml help:active-profiles"
2. Expected result: both profiles should have been activated;
Observed result: only one profile is activated,
the "testcase2" profile is not activated.
> Profile activation fails if contains variables
> --
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
>Reporter: J C
>Assignee: Benjamin Bentmann
> Attachments: pom.xml, testcase.xml, testcase2.xml
>
>
> See the attached testcase.
> The profile is not activated when has variables in it:
> ${env.M2_HOME}/bin/mvn
> But when the path is absolute, it works:
> /my/maven/home/bin/mvn
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MNG-4471) Profile activation fails if contains variables
[
http://jira.codehaus.org/browse/MNG-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
J C reopened MNG-4471:
--
I'm attaching a better testcase that shows the issue.
> Profile activation fails if contains variables
> --
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
>Reporter: J C
>Assignee: Benjamin Bentmann
> Attachments: pom.xml, testcase.xml
>
>
> See the attached testcase.
> The profile is not activated when has variables in it:
> ${env.M2_HOME}/bin/mvn
> But when the path is absolute, it works:
> /my/maven/home/bin/mvn
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SCM-455) scm:changelog command does not pick up svn changes when author has spaces
[ http://jira.codehaus.org/browse/SCM-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-455. Resolution: Fixed fix in [rev 885036|http://svn.apache.org/viewvc?view=revision&revision=885036] Thanks ! > scm:changelog command does not pick up svn changes when author has spaces > - > > Key: SCM-455 > URL: http://jira.codehaus.org/browse/SCM-455 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn >Affects Versions: 1.2 > Environment: Maven 2.0.10 >Reporter: Todd Thiessen >Assignee: Olivier Lamy > Fix For: 1.3 > > Attachments: scm-author.patch > > > If the author of a change has spaces in it, the scmLchangelog does not pick > up this change. I have reproduced this with svn. I have not tried with other > providers. > I have done a detailed analysis of the problem and have a fix. > The file which parses the changelog output is: > scm\maven-scm-providers\maven-scm-providers-svn\maven-scm-provider-svnexe\src\main\java\org\apache\maven\scm\provider\svn\svnexe\command\changelog\SvnChangeLogConsumer.java > This file uses a regular expression which does not recognize a regular > expression which contains spaces in the author's name. The regular expression > expects the author to be in a "userID" kind of format. > So, for example, if the author of a change was "thiessen", then the command > mvn scm:changelog would pick up this change. > However, if the author was "Todd Thiessen", the change which be skipped > entirely. > As far as my understanding goes, svn:author is simply a property and makes no > statement that the author MUST be in userID format. SVN users are free to > change the author as they see fit using SVN hooks. This is reasonable since > often the userID isn't very readable to a human reader. Thus putting in the > author's full name is very helpful. > Note that this issue has downstream effects in that it affects the change log > plugin: > http://maven.apache.org/plugins/maven-changelog-plugin/ > I have submitted a patch with a resolution to this. The patch simply treats > the author portion of an svn log command as text. It does not mandate that > the author must be in a certain format. The patch includes junit tests cases > which reproduce the problem and also the changes to the main code to fix it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4471) Profile activation fails if contains variables
[
http://jira.codehaus.org/browse/MNG-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4471.
--
Resolution: Cannot Reproduce
Assignee: Benjamin Bentmann
> Profile activation fails if contains variables
> --
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
>Reporter: J C
>Assignee: Benjamin Bentmann
> Attachments: pom.xml, testcase.xml
>
>
> See the attached testcase.
> The profile is not activated when has variables in it:
> ${env.M2_HOME}/bin/mvn
> But when the path is absolute, it works:
> /my/maven/home/bin/mvn
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-4471) Profile activation fails if contains variables
[
http://jira.codehaus.org/browse/MNG-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4471:
---
Attachment: pom.xml
I slightly modified your test POM to allow for better testing. Running
{noformat}
mvn org.apache.maven.plugins:maven-help-plugin:2.1:effective-pom -V
{noformat}
on this POM I get
{noformat}
...
ACTIVATED
M:\am\3.0-alpha-5\bin\..
...
{noformat}
in the console output, i.e. I failed to reproduce the issue.
If you receive an effective POM using the above command where the property
{{test}} is present but {{profile}} not, please attach this log and re-open the
issue. In this case, it would also be nice to know whether Maven 2.x behaves
differently.
Otherwise, I assume the environment variable is simply not properly set on your
machine, i.e. {{export M2_HOME=...}}.
> Profile activation fails if contains variables
> --
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
>Reporter: J C
> Attachments: pom.xml, testcase.xml
>
>
> See the attached testcase.
> The profile is not activated when has variables in it:
> ${env.M2_HOME}/bin/mvn
> But when the path is absolute, it works:
> /my/maven/home/bin/mvn
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-165) Ability to exclude filtered resources from eclipse's source directories
[ http://jira.codehaus.org/browse/MECLIPSE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Florian Kirchmeir updated MECLIPSE-165: --- Attachment: ResourceExcludes.patch I've implemented a "resourceExcludes" parameter, similar to the "sourceEcludes" added in version 2.7. This way, you can at least manually configure stuff you want to have excluded. > Ability to exclude filtered resources from eclipse's source directories > --- > > Key: MECLIPSE-165 > URL: http://jira.codehaus.org/browse/MECLIPSE-165 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: PDE support >Affects Versions: 2.3 >Reporter: Cédric Vidal >Assignee: Brian Fox > Attachments: MECLIPSE-165.patch, ResourceExcludes.patch > > > Resources should be in the classpath from Eclipse's point of view because > they end up being in the classpath from Maven 2's point of view, but whenever > resources are marked as being filtered by M2, Eclipse puts them unfiltered in > the classpath thus introducing an inconsistency between Maven 2 and Eclipse. > Whether or not to include filtered resource directories in eclipse's sources > directories is therefore a real dilemna. While I'm sure a consistent solution > to this dilemna will eventually be found, it would be great to let the user > choose what to do in the meantime. > The attached patch adresses this issue by adding a parameter, > 'excludeFilteredResourcesFromSourceDirs', which when set to true prevents > filtered resource directories from being added to eclipse's source > directories. The parameter defaults to false to avoid changing current > projects' behavior. > Regards, > Cédric Vidal > http://www.B-Process.com > PS: This parameter could be overriden on a per resource directory basis as > mentionned in MECLIPSE-162. This is not adressed by the attached patch though -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-71) javac compilation error for package-info.java containing package annotation
[ http://jira.codehaus.org/browse/MCOMPILER-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199749#action_199749 ] Ivan Bogouchev commented on MCOMPILER-71: - We experience the same problem and it seems this is a bug in javac 1.5 : http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6198196 > javac compilation error for package-info.java containing package annotation > --- > > Key: MCOMPILER-71 > URL: http://jira.codehaus.org/browse/MCOMPILER-71 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: Windows XP SP2 > JDK 1.5.0_15 >Reporter: Gabriel Forro > Attachments: compile_error_2.0.2.log > > > The package-info.java files can not be compiled in Maven 2 if the 2.0.2 > maven-compiler-plugin is used. package-info.java files can be compiled by > earlier versions of the maven-compiler-plugin (I have tried 2.0 and 2.0.1). > Newer snapshot versions does not work also and it fails in the same error (I > have tried version 2.1-snapshot). > This problem can be caused by an unusual behavior of the javac from jdk 1.5. > This behavior is as follows: > You can not use '/' file separator during compiling package-info.java (for > instance "javac sk/forro/package-info.java"). You must use '\' separator (for > instance "javac sk\forro\package-info.java"). If you use the '/' separator > you get the the compilation error reported by this bug (package annotations > should be in file package-info.java). This is javac 'feature' has been > removed in jdk 6 and in jdk 6 you can use either '/' or '\' - it does not > matter. > It looks like the maven-compiler-plugin or one of its components (I mean > plexus-x artefacts used by maven-compiler-plugin) uses '/' instead of the '\' > in the MS Windows environment. > I have attached a log file of an unsuccessful build (generated by mvn install > -X) > A possible workaround to solve this problem temporarily: > The compilation successes if I use either an older version of > maven-compiler-plugin or jdk 6 or do not use package-info.java files at all. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4471) Profile activation fails if contains variables
Profile activation fails if contains variables
--
Key: MNG-4471
URL: http://jira.codehaus.org/browse/MNG-4471
Project: Maven 2
Issue Type: Bug
Components: Profiles
Affects Versions: 3.0-alpha-5
Environment: Mac OS X 10.6.2
Reporter: J C
Attachments: testcase.xml
See the attached testcase.
The profile is not activated when has variables in it:
${env.M2_HOME}/bin/mvn
But when the path is absolute, it works:
/my/maven/home/bin/mvn
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-200) Please add support for the AJDT plugin
[ http://jira.codehaus.org/browse/MECLIPSE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199741#action_199741 ] Eirik Rosvold Larsen commented on MECLIPSE-200: --- Arnaud: thanks for the link. After plundering around, I found that adding wtp version 2.0 to the pom automatically added the required attributes to the classpathentries like this: A nice feature was that the attribute was only added if the maven dependency scope was compile or runtime. Small question though: If the scope is provided, the maven eclipse plugin doesn't add any attribute to the corresponding classpathentry. The wtp plugin for eclipse seems to support the following attribute for entries that are not to be deployed: "org.eclipse.jst.component.nondependency" Maybe you should add this for scope provided? Just a thought.. Thanks again! > Please add support for the AJDT plugin > -- > > Key: MECLIPSE-200 > URL: http://jira.codehaus.org/browse/MECLIPSE-200 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: AJDT support >Affects Versions: 2.2 >Reporter: Eric Berry >Assignee: Arnaud Heritier > Fix For: 2.6 > > Attachments: ajdt.patch, maven-eclipse-plugin.zip, > maven-eclipse-plugin.zip > > > Please add support for the AJDT plugin. > I have modified the eclipse plugin for our site with the needed changes. I > have attached the modifications that I made for someone to look at and > incorporate into the plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4060) Remove support for profiles.xml
[
http://jira.codehaus.org/browse/MNG-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199719#action_199719
]
Milos Kleint commented on MNG-4060:
---
the fact that mixins are mentioned to be placed in repository, doesn't make
them a proper replacement of profiles.xml file for user-private settings..
> Remove support for profiles.xml
> ---
>
> Key: MNG-4060
> URL: http://jira.codehaus.org/browse/MNG-4060
> Project: Maven 2
> Issue Type: Task
> Components: Profiles
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
>Priority: Minor
> Fix For: 3.0-alpha-3
>
>
> As per [r748226|http://svn.eu.apache.org/viewvc?view=rev&revision=748226]
> support for {{profiles.xml}} will be dropped. Tracking this here as a user
> visible change for the release history.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4060) Remove support for profiles.xml
[
http://jira.codehaus.org/browse/MNG-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199718#action_199718
]
Tuomas Kiviaho commented on MNG-4060:
-
I think that the feature has become obsolete because it can be replaced with
mixins (http://markmail.org/thread/6qqccwkrry5up2un). I just don't know how to
do this.
> Remove support for profiles.xml
> ---
>
> Key: MNG-4060
> URL: http://jira.codehaus.org/browse/MNG-4060
> Project: Maven 2
> Issue Type: Task
> Components: Profiles
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
>Priority: Minor
> Fix For: 3.0-alpha-3
>
>
> As per [r748226|http://svn.eu.apache.org/viewvc?view=rev&revision=748226]
> support for {{profiles.xml}} will be dropped. Tracking this here as a user
> visible change for the release history.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4060) Remove support for profiles.xml
[
http://jira.codehaus.org/browse/MNG-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199715#action_199715
]
Milos Kleint commented on MNG-4060:
---
this doesn't sound like a "minor task" to me. The only way to have per-project
non-sharable settings has been removed. Now only global per project settings
are available in settings.xml.
It will cause me headaches in netbeans IDE integration eg. the deployment
server TYPE is noted in the pom.xml as it's something that is usually shared
across all developers, but the deployment server ID is stored in profiles.xml
file because the ID token value is user installation based (can include path to
the server installation)
> Remove support for profiles.xml
> ---
>
> Key: MNG-4060
> URL: http://jira.codehaus.org/browse/MNG-4060
> Project: Maven 2
> Issue Type: Task
> Components: Profiles
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
>Priority: Minor
> Fix For: 3.0-alpha-3
>
>
> As per [r748226|http://svn.eu.apache.org/viewvc?view=rev&revision=748226]
> support for {{profiles.xml}} will be dropped. Tracking this here as a user
> visible change for the release history.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEAR-116) different build results from single module build and from reactor build
different build results from single module build and from reactor build --- Key: MEAR-116 URL: http://jira.codehaus.org/browse/MEAR-116 Project: Maven 2.x Ear Plugin Issue Type: Bug Affects Versions: 2.4 Environment: maven 2.2.0 Reporter: Milos Kleint Priority: Critical attached is a sample application as generated by netbeans 6.8 (using archetypes from org.codehaus.mojo.archetypes) a simple ear+ejb+war multiproject. when building everything together from the root pom, I get this output: [ear:ear] Copying artifact[ejb:org.kleint:samplejavaee6-ejb:1.0-SNAPSHOT] to[samplejavaee6-ejb.jar] Copying artifact[war:org.kleint:samplejavaee6-web:1.0-SNAPSHOT] to[samplejavaee6-web.war] and the war and ejb artifacts are included with names not including version. However if I later do a mvn clean install on the ear project, I get this output: [ear:ear] Copying artifact[ejb:org.kleint:samplejavaee6-ejb:1.0-SNAPSHOT] to[samplejavaee6-ejb-1.0-SNAPSHOT.jar] Copying artifact[war:org.kleint:samplejavaee6-web:1.0-SNAPSHOT] to[samplejavaee6-web-1.0-SNAPSHOT.war] and the war/ejb artifacts get a version in the name. This sounds like it has to do with the finalname being resolved differently in single module build and in reactor build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
