Any interest in a maven-properties-plugin?

[Zarar Siddiqi]

I've written a plugin that serves as a good utility in handling properties.  Given the many questions on this mailing list about handling properties for different environments and I/O'ing them from files, I think this would help in alleviating this problem.

It has three goals (for now):

1. read-project-properties: Given a set of property files in name=value format, it reads them and stores them as project properties.  This would be nice for those of us that store environment specific information in different property files.

2. write-project-properties: Writes project properties to a given file.  Helpful when some properties need to be available at runtime (e.g.: Spring's PropertyPlaceholderConfigurer)

3. write-active-profile-properties:  Writes the properties of any active profiles to a file.

The above three are the use cases that I've encountered.  I'm sure there are many more.

If there is any interest in such a plugin, do respond to this and I will make a site for it and start the process of submitting a plugin to org.codehaus.mojo.

Thank you.

[Wayne Fay]

I think there is certainly some interest in this kind of plugin. In
particular, the write-project-properties functionality might be useful
to build up properties files used by Spring etc.

However, it should be named properties-maven-plugin, as it does not
originate from the Maven Dev team.

Wayne

On 10/16/06, Zarar Siddiqi <zarars@...> wrote:

>
> I've written a plugin that serves as a good utility in handling properties.
> Given the many questions on this mailing list about handling properties for
> different environments and I/O'ing them from files, I think this would help
> in alleviating this problem.
>
> It has three goals (for now):
>
> 1. read-project-properties: Given a set of property files in name=value
> format, it reads them and stores them as project properties.  This would be
> nice for those of us that store environment specific information in
> different property files.
>
> 2. write-project-properties: Writes project properties to a given file.
> Helpful when some properties need to be available at runtime (e.g.: Spring's
> PropertyPlaceholderConfigurer)
>
> 3. write-active-profile-properties:  Writes the properties of any active
> profiles to a file.
>
> The above three are the use cases that I've encountered.  I'm sure there are
> many more.
>
> If there is any interest in such a plugin, do respond to this and I will
> make a site for it and start the process of submitting a plugin to
> org.codehaus.mojo.
>
> Thank you.
>
> --
> View this message in context: http://www.nabble.com/Any-interest-in-a-maven-properties-plugin--tf2454363.html#a6840727
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Zarar Siddiqi]

Here's a site for the plugin:

http://individual.utoronto.ca/zarar/properties-maven-plugin/site/

Zarar Siddiqi wrote:

I've written a plugin that serves as a good utility in handling properties.  Given the many questions on this mailing list about handling properties for different environments and I/O'ing them from files, I think this would help in alleviating this problem.

It has three goals (for now):

1. read-project-properties: Given a set of property files in name=value format, it reads them and stores them as project properties.  This would be nice for those of us that store environment specific information in different property files.

2. write-project-properties: Writes project properties to a given file.  Helpful when some properties need to be available at runtime (e.g.: Spring's PropertyPlaceholderConfigurer)

3. write-active-profile-properties:  Writes the properties of any active profiles to a file.

The above three are the use cases that I've encountered.  I'm sure there are many more.

If there is any interest in such a plugin, do respond to this and I will make a site for it and start the process of submitting a plugin to org.codehaus.mojo.

Thank you.

[mickknutson]

I have a question about this plugin....
is this going to allow me to pull a file from the local machine:

<file>c:/etc/config/dev.properties</file>

Then put those parameters into scope of the build. Similiar to settings.xml
    <properties>
                <project.param>Project-Parameter</project.param>




On 10/16/06, Zarar Siddiqi <zarars@...> wrote:

>
>
>
> Here's a site for the plugin:
>
> http://individual.utoronto.ca/zarar/properties-maven-plugin/site/
>
>
>
>
> Zarar Siddiqi wrote:
> >
> > I've written a plugin that serves as a good utility in handling
> > properties.  Given the many questions on this mailing list about
> handling
> > properties for different environments and I/O'ing them from files, I
> think
> > this would help in alleviating this problem.
> >
> > It has three goals (for now):
> >
> > 1. read-project-properties: Given a set of property files in name=value
> > format, it reads them and stores them as project properties.  This would
> > be nice for those of us that store environment specific information in
> > different property files.
> >
> > 2. write-project-properties: Writes project properties to a given file.
> > Helpful when some properties need to be available at runtime (e.g.:
> > Spring's PropertyPlaceholderConfigurer)
> >
> > 3. write-active-profile-properties:  Writes the properties of any active
> > profiles to a file.
> >
> > The above three are the use cases that I've encountered.  I'm sure there
> > are many more.
> >
> > If there is any interest in such a plugin, do respond to this and I will
> > make a site for it and start the process of submitting a plugin to
> > org.codehaus.mojo.
> >
> > Thank you.
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Any-interest-in-a-maven-properties-plugin--tf2454363.html#a6842863
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

--

Thanks

DJ MICK
http://www.djmick.com
http://www.myspace.com/mickknutson

[Zarar Siddiqi]

Once you invoke the plugin on dev.properties, any properties in the file will become part of the build. So if the property file contained:

var1=value1
var2=value2

It would be the equivalent of you declaring the following in your pom.xml or settings.xml:

<properties>
  <var1>value1</var1>
  <var2>value2</var2>
</properties>

So you can either:

A) specify one property file which contains all your properties
OR
B) declare them manually in your pom.xml or settings.xml

Note that you don't have to do both A and B, just one of them.

