[
https://issues.apache.org/jira/browse/ODE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787852#action_12787852
]
Alexis Midon commented on ODE-729:
----------------------------------
"In some scenarios the more complex maven dependency mechanisms for transitive
and scoped dependencies would be useful for ODE developers and users. "
what are these scenarios today?
I don't think we are badly missing the transitive dependency management today.
Assuming that we need it someday, it's likely that Buildr will have support it
in the meantime. There are already some development around that.
Buildr reuses a lot of maven conventions and brings the power and flexibility
of a scripting language. I'd be interested in knowing what the motivations for
Maven are.
IMHO going back to Maven will be a huge task... and regression.
> Consider moving to maven
> ------------------------
>
> Key: ODE-729
> URL: https://issues.apache.org/jira/browse/ODE-729
> Project: ODE
> Issue Type: New Feature
> Components: Build System
> Affects Versions: Wishlist
> Reporter: Greg Lucas
>
> This was recently discussed on IRC so I'm raising a JIRA to track further
> comments and gauge interest: Should ODE consider adopting a Maven 2 (or maven
> 3) build?
> Maven has become widely adopted for open source and is used for many popular
> Apache projects. Developers coming to ODE are likely to be familiar with
> maven and already be using tools (such as IDEs, continuous integration
> servers, etc) that have built-in support for maven poms. In some scenarios
> the more complex maven dependency mechanisms for transitive and scoped
> dependencies would be useful for ODE developers and users.
> Is the ODE community interested in a maven-based build? Can maven handle the
> complexities of ODE's packaging?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
