Sounds like when the MVEL author release 1.2.24 he didn't do a valid
pom.xml - I'll let him know.
There is also another problem with the 4.0.5 and the MVEL eclipse
configuration - see email thread below. I'm going to push for a 4.0.6
release next week, to address this.
1.2.25 or 1.2.24 is fine - as long as you always use the same version
for everything, they aren't serialisation compatible.
Sorry.
Eric Miles wrote:
I am attempting to build a project using Maven2 with Drools 4.0.5
and
JDK 1.4. The MVEL dependency was downloaded and I'm getting an error
with it's pom:
mvel-1.2.24-java1.4.pom
3/26/08 8:51:09 AM EDT: Parsing
error /home/emiles/.m2/repository/org/mvel/mvel/1.2.24-java1.4/mvel-1.2.24-java1.4.pom;
org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag name </pakaging>
must match start tag name <packaging> from line 6 (position: TEXT seen
...<packaging>jar</pakaging>... @6:30)
3/26/08 8:51:09 AM EDT: Unable to read smarttime/pom.xml;
org.eclipse.core.runtime.CoreException: Parsing
error /home/emiles/.m2/repository/org/mvel/mvel/1.2.24-java1.4/mvel-1.2.24-java1.4.pom;
org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag name </pakaging>
must match start tag name <packaging> from line 6 (position: TEXT seen
...<packaging>jar</pakaging>... @6:30)
I excluded version 1.2.24 and used 1.2.25 instead, which fixes my build
path errors. Is this version okay to use with Drools 4.0.5?
Thanks!
Eric
The mvel release is screwed up.
dependency>
<groupId>org.mvel</groupId>
<artifactId>mvel</artifactId>
<version>1.2.24-java1.4</version>
</dependency>
Our mvel, for the 1.4 backport, has always been called mve14 - as we've
done the releases ourselves in the past.
<dependency>
<groupId>org.mvel</groupId>
<artifactId>mvel14</artifactId>
<version>1.2.21</version>
</dependency>
So now when eclipse does the version stripping it includes mvel.jar and
not mvel14.jar, leaving it screwed.
Mark