[
https://issues.apache.org/jira/browse/OPENJPA-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650601#action_12650601
]
Michael Dick commented on OPENJPA-779:
--------------------------------------
As developers can't we all just agree to use vi instead of emacs :-) ?
I don't particularly mind how the other contributors organize their IDE, or
which IDE they use so long as the code builds with maven (and it works
correctly). I also don't want to worry about my IDE updating it's config file
to an openjpa project (ie pydev) because I added some artifact that I haven't
contributed. It's one more thing I have to revert or redo before I commit.
Is "svn up; import" that much better than "svn up; mvn eclipse:eclipse;import"
?
WRT the maven plugin for eclipse David's right. I don't use it at the moment
because it triggers full maven builds a bit too often for me (probably
configurable). It also adds a custom builder to the .project file which can be
a problem if .project is in version control.
We can certainly propose a vote on the dev mailing list though. If I'm in the
clear minority then we can commit the IDE specific files.
> patch for eclipse .project and .classpath files...
> --------------------------------------------------
>
> Key: OPENJPA-779
> URL: https://issues.apache.org/jira/browse/OPENJPA-779
> Project: OpenJPA
> Issue Type: Improvement
> Components: build / infrastructure
> Affects Versions: 1.2.0
> Reporter: Fernando
> Attachments: .classpath, eclipse.diff, openjpa-formatter.xml
>
>
> these are the .project and .classpath files generated by running mvn
> eclipse:eclipse, so that people can develop with eclipse without any further
> work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
