[jira] (MRELEASE-821) Profiles enabled on the command line are not passed to the forked maven instance
[
https://jira.codehaus.org/browse/MRELEASE-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317526#comment-317526
]
Robert Scholte commented on MRELEASE-821:
-
You said 2.2.1, or is this the maven-release-version?
Assuming that the profiles are listed in the {{settings.xml}}, you need to
upgrade Maven to 3.0.4, as mentioned
http://maven.apache.org/maven-release/maven-release-plugin/
> Profiles enabled on the command line are not passed to the forked maven
> instance
>
>
> Key: MRELEASE-821
> URL: https://jira.codehaus.org/browse/MRELEASE-821
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.4
>Reporter: Steve Ash
>Assignee: Robert Scholte
>Priority: Blocker
> Attachments: FS-RELEASE-RELEASE-31.log
>
>
> I enable some profiles on the command line, which activate our companies
> repositories. I see in the maven instance that is first called they are
> active.
> {panel}
> build 17-Jan-2013 12:40:34[INFO]
>
> build 17-Jan-2013 12:40:34[INFO] Building fuzzy-project 1.2.1-SNAPSHOT
> build 17-Jan-2013 12:40:34[INFO]
>
> ...
> build 17-Jan-2013 12:40:34[DEBUG] === PROJECT BUILD PLAN
>
> build 17-Jan-2013 12:40:34[DEBUG] Project:
> com.argodata.fuzzy:fuzzy-project:1.2.1-SNAPSHOT
> build 17-Jan-2013 12:40:34[DEBUG] Dependencies (collect): []
> build 17-Jan-2013 12:40:34[DEBUG] Dependencies (resolve): []
> build 17-Jan-2013 12:40:34[DEBUG] Repositories (dependencies): [central
> (http://membuild01:8081/artifactory/libs-release, releases), snapshots
> (http://membuild01:8081/artifactory/libs-snapshot, releases+snapshots),
> com.argodata (http://serv107.argo.local/archiva/repository/com.argodata,
> releases+snapshots)]
> {panel}
> When the prepare method forks a new maven instance, the profiles are not
> enabled, causing our repos to not be used:
> {panel}
> build 17-Jan-2013 12:41:21[INFO] [INFO]
>
> build 17-Jan-2013 12:41:21[INFO] [INFO] Building fuzzy-project 1.2.1
> build 17-Jan-2013 12:41:21[INFO] [INFO]
>
> ...
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] === PROJECT BUILD PLAN
>
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Project:
> com.argodata.fuzzy:fuzzy-project:1.2.1
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Dependencies (collect): []
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Dependencies (resolve): []
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Repositories (dependencies):
> [central (http://repo1.maven.org/maven2, releases)]
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Repositories (plugins) :
> [central (http://repo1.maven.org/maven2, releases)]
> {panel}
> We were using 2.2.1 and not getting some of our profiles passed to the forked
> process, but we were getting the repos there...so I'm really confused. I
> upgraded to 2.4 to fix the problem seeing that MRELEASE-260 seemed like the
> culprit. When I upgraded however, it started failing sooner due to this
> problem.
> So I'm lost.
> I've attached the whole log if you're interested.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-821) Profiles enabled on the command line are not passed to the forked maven instance
[
https://jira.codehaus.org/browse/MRELEASE-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317517#comment-317517
]
Steve Ash commented on MRELEASE-821:
I'm using Maven 3.0.3
> Profiles enabled on the command line are not passed to the forked maven
> instance
>
>
> Key: MRELEASE-821
> URL: https://jira.codehaus.org/browse/MRELEASE-821
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.4
>Reporter: Steve Ash
>Assignee: Robert Scholte
>Priority: Blocker
> Attachments: FS-RELEASE-RELEASE-31.log
>
>
> I enable some profiles on the command line, which activate our companies
> repositories. I see in the maven instance that is first called they are
> active.
> {panel}
> build 17-Jan-2013 12:40:34[INFO]
>
> build 17-Jan-2013 12:40:34[INFO] Building fuzzy-project 1.2.1-SNAPSHOT
> build 17-Jan-2013 12:40:34[INFO]
>
> ...
> build 17-Jan-2013 12:40:34[DEBUG] === PROJECT BUILD PLAN
>
> build 17-Jan-2013 12:40:34[DEBUG] Project:
> com.argodata.fuzzy:fuzzy-project:1.2.1-SNAPSHOT
> build 17-Jan-2013 12:40:34[DEBUG] Dependencies (collect): []
> build 17-Jan-2013 12:40:34[DEBUG] Dependencies (resolve): []
> build 17-Jan-2013 12:40:34[DEBUG] Repositories (dependencies): [central
> (http://membuild01:8081/artifactory/libs-release, releases), snapshots
> (http://membuild01:8081/artifactory/libs-snapshot, releases+snapshots),
> com.argodata (http://serv107.argo.local/archiva/repository/com.argodata,
> releases+snapshots)]
> {panel}
> When the prepare method forks a new maven instance, the profiles are not
> enabled, causing our repos to not be used:
> {panel}
> build 17-Jan-2013 12:41:21[INFO] [INFO]
>
> build 17-Jan-2013 12:41:21[INFO] [INFO] Building fuzzy-project 1.2.1
> build 17-Jan-2013 12:41:21[INFO] [INFO]
>
> ...
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] === PROJECT BUILD PLAN
>
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Project:
> com.argodata.fuzzy:fuzzy-project:1.2.1
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Dependencies (collect): []
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Dependencies (resolve): []
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Repositories (dependencies):
> [central (http://repo1.maven.org/maven2, releases)]
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Repositories (plugins) :
> [central (http://repo1.maven.org/maven2, releases)]
> {panel}
> We were using 2.2.1 and not getting some of our profiles passed to the forked
> process, but we were getting the repos there...so I'm really confused. I
> upgraded to 2.4 to fix the problem seeing that MRELEASE-260 seemed like the
> culprit. When I upgraded however, it started failing sooner due to this
> problem.
> So I'm lost.
> I've attached the whole log if you're interested.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-821) Profiles enabled on the command line are not passed to the forked maven instance
[
https://jira.codehaus.org/browse/MRELEASE-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-821.
---
Resolution: Not A Bug
Assignee: Robert Scholte
MRELEASE-571 is the issue responsible for the fix, and it has this quote:
{quote}
Be aware that this fix will only work for Maven3, because only this version has
an API to get the original passed commandline arguments.
To get the same result with Maven2 requires a lot of calculations and even then
it is not sure if all profiles are gathered.
{quote}
It is not possible to fix this for Maven2.
> Profiles enabled on the command line are not passed to the forked maven
> instance
>
>
> Key: MRELEASE-821
> URL: https://jira.codehaus.org/browse/MRELEASE-821
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.4
>Reporter: Steve Ash
>Assignee: Robert Scholte
>Priority: Blocker
> Attachments: FS-RELEASE-RELEASE-31.log
>
>
> I enable some profiles on the command line, which activate our companies
> repositories. I see in the maven instance that is first called they are
> active.
> {panel}
> build 17-Jan-2013 12:40:34[INFO]
>
> build 17-Jan-2013 12:40:34[INFO] Building fuzzy-project 1.2.1-SNAPSHOT
> build 17-Jan-2013 12:40:34[INFO]
>
> ...
> build 17-Jan-2013 12:40:34[DEBUG] === PROJECT BUILD PLAN
>
> build 17-Jan-2013 12:40:34[DEBUG] Project:
> com.argodata.fuzzy:fuzzy-project:1.2.1-SNAPSHOT
> build 17-Jan-2013 12:40:34[DEBUG] Dependencies (collect): []
> build 17-Jan-2013 12:40:34[DEBUG] Dependencies (resolve): []
> build 17-Jan-2013 12:40:34[DEBUG] Repositories (dependencies): [central
> (http://membuild01:8081/artifactory/libs-release, releases), snapshots
> (http://membuild01:8081/artifactory/libs-snapshot, releases+snapshots),
> com.argodata (http://serv107.argo.local/archiva/repository/com.argodata,
> releases+snapshots)]
> {panel}
> When the prepare method forks a new maven instance, the profiles are not
> enabled, causing our repos to not be used:
> {panel}
> build 17-Jan-2013 12:41:21[INFO] [INFO]
>
> build 17-Jan-2013 12:41:21[INFO] [INFO] Building fuzzy-project 1.2.1
> build 17-Jan-2013 12:41:21[INFO] [INFO]
>
> ...
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] === PROJECT BUILD PLAN
>
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Project:
> com.argodata.fuzzy:fuzzy-project:1.2.1
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Dependencies (collect): []
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Dependencies (resolve): []
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Repositories (dependencies):
> [central (http://repo1.maven.org/maven2, releases)]
> build 17-Jan-2013 12:41:21[INFO] [DEBUG] Repositories (plugins) :
> [central (http://repo1.maven.org/maven2, releases)]
> {panel}
> We were using 2.2.1 and not getting some of our profiles passed to the forked
> process, but we were getting the repos there...so I'm really confused. I
> upgraded to 2.4 to fix the problem seeing that MRELEASE-260 seemed like the
> culprit. When I upgraded however, it started failing sooner due to this
> problem.
> So I'm lost.
> I've attached the whole log if you're interested.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-821) Profiles enabled on the command line are not passed to the forked maven instance
Steve Ash created MRELEASE-821:
--
Summary: Profiles enabled on the command line are not passed to
the forked maven instance
Key: MRELEASE-821
URL: https://jira.codehaus.org/browse/MRELEASE-821
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.4
Reporter: Steve Ash
Priority: Blocker
Attachments: FS-RELEASE-RELEASE-31.log
I enable some profiles on the command line, which activate our companies
repositories. I see in the maven instance that is first called they are
active.
{panel}
build 17-Jan-2013 12:40:34[INFO]
build 17-Jan-2013 12:40:34[INFO] Building fuzzy-project 1.2.1-SNAPSHOT
build 17-Jan-2013 12:40:34[INFO]
...
build 17-Jan-2013 12:40:34[DEBUG] === PROJECT BUILD PLAN
build 17-Jan-2013 12:40:34[DEBUG] Project:
com.argodata.fuzzy:fuzzy-project:1.2.1-SNAPSHOT
build 17-Jan-2013 12:40:34[DEBUG] Dependencies (collect): []
build 17-Jan-2013 12:40:34[DEBUG] Dependencies (resolve): []
build 17-Jan-2013 12:40:34[DEBUG] Repositories (dependencies): [central
(http://membuild01:8081/artifactory/libs-release, releases), snapshots
(http://membuild01:8081/artifactory/libs-snapshot, releases+snapshots),
com.argodata (http://serv107.argo.local/archiva/repository/com.argodata,
releases+snapshots)]
{panel}
When the prepare method forks a new maven instance, the profiles are not
enabled, causing our repos to not be used:
{panel}
build 17-Jan-2013 12:41:21[INFO] [INFO]
build 17-Jan-2013 12:41:21[INFO] [INFO] Building fuzzy-project 1.2.1
build 17-Jan-2013 12:41:21[INFO] [INFO]
...
build 17-Jan-2013 12:41:21[INFO] [DEBUG] === PROJECT BUILD PLAN
build 17-Jan-2013 12:41:21[INFO] [DEBUG] Project:
com.argodata.fuzzy:fuzzy-project:1.2.1
build 17-Jan-2013 12:41:21[INFO] [DEBUG] Dependencies (collect): []
build 17-Jan-2013 12:41:21[INFO] [DEBUG] Dependencies (resolve): []
build 17-Jan-2013 12:41:21[INFO] [DEBUG] Repositories (dependencies):
[central (http://repo1.maven.org/maven2, releases)]
build 17-Jan-2013 12:41:21[INFO] [DEBUG] Repositories (plugins) :
[central (http://repo1.maven.org/maven2, releases)]
{panel}
We were using 2.2.1 and not getting some of our profiles passed to the forked
process, but we were getting the repos there...so I'm really confused. I
upgraded to 2.4 to fix the problem seeing that MRELEASE-260 seemed like the
culprit. When I upgraded however, it started failing sooner due to this
problem.
So I'm lost.
I've attached the whole log if you're interested.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
