[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-11374 at 3/22/12 10:43 AM:
--------------------------------------------------------------
Rob:
I applaud the fact that a) you read the docs, b) you determined the default value, and c)
feel that the default for end users should not be the one used by Jenkins, and d) reported
a JIRA. This means the system is up. Truly you are full of consummate v's, and a
burninating force to be reckoned with! :D (It's moments like this I wish I could
install a lightswitch for the sole purpose of raving.
(
http://www.hrwiki.org/wiki/The_Cheat%27s_Lightswitch)
--
Since we're looking to change this and since you use the work "insists"
(which could imply you don't like the suggested default path), where would YOU like
the default to be? I can update both the parent pom AND the docs, if a new default would
make more sense. Would /tmp be good? I don't know if I can do relative or
${HOME}-based paths and have Tycho resolve them w/o setting them via commandline.
(Note too that in addition to the wiki and the parent pom, I will need to change all the
jobs that use the local.site profile so that they now set an override value of
-Dsite.local=file:///home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/
to correctly resolve the outside-of-Jenkins-workspace local site. This will need to be
done for all three development streams - 3.2x, 3.3x, and trunk.
was (Author: nickboldt):
Rob:
I applaud the fact that a) you read the docs, b) you determined the default value, and c)
feel that the default for end users should not be the one used by Jenkins, and d) reported
a JIRA. This means the system's working. Truly you are full of consummate v's, and
a burninating force to be reckoned with! :D (It's moments like this I wish I could
install a lightswitch for the sole purpose of raving.
(
http://www.hrwiki.org/wiki/The_Cheat%27s_Lightswitch)
--
Since we're looking to change this and since you use the work "insists"
(which could imply you don't like the suggested default path), where would YOU like
the default to be? I can update both the parent pom AND the docs, if a new default would
make more sense. Would /tmp be good? I don't know if I can do relative or
${HOME}-based paths and have Tycho resolve them w/o setting them via commandline.
(Note too that in addition to the wiki and the parent pom, I will need to change all the
jobs that use the local.site profile so that they now set an override value of
-Dsite.local=file:///home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/
to correctly resolve the outside-of-Jenkins-workspace local site. This will need to be
done for all three development streams - 3.2x, 3.3x, and trunk.
BUILD USABILITY BUG: build should assume target platform is in
build/target-platform/REPO
------------------------------------------------------------------------------------------
Key: JBIDE-11374
URL:
https://issues.jboss.org/browse/JBIDE-11374
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta3
Reporter: Rob Stryker
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
If I run the command: mvn clean install -f ../build/pom-core.xml
-Parchives-bootstrap,default,local.site -Dmaven.test.skip=true
Then the build system assumes we're running on hudson. The error is:
{code}
[ERROR] Internal error: java.lang.RuntimeException: java.lang.RuntimeException:
org.eclipse.equinox.p2.core.ProvisionException: No repository found at
file:/home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/.
-> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException:
java.lang.RuntimeException: org.eclipse.equinox.p2.core.ProvisionException: No repository
found at
file:/home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/.
{code}
Our documentation, however, insists we put the repo over in build/target-platform/REPO/.
If our documentation wants the target-platform there, then the build system should assume
it is there first, rather than assume it is in a hudson-specific location.
Documentation:
https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3
Currently, if no local.site is set, it assumes it will be at
file:/home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/,
but really it should assume it is at ../build/target-platform/REPO/
--
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