[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-5649) improve eclipse support with migration to gradle

[Strong Liu (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Strong Liu updated HHH-5649:
----------------------------

    Description: 
currently, I found the following problems when using gradle to generate the eclipse project metadata files:
* [GRADLE-1132|http://jira.codehaus.org/browse/GRADLE-1132] Gradle should generate .settings/org.eclipse.jdt.core.prefs
this means you may need set the project's compile level manually, ATM, jdk6
* [GRADLE-1074|http://jira.codehaus.org/browse/GRADLE-1074] Add eclipse variables to workspace.
the .classpath generated by gradle uses GRADLE_CACHE variable, and this need be added manually, just point it to your $user.home/.gradle/cache
* -jacc and ant are not in core's classpath
these two, (and actually others, such validtion, cglib, but these are added to both "provided" and "testRuntime" configuration) are only in the custom "provided" configuration, by default, eclipse plugin don't know how to deal with a customer configuration.- (done)
* -hibernate-core/src/main/antlr is incorrectly added into classpath- (add by antlr plugin)
* entitymanager's generate-src is not added into classpath


  was:
currently, I found the following problems when using gradle to generate the eclipse project metadata files:
* [GRADLE-1132|http://jira.codehaus.org/browse/GRADLE-1132] Gradle should generate .settings/org.eclipse.jdt.core.prefs
this means you may need set the project's compile level manually, ATM, jdk6
* [GRADLE-1074|http://jira.codehaus.org/browse/GRADLE-1074] Add eclipse variables to workspace.
the .classpath generated by gradle uses GRADLE_CACHE variable, and this need be added manually, just point it to your $user.home/.gradle/cache
* jacc and ant are not in core's classpath
these two, (and actually others, such validtion, cglib, but these are added to both "provided" and "testRuntime" configuration) are only in the custom "provided" configuration, by default, eclipse plugin don't know how to deal with a customer configuration.
* -hibernate-core/src/main/antlr is incorrectly added into classpath- (by antlr plugin)
* entitymanager's generate-src is not added into classpath



> improve eclipse support with migration to gradle
> ------------------------------------------------
>
>                 Key: HHH-5649
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5649
>             Project: Hibernate Core
>          Issue Type: Improvement
>            Reporter: Strong Liu
>            Assignee: Strong Liu
>             Fix For: 4.x
>
>
> currently, I found the following problems when using gradle to generate the eclipse project metadata files:
> * [GRADLE-1132|http://jira.codehaus.org/browse/GRADLE-1132] Gradle should generate .settings/org.eclipse.jdt.core.prefs
> this means you may need set the project's compile level manually, ATM, jdk6
> * [GRADLE-1074|http://jira.codehaus.org/browse/GRADLE-1074] Add eclipse variables to workspace.
> the .classpath generated by gradle uses GRADLE_CACHE variable, and this need be added manually, just point it to your $user.home/.gradle/cache
> * -jacc and ant are not in core's classpath
> these two, (and actually others, such validtion, cglib, but these are added to both "provided" and "testRuntime" configuration) are only in the custom "provided" configuration, by default, eclipse plugin don't know how to deal with a customer configuration.- (done)
> * -hibernate-core/src/main/antlr is incorrectly added into classpath- (add by antlr plugin)
> * entitymanager's generate-src is not added into classpath

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira