Help output

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

Help output

Russel Winder-2
"gradle --help" produces serious bizarre output using Gradle installed
from Subversion HEAD (r689) -- see below.  Is this an indication that
JOpt Simple is not actually up to the job and sticking with CliBuilder
would have been a better move -- especially as with groovy-all there is
no need for extra libraries Commons CLI is JarJar'd in.  Or maybe I am
missing something?
 

|> gradle --help
Option
Description                            
------
-----------                            
-?, -h                                  Shows this help
message                
-B, --bootstrap-debug                   Specify a text to be logged at
the    
-D, --systemprop                          beginning (e.g. used by
Gradle's    
-I, --no-imports                          bootstrap
class.                    
-P, --projectprop                       Set system property of the JVM
(e.g. -
-S
Dmyprop=myvalue).                    
-b, --buildfile                         Disable usage of default imports
for  
-d, --debug                               build script
files.                  
-e, --embedded                          Set project property for the
build    
-f, --full-stacktrace                     script (e.g.
-Pmyprop=myvalue).      
-g, --gradle-user-home                  Don't trigger a System.exit(0)
for    
-i, --ivy-quiet                           normal termination. Used
for        
-j, --ivy-debug                           Gradle's internal
testing.          
-l, --plugin-properties-file            Specifies the build file name
(also    
-n, --non-recursive                       for subprojects). Defaults to
build.
-p, --project-dir
gradle.                              
-q, --quiet                             Log in debug mode (includes
normal    
-r, --rebuild-cache
stacktrace).                        
-s, --stacktrace                        Specify an embedded build
script.      
-t, --tasks                             Print out the full (very
verbose)      
-u, --no-search-upward                    stacktrace for any
exceptions.      
-v, --version                           Specifies the gradle user home
dir.    
-x, --cache-off                         Set Ivy log level to
quiet.            
Set Ivy log level to debug (very      
  verbose).                            
Specifies the plugin.properties file.  
Do not execute primary tasks of        
  childprojects.                      
Specifies the start dir for Gradle.    
  Defaults to current dir.            
Log errors only.                      
Rebuild the cache of compiled build    
  scripts.                            
Print out the stacktrace also for user
  exceptions (e.g. compile error).    
Show list of all available tasks and  
  there dependencies.                  
Don't search in parent folders for a  
  settings.gradle file.                
Print version info.                    
No caching of compiled build scripts.  
====

--
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: Help output

hans_d
Administrator
Hi Russel,

On Jul 14, 2008, at 1:06 PM, Russel Winder wrote:

> "gradle --help" produces serious bizarre output using Gradle installed
> from Subversion HEAD (r689) -- see below.  Is this an indication that
> JOpt Simple is not actually up to the job and sticking with CliBuilder
> would have been a better move -- especially as with groovy-all  
> there is
> no need for extra libraries Commons CLI is JarJar'd in.  Or maybe I am
> missing something?


The help output of JOpt Simple need improvement. Except this, it is  
an excellent library under _active_ development. And we are  
refactoring the core to Java. Our Main class is already written in  
Java, therefore we don't use the Groovy wrapper for command line  
processing. JOpt is very nice to use from java. I'm surprised of your  
sudden fondness of commons-cli ;)

- Hans

--
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: Help output

Russel Winder-2
Hans,

On Mon, 2008-07-14 at 13:34 +0200, Hans Dockter wrote:

> The help output of JOpt Simple need improvement. Except this, it is  
> an excellent library under _active_ development. And we are  
> refactoring the core to Java. Our Main class is already written in  
> Java, therefore we don't use the Groovy wrapper for command line  
> processing. JOpt is very nice to use from java. I'm surprised of your  
> sudden fondness of commons-cli ;)

It is possible that Commons CLI 1.2 and indeed Commons CLI 2.0 will be
released in the next few weeks.  I have been pushing for the Commons
people to either do some work on CLI or declare it dead.

Gant main class is still in Groovy and so I am trying to get rid of the
explicit dependence on Commons CLI by using only CliBuilder and its API.
The only problem is that Commons CLI 1.0 is broken.
 
--
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: Help output

hans_d
Administrator
Hi Russel,

