[ https://jira.jboss.org/browse/JBIDE-6537?page=com.atlassian.jira.plugin.s... ] Darryl Miles commented on JBIDE-6537: ------------------------------------- The update URL provided (on IRC) doesn't work and doesn't look correct to me. So there appears to be no 3.2 release from my point of view. http://downloads.jboss.org/jbosstools/builds/nightly/3.2.helios/ is not a valid update site. I am looking for a single URL I can setup in Helios to install some version of JBT (supported or not). I'm not sure why Seam tools is not supported, on the basis that Helios is backwardly compatible with Galileo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6537?page=com.atlassian.jira.plugin.s... ] Darryl Miles commented on JBIDE-6537: ------------------------------------- Well are you already know since making your last comment in JIRA the important URL http://downloads.jboss.org/jbosstools/builds/nightly/3.2.helios/jbosstool... is broken (as per my previous comment). Yes even if 3.1.x is not being fixed with regards to this bug report, please consider the point being made when it comes to setting the version for the 3.2.x and future releases of JBT. There is no shame with running plugins designed for a pervious generation of Eclipse (Galileo in this case) with the current generation of Eclipse (Helios in this case) until such time that the GA version of the Helios release is ready. We understand we won't have any new Helios features integrated but we do expect it to work with Helios (even if its not officially supported). There is also no shame in citing the Eclipse platform as "letting JBT down" with regards to the Eclipse project goals to do with major/minor/patchlevel incremental changes - if eclipse.org break something. Your presumption has to be on the side of the overall compatibility goals with version numbering. This means using "[3.4.4,5)" in the case of com.ibm.icu here (for JBT 3.1.x), possibly moving up the lower limit for the JBT 3.2.x releases to "[4.2,5)". So please don't be scared on putting faith into the eclipse.org compatibility goals, you should expect minor number version changes of dependant plugins to just work and therefore configure your pre-requisites accordingly. This isn't my first bug report filed with JBT on just this kind of problem (to do with version settings). Also update sites are no use unless they are exploded on a URL, I'm done with running arround managing eclipse plugins from multiple sources/ZIPs/etc..., downloading, messing up, reinstalling; have spent far too much of my life dealing with that, its obviously what the problems (with the system) are but nobody has been able to fix them in the 6 years I've been following eclipse. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6537?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen resolved JBIDE-6537. ---------------------------------------- Resolution: Rejected Sorry, but there is simply no way to make plugins that work on both helios and Galileo when you depend provisional API as we do in certain areas. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira