JSPWiki Future and Roadmap post v2.8.2

[supernovachild]

Hi Guys

I'm an avid fan of JSPWiki, but I'm concerned about it's future with it being part of the Apache incubator project

The reasons are:

- Edits on jspwiki seem to be slowing down
- No-one has been contributing Templates. When I started using JSPWiki at ver 2.0.x there where a whole bunch and then it slowed down. By ver 2.6 no-one was contributing any more
- The same applies to the plugins
- The http://incubator.apache.org/jspwiki/ site seems very lean and nothing much seems to be going on
- The JIRA site seems to have items logged in 2008 with no resolution

Having said all of this; the number & frequency of subversion commits seems to be fairly ok which might indicate that their is perhaps nothing to fear? :)

I know the more people helping on a project the better. Unfortunately I can only be an avid user and fan and not contribute due my hectic work and 60+ hours weeks.

If we the fans have nothing to fear, may I be so bold as to ask the team to stick something on the main page of jspwiki.org as well as the incubator page explaining that there is nothing to fear and that the project is alive and kicking. Also (I'm not sure if this is somewhere), do you have any idea of the release roadmap concerning rough dates... i.e. from 2.8.3 to 3.0 to 3.1?


Thanks Guys

A major fan

Greg

[Janne Jalkanen]

Heya!

I don't think moving to Apache Incubation had anything to do with it,  
really - I believe it's just the fact that all of the developers are  
busy elsewhere with new jobs or children.  Or both, in my case.

You're right that we haven't kept the web sites up to date.  When  
you're under time constraints, SVN and code takes precedence :-).  If  
there's a volunteer who would like to help in maintaining the web site  
and the wiki, it would be a great help.  No coding expertise required;  
just someone who wants to write about JSPWiki.  But yeah, we should  
really stick something on the websites.

As to why there haven't been that many plugins or templates... I don't  
know.  Perhaps there just aren't that many users anymore for  
standalone wikis :-/.

I wouldn't use the JIRA as a guideline for project activity; if you  
take a look at Firefox Bugzilla, they'll have major things open from  
2004 or so in it...

/Janne

On 30 Jul 2009, at 12:54, supernovachild wrote:

>
> Hi Guys
>
> I'm an avid fan of JSPWiki, but I'm concerned about it's future with  
> it
> being part of the Apache incubator project
>
> The reasons are:
>
> - Edits on jspwiki seem to be slowing down
> - No-one has been contributing Templates. When I started using  
> JSPWiki at
> ver 2.0.x there where a whole bunch and then it slowed down. By ver  
> 2.6
> no-one was contributing any more
> - The same applies to the plugins
> - The http://incubator.apache.org/jspwiki/ site seems very lean and  
> nothing
> much seems to be going on
> - The JIRA site seems to have items logged in 2008 with no resolution
>
> Having said all of this; the number & frequency of subversion  
> commits seems
> to be fairly ok which might indicate that their is perhaps nothing  
> to fear?
> :)
>
> I know the more people helping on a project the better.  
> Unfortunately I can
> only be an avid user and fan and not contribute due my hectic work  
> and 60+
> hours weeks.
>
> If we the fans have nothing to fear, may I be so bold as to ask the  
> team to
> stick something on the main page of jspwiki.org as well as the  
> incubator
> page explaining that there is nothing to fear and that the project  
> is alive
> and kicking. Also (I'm not sure if this is somewhere), do you have  
> any idea
> of the release roadmap concerning rough dates... i.e. from 2.8.3 to  
> 3.0 to
> 3.1?
>
>
> Thanks Guys
>
> A major fan
>
> Greg
>
>
> --
> View this message in context: http://www.nabble.com/JSPWiki-Future-and-Roadmap-post-v2.8.2-tp24735443p24735443.html
> Sent from the JspWiki - User mailing list archive at Nabble.com.

[ChristopheDD]

Dear Janne,

"Perhaps there just aren't that many users anymore for standalone wikis"
What do you mean by this? Within what JSPWiki should be integrated to be "interesting" for users?

In my case, it is "page indexation" (what one may call a "semantic wiki") and I will work on that on the basis of 3.0 (a permanent id being then assigned to pages, indexation will be easier to track).
But I suppose it is not the mainstream concern?

Thanks for your enlightments!

Christophe Dupriez
Centre Antipoisons-Antigifcentrum
C/o Hôpital Central de la Base Reine Astrid
Rue Bruyn
1120 Bruxelles
Belgique
tel [phone]
fax [phone]



----- Original Message -----
From: Janne Jalkanen [mailto:janne.jalkanen@...]
To: jspwiki-user@...
Subject: Re: JSPWiki Future and Roadmap post v2.8.2

>
> Heya!
>
> I don't think moving to Apache Incubation had anything to do with it,  
> really - I believe it's just the fact that all of the developers are  
> busy elsewhere with new jobs or children.  Or both, in my case.
>
> You're right that we haven't kept the web sites up to date.  When  
> you're under time constraints, SVN and code takes precedence :-).  If  
> there's a volunteer who would like to help in maintaining the web site  
> and the wiki, it would be a great help.  No coding expertise required;  
> just someone who wants to write about JSPWiki.  But yeah, we should  
> really stick something on the websites.
>
> As to why there haven't been that many plugins or templates... I don't  
> know.  Perhaps there just aren't that many users anymore for  
> standalone wikis :-/.
>
> I wouldn't use the JIRA as a guideline for project activity; if you  
> take a look at Firefox Bugzilla, they'll have major things open from  
> 2004 or so in it...
>
> /Janne
>
> On 30 Jul 2009, at 12:54, supernovachild wrote:
>
> >
> > Hi Guys
> >
> > I'm an avid fan of JSPWiki, but I'm concerned about it's future with  
> > it
> > being part of the Apache incubator project
> >
> > The reasons are:
> >
> > - Edits on jspwiki seem to be slowing down
> > - No-one has been contributing Templates. When I started using  
> > JSPWiki at
> > ver 2.0.x there where a whole bunch and then it slowed down. By ver  
> > 2.6
> > no-one was contributing any more
> > - The same applies to the plugins
> > - The http://incubator.apache.org/jspwiki/ site seems very lean and  
> > nothing
> > much seems to be going on
> > - The JIRA site seems to have items logged in 2008 with no resolution
> >
> > Having said all of this; the number & frequency of subversion  
> > commits seems
> > to be fairly ok which might indicate that their is perhaps nothing  
> > to fear?
> > :)
> >
> > I know the more people helping on a project the better.  
> > Unfortunately I can
> > only be an avid user and fan and not contribute due my hectic work  
> > and 60+
> > hours weeks.
> >
> > If we the fans have nothing to fear, may I be so bold as to ask the  
> > team to
> > stick something on the main page of jspwiki.org as well as the  
> > incubator
> > page explaining that there is nothing to fear and that the project  
> > is alive
> > and kicking. Also (I'm not sure if this is somewhere), do you have  
> > any idea
> > of the release roadmap concerning rough dates... i.e. from 2.8.3 to  
> > 3.0 to
> > 3.1?
> >
> >
> > Thanks Guys
> >
> > A major fan
> >
> > Greg
> >
> >
> > --
> > View this message in context:
> http://www.nabble.com/JSPWiki-Future-and-Roadmap-post-v2.8.2-tp24735443p24735443.html
> > Sent from the JspWiki - User mailing list archive at Nabble.com.
>
>

[Janne Jalkanen]

I meant that Google Docs, pmwiki and other WikiFarms have probably  
taken a big market share.  JSPWiki seems to be mainly used in  
companies, and few companies share the plugins/templates they create...

/Janne

On 30 Jul 2009, at 16:29, Christophe Dupriez wrote:

> Dear Janne,
>
> "Perhaps there just aren't that many users anymore for standalone  
> wikis"
> What do you mean by this? Within what JSPWiki should be integrated  
> to be "interesting" for users?
>
> In my case, it is "page indexation" (what one may call a "semantic  
> wiki") and I will work on that on the basis of 3.0 (a permanent id  
> being then assigned to pages, indexation will be easier to track).
> But I suppose it is not the mainstream concern?
>
> Thanks for your enlightments!
>
> Christophe Dupriez
> Centre Antipoisons-Antigifcentrum
> C/o Hôpital Central de la Base Reine Astrid
> Rue Bruyn
> 1120 Bruxelles
> Belgique
> tel [phone]
> fax [phone]
>
>
>
> ----- Original Message -----
> From: Janne Jalkanen [mailto:janne.jalkanen@...]
> To: jspwiki-user@...
> Subject: Re: JSPWiki Future and Roadmap post v2.8.2
>
>
>>
>> Heya!
>>
>> I don't think moving to Apache Incubation had anything to do with it,
>> really - I believe it's just the fact that all of the developers are
>> busy elsewhere with new jobs or children.  Or both, in my case.
>>
>> You're right that we haven't kept the web sites up to date.  When
>> you're under time constraints, SVN and code takes precedence :-).  If
>> there's a volunteer who would like to help in maintaining the web  
>> site
>> and the wiki, it would be a great help.  No coding expertise  
>> required;
>> just someone who wants to write about JSPWiki.  But yeah, we should
>> really stick something on the websites.
>>
>> As to why there haven't been that many plugins or templates... I  
>> don't
>> know.  Perhaps there just aren't that many users anymore for
>> standalone wikis :-/.
>>
>> I wouldn't use the JIRA as a guideline for project activity; if you
>> take a look at Firefox Bugzilla, they'll have major things open from
>> 2004 or so in it...
>>
>> /Janne
>>
>> On 30 Jul 2009, at 12:54, supernovachild wrote:
>>
>>>
>>> Hi Guys
>>>
>>> I'm an avid fan of JSPWiki, but I'm concerned about it's future with
>>> it
>>> being part of the Apache incubator project
>>>
>>> The reasons are:
>>>
>>> - Edits on jspwiki seem to be slowing down
>>> - No-one has been contributing Templates. When I started using
>>> JSPWiki at
>>> ver 2.0.x there where a whole bunch and then it slowed down. By ver
>>> 2.6
>>> no-one was contributing any more
>>> - The same applies to the plugins
>>> - The http://incubator.apache.org/jspwiki/ site seems very lean and
>>> nothing
>>> much seems to be going on
>>> - The JIRA site seems to have items logged in 2008 with no  
>>> resolution
>>>
>>> Having said all of this; the number & frequency of subversion
>>> commits seems
>>> to be fairly ok which might indicate that their is perhaps nothing
>>> to fear?
>>> :)
>>>
>>> I know the more people helping on a project the better.
>>> Unfortunately I can
>>> only be an avid user and fan and not contribute due my hectic work
>>> and 60+
>>> hours weeks.
>>>
>>> If we the fans have nothing to fear, may I be so bold as to ask the
>>> team to
>>> stick something on the main page of jspwiki.org as well as the
>>> incubator
>>> page explaining that there is nothing to fear and that the project
>>> is alive
>>> and kicking. Also (I'm not sure if this is somewhere), do you have
>>> any idea
>>> of the release roadmap concerning rough dates... i.e. from 2.8.3 to
>>> 3.0 to
>>> 3.1?
>>>
>>>
>>> Thanks Guys
>>>
>>> A major fan
>>>
>>> Greg
>>>
>>>
>>> --
>>> View this message in context:
>> http://www.nabble.com/JSPWiki-Future-and-Roadmap-post-v2.8.2-tp24735443p24735443.html
>>> Sent from the JspWiki - User mailing list archive at Nabble.com.
>>
>>

[gila]

To give a bit more optimistic view :-)  .. the baseline is fairly usable!

I'm using JSPwiki embedded (lightly - mostly through xml-rpc) for a
couple of law firms; so far only need I had was localisation for Italian
(which was contributed back). I'm using a three columns template derived
from base one - only reason I did not (yet) share was that the third col
is used for external stuff; I would gladly contribute is as an empty
template if needed - was only waiting 3.0 as I believe I will have to
change a number of things and cannot manage day to day alignment with
the ongoing 3.0 work (sorry).
Keep on with this nice stuff!
Luca

PS: in our case part of the extensions also are to get pages indexed and
related to other stuff ... bits of semantic ... :-)

Janne Jalkanen wrote:

>
> I meant that Google Docs, pmwiki and other WikiFarms have probably
> taken a big market share.  JSPWiki seems to be mainly used in
> companies, and few companies share the plugins/templates they create...
>
> /Janne
>
> On 30 Jul 2009, at 16:29, Christophe Dupriez wrote:
>
>> Dear Janne,
>>
>> "Perhaps there just aren't that many users anymore for standalone wikis"
>> What do you mean by this? Within what JSPWiki should be integrated to
>> be "interesting" for users?
>>
>> In my case, it is "page indexation" (what one may call a "semantic
>> wiki") and I will work on that on the basis of 3.0 (a permanent id
>> being then assigned to pages, indexation will be easier to track).
>> But I suppose it is not the mainstream concern?
>>
>> Thanks for your enlightments!
>>
>> Christophe Dupriez
>> Centre Antipoisons-Antigifcentrum
>> C/o Hôpital Central de la Base Reine Astrid
>> Rue Bruyn
>> 1120 Bruxelles
>> Belgique
>> tel [phone]
>> fax [phone]
>>

