burtonator wrote:
>
> [EMAIL PROTECTED] wrote:
> >
> > I was fixing a couple of bugs in Jetspeed this weekend when I found this in the
> > TODO list:
> >
> > - Make sure that Admin portlets can't be instantiated from not within the
> > Admin screen.
> >
> > Kevin, do you *really* consider this to be a high priority release stopper ?
> > I don't see this having a lot of impact and any simple fix we may make will be
> > a hack.
> > I'd much rather wait for a correct implementation of security features in the
> > portlet registry and relegate this bug to normal priority.
>
> No. I think this is a big issue. Just do a:
>
> /servlet/jetspeed/portlet/JavaRuntimePortlet and you will get the users
> JVM info :(
>
Not with this URL but it's indeed feasible. Still, Jetspeed is currently
unsuitable for production environments, so we just have to warn users about the
danger.
I strongly vote for relasing a 1.2b1 release now, without trying to correct
further bugs. Why ?
- the CVS tree has already be closed for feature work for 2 weeks, we need
either to branch the tree to start working on 1.2 features or tag the current
state, release and go on with it.
- the XML.com article details features of the CVS version which are NOT available
in the current jetspeed dist. This will throw off a lot of new people when they
try it
- Jetspeed 1.1 is buggy and not actively supported by us anymore. I don't even
precisely remember how to setup it up...
So, I'm +1 for releasing 1.2b1 during the week-end, with all the outstanding bugs.
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
