Maven compliance

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Maven compliance

Russel Winder-2
I know this is definitely an RTFM question, but I think there is a
strategy issue here as well worth a quick email.

Gradle by default uses the directory build as the build directory
whereas Maven uses target.  Is there a quick and easy way to make Gradle
Maven compliant?

I wonder if Gradle should just go with the Maven structure by default?

--
Russel.
====================================================
Dr Russel Winder                 Partner

Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,              f: +44 8700 516 084
London SW11 1EN, UK.             m: +44 7770 465 077

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Maven compliance

hans_d
Administrator

On Jun 25, 2008, at 6:56 AM, Russel Winder wrote:

> I know this is definitely an RTFM question, but I think there is a
> strategy issue here as well worth a quick email.
>
> Gradle by default uses the directory build as the build directory
> whereas Maven uses target.  Is there a quick and easy way to make  
> Gradle
> Maven compliant?

buildDir = 'target'

>
> I wonder if Gradle should just go with the Maven structure by default?

I find target is a very unexpressive name and build more appropriate.  
As this is a constructed folder, Maven projects don't have to change  
there layouts.

I'm wondering what other people think about this.

- Hans

>
> --
> Russel.
> ====================================================
> Dr Russel Winder                 Partner
>
> Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
> 41 Buckmaster Road,              f: +44 8700 516 084
> London SW11 1EN, UK.             m: +44 7770 465 077

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Maven compliance

hans_d
Administrator

On Jun 25, 2008, at 8:51 AM, Hans Dockter wrote:

>
> On Jun 25, 2008, at 6:56 AM, Russel Winder wrote:
>
>> I know this is definitely an RTFM question, but I think there is a
>> strategy issue here as well worth a quick email.
>>
>> Gradle by default uses the directory build as the build directory
>> whereas Maven uses target.  Is there a quick and easy way to make  
>> Gradle
>> Maven compliant?
>
> buildDir = 'target'

Correction: buildDirName = 'target'

- Hans

>
>>
>> I wonder if Gradle should just go with the Maven structure by  
>> default?
>
> I find target is a very unexpressive name and build more  
> appropriate. As this is a constructed folder, Maven projects don't  
> have to change there layouts.
>
> I'm wondering what other people think about this.
>
> - Hans
>
>>
>> --
>> Russel.
>> ====================================================
>> Dr Russel Winder                 Partner
>>
>> Concertant LLP                   t: +44 20 7585 2200, +44 20 7193  
>> 9203
>> 41 Buckmaster Road,              f: +44 8700 516 084
>> London SW11 1EN, UK.             m: +44 7770 465 077
>
> --
> Hans Dockter
> Gradle Project lead
> http://www.gradle.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Maven compliance

Russel Winder-2
In reply to this post by hans_d
On Wed, 2008-06-25 at 08:51 +0200, Hans Dockter wrote:

> > Gradle by default uses the directory build as the build directory
> > whereas Maven uses target.  Is there a quick and easy way to make  
> > Gradle
> > Maven compliant?
>
> buildDir = 'target'

On Wed, 2008-06-25 at 09:12 +0200, Hans Dockter wrote:
> Correction: buildDirName = 'target'

Splendid.  That was easy :-)

> > I wonder if Gradle should just go with the Maven structure by default?
>
> I find target is a very unexpressive name and build more appropriate.  
> As this is a constructed folder, Maven projects don't have to change  
> there layouts.

I have a few, essentially trivial, points:

-- I like using Build as the name of directory but that is because I
tend to use initial capital for directory names and initial lower case
for file names.
 
--  With the script called build.gradle, the directory name build is a
bit irritating when it comes to command line completion.

-- Where there are multiple build systems for a given project,
consistency of default naming is helpful.

--  Even people who don't use Maven are beginning to use the Maven
structuring conventions.

PS Any news on making Gradle HEAD buildable?  I am still getting:

Exception: org.gradle.api.GradleScriptException: : Warning: Could not
find
file /home/Checkouts/Bazaar/GradleCore_Trunk/src/docs/userguide/master.pdf to copy. Buildscript=build.gradle in line(s): 228 218

--
Russel.
====================================================
Dr Russel Winder                 Partner

Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,              f: +44 8700 516 084
London SW11 1EN, UK.             m: +44 7770 465 077

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Maven compliance

Ittay Dror
In reply to this post by hans_d


Hans Dockter wrote:

>
> On Jun 25, 2008, at 6:56 AM, Russel Winder wrote:
>
>> I know this is definitely an RTFM question, but I think there is a
>> strategy issue here as well worth a quick email.
>>
>> Gradle by default uses the directory build as the build directory
>> whereas Maven uses target.  Is there a quick and easy way to make Gradle
>> Maven compliant?
>
> buildDir = 'target'
>
>>
>> I wonder if Gradle should just go with the Maven structure by default?
>
> I find target is a very unexpressive name and build more appropriate.
> As this is a constructed folder, Maven projects don't have to change
> there layouts.
>
> I'm wondering what other people think about this.
IMHO 'target' is confusing and I like 'build' or 'out' better. The
things I find confusing are the build-resolvers and buildSrc directory
names. Can I suggest build/resolvers and  'src/build/groovy'
respectively (of course the user can change the layout in the same way
he can redefine src/main/java)?

Ittay

>
> - Hans
>
>>
>> --
>> Russel.
>> ====================================================
>> Dr Russel Winder                 Partner
>>
>> Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
>> 41 Buckmaster Road,              f: +44 8700 516 084
>> London SW11 1EN, UK.             m: +44 7770 465 077
>
> --
> Hans Dockter
> Gradle Project lead
> http://www.gradle.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

--
--
Ittay Dror <[hidden email]>


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Maven compliance

