pom.xml's in the trunk

Are you guys using maven2 or ant for building the trunk?

I noticed the pom.xml's are "3.0.2" instead of "3.1.0-SNAPSHOT", so I am 
fear the dependency versions will be out of date too?

Also, I noticed you didn't lock down the maven plugin versions, which 
can lead to instable maven2 builds. I do that like this in the parent pom:

     <build>
         <pluginManagement>
             <plugins>
                 <!--
                     Last time synchronized with the latest plugin releases:
                     2006-06-21
                     See 
http://news.gmane.org/gmane.comp.apache.maven.announce
                 -->

                 <!-- Building -->
                 <plugin>
                     <groupId>org.apache.maven.plugins</groupId>
                     <artifactId>maven-help-plugin</artifactId>
                     <version>2.0.1</version>
                 </plugin>
                 <plugin>
                     <groupId>org.apache.maven.plugins</groupId>
                     <artifactId>maven-clean-plugin</artifactId>
                     <version>2.1</version>
                 </plugin>
                 <plugin>

Re: pom.xml's in the trunk

We use pom's for dependency management, but actually build wtih ant 
(which can use maven), we just haven't updated the pom as our day to day 
work is done in eclipse - where it doesn't matter as much.

Mark
Geoffrey De Smet wrote:
> Are you guys using maven2 or ant for building the trunk?
>
> I noticed the pom.xml's are "3.0.2" instead of "3.1.0-SNAPSHOT", so I 
> am fear the dependency versions will be out of date too?
>
> Also, I noticed you didn't lock down the maven plugin versions, which 
> can lead to instable maven2 builds. I do that like this in the parent 
> pom:
>
>     <build>
>         <pluginManagement>
>             <plugins>
>                 <!--
>                     Last time synchronized with the latest plugin 
> releases:
>                     2006-06-21
>                     See 
> http://news.gmane.org/gmane.comp.apache.maven.announce
>                 -->
>
>                 <!-- Building -->
>                 <plugin>
>                     <groupId>org.apache.maven.plugins</groupId>
>                     <artifactId>maven-help-plugin</artifactId>

Re: pom.xml's in the trunk

If you're interested in applying them, I could create some JIRA patches 
to improve your current pom.xml's.

I've maven2ized http://spring-rich-c.sf.net , http://networktools.sf.net 
and several other projects.

With kind regards,
Geoffrey De Smet

Mark Proctor wrote:
> We use pom's for dependency management, but actually build wtih ant 
> (which can use maven), we just haven't updated the pom as our day to day 
> work is done in eclipse - where it doesn't matter as much.
> 
> Mark
> Geoffrey De Smet wrote:
>> Are you guys using maven2 or ant for building the trunk?
>>
>> I noticed the pom.xml's are "3.0.2" instead of "3.1.0-SNAPSHOT", so I 
>> am fear the dependency versions will be out of date too?
>>
>> Also, I noticed you didn't lock down the maven plugin versions, which 
>> can lead to instable maven2 builds. I do that like this in the parent 
>> pom:
>>
>>     <build>
>>         <pluginManagement>
>>             <plugins>
>>                 <!--
>>                     Last time synchronized with the latest plugin 

A few problems compiling the trunk

1) Unused, broken import in:
drools-compiler\src\main\java\org\drools\semantics\java\StaticMethodFunctionResolver.java

import antlr.collections.AST; // unused and breaks compiling because it 
no longer exists

2) http://jira.jboss.com/jira/browse/JBRULES-537

3) Drools-compiler depends on Jess.
Since Jess isn't open source, it cannot be distributed,
which means that drools-compiler can't be fully build?
Maybe the benchmarks should be moved to a separate module which isn't 
included in the default module set?

4) I've also found a bug on the QueryResults on the 3.0.x branch, which 
I 'll verify in the trunk (if I can get it to build ;) and create a 
testcase for.
[Apparently doing the same query twice and using A and exist(anotherA 
with a greater id) gives problems. In 3.0.4 with logical retractions it 
works. But anyway, I 'll create a testcase.]

--

-- 
With kind regards,
Geoffrey De Smet

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

JBRULES-310 and primitives

Edson,

With the latest primitives support is this jira  now obsolete?
http://jira.jboss.com/jira/browse/JBRULES-310

If so, can you close as "won't fix".

Mark

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Re: A few problems compiling the trunk

Geoffrey,

After the last few weeks manic performance work, where we broke 
everything, we are now just in the process on getting trunk working 
again and pushing out a milestone release.

1)  (Fixed)

2) See comment in jira

3) Damn didn't mean to commit that eclipse project, it was just 
something I was messing around with locally - sorry. (Fixed)

4)  Will  look into this  soon.

Thanks for this, it really  helps keep us on our toes  and move  the 
project forward. With regards to the build  system, more than happy for  
you to start maintaing that for us :) We use  the pom's for dependency 
management but ant for  actual building as I just had too many issues 
trying to get maven  working the way we wanted.  I figured if we are 
going to move to  maven 100% we need to invest in writing  our own 
plugins, which I don't have time for now. I actually think our current 
ant build, with "usage help instructions" is quite a nice  system. If 
you are planning to stick around and want commit rights, just ask.

Mark
Geoffrey De Smet wrote:
> 1) Unused, broken import in:
> drools-compiler\src\main\java\org\drools\semantics\java\StaticMethodFunctionResolver.java 
>

Re: A few problems compiling the trunk

Thanks Mark

The issue for 4) is:
http://jira.jboss.com/jira/browse/JBRULES-539

The trunk now builds (I still had to fix 1) though),
but a good number of testcases failed (due to the important refactoring 
issupose), so I 'll stick with the branch for now for my program.
Once the trunk stabilizes again, I 'll be happy to test it out.

Thanks again.

With kind regards,
Geoffrey De Smet

Mark Proctor wrote:
> Geoffrey,
> 
> After the last few weeks manic performance work, where we broke 
> everything, we are now just in the process on getting trunk working 
> again and pushing out a milestone release.
> 
> 1)  (Fixed)
> 
> 2) See comment in jira
> 
> 3) Damn didn't mean to commit that eclipse project, it was just 
> something I was messing around with locally - sorry. (Fixed)
> 
> 4)  Will  look into this  soon.

Repository storage/mapping of DSLs and rule files - a design discussion.

Re: JBRULES-310 and primitives

Re: Re: pom.xml's in the trunk