Re: [JBoss-dev] CVS update: build/jboss build.xml
Can you make the info a dependency (or call target), which will only run if a property is set, so those who don't really want to see this do not have to. --jason On Fri, 31 Aug 2001, Chris Kimpton wrote: > User: kimptoc > Date: 01/08/31 03:01:18 > > Modified:jbossbuild.xml > Log: > added some echo info to let you know what you are using - just in case you think >its different > > Revision ChangesPath > 1.13 +16 -1 build/jboss/build.xml > > Index: build.xml > === > RCS file: /cvsroot/jboss/build/jboss/build.xml,v > retrieving revision 1.12 > retrieving revision 1.13 > diff -u -r1.12 -r1.13 > --- build.xml 2001/08/31 05:25:55 1.12 > +++ build.xml 2001/08/31 10:01:18 1.13 > @@ -10,7 +10,7 @@ > > > > - > + > > > > @@ -42,6 +42,21 @@ > > depends="init-buildlog"> > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > > > > > > > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jboss build.xml
why mail over mimemail?
--jason
On Sun, 2 Sep 2001, Chris Kimpton wrote:
> User: kimptoc
> Date: 01/09/02 12:29:38
>
> Modified:jbossbuild.xml
> Log:
> changes to make the testsuite email report more generic
>
> Revision ChangesPath
> 1.14 +20 -9 build/jboss/build.xml
>
> Index: build.xml
> ===
> RCS file: /cvsroot/jboss/build/jboss/build.xml,v
> retrieving revision 1.13
> retrieving revision 1.14
> diff -u -r1.13 -r1.14
> --- build.xml 2001/08/31 10:01:18 1.13
> +++ build.xml 2001/09/02 19:29:38 1.14
> @@ -10,7 +10,7 @@
>
>
>
> -
> +
>
>
>
> @@ -225,6 +225,10 @@
>
>
>
> +
> + value="[EMAIL PROTECTED]"/>
> +
> +
>
>
>
> @@ -587,16 +591,23 @@
>
>
>
> +
> +
> +
> +
> +
>Sending Reports
>
> - - subject="Automated JBoss Testsuite"
> - message="Automated JBoss Testsuite"
> - from="[EMAIL PROTECTED]">
> -
> -
> -
> -
> + + subject="Automated JBoss Testsuite Results"
> + message="Automated JBoss Testsuite Results"
> + from="${run.nightly.email.from}"
> + mailhost="${run.nightly.email.mailhost}"
> +
>files="${project.root}/testsuite/output/reports/text/TESTS-TestSuites.txt"
> +/>
> +
> +
> +
>
>
>
>
>
>
>
> ___
> 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
Re: [JBoss-dev] CVS update: build/jboss build.xml
Hi,
--- Jason Dillon <[EMAIL PROTECTED]> wrote:
> why mail over mimemail?
>
> --jason
>
>
> On Sun, 2 Sep 2001, Chris Kimpton wrote:
>
> > User: kimptoc
> > Date: 01/09/02 12:29:38
> >
> > - > - subject="Automated JBoss Testsuite"
> > - message="Automated JBoss Testsuite"
> > - from="[EMAIL PROTECTED]">
> > -
> > -
> > -
> > -
> > + > + subject="Automated JBoss Testsuite Results"
> > + message="Automated JBoss Testsuite Results"
> > + from="${run.nightly.email.from}"
> > + mailhost="${run.nightly.email.mailhost}"
> > +
>
files="${project.root}/testsuite/output/reports/text/TESTS-TestSuites.txt"
> > +/>
> > +
> > +
> > +
Laziness ;-)
ant complained that it did not recognise the mimemail task - and I
could not see it - until I upgraded my docs to be ant1.4beta2 - and
then I saw it was an optional task - I was too lazy to amend the
build.xml to recognise the task - especially when mail worked without
any extra config at least so I thought - but where are the daily
testing results this morning - according to the log files they were
sent...
Chris
=
Need somewhere to Live in London - http://freeflats.com
__
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jboss build.xml
> Laziness ;-) > > ant complained that it did not recognise the mimemail task - and I > could not see it - until I upgraded my docs to be ant1.4beta2 - and > then I saw it was an optional task - I was too lazy to amend the > build.xml to recognise the task - especially when mail worked without > any extra config at least so I thought - but where are the daily > testing results this morning - according to the log files they were > sent... You were not use the ant from tools then? I was thinking mimemail, so that we could eventually attach different versions of the report, like a summary, a detail and perhaps an html detail too. Please make sure you are building off of the version of ant from tools (ala the build. scripts. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] CVS update: build/jboss build.xml
thanks sorry for that marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Scott |M Stark |Sent: Wednesday, October 31, 2001 2:58 PM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] CVS update: build/jboss build.xml | | | User: starksm | Date: 01/10/31 11:58:27 | | Modified:jbossbuild.xml | Log: | Remove the obsolete idb.jar | | Revision ChangesPath | 1.44 +1 -4 build/jboss/build.xml | | Index: build.xml | === | RCS file: /cvsroot/jboss/build/jboss/build.xml,v | retrieving revision 1.43 | retrieving revision 1.44 | diff -u -r1.43 -r1.44 | --- build.xml2001/10/21 05:38:12 1.43 | +++ build.xml2001/10/31 19:58:26 1.44 | @@ -10,7 +10,7 @@ | | | | - | + | | | | @@ -1345,9 +1345,6 @@ | | | | - | - | - | | | | | | | |___ |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
Re: [JBoss-dev] CVS update: build/jboss build.xml
wow, sf mailing lists are really slow, this was done yesterday... --jason __ View: http://jboss.org/forums/thread.jsp?forum=66&thread=4930 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jboss build.xml
Diff is really odd sometimes... why did it decide that I added a new set of end tags and then filled in the rest. I don't think I could do that if I wanted too. I would get too confused. --jason > > > @@ -898,6 +898,14 @@ > > > > + > + > + > + > + > + > + > + > > > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] CVS update: build/jboss build.xml
You beat me :-))) Claudio > -Original Message- > From: Francisco Reverbel [SMTP:[EMAIL PROTECTED]] > Sent: Friday, April 19, 2002 3:25 PM > To: [EMAIL PROTECTED] > Subject: [JBoss-dev] CVS update: build/jboss build.xml > > User: reverbel > Date: 02/04/19 06:24:58 > > Modified:jbossTag: Branch_3_0 build.xml > Log: > Merged change from HEAD: copy iiop-service.xml to deploy dir. > > Revision ChangesPath > No revision > > > No revision > > > 1.117.2.2 +10 -1 build/jboss/build.xml > > Index: build.xml > === > RCS file: /cvsroot/jboss/build/jboss/build.xml,v > retrieving revision 1.117.2.1 > retrieving revision 1.117.2.2 > diff -u -r1.117.2.1 -r1.117.2.2 > --- build.xml 15 Apr 2002 09:36:40 - 1.117.2.1 > +++ build.xml 19 Apr 2002 13:24:57 - 1.117.2.2 > @@ -12,7 +12,7 @@ > > > > - > + > > > > @@ -1290,6 +1290,15 @@ > > > > + > + > + > + > + > + > + > + > + > > > > > > > > ___ > 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
Re: [JBoss-dev] CVS update: build/jboss build.xml
What a trully bizzare diff... I don't understand how it comes up with this... but whatever works. --jason Jason Dillon wrote: > User: user57 > Date: 02/04/19 16:40:36 > > Modified:jbossTag: Branch_3_0 build.xml > Log: > o include iiop & jboss.net in standard group > o drop optional-requires-config (becomes optional) > > Revision ChangesPath > No revision > > > No revision > > > 1.117.2.3 +6 -9 build/jboss/build.xml > > Index: build.xml > === > RCS file: /cvsroot/jboss/build/jboss/build.xml,v > retrieving revision 1.117.2.2 > retrieving revision 1.117.2.3 > diff -u -r1.117.2.2 -r1.117.2.3 > --- build.xml19 Apr 2002 13:24:57 - 1.117.2.2 > +++ build.xml19 Apr 2002 23:40:36 - 1.117.2.3 > @@ -12,7 +12,7 @@ > > > > - > + > > > > @@ -219,15 +219,12 @@ > cluster, > admin, > jetty, > - varia"/> > - > - > - > - > > > - > + > > > > @@ -238,11 +235,11 @@ > > > > - > + > > > > - > + > > > > > > > >___ >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
Re: [JBoss-dev] CVS update: build/jboss build.xml
version.name was never meant to have anything to do with cvs. It is there to hold the rather arbitrary name of a release (ie. rabbit-hole or whistler or merlin). While understand your desire to include cvs tag information, I do not think that this is the best place for it. I suggest we add a version.cvstag for this purpose. This is currently onlyt being used to generate the spec and impl bits for mf files right? --jason On Sun, 2002-02-17 at 07:44, Scott M Stark wrote: > User: starksm > Date: 02/02/17 07:44:38 > > Modified:jbossbuild.xml > Log: > Document the use of version.name as the cvs tag for any release build > > Revision ChangesPath > 1.85 +2 -1 build/jboss/build.xml > > Index: build.xml > === > RCS file: /cvsroot/jboss/build/jboss/build.xml,v > retrieving revision 1.84 > retrieving revision 1.85 > diff -u -r1.84 -r1.85 > --- build.xml 17 Feb 2002 15:07:14 - 1.84 > +++ build.xml 17 Feb 2002 15:44:38 - 1.85 > @@ -12,7 +12,7 @@ > > > > - > + > > > > @@ -65,6 +65,7 @@ > > > > + > > > > > > > > ___ > 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
Re: [JBoss-dev] CVS update: build/jboss build.xml
Why do we need a pet name variable that has nothing to do with obtaining a snapshot of the code? I don't care that 3.0 is also known by rabbithole. It meaningless. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Jason Dillon" <[EMAIL PROTECTED]> To: "Scott M Stark" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, February 17, 2002 4:36 PM Subject: Re: [JBoss-dev] CVS update: build/jboss build.xml > version.name was never meant to have anything to do with cvs. It is > there to hold the rather arbitrary name of a release (ie. rabbit-hole or > whistler or merlin). While understand your desire to include cvs tag > information, I do not think that this is the best place for it. > > I suggest we add a version.cvstag for this purpose. > > This is currently onlyt being used to generate the spec and impl bits > for mf files right? > > --jason > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jboss build.xml
Why does the server need to know anything about the source controlsystem which is being used to manage its sources? Pet names, as you say, are a time honored tradition amoung software developers. The are also used as a rememberance tool. Many folks will be more inclinded to remeber rabbit-hole than some arbitrary set of numbers. Along the same lines, our branch/tag naming system should be updated to include the name of the project, so we don't get namespace clashes when trying to branch jbossmq or jbossmx and such. > Why do we need a pet name variable that has nothing to > do with obtaining a snapshot of the code? I don't care > that 3.0 is also known by rabbithole. It meaningless. That is why we had shown the version as well as the version name before. It seems like you do care, or you would have left it alone. I understand that you wanted to provide versioning for all jars. I don't see how that relates to changing how we refer to the release. A side not, I don't think that the jar mf impl/spec is really the best place for this type of versioning... or rather I think that it should be expanded further. For example, there is no jboss spec... and for jars that actually do have a spec, what do we put there? What if one jar covers more than once spec. All in all the additions of this package stuff to the jdk was not very well thought out... --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jboss build.xml
> Why does the server need to know anything about the source controlsystem > which is being used to manage its sources? > > Pet names, as you say, are a time honored tradition amoung software > developers. The are also used as a rememberance tool. Many folks will be > more inclinded to remeber rabbit-hole than some arbitrary set of numbers. > > Along the same lines, our branch/tag naming system should be updated to > include the name of the project, so we don't get namespace clashes when > trying to branch jbossmq or jbossmx and such. > What do you mean by include the name of the project in the branch and version tag? Everything branches together so how it there going to be a clash? > > Why do we need a pet name variable that has nothing to > > do with obtaining a snapshot of the code? I don't care > > that 3.0 is also known by rabbithole. It meaningless. > > That is why we had shown the version as well as the version name before. > > It seems like you do care, or you would have left it alone. > I care that I can get the source code for a given release based on info included in the build and since I didn't see a reason to keep the name I used it for the version tag. > I understand that you wanted to provide versioning for all jars. I don't > see how that relates to changing how we refer to the release. > There is no change here. The release will have a JBoss_X_Y_Z version tag as its identifier. > A side not, I don't think that the jar mf impl/spec is really the best place > for this type of versioning... or rather I think that it should be expanded > further. For example, there is no jboss spec... and for jars that actually > do have a spec, what do we put there? What if one jar covers more than once > spec. All in all the additions of this package stuff to the jdk was not > very well thought out... If the jars have a spec that can be included in the specification tags. The implementation tags will be JBoss build info. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jboss build.xml
I thought we were still using R_* and Branch_* for tag names. As for the rest, I was just getting lost in the esthetics. I agree that we should include cvs tag information. --jason On Tue, 19 Feb 2002, Scott M Stark wrote: > > > Why does the server need to know anything about the source controlsystem > > which is being used to manage its sources? > > > > Pet names, as you say, are a time honored tradition amoung software > > developers. The are also used as a rememberance tool. Many folks will be > > more inclinded to remeber rabbit-hole than some arbitrary set of numbers. > > > > Along the same lines, our branch/tag naming system should be updated to > > include the name of the project, so we don't get namespace clashes when > > trying to branch jbossmq or jbossmx and such. > > > What do you mean by include the name of the project in the branch > and version tag? Everything branches together so how it there going > to be a clash? > > > > Why do we need a pet name variable that has nothing to > > > do with obtaining a snapshot of the code? I don't care > > > that 3.0 is also known by rabbithole. It meaningless. > > > > That is why we had shown the version as well as the version name before. > > > > It seems like you do care, or you would have left it alone. > > > I care that I can get the source code for a given release based on > info included in the build and since I didn't see a reason to keep > the name I used it for the version tag. > > > I understand that you wanted to provide versioning for all jars. I don't > > see how that relates to changing how we refer to the release. > > > There is no change here. The release will have a JBoss_X_Y_Z version > tag as its identifier. > > > A side not, I don't think that the jar mf impl/spec is really the best > place > > for this type of versioning... or rather I think that it should be > expanded > > further. For example, there is no jboss spec... and for jars that > actually > > do have a spec, what do we put there? What if one jar covers more than > once > > spec. All in all the additions of this package stuff to the jdk was not > > very well thought out... > If the jars have a spec that can be included in the specification tags. The > implementation tags will be JBoss build info. > > > > ___ > 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
Re: [JBoss-dev] CVS update: build/jboss build.xml
We are still using those tag names, what do you call this? - Original Message - From: "Jason Dillon" <[EMAIL PROTECTED]> To: "Scott M Stark" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, February 19, 2002 5:37 PM Subject: Re: [JBoss-dev] CVS update: build/jboss build.xml > I thought we were still using R_* and Branch_* for tag names. As for the > rest, I was just getting lost in the esthetics. I agree that we should > include cvs tag information. > > --jason > > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jboss build.xml
Ok, so I am not as crazy as I though I was. Basically if we were to start tagging other projects then we could run into namespace problems. It would be better to use something more like 'JBoss_Rel_3_0_0_3'. That is all I was trying to get across. --jason On Tue, 19 Feb 2002, Scott M Stark wrote: > We are still using those tag names, what do you call this? > > > - Original Message - > From: "Jason Dillon" <[EMAIL PROTECTED]> > To: "Scott M Stark" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Tuesday, February 19, 2002 5:37 PM > Subject: Re: [JBoss-dev] CVS update: build/jboss build.xml > > > > I thought we were still using R_* and Branch_* for tag names. As for the > > rest, I was just getting lost in the esthetics. I agree that we should > > include cvs tag information. > > > > --jason > > > > > > > > ___ > 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
Re: [JBoss-dev] CVS update: build/jboss build.xml
What do you mean by other projects? - Original Message - From: "Jason Dillon" <[EMAIL PROTECTED]> To: "Scott M Stark" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, February 19, 2002 5:59 PM Subject: Re: [JBoss-dev] CVS update: build/jboss build.xml > Ok, so I am not as crazy as I though I was. Basically if we were to start > tagging other projects then we could run into namespace problems. It would > be better to use something more like 'JBoss_Rel_3_0_0_3'. > > That is all I was trying to get across. > > --jason > > > On Tue, 19 Feb 2002, Scott M Stark wrote: > > > We are still using those tag names, what do you call this? > > > > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jboss build.xml
Like the JBossMQ and JBossMX stuff... --jason On Tue, 19 Feb 2002, Scott M Stark wrote: > > What do you mean by other projects? > > - Original Message - > From: "Jason Dillon" <[EMAIL PROTECTED]> > To: "Scott M Stark" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Tuesday, February 19, 2002 5:59 PM > Subject: Re: [JBoss-dev] CVS update: build/jboss build.xml > > > > Ok, so I am not as crazy as I though I was. Basically if we were to start > > tagging other projects then we could run into namespace problems. It > would > > be better to use something more like 'JBoss_Rel_3_0_0_3'. > > > > That is all I was trying to get across. > > > > --jason > > > > > > On Tue, 19 Feb 2002, Scott M Stark wrote: > > > > > We are still using those tag names, what do you call this? > > > > > > > > > > ___ > 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
Re: [JBoss-dev] CVS update: build/jboss build.xml
When we have done a standalone release of a subcomponent then its tag does include the project name. The only release that has been done is one of jbossmq with a tag of RelMQ_1_0_0_1 as it never was released in a final first version form. Update the cvs admin page to clarify this. - Original Message - From: "Jason Dillon" <[EMAIL PROTECTED]> To: "Scott M Stark" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, February 19, 2002 6:14 PM Subject: Re: [JBoss-dev] CVS update: build/jboss build.xml > Like the JBossMQ and JBossMX stuff... > > --jason > > > On Tue, 19 Feb 2002, Scott M Stark wrote: > > > > > What do you mean by other projects? ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jboss build.xml
On Tue, 19 Feb 2002, Jason Dillon wrote: > Like the JBossMQ and JBossMX stuff... Or what about thirdparty projects that are maintained in jboss cvs(ie, jetty)? ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jboss build.xml
We won't do releases of Jetty as Mortbay has their own Sourceforge project that handles that. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Adam Heath" <[EMAIL PROTECTED]> To: "Jason Dillon" <[EMAIL PROTECTED]> Cc: "Scott M Stark" <[EMAIL PROTECTED]>; "JBoss Development" <[EMAIL PROTECTED]> Sent: Tuesday, February 19, 2002 6:52 PM Subject: Re: [JBoss-dev] CVS update: build/jboss build.xml > On Tue, 19 Feb 2002, Jason Dillon wrote: > > > Like the JBossMQ and JBossMX stuff... > > Or what about thirdparty projects that are maintained in jboss cvs(ie, jetty)? > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jboss build.xml
On Tue, 19 Feb 2002, Scott M Stark wrote: > We won't do releases of Jetty as Mortbay has their own Sourceforge > project that handles that. Understood, that's not what I mean to imply. What I meant, was that if a thirdparty checkins in source, and when doing, they use the same tagname as what was in their local cvs repository. Then, when jboss gets ready to release, the entire repository gets tagged. I would hope that both projects would not have clashing tag names. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jboss build.xml
Are you about to do another beta build? I've finished my changes for the ear deployer problem, I think it fixes 1 bug in the testsuite, and I'm finishing an explicit test case. If no one objects I'd like to check it in before the next beta. thanks david jencks On 2002.02.21 21:51:16 -0500 Scott M Stark wrote: > User: starksm > Date: 02/02/21 18:51:16 > > Modified:jbossbuild.xml > Log: > Beta Rel_3_0_0_3 is already history > > Revision ChangesPath > 1.89 +3 -3 build/jboss/build.xml > > Index: build.xml > === > RCS file: /cvsroot/jboss/build/jboss/build.xml,v > retrieving revision 1.88 > retrieving revision 1.89 > diff -u -r1.88 -r1.89 > --- build.xml 21 Feb 2002 23:33:18 - 1.88 > +++ build.xml 22 Feb 2002 02:51:16 - 1.89 > @@ -12,7 +12,7 @@ > > > > - > + > > > > @@ -64,9 +64,9 @@ > > > > - > + > > - > + > > > > > > > > ___ > 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
Re: [JBoss-dev] CVS update: build/jboss build.xml
There will not be another beta release for at least a couple weeks. - Original Message - From: "David Jencks" <[EMAIL PROTECTED]> To: "Scott M Stark" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, February 21, 2002 7:56 PM Subject: Re: [JBoss-dev] CVS update: build/jboss build.xml > Are you about to do another beta build? I've finished my changes for the > ear deployer problem, I think it fixes 1 bug in the testsuite, and I'm > finishing an explicit test case. If no one objects I'd like to check it in > before the next beta. > > thanks > david jencks > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
