[jboss-user] [JBoss Tools Development] - JBoss Tools Target Platform Provisioning (or, how to resolve missing dependencies when compiling JBoss Tools)

Nick Boldt do-not-reply at jboss.com
Fri Aug 27 11:53:28 EDT 2010

Nick Boldt [http://community.jboss.org/people/nickboldt] created the document:

"JBoss Tools Target Platform Provisioning (or, how to resolve missing dependencies when compiling JBoss Tools)"

To view the document, visit: http://community.jboss.org/docs/DOC-15755

*+This document is a work in progress and subject to change.+*

In order to build JBoss Tools in your workspace (or on your local machine, if not in Eclipse), you need to have its dependencies available. There are a number of ways to accomplish this, depending on your needs and how much manual effort you'd like to expend.

*1. Build Parent Pom + Target Platform With Tycho + Maven 3*

Build the parent pom [1] + target platform [2], then build against that with maven3 (commandline) or m2eclipse (and don't use PDE anymore when building in Eclipse)

  cd /tmp; \
  svn co  http://anonsvn.jboss.org/repos/jbosstools/trunk/build/ http://anonsvn.jboss.org/repos/jbosstools/trunk/build; \
  cd /tmp/build/parent; \
  mvn3 clean install


  cd /tmp; \
  svn co  http://anonsvn.jboss.org/repos/jbosstools/trunk/tests; http://anonsvn.jboss.org/repos/jbosstools/trunk/tests; \
  cd /tmp/tests; \
  mvn3 clean install


This is how the Hudson builds run - compile the parent (which compiles the target platform), then build whatever component(s) you then want.

If you have the entire JBoss Tools tree on disk, you can also do multi-component builds even simpler like this:

  cd /tmp; \
   svn co  http://anonsvn.jboss.org/repos/jbosstools/trunk/ http://anonsvn.jboss.org/repos/jbosstools/trunk; \
   cd /tmp/trunk/build/component; \
  mvn3 clean install -f seam.xml

*2. Load Target Platform in Eclipse*

Attempt to get the target platform file [2] to load in Eclipse, then click 'set as target platform' in the top right corner of the editor when it's open in the Target Platform editor. This should resolve everything in the target, and install it into your Eclipse. When it works. The editor is kinda flaky.

When it completes (and it may take a significant amount of time during which your Eclipse may be unstable / unusable), you should have everything you need to develop JBoss Tools.

*3. Manual Install from Update Sites (p2 Repos)*

Read through either [1] or [2] and install - by hand - what you need from the various update sites against which we install. The sites are listed in two places [1], [2]. The target platform file lists the features/plugins you need to include when installing; the parent pom only lists the update sites. YMMV.

*4. Manually Download and Unpack Runnable Zips*

Pull down the SDKs/runtime zips [3] and dump them into your eclipse's dropins/ folder. This is the way the old "uberbuilder" works, and is deprecated, but should still work.

[1]  http://anonsvn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml http://anonsvn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml
[2]  http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/e36-wtp32.target http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/e36-wtp32.target
[3]  http://download.jboss.org/jbosstools/requirements/helios/README.txt http://download.jboss.org/jbosstools/requirements/helios/README.txt,  http://download.jboss.org/jbosstools/requirements/helios/ http://download.jboss.org/jbosstools/requirements/helios/ (GWT is missing, but the collection should otherwise be complete)


Comment by going to Community

Create a new document in JBoss Tools Development at Community
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20100827/0578fd54/attachment-0001.html 

More information about the jboss-user mailing list