But who stops a developer from still using the very same property as a
programm variable?
That's still the same solution that I pointed out the the beginning (imho) -
it "scales down" the problem,
but it's still there (on the high costs of having to manually select each
file to be filtered).
Hmm. S
Hi,
If you absolutely have go the way of filtering Java files, I would
probably do it that way:
1. Put the java files to filter in a separate directory
(src/main/java-filtered)
2. Add a filtered resource to the pom
(target/generated/sources/java-filtered)
3. Make this additional source d
Well, sure, we COULD do it at runtime, but
a) this would cost performance (okay, to be honest, of course, it could once
be loaded and runtime and so on, but still it would at least clutter the
code with additional stuff we didn't when we were using Maven 1).
b) For political reasons It would be goo
Well maybe,
Why do you want the version in the code itself?
runtime resolution
-
Would it be sufficent (or perhaps better) to get it at runtime rather than
having it compiled in?
The maven jar plugin writes a file called pom.properties in
META-INF/maven/groupid/artifa
PROTECTED]>
To: users@maven.apache.org> Subject: Re: Filtering of a SINGLE property> >
Noone?> > Please, there must be someone able to answer this?!> > > Thanks,> >
Peter> > 2008/7/3 Peter Horlock <[EMAIL PROTECTED]>:> > > Hi,> >> &g
One way of achieving this would be to put the properties files that need
to be filtered in a folder and the non-filtered ones in another folder.
These folders can then be configured for
true/false accordingly.
Something along the lines of:
src/main/filtered
true
src/main/unfiltered
f
Noone?
Please, there must be someone able to answer this?!
Thanks,
Peter
2008/7/3 Peter Horlock <[EMAIL PROTECTED]>:
> Hi,
>
> I want to let Maven / the Resource plugin (
> http://maven.apache.org/plugins/maven-resources-plugin/examples/include-exclude.html
> )
>
> parse my source code to rep
Hi,
I want to let Maven / the Resource plugin (
http://maven.apache.org/plugins/maven-resources-plugin/examples/include-exclude.html
)
parse my source code to replace {project.version} with the current version
of the project as defined in the pom.
This works great, but - in JSTL, as well as in Op
