jgarnett a écrit :
A couple of silly questions -
- eclipse intergration - is there any?
There is a plugin for Eclipse (and for Netbeans too), but I don't know
how well it performs. A Maven documentation is under way exactly on this
topic:
http://people.apache.org/~jvanzyl/maven2/guides/mini/guide-ide-eclipse.html
Totally empty for now, but at least the plugin exists (I believe) and
the guide is under way.
- what was the fix for javadoc generation?
Maven 2 use completly different plugins, so I don't think that Maven 2
fixes applies to Maven 1.
The javadoc plugin in Maven 2 still has some bugs (I had to disable some
parameters in pom.xml files), but a minimal javadoc plugin work. It can
be started with "m2 javadoc:javadoc". However, I don't know yet how to
link it to the web site generated by "m2 site:site". I'm waiting for
better documentation before to fix it.
I think we would be happy to help, what is scp? I know our sys admins
are happy with the webdev access currently inplace.
Secure copy using something similar to ssh2 (I believe). It can been
seen as a replacement for ftp, but more convenient to use and more
secure (the password is encrypted, while ftp transfer the password in
clear text). On the command line, it work as an ordinary "cp" command
except that the source or destination directory can been an URL.
I think that "scp" is standard on most Unix modern box. An "scp" command
for Windows is provided with Cygwin.
Question: One of the real problems I have with Maven 1.0 is that we are
not allowed to publish the geotools jars along with everything else (we
do once a release is made), but I often find myself working against jars
are that are not yet stable. We have a work around for udig, but we do
work with other projects and are using maven as a build system.
In Maven 2, I have setup the current Geotools version as "2.2-SNAPSHOT".
When we execute "m2 deploy", Maven 2 automatically copy the JARs to the
remote repository using scp, and replaces (on the remote repository) the
"SNAPSHOT" keyword by a timestamp, which is really very convenient.
I have (on my experimental Maven 2 repository) every JARs not provided
in http://www.ibiblio.org/maven2 including Geotools JAR. I have also
setup our own project to links against those JARs. Users have a choice:
they can declare a dependency to "somemodule-2.2-SNAPSHOT.jar", in which
case Maven 2 checks once a day (by default, this is configurable) if a
new version is available. Or the users can declare a dependency to
"somemodule-2.2-20051010.224012-1.jar" (for example) where
"20051010.224012-1" has been automatically generated by Maven when we
executed "m2 deploy". This is actually quite easy.
Actually, I believe that I'm going to love Maven 2.
Note: James has suggested we make a more persisten maven repo available
at dist.geotools.org - and Justin just got access to this last week.
"dist.geotools.org" sound nice to me. Whas is for Geotools JAR? Actually
I would suggest some adress used only for Maven 2 repository (maybe
"maven.geotools.org"?), because Maven 2 repository layout is different
from Maven 1 repository layout. We could put Geotools JARs as well as
other JARs (like GeoAPI and other dependencies) in this repository;
there is no clash since Maven 2 organize them in their own
sub-directories anyway.
An alternative is to creates a "dist.geotools.org/maven2" directory.
No matter to solution choosen, is it possible to have a scp access to
some directory for Maven 2 repository?
Thanks,
Martin.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
