I almost responded to this question with "Maven does manage dependencies at
the package level. Use OSGi for that." But then I realized that Debraj is
specifically asking about how the Maven project itself keeps track of its
package interdependencies.

Debraj, I am an outsider, so do not know for certain, but my guess is that
it is ad hoc. In other words: they probably don't. Various Maven artifacts
probably just add dependencies and use whatever classes are available in
them. It is possible (likely?) that someone(s) have used package analysis
tools in the past to check the package interdependencies, but I would be
surprised if there is any sort of formal tooling in place surrounding that.

I agree with Benson that you could probably find out if you delve into the
POMs, since any such formal tooling would likely be codified in there
somehow, e.g. in a profile.

Regards,
Curtis


On Thu, Jun 16, 2016 at 7:47 AM, Benson Margulies <bimargul...@gmail.com>
wrote:

> What do you mean by 'manage package dependencies'? By 'package' do you
> mean 'java package' (e.g. com.foo.bar), or do you mean an artifact in
> the dependency graph?
>
> Maven is open source. If you want to learn how it works, you need to
> read the code.
>
> If you want to learn how to use it, the sonatype online book is useful.
>
>
>
> On Wed, Jun 15, 2016 at 2:14 PM, Debraj Manna <subharaj.ma...@gmail.com>
> wrote:
> > Can some let me know how does maven internally manages package
> dependency?
> > Is there any architecture diagram available on the net for the same? I
> also
> > asked this in Quora
> > <https://www.quora.com/unanswered/How-does-Apache-Maven-work-internally>
> but
> > did not get any response their nor I am able to find any suitable
> resources
> > in the web that explains the working of maven and even better if I can
> find
> > some class diagram?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Reply via email to