[Foster Schucker]

JSPWiki is one of those things that once it's installed, people use it
and don't look back.

For example my personal wiki is version 2.0.56 (with custom security
patches developed back then) and it's done everything I want.

I've installed versions since then at a number of customer sites.  All
of the CSS work to make it look like they wanted was done as contract /
work for hire, and didn't come back to the base release (which is within
the license terms).  Most don't use custom plug ins, the base set gives
them the collab tools that they want and need.

There are other wiki's out there that get good use.  About eight weeks
ago I installed MediaWiki at a site, the lead admin is a PHP guru, he
wanted something he could understand.  Since then, they've updated the
css to make it what they want look and feel, but they have not written a
single line of PHP to change the code base.

Most places take the base tool, add the dancing sauages they want on the
graphics and are good to go.  The largest site as 12,000 pages on a 2.6
release and they are happy as clams.

I'll grant that the hardest part is the documentation for users.

Foster

[Kris Glover]

I am also a big fan of JSPWiki. I have used it on several projects and am
currently modifying pieces of it so that it can run within a portlet and
also connect to a JCR. As someone else mentioned my work schedule is crazy
but I would love to give back something.

I would really be interested in building some plugin's or helping out on
3.0+  I just don't know where to start or what is useful for the community
since the code base is pretty extensive. If anyone has some direction I
would be more then happy to spend some time contributing back immediately.
If not it will probably take me a few weeks to get to know the different
branches/tags and then figure out what I could do that is useful for the
community.

Thanks
Kris

On Thu, Jul 30, 2009 at 11:19 AM, lgilardoni61@... <
lgilardoni61@...> wrote:

