Hi,
you just touched a raw nerve with me... :-)
As long as maven (at least maven 1, don't know about maven 2 yet)
doesn't differentiate between
* Compile dependencies (mandatory and optional)
* Runtime dependencies (mandatory and optional)
then IMHO the dependencies page not really useful.
You have scope and optional as dependency parameters.
The combination of the 2 can provide what you are thinking about. Although not sure the dependency
report will make a separate list out of them. (but this is better for discussing on the maven user
list I guess)
Mvgr,
Martin
Henning
That policy is just for you ;)
Mvgr,
Martin
Henning Schmiedehausen wrote:
I do object to the everyone must build with maven 2 policy. :-)
Best regards
Henning
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
The JDK portion would fall under:
http://mail-archives.apache.org/mod_mbox/maven-dev/200607.mbox/[EMAIL PROTECTED]
Comments welcome. I think I may have missed the obvious part about
specifying the required JDK in the POM, actually :)
Cheers,
Brett
On 13/09/06, Yoav Shapira [EMAIL PROTECTED]
Hi,
Projects that use Maven get this for free in the dependency report
(and people can just look at the POM). Projects that use Ant might
simply direct their users to look in the relevant build script or file
(e.g. build.properties). I'm hesitant to have a separate web page
just to list
I thought there already was a standard, at least as far as dependencies
go: under Project Info...Dependencies? I recall asking about this a few
months back and was told all the Commons projects at least used this
convention... Maybe this isn't auto-generated? I remember at the time I
said I
I've also seen this problem. Last year the question about JDK version
compatibility came up on the mailing list -- it turned out that it
wasn't really clear even internally. (I think we documented this
somewhere as JDK 1.3 for runtime, 1.4 for compiling). But I bet a lot
of this is oral
Dependencies: the Maven generated page on the project site lists them. I
strongly discourage manually maintaining them in a separate location.
JDK version: what a mess. IMHO this is THE information that is missing
on almost ANY project page out there.
As a user I expect this information close to
In message [EMAIL PROTECTED], =?ISO-8859-1?Q?Ortwin_Gl=FCck?= writes:
JDK version: what a mess. IMHO this is THE information that is missing
on almost ANY project page out there.
I think everyone's responses have brought this topic to closure.
Library dependencies are already available from most
Daniel F. Savarese wrote:
In message [EMAIL PROTECTED], =?ISO-8859-1?Q?Ortwin_Gl=FCck?= writes:
JDK version: what a mess. IMHO this is THE information that is missing
on almost ANY project page out there.
I think everyone's responses have brought this topic to closure.
Library dependencies
Hi,
On 9/12/06, Stephen Colebourne [EMAIL PROTECTED] wrote:
Perhaps, this could be achieved by enhancing maven to allow the minimum
JDK level to be specified in the POM, and thus on the dependencies page?
The bottom of
As a quick addendum, it'd be nice to separately specify JDK required
for building and JDK required for running.
Velocity has a 1.3 runtime and 1.4 compile requirement, I can't
remember why off-hand. I think we relaxed the requirements for the
test classes to allow them to use JDK 1.4 libraries.
12 matches
Mail list logo
