You can see an example of using the equinox zip in a build here:
dev.eclipse.org:/cvsroot/eclipse/pde-build-home/examples/org.eclipse.pde.build.examples.rcp.cloud.releng

It downloads the equinox repo, and puts it in base/zippedRepos, the 
build.properties specifies:
repoBaseLocation=${base}/zippedRepos
transformedRepoLocation=${base}/transformedRepos

This results in a call with the following:
        <p2.repo2runnable destination="${transformedRepoLocation}">
                <source dir="${repoBaseLocation}/" includes="*"/>
        </p2.repo2runnable>

To do this in 3.4, you will need the 3.5 p2 bundles.  You can make the 
repo2runnable call yourself and then you will also need to add 
repoBaseLocation to the pluginPath property.


Alternatively, for this specific case, we know that the runnable form of 
all the bundles in the equinox repo is actually a jar with the exception 
of the launcher fragments.  You can unzip the repo into some location 
seperate from your base, and add that location to your pluginPath 
property.  If you are using the launchers, you will need to unzip those as 
well

-Andrew



Pascal Rapicault/Ottawa/i...@ibmca 
Sent by: equinox-dev-boun...@eclipse.org
03/17/2009 09:06 AM
Please respond to
Equinox development mailing list <equinox-dev@eclipse.org>


To
Equinox development mailing list <equinox-dev@eclipse.org>
cc
Equinox development mailing list <equinox-dev@eclipse.org>, 
equinox-dev-boun...@eclipse.org
Subject
Re: [equinox-dev] Re: 3.5M6 missing eclipse directory






PDE has support for n - 2 but has never guaranteed forward compatibility. 
You can always try to run the p2.repo2runnable task to make the repo in a 
format against which you can run. 


Christian Campo ---03/17/2009 04:15:05 AM---So what do you do, if you use 
a 3.4 build process to build a 3.5 target ? which isnt so unusual....


From:

Christian Campo <christian.ca...@gmail.com>

To:

Equinox development mailing list <equinox-dev@eclipse.org>

Date:

03/17/2009 04:15 AM

Subject:

Re: [equinox-dev] Re: 3.5M6 missing eclipse directory



So what do you do, if you use a 3.4 build process to build a 3.5 target ? 
which isnt so unusual....

2009/3/16 Chris Aniszczyk <z...@eclipsesource.com> 
2009/3/16 Christian Campo <christian.ca...@gmail.com>
Some more stupid questions.....:-)

Ok so that .zip as I learned looks that way because it is "p2-ized". No 
idea how to tell the PDE Build to use it, but that explains it at least.

In 3.5M5, PDE Build added support to use p2 repos as a target:
     
http://download.eclipse.org/eclipse/downloads/drops/S-3.5M5-200902021535/eclipse-news-M5.html#PDE


See the 'repoBaseLocation' and 'transformedRepoLocation' properties.
 
Cheers,

-- 
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev



-- 
christian campo (gmail.com)_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

<<image/gif>>

<<image/gif>>

<<image/gif>>

<<image/gif>>

<<image/gif>>

<<image/gif>>

<<image/gif>>

<<image/gif>>

<<image/gif>>

_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Reply via email to