> To give a bit more optimistic view :-)  .. the baseline is fairly usable!
>
> I'm using JSPwiki embedded (lightly - mostly through xml-rpc) for a couple
> of law firms; so far only need I had was localisation for Italian (which was
> contributed back). I'm using a three columns template derived from base one
> - only reason I did not (yet) share was that the third col is used for
> external stuff; I would gladly contribute is as an empty template if needed
> - was only waiting 3.0 as I believe I will have to change a number of things
> and cannot manage day to day alignment with the ongoing 3.0 work (sorry).
> Keep on with this nice stuff!
> Luca
>
> PS: in our case part of the extensions also are to get pages indexed and
> related to other stuff ... bits of semantic ... :-)
>
>
> Janne Jalkanen wrote:
>
>>
>> I meant that Google Docs, pmwiki and other WikiFarms have probably taken a
>> big market share.  JSPWiki seems to be mainly used in companies, and few
>> companies share the plugins/templates they create...
>>
>> /Janne
>>
>> On 30 Jul 2009, at 16:29, Christophe Dupriez wrote:
>>
>>  Dear Janne,
>>>
>>> "Perhaps there just aren't that many users anymore for standalone wikis"
>>> What do you mean by this? Within what JSPWiki should be integrated to be
>>> "interesting" for users?
>>>
>>> In my case, it is "page indexation" (what one may call a "semantic wiki")
>>> and I will work on that on the basis of 3.0 (a permanent id being then
>>> assigned to pages, indexation will be easier to track).
>>> But I suppose it is not the mainstream concern?
>>>
>>> Thanks for your enlightments!
>>>
>>> Christophe Dupriez
>>> Centre Antipoisons-Antigifcentrum
>>> C/o Hôpital Central de la Base Reine Astrid
>>> Rue Bruyn
>>> 1120 Bruxelles
>>> Belgique
>>> tel [phone]
>>> fax [phone]
>>>
>>>
>

[Harry Metske]

2009/7/30 supernovachild <supernovachild@...>

>
> Hi Guys
>
> I'm an avid fan of JSPWiki, but I'm concerned about it's future with it
> being part of the Apache incubator project
>
> The reasons are:
>
> - Edits on jspwiki seem to be slowing down


the last couple of months have been rather quiet, this is mainly due to the
fact that some of the main contributors have had other priorities (family
expansion, marriage, vacation and so on). Also, I think summertime with nice
weather is a cause.


> - No-one has been contributing Templates. When I started using JSPWiki at
> ver 2.0.x there where a whole bunch and then it slowed down. By ver 2.6
> no-one was contributing any more


see other comments...., I'm only involved since about 2 years...


> - The same applies to the plugins


I think we are fairly complete for basic functions, if there are
requirements for other plugin functionality people can enter JIRA issues.
Contribution of plugins is indeed low the last year, I can't explain why.


> - The http://incubator.apache.org/jspwiki/ site seems very lean and
> nothing
> much seems to be going on


as Janne already pointed out, this is due to the incubating process and our
documentation issue, we made this site very basic, pointing over to the
current wiki's (which are much easier to maintain).


> - The JIRA site seems to have items logged in 2008 with no resolution


yep, we surely could use more good developers picking up bugs and feature
requests....
the most coding time is currently spent (I guess) in getting 3.0 up to the
basic functioning (Stripes + JCR) and the promotion to an ASF top level
project, leaving not much time left for JIRA issues.

>
> Having said all of this; the number & frequency of subversion commits seems
> to be fairly ok which might indicate that their is perhaps nothing to fear?
> :)
>
> I know the more people helping on a project the better. Unfortunately I can
> only be an avid user and fan and not contribute due my hectic work and 60+
> hours weeks.
>
> If we the fans have nothing to fear, may I be so bold as to ask the team to
> stick something on the main page of jspwiki.org as well as the incubator
> page explaining that there is nothing to fear and that the project is alive
> and kicking. Also (I'm not sure if this is somewhere), do you have any idea
> of the release roadmap concerning rough dates... i.e. from 2.8.3 to 3.0 to
> 3.1?
>
>
> Thanks Guys
>
> A major fan
>
> Greg
>

regards,
Harry


>
> --
> View this message in context:
> http://www.nabble.com/JSPWiki-Future-and-Roadmap-post-v2.8.2-tp24735443p24735443.html
> Sent from the JspWiki - User mailing list archive at Nabble.com.
>
>

[Andrew Jaquith-4]

Foster has a good point. Many people are happy with the old versions.
My own website runs 2.4. I haven't upgraded, in part, because I am
worried that my custom CSS won't work. Certainly can be done, but it
is more fun to write code. :)

3.0 will be more enterprise-friendly. The back-end will be
JCR-compatible, making it possible to integrate with content
management systems like Documentum and Interwoven. I'm also
(personally) working on some officially supported authentication and
user database modules for LDAP -- OpenLDAP and Active Directory in
particular. AD integration right now is too hard, and it's too
important to be left out of the core distribution.

