Re: 1.1-beta-1 sourceModifications problem

2005-06-23 Thread Brett Porter
I use http://maven.apache.org/maven-v3_0_0.xsd in IDEA, works quite nicely. - Brett On 6/24/05, Scott Lamb <[EMAIL PROTECTED]> wrote: > On Jun 22, 2005, at 9:04 PM, Incze Lajos wrote: > > > Fix: Check your project file against the XSD published for the model > > version you are using. > > Is th

Re: 1.1-beta-1 sourceModifications problem

2005-06-23 Thread Scott Lamb
On Jun 22, 2005, at 9:04 PM, Incze Lajos wrote: Fix: Check your project file against the XSD published for the model version you are using. Is there an XML schema validator that gives decent error messages? This is frustrating because I can't get one from either maven itself or xmllint. xm

Re: 1.1-beta-1 sourceModifications problem

2005-06-22 Thread Scott Lamb
On 22 Jun 2005, at 18:31, Brett Porter wrote: Since it repeated several times, I assume this is not just a type in the email: sourceModication -> sourceModification Thanks. I didn't notice this misspelling. Too much slashdot has desensitized me, or something... Regards, Scott -- Scott

Re: 1.1-beta-1 sourceModifications problem

2005-06-22 Thread Incze Lajos
I means that you have to follow strictly the project schema. See: http://maven.apache.org/reference/backwards-compatibility.html: Parse errors on previously 'valid' project files project.xml files that used to work in older versions of Maven may now present parse errors. The parser in Maven 1.1

Re: 1.1-beta-1 sourceModifications problem

2005-06-22 Thread Brett Porter
Since it repeated several times, I assume this is not just a type in the email: sourceModication -> sourceModification Even though Maven1 didn't fail on this, it would have ignored it. Cheers, Brett On 6/23/05, Scott Lamb <[EMAIL PROTECTED]> wrote: > maven 1.1-beta-1 doesn't parse my project.xm

1.1-beta-1 sourceModifications problem

2005-06-22 Thread Scott Lamb
maven 1.1-beta-1 doesn't parse my project.xml. It gives me errors like these: org.apache.maven.MavenException: Unknown error reading project at org.apache.maven.MavenUtils.getProject(MavenUtils.java:146) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:99) ... --- Nest

Re: About sourceModifications

2004-03-21 Thread dion
It's a source modification. It excludes or includes source code. -- dIon Gillard, Multitask Consulting "Marco Tedone" <[EMAIL PROTECTED]> wrote on 19/03/2004 06:22:37 PM: > Does exclude classes or sources? Here for > classes I mean .class. In my experience, this element excludes the > source

About sourceModifications

2004-03-18 Thread Marco Tedone
Does exclude classes or sources? Here for classes I mean .class. In my experience, this element excludes the sources completely. Therefore these won't never get compiled and included in the jar. If so, the example in the descriptor documentation page could change. Marco

Re: sourceModifications

2003-10-04 Thread khote
riginal Message - From: "khote" <[EMAIL PROTECTED]> To: "Maven Users List" <[EMAIL PROTECTED]> Sent: Saturday, October 04, 2003 5:21 AM Subject: sourceModifications > I'm looking for some examples on how to use the > element in the project descripto

sourceModifications

2003-10-04 Thread khote
I'm looking for some examples on how to use the element in the project descriptor. It seems that it is replacing , rather than adding to it. What am I doing wrong? src/java com.chronicle.om.Volume