Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Not A Problem
-
2.4
-
None
-
None
Description
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.
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)]
When the prepare method forks a new maven instance, the profiles are not enabled, causing our repos to not be used:
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)]
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.
Attachments
Attachments
Issue Links
- is related to
-
-
- Closed
-