Jason van Zyl wrote:
Dan Fabulich wrote:
A small change to the default repository layout would fix this problem for
everyone: just use the <finalName> in the repository layout. IMO this is
the "right answer" for all languages, and should be the future of Maven.
My opinion hasn't change and I definitely believe that is not the right
answer.
My point is argued in, ah, quite a bit of detail in my write-up. The gist
of the argument was simply that when <finalName> is set, you need that to
be the name of your file.
http://docs.codehaus.org/display/MAVENUSER/BEA+Maven+Requirement+Documents
I don't recall the gist of your objection. I think an essential part of
your objection was that Windows sucks, a point about which I agree. ;-) I
hope you don't think that Windows isn't very important, just because it
sucks. Windows is very important, because it is so ubiquitous. (Helping
users of Windows is important BECAUSE Windows sucks.)
Could you rehearse again your reasoning here, or perhaps in some wiki
article so we don't have to bring it up again? ;-)
As I see it, the Pros/Cons of my proposal are:
Pro 1: If you declared a <finalName>, the artifact will have that name,
which is what you said you needed.
Con 1: If people declare <finalName>, the artifact won't contain a version
number, which is bad even if they say they need it.
Con 2: Changing the DefaultRepositoryLayout will require changing tools in
the world code in the world, and that's worse than the benefit.
Pro 2: The benefit is smooth integration of Windows libraries into the
Maven repository. This benefit is very important, even though Windows
sucks, because Windows is unfortunately ubiquitous.
-Dan
