openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <>
Subject [jira] Commented: (OPENJPA-779) patch for eclipse .project and .classpath files...
Date Tue, 25 Nov 2008 15:59:44 GMT


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

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:
>             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.

View raw message