Right. I was hoping to avoid that question for now, but since you asked...
The main motivator for this version bump is that we are tentatively planning to convert facets api to use generics for 2.0. The PMC is going to be discussing this at tomorrow's meeting and more details about rollout/testing will follow after that. Since this would be a fairly significant "feature", a bump in the second digit seems appropriate by the Eclipse version convention. Consistent with the version convention, the change will be source and binary compatible with 1.4 and 5.0 clients (except for those clients who were very pessimistic about version ranges - which appears to be all of WTP). - Konstantin ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chuck Bridgham Sent: Monday, February 05, 2007 12:49 PM To: General discussion of project-wide or architectural issues. Subject: Re: [wtp-dev] Incrementing plugin version for facet.core and facet.uiplugins Hi Konstantin, I'm sure these changes are compatible, but can you explain in more detail what changes require you to upgrade the second digit? We'll be happy to upgrade dependent versions, but would be more comfortable knowing the changes in store. Thanks - Chuck Rational Java Enterprise Tooling Team Lead IBM Software Lab - Research Triangle Park, NC Email: [EMAIL PROTECTED] Phone: 919-254-1848 (T/L: 444) "Konstantin Komissarchik" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 02/05/2007 02:37 PM Please respond to "General discussion of project-wide or architectural issues." <[email protected]> To "General discussion of project-wide or architectural issues." <[email protected]> cc Subject [wtp-dev] Incrementing plugin version for facet.core and facet.ui plugins I need to increment the version of org.eclipse.wst.common.project.facet.core and facet.ui plugins soon from 1.1.x to 1.2.0 to correctly reflect the type of work happening in these plugins for the 2.0 release. Before that change can be made, the referring plugins need to have their version ranges adjusted. At this point, range [1.1.0,1.2.0) is used which fails to match the new version. This affects both references to the facet.core and facet.ui plugins. In the case of the facet.core plugin, the range should be set as [1.1.0,2.0.0) since that plugin does not export any internal api. The facet.ui plugin does export internal api, so references to it should use [1.1.0,1.3.0). The following plugins are affected. Please let me know if you'd rather make this change to your plugins yourself. Otherwise, I will update these plugins in bulk in the next couple of days. org.eclipse.jst.common.frameworks org.eclipse.jst.common.project.facet.core org.eclipse.jst.ejb.ui org.eclipse.jst.j2ee org.eclipse.jst.j2ee.ejb org.eclipse.jst.j2ee.ejb.annotations.ui org.eclipse.jst.j2ee.ejb.annotations.xdoclet org.eclipse.jst.j2ee.jca org.eclipse.jst.j2ee.jca.ui org.eclipse.jst.j2ee.navigator.ui org.eclipse.jst.j2ee.ui org.eclipse.jst.j2ee.web org.eclipse.jst.j2ee.webservice org.eclipse.jst.j2ee.webservice.ui org.eclipse.jst.jsp.ui org.eclipse.jst.server.core org.eclipse.jst.server.generic.jboss org.eclipse.jst.server.generic.jonas org.eclipse.jst.server.generic.oc4j org.eclipse.jst.server.generic.weblogic org.eclipse.jst.server.tomcat.ui org.eclipse.jst.server.ui org.eclipse.jst.server.websphere.core org.eclipse.jst.servlet.ui org.eclipse.jst.ws org.eclipse.jst.ws.consumption org.eclipse.jst.ws.consumption.ui org.eclipse.jst.ws.creation.ui org.eclipse.wst.command.env org.eclipse.wst.common.emfworkbench.integration org.eclipse.wst.common.modulecore org.eclipse.wst.css.ui org.eclipse.wst.html.ui org.eclipse.wst.javascript.ui org.eclipse.wst.validation org.eclipse.wst.web org.eclipse.wst.web.ui - Konstantin _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
