[
https://issues.jboss.org/browse/JBDS-1993?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1993:
----------------------------------
This issue is only to solve the problem of Core vs. SOA aggregate sites ending up with
disparate versions -- I don't have a solution that yet guarantees ALL components use
the same upstream in the nightly stack, since they might build at different times during
high-churn trunk development.
--
So, if you're building an *aggregate* site, you simply have to aggregate from TWO
places instead of ONE using <repository> references in your root pom.
Today, we aggregate the SOA site from the staging nightly site, eg.,
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/, and include
Runtime and Usage even though they're already in the upstream JBT Core site.
But because of JBIDE-10671, this will change to TWO sites, eg.,
http://download.jboss.org/jbosstools/updates/core/trunk/ and
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli....
remove common components from JBT SOA site and simply depend on JBT
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....
- 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....
(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