Adrian Custer a écrit :
> Licenses: every jar which could eventually end up used along should
> contain a clear statement of the license(s) which apply to it.
We may have some help from Maven in some future version:
http://jira.codehaus.org/browse/MJAR-42
A question is whatever we want licenses included in JAR soon, or if we can wait
for Maven.
> <comment>: try to figure out if converting <!-- comments to <comment>
> style will keep the comments during branching/release/deploy. Note that
> this will be *a lot* easier to test if we do the local deploy profile
> discussed above.
The last time I looked at the pom.xml files generated automatically during a
"mvn release", comments were not the only issue. The pom.xml file also
contained
a strange amount of duplication in <pluginManagement> for example. I don't have
much concern about the pom.xml files in branches or tags, but would probably
like to keep the pom.xml files in trunk hand-edited.
Martin
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
