[
https://issues.jboss.org/browse/JBIDE-12307?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12307:
----------------------------------------
Have you respun either the JBT or JBDS TPs with clean=true since this
change was implemented ?
I remember I respun TP and I *think" I set clean=true... I should respin again to
ensure.
won't removing refs to unversioned included features/plugins
cause the TP to no longer include Xulrunner and m2e-wtp
Those IUs were in "includeBundles". This flag is ignored at buid-time by Tycho,
and cause trouble at dev-time in PDE. So this removal doesn't affect the TP badly.
Xulrunner is provided on our composite site, no need to have it in this TP. About m2e-wtp,
it is a workaround. m2e-wtp should become a "normal" IU when a release is
available.
unified.target appears broken
-----------------------------
Key: JBIDE-12307
URL:
https://issues.jboss.org/browse/JBIDE-12307
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: target-platform
Affects Versions: 3.4.x
Environment: Either installed Eclipse Indigo or Juno
Reporter: Paul Richardson
Assignee: Nick Boldt
Fix For: 3.4.0.M1
Attachments: jbds-target-46269.png, multiple-target-46269.png,
unified-target-46269.png
Use of the unified.target fails as PDE target platform for both Indigo and Juno.
*Indigo IDE*
Use of the trunk version of unified.target results in org.lucene.core 3.5-4 not being
found, which is true since only version 2.91 is available in the update site -
http://download.jboss.org/jbosstools/updates/target-platform_3.4.juno.SR0...
*Juno IDE*
Use of the trunk version of unified.target results in package org.xmlpull.mxp1 not being
found as a requirement of XStream.
Both errors imply an incomplete target platform but does the fact that they are different
errors imply that plugins in the installed IDE are assumed to be there?
Should it not be possible to take an eclipse Indigo and develop against a Juno target
platform?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira