I am investigating and experimenting using the contributed POMs (thanks Dennis).
Currently, I have all artifacts deploying to a locally setup Maven repository from the Ant build.xml, so that's good. I have used the Maven Ant tasks - http://maven.apache.org/ant-tasks Now the downside is this introduces a dependency on the Maven Ant tasks JAR (Ant needs it in its classpath). I believe the Ant instance Hudson uses to build has these tasks installed, but I need to check to be sure. Any thoughts on handling this dependency? Another thing I would like to do is change the current version number of the project to from 2.1.1 (which is actually incorrect, 2.1.1 was released a long time ago) to 2.2-SNAPSHOT, to match the Maven artifact version numbering (which makes a lot of sense anyway). As soon as we decide to push out AR2, we can change this to 2.2.0? Or should it be 2.2? Comments on this? Thanks Jonathan Op woensdag 30-09-2009 om 17:14 uur [tijdzone +1000], schreef Peter Firmstone: > Jeff contributed a patch containing pom's for the River dist jar files, > which I've added to the main trunk, however it isn't clear how the > download files for service clients are handled, Dennis has made some > suggestions, however I'm going to need some help with this. > > Feel free to check out and have a play. > > Thanks in advance, > > Peter. > > Patrick Wright wrote: > > Hi Peter > > > > Can you update us on the status of River vis-a-vis Maven? How far > > along are you in creating the POM(s) for the build system? What is > > missing? > > > > > > Thanks > > Patrick > > > > On Wed, Sep 30, 2009 at 8:48 AM, Peter Firmstone <[email protected]> wrote: > > > >> Anyone have any ideas or willing to assist with patches? It'd be nice to > >> have this complete for AR2. > >> > >> Cheers, > >> > >> Peter. > >> > >> Dennis Reedy (JIRA) wrote: > >> > >>> [ > >>> https://issues.apache.org/jira/browse/RIVER-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760243#action_12760243 > >>> ] > >>> Dennis Reedy commented on RIVER-317: > >>> ------------------------------------ > >>> > >>> I dont see how the -dl.jar files are being handled with this approach. How > >>> will the -dl.jar files for reggie, outrigger, mahalo (etc...) be defined? > >>> With River services we have multiple artifacts per service, an > >>> implementation jar, a download (client) jar and potentially a service ui > >>> jar. > >>> I suggest that we need to be thinking of adding classifiers for the > >>> artifacts, allowing dependencies to be resolved correctly. For example, > >>> if I > >>> am using Outrigger, I need to be able to start Outrigger using > >>> outrigger.jar > >>> and outrigger-dl.jar, but my client (the one who uses Outrigger) needs to > >>> only have outigger-dl.jar in it's classpath not outrigger.jar. > >>> > >>> Declaring dependencies on River produced maven artifacts need to account > >>> for how a maven project will use the artifacts. > >>> > >>> > >>>> Deploy Apache River artifacts to Maven repositories (both release and > >>>> snapshot) > >>>> > >>>> ------------------------------------------------------------------------------- > >>>> > >>>> Key: RIVER-317 > >>>> URL: https://issues.apache.org/jira/browse/RIVER-317 > >>>> Project: River > >>>> Issue Type: Task > >>>> Components: Web site and infrastructure > >>>> Affects Versions: AR2, AR3 > >>>> Reporter: Jeff Ramsdale > >>>> Fix For: AR2 > >>>> > >>>> Attachments: river-poms.patch > >>>> > >>>> > >>>> It would be valuable if Apache River artifacts were deployed to a Maven > >>>> repository upon release. It would be even better if snapshot builds were > >>>> also deployed to a snapshot repository by Hudson. > >>>> See thread: > >>>> http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200908.mbox/<[email protected]> > >>>> > >>>> > >>> > >> > > > > >
