[JBoss JIRA] (JBIDE-11374) BUILD USABILITY BUG: build should assume target platform is in build/target-platform/REPO
4:04 a.m.
Rob Stryker created JBIDE-11374:
-----------------------------------
Summary: 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
9:40 a.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11374:
------------------------------------
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
--
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
9:42 a.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-11374 at 3/22/12 10:42 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'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.
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
--
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
9:44 a.m.
[
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
2:04 p.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11374:
------------------------------------
Did a bit more digging here... turns out that while you CAN pass in a platform variable
like ${HOME} (if you're not on Windows), you can't use ${basedir} or
${project.build.directory} to define a relative path [1], since ${basedir} is set to each
plugin or feature's path when resolving target platform, eg.:
{code}
In parent pom:
<local.site>file:///${basedir}/../build/target-platform/REPO/</local.site>
Then run this:
cd ~/trunk/tests; mvn3 install -Plocal.site
And get:
[INFO] Adding repository
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/
[ERROR] Internal error: java.lang.RuntimeException: java.lang.RuntimeException:
org.eclipse.equinox.p2.core.ProvisionException: No repository found at
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/.
-> [Help 1]
{code}
[1] http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
And since I don't know for sure that you have the target-platform folder checked out
in ~/trunk/build/target-platform, and under that a REPO/ folder exists, I can't use an
absolute path to the directory.
So, we're back to just setting the path like this:
{code:title=https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3}
cd <yourComponent>
mvn clean install -U -B -fae -e -P local.site
-Dlocal.site=file:/${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt
or
mvn3 clean install -U -B -fae -e -Plocal.site
-Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt
{code}
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
2:06 p.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-11374 at 3/23/12 3:05 PM:
-------------------------------------------------------------
Did a bit more digging here... turns out that while you CAN pass in a platform variable
like ${HOME} (if you're not on Windows), you can't use ${basedir} or
${project.build.directory} to define a relative path [1], since ${basedir} is set to each
plugin or feature's path when resolving target platform, eg.:
In parent pom:
{code}
<local.site>file:///${basedir}/../build/target-platform/REPO/</local.site>
{code}
Then run this:
{code}
cd ~/trunk/tests; mvn3 install -Plocal.site
{code}
And get:
{code}
[INFO] Adding repository
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/
[ERROR] Internal error: java.lang.RuntimeException: java.lang.RuntimeException:
org.eclipse.equinox.p2.core.ProvisionException: No repository found at
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/.
-> [Help 1]
{code}
[1] http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
And since I don't know for sure that you have the target-platform folder checked out
in ~/trunk/build/target-platform, and under that a REPO/ folder exists, I can't use an
absolute path to the directory.
So, we're back to just setting the path like this
(https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3):
{code}
cd <yourComponent>
mvn clean install -U -B -fae -e -P local.site
-Dlocal.site=file:/${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt
or
mvn3 clean install -U -B -fae -e -Plocal.site
-Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt
{code}
was (Author: nickboldt):
Did a bit more digging here... turns out that while you CAN pass in a platform
variable like ${HOME} (if you're not on Windows), you can't use ${basedir} or
${project.build.directory} to define a relative path [1], since ${basedir} is set to each
plugin or feature's path when resolving target platform, eg.:
{code}
In parent pom:
<local.site>file:///${basedir}/../build/target-platform/REPO/</local.site>
Then run this:
cd ~/trunk/tests; mvn3 install -Plocal.site
And get:
[INFO] Adding repository
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/
[ERROR] Internal error: java.lang.RuntimeException: java.lang.RuntimeException:
org.eclipse.equinox.p2.core.ProvisionException: No repository found at
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/.
-> [Help 1]
{code}
[1] http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
And since I don't know for sure that you have the target-platform folder checked out
in ~/trunk/build/target-platform, and under that a REPO/ folder exists, I can't use an
absolute path to the directory.
So, we're back to just setting the path like this:
{code:title=https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3}
cd <yourComponent>
mvn clean install -U -B -fae -e -P local.site
-Dlocal.site=file:/${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt
or
mvn3 clean install -U -B -fae -e -Plocal.site
-Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt
{code}
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
2:06 p.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-11374 at 3/23/12 3:06 PM:
-------------------------------------------------------------
Did a bit more digging here... turns out that while you CAN pass in a platform variable
like ${HOME} (if you're not on Windows), you can't use ${basedir} or
${project.build.directory} to define a relative path [1], since ${basedir} is set to each
plugin or feature's path when resolving target platform, eg.:
In parent pom:
{code}
<local.site>file:///${basedir}/../build/target-platform/REPO/</local.site>
{code}
Then run this:
{code}
cd ~/trunk/tests; mvn3 install -Plocal.site
{code}
And get:
{code}
[INFO] Adding repository
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/
[ERROR] Internal error: java.lang.RuntimeException: java.lang.RuntimeException:
org.eclipse.equinox.p2.core.ProvisionException: No repository found at
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/.
-> [Help 1]
{code}
[1] http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
And since I don't know for sure that you have the target-platform folder checked out
in ~/trunk/build/target-platform, and under that a REPO/ folder exists, I can't use an
absolute path to the directory.
So, we're back to just setting the path like this
(https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3):
bq.
cd <yourComponent>
mvn clean install -U -B -fae -e -P local.site
-Dlocal.site=file:/${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt
or
mvn3 clean install -U -B -fae -e -Plocal.site
-Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt
was (Author: nickboldt):
Did a bit more digging here... turns out that while you CAN pass in a platform
variable like ${HOME} (if you're not on Windows), you can't use ${basedir} or
${project.build.directory} to define a relative path [1], since ${basedir} is set to each
plugin or feature's path when resolving target platform, eg.:
In parent pom:
{code}
<local.site>file:///${basedir}/../build/target-platform/REPO/</local.site>
{code}
Then run this:
{code}
cd ~/trunk/tests; mvn3 install -Plocal.site
{code}
And get:
{code}
[INFO] Adding repository
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/
[ERROR] Internal error: java.lang.RuntimeException: java.lang.RuntimeException:
org.eclipse.equinox.p2.core.ProvisionException: No repository found at
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/.
-> [Help 1]
{code}
[1] http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
And since I don't know for sure that you have the target-platform folder checked out
in ~/trunk/build/target-platform, and under that a REPO/ folder exists, I can't use an
absolute path to the directory.
So, we're back to just setting the path like this
(https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3):
{code}
cd <yourComponent>
mvn clean install -U -B -fae -e -P local.site
-Dlocal.site=file:/${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt
or
mvn3 clean install -U -B -fae -e -Plocal.site
-Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt
{code}
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
2:08 p.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-11374 at 3/23/12 3:07 PM:
-------------------------------------------------------------
Did a bit more digging here... turns out that while you CAN pass in a platform variable
like ${HOME} (if you're not on Windows), you can't use ${basedir} or
${project.build.directory} to define a relative path [1], since ${basedir} is set to each
plugin or feature's path when resolving target platform, eg.:
In parent pom:
{code}
<local.site>file:///${basedir}/../build/target-platform/REPO/</local.site>
{code}
Then run this:
{code}
cd ~/trunk/tests; mvn3 install -Plocal.site
{code}
And get:
{code}
[INFO] Adding repository
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/
[ERROR] Internal error: java.lang.RuntimeException: java.lang.RuntimeException:
org.eclipse.equinox.p2.core.ProvisionException: No repository found at
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/.
-> [Help 1]
{code}
[1] http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
And since I don't know for sure that you have the target-platform folder checked out
in ~/trunk/build/target-platform, and under that a REPO/ folder exists, I can't use an
absolute path to the directory.
So, we're back to just setting the path like this
(https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3):
{code}cd <yourComponent>
mvn clean install -U -B -fae -e -P local.site
-Dlocal.site=file:/${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt
or
mvn3 clean install -U -B -fae -e -Plocal.site
-Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt
{code}
was (Author: nickboldt):
Did a bit more digging here... turns out that while you CAN pass in a platform
variable like ${HOME} (if you're not on Windows), you can't use ${basedir} or
${project.build.directory} to define a relative path [1], since ${basedir} is set to each
plugin or feature's path when resolving target platform, eg.:
In parent pom:
{code}
<local.site>file:///${basedir}/../build/target-platform/REPO/</local.site>
{code}
Then run this:
{code}
cd ~/trunk/tests; mvn3 install -Plocal.site
{code}
And get:
{code}
[INFO] Adding repository
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/
[ERROR] Internal error: java.lang.RuntimeException: java.lang.RuntimeException:
org.eclipse.equinox.p2.core.ProvisionException: No repository found at
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/.
-> [Help 1]
{code}
[1] http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
And since I don't know for sure that you have the target-platform folder checked out
in ~/trunk/build/target-platform, and under that a REPO/ folder exists, I can't use an
absolute path to the directory.
So, we're back to just setting the path like this
(https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3):
{quote}
cd <yourComponent>
mvn clean install -U -B -fae -e -P local.site
-Dlocal.site=file:/${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt
or
mvn3 clean install -U -B -fae -e -Plocal.site
-Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt
{quote}
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
2:08 p.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-11374 at 3/23/12 3:07 PM:
-------------------------------------------------------------
Did a bit more digging here... turns out that while you CAN pass in a platform variable
like ${HOME} (if you're not on Windows), you can't use ${basedir} or
${project.build.directory} to define a relative path [1], since ${basedir} is set to each
plugin or feature's path when resolving target platform, eg.:
In parent pom:
{code}
<local.site>file:///${basedir}/../build/target-platform/REPO/</local.site>
{code}
Then run this:
{code}
cd ~/trunk/tests; mvn3 install -Plocal.site
{code}
And get:
{code}
[INFO] Adding repository
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/
[ERROR] Internal error: java.lang.RuntimeException: java.lang.RuntimeException:
org.eclipse.equinox.p2.core.ProvisionException: No repository found at
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/.
-> [Help 1]
{code}
[1] http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
And since I don't know for sure that you have the target-platform folder checked out
in ~/trunk/build/target-platform, and under that a REPO/ folder exists, I can't use an
absolute path to the directory.
So, we're back to just setting the path like this
(https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3):
{quote}
cd <yourComponent>
mvn clean install -U -B -fae -e -P local.site
-Dlocal.site=file:/${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt
or
mvn3 clean install -U -B -fae -e -Plocal.site
-Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt
{quote}
was (Author: nickboldt):
Did a bit more digging here... turns out that while you CAN pass in a platform
variable like ${HOME} (if you're not on Windows), you can't use ${basedir} or
${project.build.directory} to define a relative path [1], since ${basedir} is set to each
plugin or feature's path when resolving target platform, eg.:
In parent pom:
{code}
<local.site>file:///${basedir}/../build/target-platform/REPO/</local.site>
{code}
Then run this:
{code}
cd ~/trunk/tests; mvn3 install -Plocal.site
{code}
And get:
{code}
[INFO] Adding repository
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/
[ERROR] Internal error: java.lang.RuntimeException: java.lang.RuntimeException:
org.eclipse.equinox.p2.core.ProvisionException: No repository found at
file:////home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/tests/plugins/org.jboss.tools.tests/../build/target-platform/REPO/.
-> [Help 1]
{code}
[1] http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
And since I don't know for sure that you have the target-platform folder checked out
in ~/trunk/build/target-platform, and under that a REPO/ folder exists, I can't use an
absolute path to the directory.
So, we're back to just setting the path like this
(https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3):
bq.
cd <yourComponent>
mvn clean install -U -B -fae -e -P local.site
-Dlocal.site=file:/${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt
or
mvn3 clean install -U -B -fae -e -Plocal.site
-Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt
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
2:10 p.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11374:
------------------------------------
Would using <local.site>file:///${HOME}/REPO/</local.site> make sense as a new
default value?
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
5:24 a.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11374:
---------------------------------------------
file:///${user.home}/jbosstools-target could work...problem is though that branches would
collide - but not sure how big a problem that is since its just a readonly flag.
maybe use jbosstools-target-${target.platform.version} would be a better approach ?
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
1:11 p.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11374:
------------------------------------
${target.platform.version} is undefined. Is that a typo, or does it need to be set
somewhere as a new <property> ?
Alternatively, how about this patch to the parent pom?
Idea is to set a new default for users building locally, and use the "hudson"
profile to automatically revert to the current default when run in Jenkins.
{code}
diff --git a/build/parent/pom.xml b/build/parent/pom.xml
index 4e983c1..d314157 100644
--- a/build/parent/pom.xml
+++ b/build/parent/pom.xml
@@ -37,7 +37,7 @@
<!-- 1b. or use -Plocal.site
-Dlocal.site=file:///home/$user/trunk/build/target-platform/REPO/ -->
<!-- TODO: don't forget to update JBDS .updatesite jobs when this
value changes! -->
-
<local.site>file:///home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/</local.site>
+
<local.site>file:///${user.home}/jbosstools-target-${JBT_VERSION}.${BUILD_ALIAS}</local.site>
<!-- 2a. URL of latest JBT nightly staging composite site (all the
components
in once place) -->
@@ -585,6 +585,9 @@
<name>BUILD_NUMBER</name>
</property>
</activation>
+ <properties>
+
<local.site>file:///home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/</local.site>
+ </properties>
<build>
{code}
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
1:13 p.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-11374 at 3/28/12 2:13 PM:
-------------------------------------------------------------
${target.platform.version} is undefined. Is that a typo, or does it need to be set
somewhere as a new <property> ?
Alternatively, how about this patch to the parent pom?
Idea is to set a new default for users building locally, and use the "hudson"
profile to automatically revert to the current default when run in Jenkins.
{code}
diff --git a/build/parent/pom.xml b/build/parent/pom.xml
index 4e983c1..d314157 100644
--- a/build/parent/pom.xml
+++ b/build/parent/pom.xml
@@ -37,7 +37,7 @@
<!-- 1b. or use -Plocal.site
-Dlocal.site=file:///home/$user/trunk/build/target-platform/REPO/ -->
<!-- TODO: don't forget to update JBDS .updatesite jobs when this
value changes! -->
-
<local.site>file:///home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/</local.site>
+
<local.site>file:///${user.home}/jbosstools-target-${JBT_VERSION}.${BUILD_ALIAS}</local.site>
<!-- 2a. URL of latest JBT nightly staging composite site (all the
components
in once place) -->
@@ -585,6 +585,9 @@
<name>BUILD_NUMBER</name>
</property>
</activation>
+ <properties>
+
<local.site>file:///home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/</local.site>
+ </properties>
<build>
{code}
For me, local.site=file:///${user.home}/jbosstools-target-${JBT_VERSION}.${BUILD_ALIAS}
resolves to file:////home/nboldt/jbosstools-target-3.3.0.Beta3.
was (Author: nickboldt):
${target.platform.version} is undefined. Is that a typo, or does it need to be set
somewhere as a new <property> ?
Alternatively, how about this patch to the parent pom?
Idea is to set a new default for users building locally, and use the "hudson"
profile to automatically revert to the current default when run in Jenkins.
{code}
diff --git a/build/parent/pom.xml b/build/parent/pom.xml
index 4e983c1..d314157 100644
--- a/build/parent/pom.xml
+++ b/build/parent/pom.xml
@@ -37,7 +37,7 @@
<!-- 1b. or use -Plocal.site
-Dlocal.site=file:///home/$user/trunk/build/target-platform/REPO/ -->
<!-- TODO: don't forget to update JBDS .updatesite jobs when this
value changes! -->
-
<local.site>file:///home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/</local.site>
+
<local.site>file:///${user.home}/jbosstools-target-${JBT_VERSION}.${BUILD_ALIAS}</local.site>
<!-- 2a. URL of latest JBT nightly staging composite site (all the
components
in once place) -->
@@ -585,6 +585,9 @@
<name>BUILD_NUMBER</name>
</property>
</activation>
+ <properties>
+
<local.site>file:///home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/</local.site>
+ </properties>
<build>
{code}
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
1:27 p.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11374:
---------------------------------------------
I just meant to refer to the version of the targetplatform artifact/pom.
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
1:31 p.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11374:
------------------------------------
So every time we respin the TP, users would be forced to pull down an update / create a
new folder on disk? That seems logical, if a bit heavy-handed.
How does one get the version of the artifact from Nexus as a ${variable} I can embed in a
pom?
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
1:47 p.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-11374:
-------------------------------
Attachment: JBIDE11374.patch.txt
New approach. Use a path under ~/.m2 which maps directly to the name of the latest target
platform. Instead of using 3.3.0.Beta3, use 3.3.indigo.SR2, since that TP will be used for
Beta1, Beta2, Beta3, and beyond.
Patch: [^JBIDE11374.patch.txt]
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
Attachments: JBIDE11374.patch.txt
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
2:02 p.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11374:
------------------------------------
Committed in trunk, respinning here:
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.target-platform/ >=364
Documented in wiki:
https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3#download-...
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
Attachments: JBIDE11374.patch.txt
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
12:26 a.m.
[
https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-11374.
------------------------------
Fix Version/s: 3.3.0.Beta3
(was: 3.3.0.CR1)
Resolution: Done
New default implemented for trunk and pushed to Nexus.
Enjoy!
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.Beta3
Attachments: JBIDE11374.patch.txt
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
5128
days inactive
5135
days old
jbosstools-issues@lists.jboss.org
17 comments
3 participants
participants (3)
-
Max Rydahl Andersen (JIRA) -
Nick Boldt (JIRA)
-
Rob Stryker (JIRA)