Here is an "umbrella" issue to track related use cases.
On 04/27/2012 06:27 PM, Mickael Istria wrote:
Hi all,
As you may know, we leverage Target Platform (TP) at build-time to set
up a build path. A TP is basically a list of dependencies we allow for
build to perform. TP are also usable at dev-time in PDE and guarantees
what you can depend on when you write a plugin. For example, if you
depend on something that is not part of your TP, you'll see some
errors for unresolved bundles.
The next step for this Target Platforms would the *you, developers,
use these target platforms in PDE*. Then we would all ensure we depend
on the same stuff at dev-time and build-time, and it would prevent
some synchronization errors between what you require, and what the TP
contain.
You can use TP by importing them into your workspace (checkout
build/target-platform folder), and then enable them with Window >
Preferences > Plugin Development > Target Platform. We already
identified some pitfalls with current TP, but we'll work on making
them more usable for developers. Please report your ideas in JIRA on
how to improve target platforms so that you could use them too. Here
are some first ideas, please contribute to these ideas and raise new ones.
https://issues.jboss.org/browse/JBIDE-11688
https://issues.jboss.org/browse/JBIDE-11689
https://issues.jboss.org/browse/JBIDE-11690
Thanks,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev