You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Christian Andersson <ca...@ofs.no> on 2003/09/19 11:14:40 UTC

some ideas about a collection of default settings

not sure if this has been voiced before (I've tried some searches in the 
archive,but ither I'm not good enough with my searches or there is 
simply nothing there)

anyway, what I was wondering is if there has been any talk of some sort 
of collection of default settings..

for instance we here have many small projects creating 1 jar file each, 
in the project.xml I have for each of these the 3 or more delevoper 
tags. however these developers recur in many of these projects, so my 
idea is that instead of having to typ the complete developertag all the 
time (like this one for me)
<developer>
   <name>Christian Andersson</name>
   <id>ca</id>
   <email>ca ofs no</email>
   <organization>Open Framework Systems AS</organization>
   <timezone>+2</timezone>
</developer>

I was wondering if I could enter this information somewhere else 
"globally" and in the project xml just use something liek this..
<developer>
   <id>ca</id>
</developer>
or
<developer id="ca"/>

and maven should look my information in the "collection" of default 
settings and add the rest to the "in memory" project.xml

the same should also go for all the other data that is regularly used
like the dependency tags..

I know that I could use the "Overriding Stated Dependencies" in the 
property files to do this, but this looks to be user specific, not 
globally...  and I'm not really talking about overriding here...
more like the other way.. for example...

<dependency>
   <artifactId>servletapi</artifactId>
</dependency>

would make maven search the collection to see if that artifact is 
described in there, if it is good, use that to fill in the "empty" tags 
needed for the dependency (like groupId, version, etc)

<dependency>
   <artifactId>servletapi</artifactId>
   <version>2.2</version>
</dependency>

would make maven search the collection to see if that artifact is 
described in there, if it is good, use that to fill in the "empty" tags 
needed for the dependency, however compard to the one above, version 2.2 
should be used nomatter what has been described in the collection...

anyway it is just an idea.... :-)

/Christian Andersson


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