maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <stephen.alan.conno...@gmail.com>
Subject Re: list of available properties
Date Fri, 13 Sep 2013 10:34:26 GMT
I think some of it's goals are questionable from a “best practice” point of
view. Certainly read-project-properties and set-system-properties should
come with health warnings as they can have very visible edge cases:

* The properties they introduce all apply after a good chunk of the model
has been resolved, so while they may appear equivalent to a <properties>
section, they are not

* There are some system properties that cannot be changed once the JVM has
started. These are defined in the JLS. Similarly, some system properties
are read and acted upon before the plugin execution takes place and if you
are trying to set one of those system properties, you will be out of luck.
Finally, setting system properties is a symptom of bad plugins that are not
forking a JVM and providing system property setting configuration options.

The plugin is helpful... but usually only when you are dealing with other
plugins that are poorly written/designed.


On 13 September 2013 05:09, Manfred Moser <manfred@simpligility.com> wrote:

> > http://mojo.codehaus.org/properties-maven-plugin/usage.html
> >
> > execute read-project-properties goal  of properties-maven-plugin
> > bind to 'initialize' phase
>
> Thats one of those plugins that has been useful but has a version number
> that reflects badly on it. Could someone just release a 1.0 and get of the
> alpha stuff.
>
> manfred
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message