[
https://issues.apache.org/jira/browse/MAHOUT-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410149#comment-13410149
]
Sean Owen commented on MAHOUT-1043:
-----------------------------------
Can you make a patch? if it doesn't affect the Maven build (or fixes the rest
of it to match your changes), which is the official one, that's fine.
Cleanup of the Maven pom.xml is also quite good if that's what you are
referring to.
What I don't want to get into is letting the cart pull the horse by deciding we
can/can't do stuff in the build because of m2e or any other plugin.
> Support building project with m2e plugin in eclipse
> ---------------------------------------------------
>
> Key: MAHOUT-1043
> URL: https://issues.apache.org/jira/browse/MAHOUT-1043
> Project: Mahout
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.7
> Reporter: Stevo Slavic
>
> See
> [this|http://stackoverflow.com/questions/11282737/errors-when-importing-mahouts-maven-resource-to-eclipse]
> and
> [this|http://lucene.472066.n3.nabble.com/Eclipse-Mahout-Maven-maven-antrun-plugin-error-td3969446.html]
> and
> [this|http://mail-archives.apache.org/mod_mbox/mahout-user/201207.mbox/%3CCAK4b6ue2gtpJHz5gDZ%2BZ0_ZpccsiXecQCGfYtBCx6t%3D5ip6Sjw%40mail.gmail.com%3E]
> for examples on various issues developers have when trying to import and
> build Apache Mahout using eclipse and m2e plugin. Build scripts in sources
> seem to favour Apache Ant and maven-eclipse-plugin, while Apache Maven 3 and
> m2e are more popular build tool choices nowadays.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
