[jbosstools-issues] [JBoss JIRA] (JBDS-1993) v20120114-1832-H1633-Beta1 - conflicts installing SOA tooling

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659878#comment-12659878 ] 

Nick Boldt edited comment on JBDS-1993 at 1/17/12 10:56 AM:
------------------------------------------------------------

These two builds (JBDS Core, JBDS SOA) currently build in parallel so that they can spin faster.

We could chain them so they build in series instead, but in either case they're pulling bits from the latest available on the staging site (which could change between builds).

Really the solution here is to worry about this only when we hit the stable_branch cycle (after code freeze and branching) where the dev is slower and the shared dependencies (like runtime detection component) should be done spinning.

--

I suppose the alternative approach - if you want to guarantee that all nightlies from trunk are installable onto their equivalent nightly JBDS Core build - would be to remove shared components from the SOA site.

Therefore, there'd be no more tests, common, or runtime, so that there'd only be one version available to install -- the version ALREADY installed in JBDS.
                
      was (Author: nickboldt):
    These two builds (JBDS Core, JBDS SOA) currently build in parallel so that they can spin faster.

We could chain them so they build in series instead, but in either case they're pulling bits from the latest available on the staging site.

Really the solution here is to worry about this only when we hit the stable_branch cycle (after code freeze and branching) where the dev is slower and the shared dependencies (like runtime detection component) should be done spinning.

--

I suppose the alternative approach - if you want to guarantee that all nightlies from trunk are installable onto their equivalent nightly JBDS Core build - would be to remove shared components from the SOA site.

Therefore, there'd be no more tests, common, or runtime, so that there'd only be one version available to install -- the version ALREADY installed in JBDS.
                  
> 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 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: Nick Boldt
>             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