Silly me... :-[
I saw properties might get deprecated so I'll stick with project.properties
Regards
Nacho
Maczka Michal wrote:
-----Original Message-----
From: Nacho G. Mac Dowell [mailto:[EMAIL PROTECTED]
Sent: Friday, February 11, 2005 2:14 PM
To: Maven Developers List
Subject: Re: [MAVEN] ${pom.properties} is a ArrayList of String?
Maybe it is a stupid question:
why don't you use project.properties file for that and do is
like this:
jaxme-jelly-tag-library=http://jakarta.apache.org/commons/jel
ly/libs/jaxme/i
ndex.html
?
Actually this is what I am doing at the moment. I have:
link-jaxme-jelly-tag-library=http://jakarta.apache.org/commons
/jelly/libs/jaxme/index.html
It is probably a better aproach for this, specially when resource
bundles come in. The thing is that I didn't like mixing contents (a
link) with maven configuration (project.properties).
I just thought it would be useful to be able to navigate through the
properties (from the pom). I suppose this is for performance
reasons. If
this is the case it is agood enough reason for me.
The only real difference for maven1 is that project.properties file is not
deploy to the repository.
So project.properties are usually just good enough.
http://cvs.apache.org/viewcvs.cgi/maven-components/maven-model/
I didn't find org.apache.maven.project.Model there... no
sources either.
java classes are generated from the model file which you can find in that
project.
Regards,
Nacho
michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
