| headless product build creating different folders for each config [message #1864] |
Sun, 20 April 2008 05:47  |
Eclipse User |
|
|
|
I'm using the headless product build (on 3.4m6) and want to have it
create a different folder for each configuration, and do multiple
configurations in the same build step for a single product.
When I look at the generated assembly script, it very nicely assembles
everything to a different folder, and then (I am using the "folder"
output) it copies everything back to the parent folder and deletes the
per-configuration folder. So at the end, I get a single folder which
has the union of all of my configurations.
It would be nice if it just left is alone, as what it emits is just what
I want.
Here is my build.properties file:
topLevelElementType = feature
topLevelElementId = com.oaklandsw.transform.feature.product0
product=/com.oaklandsw.transform.feature.product0/transform. product
collectingFolder=transform0
archivePrefix=${collectingFolder}
runPackager=true
assemblyTempDir=${builder}/buildOutput
defaultAssemblyEnabled=true
If I export the same product using the product wizard it also creates a
folder per platform (when I select multiple platforms - actually it
fails to export platforms that are not the platform I'm running against
because it can't find the plugins for those, but I think that's a p2/pde
issue that's already known). What the export does is exactly what I want.
|
|
|
| Re: headless product build creating different folders for each config [message #1893 is a reply to message #1864] |
Mon, 21 April 2008 13:50  |
| Eclipse User |
|
|
|
Francis,
Unfortunately there is an outstanding bug about this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=143243
Basically, when using the "folder" output, you can only do 1 config at a time.
If you were to use an archive output (zip/tar) then the separate configs would
be done properly.
The export works because it only builds 1 config at a time, and essentially does
n exports when n configs are selected.
If you want separated folders at the end, one workaround would be to use zips or
tars and then add a custom step in the customTargets.xml postBuild target that
unzips the archives into separate folders.
-Andrew
Francis Upton wrote:
> I'm using the headless product build (on 3.4m6) and want to have it
> create a different folder for each configuration, and do multiple
> configurations in the same build step for a single product.
>
> When I look at the generated assembly script, it very nicely assembles
> everything to a different folder, and then (I am using the "folder"
> output) it copies everything back to the parent folder and deletes the
> per-configuration folder. So at the end, I get a single folder which
> has the union of all of my configurations.
>
> It would be nice if it just left is alone, as what it emits is just what
> I want.
>
> Here is my build.properties file:
>
> topLevelElementType = feature
> topLevelElementId = com.oaklandsw.transform.feature.product0
> product=/com.oaklandsw.transform.feature.product0/transform. product
> collectingFolder=transform0
> archivePrefix=${collectingFolder}
> runPackager=true
> assemblyTempDir=${builder}/buildOutput
> defaultAssemblyEnabled=true
>
> If I export the same product using the product wizard it also creates a
> folder per platform (when I select multiple platforms - actually it
> fails to export platforms that are not the platform I'm running against
> because it can't find the plugins for those, but I think that's a p2/pde
> issue that's already known). What the export does is exactly what I want.
|
|
|
| Re: headless product build creating different folders for each config [message #566046 is a reply to message #1864] |
Mon, 21 April 2008 13:50 |
| Eclipse User |
|
|
|
Francis,
Unfortunately there is an outstanding bug about this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=143243
Basically, when using the "folder" output, you can only do 1 config at a time.
If you were to use an archive output (zip/tar) then the separate configs would
be done properly.
The export works because it only builds 1 config at a time, and essentially does
n exports when n configs are selected.
If you want separated folders at the end, one workaround would be to use zips or
tars and then add a custom step in the customTargets.xml postBuild target that
unzips the archives into separate folders.
-Andrew
Francis Upton wrote:
> I'm using the headless product build (on 3.4m6) and want to have it
> create a different folder for each configuration, and do multiple
> configurations in the same build step for a single product.
>
> When I look at the generated assembly script, it very nicely assembles
> everything to a different folder, and then (I am using the "folder"
> output) it copies everything back to the parent folder and deletes the
> per-configuration folder. So at the end, I get a single folder which
> has the union of all of my configurations.
>
> It would be nice if it just left is alone, as what it emits is just what
> I want.
>
> Here is my build.properties file:
>
> topLevelElementType = feature
> topLevelElementId = com.oaklandsw.transform.feature.product0
> product=/com.oaklandsw.transform.feature.product0/transform. product
> collectingFolder=transform0
> archivePrefix=${collectingFolder}
> runPackager=true
> assemblyTempDir=${builder}/buildOutput
> defaultAssemblyEnabled=true
>
> If I export the same product using the product wizard it also creates a
> folder per platform (when I select multiple platforms - actually it
> fails to export platforms that are not the platform I'm running against
> because it can't find the plugins for those, but I think that's a p2/pde
> issue that's already known). What the export does is exactly what I want.
|
|
|
Powered by
FUDForum. Page generated in 0.02837 seconds
Home