[
https://issues.jboss.org/browse/JBIDE-7565?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-7565 at 1/18/12 8:08 PM:
------------------------------------------------------------
{code}
rm -fr ~/.m2
DISPLAY=:4 nice -n19 /opt/maven3/bin/mvn clean install -f tests/pom.xml -B -U -fae -e |
tee buildlog.tests.no.parent.pom.txt
{code}
does work, as indicated, but that's only because there's no need to resolve
upstream binary dependencies from the JBT staging site.
Conversely, building JMX the same way fails because tests can't be found:
{code}
rm -fr ~/.m2
DISPLAY=:4 nice -n19 /opt/maven3/bin/mvn clean install -f jmx/pom.xml -B -U -fae -e | tee
buildlog.jmx.no.parent.pom.txt
[ERROR] Missing requirement: org.jboss.tools.jmx.core.test 1.2.0.qualifier requires
'bundle org.jboss.tools.tests 0.0.0' but it could not be found
{code}
And so while the bootstrap profile works:
{code}
rm -fr ~/.m2
DISPLAY=:4 nice -n19 /opt/maven3/bin/mvn clean install -f build/pom.xml -B -U -fae -e -P
jmx-bootstrap | tee buildlog.jmx-bootstrap.no.parent.pom.txt
{code}
If you want to resolve against upstream binary deps in the staging site (rather than
taking the time to build them locally), you need to use this:
{code}
mvn clean install ... -P jbosstools-nightly-staging-composite
{code}
Bottom line... not sure if this is a function of something Denis changed or the way Tycho
0.13 works vs. older versions, but we no longer need to explicitly build the parent pom as
part of a component build. \o/
was (Author: nickboldt):
{code}
rm -fr ~/.m2
DISPLAY=:4 nice -n19 /opt/maven3/bin/mvn clean install -f tests/pom.xml -B -U -fae -e |
tee buildlog.tests.no.parent.pom.txt
{code}
does work, as indicated, but that's only because there's no need to resolve
upstream binary dependencies from the JBT staging site.
Conversely, building JMX the same way fails because tests can't be found:
{code}
rm -fr ~/.m2
DISPLAY=:4 nice -n19 /opt/maven3/bin/mvn clean install -f jmx/pom.xml -B -U -fae -e | tee
buildlog.jmx.no.parent.pom.txt
[ERROR] Missing requirement: org.jboss.tools.jmx.core.test 1.2.0.qualifier requires
'bundle org.jboss.tools.tests 0.0.0' but it could not be found
{code}
And so while the bootstrap profile works:
{code}
rm -fr ~/.m2
DISPLAY=:4 nice -n19 /opt/maven3/bin/mvn clean install -f build/pom.xml -B -U -fae -e -P
jmx-bootstrap | tee buildlog.jmx-bootstrap.no.parent.pom.txt
{code}
If you want to resolve against upstream binary deps in the staging site, you need to use
this, or else first build them locally:
{code}
mvn clean install ... -P jbosstools-nightly-staging-composite
{code}
Bottom line... not sure if this is a function of something Denis changed or the way Tycho
0.13 works vs. older versions, but we no longer need to explicitly build the parent pom as
part of a component build. \o/
Problems publishing and accessing parent pom + target platforms
---------------------------------------------------------------
Key: JBIDE-7565
URL:
https://issues.jboss.org/browse/JBIDE-7565
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.2.0.Beta2
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 3.3.0.Beta1
Thought I had this solved, but on further testing, I've found a problem.
This file is 404'd:
http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o...
However, the one I actually published is fine:
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
So, when I try to retrieve the pom from the repo, I get this error:
[DEBUG] Using connector WagonRepositoryConnector with priority 0 for
http://repository.jboss.org/nexus/content/groups/public/
Downloading:
http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o...
[DEBUG] Reading resolution tracking file
/home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/resolver-status.properties
[DEBUG] Writing resolution tracking file
/home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/resolver-status.properties
[DEBUG] Could not find metadata
org.jboss.tools:org.jboss.tools.target.platform:0.0.1-SNAPSHOT/maven-metadata.xml in
jboss-public-repository-group (
http://repository.jboss.org/nexus/content/groups/public/)
[DEBUG] Using connector WagonRepositoryConnector with priority 0 for
http://repository.jboss.org/nexus/content/groups/public/
Downloading:
http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o...
[DEBUG] Reading resolution tracking file
/home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/org.jboss.tools.target.platform-0.0.1-SNAPSHOT-unified.target.lastUpdated
[DEBUG] Writing resolution tracking file
/home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/org.jboss.tools.target.platform-0.0.1-SNAPSHOT-unified.target.lastUpdated
[ERROR] Internal error: java.lang.RuntimeException: Could not resolve target platform
specification artifact
org.jboss.tools:org.jboss.tools.target.platform:target:unified:0.0.1-SNAPSHOT -> [Help
1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException:
Could not resolve target platform specification artifact
org.jboss.tools:org.jboss.tools.target.platform:target:unified:0.0.1-SNAPSHOT
How can I force the resolution process to look at
https://repository.jboss.org/nexus/content/repositories/snapshots instead of
http://repository.jboss.org/nexus/content/groups ?
Or, how can I force the missing/empty file to contain the correct versioning information
so that maven can find the artifact?
I also tried to switch from
<uniqueVersion>true</uniqueVersion>
to
<uniqueVersion>false</uniqueVersion>
but the published artifacts still have the uniqueVersion suffixes.
----------
Steps to reproduce:
# remove your existing local .m2 cache
if [[ -d ~/.m2 ]]; then mv ~/.m2 ~/.m2___GOOD; fi
# check out build folder
cd /tmp; svn co
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/
# check out tests folder
cd /tmp; svn co
http://anonsvn.jboss.org/repos/jbosstools/trunk/tests/
# build tests
cd /tmp/tests; mvn3 clean install -X -e -fae -U -B
Workaround:
However, if the parent pom is built locally, then the tests can be built too, w/o a
problem (because the parent pom + target platform artifacts now exist locally in my ~/.m2
folder):
# build parent pom + target platform
cd /tmp/build; mvn3 clean install -f parent/pom.xml
# build tests
cd /tmp/tests; mvn3 clean install -X -e -fae -U -B
----------
Here's how I'm building + publishing the artifacts, fwiw:
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta2.target-platf...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira