You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Mladen Turk <mt...@apache.org> on 2006/06/26 15:16:53 UTC
Tomcat sandbox
Hi all,
IMO this is mostly Costin related, because he has something
inside the sandbox :)
Now my question is, could the current sandbox content be
moved to the /sandbox/abc so I (or someone else)
can create a /sandbox/xyz ?
Right now the sandbox is not the 'sandbox' but rather
the Tomcat6Sanbox thought.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?
Posted by Rainer Jung <ra...@kippdata.de>.
Rainer Jung schrieb:
> After releasing I would also love to change repos structure to make
> deprecated code much more visible. More precisely: I would first like to
> build consensus on what parts are deprecated.
Sorry: I meant "to make the deprecation much more visible".
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?
Posted by Rainer Jung <ra...@kippdata.de>.
The reason to change names is the same, as it was during TC 5.5
development, to reflect the TLP status of tomcat.
This will not be a change in java packages or svn directory names. The
change will only be visible in documentation and it the name of the
download file will change. In some parts of the documentation this
already happened.
I think we should do it completely to keep names consistent with the
tomcat naming.
I'm preparing a mod_jk release, which is independent of the TC version.
It contains only the native parts (no change with that) so it's
compatible with a wide range of tomcat versions.
After releasing I would also love to change repos structure to make
deprecated code much more visible. More precisely: I would first like to
build consensus on what parts are deprecated.
Rainer
Costin Manolache schrieb:
> And why are you doing this ?
>
> For tomcat5 - I don't see how much it helps. For tomcat6+ - I think the
> main issue is figuring where to put the native code so the duplicated
> java source trees don't confuse people. Given how much unused native
> we have, it may be good to just move mod_jk and whatever else is still
> used to tomcat6/ repo.
>
> Costin
>
> On 6/28/06, Rainer Jung <ra...@kippdata.de> wrote:
>>
>> I think it's time to rename jakarta-tomcat-connectors to
>> tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
>> artefacts inside the connectors module and concerning the download.
>>
>> Does anyone know about external references we might break?
>>
>> Rainer
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: dev-help@tomcat.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
AJP version
Posted by ga...@free.fr.
Hi,
I am working on mod_jk in order to add a mechanism wich would be able to bind
dynamically a client to a particular worker, something like the sticky-session.
So, I have found three files jk_ajp1{2|3|4}_worker.c, I suppose
jk_ajp12_worker.c is for the version 1.2 of the ajp protocol, and so on for the
others files...
I am currently using the version 1.3, and I have two questions:
First question :
Simply, what is the difference between ajp12, ajp13 and ajp14?
I want to understand, if this may influence the loadbalancer work.
Second question:
Is there a best version?
Thanks
Thomas d'Erceville
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?
Posted by Rainer Jung <ra...@kippdata.de>.
I understand, but for mod_jk the situation is different. It's neither
tightly coupled to a tomcat release, nor is it simply maintenance.
I think the situation is very similar to the renaming of tomcat 5.5.
I committed the necessary changes yesterday, so everyone can have a look
at it:
http://svn.apache.org/viewvc?rev=417906&view=rev
Rainer
Costin Manolache schrieb:
> "Jakarta Tomcat" was used in many contexts, and I don't see why a user
> would be confused - or care or know what a TLP is. That's internal
> apache organization.
>
> My point is - it would be better to stop using jakarta for future, and not
> change the
> past. Tomcat5 was released as 'jakarta tomcat', and it's more or less
> history - we
> make sort of maintainance releases.
>
> For tomcat6 and other future releases - we can stop using jakarta.
>
> Costin
>
> On 6/28/06, Yoav Shapira <yo...@apache.org> wrote:
>>
>> Hi,
>>
>> On 6/28/06, Costin Manolache <co...@gmail.com> wrote:
>> > And why are you doing this ?
>>
>> Why are we doing the renaming? Because the relevant project is no
>> longer part of Jakarta, so to avoid confusion among users, be
>> consistent with other Tomcat code, discharge the Jakarta PMC from
>> responsibility, etc. Ideally we would have done this right after we
>> became a TLP, but better late then never.
>>
>> Or did you mean something else other than the renaming by "this" in
>> the above question?
>>
>> Yoav
>>
>> >
>> > For tomcat5 - I don't see how much it helps. For tomcat6+ - I think the
>> > main issue is figuring where to put the native code so the duplicated
>> > java source trees don't confuse people. Given how much unused native
>> > we have, it may be good to just move mod_jk and whatever else is still
>> > used to tomcat6/ repo.
>> >
>> > Costin
>> >
>> > On 6/28/06, Rainer Jung <ra...@kippdata.de> wrote:
>> > >
>> > > I think it's time to rename jakarta-tomcat-connectors to
>> > > tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
>> > > artefacts inside the connectors module and concerning the download.
>> > >
>> > > Does anyone know about external references we might break?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?
Posted by Costin Manolache <co...@apache.org>.
"Jakarta Tomcat" was used in many contexts, and I don't see why a user
would be confused - or care or know what a TLP is. That's internal
apache organization.
My point is - it would be better to stop using jakarta for future, and not
change the
past. Tomcat5 was released as 'jakarta tomcat', and it's more or less
history - we
make sort of maintainance releases.
For tomcat6 and other future releases - we can stop using jakarta.
Costin
On 6/28/06, Yoav Shapira <yo...@apache.org> wrote:
>
> Hi,
>
> On 6/28/06, Costin Manolache <co...@gmail.com> wrote:
> > And why are you doing this ?
>
> Why are we doing the renaming? Because the relevant project is no
> longer part of Jakarta, so to avoid confusion among users, be
> consistent with other Tomcat code, discharge the Jakarta PMC from
> responsibility, etc. Ideally we would have done this right after we
> became a TLP, but better late then never.
>
> Or did you mean something else other than the renaming by "this" in
> the above question?
>
> Yoav
>
> >
> > For tomcat5 - I don't see how much it helps. For tomcat6+ - I think the
> > main issue is figuring where to put the native code so the duplicated
> > java source trees don't confuse people. Given how much unused native
> > we have, it may be good to just move mod_jk and whatever else is still
> > used to tomcat6/ repo.
> >
> > Costin
> >
> > On 6/28/06, Rainer Jung <ra...@kippdata.de> wrote:
> > >
> > > I think it's time to rename jakarta-tomcat-connectors to
> > > tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
> > > artefacts inside the connectors module and concerning the download.
> > >
> > > Does anyone know about external references we might break?
> > >
> > > Rainer
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> > > For additional commands, e-mail: dev-help@tomcat.apache.org
> > >
> > >
> >
> >
>
>
> --
> Yoav Shapira
> Nimalex LLC
> 1 Mifflin Place, Suite 310
> Cambridge, MA, USA
> yoavs@computer.org / www.yoavshapira.com
>
Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?
Posted by Yoav Shapira <yo...@apache.org>.
Hi,
On 6/28/06, Costin Manolache <co...@gmail.com> wrote:
> And why are you doing this ?
Why are we doing the renaming? Because the relevant project is no
longer part of Jakarta, so to avoid confusion among users, be
consistent with other Tomcat code, discharge the Jakarta PMC from
responsibility, etc. Ideally we would have done this right after we
became a TLP, but better late then never.
Or did you mean something else other than the renaming by "this" in
the above question?
Yoav
>
> For tomcat5 - I don't see how much it helps. For tomcat6+ - I think the
> main issue is figuring where to put the native code so the duplicated
> java source trees don't confuse people. Given how much unused native
> we have, it may be good to just move mod_jk and whatever else is still
> used to tomcat6/ repo.
>
> Costin
>
> On 6/28/06, Rainer Jung <ra...@kippdata.de> wrote:
> >
> > I think it's time to rename jakarta-tomcat-connectors to
> > tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
> > artefacts inside the connectors module and concerning the download.
> >
> > Does anyone know about external references we might break?
> >
> > Rainer
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: dev-help@tomcat.apache.org
> >
> >
>
>
--
Yoav Shapira
Nimalex LLC
1 Mifflin Place, Suite 310
Cambridge, MA, USA
yoavs@computer.org / www.yoavshapira.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?
Posted by Costin Manolache <co...@gmail.com>.
And why are you doing this ?
For tomcat5 - I don't see how much it helps. For tomcat6+ - I think the
main issue is figuring where to put the native code so the duplicated
java source trees don't confuse people. Given how much unused native
we have, it may be good to just move mod_jk and whatever else is still
used to tomcat6/ repo.
Costin
On 6/28/06, Rainer Jung <ra...@kippdata.de> wrote:
>
> I think it's time to rename jakarta-tomcat-connectors to
> tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
> artefacts inside the connectors module and concerning the download.
>
> Does anyone know about external references we might break?
>
> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?
Posted by Henri Gomez <he...@gmail.com>.
It make sense.
+0
2006/6/28, Rainer Jung <ra...@kippdata.de>:
> I think it's time to rename jakarta-tomcat-connectors to
> tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
> artefacts inside the connectors module and concerning the download.
>
> Does anyone know about external references we might break?
>
> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?
Posted by Yoav Shapira <yo...@apache.org>.
+1 to renaming.
Yoav
On 6/28/06, Rainer Jung <ra...@kippdata.de> wrote:
> That's part of what I'll be doing.
>
> Jean-frederic Clere schrieb:
> > Rainer Jung wrote:
> >
> >> I think it's time to rename jakarta-tomcat-connectors to
> >> tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
> >> artefacts inside the connectors module and concerning the download.
> >>
> >> Does anyone know about external references we might break?
> >
> > The web pages (connectors) are still telling "jakarta-bla..." that also
> > needs fixing.
> >
> > Cheers
> >
> > Jean-Frederic
> >
> >>
> >> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
--
Yoav Shapira
Nimalex LLC
1 Mifflin Place, Suite 310
Cambridge, MA, USA
yoavs@computer.org / www.yoavshapira.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?
Posted by Rainer Jung <ra...@kippdata.de>.
That's part of what I'll be doing.
Jean-frederic Clere schrieb:
> Rainer Jung wrote:
>
>> I think it's time to rename jakarta-tomcat-connectors to
>> tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
>> artefacts inside the connectors module and concerning the download.
>>
>> Does anyone know about external references we might break?
>
> The web pages (connectors) are still telling "jakarta-bla..." that also
> needs fixing.
>
> Cheers
>
> Jean-Frederic
>
>>
>> Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?
Posted by Jean-frederic Clere <jf...@gmail.com>.
Rainer Jung wrote:
> I think it's time to rename jakarta-tomcat-connectors to
> tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
> artefacts inside the connectors module and concerning the download.
>
> Does anyone know about external references we might break?
The web pages (connectors) are still telling "jakarta-bla..." that also
needs fixing.
Cheers
Jean-Frederic
>
> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Renaming jakarta-tomcat-connectors to tomcat-connectors?
Posted by Rainer Jung <ra...@kippdata.de>.
I think it's time to rename jakarta-tomcat-connectors to
tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
artefacts inside the connectors module and concerning the download.
Does anyone know about external references we might break?
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: mod_jk release plan
Posted by Jean-frederic Clere <jf...@gmail.com>.
Rainer Jung wrote:
> Hi,
>
> I would like to start releasing mod_jk 1.2.16 this week.
>
> Since our last release was done from CVS and there are several updates
> to the tool chain (autoconf/automake/m4/libtool), there is some risk
> of breaking the release (additionally to mod_jk code bugs).
> For that reason I would propose to tag as 1.2.16-rc1, because we might
> need to have a second try on releasing it.
>
> So I would propose, that I will
>
> - take the role as RM for mod_jk 1.2.16
> - tag mod_jk soon as 1.2.16-rc1
> - roll a tarball and inform the dev- and user-list about availability
> of a release candidate and invite to test it.
> - in case of negative testing: fix, retag as rc2, reroll etc.
> - after positive testing start the vote
> - after positive voting copy the final rc-tag to 1.2.16 and reroll the
> final release containing the right version numbers.
> - finally announce the official release
>
> Any comments?
Great +1
Cheers
Jean-Frederic
>
> Rainer
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: mod_jk release plan
Posted by Mladen Turk <mt...@apache.org>.
Rainer Jung wrote:
> Hi,
>
> I would like to start releasing mod_jk 1.2.16 this week.
>
> Any comments?
>
+1
--
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: mod_jk release plan
Posted by Yoav Shapira <yo...@apache.org>.
Hi,
+1 to Rainer's general plan, +0 to making release numbering / release
candidate approach consistent with Tomcat.
Yoav
On 6/27/06, David Rees <dr...@gmail.com> wrote:
> On 6/27/06, Mladen Turk <mt...@apache.org> wrote:
> > Right, release numbers are cheap.
> > We are number 16 after so many years after all :)
> >
> > Anyhow, just release 1.2.16, and if its broken
> > make 1.2.17.
>
> I'll be sure to give it a test on Linux and IRIX once the tarball is rolled. :-)
>
> -Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
--
Yoav Shapira
Nimalex LLC
1 Mifflin Place, Suite 310
Cambridge, MA, USA
yoavs@computer.org / www.yoavshapira.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: mod_jk release plan
Posted by David Rees <dr...@gmail.com>.
On 6/27/06, Mladen Turk <mt...@apache.org> wrote:
> Right, release numbers are cheap.
> We are number 16 after so many years after all :)
>
> Anyhow, just release 1.2.16, and if its broken
> make 1.2.17.
I'll be sure to give it a test on Linux and IRIX once the tarball is rolled. :-)
-Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: mod_jk release plan
Posted by Henri Gomez <he...@gmail.com>.
+0
2006/6/27, Mladen Turk <mt...@apache.org>:
> David Rees wrote:
> > On 6/27/06, Rainer Jung <ra...@kippdata.de> wrote:
> >> - take the role as RM for mod_jk 1.2.16
> >> - tag mod_jk soon as 1.2.16-rc1
> >
> > Why not do releases like tomcat/httpd do it? Go ahead and
> > rollup/release 1.2.16, then vote on the stability. If there are
> > problems, roll up another release (1.2.17) for more testing.
>
> Right, release numbers are cheap.
> We are number 16 after so many years after all :)
>
> Anyhow, just release 1.2.16, and if its broken
> make 1.2.17.
>
> Regards,
> Mladen.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: mod_jk release plan
Posted by Mladen Turk <mt...@apache.org>.
David Rees wrote:
> On 6/27/06, Rainer Jung <ra...@kippdata.de> wrote:
>> - take the role as RM for mod_jk 1.2.16
>> - tag mod_jk soon as 1.2.16-rc1
>
> Why not do releases like tomcat/httpd do it? Go ahead and
> rollup/release 1.2.16, then vote on the stability. If there are
> problems, roll up another release (1.2.17) for more testing.
Right, release numbers are cheap.
We are number 16 after so many years after all :)
Anyhow, just release 1.2.16, and if its broken
make 1.2.17.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: mod_jk release plan
Posted by David Rees <dr...@gmail.com>.
On 6/27/06, Rainer Jung <ra...@kippdata.de> wrote:
> - take the role as RM for mod_jk 1.2.16
> - tag mod_jk soon as 1.2.16-rc1
> - roll a tarball and inform the dev- and user-list about availability of
> a release candidate and invite to test it.
> - in case of negative testing: fix, retag as rc2, reroll etc.
> - after positive testing start the vote
> - after positive voting copy the final rc-tag to 1.2.16 and reroll the
> final release containing the right version numbers.
Why not do releases like tomcat/httpd do it? Go ahead and
rollup/release 1.2.16, then vote on the stability. If there are
problems, roll up another release (1.2.17) for more testing. Repeat
until you have a tarball that is ready for production, that way you
still don't risk the chance of breaking something when you re-tag the
non-rc release and rebuild the tarball (however small that chance may
be) because if you do, you'll have to bump the version number and
re-release anyway.
-Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
mod_jk release plan
Posted by Rainer Jung <ra...@kippdata.de>.
Hi,
I would like to start releasing mod_jk 1.2.16 this week.
Since our last release was done from CVS and there are several updates
to the tool chain (autoconf/automake/m4/libtool), there is some risk of
breaking the release (additionally to mod_jk code bugs).
For that reason I would propose to tag as 1.2.16-rc1, because we might
need to have a second try on releasing it.
So I would propose, that I will
- take the role as RM for mod_jk 1.2.16
- tag mod_jk soon as 1.2.16-rc1
- roll a tarball and inform the dev- and user-list about availability of
a release candidate and invite to test it.
- in case of negative testing: fix, retag as rc2, reroll etc.
- after positive testing start the vote
- after positive voting copy the final rc-tag to 1.2.16 and reroll the
final release containing the right version numbers.
- finally announce the official release
Any comments?
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Tomcat sandbox
Posted by Mladen Turk <mt...@apache.org>.
Costin Manolache wrote:
> You mean to remove the 'single tree', and only have components ? I can live
> with this,
> but I don't think it's the best idea - and I haven't seen any reasons for
> that.
>
> The idea of the sandbox is that you can try things in it - including the
> single source tree :-)
>
Right. But in a way to have multiple projects in the sandbox.
It changes nothing for a code you have in there right now.
Instead
/tomcat/sandbox/
the current code should be moved to something like
/tomcat/sandbox/tc6lite/ or what ever.
Its still the single source tree :)
OTOH it would allow to have experimental
/tomcat/sandbox/foo/ project also as a single source tree.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Tomcat sandbox
Posted by Costin Manolache <co...@gmail.com>.
You mean to remove the 'single tree', and only have components ? I can live
with this,
but I don't think it's the best idea - and I haven't seen any reasons for
that.
The idea of the sandbox is that you can try things in it - including the
single source tree :-)
Why don't you start a component directory under sandbox first, see if the
single java/ tree
bothers you in any way - and if you find a problem ( your IDE can't exclude
it, etc ) then
I can move it to a subdir.
Costin
On 6/26/06, Rainer Jung <ra...@kippdata.de> wrote:
>
> I should have been more explicit: +1 for cleaning it up according to the
> README :)
>
> Mladen Turk schrieb:
> > Rainer Jung wrote:
> >> Hi Mladen,
> >>
> >> Costins README.txt inside the sandbox already suggested:
> >>
> >
> > I know, I read the README, but the content inside does
> > not follow the README. That's the point :)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
Re: Tomcat sandbox
Posted by Rainer Jung <ra...@kippdata.de>.
I should have been more explicit: +1 for cleaning it up according to the
README :)
Mladen Turk schrieb:
> Rainer Jung wrote:
>> Hi Mladen,
>>
>> Costins README.txt inside the sandbox already suggested:
>>
>
> I know, I read the README, but the content inside does
> not follow the README. That's the point :)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Tomcat sandbox
Posted by Mladen Turk <mt...@apache.org>.
Rainer Jung wrote:
> Hi Mladen,
>
> Costins README.txt inside the sandbox already suggested:
>
I know, I read the README, but the content inside does
not follow the README. That's the point :)
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Tomcat sandbox
Posted by Rainer Jung <ra...@kippdata.de>.
Hi Mladen,
Costins README.txt inside the sandbox already suggested:
===
Sandbox components should be developed in a sub-directory of the /tomcat/sandbox
directory. Developers may choose whether to add source directly under the
component's directory or to create the standard subversion /trunk/, /branches/
and /tags/ directories and add the source under the /trunk/ directory.
The svn commands to do this will look something like:
svn mkdir https://svn.apache.org/repos/asf/tomcat/sandbox/component
svn mkdir https://svn.apache.org/repos/asf/tomcat/sandbox/component/trunk
svn mkdir https://svn.apache.org/repos/asf/tomcat/sandbox/component/branches
svn mkdir https://svn.apache.org/repos/asf/tomcat/sandbox/component/tags
Alternatively, you can use the java/ directory. If possible:
1. create a new package ( or few ) for each module
2. if you have an external dependency for an optional component - create a new package.
3. Update the top level build.xml file with targets for your module - use <include> patterns instead
of exclude.
The single tree may help increase visibility of the source code. We are in 2005 ( or more ), build tools
and IDEs have very good support for include/exclude patterns, we have tools to find dependencies between
packages, and we have a single community, so we don't need fragmented source trees and more, at least in
sandbox.
===
+1 for the "components" way of doing it. More precisely to prevent
duplicate trees, component should include a more precise description of
the issue, otherwise we might soon end up blocking general dirs like
"cluster", "connectors" etc.
Regards,
Rainer
Mladen Turk schrieb:
> Hi all,
>
> IMO this is mostly Costin related, because he has something
> inside the sandbox :)
> Now my question is, could the current sandbox content be
> moved to the /sandbox/abc so I (or someone else)
> can create a /sandbox/xyz ?
>
> Right now the sandbox is not the 'sandbox' but rather
> the Tomcat6Sanbox thought.
>
> Regards,
> Mladen.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org