[News.eclipse.technology.packaging] Custom distros for private use?

[Aaron Siri <aaron.siri@xxxxxxx>]

I'm attempting to use the EPP features for creating a custom distro for 
use within my company.  It is mainly a version of Eclipse with the 
plugins we need already installed and ready to go.  I have a few questions:

1. Is creating custom distros for private (local) use an expected use of 
EPP?

2. Which versions of Eclipse are expected to be in the rootFileFolder? 
The RCP versions?  SDK?  I don't want to have a mirror of the entire 
eclipse.org downloads and am wondering what I need for EPP to build bundles.

3. Are non-eclipse.org update sites supported?  (I was having problems 
pulling a feature from a non eclipse.org site and want to make sure EPP 
wasn't hardwired to work with eclipse.org.)

4. (This may be related to question 2 above)  I've created a 
configuration file and, using the CVS version of EPP as described in 
"How to build a package locally" it seems to get through a lot of the 
packaging process until it gets to the "Building configured 
application..." step.  All I see is (via an ant target):

>      [java] Building configured application...
>      [java]   Configuration files taken from /home/aaronsi/workspace/packagerConfiguration.
>      [java]   The application will be built in /home/aaronsi/workspace.

at which point it dies silently.  Any idea on what should be happening 
next or what I'm doing wrong?  I have the SDK and RCP eclipse packages 
in the rootFileFolder.

Thanks for any info.

-Aaron