On Jul 14, 2008, at 2:04 PM, Russel Winder wrote:

> Hans,
>
> On Mon, 2008-07-14 at 13:34 +0200, Hans Dockter wrote:
>
>> The help output of JOpt Simple need improvement. Except this, it is
>> an excellent library under _active_ development. And we are
>> refactoring the core to Java. Our Main class is already written in
>> Java, therefore we don't use the Groovy wrapper for command line
>> processing. JOpt is very nice to use from java. I'm surprised of your
>> sudden fondness of commons-cli ;)
>
> It is possible that Commons CLI 1.2 and indeed Commons CLI 2.0 will be
> released in the next few weeks.  I have been pushing for the Commons
> people to either do some work on CLI or declare it dead.
>
> Gant main class is still in Groovy and so I am trying to get rid of  
> the
> explicit dependence on Commons CLI by using only CliBuilder and its  
> API.
> The only problem is that Commons CLI 1.0 is broken.

Paul Holser, the lead of JOpt has already fixed the bug. The 2.4.1  
release which supposed to happen today. Than I will upgrade.

One thing I like with JOpt Simple is that you can do: gradle clean  
libs -Dskip.test

AFAIK with commons-cli you have to stick to: gradle -Dskip.test clean  
libs

- 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: Help output

hans_d
Administrator
Hi Russel,

On Jul 15, 2008, at 4:22 PM, Hans Dockter wrote:

> Hi Russel,
>
> On Jul 14, 2008, at 2:04 PM, Russel Winder wrote:
>
>> Hans,
>>
>> On Mon, 2008-07-14 at 13:34 +0200, Hans Dockter wrote:
>>
>>> The help output of JOpt Simple need improvement. Except this, it is
>>> an excellent library under _active_ development. And we are
>>> refactoring the core to Java. Our Main class is already written in
>>> Java, therefore we don't use the Groovy wrapper for command line
>>> processing. JOpt is very nice to use from java. I'm surprised of  
>>> your
>>> sudden fondness of commons-cli ;)
>>
>> It is possible that Commons CLI 1.2 and indeed Commons CLI 2.0  
>> will be
>> released in the next few weeks.  I have been pushing for the Commons
>> people to either do some work on CLI or declare it dead.
>>
>> Gant main class is still in Groovy and so I am trying to get rid  
>> of the
>> explicit dependence on Commons CLI by using only CliBuilder and  
>> its API.
>> The only problem is that Commons CLI 1.0 is broken.
>
> Paul Holser, the lead of JOpt has already fixed the bug. The 2.4.1  
> release which supposed to happen today. Than I will upgrade.
>
> One thing I like with JOpt Simple is that you can do: gradle clean  
> libs -Dskip.test
>
> AFAIK with commons-cli you have to stick to: gradle -Dskip.test  
> clean libs
>

I have updated Head to use the new JOpt simple 2.4.1. The help output  
is fine now.

What you can also do with JOpt simple is: gradle clean -Dskip.test libs

This arbitrary positioning of parameters is really cool when you work  
with the history of the command line and just wan to add a skip or  
whatever.

- Hans

--
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: Help output

Russel Winder-2
Hans,

On Wed, 2008-07-16 at 18:02 +0200, Hans Dockter wrote:

> I have updated Head to use the new JOpt simple 2.4.1. The help output  
> is fine now.

For some definitions of fine :-)  I generally use terminals that are
150-180 characters wide so output that assumes a fixed 80 character line
width looks dreadful.  It seems that JOpt Simple is making the same
mistake as Commons CLI and not fitting the output to the actual width of
the terminal if that can be determined or 80 characters if it cannot.
Still not really a Gradle issue.

> What you can also do with JOpt simple is: gradle clean -Dskip.test libs
>
> This arbitrary positioning of parameters is really cool when you work  
> with the history of the command line and just wan to add a skip or  
> whatever.

So does this mean that the -D option is an option to the clean target ?

Consider a command line such as:

|>  bzr -Dtransport pull --remember http://blah.blah.blah

The ordering of the options is actually critical here.  Having a system
where the ordering of parameters on the command line is not obeyed is
going to lead to great confusion.

--
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