You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Matt McMinn <ma...@digilore.com> on 2006/08/16 17:17:04 UTC

Specifying specific version of maven-project

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've got two modules, A and B, in a multi-module project, where B
depends on A.  I'm using Ant to build some files in B via xdoclet at
compile time. One of the classes in B depends on an abstract class in A,
which means that I need the actual source file of the abstract class
from A at compile time in B.  This is easily done by building a source
jar file in A, depending on that source file in B, and referencing the
needed class source file in Ant.  Works great when compiling
from the submodule level.  However, due to MNG-1245
(http://jira.codehaus.org/browse/MNG-1245), building from the top level
fails, as the source JAR dependency in B is not provided by Maven.  The
JIRA issue claims that maven-project version 2.0.5 (a snapshot of which
is provided on that page) will fix the issue.  So the question is how
can I get maven to use that specific version?  I have tried installing
the provided snapshot JAR file to my local repository, and adding it as
a dependency, but that didn't work.  Is there any other way to specify
that version 2.0.5 of maven-project should be used?  Or any other good
workaround?  Currently, I'm manually copying the class file from A into
B so I can reference it, but that is obviously not a great solution.

Thanks

Matt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFE4zbz7i/zw3AkUSkRAmiEAKCU1dpuOvzwbVLKFEavbYI5JogT9QCbBpUb
CeV1vSupfUpen8TBXy0fAyk=
=ivGh
-----END PGP SIGNATURE-----