Only issue is triggering the read. There used to be a build start goal (forgot what the name was) that you could use to attach off of (with a postGoal), but it got broken a long long time ago. I forgot the exact name. Does anybody know if this goal is still non-existentbroken? I had a look in Jira, but couldn't find an issue. Without that goal, it's almost impossible to do something at the begining of every build (like readin in properties) when you don't know what goal the user will be running, so you can do a preGoal off that or one of its dependencies...
Colin
khote wrote:
this method works? I'm going to give it a try for certain. It sounds a little chicken-and-the-egg though .... does the top-level maven.xml copy the *.properties into the sub-projects, or do the sub-projects copy from ../*.properties themselves?
----- Original Message ----- From: "Vincent Massol" <[EMAIL PROTECTED]>
To: "'Maven Users List'" <[EMAIL PROTECTED]>
Sent: Friday, September 19, 2003 11:35 AM
Subject: RE: Any way to have shared properties when extending from a base
project
Hi Colin,
This is a known wanted feature (I also want it dearly). Check JIRA. It's scheduled for 1.1. If you want it faster, please send a patch and I'll gladly apply it :-)
As a workaround on my work project, we have a custom maven.xml goal that copies the top level project.properties to the current project you're building. That means of course that you have to put all properties at the top level.
Thanks -Vincent
like-----Original Message----- From: Colin Sampaleanu [mailto:[EMAIL PROTECTED] Sent: 19 September 2003 20:30 To: Maven Users List Subject: Any way to have shared properties when extending from a base project
I just realized that while you can extend a project with something
extend>${basedir}/../master/project.xml</extend>don't
maven doesn't seem to read in build.properties (and project.properties
either I guess) from the master project. This is a real PITA, as I
want to force people to put identical build.properties files in allthe
subprojects, and it's not acceptible to have a build.properties filein
the user directory, as it will trample the version for other projects.
I think I'm missing something, as this is a big hole. What are other people doing in this situation?
Regards,
Colin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
