7:45 a.m.
I have switched HEAD of hibernate-core to use Gradle for builds. I still need
to finish up some tasks, but they mostly deal with the release process for
which I created a follow-up issue.
You can either install Gradle and use the gradle command, or you can use
"gradle wrapper" by using the ./gradlew (or ./gradlew.bat files for our Windows
friends).
---------- Forwarded Message ----------
Subject: [Hibernate-JIRA] Closed: (HHH-5616) Switch to Gradle for builds
Date: Monday, October 11, 2010, 04:46:57 pm
From: "Steve Ebersole (JIRA)" <noreply(a)atlassian.com>
To: steve(a)hibernate.org
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616?page=c...
tabpanel ]
Steve Ebersole closed HHH-5616.
-------------------------------
Resolution: Fixed
Switch to Gradle for builds
---------------------------
Key: HHH-5616
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616
Project: Hibernate Core
Issue Type: Task
Components: core
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 4.0.0.Alpha1
Time Spent: 23h
Remaining Estimate: 0h
http://gradle.org
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-----------------------------------------
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
10:58 a.m.
I should have pointed out some of the basic commands you'll commonly need.
All these can be found in the Gradle User Guide:
http://www.gradle.org/0.9-rc-1/docs/userguide/userguide_single.html
Most of the stuff we are interested in comes from the Java plugin:
http://www.gradle.org/0.9-
rc-1/docs/userguide/userguide_single.html#java_plugin
Here is a list of the ones you will currently be using (from any project in
gradle you can get a list of available tasks by executing `gradle -t`):
1) build - Assembles (jars) and tests this project.
2) buildDependents - Assembles and tests this project and all projects that
depend on it. So think of running this in hibernnate-entitymanager.. Gradle
would assemble and test hibernate-entitymanager as well as hibernate-envers
(because envers depends on entitymanager).
3) classes - compiles the main classes
4) clean - Deletes the build directory.
5) jar - Generates a jar archive with all the compiled classes.
6) testClasses - Assembles the test classes.
7) test - Runs the unit tests
8) uploadArchives - think Maven deploy
Especially those of you developing Search, Validator, etc should know about an
additional task:
9) install - installs the project jar to your local maven cache (aka
~/,m2/repository)
In the root project you can perform any task and Gradle will attempt to
perform it on each subproject.
That should be enough to get you going.
Oh and you can also execute multiple tasks:
`gradle clean build` runs both the clean and build tasks
On Monday, October 11, 2010 05:45:29 pm Steve Ebersole wrote:
I have switched HEAD of hibernate-core to use Gradle for builds. I
still
need to finish up some tasks, but they mostly deal with the release
process for which I created a follow-up issue.
You can either install Gradle and use the gradle command, or you can use
"gradle wrapper" by using the ./gradlew (or ./gradlew.bat files for our
Windows friends).
---------- Forwarded Message ----------
Subject: [Hibernate-JIRA] Closed: (HHH-5616) Switch to Gradle for builds
Date: Monday, October 11, 2010, 04:46:57 pm
From: "Steve Ebersole (JIRA)" <noreply(a)atlassian.com>
To: steve(a)hibernate.org
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616?page=com
.atlassian.jira.plugin.system.issuetabpanels:all- tabpanel ]
Steve Ebersole closed HHH-5616.
-------------------------------
Resolution: Fixed
> Switch to Gradle for builds
> ---------------------------
>
> Key: HHH-5616
> URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616
> Project: Hibernate Core
>
> Issue Type: Task
> Components: core
>
> Reporter: Steve Ebersole
> Assignee: Steve Ebersole
>
> Fix For: 4.0.0.Alpha1
>
> Time Spent: 23h
>
> Remaining Estimate: 0h
>
> http://gradle.org
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
6:56 p.m.
I've played with master and gradle this morning. So far so good. I have two issues
though:
1. (gradle build) the test suite shows massive failures (3082 tests completed, 2371
failures or something along those lines) is that expected?
2. changing branches between a mvn style approach and a gradle style approach or even
between gradle branches
One super awesome feature of the combo Idea + Maven POM's + Git was the ability to
move from one branch to another (even with a different pom structure) and be ready to work
after 10 to 20s max. Idea was detecting the pom structure changes (new modules or not) and
was refreshing the project structure on the fly and and off we go.
With Gradle, this kind of support does not seem to exist. The closest I have found is to
run gradle idea with takes between 1min30 and OOME(*) assuming all deps are downloaded
already. On top of that Idea goes wacko so you have to close and reopen the project in
Idea which with reindexing easily takes another 2 mins 30
It gets more complicated when switching between branches that use different build tools
(mvn and gradle).
When moving from Gradle to mvn, the IDE of course does not remember it has to react to pom
files and the fastest solution is to reimport from scratch which means a good 3 minutes (I
tried mvn idea:idea but it did not seem to create a working project on me).
Does anyone has a better/faster workflow? I have to admit, I will miss a lot the instant
branching, that helped me to be massively more productive.
Emmanuel
(*) Make sure to add GRADLE_OPTS=-Xmx512m
On 12 oct. 2010, at 03:58, Steve Ebersole wrote:
I should have pointed out some of the basic commands you'll
commonly need.
All these can be found in the Gradle User Guide:
http://www.gradle.org/0.9-rc-1/docs/userguide/userguide_single.html
Most of the stuff we are interested in comes from the Java plugin:
http://www.gradle.org/0.9-
rc-1/docs/userguide/userguide_single.html#java_plugin
Here is a list of the ones you will currently be using (from any project in
gradle you can get a list of available tasks by executing `gradle -t`):
1) build - Assembles (jars) and tests this project.
2) buildDependents - Assembles and tests this project and all projects that
depend on it. So think of running this in hibernnate-entitymanager.. Gradle
would assemble and test hibernate-entitymanager as well as hibernate-envers
(because envers depends on entitymanager).
3) classes - compiles the main classes
4) clean - Deletes the build directory.
5) jar - Generates a jar archive with all the compiled classes.
6) testClasses - Assembles the test classes.
7) test - Runs the unit tests
8) uploadArchives - think Maven deploy
Especially those of you developing Search, Validator, etc should know about an
additional task:
9) install - installs the project jar to your local maven cache (aka
~/,m2/repository)
In the root project you can perform any task and Gradle will attempt to
perform it on each subproject.
That should be enough to get you going.
Oh and you can also execute multiple tasks:
`gradle clean build` runs both the clean and build tasks
On Monday, October 11, 2010 05:45:29 pm Steve Ebersole wrote:
> I have switched HEAD of hibernate-core to use Gradle for builds. I still
> need to finish up some tasks, but they mostly deal with the release
> process for which I created a follow-up issue.
>
> You can either install Gradle and use the gradle command, or you can use
> "gradle wrapper" by using the ./gradlew (or ./gradlew.bat files for our
> Windows friends).
>
> ---------- Forwarded Message ----------
>
> Subject: [Hibernate-JIRA] Closed: (HHH-5616) Switch to Gradle for builds
> Date: Monday, October 11, 2010, 04:46:57 pm
> From: "Steve Ebersole (JIRA)" <noreply(a)atlassian.com>
> To: steve(a)hibernate.org
>
>
> [
> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616?page=com
> .atlassian.jira.plugin.system.issuetabpanels:all- tabpanel ]
>
> Steve Ebersole closed HHH-5616.
> -------------------------------
>
> Resolution: Fixed
>
>> Switch to Gradle for builds
>> ---------------------------
>>
>> Key: HHH-5616
>
>> URL:
> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616
>
>> Project: Hibernate Core
>>
>> Issue Type: Task
>> Components: core
>>
>> Reporter: Steve Ebersole
>> Assignee: Steve Ebersole
>>
>> Fix For: 4.0.0.Alpha1
>>
>> Time Spent: 23h
>>
>> Remaining Estimate: 0h
>>
>> http://gradle.org
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
12:02 a.m.
Missed this earlier somehow...
On Tuesday, October 12, 2010, at 04:56 am, Emmanuel Bernard wrote:
1. (gradle build) the test suite shows massive failures
(3082 tests completed, 2371 failures or something along those lines) is
that expected?
That was an odd timing related issue which effected some people/machines and
not others. The underlying cause has since been fixed so you should not be
having test failures any more.
2. changing branches between a mvn style approach and a
gradle style approach or even between gradle branches
TBH I never expected this to work. And that had nothing to do with Maven
versus Gradle. Hibernate 4 will be drastically different from Hibernate 3 in
many of the same ways Hibernate 3 was different from Hibernate 2. I did not
ever expect this behavior moving from 2 -> 3, and I did not moving from 3 ->
4.
One super awesome feature of the combo Idea + Maven POM's + Git
was the
ability to move from one branch to another (even with a different pom
structure) and be ready to work after 10 to 20s max. Idea was detecting
the pom structure changes (new modules or not) and was refreshing the
project structure on the fly and and off we go.
See above.
With Gradle, this kind of support does not seem to exist. The closest
I
have found is to run gradle idea with takes between 1min30 and OOME(*)
assuming all deps are downloaded already. On top of that Idea goes wacko
so you have to close and reopen the project in Idea which with reindexing
easily takes another 2 mins 30
IntelliJ does not support importing (nor therefore monitoring) of a Gradle
project. http://youtrack.jetbrains.net/issue/IDEA-53476?projectKey=IDEA if
that is important to you.
But even if it did, I am not sure recognizing an on-the-fly switch between a
Maven-backed project and a Gradle-backed one is "on the docket" there.
Personally I do not see even remotely close to these times. I see on average
30-40 seconds to run `gradle idea`. Yes then you must resync the IntelliJ
project, which I do not have an accurate means to measure but which *feels*
like it takes another 20-30 seconds, most of which is the (re)indexing you
mention. By the way, I had the same exact reindexing happening with
IntelliJ+Maven after "reimporting".
BTW, you do not have to close/(re)open the project. Just select the root
directory and hit synchronize.
It gets more complicated when switching between branches that use different
build tools (mvn and gradle). When moving from Gradle to mvn, the IDE of
course does not remember it has to react to pom files and the fastest
solution is to reimport from scratch which means a good 3 minutes (I tried
mvn idea:idea but it did not seem to create a working project on me).
See above.
Does anyone has a better/faster workflow? I have to admit, I will miss a
lot the instant branching, that helped me to be massively more productive.
I actually have 2 clones. One that I use for work on 3.6 (Maven) and another
that I use for 4.x work (Gradle). Like I said, I have no problems (not the
performance issues you seem to imply anyway) switching between say master and
some topic branch I create for 4.x work.
(*) Make sure to add GRADLE_OPTS=-Xmx512m
I use the same settings I had to use for Maven. On my Linux machine I set
these up in my ~/.profile settings (which is how I am used to it from Solaris
days). I simply link that in from ~/.bashrc, though you could of course add
these directly to ~/.bashrc:
#Maven defs
export MAVEN_HOME=/opt/maven/current
export M2_HOME=$MAVEN_HOME
export MAVEN_OPTS="-Xmx1024m -Xms512m"
#Gradle defs
export GRADLE_HOME=/opt/gradle/current
export GRADLE_OPTS="-Xmx1024m -Xms512m"
"current" is another cool little trick. Its a symlink to the
"current"
install.
---
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
3:07 a.m.
FYI, I wrapped this up into a blog entry:
http://in.relation.to/Bloggers/HibernateGradlePointers
On Monday, October 11, 2010, at 08:58 pm, Steve Ebersole wrote:
I should have pointed out some of the basic commands you'll
commonly need.
All these can be found in the Gradle User Guide:
http://www.gradle.org/0.9-rc-1/docs/userguide/userguide_single.html
Most of the stuff we are interested in comes from the Java plugin:
http://www.gradle.org/0.9-
rc-1/docs/userguide/userguide_single.html#java_plugin
Here is a list of the ones you will currently be using (from any project in
gradle you can get a list of available tasks by executing `gradle -t`):
1) build - Assembles (jars) and tests this project.
2) buildDependents - Assembles and tests this project and all projects that
depend on it. So think of running this in hibernnate-entitymanager..
Gradle would assemble and test hibernate-entitymanager as well as
hibernate-envers (because envers depends on entitymanager).
3) classes - compiles the main classes
4) clean - Deletes the build directory.
5) jar - Generates a jar archive with all the compiled classes.
6) testClasses - Assembles the test classes.
7) test - Runs the unit tests
8) uploadArchives - think Maven deploy
Especially those of you developing Search, Validator, etc should know about
an additional task:
9) install - installs the project jar to your local maven cache (aka
~/,m2/repository)
In the root project you can perform any task and Gradle will attempt to
perform it on each subproject.
That should be enough to get you going.
Oh and you can also execute multiple tasks:
`gradle clean build` runs both the clean and build tasks
On Monday, October 11, 2010 05:45:29 pm Steve Ebersole wrote:
> I have switched HEAD of hibernate-core to use Gradle for builds. I still
> need to finish up some tasks, but they mostly deal with the release
> process for which I created a follow-up issue.
>
> You can either install Gradle and use the gradle command, or you can use
> "gradle wrapper" by using the ./gradlew (or ./gradlew.bat files for our
> Windows friends).
>
> ---------- Forwarded Message ----------
>
> Subject: [Hibernate-JIRA] Closed: (HHH-5616) Switch to Gradle for builds
> Date: Monday, October 11, 2010, 04:46:57 pm
> From: "Steve Ebersole (JIRA)" <noreply(a)atlassian.com>
> To: steve(a)hibernate.org
>
> [
>
> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616?page=c
> om .atlassian.jira.plugin.system.issuetabpanels:all- tabpanel ]
>
> Steve Ebersole closed HHH-5616.
> -------------------------------
>
> Resolution: Fixed
> >
> > Switch to Gradle for builds
> > ---------------------------
> >
> > Key: HHH-5616
>
> > URL:
> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616
>
> > Project: Hibernate Core
> >
> > Issue Type: Task
> > Components: core
> >
> > Reporter: Steve Ebersole
> > Assignee: Steve Ebersole
> >
> > Fix For: 4.0.0.Alpha1
> >
> > Time Spent: 23h
> >
> > Remaining Estimate: 0h
> >
> > http://gradle.org
---
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
7:43 p.m.
Where are you supposed to execute 'gradle idea' from? If I execute it from the
root, the IML files created are pointing to the wrong dependencies, i.e.:
•
/Users/.gradle/cache/org.infinispan/infinispan-core/jars/infinispan-core-4.2.0.ALPHA1.jar
Clearly, this should be pointing to:
•
/Users/z/.gradle/cache/org.infinispan/infinispan-core/jars/infinispan-core-4.2.0.ALPHA1.jar
Any idea what is wrong? I can't compile anything from IDEA
On Oct 14, 2010, at 8:07 PM, Steve Ebersole wrote:
FYI, I wrapped this up into a blog entry:
http://in.relation.to/Bloggers/HibernateGradlePointers
On Monday, October 11, 2010, at 08:58 pm, Steve Ebersole wrote:
> I should have pointed out some of the basic commands you'll commonly need.
> All these can be found in the Gradle User Guide:
> http://www.gradle.org/0.9-rc-1/docs/userguide/userguide_single.html
>
> Most of the stuff we are interested in comes from the Java plugin:
> http://www.gradle.org/0.9-
> rc-1/docs/userguide/userguide_single.html#java_plugin
>
> Here is a list of the ones you will currently be using (from any project in
> gradle you can get a list of available tasks by executing `gradle -t`):
>
> 1) build - Assembles (jars) and tests this project.
> 2) buildDependents - Assembles and tests this project and all projects that
> depend on it. So think of running this in hibernnate-entitymanager..
> Gradle would assemble and test hibernate-entitymanager as well as
> hibernate-envers (because envers depends on entitymanager).
> 3) classes - compiles the main classes
> 4) clean - Deletes the build directory.
> 5) jar - Generates a jar archive with all the compiled classes.
> 6) testClasses - Assembles the test classes.
> 7) test - Runs the unit tests
> 8) uploadArchives - think Maven deploy
>
> Especially those of you developing Search, Validator, etc should know about
> an additional task:
> 9) install - installs the project jar to your local maven cache (aka
> ~/,m2/repository)
>
> In the root project you can perform any task and Gradle will attempt to
> perform it on each subproject.
>
> That should be enough to get you going.
>
> Oh and you can also execute multiple tasks:
> `gradle clean build` runs both the clean and build tasks
>
> On Monday, October 11, 2010 05:45:29 pm Steve Ebersole wrote:
>> I have switched HEAD of hibernate-core to use Gradle for builds. I still
>> need to finish up some tasks, but they mostly deal with the release
>> process for which I created a follow-up issue.
>>
>> You can either install Gradle and use the gradle command, or you can use
>> "gradle wrapper" by using the ./gradlew (or ./gradlew.bat files for
our
>> Windows friends).
>>
>> ---------- Forwarded Message ----------
>>
>> Subject: [Hibernate-JIRA] Closed: (HHH-5616) Switch to Gradle for builds
>> Date: Monday, October 11, 2010, 04:46:57 pm
>> From: "Steve Ebersole (JIRA)" <noreply(a)atlassian.com>
>> To: steve(a)hibernate.org
>>
>> [
>>
>> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616?page=c
>> om .atlassian.jira.plugin.system.issuetabpanels:all- tabpanel ]
>>
>> Steve Ebersole closed HHH-5616.
>> -------------------------------
>>
>> Resolution: Fixed
>>>
>>> Switch to Gradle for builds
>>> ---------------------------
>>>
>>> Key: HHH-5616
>>
>>> URL:
>> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616
>>
>>> Project: Hibernate Core
>>>
>>> Issue Type: Task
>>> Components: core
>>>
>>> Reporter: Steve Ebersole
>>> Assignee: Steve Ebersole
>>>
>>> Fix For: 4.0.0.Alpha1
>>>
>>> Time Spent: 23h
>>>
>>> Remaining Estimate: 0h
>>>
>>> http://gradle.org
---
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
7:58 p.m.
And to top it up, since move to gradle, my testsuite hangs in a test where it never used
to do before.
So, so far, pretty unhappy about the move to gradle :(
On Oct 15, 2010, at 12:43 PM, Galder Zamarreño wrote:
Where are you supposed to execute 'gradle idea' from? If I
execute it from the root, the IML files created are pointing to the wrong dependencies,
i.e.:
•
/Users/.gradle/cache/org.infinispan/infinispan-core/jars/infinispan-core-4.2.0.ALPHA1.jar
Clearly, this should be pointing to:
•
/Users/z/.gradle/cache/org.infinispan/infinispan-core/jars/infinispan-core-4.2.0.ALPHA1.jar
Any idea what is wrong? I can't compile anything from IDEA
On Oct 14, 2010, at 8:07 PM, Steve Ebersole wrote:
> FYI, I wrapped this up into a blog entry:
> http://in.relation.to/Bloggers/HibernateGradlePointers
>
>
> On Monday, October 11, 2010, at 08:58 pm, Steve Ebersole wrote:
>> I should have pointed out some of the basic commands you'll commonly need.
>> All these can be found in the Gradle User Guide:
>> http://www.gradle.org/0.9-rc-1/docs/userguide/userguide_single.html
>>
>> Most of the stuff we are interested in comes from the Java plugin:
>> http://www.gradle.org/0.9-
>> rc-1/docs/userguide/userguide_single.html#java_plugin
>>
>> Here is a list of the ones you will currently be using (from any project in
>> gradle you can get a list of available tasks by executing `gradle -t`):
>>
>> 1) build - Assembles (jars) and tests this project.
>> 2) buildDependents - Assembles and tests this project and all projects that
>> depend on it. So think of running this in hibernnate-entitymanager..
>> Gradle would assemble and test hibernate-entitymanager as well as
>> hibernate-envers (because envers depends on entitymanager).
>> 3) classes - compiles the main classes
>> 4) clean - Deletes the build directory.
>> 5) jar - Generates a jar archive with all the compiled classes.
>> 6) testClasses - Assembles the test classes.
>> 7) test - Runs the unit tests
>> 8) uploadArchives - think Maven deploy
>>
>> Especially those of you developing Search, Validator, etc should know about
>> an additional task:
>> 9) install - installs the project jar to your local maven cache (aka
>> ~/,m2/repository)
>>
>> In the root project you can perform any task and Gradle will attempt to
>> perform it on each subproject.
>>
>> That should be enough to get you going.
>>
>> Oh and you can also execute multiple tasks:
>> `gradle clean build` runs both the clean and build tasks
>>
>> On Monday, October 11, 2010 05:45:29 pm Steve Ebersole wrote:
>>> I have switched HEAD of hibernate-core to use Gradle for builds. I still
>>> need to finish up some tasks, but they mostly deal with the release
>>> process for which I created a follow-up issue.
>>>
>>> You can either install Gradle and use the gradle command, or you can use
>>> "gradle wrapper" by using the ./gradlew (or ./gradlew.bat files for
our
>>> Windows friends).
>>>
>>> ---------- Forwarded Message ----------
>>>
>>> Subject: [Hibernate-JIRA] Closed: (HHH-5616) Switch to Gradle for builds
>>> Date: Monday, October 11, 2010, 04:46:57 pm
>>> From: "Steve Ebersole (JIRA)" <noreply(a)atlassian.com>
>>> To: steve(a)hibernate.org
>>>
>>> [
>>>
>>> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616?page=c
>>> om .atlassian.jira.plugin.system.issuetabpanels:all- tabpanel ]
>>>
>>> Steve Ebersole closed HHH-5616.
>>> -------------------------------
>>>
>>> Resolution: Fixed
>>>>
>>>> Switch to Gradle for builds
>>>> ---------------------------
>>>>
>>>> Key: HHH-5616
>>>
>>>> URL:
>>> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616
>>>
>>>> Project: Hibernate Core
>>>>
>>>> Issue Type: Task
>>>> Components: core
>>>>
>>>> Reporter: Steve Ebersole
>>>> Assignee: Steve Ebersole
>>>>
>>>> Fix For: 4.0.0.Alpha1
>>>>
>>>> Time Spent: 23h
>>>>
>>>> Remaining Estimate: 0h
>>>>
>>>> http://gradle.org
>
> ---
> Steve Ebersole <steve(a)hibernate.org>
> http://hibernate.org
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
8:05 p.m.
And since I can't run the test that hangs from IDEA without manually fixing the paths,
I can't easily figure out whether the failure is due to gradle or changes within
Hibernate.
On Oct 15, 2010, at 12:58 PM, Galder Zamarreño wrote:
And to top it up, since move to gradle, my testsuite hangs in a test
where it never used to do before.
So, so far, pretty unhappy about the move to gradle :(
On Oct 15, 2010, at 12:43 PM, Galder Zamarreño wrote:
> Where are you supposed to execute 'gradle idea' from? If I execute it from
the root, the IML files created are pointing to the wrong dependencies, i.e.:
>
> •
/Users/.gradle/cache/org.infinispan/infinispan-core/jars/infinispan-core-4.2.0.ALPHA1.jar
>
> Clearly, this should be pointing to:
>
> •
/Users/z/.gradle/cache/org.infinispan/infinispan-core/jars/infinispan-core-4.2.0.ALPHA1.jar
>
> Any idea what is wrong? I can't compile anything from IDEA
>
> On Oct 14, 2010, at 8:07 PM, Steve Ebersole wrote:
>
>> FYI, I wrapped this up into a blog entry:
>> http://in.relation.to/Bloggers/HibernateGradlePointers
>>
>>
>> On Monday, October 11, 2010, at 08:58 pm, Steve Ebersole wrote:
>>> I should have pointed out some of the basic commands you'll commonly
need.
>>> All these can be found in the Gradle User Guide:
>>> http://www.gradle.org/0.9-rc-1/docs/userguide/userguide_single.html
>>>
>>> Most of the stuff we are interested in comes from the Java plugin:
>>> http://www.gradle.org/0.9-
>>> rc-1/docs/userguide/userguide_single.html#java_plugin
>>>
>>> Here is a list of the ones you will currently be using (from any project in
>>> gradle you can get a list of available tasks by executing `gradle -t`):
>>>
>>> 1) build - Assembles (jars) and tests this project.
>>> 2) buildDependents - Assembles and tests this project and all projects that
>>> depend on it. So think of running this in hibernnate-entitymanager..
>>> Gradle would assemble and test hibernate-entitymanager as well as
>>> hibernate-envers (because envers depends on entitymanager).
>>> 3) classes - compiles the main classes
>>> 4) clean - Deletes the build directory.
>>> 5) jar - Generates a jar archive with all the compiled classes.
>>> 6) testClasses - Assembles the test classes.
>>> 7) test - Runs the unit tests
>>> 8) uploadArchives - think Maven deploy
>>>
>>> Especially those of you developing Search, Validator, etc should know about
>>> an additional task:
>>> 9) install - installs the project jar to your local maven cache (aka
>>> ~/,m2/repository)
>>>
>>> In the root project you can perform any task and Gradle will attempt to
>>> perform it on each subproject.
>>>
>>> That should be enough to get you going.
>>>
>>> Oh and you can also execute multiple tasks:
>>> `gradle clean build` runs both the clean and build tasks
>>>
>>> On Monday, October 11, 2010 05:45:29 pm Steve Ebersole wrote:
>>>> I have switched HEAD of hibernate-core to use Gradle for builds. I
still
>>>> need to finish up some tasks, but they mostly deal with the release
>>>> process for which I created a follow-up issue.
>>>>
>>>> You can either install Gradle and use the gradle command, or you can use
>>>> "gradle wrapper" by using the ./gradlew (or ./gradlew.bat files
for our
>>>> Windows friends).
>>>>
>>>> ---------- Forwarded Message ----------
>>>>
>>>> Subject: [Hibernate-JIRA] Closed: (HHH-5616) Switch to Gradle for builds
>>>> Date: Monday, October 11, 2010, 04:46:57 pm
>>>> From: "Steve Ebersole (JIRA)" <noreply(a)atlassian.com>
>>>> To: steve(a)hibernate.org
>>>>
>>>> [
>>>>
>>>>
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616?page=c
>>>> om .atlassian.jira.plugin.system.issuetabpanels:all- tabpanel ]
>>>>
>>>> Steve Ebersole closed HHH-5616.
>>>> -------------------------------
>>>>
>>>> Resolution: Fixed
>>>>>
>>>>> Switch to Gradle for builds
>>>>> ---------------------------
>>>>>
>>>>> Key: HHH-5616
>>>>
>>>>> URL:
>>>> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616
>>>>
>>>>> Project: Hibernate Core
>>>>>
>>>>> Issue Type: Task
>>>>> Components: core
>>>>>
>>>>> Reporter: Steve Ebersole
>>>>> Assignee: Steve Ebersole
>>>>>
>>>>> Fix For: 4.0.0.Alpha1
>>>>>
>>>>> Time Spent: 23h
>>>>>
>>>>> Remaining Estimate: 0h
>>>>>
>>>>> http://gradle.org
>>
>> ---
>> Steve Ebersole <steve(a)hibernate.org>
>> http://hibernate.org
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
> --
> Galder Zamarreño
> Sr. Software Engineer
> Infinispan, JBoss Cache
>
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
8:17 p.m.
On Oct 15, 2010, at 1:05 PM, Galder Zamarreño wrote:
And since I can't run the test that hangs from IDEA without
manually fixing the paths, I can't easily figure out whether the failure is due to
gradle or changes within Hibernate.
On Oct 15, 2010, at 12:58 PM, Galder Zamarreño wrote:
> And to top it up, since move to gradle, my testsuite hangs in a test where it never
used to do before.
>
> So, so far, pretty unhappy about the move to gradle :(
>
> On Oct 15, 2010, at 12:43 PM, Galder Zamarreño wrote:
>
>> Where are you supposed to execute 'gradle idea' from? If I execute it
from the root, the IML files created are pointing to the wrong dependencies, i.e.:
>>
>> •
/Users/.gradle/cache/org.infinispan/infinispan-core/jars/infinispan-core-4.2.0.ALPHA1.jar
>>
>> Clearly, this should be pointing to:
>>
>> •
/Users/z/.gradle/cache/org.infinispan/infinispan-core/jars/infinispan-core-4.2.0.ALPHA1.jar
>>
>> Any idea what is wrong? I can't compile anything from IDEA
I've tried running the following from the root of hibernate and no luck:
gradle cleanIdea idea
>>
>> On Oct 14, 2010, at 8:07 PM, Steve Ebersole wrote:
>>
>>> FYI, I wrapped this up into a blog entry:
>>> http://in.relation.to/Bloggers/HibernateGradlePointers
>>>
>>>
>>> On Monday, October 11, 2010, at 08:58 pm, Steve Ebersole wrote:
>>>> I should have pointed out some of the basic commands you'll commonly
need.
>>>> All these can be found in the Gradle User Guide:
>>>> http://www.gradle.org/0.9-rc-1/docs/userguide/userguide_single.html
>>>>
>>>> Most of the stuff we are interested in comes from the Java plugin:
>>>> http://www.gradle.org/0.9-
>>>> rc-1/docs/userguide/userguide_single.html#java_plugin
>>>>
>>>> Here is a list of the ones you will currently be using (from any project
in
>>>> gradle you can get a list of available tasks by executing `gradle -t`):
>>>>
>>>> 1) build - Assembles (jars) and tests this project.
>>>> 2) buildDependents - Assembles and tests this project and all projects
that
>>>> depend on it. So think of running this in hibernnate-entitymanager..
>>>> Gradle would assemble and test hibernate-entitymanager as well as
>>>> hibernate-envers (because envers depends on entitymanager).
>>>> 3) classes - compiles the main classes
>>>> 4) clean - Deletes the build directory.
>>>> 5) jar - Generates a jar archive with all the compiled classes.
>>>> 6) testClasses - Assembles the test classes.
>>>> 7) test - Runs the unit tests
>>>> 8) uploadArchives - think Maven deploy
>>>>
>>>> Especially those of you developing Search, Validator, etc should know
about
>>>> an additional task:
>>>> 9) install - installs the project jar to your local maven cache (aka
>>>> ~/,m2/repository)
>>>>
>>>> In the root project you can perform any task and Gradle will attempt to
>>>> perform it on each subproject.
>>>>
>>>> That should be enough to get you going.
>>>>
>>>> Oh and you can also execute multiple tasks:
>>>> `gradle clean build` runs both the clean and build tasks
>>>>
>>>> On Monday, October 11, 2010 05:45:29 pm Steve Ebersole wrote:
>>>>> I have switched HEAD of hibernate-core to use Gradle for builds. I
still
>>>>> need to finish up some tasks, but they mostly deal with the release
>>>>> process for which I created a follow-up issue.
>>>>>
>>>>> You can either install Gradle and use the gradle command, or you can
use
>>>>> "gradle wrapper" by using the ./gradlew (or ./gradlew.bat
files for our
>>>>> Windows friends).
>>>>>
>>>>> ---------- Forwarded Message ----------
>>>>>
>>>>> Subject: [Hibernate-JIRA] Closed: (HHH-5616) Switch to Gradle for
builds
>>>>> Date: Monday, October 11, 2010, 04:46:57 pm
>>>>> From: "Steve Ebersole (JIRA)"
<noreply(a)atlassian.com>
>>>>> To: steve(a)hibernate.org
>>>>>
>>>>> [
>>>>>
>>>>>
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616?page=c
>>>>> om .atlassian.jira.plugin.system.issuetabpanels:all- tabpanel ]
>>>>>
>>>>> Steve Ebersole closed HHH-5616.
>>>>> -------------------------------
>>>>>
>>>>> Resolution: Fixed
>>>>>>
>>>>>> Switch to Gradle for builds
>>>>>> ---------------------------
>>>>>>
>>>>>> Key: HHH-5616
>>>>>
>>>>>> URL:
>>>>> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616
>>>>>
>>>>>> Project: Hibernate Core
>>>>>>
>>>>>> Issue Type: Task
>>>>>> Components: core
>>>>>>
>>>>>> Reporter: Steve Ebersole
>>>>>> Assignee: Steve Ebersole
>>>>>>
>>>>>> Fix For: 4.0.0.Alpha1
>>>>>>
>>>>>> Time Spent: 23h
>>>>>>
>>>>>> Remaining Estimate: 0h
>>>>>>
>>>>>> http://gradle.org
>>>
>>> ---
>>> Steve Ebersole <steve(a)hibernate.org>
>>> http://hibernate.org
>>> _______________________________________________
>>> hibernate-dev mailing list
>>> hibernate-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>> --
>> Galder Zamarreño
>> Sr. Software Engineer
>> Infinispan, JBoss Cache
>>
>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
> --
> Galder Zamarreño
> Sr. Software Engineer
> Infinispan, JBoss Cache
>
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
4953
days inactive
4957
days old
8 comments
3 participants
participants (3)
-
Emmanuel Bernard -
Galder Zamarreño -
Steve Ebersole