gradle -xtest clean build
On Oct 14, 2010, at 4:02 PM, Galder Zamarreño wrote:
How do you run a build skipping test execution?
I've tried the following but no luck: gradle -Dskip.tests=true clean build
On Oct 12, 2010, at 3:58 AM, 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
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache