]
Max Rydahl Andersen commented on JBDS-2253:
-------------------------------------------
Tried using the staging site on an eclipse with JBT Alpha2 installed - that should work
should it not ?
But i'm getting this funky error:
Cannot complete the install because of a conflicting dependency.
Software being installed: JBoss Developer Studio (Core Features)
6.0.0.Beta1-v20121015-0254-B45 (com.jboss.jbds.product.feature.feature.group
6.0.0.Beta1-v20121015-0254-B45)
Software currently installed: JBoss Portlet 1.4.0.Alpha2-v20120922-1553-B34
(org.jboss.tools.portlet.feature.feature.group 1.4.0.Alpha2-v20120922-1553-B34)
Only one of the following can be installed at once:
JBoss Portlet 1.4.0.Beta1-v20121013-2108-B36 (org.jboss.tools.portlet.ui
1.4.0.Beta1-v20121013-2108-B36)
JBoss Portlet 1.4.0.Alpha2-v20120922-1553-B34 (org.jboss.tools.portlet.ui
1.4.0.Alpha2-v20120922-1553-B34)
Cannot satisfy dependency:
From: JBoss Developer Studio (Core Features) 6.0.0.Beta1-v20121015-0254-B45
(com.jboss.jbds.product.feature.feature.group 6.0.0.Beta1-v20121015-0254-B45)
To: org.jboss.tools.portlet.feature.feature.group [1.4.0.Beta1-v20121013-2108-B36]
Cannot satisfy dependency:
From: JBoss Portlet 1.4.0.Alpha2-v20120922-1553-B34
(org.jboss.tools.portlet.feature.feature.group 1.4.0.Alpha2-v20120922-1553-B34)
To: org.jboss.tools.portlet.ui [1.4.0.Alpha2-v20120922-1553-B34]
Cannot satisfy dependency:
From: JBoss Portlet 1.4.0.Beta1-v20121013-2108-B36
(org.jboss.tools.portlet.feature.feature.group 1.4.0.Beta1-v20121013-2108-B36)
To: org.jboss.tools.portlet.ui [1.4.0.Beta1-v20121013-2108-B36]
Support installing JBDS 6 into Eclipse 4.2 ("BYOE")
---------------------------------------------------
Key: JBDS-2253
URL:
https://issues.jboss.org/browse/JBDS-2253
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build, updatesite
Affects Versions: 6.0.0.Alpha1
Reporter: Nick Boldt
Assignee: Len DiMaggio
Labels: respin-b
Fix For: 4.0.0.Beta1, 6.0.0.Beta1
Attachments: BYOE-Juno42-JBDS6Nightly-central1.png,
BYOE-Juno42-JBDS6Nightly-central2.png, core-site-option1.png,
JBDS-2253.40x.branch.patch.txt, JBDS2253-add-update-sites-for-m2e-and-egit.png,
JBDS2253-egit2.0-installed.png,
JBDS2253-install-entire-JBDS-BrandedProduct-feature-to-EclipsePlatformRuntimeBinary4.2.1-note-changed-icons-and-About-screen.png,
JBDS2253-install-entire-JBDS-BrandedProduct-feature-to-EclipsePlatformRuntimeBinary4.2.1-uncheck-group-by-category.png,
JBDS2253-install-entire-JBDS-core-site-to-EclipsePlatformRuntimeBinary4.2.1-About-after-with-Central.png,
JBDS2253-install-entire-JBDS-core-site-to-EclipsePlatformRuntimeBinary4.2.1-About-before.png,
JBDS2253-install-entire-JBDS-core-site-to-EclipsePlatformRuntimeBinary4.2.1-available-sites.png,
JBDS2253-install-entire-JBDS-core-site-to-EclipsePlatformRuntimeBinary4.2.1.png,
JBDS2253-install-updated-to-egit2.2-and-m2e1.3.png,
JBDS2253-install-updates-to-egit2.2-and-m2e1.3.png,
JBDS2253-splash-screen-has-version-6.0.0-but-wrong-image.png,
JBDS2253_install_core_features-whole-category.png, JBDS2253_install_core_features.png,
JBDS2253_install_everything.png, techpreview-site-option1.png,
techpreview-site-option2.png
BYOE JBDS 6 Nightly
1. Launch clean Eclipse 4.2
2. Help > Install new
3. Add the following sites (sorry, VPN required!)
http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju...
(target platform)
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_trunk....
(extras)
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_trunk....
(product)
4. Select all categorized features on the /product/ site. Click Next. Install. Restart
when prompted.
Once we have a first Early Access release of JBDS 6, the above process will change to:
1. Launch clean Eclipse 4.2
2. Help > Install new
3. Add the following site (will be public, no VPN required)
https://devstudio.jboss.com/updates/6.0-staging/central/core/ (target platform + product
+ extras)
4. Select all categorized features. Click Next. Install. Restart when prompted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: