ntext it is found. This
has been
done so the second datasource element simply needs to be removed. I have
done this.
- Original Message -
From: "Vinay Menon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 11, 2001 4:00 PM
Subject: Re: [JBoss-dev] jaws
You can have only one definition of the datasource element - and that's
all we need since it's the same either place (just contains CDATA). As
long as it's listed as a possible contained element for both the global
jaws element, and the entity-bean element, we should be fine. Unless I'm
missin
Mike,
That is a bean level datasource and quite obviously cannot be commented
out in principal! I mean if you got to have a bean level ds you got to have
one! Client programs should be able to define a datasource at the file level
i.e. applicable to all the beans declared in the jaws.xml and t
ense is to have the version
track the corresponding J2EE dtd version with a patch level added, so:
jboss_2_0_1.dtd
jboss-web_2_2_0.dtd
- Original Message -
From: "Vinay Menon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 08, 2001 5:34 AM
Subje
Correct.
- Original Message -
From: "Vincent Harcq" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 08, 2001 5:14 AM
Subject: RE: [JBoss-dev] JAWS_2_4 DTD
> I am not sure Scott is around, so I'll try to explain.
>
> I check out "
TED]]De la part de
> > Vinay Menon
> > Envoyé : dimanche 8 juillet 2001 14:33
> > À : [EMAIL PROTECTED]
> > Objet : Re: [JBoss-dev] JAWS_2_4 DTD
> >
> >
> > Vincent,
> > Many thanks! I've commited the changes to the jaws.dtd and
> &
bad wording - I meant that the change had been done a wee while back but it
hadn't shown up on labels created since it had been committed. (At least I
think labels have been created since it was committed)
Mike S-R
>A change typically does not use the latest label if that is what your
>referri
gt; was the last
> used tag and am going to increment it by one as you said and tag it. What
> about the trunk?
>
> Vinay
>
> - Original Message -
> From: "Vincent Harcq" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, July 08, 20
Isn't is a slight misnomer then if we have things like jaws_2_4.dtd in the
main trunk?
- Original Message -
From: "marc fleury" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 08, 2001 1:33 PM
Subject: RE: [JBoss-dev] JAWS_2_4 DTD
> ok
d tag it. What
about the trunk?
Vinay
- Original Message -
From: "Vincent Harcq" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 08, 2001 1:14 PM
Subject: RE: [JBoss-dev] JAWS_2_4 DTD
> I am not sure Scott is around, so I'll try to explain.
oka
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Sunday, July 08, 2001 2:04 AM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] JAWS_2_4 DTD
|
|
|We decided to forgo an explicit future 3.0 branch and just make main
|the
De la part de
> Vinay Menon
> Envoyé : dimanche 8 juillet 2001 13:48
> À : [EMAIL PROTECTED]
> Objet : Re: [JBoss-dev] JAWS_2_4 DTD
>
>
> Scott,
> Alright did go thru the document. I am a complete CVS dumbo. Is this
> what I need to do
>
> 1. Check in all the changes
ce.
Vinay
- Original Message -
From: "Scott M Stark" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 08, 2001 12:15 AM
Subject: Re: [JBoss-dev] JAWS_2_4 DTD
> kvvinaymenon,
>
> You need to follow the cvs proceedures for updating a branch and making
sure
>
Will clean it up today ... once I get around the CVS policy documentation ..
it is a pretty complex beast!
- Original Message -
From: "Scott M Stark" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 08, 2001 12:15 AM
Subject: Re: [JBoss-dev] JAWS_2_
t; <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 07, 2001 9:07 PM
Subject: RE: [JBoss-dev] JAWS_2_4 DTD
> ok good, so I need to deal with the branch stuff only if I want to back
port
> something. Ok.
>
> what happened to the 3.0 branch? I am finishing the jive
L PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Saturday, July 07, 2001 11:49 PM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] JAWS_2_4 DTD
|
|
|Right, you committed to main. This is the 2.5 effort although its not a
|branch.
|
|- Original Message -
|From: "marc fleury" <[EM
Right, you committed to main. This is the 2.5 effort although its not a
branch.
- Original Message -
From: "marc fleury" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 07, 2001 6:34 PM
Subject: RE: [JBoss-dev] JAWS_2_4 DTD
> ok,
> I am
ECTED]
|Subject: Re: [JBoss-dev] JAWS_2_4 DTD
|
|
|Yes, every incremental change made on a branch needs to be tagged to
|make it easy to identify the changes going into a release.
|
|- Original Message -
|From: "Aaron Mulder" <[EMAIL PROTECTED]>
|To: <[EMAIL PROTECTED]&g
Yes, every incremental change made on a branch needs to be tagged to
make it easy to identify the changes going into a release.
- Original Message -
From: "Aaron Mulder" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 07, 2001 4:18 PM
Subject: Re
On Sat, 7 Jul 2001, Scott M Stark wrote:
> When you make a change to a branch you need to tag it with the
> next beta binary release tag: Rel_...
Are you saying that a release does not just label and use the
"head of the branch" but is built based on a label created at the time of
the pre
When you make a change to a branch you need to tag it with the
next beta binary release tag: Rel_...
A change typically does not use the latest label if that is what your
referring to as the "current 2_4 label".
>
> the datasource element was added to the entity element in version 1.1.2.2
> on B
kvvinaymenon,
You need to follow the cvs proceedures for updating a branch and making sure
the changes are applied to main. Read them here:
http://www.jboss.org/CVSAdmin.jsp
and then clean up your changes.
- Original Message -
From: "Mike Swainston-Rainford" <[EMAIL PROTECTED]>
To: <[EMA
22 matches
Mail list logo
