2.4.48 is available

Hi again!

No stable yet, but I just wanted you to know that if you're
running  
2.4.x on a public wiki, you might want to upgrade...
There's a bug in  
2.4.40 which allows you to gain privileges by faking a
cookie.

In other words... I want to release a stable.  Does anyone
know of  
any showstoppers which should delay release?  This is the
time to go  
through your pet bugs, submit fixes or beg anyone else to
fix them...

/Janne

2006-09-05  Janne Jalkanen <jalkanenecyrd.com>

         * 2.4.48

         * Bug fix: it was possible to gain user privileges
simply
         by faking the cookie.  This is a serious problem
and all
         people running 2.4.x are suggested to upgrade. 
Thanks
         to Andrew for the fix.

         * SecurityVerifier no longer gets confused, if you
state
         a property using "==" instead of
"=".

2006-09-05  Christoph Sauer <sauerhs-heilbronn.de>

         * 2.4.47

         * Added title and accesskey attribute to
           LinkTag, EditLinkTag and PageInfoTag. You can now
set
           accesskeys to edit pages in the PageActions.jsp
           Use the title attribute to add a tooltip text to
indicate
           the speedkey you used.

_______________________________________________
Jspwiki-users mailing list
Jspwiki-usersecyrd.com
http://ecyrd.com/cgi-bin/mailman/listinfo/jspwiki-users

Hi there,

>  Does anyone know of  
> any showstoppers which should delay release?

I don't know if anybody shares it, but my personal opinion
is
that a bug-free page rename function would be important to
call it a “stable release”, because I think that all new
features
of a new “major” release should work properly when you
call
it “stable”.

I still got problems with the Reference Manager on page
renaming.
ReferringPagesPlugin shows both the old and the new name of
a renamed page, but the old name does not exist anymore.
And updating the referrers does not work with links on
attachments
or sections and shows strange behaviour as I described on
htt
p://jspwiki.org/wiki/BugStrangeRenameBehaviour .

I am sorry that I can't provide any patch, I've tried my
best to find
the bugs but I honestly have no idea what causes the
problem.


-- 
Candid Dauth
Rotbachstr. 9
88433 Schemmerhofen
Germany

http://cdauth.de/
mailto:cdauthcdauth.de

-- 
Candid Dauth
Rotbachstr. 9
88433 Schemmerhofen
Germany

http://cdauth.de/
mailto:mailinglistscdauth.de
_______________________________________________
Jspwiki-users mailing list
Jspwiki-usersecyrd.com
http://ecyrd.com/cgi-bin/mailman/listinfo/jspwiki-users

> I am sorry that I can't provide any patch, I've tried
my best to find
> the bugs but I honestly have no idea what causes the
problem.

I added a bunch of unit tests to the CVS, so if anyone could
go and  
check them out, and figure out problems (hint: put a
breakpoint at  
the beginning of the test, then use Eclipse's "Debug
as Junit  
test" , that
would be a great help.  It seems that there is  
something rather big in both Renamer *and*
ReferenceManager...

/Janne
_______________________________________________
Jspwiki-users mailing list
Jspwiki-usersecyrd.com
http://ecyrd.com/cgi-bin/mailman/listinfo/jspwiki-users

On Wed, Sep 06, 2006 at 10:07:55AM +0300, Janne Jalkanen
wrote:
> >I am sorry that I can't provide any patch, I've
tried my best to find
> >the bugs but I honestly have no idea what causes
the problem.
> 
> I added a bunch of unit tests to the CVS, so if anyone
could go and  
> check them out, and figure out problems (hint: put a
breakpoint at  
> the beginning of the test, then use Eclipse's
"Debug as Junit  
> test" , that
would be a great help.  It seems that there is  
> something rather big in both Renamer *and*
ReferenceManager...

Treid to do the debuging bit. I have started eclipse and
start a new
workspace, and then started a new CVS project, got the
lastest HEAD.

I found the tests directory and went to AllTests.java in
com.ecryd.jspwiki, placed a break point and then tried to do
the debug
as junit test, after setting a break point on static Test
Suite and it
failled 
junit.framework.AssertionFailedError: No property file
found!




> 
> /Janne
> _______________________________________________
> Jspwiki-users mailing list
> Jspwiki-usersecyrd.com
> http://ecyrd.com/cgi-bin/mailman/listinfo/jspwiki-users
> 
_______________________________________________
Jspwiki-users mailing list
Jspwiki-usersecyrd.com
http://ecyrd.com/cgi-bin/mailman/listinfo/jspwiki-users

> junit.framework.AssertionFailedError: No property file
found!

You need to build the test environment once first.  Go to
eclipse/JSPWiki (or wherever you have installed it), and
from the
command line, run "ant tests-init".  Or
"ant tests" or "ant guitests",
if you want to see the tests run.

After that tests should run from Eclipse, too.

(Sorry for not documenting this anywhere.  Bad, bad me.)

/Janne
_______________________________________________
Jspwiki-users mailing list
Jspwiki-usersecyrd.com
http://ecyrd.com/cgi-bin/mailman/listinfo/jspwiki-users

On Wed, Sep 06, 2006 at 10:07:55AM +0300, Janne Jalkanen
wrote:
> >I am sorry that I can't provide any patch, I've
tried my best to find
> >the bugs but I honestly have no idea what causes
the problem.
> 
> I added a bunch of unit tests to the CVS, so if anyone
could go and  
> check them out, and figure out problems (hint: put a
breakpoint at  
> the beginning of the test, then use Eclipse's
"Debug as Junit  
> test" , that
would be a great help.  It seems that there is  
> something rather big in both Renamer *and*
ReferenceManager...

Treid to do the debuging bit. I have started eclipse and
start a new
workspace, and then started a new CVS project, got the
lastest HEAD.

I found the tests directory and went to AllTests.java in
com.ecryd.jspwiki, placed a break point and then tried to do
the debug
as junit test, after setting a break point on static Test
Suite and it
failled 
junit.framework.AssertionFailedError: No property file
found!




> 
> /Janne
> _______________________________________________
> Jspwiki-users mailing list
> Jspwiki-usersecyrd.com
> http://ecyrd.com/cgi-bin/mailman/listinfo/jspwiki-users
> 
_______________________________________________
Jspwiki-users mailing list
Jspwiki-usersecyrd.com
http://ecyrd.com/cgi-bin/mailman/listinfo/jspwiki-users

> junit.framework.AssertionFailedError: No property file
found!

You need to build the test environment once first.  Go to
eclipse/JSPWiki (or wherever you have installed it), and
from the
command line, run "ant tests-init".  Or
"ant tests" or "ant guitests",
if you want to see the tests run.

After that tests should run from Eclipse, too.

(Sorry for not documenting this anywhere.  Bad, bad me.)

/Janne
_______________________________________________
Jspwiki-users mailing list
Jspwiki-usersecyrd.com
http://ecyrd.com/cgi-bin/mailman/listinfo/jspwiki-users