[ https://issues.jboss.org/browse/JBDS-1559?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-1559: ---------------------------------- Need steps to repro. Was the com.jboss.jbds.product.feature feature selected for update? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1559?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-1559: ----------------------------- Attachment: Screenshot-JBDS-beta2-before-update.png Screenshot-JBDS-beta2-after-update-to-CR2.png Screenshot-select-features-not-found-automatically.png screenshots -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1559?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-1559 at 2/9/11 3:40 PM: ---------------------------------------------------------- 1. install jbdevstudio-eap-linux-gtk-4.0.0.v201012070137R-H33-Beta2 !Screenshot-JBDS-beta2-before-update.png! 2. add http://reports.qa.atl.jboss.com/binaries/RHDS/updates/development/4.0.0.C... to avail sites. 3. Help > Check for updates. Install offered updates. Restart. 4. Help > install new software... Browse the site. Select the omitted features. !Screenshot-select-features-not-found-automatically.png! 5. After restart, the Help > About shows that the JBDS product feature has in fact been updated. !Screenshot-JBDS-beta2-after-update-to-CR2.png! was (Author: nickboldt): 1. install jbdevstudio-eap-linux-gtk-4.0.0.v201012070137R-H33-Beta2 !Screenshot-JBDS-beta2-before-update.png! 2. add http://reports.qa.atl.jboss.com/binaries/RHDS/updates/development/4.0.0.C... to avail sites. 3. Help > Check for updates. Install offered updates. Restart. 4. Help > install new software... Browse the site. Select the omitted features. !Screenshot-select-features-not-found-automatically.png! !Screenshot-JBDS-beta2-after-update-to-CR2.png! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1559?page=com.atlassian.jira.plugin.... ] Martin Malina reopened JBDS-1559: --------------------------------- Assignee: Max Rydahl Andersen (was: Nick Boldt) Max, do you think it's ok that the product feature package won't get updated automatically? I certainly don't agree with the resolution "cannot reproduce", but if you think that being able to upgrade the package manually is good enough, then feel free to resolve this issue again. But in that case the additional step needed should be mentioned somewhere in the documentation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1559?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-1559: ------------------------------------- Hi Denis, "using old update site". What do you mean by that? I was using the CR2 update site. At that time it was the newest available. Do you think this problem no longer appears with CR3? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1559?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-1559 at 2/10/11 11:58 AM: ------------------------------------------------------------ Maybe we should be looking at updating an old product build (CR2) 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.) was (Author: nickboldt): 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.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1559?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-1559: ---------------------------------- Additional test using techpreview site works fine: 1. Install BPEL from CR1 site: http://devstudio.jboss.com/updates/4.0/staging/techpreview/ 2. Restart. Add CR3 site: http://reports.qa.atl.jboss.com/binaries/RHDS/updates/development/4.0.0.C... 3. Check for updates, install CR3 version. Restart. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1559?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-1559 at 2/10/11 12:46 PM: ------------------------------------------------------------ Using Denis' product build update site (623M) instead of the smaller JBDS .updatesite build site (224M, contains no Eclipse.org stuff) [1]: 1. download jbdevstudio-product-linux-gtk-4.0.0.v201102031426R-H148-CR2.jar 2. java -jar jbdevstudio-product-linux-gtk-4.0.0.v201102031426R-H148-CR2.jar; install into /home/nboldt/jbdevstudio-product-linux-gtk-4.0.0.v201102031426R-H148-CR2 3. start it up, use default workspace location. Size on disk: 427M jbdevstudio-product-linux-gtk-4.0.0.v201102031426R-H148-CR2 4. Window > Preferences > Install/Update > Available Software Sites > add *CORRECTED* http://reports.qa.atl.jboss.com/binaries/RHDS/builds/staging/devstudio-4.... > OK 5. Help > Check for updates 6. Select single all-in-one JBDS feature, com.jboss.jbds.all, for update. 7. After restart, splash looks good, Help > About shows "CR3", etc. Size on disk now: 534M jbdevstudio-product-linux-gtk-4.0.0.v201102031426R-H148-CR2 [1] http://reports.qa.atl.jboss.com/binaries/RHDS/updates/development/4.0.0.C... was (Author: nickboldt): Using Denis' product build update site (623M) instead of the smaller JBDS .updatesite build site (224M, contains no Eclipse.org stuff) [1]: 1. download jbdevstudio-product-linux-gtk-4.0.0.v201102031426R-H148-CR2.jar 2. java -jar jbdevstudio-product-linux-gtk-4.0.0.v201102031426R-H148-CR2.jar; install into /home/nboldt/jbdevstudio-product-linux-gtk-4.0.0.v201102031426R-H148-CR2 3. start it up, use default workspace location. Size on disk: 427M jbdevstudio-product-linux-gtk-4.0.0.v201102031426R-H148-CR2 4. Window > Preferences > Install/Update > Available Software Sites > add -http://reports.qa.atl.jboss.com/binaries/RHDS/updates/development/4.0.0.CR3/all/repo/- http://reports.qa.atl.jboss.com/binaries/RHDS/builds/staging/devstudio-4.... > OK 5. Help > Check for updates 6. Select single all-in-one JBDS feature, com.jboss.jbds.all, for update. 7. After restart, splash looks good, Help > About shows "CR3", etc. Size on disk now: 534M jbdevstudio-product-linux-gtk-4.0.0.v201102031426R-H148-CR2 [1] http://reports.qa.atl.jboss.com/binaries/RHDS/updates/development/4.0.0.C... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1559?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-1559: ------------------------------------- So the conclusion is that it does not work and will not work when updating from Beta2, but it works fine when updating from CR2 to CR3, correct? Had I known it was not supposed to work from Beta2, I wouldn't have filed this JIRA in the first place. But I was originally asked to test that the update works when Beta2 is installed and then CR2/3 update site added and new updates are installed. I'm not the one to say if it should or shouldn't work from Beta2, so if you think it's fine it doesn't, then everything is fine :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1559?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-1559. ------------------------------ Resolution: Rejected Closing again, as I don't think we will ever be able to make a non-product build (Beta2) update to a product build due to conflicting base product IUs. And other than a few annoyed EA testers, who will have to download a full installer (343M) rather than being able to do a smaller update (107M), I don't think this will impact Actual Customers as they upgrade from 4.0 to 4.0.x. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1559?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-1559: ------------------------------------- ok, thanks for the clarification, Nick and Max. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira