[jbosstools-issues] [JBoss JIRA] (JBIDE-12307) unified.target appears broken
[
https://issues.jboss.org/browse/JBIDE-12307?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12307:
----------------------------------------
unified.target is preferred to multiple.target because it resolves deps much faster (1
aggregated site vs 7 sites in composite).
IMHO, as discussed in JBIDE-11734 , multiple.target is "only" useful to create
the aggregated target site. It's not really intended to end-users, but it's more a
trick we use in our TP creation process.
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
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