You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by Christopher Lenz <cm...@gmx.de> on 2002/02/12 16:41:36 UTC

Bugfix release ? (WAS: Re: adding users to namespace)

Which reminds me... has anyone been porting bugfixes (in the WebDAV Servlet for 
example) back to the 1.0 branch so that we can release bugfix releases ?

------- Start of forwarded message -------
From: Christopher Lenz <cm...@gmx.de>
To: "Slide Users List" <sl...@jakarta.apache.org>
Reply-To: "Slide Users List" <sl...@jakarta.apache.org>
Subject: Fwd: Re: adding users to namespace
Date: 12.02.2002 15:53:11

Hi Cevat,

I've checked this behaviour, and you're right: it's a bug in Slide, 
having to do with use of the admin web-app in the context of the 
tomcat-integrated distribution (which I don't use heavily, so I 
didn't notice the problem before).

Bug report at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6398
I'll fix the problem as soon as possible. Thanks for the report.

12.02.2002 15:29:53, "Cevat Ikibas" <ce...@hotmail.com> wrote:
>
>
>Hello!
>
>I ahve added new namespace to slide along with the slide itself
>I can see both
>http://localhost:808x/slide
>http://localhost:808x/newnamespace
>
>but when I intended to add new users to new namespace by using
>http://localhost:8082/newnamespape
>it adds the users to slide, that is strange right?
>Is there any one who would like to help me out with this?
>any help would be appriciated
>thank you
>

-chris
_______________________________________________
 /=/ cmlenz at gmx.de




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


-------- End of forwarded message --------
-chris
_______________________________________________
 /=/ cmlenz at gmx.de





--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Slide and DASL

Posted by Jean-Philippe Courson <co...@noos.fr>.
Hi,

Can anybody tell me what is the progress state of DASL works ?
What is already defined ?
What is already implemented ?
What should be shortly done ?
What are the long term plans about DASL ?

Thanks in advance.

JP


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Bugfix release ? (WAS: Re: adding users to namespace)

Posted by Colin Britton <cb...@metatomix.com>.
>
> The J2EE content store doesn't have the latest code at the moment (or we
> need to merge the two stores).
>

We have prepared a version of the J2EE content store based on the new XA
based descriptor store. We have been running it on one of our test servers
over the weekend, will post it tomorrow.

rgds
CB


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Bugfix release ? (WAS: Re: adding users to namespace)

Posted by Remy Maucherat <re...@apache.org>.
> [snip]
> >> What would the version number of this release be? 1.1.0 (beta) or
> >> 1.0.17 (beta)?
> >
> >It depends on how significant we feel the changes over 1.0.16 are.
> >If we also add the iems mentioned above, 1.1.0 looks a good version
> >number.
>
> Yeah, I'll also investigate making the directory-browsing feature of
> the WebdavServlet more flexible: letting the user define a directory-
> browsing-template URL that should point to a JSP that handles the
> (mostly) HTML stuff. then, there'd be 3 versions of the JSP: one using
> just standard Java against the Slide/WebDAV API (essentially moving
> the HTML display code out of WebdavServlet.java), the two others using
> the Struts and JSTL taglib, respectively.
>
> That change would go into HEAD as well as SLIDE_1_0, since I
> personally think it's a feature a lot of people might want from Slide.

Yes, that is obviously a very nice user-oriented feature.

> >> [And btw, why's Slide the only Jakarta-project using
> >> that versioning scheme? ;o)]
> >
> >It's Apache 2 versioning number. I liked it, proposed it a while ago,
> >and it was accepted. Quite frankly I expected it to become used by
> >other projects at Apache, but it didn't happen.
>
> I don't remember if I was already involved at that time, but I find
> the numbering scheme a bit confusing, to be honest :P. Especially in
> being unclear about alpha/beta/stable status.

I started realizing this numbering scheme may be a good idea during the
development process of Tomcat 4 (where there was the "M"-series, followed by
the "Beta" series, and then by the "RC" series); I felt it was more
consistent. I wouldn't change the numbering scheme in the current branch
(otherwise, it would really start confusing people IMO). We could change it
for future releases, of course.

Remy


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Bugfix release ? (WAS: Re: adding users to namespace)

Posted by Christopher Lenz <cm...@gmx.de>.
24.02.2002 22:28:23, "Remy Maucherat" <re...@apache.org> wrote:
[snip]
>> So, I've spent some time today to go through the commit messages of
>> the past 3 months and browsing through cvsview. I've come up with a
>> list of changes that I personally consider "portable" to 1.0, i.e. 
not
>> necessarily bug-fixes in the strict sense, but also clean-up and 
tiny
>> feature-additions. I've attached a list of the commit messages
>> (without the diffs), annotated with comments about what I think 
should
>> be done. I have applied most of the changes in that list to my 
local
>> working copy of the 1.0 branch, and couldn't find any serious
>> problems, but more testing will follow.
>
>Great initiative. Extremely useful work :)
>+1 for the proposed changes (I didn't go through the list item by 
>item, but it looks reasonable, and I trust your judgement).

Okay, I've started porting some of the core changes to CVS, more will 
follow tomorrow.

[snip]
>> What would the version number of this release be? 1.1.0 (beta) or
>> 1.0.17 (beta)?
>
>It depends on how significant we feel the changes over 1.0.16 are.
>If we also add the iems mentioned above, 1.1.0 looks a good version 
>number.