I like the simplicity of A and the power to have multiple property files is also nice.

Mick Knutson-4 wrote:

I have a question about this plugin....
is this going to allow me to pull a file from the local machine:

<file>c:/etc/config/dev.properties</file>

Then put those parameters into scope of the build. Similiar to settings.xml
    <properties>
                <project.param>Project-Parameter</project.param>




On 10/16/06, Zarar Siddiqi <[e-mail]> wrote:
>
>
>
> Here's a site for the plugin:
>
> http://individual.utoronto.ca/zarar/properties-maven-plugin/site/
>
>
>
>
> Zarar Siddiqi wrote:
> >
> > I've written a plugin that serves as a good utility in handling
> > properties.  Given the many questions on this mailing list about
> handling
> > properties for different environments and I/O'ing them from files, I
> think
> > this would help in alleviating this problem.
> >
> > It has three goals (for now):
> >
> > 1. read-project-properties: Given a set of property files in name=value
> > format, it reads them and stores them as project properties.  This would
> > be nice for those of us that store environment specific information in
> > different property files.
> >
> > 2. write-project-properties: Writes project properties to a given file.
> > Helpful when some properties need to be available at runtime (e.g.:
> > Spring's PropertyPlaceholderConfigurer)
> >
> > 3. write-active-profile-properties:  Writes the properties of any active
> > profiles to a file.
> >
> > The above three are the use cases that I've encountered.  I'm sure there
> > are many more.
> >
> > If there is any interest in such a plugin, do respond to this and I will
> > make a site for it and start the process of submitting a plugin to
> > org.codehaus.mojo.
> >
> > Thank you.
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Any-interest-in-a-maven-properties-plugin--tf2454363.html#a6842863
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [e-mail]
> For additional commands, e-mail: [e-mail]
>
>


--

Thanks

DJ MICK
http://www.djmick.com
http://www.myspace.com/mickknutson

[Zarar Siddiqi]

I've created a JIRA for this:

http://jira.codehaus.org/browse/MOJO-535

Please vote if you feel this is helpful.

Wayne Fay wrote:

I think there is certainly some interest in this kind of plugin. In
particular, the write-project-properties functionality might be useful
to build up properties files used by Spring etc.

However, it should be named properties-maven-plugin, as it does not
originate from the Maven Dev team.

Wayne

On 10/16/06, Zarar Siddiqi <[e-mail]> wrote:
>
> I've written a plugin that serves as a good utility in handling properties.
> Given the many questions on this mailing list about handling properties for
> different environments and I/O'ing them from files, I think this would help
> in alleviating this problem.
>
> It has three goals (for now):
>
> 1. read-project-properties: Given a set of property files in name=value
> format, it reads them and stores them as project properties.  This would be
> nice for those of us that store environment specific information in
> different property files.
>
> 2. write-project-properties: Writes project properties to a given file.
> Helpful when some properties need to be available at runtime (e.g.: Spring's
> PropertyPlaceholderConfigurer)
>
> 3. write-active-profile-properties:  Writes the properties of any active
> profiles to a file.
>
> The above three are the use cases that I've encountered.  I'm sure there are
> many more.
>
> If there is any interest in such a plugin, do respond to this and I will
> make a site for it and start the process of submitting a plugin to
> org.codehaus.mojo.
>
> Thank you.
>
> --
> View this message in context: http://www.nabble.com/Any-interest-in-a-maven-properties-plugin--tf2454363.html#a6840727
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [e-mail]
> For additional commands, e-mail: [e-mail]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [e-mail]
For additional commands, e-mail: [e-mail]

[ertnutler]

i'm interested in using this plugin, but i can't checkout the source or browse the repository from the project home page.  has it been removed?

[Zarar Siddiqi]

It is going through the tedious process of being accepted as a plugin.  Vote for it here:

http://jira.codehaus.org/browse/MOJO-535

The source can also be found in JIRA.

ertnutler wrote:

i'm interested in using this plugin, but i can't checkout the source or browse the repository from the project home page.  has it been removed?

[Ian Springer]

I'd also find very useful a goal (or an option to the existing
write-properties goal) that echoes all properties, or a set of specified
properties, to the console - along the same line as the echoproperties
Ant task
(http://ant.apache.org/manual/OptionalTasks/echoproperties.html). This
would be handy for two purposes:

1) debugging the build
2) printing certain properties (e.g. java.version) during the build for
informational purposes

| -----Original Message-----
| From: Zarar Siddiqi [mailto:zarars@...]
| Sent: Thursday, October 26, 2006 10:09 AM
| To: users@...
| Subject: Re: Any interest in a maven-properties-plugin?
|
|
| It is going through the tedious process of being accepted as
| a plugin.  Vote
| for it here:
|
| http://jira.codehaus.org/browse/MOJO-535
|
| The source can also be found in JIRA.
|
|
|
| ertnutler wrote:
| >
| > i'm interested in using this plugin, but i can't checkout
| the source or
| > browse the repository from the project home page.  has it
| been removed?
| >
|
| --
| View this message in context:
| http://www.nabble.com/Any-interest-in-a-maven-properties-plugi
n--tf2454363.html#a7011829
| Sent from the Maven - Users mailing list archive at Nabble.com.
|
|
| ---------------------------------------------------------------------
| To unsubscribe, e-mail: users-unsubscribe@...
| For additional commands, e-mail: users-help@...
|
|

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...