Re: Why do we need POMs in repo for non-Maven projects?

[bob mcwhirter <bo...@codehaus.org>]

Sure, but dependencies don't necessarily mean build-time stuff.

My project might depend on NonMavenProject-A, which also depends on
NonMavenProject-B.

So, I build my project against their NonMavenProject-A.jar file, and then
to *use* my project at runtime, I have to include NonMavenProject-B.jar
in my CLASSPATH.  That's where I see transitive dependencies for non-maven
projects to be nice.

Though, I can understand creating POMs might be a hassle.  Perchance we
should also allow for some simplified runtime-dependencies.txt or
something, that simply enumerates the non-maven project's runtime
dependencies?

	-bob


On Sun, 13 Jun 2004, Vincent Massol wrote:

> Hi,
>
> A stupid question: Why do we need POMs in repo for non-Maven projects?
>
> It seems to me, this is for supporting transitive dependencies. However
> Maven will not try to build non-Maven projects, right? Is there a use
> case where it's still useful to have POM information for non-Maven
> projects?
>
> I'm asking because it's a pain to get POMs for non-Maven projects and
> I'm not sure about the benefit.
>
> Shouldn't non-Maven projects artifacts considered as already *built*?
>
> Thanks
> -Vincent
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

--
Bob McWhirter        bob@werken.com
The Werken Company   http://werken.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org