[
https://jira.jboss.org/browse/JBDS-1405?page=com.atlassian.jira.plugin.sy...
]
Nick Boldt reassigned JBDS-1405:
--------------------------------
Assignee: Max Andersen (was: Nick Boldt)
Wow, that's weird. If you look closely you'll see BOTH the "old" CR1
features and the "new" Beta2 features, plus all the Beta2 plugins (but NONE of
the CR1-labelled ones).
Suspect this is a case of "cruft in the staging dir". Since the version of the
Beta2 features is NEWER (datestamp) than the CR1 features, only the Beta2 ones will be
activated.
I don't consider this blocking. We could purge the workspace and respin to clean the
cruft out, but I'm not worried about customer impact since the plugins aren't
present and the features are "older".
Wrong feature versions on JBDS 4.0.0.beta2
------------------------------------------
Key: JBDS-1405
URL:
https://jira.jboss.org/browse/JBDS-1405
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Build
Affects Versions: 4.0.0.Beta2
Environment: 4.0.0.v201011172142N-H477-Beta1, resp.
jbdevstudio-eap-linux-gtk-x86_64-4.0.0.v201011172142N-H477-Beta2.jar
Reporter: Jiri Peterka
Assignee: Max Andersen
Fix For: 4.0.0.Beta2
Attachments: beta1-wrong.png, beta2-mixed-versions.png, beta2-ok.png,
Screenshot-2.png, Screenshot-3.png
There are wrong versions on beta2 build. Features are mainly marked as beta1 although
it's beta2 build (see screen-shots)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira