[
https://issues.apache.org/jira/browse/GIRAPH-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396541#comment-13396541
]
Paolo Castagna commented on GIRAPH-207:
---------------------------------------
What people usually do with Eclipse is svn co ... + mvn eclipse:eclipse
They code or fix bugs and svn diff > filename.patch
This workflow does not work with 'munging' as explained above.
Not sure how fixing Maven and/or Eclipse can actually be done.
A short term solution is to create documentation on how to setup Eclipse with
Giraph properly.
A long term solution is to get rid of 'munging'. ;-)
> Eclipse's maven support is pointing its source directory to the munged sources
> ------------------------------------------------------------------------------
>
> Key: GIRAPH-207
> URL: https://issues.apache.org/jira/browse/GIRAPH-207
> Project: Giraph
> Issue Type: Bug
> Components: build
> Reporter: Jakob Homan
>
> Talking with Paolo, it appears that when one uses Eclipse with Maven, Eclipse
> points marks the munged source directory as the location where one edits the
> source, meaning they're working within /target. Which is bad, of course. We
> need to fix Maven and/or Eclipse to point towards the source directory.
--
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
