river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Reedy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-300) introduce maven to the river build process
Date Wed, 19 Jan 2011 15:14:45 GMT

    [ https://issues.apache.org/jira/browse/RIVER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983754#action_12983754
] 

Dennis Reedy commented on RIVER-300:
------------------------------------

So #1, #3 and #2 seems to be the priority?

Publishing artifacts to a Maven repository should be no problem with Gradle. Disclaimer: I
am learning Gradle as this goes along, so this should be fun :)

As far as moving forward with Maven and Gradle, I'd rather just choose one. My suggestion
is Gradle. 

Pros: 
- It handles multi-module projects better
- Very powerful and flexible
- It is Groovy based, so we can program our build scripts, plus get away from XML

Cons:
- Still early in it's process, not mature



> introduce maven to the river build process
> ------------------------------------------
>
>                 Key: RIVER-300
>                 URL: https://issues.apache.org/jira/browse/RIVER-300
>             Project: River
>          Issue Type: Improvement
>          Components: build
>            Reporter: Jools Enticknap
>         Attachments: apache-river-gradle.zip, apache-river-maven.zip, river-modularization-overview.odt,
river-modularization-overview.pdf
>
>
> Currently the river build using ant, but it's a custom build process and has many hang
overs from the original make build.
> Given that the project has no 3rd party dependencies, it would be very easy to break
the code up into modules.
> Please feel free to add to this JIRA if you have any opinions on how the maven repository
should be setup.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message