Hello,
I would like to change properties values during integration.
In order to put values into properties file specific to an environnement
(path to generate files, etc), I would like to describe the properties to
valorize into the pom.
Then a maven "plugin" could change the values following a
Hi Wayne
"filter resources during build" could be acceptable,
but how notify the build to use a filter file for a specified environment?
For example, in the pom we can write:
...
src/test/filters/dico.properties
src/main/resources
ok
after good reading I see the potential issue in using profiles to put
different filters file:
...
src/test/filters/dico.properties
src/main/resources
ok
after good reading I see the potential issue in using profiles to put
different filters file:
...
src/test/filters/dico.properties
src/main/resources
Hi
I have specified Eclipse to build a module using maven, but
eclipse:eclipse goal delete the ExternalToolBuilder instance in the .project
file.
I saw we can specified in the pom for the Eclipse plugin,
but how to notify the arguments?
The goal is to generate the following .project info:
...
Hello,
what do youy think of "injecting" pom distribution information from settings
file:
http://maven.apache.org/examples/injecting-properties-via-settings.html
http://maven.apache.org/examples/injecting-properties-via-settings.html
Sébastien
Clifton Craig-3 wrote:
>
> Marcel,
>
> Thank
Hi,
What about use tag inherited into child pom to put
information?
Parent POM will define with this property version,
and child module will use also the property to define their version.
For example, you will have Parent like this:
...
pom
2.2
COMMON
http://m
