You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by av...@apache.org on 2003/06/02 10:03:30 UTC
cvs commit: jakarta-poi build.xml
avik 2003/06/02 01:03:30
Modified: . Tag: REL_2_BRANCH build.xml
Log:
Added ability to debug testcases using jpda, also refactored a bit
Revision Changes Path
No revision
No revision
1.41.2.2 +27 -13 jakarta-poi/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/jakarta-poi/build.xml,v
retrieving revision 1.41.2.1
retrieving revision 1.41.2.2
diff -u -r1.41.2.1 -r1.41.2.2
--- build.xml 30 May 2003 13:43:41 -0000 1.41.2.1
+++ build.xml 2 Jun 2003 08:03:30 -0000 1.41.2.2
@@ -215,15 +215,16 @@
</uptodate>
</target>
- <target name="test-main" depends="compile-main,-test-main-check" unless="main.test.notRequired">
- <junit printsummary="yes" showoutput="true" filtertrace="no" fork="no"
- haltonfailure="${halt.on.test.failure}" failureproperty="main.test.failed">
- <classpath>
+ <path id="test.classpath">
<path refid="main.classpath"/>
<pathelement location="${main.output.dir}"/>
<pathelement location="${main.output.test.dir}"/>
<pathelement location="${junit.jar1.dir}"/>
- </classpath>
+ </path>
+ <target name="test-main" depends="compile-main,-test-main-check" unless="main.test.notRequired">
+ <junit printsummary="yes" showoutput="true" filtertrace="no" fork="no"
+ haltonfailure="${halt.on.test.failure}" failureproperty="main.test.failed">
+ <classpath refid="test.classpath"/>
<sysproperty key="HSSF.testdata.path" value="${main.src.test}/org/apache/poi/hssf/data"/>
<sysproperty key="HPSF.testdata.path" value="${main.src.test}/org/apache/poi/hpsf/data"/>
<formatter type="plain"/>
@@ -239,20 +240,33 @@
<antcall target="-test-main-write-testfile"/>
</target>
- <target name="single-test" depends="compile-main">
- <junit printsummary="no" showoutput="true" filtertrace="no" fork="no" haltonfailure="${halt.on.test.failure}" failureproperty="main.test.failed" >
- <classpath>
- <path refid="main.classpath"/>
- <pathelement location="${main.output.dir}"/>
- <pathelement location="${main.output.test.dir}"/>
- <pathelement location="${junit.jar1.dir}"/>
- </classpath>
+ <target name="single-test" depends="-test-property-check,compile-main">
+ <junit printsummary="no" showoutput="true" filtertrace="no" haltonfailure="${halt.on.test.failure}" failureproperty="main.test.failed" >
+ <classpath refid="test.classpath"/>
<sysproperty key="HSSF.testdata.path" value="${main.src.test}/org/apache/poi/hssf/data"/>
<sysproperty key="HPSF.testdata.path" value="${main.src.test}/org/apache/poi/hpsf/data"/>
<formatter type="plain" usefile="no"/>
<formatter type="xml"/>
<test name="${testcase}" />
</junit>
+ </target>
+
+ <target name="debug-test" depends="-test-property-check,compile-main">
+ <junit printsummary="no" showoutput="true" filtertrace="no" fork="yes" haltonfailure="${halt.on.test.failure}" failureproperty="main.test.failed" >
+ <jvmarg value="-Xdebug"/>
+ <jvmarg value="-Xrunjdwp:transport=dt_socket,address=5001,server=y,suspend=y"/>
+ <sysproperty key="java.compiler" value="NONE"/>
+ <classpath refid="test.classpath"/>
+ <sysproperty key="HSSF.testdata.path" value="${main.src.test}/org/apache/poi/hssf/data"/>
+ <sysproperty key="HPSF.testdata.path" value="${main.src.test}/org/apache/poi/hpsf/data"/>
+ <formatter type="plain" usefile="no"/>
+ <test name="${testcase}" />
+ </junit>
+ </target>
+
+ <target name="-test-property-check" unless="testcase">
+ <echo message="Please use -Dtestcase=org.your.testcase to run a single test"/>
+ <fail/>
</target>
<target name="-test-main-write-testfile" unless="main.test.failed">
Re: HDF status
Posted by Avik Sengupta <av...@apache.org>.
indeed! much better that way.
On Mon, 2003-06-02 at 17:55, Andrew C. Oliver wrote:
> Commit early, commit often.
>
> On 6/2/03 6:44 AM, "Ryan Ackley" <sa...@cfl.rr.com> wrote:
>
> > I just wanted to keep everyone up to date, I wasn't able to finish adding
> > the writing component of HDF this past weekend. I worked on it all weekend
> > but there just isn't enough time in the day. The good news is that progress
> > is being made.
> >
> > Ryan
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: poi-dev-help@jakarta.apache.org
> >
--
Avik Sengupta <av...@apache.org>
Re: HDF status
Posted by Tetsuya Kitahata <te...@nifty.com>.
On Mon, 02 Jun 2003 11:06:40 -0400
> > HDF = Hemodiafiltration?? ;-)
> http://eosweb.larc.nasa.gov/HBDOCS/hdf.html
Wow.. I see. I don't have to take a nephrectomy ;-)
> > What's "HWPF"? ... acronym of "Horrible Word Processor Format"?
<snip>
> Now I just figure, its too late to change, best be consistent. Even if it
> makes your and my job a little bit harder as open source marketeers of
> sorts.. ;-) (oh god...did I just say that....I'm going to go wash my
> fingertips off)
Ahaha. Take it easy. Just use "Horrible"
as jargon, secret language. And officially (in business) announce
"Oh! it is acronym of 'Highlevel Word Processor Format'"
or something ;-) ... with evident sarcasm
Cheers,
-----------------------------------------------------
Tetsuya Kitahata -- Terra-International, Inc.
E-mail: kitahata@bb.mbn.or.jp
Re: HDF status
Posted by "Andrew C. Oliver" <ac...@apache.org>.
On 6/2/03 10:16 AM, "Tetsuya Kitahata" <te...@nifty.com> wrote:
>
> On Mon, 02 Jun 2003 10:05:54 -0400
> (Subject: Re: HDF status)
> "Andrew C. Oliver" <ac...@apache.org> wrote:
>
>> Create something Peer to HDF and come up with another cleaver acronym. This
>> time lets check Google to see if its taken. Maybe "HWPF" or something. (We
>> need to change the name of HDF anyhow)
>
> HDF = Hemodiafiltration?? ;-)
>
http://eosweb.larc.nasa.gov/HBDOCS/hdf.html
> What's "HWPF"? ... acronym of "Horrible Word Processor Format"?
>
Yup. Had I known POI stuff would be viable as a business model I'd have
taken naming a lot more seriously and come up with something more stodgy.
However there was equal pressure from the open source folks with Richard
Stallman running off at the mouth about how you should tell customers not to
send you word documents and the such! (it is easy to see who has real
client and who has speaking engagements). The open source community seemed
to have a consensus at the time that projects such as POI would propagate
these formats rather than open them and make creating proprietary formats
largely a fools errand. In order to dispel that view, we needed to
disparage the formats openly while porting them. This was easy to do since
the file formats are indeed very bad.
Now I just figure, its too late to change, best be consistent. Even if it
makes your and my job a little bit harder as open source marketeers of
sorts.. ;-) (oh god...did I just say that....I'm going to go wash my
fingertips off)
--
Andrew C. Oliver
http://www.superlinksoftware.com/poi.jsp
Custom enhancements and Commercial Implementation for Jakarta POI
http://jakarta.apache.org/poi
For Java and Excel, Got POI?
Re: HDF status
Posted by Tetsuya Kitahata <te...@nifty.com>.
On Mon, 02 Jun 2003 10:05:54 -0400
(Subject: Re: HDF status)
"Andrew C. Oliver" <ac...@apache.org> wrote:
> Create something Peer to HDF and come up with another cleaver acronym. This
> time lets check Google to see if its taken. Maybe "HWPF" or something. (We
> need to change the name of HDF anyhow)
HDF = Hemodiafiltration?? ;-)
What's "HWPF"? ... acronym of "Horrible Word Processor Format"?
-----------------------------------------------------
Tetsuya Kitahata -- Terra-International, Inc.
E-mail: kitahata@bb.mbn.or.jp
Re: HDF status
Posted by "Andrew C. Oliver" <ac...@apache.org>.
Then this is a good time to make the "break".
Create something Peer to HDF and come up with another cleaver acronym. This
time lets check Google to see if its taken. Maybe "HWPF" or something. (We
need to change the name of HDF anyhow)
Or we could call it "anti-trust" ;-)
Just use HDF as the example and make the new tree, build changes, etc.
-Andy
On 6/2/03 9:15 AM, "Ryan Ackley" <sa...@cfl.rr.com> wrote:
>> No.. You just write over them. CVS will automatically version them. If
> you
>> need a before and after
>
> I'm using the same class names but not they are no longer the same classes.
> They will break the old stuff. understand?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
>
--
Andrew C. Oliver
http://www.superlinksoftware.com/poi.jsp
Custom enhancements and Commercial Implementation for Jakarta POI
http://jakarta.apache.org/poi
For Java and Excel, Got POI?
Re: HDF status
Posted by Ryan Ackley <sa...@cfl.rr.com>.
> No.. You just write over them. CVS will automatically version them. If
you
> need a before and after
I'm using the same class names but not they are no longer the same classes.
They will break the old stuff. understand?
Re: HDF status
Posted by "Andrew C. Oliver" <ac...@apache.org>.
No.. You just write over them. CVS will automatically version them. If you
need a before and after
Cvs co jakarta-poi
Cvs tag pre-ryan jakarta-poi
Cvs update -A jakarta-poi
Vi ....
Cvs commit
-----
Cvs co -r pre-ryan jakarta-poi (gets before you changed them)
---
This isn't a branch, its just a tag.
On 6/2/03 9:04 AM, "Ryan Ackley" <sa...@cfl.rr.com> wrote:
>
>
>> Why do you need a branch? This is in the sandbox. Just make it compile
> and
>> commit.
>
> I'm using same class names as whats there now. Do I just create a new
> directory and throw everything in there?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
>
--
Andrew C. Oliver
http://www.superlinksoftware.com/poi.jsp
Custom enhancements and Commercial Implementation for Jakarta POI
http://jakarta.apache.org/poi
For Java and Excel, Got POI?
Re: HDF status
Posted by Ryan Ackley <sa...@cfl.rr.com>.
> Why do you need a branch? This is in the sandbox. Just make it compile
and
> commit.
I'm using same class names as whats there now. Do I just create a new
directory and throw everything in there?
Re: HDF status
Posted by "Andrew C. Oliver" <ac...@apache.org>.
Why do you need a branch? This is in the sandbox. Just make it compile and
commit.
On 6/2/03 8:39 AM, "Ryan Ackley" <sa...@cfl.rr.com> wrote:
>> Commit early, commit often.
>
> How do I create a branch in cvs?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
>
--
Andrew C. Oliver
http://www.superlinksoftware.com/poi.jsp
Custom enhancements and Commercial Implementation for Jakarta POI
http://jakarta.apache.org/poi
For Java and Excel, Got POI?
Re: HDF status
Posted by Ryan Ackley <sa...@cfl.rr.com>.
> Commit early, commit often.
How do I create a branch in cvs?
Re: HDF status
Posted by "Andrew C. Oliver" <ac...@apache.org>.
Commit early, commit often.
On 6/2/03 6:44 AM, "Ryan Ackley" <sa...@cfl.rr.com> wrote:
> I just wanted to keep everyone up to date, I wasn't able to finish adding
> the writing component of HDF this past weekend. I worked on it all weekend
> but there just isn't enough time in the day. The good news is that progress
> is being made.
>
> Ryan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
>
--
Andrew C. Oliver
http://www.superlinksoftware.com/poi.jsp
Custom enhancements and Commercial Implementation for Jakarta POI
http://jakarta.apache.org/poi
For Java and Excel, Got POI?
HDF status
Posted by Ryan Ackley <sa...@cfl.rr.com>.
I just wanted to keep everyone up to date, I wasn't able to finish adding
the writing component of HDF this past weekend. I worked on it all weekend
but there just isn't enough time in the day. The good news is that progress
is being made.
Ryan
Debugging Testcases
Posted by Avik Sengupta <av...@apache.org>.
Folks
If you want to debug a particular testcase, run
$ ant -Dtestcase=org.apache.poi.somepack.someclass debug-test
This will cause a JVM to wait at port 5001. Just attach your favourite
IDE (after setting some breakpounts) and voila, step thru the code.
I know most people probably run tests from within IDE, but i think an
IDE independent command line method of starting poi in debug mode is
useful.
HTH
-
Avik
On Mon, 2003-06-02 at 13:33, avik@apache.org wrote:
> avik 2003/06/02 01:03:30
>
> Modified: . Tag: REL_2_BRANCH build.xml
> Log:
> Added ability to debug testcases using jpda, also refactored a bit
>