Yeah, I'll also investigate making the directory-browsing feature of 
the WebdavServlet more flexible: letting the user define a directory-
browsing-template URL that should point to a JSP that handles the 
(mostly) HTML stuff. then, there'd be 3 versions of the JSP: one using 
just standard Java against the Slide/WebDAV API (essentially moving 
the HTML display code out of WebdavServlet.java), the two others using 
the Struts and JSTL taglib, respectively.

That change would go into HEAD as well as SLIDE_1_0, since I 
personally think it's a feature a lot of people might want from Slide.

>> [And btw, why's Slide the only Jakarta-project using
>> that versioning scheme? ;o)]
>
>It's Apache 2 versioning number. I liked it, proposed it a while ago, 
>and it was accepted. Quite frankly I expected it to become used by 
>other projects at Apache, but it didn't happen.

I don't remember if I was already involved at that time, but I find 
the numbering scheme a bit confusing, to be honest :P. Especially in 
being unclear about alpha/beta/stable status.

-chris
________________________________________________________________
cmlenz at gmx.de




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Bugfix release ? (WAS: Re: adding users to namespace)

Posted by Remy Maucherat <re...@apache.org>.
> Okay, I personally don't like the situation that the 1.0 branch is
> kind of abandoned currently, especially when considering that HEAD
> represents a new major version with API changes and all that.
>
> So, I've spent some time today to go through the commit messages of
> the past 3 months and browsing through cvsview. I've come up with a
> list of changes that I personally consider "portable" to 1.0, i.e. not
> necessarily bug-fixes in the strict sense, but also clean-up and tiny
> feature-additions. I've attached a list of the commit messages
> (without the diffs), annotated with comments about what I think should
> be done. I have applied most of the changes in that list to my local
> working copy of the 1.0 branch, and couldn't find any serious
> problems, but more testing will follow.

Great initiative. Extremely useful work :)
+1 for the proposed changes (I didn't go through the list item by item, but
it looks reasonable, and I trust your judgement).

> Now, if all could just check the list and shout out loud if they feel
> something shouldn't be there or something else is missing.
>
> In addition, we should consider adding the following new features to
> the 1.0 branch as well:
>  - J2EE-Stores (is it ready yet?)

It's probably ready for a beta, but unfortunately this store won't work in
the 1.x embedded server (it relies exclusively on JNDI to retrieve the
DataSource, and that is not supported in TC 4.0.x).
I would port it anyway, as it is very useful to improve scalability.

The J2EE content store doesn't have the latest code at the moment (or we
need to merge the two stores).

>  - XMLFileDescriptorsStore

I didn't test it at all, so I have no opinion on this.

>  - WebdavFile and the JFileChooser

It wouldn't hurt.

>  - others?
>
> What would the version number of this release be? 1.1.0 (beta) or
> 1.0.17 (beta)?

It depends on how significant we feel the changes over 1.0.16 are.
If we also add the iems mentioned above, 1.1.0 looks a good version number.

> [And btw, why's Slide the only Jakarta-project using
> that versioning scheme? ;o)]

It's Apache 2 versioning number. I liked it, proposed it a while ago, and it
was accepted. Quite frankly I expected it to become used by other projects
at Apache, but it didn't happen.

Remy


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Bugfix release ? (WAS: Re: adding users to namespace)

Posted by Christopher Lenz <cm...@gmx.de>.
Okay, I personally don't like the situation that the 1.0 branch is 
kind of abandoned currently, especially when considering that HEAD 
represents a new major version with API changes and all that.

So, I've spent some time today to go through the commit messages of 
the past 3 months and browsing through cvsview. I've come up with a 
list of changes that I personally consider "portable" to 1.0, i.e. not 
necessarily bug-fixes in the strict sense, but also clean-up and tiny 
feature-additions. I've attached a list of the commit messages 
(without the diffs), annotated with comments about what I think should 
be done. I have applied most of the changes in that list to my local 
working copy of the 1.0 branch, and couldn't find any serious 
problems, but more testing will follow.

Now, if all could just check the list and shout out loud if they feel 
something shouldn't be there or something else is missing.

In addition, we should consider adding the following new features to 
the 1.0 branch as well:
 - J2EE-Stores (is it ready yet?)
 - XMLFileDescriptorsStore
 - WebdavFile and the JFileChooser
 - others?

What would the version number of this release be? 1.1.0 (beta) or 
1.0.17 (beta)? [And btw, why's Slide the only Jakarta-project using 
that versioning scheme? ;o)]

12.02.2002 18:00:47, "Remy Maucherat" <re...@apache.org> wrote:
>> Which reminds me... has anyone been porting bugfixes (in the WebDAV
>Servlet for
>> example) back to the 1.0 branch so that we can release bugfix 
releases ?
>
>AFAIK, few patches have been ported. It may not be a good idea to 
port a lot
>of them for stability concerns, but I assume some of them should be.
>
>So far, I haven't seen any showstopper problem being fixed, so I 
wasn't in a
>hurry to propose releasing 1.0.17.
>
>Remy
>

-chris
________________________________________________________________
cmlenz at gmx.de

Re: Bugfix release ? (WAS: Re: adding users to namespace)

Posted by Remy Maucherat <re...@apache.org>.
> Which reminds me... has anyone been porting bugfixes (in the WebDAV
Servlet for
> example) back to the 1.0 branch so that we can release bugfix releases ?

AFAIK, few patches have been ported. It may not be a good idea to port a lot
of them for stability concerns, but I assume some of them should be.

So far, I haven't seen any showstopper problem being fixed, so I wasn't in a
hurry to propose releasing 1.0.17.

Remy


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>