Andrew


On Jul 30, 2009, at 11:46, Foster Schucker <Foster@...> wrote:

> JSPWiki is one of those things that once it's installed, people use
> it and don't look back.
> For example my personal wiki is version 2.0.56 (with custom security
> patches developed back then) and it's done everything I want.
>
> I've installed versions since then at a number of customer sites.
> All of the CSS work to make it look like they wanted was done as
> contract / work for hire, and didn't come back to the base release
> (which is within the license terms).  Most don't use custom plug
> ins, the base set gives them the collab tools that they want and need.
>
> There are other wiki's out there that get good use.  About eight
> weeks ago I installed MediaWiki at a site, the lead admin is a PHP
> guru, he wanted something he could understand.  Since then, they've
> updated the css to make it what they want look and feel, but they
> have not written a single line of PHP to change the code base.
>
> Most places take the base tool, add the dancing sauages they want on
> the graphics and are good to go.  The largest site as 12,000 pages
> on a 2.6 release and they are happy as clams.
>
> I'll grant that the hardest part is the documentation for users.
>
> Foster
>
>

[Juergen Weber]

Janne Jalkanen wrote:

I meant that Google Docs, pmwiki and other WikiFarms have probably  
taken a big market share.  JSPWiki seems to be mainly used in  
companies, and few companies share the plugins/templates they create...

Under that view you could scrap almost all products of Apache. Tomcat, Geronimo and friends are all for companies or institutions. Still, there are lots of downloads of the products (btw, do you count JSPWiki downloads?).

Our company is a happy JSPWiki user, too. Currently we have 1200 pages and growing ...

Thanks to the community for the great Wiki product !!

I think http://www.jspwiki.org/wiki/JSPWikiSites  should be made prettier and prominently linked  on JSPWiki.org, it could look like the Glassfish success stories: http://blogs.sun.com/stories/


Thanks,
Juergen

[Janne Jalkanen]

>>
>> I meant that Google Docs, pmwiki and other WikiFarms have probably
>> taken a big market share.  JSPWiki seems to be mainly used in
>> companies, and few companies share the plugins/templates they  
>> create...
>>
>
> Under that view you could scrap almost all products of Apache. Tomcat,
> Geronimo and friends are all for companies or institutions. Still,  
> there are
> lots of downloads of the products (btw, do you count JSPWiki  
> downloads?).

Erm, I didn't mean that it renders JSPWiki (or any other product)  
useless.  It's just that individual users are far more likely to  
contribute their patches to JSPWiki rather than companies :-)

> Thanks to the community for the great Wiki product !!

Thanks for using JSPWiki :)

> I think http://www.jspwiki.org/wiki/JSPWikiSites  should be made  
> prettier
> and prominently linked  on JSPWiki.org, it could look like the  
> Glassfish
> success stories: http://blogs.sun.com/stories/

I agree. Want to take the job? ;-)

/Janne

[Rolf Schumacher]

Its a very good idea to publish an honest road map, even if it will be
changed every other week. Hope is fun.

Short, simple to understand and attractive to end-users.

Rolf


Urspru"ngliche Nachricht vom 27.05.2008 um 21:04:
> Using the Wiki in trac is a bit intricated compared to JSPWiki. However,
> combining Wiki with issue mgmt, version control and roadmaps of
> milestones in an easy manner seems worth trying.

> Any plans to broaden the functionality scope in a similar direction?

Rolf

Janne Jalkanen wrote:

>
> Heya!
>
> I don't think moving to Apache Incubation had anything to do with it,
> really - I believe it's just the fact that all of the developers are
> busy elsewhere with new jobs or children. Or both, in my case.
>
> You're right that we haven't kept the web sites up to date. When
> you're under time constraints, SVN and code takes precedence :-). If
> there's a volunteer who would like to help in maintaining the web site
> and the wiki, it would be a great help. No coding expertise required;
> just someone who wants to write about JSPWiki. But yeah, we should
> really stick something on the websites.
>
> As to why there haven't been that many plugins or templates... I don't
> know. Perhaps there just aren't that many users anymore for standalone
> wikis :-/.
>
> I wouldn't use the JIRA as a guideline for project activity; if you
> take a look at Firefox Bugzilla, they'll have major things open from
> 2004 or so in it...
>
> /Janne
>
> On 30 Jul 2009, at 12:54, supernovachild wrote:
>
>>
>> Hi Guys
>>
>> I'm an avid fan of JSPWiki, but I'm concerned about it's future with it
>> being part of the Apache incubator project
>>
>> The reasons are:
>>
>> - Edits on jspwiki seem to be slowing down
>> - No-one has been contributing Templates. When I started using
>> JSPWiki at
>> ver 2.0.x there where a whole bunch and then it slowed down. By ver 2.6
>> no-one was contributing any more
>> - The same applies to the plugins
>> - The http://incubator.apache.org/jspwiki/ site seems very lean and
>> nothing
>> much seems to be going on
>> - The JIRA site seems to have items logged in 2008 with no resolution
>>
>> Having said all of this; the number & frequency of subversion commits
>> seems
>> to be fairly ok which might indicate that their is perhaps nothing to
>> fear?
>> :)
>>
>> I know the more people helping on a project the better. Unfortunately
>> I can
>> only be an avid user and fan and not contribute due my hectic work
>> and 60+
>> hours weeks.
>>
>> If we the fans have nothing to fear, may I be so bold as to ask the
>> team to
>> stick something on the main page of jspwiki.org as well as the incubator
>> page explaining that there is nothing to fear and that the project is
>> alive
>> and kicking. Also (I'm not sure if this is somewhere), do you have
>> any idea
>> of the release roadmap concerning rough dates... i.e. from 2.8.3 to
>> 3.0 to
>> 3.1?
>>
>>
>> Thanks Guys
>>
>> A major fan
>>
>> Greg
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JSPWiki-Future-and-Roadmap-post-v2.8.2-tp24735443p24735443.html
>>
>> Sent from the JspWiki - User mailing list archive at Nabble.com.
>

[Janne Jalkanen]

So therefore I call forth the opening for the position of the Official  
Roadmap Maintainer :-)

(I don't think I have the time to update a roadmap - I rather use the  
time for coding.  But if someone is savvy enough with JIRA and  
ChangeLog, and bothers to pester the committers what their plan are  
next in a regular interval, they would make one killer roadmap  
writer...  Anybody want to take the job?  It would be easy enough to  
maintain in the wiki)

/Janne

On 22 Aug 2009, at 13:22, Rolf Schumacher wrote:

> Its a very good idea to publish an honest road map, even if it will be
> changed every other week. Hope is fun.
>
> Short, simple to understand and attractive to end-users.
>
> Rolf
>
>
> Urspru"ngliche Nachricht vom 27.05.2008 um 21:04:
>> Using the Wiki in trac is a bit intricated compared to JSPWiki.  
>> However,
>> combining Wiki with issue mgmt, version control and roadmaps of
>> milestones in an easy manner seems worth trying.
>
>> Any plans to broaden the functionality scope in a similar direction?
>
> Rolf
>
> Janne Jalkanen wrote:
>>
>> Heya!
>>
>> I don't think moving to Apache Incubation had anything to do with it,
>> really - I believe it's just the fact that all of the developers are
>> busy elsewhere with new jobs or children. Or both, in my case.
>>
>> You're right that we haven't kept the web sites up to date. When
>> you're under time constraints, SVN and code takes precedence :-). If
>> there's a volunteer who would like to help in maintaining the web  
>> site
>> and the wiki, it would be a great help. No coding expertise required;
>> just someone who wants to write about JSPWiki. But yeah, we should
>> really stick something on the websites.
>>
>> As to why there haven't been that many plugins or templates... I  
>> don't
>> know. Perhaps there just aren't that many users anymore for  
>> standalone
>> wikis :-/.
>>
>> I wouldn't use the JIRA as a guideline for project activity; if you
>> take a look at Firefox Bugzilla, they'll have major things open from
>> 2004 or so in it...
>>
>> /Janne
>>
>> On 30 Jul 2009, at 12:54, supernovachild wrote:
>>
>>>
>>> Hi Guys
>>>
>>> I'm an avid fan of JSPWiki, but I'm concerned about it's future  
>>> with it
>>> being part of the Apache incubator project
>>>
>>> The reasons are:
>>>
>>> - Edits on jspwiki seem to be slowing down
>>> - No-one has been contributing Templates. When I started using
>>> JSPWiki at
>>> ver 2.0.x there where a whole bunch and then it slowed down. By  
>>> ver 2.6
>>> no-one was contributing any more
>>> - The same applies to the plugins
>>> - The http://incubator.apache.org/jspwiki/ site seems very lean and
>>> nothing
>>> much seems to be going on
>>> - The JIRA site seems to have items logged in 2008 with no  
>>> resolution
>>>
>>> Having said all of this; the number & frequency of subversion  
>>> commits
>>> seems
>>> to be fairly ok which might indicate that their is perhaps nothing  
>>> to
>>> fear?
>>> :)
>>>
>>> I know the more people helping on a project the better.  
>>> Unfortunately
>>> I can
>>> only be an avid user and fan and not contribute due my hectic work
>>> and 60+
>>> hours weeks.
>>>
>>> If we the fans have nothing to fear, may I be so bold as to ask the
>>> team to
>>> stick something on the main page of jspwiki.org as well as the  
>>> incubator
>>> page explaining that there is nothing to fear and that the project  
>>> is
>>> alive
>>> and kicking. Also (I'm not sure if this is somewhere), do you have
>>> any idea
>>> of the release roadmap concerning rough dates... i.e. from 2.8.3 to
>>> 3.0 to
>>> 3.1?
>>>
>>>
>>> Thanks Guys
>>>
>>> A major fan
>>>
>>> Greg
>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/JSPWiki-Future-and-Roadmap-post-v2.8.2-tp24735443p24735443.html
>>>
>>> Sent from the JspWiki - User mailing list archive at Nabble.com.
>>

[Roland Whitehead]

On 30 Jul 2009, at 10:54, Greg wrote:

> - Edits on jspwiki seem to be slowing down
> - No-one has been contributing Templates. When I started using  
> JSPWiki at
> ver 2.0.x there where a whole bunch and then it slowed down. By ver  
> 2.6
> no-one was contributing any more
> - The same applies to the plugins

We have been working on a number of plugins. We've already  
significantly modified the FormMailer plugin and have uploaded the new  
version (it works, it redirects to another page and some other mods),  
have produced a new plugin that munge's plugin paramters into some  
HTML code stored in the jspwiki.properties file (it was going to be a  
plugin for various embedded videos but now we're using it for all  
sorts of stuff) that we are testing before uploading to the wiki and  
we've done quite a bit of work on making a forum pluging actually work  
correctly. All of these are intended for sharing with the community  
and there are several that we've done that will remain private (like  
the plugin + perl + other licensed code that we use for producing  
print ready PDF-X1As direct from the Wiki) unless we see some demand.

