[
https://jira.jboss.org/jira/browse/JBDS-221?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBDS-221:
---------------------------------
p2 takes a small eternity resolving dependencies. My "scientific" analysis was
"hmm... more than 30 seconds? I'll just let it run on another screen." I
have no idea how long it *actually* took to compute or download, just felt lengthy (the
update site is 160M), so it should take about as long as downloading an Eclipse SDK +
unpack200'ing and unjar'ing.
Version numbers? You mean the fact that this build still has 2.0.1 in it, not 2.1.0? At
the time it was spun, that's what it was called - these are the 3.0.1 equivalent bits.
:) But yes, we can respin as 2.1.0.whateversuffixyouwant
Splash and branding are fine for a JBDS upgrade.
If you start with Eclipse and install JBDS into it, you end up with JBoss Tools + a couple
extra features. No branding except as far as the Red Hat support link under the Help menu
and the red ball in Help > About (because of the JBDS product feature). IMHO this is as
expected.
eclipse update manager for JBDS
-------------------------------
Key: JBDS-221
URL:
https://jira.jboss.org/jira/browse/JBDS-221
Project: Developer Studio
Issue Type: Sub-task
Components: Build
Affects Versions: LATER
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Priority: Blocker
Fix For: 2.0.1, 2.1.0
Attachments: tasktop-signup-1.png, tasktop-signup-2.png, tasktop-signup-3.png
requires update manager to support password protected content.
Need to verify that the info in the following thread is correct:
http://dev.eclipse.org/newslists/news.eclipse.tools/msg49329.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira