[
https://issues.apache.org/jira/browse/OPENJPA-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650422#action_12650422
]
David Jencks commented on OPENJPA-779:
--------------------------------------
I'm not very involved in openjpa but...
I use idea, I don't appreciate people forcing configuration files for other
IDEs on me. Having them in a separate area from the code checkout wouldn't
disturb me.
If I did use eclipse I expect I'd use m2eclipse rather than mvn
eclipse:eclipse. I haven't tried it but have the impression that it lets you
open the project via the pom rather than having to run maven to generate
eclipse files. I might be dreaming since this is what IDEA lets you do.
I also doubt that such eclipse files could be kept up to date. Certainly if I
contributed something to openjpa I wouldn't be able to update the 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.
