What I more commonly see are module naming conventions that make this
pattern really obvious. For example
common
client
server
where common is a dependency of both client and server.
Cheers, Eric
On 2013-09-05 1:53 AM, Anders Hammar wrote:
Yes, it is called a dependency. Dependency Management is one of the core
things in Maven. I suggest you read one of the freely available
books/articles describing how Maven works [1]; it is well described there.
Is see that the link to Sonatype's book doesn't work any more. You can find
that book here [2].
[1] http://maven.apache.org/articles.html
[2] http://www.sonatype.com/resources/books
/Anders
On Thu, Sep 5, 2013 at 10:25 AM, eaglefly <mroz...@gmail.com> wrote:
Hi,
I would like to make maven project as a shared library. My purpose is to
use
one maven by two other projects. Do you know how to do something like this?
Proj1 (use Proj3 as shared library)
Proj2 (use Proj3 as shared library)
Proj3 (shared library)
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-project-as-a-shared-library-tp5769523.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
