For the past few weeks I've been using a modified maven-embedder to allow for AJDT & Modelling use within Eclipse Ganymede.
I've created a branch at q4e to show what I've done
https://q4e.googlecode.com/svn/branches/maven-embedder-2.1.0.659801c One thing we need to address is how do we create an
eclipse.org update site that references the q4e update site for content, so that we don't include the maven-embedder into the /features/ and /plugins/ on the
eclipse.org update site.
I have a solution for that too. :-)
(But only for Eclipse Ganymede users, I rely on P2.)
This is how it's set up.
1) Generate the q4e side update site with the maven-embedder update within it.
2) Generate the p2 metadata on the q4e side.
3) Generate the IAM side update site.
4) Generate the p2 metadata on the IAM side.
5) Manually Update the IAM update site's content.xml to include the following lines ...
<references size='2'>
<repository url="" href="http://dev.eclipse.org/svnroot/technology/org.eclipse.iam/trunk/updatesite" target="_blank">http://dev.eclipse.org/svnroot/technology/org.eclipse.iam/trunk/updatesite' type='0' options='0'/>
<repository url="" href="http://dev.eclipse.org/svnroot/technology/org.eclipse.iam/trunk/updatesite" target="_blank">http://dev.eclipse.org/svnroot/technology/org.eclipse.iam/trunk/updatesite' type='1' options='0'/>
<repository url="" href="http://q4e.googlecode.com/svn/trunk/updatesite-dev/" target="_blank">http://q4e.googlecode.com/svn/trunk/updatesite-dev/' type='0' options='1'/>
<repository url="" href="http://q4e.googlecode.com/svn/trunk/updatesite-dev/" target="_blank">http://q4e.googlecode.com/svn/trunk/updatesite-dev/' type='1' options='1'/>
</references>
What this does, is add a reference to the metadata repository and artifact repository on the q4e side, and also specify in the options that it is enabled. This will in turn cause P2 to add all 4 repositories listed and search them for dependencies.
- Joakim Erdfelt
