Eclipse Community Forums: Plugin Development Environment (PDE) » Headless build contribute root files twice when p2.gathering=true

Home » Eclipse Projects » Plugin Development Environment (PDE) » Headless build contribute root files twice when p2.gathering=true

Show: Today's Messages :: Show Polls :: Message Navigator

Headless build contribute root files twice when p2.gathering=true [message #483318]

Tue, 01 September 2009 04:27

Patrick Roumanoff

Messages: 19
Registered: July 2009

Junior Member

Hi,

I had a pde headless build for a product with the JRE being contributed
through a feature and everything was working fine.

Now I want to enable p2 for this build, so I added p2.gathering=true to my
build.properties and after solving a few issues and defining an update
site for external dependencies I have a successful product build.

So far so good. But wait, now the zip is 30Mo bigger because the JRE is
included twice:
- once under the jre folder as it should be
- once under p2/org.eclipse.equinox.p2.core/cache/binary in a single file
called [feature name]_root.win32.win32.x86_1.0.0

I have tried manually removing the cache folder and the product seems to
be launching properly, I haven't try the run a p2 update yet.

So my questions are:
1) Is this file necessary?
2) How can I avoid generating this file?

thanks in advance,
Patrick.

Report message to a moderator

Re: Headless build contribute root files twice when p2.gathering=true [message #494091 is a reply to message #483318]

Thu, 29 October 2009 08:11

Urs Breu

Messages: 12
Registered: October 2009
Location: Switzerland

Junior Member

I am having the same issue.
Is there any way to clean the p2 download cache after executing the director call?

Report message to a moderator

Re: Headless build contribute root files twice when p2.gathering=true [message #494215 is a reply to message #494091]

Thu, 29 October 2009 15:25

Andrew Niefer

Messages: 990
Registered: July 2009

Senior Member

The cache is used when reverting to a previous install after upgrading.

Also, it is used if someone else points at your eclipse install and uses
it as a repository. If the cache is there, it is possible to point at
an existing install and fully re-create a new install of it.

If the cache is not there, then both of these will require downloading
artifacts from some other repository.

I don't know if there is a way to avoid having the cache in the first
place, but you can delete the cache during the build. The Eclipse SDK
itself used to delete the cache, but stopped doing that for 3.5 (see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=270508)

Use customAssembly.xml/pre.archive, something like
<target name="pre.archive">
<delete failonerror="false" includeEmptyDirs="true"
dir="${eclipse.base}/p2/org.eclipse.equinox.p2.core/cache"
/>
</target>

http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .pde.doc.user/tasks/pde_customization.htm

Urs Breu wrote:
> I am having the same issue.
> Is there any way to clean the p2 download cache after executing the
> director call?

Report message to a moderator