Hi David,
We have a similar setup for our projects. We use M2Eclipse 0.0.10, and
it has the ability to automatically add Eclipse dependencies instead of
going to the Maven repository.
In order for the plugin to identify an open eclipse project as a match
for a dependency, I believe both projects must be setup in Eclipse as
Maven projects and the pom.xml for B should use exactly the same
artifact id and version id as specified in A's dependency.
We have our version numbers assigned as part of our Luntbuild ci process
so we have worked around the version number requirement by storing a
static "version-replaced-by-luntbuild" string in both poms, and then
replacing this with a proper version using a find/replace in our
automated build process.
It is a bit of a pain as you have to remember to add in the correct
version when you build the project on the console, but for the most part
it works OK.
HTH,
Ben
David Corbin wrote:
I'm new to Maven, and M2Eclipse. I noticed a recent thread that might have
been on this very subject, but I'm not sure so I'm asking.
In our pom.xml, we have a project A depending on artifact B. And in Eclipse
we have project A depending on project B. But A is failing because there is
no B in the repository. In eclipse, I don't really want it to refer to the
repository for B, but it seems to be doing so. Also, it would be nice if I
didn't have to manully add the Eclipse dependencies.
Any solutions?
David
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
