[
https://issues.jboss.org/browse/JBDS-1707?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen reassigned JBDS-1707:
-----------------------------------------
Assignee: Nick Boldt (was: Max Rydahl Andersen)
yes, for now JBDS 5 milestones are not intended to be preloaded with access to SOA.
The current thinking is that once SOA plugins gets available the idea is to make them
aggregated into the core site so there is no default notion of a separated site for the
user - but for now that site exists externally and are not merged in.
JBDS 5 refers to 4.0 updatesites
--------------------------------
Key: JBDS-1707
URL:
https://issues.jboss.org/browse/JBDS-1707
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-5.0.0.v201106290641R-H21-M2.jar
Reporter: Libor Zoubek
Assignee: Nick Boldt
Priority: Blocker
Fix For: 5.0.0.M3
Right now JBDS 5 refers to
*
https://devstudio.jboss.com/updates/4.0/
*
https://devstudio.jboss.com/updates/4.0/extras/
Which is wrong, since users won't be albe to install 5.0 extras or SOA
We need to create 5.0 updatesites (5.0,5.0/extras,5.0/soa-tooling) + add/update
references in JBDS
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira