Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 77134

Summary:	Would like to build without checkout
Product:	[Eclipse Project] PDE	Reporter:	Chris Longfield <clongfield>
Component:	Build	Assignee:	pde-build-inbox <pde-build-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	3.0.1
Target Milestone:	3.1
Hardware:	All
OS:	All
Whiteboard:

Description Chris Longfield

2004-10-27 12:50:23 EDT

It would be nice to be able to do a automated pde build without the checkout
step.  When a checkout is required, it means that the code you want to compile
has to be checked in.  This prevents us from enforcing the rule that the CVS
head must compile - for if we have to check it in before it compiles, we can't
be sure that it will.

I'm fine with a task that copies stuff out of the build tree using a map
file-like structure to find everything relative to some root directory and put
it in a more restrictive structure like the current eclipse.fetch task does.

I tried to do this myself using standard ant tasks, but one really needs to get
in and exampine the features to get the recursion that allows you to copy over
all the needed bits.  I would guess that this code is already pretty much in the
fetch task and could be applied to a copy rathed than a checkout.  If I get
time, I'll look myself.

Comment 1 Pascal Rapicault

2004-10-29 10:00:16 EDT

If you are able to setup your source in the following way (similar to an 
eclipse install without the version numbers):
 features/
   feature_bar/
     source
   feature_foo/
     sourc
 plugins/
   p1/
   p2/

Then change the main target in plugins/org.eclipse.pde.build/scripts/build.xml 
and comment out the fetch phase.

This requirement is somehow similar to bug 34757 since you want to get the 
source from somewhere else.

Comment 2 Chris Longfield

2004-11-01 14:09:47 EST

This should be doable, but there is no recursive mechanism to go get the
apropriate plugins/features from the source area and put them into the build
area.  I guess it's not too hard to just do all of them, and then let the
building step recursively pull in what is appropriate from the setup area.

Comment 3 Pascal Rapicault

2004-11-05 17:36:57 EST

It seems that what you want goes along the line of what is required by bug 
34757. Indeed for task we use, fetching code from the a local file system or 
fetching from a repository is not any different.
It may just require an enhancement so map files can refer to local files.

Comment 4 Pascal Rapicault

2005-05-19 17:43:53 EDT

This has been fixed a little while ago.
We don't fetch, if skipFetch is specified.