Message-ID: <8788867.2289.1419116593859.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2288_713358124.1419116593859" ------=_Part_2288_713358124.1419116593859 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Get nightly site and javadoc builds
The modules have now been renamed. Jars often start with 'gt-' as in 'gt= -main'.=20
Maven behaves better when we stick to its default behavior. Among other =
it expects module names to match directory names. Previous module names hav=
gt2- prefix in front of them, which isn't present in direc=
tory name. The consequence is broken URL in the generated web site. It is p=
ossible to workaround by providing explicitly
<scm> or <=
code><url> elements in every
pom.xml files, but t=
his is tedious, error-prone and we always end up with modules with wrong se=
ttings. Given the large amount of modules in GeoTools, less manual settings=
we have, better it will be.
However if we blindly remove
gt2- prefix in every module na=
mes, we get potential conflict in JAR names like GeoTools
SHOT.jar with the
h2-1.0-SNAPSHOT.jar database driver: =
only the version number distinguish them, which is fragile. In order to kee=
p some prefix in the JAR name, a possible approach is to use the
finalName> element in
pom.xml like below:
However as of Maven 2.0.8, prefix specified that way are not propagated =
to the online repository and in the JAR downloaded by users. A custom plugi=
n defined in GeoTools,
jar-collector, can take care of copying=
the JAR in a target directory with the right prefix. Every users (=
not just the ones building GeoTools) can get this flat directory p=
roviding they put the following in their own
gt2-prefix from all module names.
<gro= upId>(the need to prefix
<groupId>suggests that something is not work= ing with Maven model...)
g= t-plg-, etc.).
jar-collect= ormentioned above solve those conflicts, but not every users will a= ccept this non-standard plugins.
gt-prefix (without the
2charac= ter), but only for leaves (not for parent modules containi= ng child modules).
gt-prefix in directory name as well. We would = get for example
modules/library/gt-metadata(note that the
Because only leaves produce JAR, it doesn't matter if the parents are no= t prefixed.=20
<finalName>declarat= ion, so we get a total matching between our naming scheme and Maven default= s.
modules/library/gt-metadata, a little bit tedious for those who use a lot the command line.