MNG-1120.
IF someone provides a patch, it will be included in 2.0, otherwise, I'll
leave it for 2.0.1...
- Brett
Brett Porter wrote:
>+1. Got a patch? :)
>
>Thomas Van de Velde wrote:
>
>
-
To unsubscribe, e-mail: [EMAIL PRO
+1. Got a patch? :)
Thomas Van de Velde wrote:
>That would be great. I think it's better to always declare a schema. That
>way you can use your XML editor for auto-completion, validation, ...
>
>Thomas
>
>On 10/6/05, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
>
>
>>On 10/6/05, Thomas Van de V
That would be great. I think it's better to always declare a schema. That
way you can use your XML editor for auto-completion, validation, ...
Thomas
On 10/6/05, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
>
> On 10/6/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote:
> > Would you think that th
On 10/6/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote:
> Would you think that this is unnecessary duplication?
>
> http://maven.apache.org/POM/4.0.0";>
> 4.0.0
this is a good point: enforcing the schema declaration instead of the
element in m2 could be a better solution. What about
making mo
Would you think that this is unnecessary duplication?
http://maven.apache.org/POM/4.0.0";>
4.0.0
Isn't it better to rely on a DTD or Schema, instead of document element.
This is IMO the common practise (see Hibernate mappings, Spring bean
factories, Struts, ...)
Cheers,
Thomas
On 10/5/05, Anth
When is a POM a legacy POM? The problem is that if you don't label the
POM version up front, *that* is how you end up with a legacy issue.
People will just lose track of the correct POM versions. The problem with
assumed values is that assumptions change over time.
Cheers, Tony.
On Wed,
Again, just wondering if it can be set to a default value within the M2 API
given that this is a very technical requirement that is not directly related
to the build configuration.
On 10/5/05, John Casey <[EMAIL PROTECTED]> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Have you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Have you ever used java object serialization without specifying:
static final long serialVersionUID = ;
then changed the class once you had some serialized data somewhere? This
version element has a similar purpose to serialVersionUID, and it's
ever
d flexibility that is possible in
> the way Maven 2 is set up.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Thomas Van de Velde
> Sent: Wednesday, October 05, 2005 10:21
> To: Maven Developers List; [EMAIL PROTECTED]
> Su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It will help avoid another problem like we're having right now in moving
from maven 1 POMs to maven 2 POMs, for one thing.
I understand wanting to streamline the amount of xml you have to write
for a new project, but surely 34 characters that don't e
TECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Thomas Van de Velde
Sent: Wednesday, October 05, 2005 10:21
To: Maven Developers List; [EMAIL PROTECTED]
Subject: Re: [M2] Provide default for pom.modelVersion
But this is irrelevant for people not using legecy POM's (which I would
think is the g
But this is irrelevant for people not using legecy POM's (which I would
think is the great majority). What would be the inconvenience of having
defaut values? People wanting to use legacy poms just need to override
those.
Thomas
On 10/5/05, Anthony B. Coates <[EMAIL PROTECTED]> wrote:
>
> Such a
Such a default value would be bad karma, in the sense that you have no
indication which version of the POM (Schema) the POM instance was written
against. That stops you from doing intelligent support of legacy POMs,
especially if you make a non-backwards-compatible major version change.
A
Hi,
Currently you are forced to define the modelVersion for each pom, even when
declaring a parent. To me this seems to be a purely technical element that
is of limited interest to end users. Would it not make sense to provide a
default value (4.0.0) if not defined explicitly in the POM?
Cheers,
14 matches
Mail list logo
