Simon,
Thanks a lot for responding. I'm still a bit confused, as I don't see a
".m2" directory anywhere. I should mention that I am using windows - do
that change the behaviour at all?
What I have tried is putting shared and tomahawk sources in folders next
to each other, then running "maven install" in each one. (shared first)
Regards,
Jeff Bischoff
Kenneth L Kurz & Associates, Inc.
Simon Kitching wrote:
Jeff Bischoff wrote:
Hey gang,
I want to build the Tomahawk 1.1.4 branch (release candidate?) locally
so that I can do some testing on it to prepare our eventual upgrade to
1.1.4
Using SVN, I downloaded the source for this branch from the repos
listed on the status doc. [1]
They both seem to build fine, but it occurred to me that the Tomahawk
stuff would have no way to find the Shared project that I just built.
So it must be using the one from the repository online, yes? Is it
reasonable to let it do that? Do I need to create a maven repository
in order to build both together, locally?
[1] http://svn.apache.org/repos/asf/myfaces/current/STATUS.txt
When you run "mvn install" in your local copy of the shared project, the
resulting jar is copied into your ~/.m2 directory.
When you then run "mvn build" or "mvn install" in your local copy of
tomahawk, maven first checks ~/.m2 and uses the version found there.
Only if nothing with the desired version# is found locally will it
download it and then store the downloaded file under ~/.m2
Cheers, Simon
