Yes U are right. I've only wrote about this file, becuse this is the place for properties for the project in maven.
Hi Marci,
I don't think, that You want to change the static properties of Your project very often, so a configure plugin would probably not be the right solution.
To configure project.properties, You should either use one file as a template (if the changes are always nearly the same),I had template file in mind. For example xml-based file "configuration.xml" which could describe important properties
for my project. configuration goal can read it and in a case
of configuration:help print described properties with human readable
explanation.
Because there can be some properties expected for my artifact and some other may be optional, so during "configuration:configuration" there could be check of project properties (from [project/build].properties and from command line) based on rules from configuration.xml.
Any problems with them could bed reported on console with clear info
what is wrong with project configuration.
> or > wait for an IDE integration (such as mevenide).
this is what I'm doing now.. telling other people what they should switch or pass to get good build and that why I've started thinking about configuration goal/plugin.
AFAIK, to change properties only for one build, You can use -Dpropertyname=value (propably in a batch-file or shell-script).
All above came from project that I'm involved. There is few open source components that are very heavy-ant'ed;) I've created maven build's over each of them to get every component as a artifact (at least one;)).
And here we come:
other developers are to build/extend functionality of the project by creating new web components. this new components are depedant on artifacts created by me. beside that I've wrote some goals for integration-builds and deployment. On every developer's environement there must be set some properties like deploment dir, expected components (it's not about dependecies in project.xml), etc.
and here we are with configuration problem:
how not explain and don't lose time on every new person which has to know what to set before making build.
i think it's time for me to work on plugin:)
tell me what you think about that?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
