Found an answer, use the "relativePath" element in the parent
declaration. Still might be a bug though as the parent pom was still in
my local maven repo. But hey, never look a gift horse in the mouth :)
Justin Deoliveira wrote:
> Hi all,
>
> While doing the move of the jdbc-ng modules to supported I ran into an
> issue with the jar collector. I have run up against this before but
> never taken the time to figure out the issue, until today. Apologies if
> this is a known issue. And I am not sure if this is a documented bug in
> maven, but here goes:
>
> At some point the jar-collector plugin walks the pom hierachy to the top:
>
> MavenProject parent = project;
> while (parent.hasParent()) {
> parent = parent.getParent();
> }
> collectDirectory = parent.getBuild().getDirectory();
>
> This only seems to work if the pom hierarchy matches the actual
> directory hierarchy on the file system. However, if I create a pom which
> references a parent pom which lives in a non-parent directory the maven
> poms do not seem to resolve properly, and the value of the string:
>
> parent.getBuild().getDirectory() resolve to "${project.basedir}/target"
> rather than the actual path, and the plug-in fails.
>
> Has anyone else run up against this. I am also a little unsure of why
> this plug-in is needed? It seems to put gather up all built jars and put
> them into the root target directory, I guess this is for release purposes?
>
> -Justin
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
