I'll look at it now before I go to bed - sorry :(

Mark
Michael Neale wrote:
have we applied this yet? I haven't had need to change a pom.xml yet, but will shortly, want to get these patches in place ASAP.

Thanks geoffrey

what do you mean by leaving it as "SNAPSHOT" ? I thought we did most of the time?

On 12/3/06, *Geoffrey De Smet* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    Be careful what you which for :)

    http://jira.jboss.com/jira/browse/JBRULES-576

    Please don't let it go stale - it's a lot of changes (only in the
    pom.xml files), but the jira explains them. Feel free to ping me
    (ge0ffrey.spam AT gmail.com <http://gmail.com>) if something is
    unclear.

    With kind regards,
    Geoffrey De Smet


    Michael Neale wrote:
    > please, do, patch away !
    >
    >
    > On 11/1/06, *Geoffrey De Smet* <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>
    > <mailto: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>>> wrote:
    >
    >     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
    >      >> 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>
> >> <groupId>org.apache.maven.plugins</groupId> > >> <artifactId>maven-resources-plugin</artifactId>
    >      >>                     <version> 2.2</version>
    >      >>                 </plugin>
    >      >> ...
    >      >>
    >      >
    >      >
    >      >
    ---------------------------------------------------------------------
    >      > To unsubscribe from this list please visit:
    >      >
    >      >    http://xircles.codehaus.org/manage_email
    >      >
    >      >
    >
    >
> ---------------------------------------------------------------------
    >     To unsubscribe from this list please visit:
    >
    >         http://xircles.codehaus.org/manage_email
    >
    >


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

         http://xircles.codehaus.org/manage_email



Reply via email to