t.
-Original Message-
From: Michal Maczka [mailto:[EMAIL PROTECTED]
Sent: Friday, June 06, 2003 8:00 AM
To: 'Maven Users List'
Subject: RE: [Proposla] changes in POM needed by new features of
maven-new [w as:RE: Refining dependencies for test and non-test]
> > 2. I want to pre
> > 2. I want to prepare a field for <> dependencies. I think
> that
> > is should be controllable if given dependency is transitive or not.
> >
> > So I am proposing to use:
> >
> > true
> > or
> > false (default, can be skipped)
>
> As Ben noted, we may need to have dependencies with varying '
Michal Maczka wrote:
> 1. I want to support mapping between dependencies in POM and multiple
> classpaths.
First of all, I think this is a great idea.
I would rather called them 'dependency sets' or something because
dependency != jar.
> I see a need of having at least 3 classpaths: compile, te
>Then to dep groups - remove the whole war.bundle.jar and just make it
>war.bundle.jar
Well. This won't be needed anymore!
Simply in your project which produces war all "runtime" dependencies will be
bundled. And certainly jars will be bundled differently then tlds or
"webcomponents" (whatever
All good, cept
I'd prefer
testsruntime
over
tests, runtime
Then to dep groups - remove the whole war.bundle.jar and just make it
war.bundle.jar
eg
foo
baa
1.0.0
jar
test
eclipse.dependecy
true
Not really sure about the transitive stuff yet, I have a feeling that it
could pos
