Adrian Custer a écrit :
> Could whoever designed this please explain what's going on? It seems to
> break thing because the name in the local maven repo used during the
> build differs from the name of the jars that will be used to run.
The "gt-" prefix is inserted correctly in the classpath when we run "mvn
install" from Geotools project root directory. But I noticed that it is not
inserted correctly when we run "mvn install" from a particular module,
including
I guess when a user run "mvn install" from his own module created from the
artifact. It sound like yet an other Maven bug. I was not expecting this issue
when I configured Maven that way last Monday.
The following JIRA task may be related (I will create an other one more
explicit):
http://jira.codehaus.org/browse/MJAR-28
I don't know how to workaround this problem for now.
If we decide to reinsert the "gt2-" prefix in all Geotools module name, we will
come back to the <scm> issue. This one has a workaround however: we can
manually
add <scm> in every pom.xml files. But experience suggested that it is error
prone.
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