The issue isn't that there isn't work being done but more that there  
isn't the perceived demand for more work. JPSWiki just works so how  
much does it need changing?

You might be interested to know that most of this plugin work is  
fuelled not only for our own needs but for the needs of another open  
source project (to build hydrogen fuel cell cars - http://www.40fires.org 
) who are priming the pump - its a case of one open source project  
feeding another!


Roland
--
QURU, London

[Robert Forbes-2]

Some parts of this message have been removed. Learn more about Nabble's security policy.

We want to deploy JSPWiki 2.8.2 against an Oracle Application Server. 

 

We have successfully installed JSPWiki 2.8.2 on an OAS 10.1.3.1 version, but it won't go on 10.1.3.4.

 

This is the error message that we get

 

You tried to instantiate an abstract class com.ecyrd.jspwiki.PageManager

 

As we can see in a more complete stack trace attached.  I saw the two threads on the discussion board with this error and tried to resolve it in that manner, but I suspect that we are dealing with something yet slightly different ....

 

ANY thoughts on where I should start hunting ???

[Harry Metske]

this mail list does not accept attachments, could you cut/paste the
stacktrace in the mail body ?
regards,
Harry

2009/8/28 Robert FORBES <rforbes@...>

>  We want to deploy JSPWiki 2.8.2 against an Oracle Application Server.
>
>
>
> We have successfully installed JSPWiki 2.8.2 on an OAS 10.1.3.1 version,
> but it won't go on 10.1.3.4.
>
>
>
> This is the error message that we get
>
>
>
> *You tried to instantiate an abstract class com.ecyrd.jspwiki.PageManager*
>
>
>
> As we can see in a more complete stack trace attached.  I saw the two
> threads on the discussion board with this error and tried to resolve it in
> that manner, but I suspect that we are dealing with something yet slightly
> different ....
>
>
>
> ANY thoughts on where I should start hunting ???
>

[Robert Forbes-2]

Error log below....  thanks for pointing that out.


009-08-26 21:27:34,872 [OC4J Launcher] INFO com.ecyrd.jspwiki.WikiEngine  - *******************************************
2009-08-26 21:27:34,872 [OC4J Launcher] INFO com.ecyrd.jspwiki.WikiEngine  - JSPWiki 2.8.2 starting. Whee!
2009-08-26 21:27:34,872 [OC4J Launcher] INFO com.ecyrd.jspwiki.WikiEngine  - Servlet container: Oracle Containers for J2EE 10g (10.1.3.4.0)
2009-08-26 21:27:34,888 [OC4J Launcher] INFO com.ecyrd.jspwiki.WikiEngine  - JSPWiki working directory is 'c:\highline\wiki\wikitemp'
2009-08-26 21:27:35,090 [OC4J Launcher] INFO com.ecyrd.jspwiki.util.ClassUtil  - You tried to instantiate an abstract class com.ecyrd.jspwiki.PageManager
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at com.ecyrd.jspwiki.util.ClassUtil.getMappedObject(ClassUtil.java:276)
        at com.ecyrd.jspwiki.util.ClassUtil.getMappedObject(ClassUtil.java:228)
        at com.ecyrd.jspwiki.WikiEngine.initialize(WikiEngine.java:525)
        at com.ecyrd.jspwiki.WikiEngine.<init>(WikiEngine.java:399)
        at com.ecyrd.jspwiki.WikiEngine.getInstance(WikiEngine.java:340)
        at com.ecyrd.jspwiki.WikiEngine.getInstance(WikiEngine.java:286)
        at com.ecyrd.jspwiki.WikiServlet.init(WikiServlet.java:54)
        at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2379)
        at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4830)
        at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4754)
        at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4942)
        at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1144)
        at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:741)
        at com.evermind.server.ApplicationStateRunning.getHttpApplication(ApplicationStateRunning.java:431)
        at com.evermind.server.Application.getHttpApplication(Application.java:586)
        at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.createHttpApplicationFromReference(HttpSite.java:1987)
        at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.<init>(HttpSite.java:1906)
        at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:643)
        at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:290)
        at com.evermind.server.http.HttpServer.setSites(HttpServer.java:270)
        at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:177)
        at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2493)
        at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1042)
        at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:131)
        at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ExceptionInInitializerError
        at com.ecyrd.jspwiki.providers.CachingProvider.initialize(CachingProvider.java:138)
        at com.ecyrd.jspwiki.PageManager.<init>(PageManager.java:166)
        ... 29 more
Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@18cecd for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Category) (Caused by org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@18cecd for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Category))
        at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
        at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
        at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
        at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
        at com.opensymphony.oscache.base.Cache.<clinit>(Cache.java:42)
        ... 31 more
Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@18cecd for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Category)
        at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:413)
        at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
        ... 35 more
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Category
        at java.lang.Class.getDeclaredConstructors0(Native Method)
        at java.lang.Class.privateGetDeclaredConstructors(Class.java:2328)
        at java.lang.Class.getConstructor0(Class.java:2640)
        at java.lang.Class.getConstructor(Class.java:1629)
        at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:410)
        ... 36 more
2009-08-26 21:27:35,090 [OC4J Launcher] FATAL com.ecyrd.jspwiki.WikiEngine  - JSPWiki could not start, due to an unknown exception when starting.
com.ecyrd.jspwiki.WikiException: Failed to instantiate class com.ecyrd.jspwiki.PageManager
        at com.ecyrd.jspwiki.util.ClassUtil.getMappedObject(ClassUtil.java:312)
        at com.ecyrd.jspwiki.util.ClassUtil.getMappedObject(ClassUtil.java:228)
        at com.ecyrd.jspwiki.WikiEngine.initialize(WikiEngine.java:525)
        at com.ecyrd.jspwiki.WikiEngine.<init>(WikiEngine.java:399)
        at com.ecyrd.jspwiki.WikiEngine.getInstance(WikiEngine.java:340)
        at com.ecyrd.jspwiki.WikiEngine.getInstance(WikiEngine.java:286)
        at com.ecyrd.jspwiki.WikiServlet.init(WikiServlet.java:54)
        at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2379)
        at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4830)
        at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4754)
        at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4942)
        at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1144)
        at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:741)
        at com.evermind.server.ApplicationStateRunning.getHttpApplication(ApplicationStateRunning.java:431)
        at com.evermind.server.Application.getHttpApplication(Application.java:586)
        at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.createHttpApplicationFromReference(HttpSite.java:1987)
        at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.<init>(HttpSite.java:1906)
        at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:643)
        at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:290)
        at com.evermind.server.http.HttpServer.setSites(HttpServer.java:270)
        at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:177)
        at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2493)
        at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1042)
        at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:131)
        at java.lang.Thread.run(Thread.java:595)
2009-08-26 21:27:40,582 [Finalizer] INFO com.ecyrd.jspwiki.WikiServlet  - WikiServlet shutdown.
2009-08-26 21:29:09,116 [AJPRequestHandler-RMICallHandler-6] INFO com.ecyrd.jspwiki.util.UtilJ2eeCompat  - serverInfo: Oracle Containers for J2EE 10g (10.1.3.4.0)
2009-08-26 21:29:09,116 [AJPRequestHandler-RMICallHandler-6] INFO com.ecyrd.jspwiki.util.UtilJ2eeCompat  - Oracle Container for JEE detected

-----Original Message-----
From: Harry Metske [mailto:harry.metske@...]
Sent: August-28-09 9:35 AM
To: jspwiki-user@...
Subject: Re: JSPWiki 2.8.2 - Oracle Application Server

this mail list does not accept attachments, could you cut/paste the
stacktrace in the mail body ?
regards,
Harry

2009/8/28 Robert FORBES <rforbes@...>

>  We want to deploy JSPWiki 2.8.2 against an Oracle Application Server.
>
>
>
> We have successfully installed JSPWiki 2.8.2 on an OAS 10.1.3.1 version,
> but it won't go on 10.1.3.4.
>
>
>
> This is the error message that we get
>
>
>
> *You tried to instantiate an abstract class com.ecyrd.jspwiki.PageManager*
>
>
>
> As we can see in a more complete stack trace attached.  I saw the two
> threads on the discussion board with this error and tried to resolve it in
> that manner, but I suspect that we are dealing with something yet slightly
> different ....
>
>
>
> ANY thoughts on where I should start hunting ???
>

[Janne Jalkanen]

Here's the root cause:

> Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Category
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2328)
> at java.lang.Class.getConstructor0(Class.java:2640)
> at java.lang.Class.getConstructor(Class.java:1629)
> at  
> org
> .apache
> .commons
> .logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:
> 410)
> ... 36 more

Looks like you have a classpath problem with log4j.  Make sure that

a) you have one somewhere in your classpath, and
b) you don't have conflicting installations in your Oracle classpath.

I'm also somewhat worried at who is calling apache commons logging -  
jspwiki does not use it at all...

/Janne