Like I said, personally I would prefer a full path here too. I assume they do
this because they are far more flexible in terms of dependencies (leveraging
Ivy under the covers). Dunno for sure. I assume though what happens is that
Gradle's "project path" here is the symlink name and so the resolution of
user.home against that fails. Just a guess. I'll ask around.
On Friday, October 15, 2010, at 07:12 am, Galder Zamarreño wrote:
Oh, I think I know what the problem is:
Locally, this is located in:
/Users/z/JBoss/code/hibernate/hibernate-core.git
However, JBoss is a symlink to: Dropbox/JBoss
So, the actual full path is:
/Users/z/Dropbox/JBoss/code/hibernate/hibernate-core.git
So, I have to go through the full path for the libraries to be resolved
properly.
This doesn't make sense though, I never had this issue with Maven. Most
likely this is a bug in Gradle.
On Oct 15, 2010, at 1:55 PM, Steve Ebersole wrote:
> I bet its relative to where you have your project. That's sort of the
> nature of "realtive" paths :)
>
> Mine has the correct number.
>
> On Friday, October 15, 2010, at 06:46 am, Galder Zamarreño wrote:
>> On Oct 15, 2010, at 1:31 PM, Steve Ebersole wrote:
>>> Strange. Quite a few of us have been able to do this successfully.
>>
>> I know, which is what makes this really odd.
>>
>>> Maybe you ran that as root? That would explain why user home there is
>>> Users root (extrapolating Linux knowledge to Mac).
>>
>> No, definitely not root. My username: 'z' is an administrator but
that's
>> it.
>>
>>> In mine I just noticed that while it works, the paths to the jar are
>>> relative from the IntelliJ variable $MODULE_DIR. If you look at the
>>> .iml file, is yours the same? Not sure why they do it that way as
>>> opposed to an absolute path. Still does not explain why yours is off,
>>> but I can look into that.
>>
>> Mine is also relative to $MODULE_DIR. Let's take an example:
>> <CLASSES>
>>
>> <root
>>
>> url="jar://$MODULE_DIR$/../../../../../../.gradle/cache/org.infinispan/i
>> nf inispan-core/jars/infinispan-core-4.2.0.ALPHA1.jar!/" />
</CLASSES>
>>
>> So, how many '..' are in yours? In mine there's 6. I bet in yours
>> there's only 5.
>>
>>> On Friday, October 15, 2010, at 05:42 am, 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-co
>>>> re -4 .2.0.ALPHA1.jar
>>>>
>>>> Clearly, this should be pointing to:
>>>> •
>>>>
>>>> /Users/z/.gradle/cache/org.infinispan/infinispan-core/jars/infinispan-
>>>> co re -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?
>>>>>>> pa ge =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
>>>
>>> ---
>>> Steve Ebersole <steve(a)hibernate.org>
>>>
http://hibernate.org
>>
>> --
>> Galder Zamarreño
>> Sr. Software Engineer
>> Infinispan, JBoss Cache
>
> ---
> 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