You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-commits@db.apache.org by an...@apache.org on 2007/11/19 18:39:28 UTC
svn commit: r596377 - /db/jdo/trunk/tck2/maven.xml
Author: andyj
Date: Mon Nov 19 09:39:27 2007
New Revision: 596377
URL: http://svn.apache.org/viewvc?rev=596377&view=rev
Log:
Reformat some of the "help" output so we have half a chance of having it on one page of a normal sized screen.
Are we seriously sticking to 80 char line widths for help text ?
Modified:
db/jdo/trunk/tck2/maven.xml
Modified: db/jdo/trunk/tck2/maven.xml
URL: http://svn.apache.org/viewvc/db/jdo/trunk/tck2/maven.xml?rev=596377&r1=596376&r2=596377&view=diff
==============================================================================
--- db/jdo/trunk/tck2/maven.xml (original)
+++ db/jdo/trunk/tck2/maven.xml Mon Nov 19 09:39:27 2007
@@ -35,44 +35,38 @@
<echo>Custom goals for this project are:</echo>
<echo> installSchema - installs the database schema</echo>
<echo></echo>
- <echo> enhance.iut - enhances persistence capable classes</echo>
- <echo> with the implementation under test enhancer</echo>
- <echo> if enhancement is not up to date</echo>
- <echo> enhance.jdori - enhances persistence capable classes</echo>
- <echo> with the JDO Reference Implementation enhancer </echo>
- <echo> if enhancement is not up to date</echo>
+ <echo> enhance.iut - enhances persistence capable classes with the implementation</echo>
+ <echo> under test enhancer if enhancement is not up to date</echo>
+ <echo> enhance.jdori - enhances persistence capable classes with the JDO Reference</echo>
+ <echo> Implementation enhancer if enhancement is not up to date</echo>
<echo></echo>
<echo> runtck.iut - runs the TCK on the implementation under test</echo>
<echo> runtck.jdori - runs the TCK on the JDO Reference Implementation</echo>
<echo></echo>
- <echo> debugtck.jdori - waits for a debugger to attach </echo>
- <echo> and then runs the TCK on the JDO RI</echo>
- <echo> debugtck.iut - waits for a debugger to attach</echo>
- <echo> and then runs the TCK on the implementation under test</echo>
+ <echo> debugtck.jdori - waits for a debugger to attach and then runs the</echo>
+ <echo> TCK on the JDO RI</echo>
+ <echo> debugtck.iut - waits for a debugger to attachand then runs the</echo>
+ <echo> TCK on the implementation under test</echo>
<echo></echo>
<echo> cleanClasses - deletes classes and enhanced classes</echo>
<echo></echo>
<echo></echo>
- <echo>To run a single test, create a .conf file</echo>
- <echo> (copy an existing file) and edit the </echo>
- <echo> jdo.tck.classes property to include </echo>
- <echo> the name of the test class. </echo>
+ <echo>To run a single test, create a .conf file (copy an existing file) and edit</echo>
+ <echo> the "jdo.tck.classes property" to include the name of the test class.</echo>
<echo></echo>
<echo></echo>
<echo>Options for this project are:</echo>
- <echo> -Djdo.tck.cfglist=xxx - a list of configuration files </echo>
- <echo> (must be in src/conf)</echo>
+ <echo> -Djdo.tck.cfglist=xxx - a list of configuration files (must be in src/conf)</echo>
<echo> -Djdo.tck.dblist=xxx - a list of databases</echo>
<echo> -Djdo.tck.identitytypes=xxx - a list of identity types </echo>
<echo> (applicationidentity, datastoreidentity)</echo>
<echo> -Djdo.tck.cleanupaftertest=xxx - true/false. </echo>
- <echo> Setting it to false will retain data in database </echo>
- <echo> after test. This will allow inspection of data after</echo>
- <echo> test is run. Default is true</echo>
- <echo> -Djdo.tck.debug.port=##### - the port number the JVM </echo>
- <echo> should listen for a debugger on (default 8787)</echo>
+ <echo> Setting it to false will retain data in database after test. This will</echo>
+ <echo> allow inspection of data after test is run. Default is true</echo>
+ <echo> -Djdo.tck.debug.port=##### - the port number the JVM should listen for a</echo>
+ <echo> debugger on (default 8787)</echo>
<echo> -Djdo.tck.debug.jvmargs=xxx - the "-Xdebug ..." arguments</echo>
- <echo> in the event you want to supply your own debug directives</echo>
+ <echo> in the event you want to supply your own debug directives</echo>
<echo></echo>
<echo>Examples:</echo>
<echo> maven -Djdo.tck.identitytypes=datastoreidentity installSchema</echo>
@@ -80,9 +74,8 @@
<echo> for all supported databases</echo>
<echo></echo>
<echo> maven -Djdo.tck.cfglist="alltests.conf cfg1.conf" runtck.jdori</echo>
- <echo> Runs the test configurations specified in</echo>
- <echo> alltests.conf and cfg1.conf on the JDORI, </echo>
- <echo> using all supported identity types and databases. </echo>
+ <echo> Runs the test configurations specified in alltests.conf and cfg1.conf </echo>
+ <echo> on the JDORI, using all supported identity types and databases. </echo>
<echo></echo>
<echo> maven -Djdo.tck.cfglist=detach.conf debugtck.jdori</echo>
<echo> Runs the test detach.conf configuration, waiting for </echo>
@@ -93,13 +86,12 @@
<echo> for a debugger to attach on port 9343</echo>
<echo></echo>
<echo>Note:</echo>
- <echo> By default, the database schema is NOT installed</echo>
- <echo> when the custom goals </echo>
- <echo> runtck.iut and runtck.jdori are run.</echo>
- <echo> maven build installs the database schema and runs</echo>
- <echo> the TCK on the JDO Reference Implementation.</echo>
- <echo> Enhancement is always done before running the TCK </echo>
- <echo> when the enhanced classes are not up to date.</echo>
+ <echo> By default, the database schema is NOT installed when the custom goals</echo>
+ <echo> "runtck.iut" and "runtck.jdori" are run.</echo>
+ <echo> "maven build" installs the database schema and runs the TCK on the
+ <echo> JDO Reference Implementation.</echo>
+ <echo> Enhancement is always done before running the TCK when the enhanced classes</echo>
+ <echo> are not up to date.</echo>
</goal>
<goal name="build">
Re: svn commit: r596377 - /db/jdo/trunk/tck2/maven.xml
Posted by Andy Jefferson <an...@jpox.org>.
Hi Craig,
> Sorry my comments were interpreted as requesting you to roll back the
> changes. I hadn't completely read the commit and wasn't trying to
> interfere.
No problem at all. I don't see what others are seeing, so was assuming they
all have screens with VTs 180 chars wide :-)
Now updated to hopefully fit in with the majority of tastes. Still 80 chars
wide, but minimised lines so the key info is there for most.
--
Andy (Java Persistent Objects - http://www.jpox.org)
Re: svn commit: r596377 - /db/jdo/trunk/tck2/maven.xml
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Andy,
Sorry my comments were interpreted as requesting you to roll back the
changes. I hadn't completely read the commit and wasn't trying to
interfere.
I agree with the goal to have the entire help fit into what most
users can see on a virtual terminal. Beyond that, I don't want to
paint the bike shed a different color.
Craig
On Nov 19, 2007, at 9:58 AM, Andy Jefferson wrote:
> Hi Craig,
>
>> Most of my use of the tck is on a virtual terminal, so I guess I'd
>> like to keep the 80 character guideline.
>
> Ok (but dont VTs allow more than 80 chars? I can on Linux).
> Previous version
> of maven.xml is now reinstated but I would say that a "help page"
> should have
> all key info on *one* page of a typical users screen. So if we are
> limiting
> to 80 chars width then that would have to fit into say 64 lines
> (how many I
> have on my screen, and many people will have less). What is there
> currently
> doesnt even with 64 lines ... hence scrolling
>
>
> --
> Andy (Java Persistent Objects - http://www.jpox.org)
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Fwd: svn commit: r596377 - /db/jdo/trunk/tck2/maven.xml
Posted by Andy Jefferson <an...@jpox.org>.
Hi Craig,
> Most of my use of the tck is on a virtual terminal, so I guess I'd
> like to keep the 80 character guideline.
Ok (but dont VTs allow more than 80 chars? I can on Linux). Previous version
of maven.xml is now reinstated but I would say that a "help page" should have
all key info on *one* page of a typical users screen. So if we are limiting
to 80 chars width then that would have to fit into say 64 lines (how many I
have on my screen, and many people will have less). What is there currently
doesnt even with 64 lines ... hence scrolling
--
Andy (Java Persistent Objects - http://www.jpox.org)
Fwd: svn commit: r596377 - /db/jdo/trunk/tck2/maven.xml
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Andy,
Begin forwarded message:
> Log:
> Reformat some of the "help" output so we have half a chance of
> having it on one page of a normal sized screen.
> Are we seriously sticking to 80 char line widths for help text ?
Most of my use of the tck is on a virtual terminal, so I guess I'd
like to keep the 80 character guideline.
Craig
>
> Modified:
> db/jdo/trunk/tck2/maven.xml
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: svn commit: r596377 - /db/jdo/trunk/tck2/maven.xml
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Andy,
I'll try to be more focused in this reply ;-)
I use a terminal that can be resized horizontally from 80 to very
wide, and vertically up to 60 lines.
So I support going beyond the 80 character guideline if it means that
the entire help text fits into my 60 lines.
I know that others use terminal emulators that don't resize
horizontally past 80 characters.
Craig
On Nov 19, 2007, at 9:39 AM, andyj@apache.org wrote:
> Author: andyj
> Date: Mon Nov 19 09:39:27 2007
> New Revision: 596377
>
> URL: http://svn.apache.org/viewvc?rev=596377&view=rev
> Log:
> Reformat some of the "help" output so we have half a chance of
> having it on one page of a normal sized screen.
> Are we seriously sticking to 80 char line widths for help text ?
>
> Modified:
> db/jdo/trunk/tck2/maven.xml
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!