[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [pde-build-dev] maven-pde-plugin
|
Which build.properties are you talking about? The one in the plug-in or the
global one that sets up the build infrastructure (it usually sits next to a
customTargets.xml)
PaScaL
"Graham Leggett"
<minfrin@xxxxxxxx
> To
Sent by: pde-build-dev@xxxxxxxxxxx
pde-build-dev-bou cc
nces@xxxxxxxxxxx
Subject
[pde-build-dev] maven-pde-plugin
05/23/2007 07:01
AM
Please respond to
"Eclipse PDE
Build developers
list."
<pde-build-dev@ec
lipse.org>
Hi all,
I am in the process of trying to improve the maven pde plugin that wraps
the PDE headless build process, and have come up with some strange
behaviour that I cannot seem to find an explanation for.
I would like to somehow pass maven created environment variables into the
PDE ant build, and have modified the maven plugin to pass these variables
into the ant environment. So far this works - buried inside the reams of
output from the PDE build is a dump of the environment, and the maven
generated variables show up correctly.
However, if I try and embed one of these variables inside the
build.properties file, this variable has no effect.
Would it be possible for someone to share some light on what mechanism
might be supported to inject values into the build.properties file,
assuming passing variables to ant via -D don't work?
For example, from the build.properties files, ${pom.version} isn't
resolved even when passed to ant with -Dpom.version=4.0.0:
buildLabel=target/${buildType}.${buildId}-${pom.version}
Regards,
Graham
--
_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev