[ https://jira.jboss.org/jira/browse/JBDS-1004?page=com.atlassian.jira.plug... ] Denis Golovin reassigned JBDS-1004: ----------------------------------- Assignee: Denis Golovin -- 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/JBDS-1004?page=com.atlassian.jira.plug... ] Jeff updated JBDS-1004: ----------------------- Attachment: Screen shot 2009-12-21 at 10.10.23 AM.png screen shot of eclipse version -- 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/JBDS-1004?page=com.atlassian.jira.plug... ] Denis Golovin commented on JBDS-1004: ------------------------------------- I assume you would like update 2.1.0.GA to last available JBDS. I have installed 2.1.0.GA and have the same error now. It can be solved by disabling http://download.jboss.org/jbosstools/updates/stable update site. Then you can add last update site for JBDS 3.0.0.CR1. Elipse will show you all it is going to update without errors, but during update you'll get errors like: Error Mon Dec 21 13:13:41 PST 2009 No repository found containing: org.mortbay.jetty.util.source/osgi.bundle/6.1.15.v200905182336 Error Mon Dec 21 13:13:41 PST 2009 No repository found containing: org.mortbay.jetty.util/osgi.bundle/6.1.15.v200905182336 which seems to be related to galileo update site. -- 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/JBDS-1004?page=com.atlassian.jira.plug... ] Denis Golovin commented on JBDS-1004: ------------------------------------- According http://dev.eclipse.org/newslists/news.eclipse.newcomer/msg29264.html there is no way to update eclipse 3.4.X to 3.5.x thus all update sites that contains updates required 3.5.x should be disabled. There were no updates for eclipse 3.4.2 since last jbds release and for other tools like WTP/DTP/GEF/ETC. Which means all update sites should disabled except JBDS. After that, I was able to update JBDS 2.1.0.GA to last stable JBDS 2.1.1.GA release. -- 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/JBDS-1004?page=com.atlassian.jira.plug... ] Denis Golovin updated JBDS-1004: -------------------------------- Component/s: Build -- 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/JBDS-1004?page=com.atlassian.jira.plug... ] Denis Golovin commented on JBDS-1004: ------------------------------------- That's related to WTP update site. Eclipse will pick up latest version of WTP. It requires eclipse 3.5 and it will be picked up through the associated update sites. -- 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/JBDS-1004?page=com.atlassian.jira.plug... ] Nick Boldt commented on JBDS-1004: ---------------------------------- Denis, Max, I would argue that we need a new stable URL so that we don't end up breaking the JBT 3.0 / JBDS 2.1 folks by swapping the contents of /stable/ for the newer JBT 3.1 / JBDS 3.0 bits. Having a separate site means that the annual releases will never try to update themselves from the NEXT year's content; thus a product built on Eclipse 3.4 will never try to get updates for Eclipse 3.5. Once a product is deployed, we can't disable remotely what people have enabled/disabled in their Eclipse's list of update sites; nor can we change their feature.xml files to point at a different URL for automated updates. However, we can make sure that OUR update sites are designed to never overlap or break by replacing the content with an incompatible update site (ie., putting JBT 3.1 into /stable/ if JBT 3.0 expects it to have updates that depend on Eclipse 3.4, not 3.5). And we can encode our features so that they point to year-specific update sites (Ganymede vs. Galileo, Eclipse 3.4 vs. 3.5, JBT 3.0 vs. 3.1). Would you agree? I'm not sure what's the best URL to use... * use eclipse versioning: /updates/stable-3.5/ or /updates/stable/3.5/ or /updates/3.5/ or /updates/galileo/ * use JBDS versioning: /updates/stable-3.0/ or /updates/stable/3.0/ or /updates/3.0/ Personally, I like the simplest: /updates/3.0/ (Aside: plugins don't have update site references; it's their features' feature.xml files that state from where to be updated.) -- 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/JBDS-1004?page=com.atlassian.jira.plug... ] Max Rydahl Andersen updated JBDS-1004: -------------------------------------- Assignee: Nick Boldt (was: Max Rydahl Andersen) -- 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/JBDS-1004?page=com.atlassian.jira.plug... ] Nick Boldt updated JBDS-1004: ----------------------------- Workaround Description: Disable/delete update sites which are not compatible with current platform, such as those for Eclipse 3.5 / WTP 3.1 / JBT 3.1 / JBDS 3.0. Fix Version/s: (was: 3.0.0.CR2) Priority: Optional (was: Critical) Downgrading severity as workaround exists. -- 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