[jbosstools-issues] [JBoss JIRA] (JBIDE-17002) Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2

[ https://issues.jboss.org/browse/JBIDE-17002?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17002: ------------------------------------ OK, so long circular discussion aside, I see above and on the PR these comments: +1 from Fred, Max, Nick for inclusion of PDE feature -1 from Mickael for inclusion of PDE feature * Suggestion to change the URL in the connector to http://www.eclipse.org/downloads/java8/ (which doesn't mention m2e 1.4.1 but it's better than what I had), so +1 * Suggestion to rename the category from Patches to Java 8 * Suggestion to either list the new Java 8 category after maven or under maven. I assume Max meant *after* since we can't nest categories. I would prefer to keep the new category at the top since it's something EVERYONE is going to want, and it showcases immediately that there's something new in Central and we're just as good as STS (who also added this) [1] http://dist.springsource.com/snapshot/TOOLS/java8/e43 * Suggestion to use "osgi" instead of "pde" in order to "reduce the use of acronyms". Because Max things "osgi" is not an acryonym, but PDE is. -1, would rather use the phrase "plugin development" than "osgi", if the goal is reduction of acroyms. Also don't see the need to have "Adding" or "for Eclipse" in the description since well, it's going to install features into Eclipse which by definition adds something to Eclipse. Thus: {quote} Description: Java 8 support for java, web, plugin and maven development. Name: Java 8 Support {quote} * Clarification to the URL [1] used to source the bits: No, that URL is not temporary. It's the mirror I created of the three upstream sites. It was decided to NOT include this update in the Central target platform, so I created a simple mirror instead. If you don't like the lengthy (but detailed) URL, I can shorten it, perhaps to just "/kepler/java8/" ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira