[
https://issues.apache.org/jira/browse/OPENJPA-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649975#action_12649975
]
Michael Dick commented on OPENJPA-779:
--------------------------------------
I'm opposed to putting .classpath and .project files in svn. There are multiple
ways to set up an eclipse environment and (single vs multiple project for
example) and I don't want to force developers down a specific path. I've
already tried convincing other devs that multiple projects is the right way to
go and I haven't had much luck.
I wouldn't mind putting example .classpath and .project files on the website if
people think it would help them.
Storing a standard set of formatting preferences is a very good idea and we
should add one either to svn or to the openjpa web site (maybe on the page
about code formatting).
> 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.
