> If you'd like, you can use the same code Maven does:
> maven-model-2.0-alpha-1.jar (you'll also need plexus-utils-1.0-alpha-
> 2.jar)
>
> MavenXppReader reader = new MavenXpp3Reader();
> Model pom = reader.read( new FileReader( new File( "pom.xml" ) ) );
> (with suitable error handling on the Fi
> From: Brett Porter Sent: Sunday, April 17, 2005 8:14 AM
> To: Maven Developers List
> Subject: Re: POM root Element: project or model?
>
[snip]
> It's planned to provide a generated schema - however, different
> namespaces will not tend to be used inside the POM - we've looked at the
> option
The Docs on m2 web site for the POM shows as the root element.
In the m2 cvs is a mixture of and elements in the pom.xml
files.
What is the planned name for this element, project or model?
BTW Why not using a namespace declaration (and an online accessible schema
representation of the pom) i
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Saturday, April 16, 2005 4:07 PM
> To: 'Maven Developers List'
> Subject: RE: Maven 2 directory structure for Multiple Modules
> configurable?
[snip]
> It's actually there... (unless I've misunderstood what you meant :-)).
Aahhh I see it
> From: Michal Maczka [mailto:[EMAIL PROTECTED]
> AFAIK the only limitation which exists in eclipse is that project
> directories cannot overlap.
Yes
> So you should be able to import to eclipse all projects, which contain
> java sources and are "leaves" in the directory tree.
> So in you case y
Hi all,
Good to see all these changes in Maven 2.
I use Maven since a long time and actually in a big J2EE project producing a
lot of different artifacts with multi-project. We use Eclipse 3 as IDE and
the maven-eclipse-plugin to create .project and .classpath files. This works
fine for us and tha
