On 2001.10.26 19:10:53 -0400 Luke Taylor wrote:
> 
> Hi,
> 
> I want to check in some minor changes for a bugfix but I have one or
> two questions first before I screw things up :-)...
> 
> 1. What's the situation with the test suite on different platforms. I
> get a more errors than the number in the standard automated report? I'm
> running on NT - do some of the tests only work on Linux?
My understanding is that Chris only can run the tests on his linux system. 
I for one would be delighted if someone could run a nightly test on each
other platform (hint hint;-)

> 
> 2. The bug was reported on version the version 2.4.x branch. Should I
> change the code here as well as in the main branch? If so is there some
> way of doing this other than checking both trees out of cvs and making
> the changes in both of them separately?

cvs update -j <version # with revision> <filename>  applies changes from
branch point to named version to your working copy file.

cvs update -j <version#1> -j <version#2> <filename> applies changes between
the 2 named versions to your working copy.

It may be easier to apply the changes by hand if they are small and this
comfuses you as much as it did me. You might also want to check a manual to
make sure I got this correct.
> 
> 3. Does anyone know if it's possible to configure Together to apply the
> JBoss code guidelines on indentation - it only seems possible to get it
> to use a fixed indentation width.

You might try the pretty task that was (is?) is some versions of the 3.0
build.xml files.  There is a format file in build somewhere that I think I
got to match the coding guidelines quite well.  Don't try it on the only
copy of your work -- I think it does well but some people don't like it.

Here's a couple targets:

  <!-- ==================================================================
-->
  <!-- Pretty                                                            
-->
  <!-- ==================================================================
-->

  <!-- 
     |  Pretty print everything.
     |
     |  This uses the jedit JavaStyle plugin via the ejbdoclet pretty ant
task.
     |  cvs="true" only pretties files you have already modified.
     |  cvs="false" pretties all files.
    -->

  <target name="pretty" depends="init">
<echo message="settingsDir=${project.build}/etc"/>
    <taskdef name="pretty" classname="pretty.Pretty"/>
    <pretty settingsDir="${project.build}/etc" cvs="true">
      <fileset dir="${source.java}">
        <include name="**/*.java"/>
      </fileset>
    </pretty>
  </target>

  <target name="pretty-one" depends="init" if="pretty-file">
<echo message="settingsDir=${project.build}/etc"/>
<echo message="pretty-file=${pretty-file}.java"/>
    <taskdef name="pretty" classname="pretty.Pretty"/>
    <pretty settingsDir="${project.build}/etc" cvs="false">
      <fileset dir="${source.java}">
        <include name="**/${pretty-file}.java"/>
      </fileset>
    </pretty>
  </target>


david jencks
> 
> cheers,
> 
> Luke.
> 
> 
> -- 
>  Luke Taylor.                                  Monkey Machine Ltd.
>  PGP Key ID: 0x57E9523C                        http://www.mkeym.com
> 
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to