[
https://issues.jboss.org/browse/JBDS-1559?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1559:
----------------------------------
Maybe we should be looking at updating an old product build (CR1) to a new product build
(CR3) instead of the old uberbuild to product, since this issue will only hit Early Access
users and us devs, but won't affect a customer who's installed 4.0.0.GA wanting to
update to 4.0.1.GA.
I'll try that scenario today on lin32. (Don't have mac.)
After updating JBDS from the update site the version stays the same
-------------------------------------------------------------------
Key: JBDS-1559
URL:
https://issues.jboss.org/browse/JBDS-1559
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Build
Affects Versions: 4.0.0.CR2
Environment: Mac OS X 10.6 Snow Leopard
jbdevstudio-eap-macosx-cocoa-4.0.0.v201012070137R-H33-Beta2.jar
jbdevstudio-macosx-cocoa-4.0.0.v201012070137R-H33-Beta2.jar
Update site
http://reports.qa.atl.jboss.com/binaries/RHDS/updates/development/4.0.0.C...
Reporter: Martin Malina
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 4.0.0.GA
Attachments: Screenshot-JBDS-beta2-after-update-to-CR2.png,
Screenshot-JBDS-beta2-before-update.png,
Screenshot-select-features-not-found-automatically.png
When I install JBDS 4.0.0 Beta2 and then upgrade to CR2 using the CR2 update site, after
restarting JBDS the version in the splash screen as well as in File -> About still says
4.0.0 Beta2.
I believe the version should be updated. Correct me if I'm wrong.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira