Even without considering this, there is the classical problem of people
trying to use maven who are not connected to the internet. This
definitely should not be a prerequisite for maven usage. If a person has
all the dependencies he needs located in the local repository, there is
no need to connect to the internet at all.

Another thing: as far as maven.xml is concerned, it is mainly composed
of other jelly namespaces (read: taglibs). The only thing which *might*
be documented in an XSD is the werkz jelly taglib, which would only give
you the <project>, <goal>, <pre/<postGoal>, <attain>, <attainGoal>, etc.
tags...not very useful, since these are pretty simple anyway.

-john

On Mon, 2004-03-01 at 05:15, Maczka Michal wrote:
> > -----Original Message-----
> > From: Maczka Michal [mailto:[EMAIL PROTECTED]
> > Sent: Monday, March 01, 2004 10:58 AM
> > To: 'Maven Users List'
> > Subject: RE: Depenceny version..
> > 
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > > Sent: Monday, March 01, 2004 10:29 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: RE: Depenceny version..
> > > 
> > > 
> > > Hi,
> > > 
> > > > -----Original Message-----
> > > > From: ext John Casey [mailto:[EMAIL PROTECTED]
> > > 
> > > > The reason maven doesn't squawk at this is that it 
> > > > doesn't check for
> > > > XML validity when parsing...
> > > 
> > > Is this excpected to change in future releases? A non 
> > > validating project.xml already was the source of some weird 
> > > problems. Is the schema somewhere available online, so that 
> > > you can define a schema location for it, which is public for all?
> > > 
> > > Also, would it make sense to have a schema for maven.xml, too?
> > > 
> > > Br,
> > >  _         __      _  _
> > > 
> > 
> > I doubt if it will be possible to validate POM using XML Schema.
> > The thing is that there is such thing like "POM inheritence" 
> > and some mandatory tags can be inherited from parent project.
> > 
> > It shouldn't be that hard to write our own POM validator in Java.
> > It even makes more sense then using XML based technlogies and POM
> > does't need.
> > 
> > 
> > Michal
> > 
> 
> I haven't finshed the last sententece :) 
> 
> In the last sentence I meant
> that POM doesn't need to be read from XML. It can be read from db, file
> produuced by java serialization mechanism etc.
> 
> 
> Michal
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
John Casey
[EMAIL PROTECTED]
CommonJava Open Components Project
http://www.commonjava.org


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to