Build breaks with jar-collector run in jdbc-ng on trunk and Maven 2.1
---------------------------------------------------------------------
Key: GEOT-2502
URL: http://jira.codehaus.org/browse/GEOT-2502
Project: GeoTools
Issue Type: Bug
Affects Versions: 2.5.5
Reporter: Andrea Aime
Assignee: Andrea Aime
Fix For: 2.5.6
After quite some debugging I found out that the failure was due to the wrong
parent pom specified in the jdbc-ng datastores, it was "unsupported" but it
should have been "gt-jdbc-ng" (that is, the pom in the parent directory).
Apparently in Maven 2.1 this relationship (the declared parent pom is actually
what you find in ../pom.xml) is pretty important, the build was broken in other
modules for the same reason.
For the record, debugging the jar collector resulted in unresolved variables in
the project object model, the build directory was "${project.basedir}/target",
that is, with a variable un-expanded, and running mvn with -X returned a
warning stating that the contents of ../pom.xml were not consistent with the
declared parent pom.
Puzzling thought, on 2.5.x the build works fine with Maven 2.1 and the same jar
collector... wonders...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
