[ https://jira.jboss.org/jira/browse/JBIDE-5898?page=com.atlassian.jira.plu... ] Jiri Peterka updated JBIDE-5898: -------------------------------- Component/s: Build/Releng Fix Version/s: 3.1.0.GA Affects Version/s: 3.1.0.CR2 -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5898?page=com.atlassian.jira.plu... ] Jiri Peterka commented on JBIDE-5898: ------------------------------------- When Jboss Tools SDK Feature is removed from installation, there are BPEL editor conflicts, see screenshot 2 -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5898?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-5898: ----------------------------------- To solve the bpel conflict, you have to install the bpel SDK on top of the existing bpel SDK. You cannot simply update the runtime w/o updating the SDK feature. This is p2 being p2 and there's nothing that we can do from the release side of things to fix this. Alternatively, uninstall the existing BPEL SDK feature, then install the new BPEL runtime feature. To solve the jbpm issue, uninstall the old jbpm features before installing the new version. This problem arises because of the way the features are encoded to not permit 4.3 to be a valid update for 4.0, and the fragile dependency of jbpm3 and jbpm4 on their jbpm.common feature. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5898?page=com.atlassian.jira.plu... ] Nick Boldt updated JBIDE-5898: ------------------------------ Attachment: install-cr1-Screenshot-0.png install-cr1-Screenshot-1.png install-cr1-Screenshot-2.png -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5898?page=com.atlassian.jira.plu... ] Nick Boldt resolved JBIDE-5898. ------------------------------- Resolution: Cannot Reproduce Bug Cannot reproduce. Here's what I did: 1. Start a fresh Eclipse on linux 32, with openJDK6. #!/bin/bash workspace=/home/nboldt/eclipse/workspace-clean35 target=/home/nboldt/eclipse/35clean #eclipse=eclipse-SDK-3.5.1-linux-gtk.tar.gz #eclipse=eclipse-jee-galileo-SR1-linux-gtk.tar.gz eclipse=eclipse-SDK-M20100120-0800-linux-gtk.tar.gz if [[ $1 ]]; then echo "Wipe $target/eclipse and $workspace ..." rm -fr $target/eclipse $workspace echo "Unpack $eclipse ..." tar xzf $eclipse fi export GDK_NATIVE_WINDOWS=true #./eclipse/eclipse -clean -showLocation -data $workspace -consolelog -console -vm /opt/jdk1.5.0_19/bin/java -vmargs -Xms128M -Xmx256M -XX:PermSize=128M -XX:MaxPermSize=256M 2>&1 | tee "logs/eclipse.log.`date`.txt" ./eclipse/eclipse -clean -showLocation -data $workspace -consolelog -console -vmargs -Xms128M -Xmx256M -XX:PermSize=128M -XX:MaxPermSize=256M 2>&1 | tee "logs/eclipse.log.`date`.txt" 2. Download JBossTools-Update-3.1.0.v200912250601M-H198-CR1.zip (final CR1 build) 3. Download JBossTools-Update-3.1.0.v201002222217M-H271-CR2.zip (latest CR2 build) 4. Add H198-CR1 zip to Eclipse and select the following features to be installed: * JBoss Tools * JBoss BPEL Editor (just this feature) * JBoss Tools jBPM Tools (whole category) * JBoss Tools SDK * JBoss BPEL Editor SDK * jBPM 3 Tools SDK * jBPM 4 Tools SDK See install-cr1-Screenshot-0.png See install-cr1-Screenshot-1.png See install-cr1-Screenshot-2.png 5. Restart when prompted; check install details to see what's installed. See install-cr1-Screenshot-3.png 6. Add H271-CR2 zip to Eclipse. 7. Help > Check for updates See update-cr2-Screenshot-0.png 8. Install updates. Restart when prompted. See update-cr2-Screenshot-1.png Closing as CANNOT REPRODUCE. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5898?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-5898: ----------------------------------- Jiri, the title of this JIRA is "jBPM conflicts..." m2eclipse support isn't relevant to that. Anyway, are you satisfied that there's a viable workaround here? Or are you suggesting there's a real issue still to fix? (Note that we cannot fix p2, since 3.5.2 is now final, and will GA tomorrow. We can only endure the situation provided to us by Eclipse and suggest improvements for 3.6 (due out in June).) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5898?page=com.atlassian.jira.plu... ] Jiri Peterka closed JBIDE-5898. ------------------------------- Assignee: Jiri Peterka (was: Nick Boldt) Verified in JBDS 3.0.0 CR2 184, Linux 32 -- 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