[jbosstools-issues] [JBoss JIRA] (JBDS-1993) remove common components from JBDS SOA site and simply depend on JBDS Core upstream (was v20120114-1832-H1633-Beta1 - conflicts installing SOA tooling)
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Fri Feb 10 11:00:48 EST 2012
[ https://issues.jboss.org/browse/JBDS-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665683#comment-12665683 ]
Nick Boldt edited comment on JBDS-1993 at 2/10/12 10:59 AM:
------------------------------------------------------------
I've added the following to these jobs:
https://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.soa-tooling.updatesite/
{code}
--- /qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_trunk.soa-tooling.updatesite/config-history/2012-01-31_15-16-12/config.xml
+++ /qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_trunk.soa-tooling.updatesite/config-history/2012-02-10_10-53-27/config.xml
@@ -101,106 +99,108 @@
<mavenName>maven-3.0.3</mavenName>
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m</jvmOptions>
<pom>${WORKSPACE}/sources/product-soa/pom.xml</pom>
+ <properties># use latest upstream JBDS nightly Core update site instead of "wild components" in the composite staging site
+jbosstools-nightly-staging-composite=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/product/
+# use latest upstream JBT nightly SOA Tooling site instead of "wild components" in the composite staging site
+jbosstools-nightly-staging-composite-soa-tooling=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/</properties>
<usePrivateRepository>false</usePrivateRepository>
</hudson.tasks.Maven>
<hudson.tasks.Shell>
{code}
https://hudson.qa.jboss.com/hudson/job/devstudio-5.0_stable_branch.soa-tooling.updatesite/
{code}
--- /qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_stable_branch.soa-tooling.updatesite/config-history/2011-12-15_18-40-34/config.xml
+++ /qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_stable_branch.soa-tooling.updatesite/config-history/2012-02-10_10-56-43/config.xml
@@ -46,52 +47,53 @@
</pre>
</description>
- <defaultValue>clean install -B -U -fae -e -P hudson,jbosstools-nightly-staging-composite,jboss-requirements-composite-mirror,local.site,local.requirements -Dlocal.site=file://home/hudson/static_build_env/jbds/jbds-target-platform_3.3.indigo/jbds500-e371-wtp331.target/ -Dmaven.repo.local=${WORKSPACE}/m2-repository -Dlocal.site=file:///home/hudson/static_build_env/jbds/jbds-target-platform_3.3.indigo/jbds500-e371-wtp331.target</defaultValue>
+ <defaultValue>clean install -B -U -fae -e -P hudson,jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,jboss-requirements-composite-mirror,local.site,local.requirements -Dlocal.site=file://home/hudson/static_build_env/jbds/jbds-target-platform_3.3.indigo/jbds500-e371-wtp331.target/ -Dmaven.repo.local=${WORKSPACE}/m2-repository -Dlocal.site=file:///home/hudson/static_build_env/jbds/jbds-target-platform_3.3.indigo/jbds500-e371-wtp331.target</defaultValue>
</hudson.model.StringParameterDefinition>
<hudson.model.ChoiceParameterDefinition>
<name>RELEASE</name>
@@ -127,132 +127,136 @@
<mavenName>maven-3.0.3</mavenName>
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m</jvmOptions>
<pom>${WORKSPACE}/sources/product-soa/pom.xml</pom>
+ <properties># use latest upstream JBDS nightly Core update site instead of "wild components" in the composite staging site
+jbosstools-nightly-staging-composite=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable_branch.updatesite/product/
+# use latest upstream JBT nightly SOA Tooling site instead of "wild components" in the composite staging site
+jbosstools-nightly-staging-composite-soa-tooling=http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/</properties>
<usePrivateRepository>false</usePrivateRepository>
</hudson.tasks.Maven>
<hudson.tasks.Shell>
{code}
was (Author: nickboldt):
I've added this to the JBDS SOA aggregate job (for trunk) - need to now roll it out to stable_branch too.
{code}
--- /qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_trunk.soa-tooling.updatesite/config-history/2012-01-31_15-16-12/config.xml
+++ /qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_trunk.soa-tooling.updatesite/config-history/2012-02-10_10-53-27/config.xml
@@ -101,106 +99,108 @@
<mavenName>maven-3.0.3</mavenName>
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m</jvmOptions>
<pom>${WORKSPACE}/sources/product-soa/pom.xml</pom>
+ <properties># use latest upstream JBDS nightly Core update site instead of "wild components" in the composite staging site
+jbosstools-nightly-staging-composite=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/product/
+# use latest upstream JBT nightly SOA Tooling site instead of "wild components" in the composite staging site
+jbosstools-nightly-staging-composite-soa-tooling=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/</properties>
<usePrivateRepository>false</usePrivateRepository>
</hudson.tasks.Maven>
<hudson.tasks.Shell>
{code}
> remove common components from JBDS SOA site and simply depend on JBDS Core upstream (was v20120114-1832-H1633-Beta1 - conflicts installing SOA tooling)
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-1993
> URL: https://issues.jboss.org/browse/JBDS-1993
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.0.M5
> Environment: Version: 5.0.0.Beta1
> Build id: v20120114-1832-H1633-Beta1
> Build date: 20120114-1832
> http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.soa-tooling.updatesite/product-soa/ - nightly as of Jan 16
> Reporter: Len DiMaggio
> Assignee: Douglas Palmer
> Fix For: 5.0.0.Beta1
>
> Attachments: Screenshot.png
>
>
> Attempting to install the "SOA abridged" plugins from:
> http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.soa-tooling.updatesite/product-soa/ (nightly - Jan 16 2012)
> On top of the Jan 16 build:
> Version: 5.0.0.Beta1
> Build id: v20120114-1832-H1633-Beta1
> Build date: 20120114-1832
> Results in these errors:
> Your original request has been modified.
> "Runtime Initialization" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Runtime Initialization 1.3.0.v20120116-1513-H527-Beta1 (org.jboss.tools.runtime.feature.feature.group 1.3.0.v20120116-1513-H527-Beta1)
> Software currently installed: JBoss Developer Studio 5.0.0.201201141342 (com.jboss.jbds.all 5.0.0.201201141342)
> Only one of the following can be installed at once:
> JBoss Runtime Initializer 1.3.0.v20120114-1741-H525-Beta1 (org.jboss.tools.runtime 1.3.0.v20120114-1741-H525-Beta1)
> JBoss Runtime Initializer 1.3.0.v20120116-1513-H527-Beta1 (org.jboss.tools.runtime 1.3.0.v20120116-1513-H527-Beta1)
> Cannot satisfy dependency:
> From: JBoss Developer Studio 5.0.0.201201141342 (com.jboss.jbds.all 5.0.0.201201141342)
> To: org.jboss.tools.runtime.feature.feature.group [1.3.0.v20120114-1741-H525-Beta1]
> Cannot satisfy dependency:
> From: Runtime Initialization 1.3.0.v20120114-1741-H525-Beta1 (org.jboss.tools.runtime.feature.feature.group 1.3.0.v20120114-1741-H525-Beta1)
> To: org.jboss.tools.runtime [1.3.0.v20120114-1741-H525-Beta1]
> Cannot satisfy dependency:
> From: Runtime Initialization 1.3.0.v20120116-1513-H527-Beta1 (org.jboss.tools.runtime.feature.feature.group 1.3.0.v20120116-1513-H527-Beta1)
> To: org.jboss.tools.runtime [1.3.0.v20120116-1513-H527-Beta1]
--
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
More information about the jbosstools-issues
mailing list