hans_d
Administrator
In reply to this post by Russel Winder-2

On Jun 25, 2008, at 9:51 AM, Russel Winder wrote:

> On Wed, 2008-06-25 at 08:51 +0200, Hans Dockter wrote:
>
>>> Gradle by default uses the directory build as the build directory
>>> whereas Maven uses target.  Is there a quick and easy way to make
>>> Gradle
>>> Maven compliant?
>>
>> buildDir = 'target'
>
> On Wed, 2008-06-25 at 09:12 +0200, Hans Dockter wrote:
>> Correction: buildDirName = 'target'
>
> Splendid.  That was easy :-)
>
>>> I wonder if Gradle should just go with the Maven structure by  
>>> default?
>>
>> I find target is a very unexpressive name and build more appropriate.
>> As this is a constructed folder, Maven projects don't have to change
>> there layouts.
>
> I have a few, essentially trivial, points:
>
> -- I like using Build as the name of directory but that is because I
> tend to use initial capital for directory names and initial lower case
> for file names.
>
> --  With the script called build.gradle, the directory name build is a
> bit irritating when it comes to command line completion.
>
> -- Where there are multiple build systems for a given project,
> consistency of default naming is helpful.
>
> --  Even people who don't use Maven are beginning to use the Maven
> structuring conventions.
>
> PS Any news on making Gradle HEAD buildable?  I am still getting:
>
> Exception: org.gradle.api.GradleScriptException: : Warning: Could not
> find
> file /home/Checkouts/Bazaar/GradleCore_Trunk/src/docs/userguide/
> master.pdf to copy. Buildscript=build.gradle in line(s): 228 218

There seem to be some issue with the LaTeX userguide generation. It  
should work if you set -Dskip.userguide.

The output of the LaTeX pdf process can be found in: build/docs/
userguide/pdfOut

- Hans

>
> --
> Russel.
> ====================================================
> Dr Russel Winder                 Partner
>
> Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
> 41 Buckmaster Road,              f: +44 8700 516 084
> London SW11 1EN, UK.             m: +44 7770 465 077

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Maven compliance

Russel Winder-2
On Wed, 2008-06-25 at 19:22 +0200, Hans Dockter wrote:

> > Exception: org.gradle.api.GradleScriptException: : Warning: Could not
> > find
> > file /home/Checkouts/Bazaar/GradleCore_Trunk/src/docs/userguide/
> > master.pdf to copy. Buildscript=build.gradle in line(s): 228 218
>
> There seem to be some issue with the LaTeX userguide generation. It  
> should work if you set -Dskip.userguide.

Well that gets an installation of Gradle in place so that is good, but
it seems very unsatisfactory that the build is not completing smoothly
with all components build correctly.  Is there anything I can do to
help?

> The output of the LaTeX pdf process can be found in: build/docs/
> userguide/pdfOut

The directory is empty

|> ll build/docs/userguide/
total 8
drwx------ 2 russel russel 4096 2008-06-25 19:19 ./
drwx------ 3 russel russel 4096 2008-06-25 19:19 ../
|>

--
Russel.
====================================================
Dr Russel Winder                 Partner

Concertant LLP                   t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,              f: +44 8700 516 084
London SW11 1EN, UK.             m: +44 7770 465 077

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Maven compliance

hans_d
Administrator
In reply to this post by Ittay Dror
Hi Ittay,

On Jun 25, 2008, at 10:42 AM, Ittay Dror wrote:

>
>
> Hans Dockter wrote:
>>
>> On Jun 25, 2008, at 6:56 AM, Russel Winder wrote:
>>
>>> I know this is definitely an RTFM question, but I think there is a
>>> strategy issue here as well worth a quick email.
>>>
>>> Gradle by default uses the directory build as the build directory
>>> whereas Maven uses target.  Is there a quick and easy way to make  
>>> Gradle
>>> Maven compliant?
>>
>> buildDir = 'target'
>>
>>>
>>> I wonder if Gradle should just go with the Maven structure by  
>>> default?
>>
>> I find target is a very unexpressive name and build more  
>> appropriate. As this is a constructed folder, Maven projects don't  
>> have to change there layouts.
>>
>> I'm wondering what other people think about this.
> IMHO 'target' is confusing and I like 'build' or 'out' better. The
> things I find confusing are the build-resolvers and buildSrc directory
> names. Can I suggest build/resolvers and  'src/build/groovy'
> respectively (of course the user can change the layout in the same way
> he can redefine src/main/java)?

build-resolver is a temporary dir and is always deleted before the  
build starts. Therefore we should also delete it after the build has  
executed. It should also live not in the top-level but in a  
PROJECT_ROOT/.grade folder I think. If we do it like this I guess  
your issue with build-resolver is solved?

I'm not sure about buildSrc. For one, I see the src folder as the  
input for the build. buildSrc is not input for the build, but part of  
the build logic which is otherwise contained in the build script  
which lives on the top level. But I agree that there should be a  
possibility to customize the location. This would be done in the  
settings.gradle file, as the buildSrc jar is needed to compile the  
build.gradle.

- Hans


>
> Ittay
>>
>> - Hans
>>
>>>
>>> --
>>> Russel.
>>> ====================================================
>>> Dr Russel Winder                 Partner
>>>
>>> Concertant LLP                   t: +44 20 7585 2200, +44 20 7193  
>>> 9203
>>> 41 Buckmaster Road,              f: +44 8700 516 084
>>> London SW11 1EN, UK.             m: +44 7770 465 077
>>
>> --
>> Hans Dockter
>> Gradle Project lead
>> http://www.gradle.org
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> --
> --
> Ittay Dror <[hidden email]>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email