[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [pde-dev] Headless build changes in M4
|
The new allElements.xml file provides
a "defaultAssemble" target that will be called for each configuration
which removes the need to define individual "assemble.[feature].[os].[ws].[arch]"
targets. Together with 2 new properties "topLevelElementType"
and "topLevelElementId", the default template allElements.xml
is sufficient on its own so new setups don't actually need to copy it unless
they are adding customizations. The individual assemble targets can
still be defined if a particular configuration needs custom handling.
This new allElements.xml defines a property
"defaultAssemblyEnabled" which distinguishes it from the old
format. The generated assemble.[feature].all.xml script uses this
property as part of a macro to call the appropriate assemble target (either
the old assemble targets, the new default target, or a new custom target).
This change is supposed to be backward compatible and should even
work with the original customTargets.xml pattern that was used before the
allElements.xml file was introduced.
The second item is the introduction
of custom steps in the assembly/packaging phase. These are somewhat
analagous to the customTargets, or customBuildCallbacks. They provide
oppotunity for custom ant steps before and after jaring, and before the
final results are archived. This is based on the property "customAssembly"
which will be defined by default if the file ${builder}/customAssembly.xml
exists.
-Andrew
"Konstantin Komissarchik"
<kosta@xxxxxxx>
Sent by: pde-dev-bounces@xxxxxxxxxxx
01/03/2008 02:15 PM
|
Please respond to
"Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx> |
|
|
To
| <pde-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| [pde-dev] Headless build changes in
M4 |
|
Could someone provide more info regarding
the following item in M4 new and noteworthy? We have a headless build that
was working with M3 and is having issues with M4.
Greater simplification and customizability in headless
builds
Setting up a headless build has been simplified. A build
can be set up with only the single build.properties configuration file.
The allElements.xml file is not needed unless the added customization it
provides is desired.
PDE Build now also allows custom steps during the assembly
and packaging phase of a headless build. A template customAssembly.xml
script is provided with the available targets.
Thanks,
- Konstantin
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated entities,
that may be confidential, proprietary, copyrighted and/or legally privileged,
and is intended solely for the use of the individual or entity named in
this message. If you are not the intended recipient, and have received
this message in error, please immediately return this by email and then
delete it._______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev
