[
https://issues.apache.org/jira/browse/OPENJPA-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650401#action_12650401
]
Fernando commented on OPENJPA-779:
----------------------------------
So.. as a group we can't decide to just pick one project or many projects??
really??
that seems like such a trivial thing that should just get decided.
I vote for multiple projects, just because mvn eclipse:eclipse will then
maintain all of the .classpath and .project for us :)
But I also use other projects ( tapestry.apache.org ) that they do one large
project. And really, it doesn't make a difference to me. I can easy
import/delete/close/open a list of projects just as easily as I can do it for
one project. The only requirement is that all sub-projects should start with
the same prefix.. to be easy to find and identify within my workspace ( and
we're already doing that.. openjpa-* ).
I've asked before, but who are the active developers on the project? how can
we go about getting a vote going? any new developer should just be able to svn
up, eclipse import, and go!
> 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.
