| PDE Build with Packager [message #327398] |
Thu, 17 April 2008 11:03  |
Eclipse User |
|
|
|
Originally posted by: mike.aol.com
I am trying to structure an efficient headless build for our components which includes generating RCP packages and the pieces are not fitting together yet.
I am successfully building all the component jar files in one step using the feature builder (${eclipse.pdebuild.scripts}/build.xml). Next, I want to build the RCP package using the already created jar files. I *think* using the packager
(${eclipse.pdebuild.scripts}/package.xml). It fails in package.xml:generateAssembleScripts:
...org.eclipse.pde.build_3.3.0.v20070612\scripts\package.xml :46: Unable to find feature: foo.rcp_feature.
My main RCP feature was created here:
${vceBuildDir}/I.vce/foo.rcp_feature-vce.zip
I'm invoking package.xml this way:
<ant antfile="package.xml" dir="${eclipse.pdebuild.scripts}">
<property name="vceBuildDir" value="${vceBuildDir}" />
<property name="assemblyTempDir" value="${vceBuildDir}/jartmp" />
<property name="featurePaths" location="${vceBuildDir}/I.vce"/>
<property name="packagingInfo" location="${basedir}/configs/all-features-prod/packager" />
</ant>
My packager.properties file includes:
product = ${packagingInfo}/vce.product
baseDirectory = ${vceBuildDir}
filteredDependencyCheck=false
featureList = foo.rcp_feature
config=win32, win32, x86
normalizeWhilePackaging=true
prefilledTarget = true
componentFilter=*
workingDirectory = ${baseDirectory}/workingPlace
buildDirectory = ${workingDirectory}
downloadDirectory = ${baseDirectory}/toPackage
tempDirectory = ${baseDirectory}/temp
sourceFolder = ${downloadDirectory}
target = ${tempDirectory}/eclipse
buildId=vce
buildType=I
buildLabel=${buildType}.${buildId}
archivesFormat=win32, win32, x86 - antZip
archivePrefix=eclipse
collectingFolder=eclipse
packagingProperties = packaging.properties
Any pointers would be most welcome!
Thanks,
Mike Gering
|
|
|
| Re: PDE Build with Packager [message #327408 is a reply to message #327398] |
Thu, 17 April 2008 16:43  |
| Eclipse User |
|
|
|
The script generator (the call to eclipse.assembler in package.xml) is looking
for the features and plugins it wants on disk in the set of locations determined
by ${workingDirectory} and ${target}. ${target} can actually be a comma
separated list of directories.
The property ${featurePaths} is only used to give a value to ${target} (target =
${tempDirectory}/${featurePaths}) if it does not already have one. (And since
you give a value for target, featurePaths is ignored for you).
Given the properties you posted below, this comes down to
${vceBuildDir}/workingPlace, ${vceBuildDir}/temp/eclipse
All of your plugins and features must exist on disk in one of those locations.
You have defined "prefilledTarget = true", this means that your input zips have
already been extracted to those locations. This is probably not correct for
you. prefilledTarget is the same as skipMaps=true, skipFetch=true & skipUnzip=true.
What you want instead is just skipMaps=true and skipFetch=true. This will then
run the unzipper before the generator. I believe the unzipper is unzipping from
the ${downloadDirectory} into the ${tempDirectory}
(from ${vceBuildDir}/toPackage to ${vceBuildDir}/temp)
Since the archives generally have eclipse in the root, this populates the
${target} directory for you.
In your setup, it looks like you want to set downloadDirectory=${vceBuildDir}/I.vce
-Andrew
Mike Gering wrote:
> I am trying to structure an efficient headless build for our components
> which includes generating RCP packages and the pieces are not fitting
> together yet.
>
> I am successfully building all the component jar files in one step using
> the feature builder (${eclipse.pdebuild.scripts}/build.xml). Next, I
> want to build the RCP package using the already created jar files. I
> *think* using the packager (${eclipse.pdebuild.scripts}/package.xml). It
> fails in package.xml:generateAssembleScripts:
>
> ...org.eclipse.pde.build_3.3.0.v20070612\scripts\package.xml :46:
> Unable to find feature: foo.rcp_feature.
>
> My main RCP feature was created here:
> ${vceBuildDir}/I.vce/foo.rcp_feature-vce.zip
>
> I'm invoking package.xml this way:
> <ant antfile="package.xml" dir="${eclipse.pdebuild.scripts}">
> <property name="vceBuildDir" value="${vceBuildDir}" />
> <property name="assemblyTempDir" value="${vceBuildDir}/jartmp" />
> <property name="featurePaths" location="${vceBuildDir}/I.vce"/>
> <property name="packagingInfo"
> location="${basedir}/configs/all-features-prod/packager" />
> </ant>
>
> My packager.properties file includes:
> product = ${packagingInfo}/vce.product
> baseDirectory = ${vceBuildDir}
> filteredDependencyCheck=false
> featureList = foo.rcp_feature
> config=win32, win32, x86
> normalizeWhilePackaging=true
> prefilledTarget = true
> componentFilter=*
> workingDirectory = ${baseDirectory}/workingPlace
> buildDirectory = ${workingDirectory}
> downloadDirectory = ${baseDirectory}/toPackage
> tempDirectory = ${baseDirectory}/temp
> sourceFolder = ${downloadDirectory}
> target = ${tempDirectory}/eclipse
> buildId=vce
> buildType=I
> buildLabel=${buildType}.${buildId}
> archivesFormat=win32, win32, x86 - antZip
> archivePrefix=eclipse
> collectingFolder=eclipse
> packagingProperties = packaging.properties
>
> Any pointers would be most welcome!
>
> Thanks,
> Mike Gering
|
|
|
| Re: PDE Build with Packager [message #327424 is a reply to message #327408] |
Fri, 18 April 2008 09:16 |
| Eclipse User |
|
|
|
Originally posted by: mike.aol.com
Andrew,
Thanks for the prompt and thorough explanation. I have it working better
and can hopefully overcome the remaining little problems.
Mike
|
|
|
Powered by
FUDForum. Page generated in 0.07374 seconds
Home