On Thu, 13 Mar 2003 00:21, Jason van Zyl wrote:
> > The reason for this is that then almost all the generic stuff in my
> > projects can be dealt with in template. Currently I am setting
> > gumpRepositoryId in project.xml (as I don't use it elsewhere) and then
> > reading gumpRepositoryId in project-template.xml - but that seems like a
> > hack.
>
> I would suggest using the id if at all possible.
the problem is that the id (or to be more accurate the artefactId) is not
sufficient. And I can't use groupId because rsn I want to use groupId the way
it is intended (hence why I am currently using the unused gumpRepositoryId).
> Although the XML format
> of the POM is really all that is used there will soon come a day when
> the information is extracted from a database say. Even if you could use
> a property.
true. However I think that information that I want still needs to be there.
The information is essentially the base directory of the project so if I can
get this through some other mechanism - say there was a ${pom.dir} property
added that was set at the instantiation of Project object and was same as
${basedir} in outermost/top level project then that would be perfect.
--
Cheers,
Peter Donald
*-----------------------------------------------------*
* "Faced with the choice between changing one's mind, *
* and proving that there is no need to do so - almost *
* everyone gets busy on the proof." *
* - John Kenneth Galbraith *
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
