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
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
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
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
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
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
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
] 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
: [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
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
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
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]
]
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
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
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
-
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
wow, sf mailing lists are really slow, this was done yesterday...
--jason
__
View: http://jboss.org/forums/thread.jsp?forum=66thread=4930
___
Jboss-development mailing list
[EMAIL
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
project default=main name=JBoss/Build
@@ -898,6 +898,14 @@
fileset
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:
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
!-- email output to list --
-mimemail tolist=[EMAIL PROTECTED]
- subject=Automated JBoss
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
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:
22 matches
Mail list logo
