> With this in mind I would like to try tagging a 2.6-M3 - with the hopes of
> also
> addressing the source artifact generation problem.
Interesting:
- 2.5.x: mvn -DskipTests assembly:assembly
Is good.
- 2.6.x: mvn -DskipTests assembly:assembly
Is good.
- 2.6-M2: mvn -DskipTests assembly:assembly
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.geotools:gt-jdbc:jar:tests:2.6-M2
...
Path to dependency:
1) org.geotools.jdbc:gt-jdbc-h2:jar:2.6-M2
2) org.geotools:gt-jdbc:jar:tests:2.6-M2
Mark mentioned a problem about having to go in and build an
unsupported module first; and then trying again when making the 2.5.7
release. Perhaps I am looking at a similar situation?
Jody
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
