Re: current situtation JSPWiki VM

[Harry Metske]

strange indeed. also logged in users cannot save their preferences.

for the encoding thing, I addedd URIEncoding=UTF-8 to the AJP connector
(though that shouldn't be necessary) , but that did not help.
Looking with vi at the file on the filesystem shows correct encoding.
I have to dig a bit more (tomorrow I think).

regards,
Harry



On 29 November 2013 00:00, Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com wrote:

 Hi,

 I've just noticed a couple of strange things:

 - preferences aren't saved if you're an anonymous user, not sure if related
 to ProxyPassReverseCookiePath parameter being (not?) set on apache cfg?
 apache isn't changing the app path, so it shouldn't be necessary.

 - non-ascii letters are shown as ?, i.e. I get Buenas, (an?nimo) instead
 of Buenas, (anónimo) not sure if uriencoding is set on tomcats'
 server.xml, or if it's an apache issue

 both issues also happen when going directly through jspwiki-vm.a.o/wiki

 thoughts?


 br,
 juan pablo



 On Wed, Nov 27, 2013 at 11:14 PM, Glen Mazza glen.ma...@gmail.com wrote:

  Could it be that they didn't give us jspwiki.apache.org/wiki directly
  because jspwiki.apache.org refers to a different machine (IP address)?
   But at least j.a.o/wiki redirects to the wiki.
 
  Glen
 
 
  On 11/27/2013 03:19 PM, Harry Metske wrote:
 
  Juan,
 
  X-Forwarded-For header is an excellent idea. I should have thought of
 that
  myself :-).
  I just check on the vm, we get that header passed from the proxy. I will
  create a JIRA issue for JSPWiki SpamFilter for that.
  I'll also ask INFRA if it possible to have the URL changed.
 
  tx,
  Harry
 
 
 
  On 27 November 2013 18:59, Juan Pablo Santos Rodríguez 
  juanpablo.san...@gmail.com wrote:
 
   Hi Harry,
 
  thanks a lot for pursuing this!!
 
  as you say, https://jspwiki-wiki.apache.org/wiki seems a little weird,
  ideally, jspwiki.a.o/wiki should serve the wiki (same for doc wiki). As
  for
  the real ip, could we use x-ip-forwarded-for header? (don't know about
  fail2ban, but most probably SpamFilter isn't looking in for that
 header,
  we
  should add it)
 
 
  br,
  juan pablo
 
 
 
  On Wed, Nov 27, 2013 at 9:40 AM, Harry Metske harry.met...@gmail.com
 
  wrote:
  Folks,
 
  Our wiki is now available at : https://jspwiki-wiki.apache.org/wiki
 
 
  See the last comment for the status :
 
 
   https://issues.apache.org/jira/browse/INFRA-5588?
  focusedCommentId=13833580page=com.atlassian.jira.
  plugin.system.issuetabpanels:comment-tabpanel#comment-13833580
 
  Does anyone of you have anything to add here ?
 
  * I like to see client IP address, so we can use the SpamFilter and
  fail2ban.
  * the URL has a double reference to wiki, both in the hostname and the
  resource after the / (and also for doc), but is not a showstopper to
 
  me.
 
  kind regards,
  Harry
 
 
 

Re: Kick out 2.9.1

[Harry Metske]

Juan Pablo,

first, thanks for all your efforts, I too appreciate !

I have been testing the trunk, the only thing I could find until now is
every 30 seconds a couple of these in the jspwiki.log:

2013-12-18 20:44:11,954 ERROR org.apache.wiki.WatchDog - Stack is empty!
java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:102)
at org.apache.wiki.WatchDog.check(WatchDog.java:264)
at org.apache.wiki.WatchDog.access$300(WatchDog.java:52)
at
org.apache.wiki.WatchDog$WatchDogThread.backgroundTask(WatchDog.java:371)
at
org.apache.wiki.WikiBackgroundThread.run(WikiBackgroundThread.java:118)

I'm investigating it currently...

kind regards,
Harry




On 18 December 2013 02:00, Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com wrote:

 Hi,

 quick note, as it's nearly 2.00am here; done almost all steps required to
 publish all artifacts on a staging repo, which the vote is going to be run
 against. Currently blocked by a nexus timeout on closing the staging repo,
 progress can be followed at
 https://issues.apache.org/jira/browse/INFRA-7105.
 Once this is fixed (hopefully by tomorrow..), the vote for 2.10.0 release
 will be called.


 br,
 juan pablo



 On Mon, Dec 16, 2013 at 10:50 PM, Siegfried Goeschl 
 siegfried.goes...@it20one.com wrote:

  Hi Juan Pablo,
 
  I will play around with the current trunk :-)
 
  Cheers,
 
  Siegfried Goeschl
 
 
  On 16 Dec 2013, at 22:03, Juan Pablo Santos Rodríguez 
  juanpablo.san...@gmail.com wrote:
 
   Hi,
  
   just finished doing a big bunch of pending refactors prior to releasing
   2.10. We should be able to end up with all the artifacts on maven
 central
   too (once the vote+release passes), and use a staged repository[#1] to
  vote
   instead of uploading to somewhere at people.a.o
  
   There are only a couple of points remaining: updating UPGRADING and
   ReleaseNotes and ensuring all the prerequisites of [#1] are met.
  Hopefully,
   they will be done between today and tomorrow. In the meantime, this is
 a
   call for testing current trunk, which is going to be most likely
 2.10.0.
   I've tried to test all the recent commits (and will continue to do some
   more testing), but for sure the more people looking into it before
 voting
   the release, the better.
  
  
   thanks + br,
   juan pablo
  
  
   [#1]:
  
 http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven
  
  
  
   On Sun, Nov 10, 2013 at 11:07 PM, Siegfried Goeschl 
   siegfried.goes...@it20one.at wrote:
  
   Hi folks,
  
   IMHO it is important to get the release out
  
   * users are looking at project activity - there are many different
 wikis
   out there ...
  
   * are there bugfixes in 2.9.1 the users would appreciate? Better have
 a
   small bugfix release now than the latest and greatest release 9 months
  down
   the road (which might get delayed later on)
  
   Cheers,
  
   Siegfried Goeschl
  
  
  
  
   On 10.11.13 21:39, Juan Pablo Santos Rodríguez wrote:
  
   Hi,
  
   about 2.9 vs 2.10, I was having in mind releasing trunk in any case,
  the
   version numbers were just to note binary compatibility. If we release
   current trunk as it is, it isn't binary compatible with latest
 release,
   because of 2.10.0-svn-8 and 2.10.0-svn-26. We could copy those
 classes
   back
   to their original location and have 2.9.2 (with some duplicated
  classes)
   or
   just release 2.10.0 as it is. I'm a little inclined to 2.9.2,
 because I
   was
   having in mind further similar refactorings with the rest of the
  managers
   for 2.10, but given the fact I've been unable to spend time coding
  these
   last months, 2.10 would also be fine for me.
  
   As an aside, there's an initial Infra setup [#1] to allow us to
 deploy
  to
   repository.apache.org, which is synced with central. Once that is
  done,
   I'll update the appropiate page on jspwiki.a.o
  
  
   br,
   juan pablo
  
   [#1] https://issues.apache.org/jira/browse/INFRA-6986
  
  
  
   On Fri, Nov 8, 2013 at 10:39 PM, Glen Mazza glen.ma...@gmail.com
  wrote:
  
   Yes, I don't see any need to release the same 2.9.1 product just
  without
   incubator in its version name, that's not a very Apache-esque way
 of
   doing things (the incubator in version release is not an indicator
  of
   software quality, as Apache stresses over and over.)   If none of us
   right
   now have time to work on JSPWiki (a situation I hope changes soon
 with
   me),
   busywork such as that isn't going to help the situation.
  
   Glen
  
  
   On 11/08/2013 01:02 PM, Harry Metske wrote:
  
   what would be reasons to release 2.9.x versus 2.10.x ?
   The latter has more issues fixed...
  
   regards,
   Harry
  
  
  
   On 8 November 2013 08:41, Jürgen Weber juer...@jwi.de wrote:
  
+1
  
   Am 07.11.2013 19:33 schrieb Juan Pablo Santos Rodríguez 
   juanpablo.san...@gmail.com:
  
+1 too
  
   In order to remain 2.9.x, we should get back o.a.w.WikiException
   (deleted
   in favour

Re: Kick out 2.9.1

[Harry Metske]

Also, I was wondering why we need this WatchDog thing altogether.
I understand that it should notify (log a message) when a Thread takes too
long to end, but to be honest I have never seen such a warning.
The cons are :
* it clutters up our code
* leaves running threads behing when the webapp is stopped (Tomcat
complains about it), for example the Lucene Indexer, RSS generator, and
more)
* for every request we make 2 WatchDogs (WikiJSPPFilter), and if I'm
correct that means 2 Threads created/destroyed, I would think that's quite
some overhead (I could do some measurements on that).
* it now also pollutes the log (but we might fix that)

WDYT ?

kind regards,
Harry



On 18 December 2013 22:14, Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com wrote:

 Hi Harry,

 I had a lot of those while testing before r1551702, due to
 o.a.w.tags.SearchResultIteratorInfo containing a String with an incorrect
 classname. I'm currently re-trying to close the repo*, but I'll recheck on
 that too to make sure everything is ok in order to proceed with voting


 br,
 juan pablo


 * my current plan is to try 2 or 3 more times in the following hours, while
 updating the How to release instructions at jspwiki.a.o. If tomorrow
 morning the repo persists in not being closed, I'll upload the repo
 artifacts somewhere at people.a.o to start the vote with some convenience
 binaries. Later on we can mark that staging repo as closed + released, so
 binaries effectively reach Central..


 On Wed, Dec 18, 2013 at 8:47 PM, Harry Metske harry.met...@gmail.com
 wrote:

  Juan Pablo,
 
  first, thanks for all your efforts, I too appreciate !
 
  I have been testing the trunk, the only thing I could find until now is
  every 30 seconds a couple of these in the jspwiki.log:
 
  2013-12-18 20:44:11,954 ERROR org.apache.wiki.WatchDog - Stack is empty!
  java.util.EmptyStackException
  at java.util.Stack.peek(Stack.java:102)
  at org.apache.wiki.WatchDog.check(WatchDog.java:264)
  at org.apache.wiki.WatchDog.access$300(WatchDog.java:52)
  at
  org.apache.wiki.WatchDog$WatchDogThread.backgroundTask(WatchDog.java:371)
  at
  org.apache.wiki.WikiBackgroundThread.run(WikiBackgroundThread.java:118)
 
  I'm investigating it currently...
 
  kind regards,
  Harry
 
 
 
 
  On 18 December 2013 02:00, Juan Pablo Santos Rodríguez 
  juanpablo.san...@gmail.com wrote:
 
   Hi,
  
   quick note, as it's nearly 2.00am here; done almost all steps required
 to
   publish all artifacts on a staging repo, which the vote is going to be
  run
   against. Currently blocked by a nexus timeout on closing the staging
  repo,
   progress can be followed at
   https://issues.apache.org/jira/browse/INFRA-7105.
   Once this is fixed (hopefully by tomorrow..), the vote for 2.10.0
 release
   will be called.
  
  
   br,
   juan pablo
  
  
  
   On Mon, Dec 16, 2013 at 10:50 PM, Siegfried Goeschl 
   siegfried.goes...@it20one.com wrote:
  
Hi Juan Pablo,
   
I will play around with the current trunk :-)
   
Cheers,
   
Siegfried Goeschl
   
   
On 16 Dec 2013, at 22:03, Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com wrote:
   
 Hi,

 just finished doing a big bunch of pending refactors prior to
  releasing
 2.10. We should be able to end up with all the artifacts on maven
   central
 too (once the vote+release passes), and use a staged repository[#1]
  to
vote
 instead of uploading to somewhere at people.a.o

 There are only a couple of points remaining: updating UPGRADING and
 ReleaseNotes and ensuring all the prerequisites of [#1] are met.
Hopefully,
 they will be done between today and tomorrow. In the meantime, this
  is
   a
 call for testing current trunk, which is going to be most likely
   2.10.0.
 I've tried to test all the recent commits (and will continue to do
  some
 more testing), but for sure the more people looking into it before
   voting
 the release, the better.


 thanks + br,
 juan pablo


 [#1]:

  
 http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven



 On Sun, Nov 10, 2013 at 11:07 PM, Siegfried Goeschl 
 siegfried.goes...@it20one.at wrote:

 Hi folks,

 IMHO it is important to get the release out

 * users are looking at project activity - there are many different
   wikis
 out there ...

 * are there bugfixes in 2.9.1 the users would appreciate? Better
  have
   a
 small bugfix release now than the latest and greatest release 9
  months
down
 the road (which might get delayed later on)

 Cheers,

 Siegfried Goeschl




 On 10.11.13 21:39, Juan Pablo Santos Rodríguez wrote:

 Hi,

 about 2.9 vs 2.10, I was having in mind releasing trunk in any
  case,
the
 version numbers were just to note binary compatibility. If we
  release
 current trunk

Re: Subject: [VOTE] Release JSPWiki version 2.10.0

[Harry Metske]

the same for all the other artifacts.
We need JP or root to chmod them...
 Op 21 dec. 2013 08:24 schreef Ichiro Furusato ichiro.furus...@gmail.com
:

 Just a note: when I tried to access the source zip permissions didn't
 permit me to download it.


 On Sat, Dec 21, 2013 at 12:02 PM, Juan Pablo Santos Rodríguez 
 juanpablo.san...@gmail.com wrote:

  This is a release vote for Apache JSPWiki, version 2.10.0. The vote will
 be
  open for at least 72 hours from now.
 
  It fixes the following issues:
 
 
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12323941
 
  Note that we are voting upon the source (tag), binaries are provided for
  convenience.
 
  Everybody is encouraged to vote.
 
  Source and binary files:
  http://people.apache.org/~juanpablo/releases/2.10.0-rc1
 
  The tag to be voted upon:
  http://svn.apache.org/repos/asf/jspwiki/tags/jspwiki_2_10_0_rc1
 
  JSPWiki's KEYS file containing PGP keys we use to sign the release:
  http://www.apache.org/dist/jspwiki/KEYS
 
  *** Please download, test and vote:
 
  [ ] +1 Approve the release
  [ ]  0 Don't mind
  [ ] -1 Disapprove the release (please provide specific comments)
 
 
  br,
  juan pablo
 

Re: Subject: [VOTE] Release JSPWiki version 2.10.0

[Harry Metske]

I'm sorry, but I have to give this a -1

Reason is the pollution of log files with the
java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:102)
at org.apache.wiki.WatchDog.check(WatchDog.java:263)
at org.apache.wiki.WatchDog.access$300(WatchDog.java:52)
at
org.apache.wiki.WatchDog$WatchDogThread.backgroundTask(WatchDog.java:370)
at
org.apache.wiki.WikiBackgroundThread.run(WikiBackgroundThread.java:118)

For the rest I did not find any issues.

kind regards,
Harry

(I already did some testing with the WatchDog thingy ripped out. No
noticeable difference in resource consumption though, but still a few
reasons to get rid of it, let me know what you think).




On 21 December 2013 00:02, Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com wrote:

 This is a release vote for Apache JSPWiki, version 2.10.0. The vote will be
 open for at least 72 hours from now.

 It fixes the following issues:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12323941

 Note that we are voting upon the source (tag), binaries are provided for
 convenience.

 Everybody is encouraged to vote.

 Source and binary files:
 http://people.apache.org/~juanpablo/releases/2.10.0-rc1

 The tag to be voted upon:
 http://svn.apache.org/repos/asf/jspwiki/tags/jspwiki_2_10_0_rc1

 JSPWiki's KEYS file containing PGP keys we use to sign the release:
 http://www.apache.org/dist/jspwiki/KEYS

 *** Please download, test and vote:

 [ ] +1 Approve the release
 [ ]  0 Don't mind
 [ ] -1 Disapprove the release (please provide specific comments)


 br,
 juan pablo

Re: can't build trunk

[Harry Metske]

Glen,

since rev 1551279 (16 Dec) the port was changed from 9001 to 9321. This was
done to prevent similar intermittent errors on the apache Jenkins machine
(assuming other projects running on the same machine were also using HSQLDB
with the same port).
Do you have some running on that 9321 port maybe ?

regards,
Harry




On 22 December 2013 13:04, Glen Mazza glen.ma...@gmail.com wrote:

 Hi all, I can't build trunk--doing JDK 1.7.0_25 on Ubuntu.  With a fresh
 checkout of jspwiki from SVN into an empty folder and running mvn clean
 install returns these errors:

 Running org.apache.wiki.auth.user.JDBCUserDatabaseTest
 [Server@396352e]: [Thread[main,5,main]]: setSilent(true)
 [Server@34a403c7]: [Thread[main,5,main]]: setSilent(true)
 Looks like your database could not be connected to - please make sure that
 you have started your database, exception: java.sql.SQLException:
 java.lang.NullPointerException java.lang.NullPointerException
 [Server@69673772]: [Thread[main,5,main]]: setSilent(true)
 [Server@69673772]: [Thread[HSQLDB Server @69673772,5,main]]:
 run()/openServerSocket():
 java.net.BindException: Address already in use
 at java.net.PlainSocketImpl.socketBind(Native Method)
 at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:
 376)

 ...

 Looks like your database could not be connected to - please make sure that
 you have started your database, exception: java.sql.SQLException:
 java.lang.NullPointerException java.lang.NullPointerException
 Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 1.304 sec
  FAILURE! - in org.apache.wiki.auth.authorize.JDBCGroupDatabaseTest
 testSave(org.apache.wiki.auth.authorize.JDBCGroupDatabaseTest)  Time
 elapsed: 0.328 sec   ERROR!
 java.sql.SQLException: java.lang.NullPointerException
 java.lang.NullPointerException
 at org.hsqldb.error.Error.error(Unknown Source)
 at org.hsqldb.ClientConnection.init(Unknown Source)
 at org.hsqldb.jdbc.JDBCConnection.init(Unknown Source)
 at org.hsqldb.jdbc.JDBCDriver.getConnection(Unknown Source)
 at org.hsqldb.jdbc.JDBCDriver.connect(Unknown Source)
 at org.apache.wiki.TestJDBCDataSource.getConnection(
 TestJDBCDataSource.java:100)
 at org.apache.wiki.TestJDBCDataSource.getConnection(
 TestJDBCDataSource.java:86)
 at org.apache.wiki.auth.authorize.JDBCGroupDatabaseTest.setUp(
 JDBCGroupDatabaseTest.java:83)

 testDelete(org.apache.wiki.auth.authorize.JDBCGroupDatabaseTest) Time
 elapsed: 0.324 sec   ERROR!
 java.sql.SQLException: java.lang.NullPointerException
 java.lang.NullPointerException
 at org.hsqldb.error.Error.error(Unknown Source)
 at org.hsqldb.ClientConnection.init(Unknown Source)
 at org.hsqldb.jdbc.JDBCConnection.init(Unknown Source)
 at org.hsqldb.jdbc.JDBCDriver.getConnection(Unknown Source)
 at org.hsqldb.jdbc.JDBCDriver.connect(Unknown Source)
 at org.apache.wiki.TestJDBCDataSource.getConnection(
 TestJDBCDataSource.java:100)
 at org.apache.wiki.TestJDBCDataSource.getConnection(
 TestJDBCDataSource.java:86)
 at org.apache.wiki.auth.authorize.JDBCGroupDatabaseTest.setUp(
 JDBCGroupDatabaseTest.java:83)

 ...

 Tests in error:
   JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
   JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
   JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
   JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
   JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
   JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
   JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
   JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
   JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
   JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
   JDBCGroupDatabaseTest.setUp:90 SQL java.lang.NullPointerException
 java.lang.Nu...
   JDBCGroupDatabaseTest.setUp:90 SQL java.lang.NullPointerException
 java.lang.Nu...
   JDBCGroupDatabaseTest.setUp:90 SQL java.lang.NullPointerException
 java.lang.Nu...
   JDBCGroupDatabaseTest.setUp:90 SQL java.lang.NullPointerException
 java.lang.Nu...

 Tests run: 936, Failures: 0, Errors: 14, Skipped: 0

 The problem appears to be the Address already in use error above w.r.t.
 HSQLDB.  FWIW, I didn't have Tomcat or other container running on my
 machine at the time of compile, and AFAIK am not running HSQLDB separately
 either.  Anybody know what the problem is?

 Regards,
 Glen

Re: can't build trunk

[Harry Metske]

I am running Ubuntu, and have not seen this issue at all.
I just ran the test suite again (while looking at the jspwiki.policy.file
issue), and it runs fine here.

regards,
Harry



On 22 December 2013 14:01, Glen Mazza glen.ma...@gmail.com wrote:

 No, I wasn't able to find 9321 in use anywhere using the netstat (
 http://askubuntu.com/a/278455). And same problem when I flipped it back
 to 9001 in jspwiki-war/src/test/resources/jspwiki-custom.properties (both
 places).   I wonder if our test processes are trying to activate that port
 twice.  Anybody else using Linux/Ubuntu and can get the build to work?

 Glen

 On 12/22/2013 07:20 AM, Harry Metske wrote:

 Glen,

 since rev 1551279 (16 Dec) the port was changed from 9001 to 9321. This
 was
 done to prevent similar intermittent errors on the apache Jenkins machine
 (assuming other projects running on the same machine were also using
 HSQLDB
 with the same port).
 Do you have some running on that 9321 port maybe ?

 regards,
 Harry




 On 22 December 2013 13:04, Glen Mazza glen.ma...@gmail.com wrote:

  Hi all, I can't build trunk--doing JDK 1.7.0_25 on Ubuntu.  With a fresh
 checkout of jspwiki from SVN into an empty folder and running mvn clean
 install returns these errors:

 Running org.apache.wiki.auth.user.JDBCUserDatabaseTest
 [Server@396352e]: [Thread[main,5,main]]: setSilent(true)
 [Server@34a403c7]: [Thread[main,5,main]]: setSilent(true)
 Looks like your database could not be connected to - please make sure
 that
 you have started your database, exception: java.sql.SQLException:
 java.lang.NullPointerException java.lang.NullPointerException
 [Server@69673772]: [Thread[main,5,main]]: setSilent(true)
 [Server@69673772]: [Thread[HSQLDB Server @69673772,5,main]]:
 run()/openServerSocket():
 java.net.BindException: Address already in use
  at java.net.PlainSocketImpl.socketBind(Native Method)
  at java.net.AbstractPlainSocketImpl.bind(
 AbstractPlainSocketImpl.java:
 376)

 ...

 Looks like your database could not be connected to - please make sure
 that
 you have started your database, exception: java.sql.SQLException:
 java.lang.NullPointerException java.lang.NullPointerException
 Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 1.304 sec
  FAILURE! - in org.apache.wiki.auth.authorize.JDBCGroupDatabaseTest
 testSave(org.apache.wiki.auth.authorize.JDBCGroupDatabaseTest)  Time
 elapsed: 0.328 sec   ERROR!
 java.sql.SQLException: java.lang.NullPointerException
 java.lang.NullPointerException
  at org.hsqldb.error.Error.error(Unknown Source)
  at org.hsqldb.ClientConnection.init(Unknown Source)
  at org.hsqldb.jdbc.JDBCConnection.init(Unknown Source)
  at org.hsqldb.jdbc.JDBCDriver.getConnection(Unknown Source)
  at org.hsqldb.jdbc.JDBCDriver.connect(Unknown Source)
  at org.apache.wiki.TestJDBCDataSource.getConnection(
 TestJDBCDataSource.java:100)
  at org.apache.wiki.TestJDBCDataSource.getConnection(
 TestJDBCDataSource.java:86)
  at org.apache.wiki.auth.authorize.JDBCGroupDatabaseTest.setUp(
 JDBCGroupDatabaseTest.java:83)

 testDelete(org.apache.wiki.auth.authorize.JDBCGroupDatabaseTest) Time
 elapsed: 0.324 sec   ERROR!
 java.sql.SQLException: java.lang.NullPointerException
 java.lang.NullPointerException
  at org.hsqldb.error.Error.error(Unknown Source)
  at org.hsqldb.ClientConnection.init(Unknown Source)
  at org.hsqldb.jdbc.JDBCConnection.init(Unknown Source)
  at org.hsqldb.jdbc.JDBCDriver.getConnection(Unknown Source)
  at org.hsqldb.jdbc.JDBCDriver.connect(Unknown Source)
  at org.apache.wiki.TestJDBCDataSource.getConnection(
 TestJDBCDataSource.java:100)
  at org.apache.wiki.TestJDBCDataSource.getConnection(
 TestJDBCDataSource.java:86)
  at org.apache.wiki.auth.authorize.JDBCGroupDatabaseTest.setUp(
 JDBCGroupDatabaseTest.java:83)

 ...

 Tests in error:
JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
JDBCUserDatabaseTest.setUp:131 SQL java.lang.NullPointerException
 java.lang.Nu...
JDBCGroupDatabaseTest.setUp:90 SQL java.lang.NullPointerException
 java.lang.Nu...
JDBCGroupDatabaseTest.setUp:90 SQL java.lang.NullPointerException
 java.lang.Nu...
JDBCGroupDatabaseTest.setUp:90 SQL java.lang.NullPointerException

ReferringUndefinedPagesPlugin in the base distribution

[Harry Metske]

Hi,

I would like to see the ReferringUndefinedPagesPlugin as one of the core
plugins.
See http://www.ecyrd.com/JSPWiki/wiki/ReferringUndefinedPagesPlugin for
more info.
The code is just a few lines:
http://www.ecyrd.com/JSPWiki/attach/ReferringUndefinedPagesPlugin/ReferringUndefinedPagesPlugin.java.

The original (non-core) plugin was an idea by Gregor Hagedorn.
Are there any legal issues, how to approach ?

We could also rewrite from scratch, it's just a few lines.

regards,
Harry

Re: new JSPWiki wiki available, https://jspwiki-wiki.apache.org

[Harry Metske]

Hi,

the latest version (1.0.8) of the CleanBlue is now on
jspwiki-wiki.apache.org and looks good.
What would you think to sollicit some more feedback:
* make this skin (temporarily) the default
(jspwiki.defaultprefs.template.skinname = CleanBlue)
* make a temporary Titlebox page to tell about it and ask for feedback ?

regards,
Harry




On 2 January 2014 20:58, Harry Metske harry.met...@gmail.com wrote:

 Ichiro, thanks for the skin,

 I installed the skin on https://jspwiki-wiki.apache.org .

 Let me know what you all think...

 it is all personal preferences of course, but I think it needs a couple of
 tweaks:
 * logo's are indeed much better
 * at the top of screen too much space is used for the page title and the
 tabs (view/attach/info), leaving too little left for the page content
 * i'd like the fonts in general a little smaller
 * the left menu background color could be little darker, a bit more
 contrast would be nice (when hovering over it is exactly right).


 BTW: I do get 404's for the following files with this skin :
 /wiki/templates/default/images/jspwiki-strip.gif
 /wiki/templates/default/skins/CleanBlue/images/search.gif
 /wiki/templates/default/skins/CleanBlue/images/sortable.gif

 regards,
 Harry




 On 2 January 2014 02:11, Ichiro Furusato ichiro.furus...@gmail.comwrote:

 Happy new year Harry and thanks for the new wiki. Good timing on a new
 start...

 Would you be interested in adopting a template we've been testing here for
 about a month? It's not perfect but it looks a lot better than the
 default,
 and
 we'd be willing to donate it to the project under an Apache license if the
 team
 liked it.

 If so, let me know and I'll send you a zip.

 Ichiro


 On Wed, Jan 1, 2014 at 10:25 PM, Harry Metske harry.met...@gmail.com
 wrote:

  Hi all,
 
  First of all, we wish you a Happy New Year !
 
  we have our new JSPWiki wiki running at apache infra. It is available at
  https://jspwiki-wiki.apache.org.
  This is the official replacement for the old www.jspwiki.org (which is
  read-only at http://www.ecyrd.com/JSPWiki/wiki/).
 
  The wiki is currently almost empty, we have to start building that up
  again.
  So anyone who is willing to help, register an account and start working
 on
  the wiki.
 
  If you have any questions, do not hesitate to send your questions to the
  list (user or dev).
 
  kind regards,
  the JSPWiki team
 

Re: new JSPWiki wiki available, https://jspwiki-wiki.apache.org

[Harry Metske]

  
  
  
  
  
  
   On Mon, Jan 6, 2014 at 7:56 PM, Harry Metske 
   harry.met...@gmail.com

   wrote:
  
Hi,
   
the latest version (1.0.8) of the CleanBlue is now on
jspwiki-wiki.apache.org and looks good.
What would you think to sollicit some more feedback:
* make this skin (temporarily) the default
(jspwiki.defaultprefs.template.skinname = CleanBlue)
* make a temporary Titlebox page to tell about it and ask for
 feedback
  ?
   
regards,
Harry
   
   
   
   
On 2 January 2014 20:58, Harry Metske 
 harry.met...@gmail.com
 wrote:
   
 Ichiro, thanks for the skin,

 I installed the skin on https://jspwiki-wiki.apache.org .

 Let me know what you all think...

 it is all personal preferences of course, but I think it
  needs
   a
  couple
of
 tweaks:
 * logo's are indeed much better
 * at the top of screen too much space is used for the page
   title
 and
   the
 tabs (view/attach/info), leaving too little left for the
 page
 content
 * i'd like the fonts in general a little smaller
 * the left menu background color could be little darker, a
  bit
more
 contrast would be nice (when hovering over it is exactly
   right).


 BTW: I do get 404's for the following files with this skin
 :
 /wiki/templates/default/images/jspwiki-strip.gif
 /wiki/templates/default/skins/CleanBlue/images/search.gif
 /wiki/templates/default/skins/CleanBlue/images/sortable.gif

 regards,
 Harry




 On 2 January 2014 02:11, Ichiro Furusato 
 ichiro.furus...@gmail.com
wrote:

 Happy new year Harry and thanks for the new wiki. Good
  timing
on a
  new
 start...

 Would you be interested in adopting a template we've been
testing
  here
for
 about a month? It's not perfect but it looks a lot better
  than
the
 default,
 and
 we'd be willing to donate it to the project under an
 Apache
 license
  if
the
 team
 liked it.

 If so, let me know and I'll send you a zip.

 Ichiro


 On Wed, Jan 1, 2014 at 10:25 PM, Harry Metske 
  harry.met...@gmail.com
 wrote:

  Hi all,
 
  First of all, we wish you a Happy New Year !
 
  we have our new JSPWiki wiki running at apache infra. It
  is
   available
at
  https://jspwiki-wiki.apache.org.
  This is the official replacement for the old
   www.jspwiki.org
 (which
is
  read-only at http://www.ecyrd.com/JSPWiki/wiki/).
 
  The wiki is currently almost empty, we have to start
   building
 that
   up
  again.
  So anyone who is willing to help, register an account
 and
start
working
 on
  the wiki.
 
  If you have any questions, do not hesitate to send your
 questions
  to
the
  list (user or dev).
 
  kind regards,
  the JSPWiki team
 



   
  
 

   
  
 

Re: new JSPWiki wiki available, https://jspwiki-wiki.apache.org

[Harry Metske]

With the logo
Op 12 jan. 2014 21:41 schreef Ichiro Furusato ichiro.furus...@gmail.com:

 Thanks - do you guys like the logo with or without the Apache on the
 hover image?


 On Mon, Jan 13, 2014 at 3:14 AM, Juan Pablo Santos Rodríguez 
 juanpablo.san...@gmail.com wrote:

  Hi,
 
  I'm +1 on including it, nice work Ichiro!
 
 
  br,
  juan pablo
 
 
 
  On Sun, Jan 12, 2014 at 2:23 PM, Harry Metske harry.met...@gmail.com
  wrote:
 
   Hi,
  
   Ichiro submitted the latest (1.0.10) version of the CleanBlue template,
  all
   coloring issues have been fixed.
   I just put it on https://jspwiki-wiki.apache.org .
  
   If there are no more issues, what about adding this template to the
 core
  ?
  
   regards,
   Harry
  
  
  
  
  
   On 9 January 2014 22:34, Dirk Frederickx dirk.frederi...@gmail.com
   wrote:
  
Ichiro,
   
This problem also occurs on FF.
   
This is the reason of the problem:
#header * a, #footer * a {
   
   1. color: #F5FBFF;
   2. font-size: 95%;
   
}
   
This sets the color of links inside a header to light-blue, which is
  also
the color of the background.
   
Try #searchboxMenu a { color: black; } to set the color to black.
   
   
dirk
   
   
   
On Thu, Jan 9, 2014 at 10:02 PM, Ichiro Furusato
ichiro.furus...@gmail.comwrote:
   
 Hi Dirk,

 I've tried this again and can't replicate it on Chrome on Linux.

 The selector I'm seeing is a within a bullet list inside of a
 div
 id=searchOutput.

 The current stylesheet has the following match:

 #searchboxMenu, #searchResult, #searchTarget,
 * #searchOutput, #searchOutput a, *#recentSearches,
 #recentClear
  {
   background:#F5FBFF; color : #00 ;
 }

 I've added a more specific selector to that list:

 #searchOutput ui li a { ... }

 and will publish that upon the next update.

 Ichiro



 On Fri, Jan 10, 2014 at 8:23 AM, Dirk Frederickx
 dirk.frederi...@gmail.comwrote:

  Ichiro,
 
 
 
 
 
  *The one remaining issue was the quick search. I don't see a
  problem
with
  itin Chrome. Could you confirm where that is? Possibly do an
  'Inspect
  Element(Q)'on it with FireBug to provide the selector?*
 
  You can repeat the issue like this:
   Do a search in JSPWiki
   The Quick Navigation drop down now show the searched value in
  the
  Recent-Searches list
   the color of that list is white on white (in webkit)
 
 
  dirk
 
 
  On Mon, Jan 6, 2014 at 11:35 PM, Ichiro Furusato
  ichiro.furus...@gmail.comwrote:
 
   Hi Dirk,
  
   Thanks very much for that converter link -- very handy!  I've
   managed
 to
   fix the
   gradient problem in my local copy (now works in Chrome on
 Linux),
will
  post
   the new version of CleanBlue later today.
  
   The one remaining issue was the quick search. I don't see a
  problem
 with
  it
   in Chrome. Could you confirm where that is? Possibly do an
  'Inspect
  Element
   (Q)'
   on it with FireBug to provide the selector?
  
   Cheers,
  
   Ichiro
  
  
  
   On Tue, Jan 7, 2014 at 10:54 AM, Dirk Frederickx
   dirk.frederi...@gmail.comwrote:
  
Ichiro,
   
Aha - Firefox;  that looks much better !
I was checking Chrome  Safari.
   
You may want to check-out
  http://lea.verou.me/demos/cssgradientsplease/to
convert to -webkit- gradients.
   
   
dirk
   
   
   
On Mon, Jan 6, 2014 at 10:41 PM, Ichiro Furusato
ichiro.furus...@gmail.comwrote:
   
 Hi Dirk,

  I noticed some colouring issues:
 
  - the pagename is white, on a white background

 Do mean the page name at the top of the page? Ack. I just
   thought
 you
 must not be using Firefox so I tried Chrome and see this
 now.
I'll
  have
to
 see if there's some way to have Chrome do a mozilla-style
gradient.

  - also the page-footer text is white, on a white
 background

 Ah, yes, will fix that.

  - idem for the recent-search results (in the
  quick-navigation
 drop
down)

 Again, this looks fine in Firefox, black on translucent
 light
blue.
   Looks
 okay
 in Chrome (on Linux), so I'm wondering if this is browser
dependent
  or
I'm
 not understanding where it is you're seeing this.

  BTW, the google fonts are loaded from http://, while the
apache
  wiki
 site
  is loaded from https:// ; which gives a security warning
  in
 google
 chrome.
  You may want to also load the fonts from https

updating wikimatrix.org

[Harry Metske]

Hello,

I think it is about time to update our page at
http://www.wikimatrix.org/show/JSPWiki .
If I remember correctly, keeping wikimatrix up-to-date was a task for
Florian.
But since Florian is not very active anymore, how to proceed ?

@Florian: If you are listening, are you still able and willing to do such
an update ?

If Florian does not reply, I will try to contact him on another email
address, if he is not able/ willing to update, I could do it, but I need
the userid/password

regards,
Harry

Re: replace (Legacy)Doc wiki link at jspwiki.a.o?

[Harry Metske]

+1
Op 14 jan. 2014 23:43 schreef Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com:

 Hi,

 the (Legacy)Doc wiki at jspwiki.a.o points to
 http://www.ecyrd.com/JSPWiki/wiki/JSPWikiDocumentation, how about changing
 it to https://jspwiki-wiki.apache.org/Wiki.jsp?page=JSPWikiDocumentation?


 br,
 juan pablo

Re: [VOTE] Release JSPWiki version 2.10.0

[Harry Metske]

+1

kind regards,
Harry



On 14 January 2014 23:08, Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com wrote:

 This is a release vote for Apache JSPWiki, version 2.10.0. The vote will be
 open for at least 72 hours from now.

 It fixes the following issues:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12323941

 Note that we are voting upon the source (tag), binaries are provided for
 convenience.

 Everybody is encouraged to vote.

 Source and binary files:
 http://people.apache.org/~juanpablo/releases/2.10.0-rc2

 Nexus staging repo:
 https://repository.apache.org/content/repositories/orgapachejspwiki-1000/

 The tag to be voted upon:
 http://svn.apache.org/repos/asf/jspwiki/tags/jspwiki_2_10_0_rc2

 JSPWiki's KEYS file containing PGP keys we use to sign the release:
 http://svn.apache.org/repos/asf/jspwiki/tags/jspwiki_2_10_0_rc2/KEYS

 *** Please download, test and vote:

 [ ] +1 Approve the release
 [ ]  0 Don't mind
 [ ] -1 Disapprove the release (please provide specific comments)


 br,
 juan pablo

Re: updating wikimatrix.org

[Harry Metske]

thanks Florian

regards,
Harry



On 2 February 2014 10:18, Florian Holeczek flor...@holeczek.de wrote:

 Hi all,

 I've updated the following pages:

 [1] http://www.wikimatrix.org/show/JSPWiki
 [2] http://de.wikipedia.org/w/index.php?title=JSPWikistable=0
 [3] http://es.wikipedia.org/wiki/JSPWiki
 [4] http://fr.wikipedia.org/wiki/JSPWiki
 [5] http://simple.wikipedia.org/wiki/JSPWiki
 [6] http://www.heise.de/download/jspwiki-1160392.html

 Notes:
 [2] needs to be approved by wiki admins before it is publicly visible.
 Regarding [3] and [4], I've only updated the info boxes but not the text
 contents. Preferably, this task will be done by someone who knows these
 languages better.

 Regards
  Florian

Re: JSON-RPC support

[Harry Metske]

I am a complete novice in this area, but aren't you running in this same
situation as we did before:

https://issues.apache.org/jira/browse/JSPWIKI-659?focusedCommentId=13552522page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13552522

kind regards,
Harry




On 15 February 2014 14:00, Ichiro Furusato ichiro.furus...@gmail.comwrote:

 Hi Dirk,

 I'm not suggesting the issue is mootools vs. jQuery, only that my
 inexperience
 with the former and the difficulty in intermixing them has kept me from
 using my
 own jQuery knowledge (which is still relatively novice-level) to quickly
 debug the
 problem, client-side.

 More pertinent to what I agree is the problem is why the global
 registration never
 seems to result in the JSON-RPC calls being successful. After all I've
 tried I'm
 now registering a singleton global object similar to the SearchManager,
 i.e., an
 object that exists prior to the page containing either the plugin or the
 JSP-based
 client-side script being called. And the registration does show up as
 successful
 in the logs. So I agree, this is server-side, but it seems to have more to
 do with
 the client being unable to get *any* response from the server on a
 pre-registered
 RPCCallable object. As I mentioned, until the RPCSamplePlugin can be shown
 to work I think I'm just stabbing in the dark. I don't think (after all of
 our discussion)
 that there's anything remarkable about my code -- it's all as I've
 described
 previously, pretty simple stuff.

 Cheers,

 Ichiro


 On Sun, Feb 16, 2014 at 12:30 AM, Dirk Frederickx 
 dirk.frederi...@gmail.com
  wrote:

  Ichiro,
 
  The issue is *not* client-side related ; actually the moo tools rpc-calls
  are working perfectly; and returning the proper json rpc error codes.
  So mootools or jquery would not make any difference here.
  The problem is the registration of the JSONRPC-Callable classes on the
  server.
 
  Perhaps the registration of your JSON-RPC plugin is happening too late
 for
  the JSONRPC-Manager.sessionCreated() to be picked up ?
  Maybe a logging of the c_gloablObjects in the JSONRPC-Manager may help to
  reveal a timing issues.
 
  Just my .02 cents,
 
 
  Feel free to share your java and js code on the dev mailbox.
 
  dirk
 
 
 
  On Sat, Feb 15, 2014 at 9:19 AM, Ichiro Furusato
  ichiro.furus...@gmail.comwrote:
 
   Hi Dirk,
  
   Yes, you're understanding what I'm trying to do. In addition to the
  plugin
   I've
   also been using a bespoke JSP page with scriptlets to prototype ideas
   quickly,
   as well as a JavaScriptPlugin we wrote years ago as a test bed. (That
  could
   be submitted as a replacement for the JSPWiki plugin of the same name
 if
   people are interested.)
  
   I have tried the 'domready' wrapper you suggested but that didn't seem
 to
   make any difference, and given the amount of time I've now spent on
 this
  I
   have to say that I'm likely going to abandon any AJAX-related work in
 the
   JSPWiki space until it at some point as moved over to jQuery, and
  there's a
   working RPCSamplePlugin. I've just run out of both steam and time.
  
   For now I'll probably try using some other approach than the
  JSONRPCManager
   since I just can't get that to work. Perhaps Apache Wink or some kind
 of
   lightweight RESTful client-server thing, dunno.
  
   Thanks very much for all your help,
  
   Ichiro
  
 

Re: Mobile experience

[Harry Metske]

Jürgen,

I haven' t.
And BTW, the attachment is not there, I think the list does not accept
attachments.

regards,
Harry



On 26 March 2014 23:13, Jürgen Weber juer...@jwi.de wrote:

 Hi,

 has anybody tried to make wiki pages look better on small mobile screens?
 Is there a suitable css?
 The attached screenshot is from Firefox on Android, the menu column and
 top row buttons are a bit small, whereas the second screenshot from
 wikipedia looks good.


 Greetings, Juergen

Re: 2.10.1 release?

[Harry Metske]

+1 on integrating it in the trunk before the release.

regards,
Harry



On 10 April 2014 00:45, Siegfried Goeschl siegfried.goes...@it20one.comwrote:

 Hi folks,

 can we move my GitHub stuff back to the SVN trunk - either before or after
 the release?

 The stuff is mostly finished but having it out-of-sync with SVN is a bit
 dangerous - I will sync GitHub with the latest SVN commits to make the
 merge easier

 Cheers,

 Siegfried Goeschl

 On 07 Apr 2014, at 15:02, Juan Pablo Santos Rodríguez 
 juanpablo.san...@gmail.com wrote:

  Hi!
 
  As noted by several comments at JSPWIKI-817, a 2.10.1 release is needed.
 
  Current trunk not only solves this issue, but also JSPWIKI-831 (Container
  authentication broken), which make a very good couple of reasons to make
  the release. I'd like to also include JSPWIKI-832 and JSPWIKI-822, which
  are two low-hanging fruits, and also JSPWIKI-814 (got it on local,
 attached
  unit tests look good, but I'd like to do some more testing).
 
  If anyone doesn't do it before, I think I'll be able to have them in
 trunk
  in 5 to 10 days, so my question is, sounds reasonable if we wait these
 days
  to get these issues fixed before 2.10.1?
 
 
  br,
  juan pablo
 
 
  On Mon, Apr 7, 2014 at 10:51 PM, Juan Pablo Santos Rodríguez (JIRA) 
  j...@apache.org wrote:
 
 
 [
 
 https://issues.apache.org/jira/browse/JSPWIKI-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13962238#comment-13962238
 ]
 
  Juan Pablo Santos Rodríguez commented on JSPWIKI-817:
  -
 
  Hi!
 
  es_ES translation was also updated at r1569989. As for the release, it
  seems it'll be very welcome, let's follow this up at dev@j.a.o
 
 
  br,
  juan pablo
 
  Install.jsp is broken, and should be more foolproof and provide better
  guidance
 
 
 ---
 
 Key: JSPWIKI-817
 URL: https://issues.apache.org/jira/browse/JSPWIKI-817
 Project: JSPWiki
  Issue Type: Bug
  Components: Core  storage
Affects Versions: 2.10
 Environment: Ubuntu Linux
  Java 7
  Tomcat 7
  JSPWiki 2.10.0
Reporter: Harry Metske
Assignee: Harry Metske
 Fix For: 2.10.1
 
 
  Firing up the JSPWiki/Install.jsp gives the following NPE:
  {noformat}
  Feb 02, 2014 1:59:04 PM org.apache.catalina.core.StandardWrapperValve
  invoke
  SEVERE: Servlet.service() for servlet [jsp] in context with path
 [/wiki]
  threw exception [An exception occurred processing JSP page /Install.jsp
 at
  line 46
  43: WikiSession wikiSession = wikiContext.getWikiSession();
  44:
  45: // Parse the existing properties
  46: installer.parseProperties();
  47: boolean validated = false;
  48: String password = null;
  49: ResourceBundle rb = Preferences.getBundle( wikiContext,
  CoreResources );
  Stacktrace:] with root cause
  java.lang.NullPointerException
   at
 
 org.apache.wiki.util.CommentedProperties.writeProperty(CommentedProperties.java:213)
   at
 
 org.apache.wiki.util.CommentedProperties.put(CommentedProperties.java:116)
   at org.apache.wiki.ui.Installer.parseProperty(Installer.java:320)
   at
 org.apache.wiki.ui.Installer.parseProperties(Installer.java:223)
   at org.apache.jsp.Install_jsp._jspService(Install_jsp.java:122)
   at
  org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
   at
 
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
   at
  org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
   at
  org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
   at
 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
   at
 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
   at
 
 org.apache.wiki.ui.WikiServletFilter.doFilter(WikiServletFilter.java:177)
   at
  org.apache.wiki.ui.WikiJSPFilter.doFilter(WikiJSPFilter.java:121)
   at
 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
   at
 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
   at
 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
   at
 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
   at
 
 org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
   at
 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
   at
 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99

Re: Open Discussion - How to increasing JSPWiki publicity ...

[Harry Metske]

sounds like a good idea to me !


On 11 April 2014 03:42, Glen Mazza glen.ma...@gmail.com wrote:

 One easy way to raise JSPWiki's profile is to provide a page showing all
 the external sites using it.  I created this for Apache Roller: 
 https://cwiki.apache.org/confluence/display/ROLLER/WhoUsesRoller;. To
 find out Roller bloggers, I googled a text string that is usually present
 on Roller's login page (powered by apache roller weblogger version ...).
  If JSPWiki could place a similar, non-obtrusive string on its login page
 (or actually anywhere, doesn't matter) googling on a monthly basis should
 see an increasing number of Wikis that could be added to a WhoUsesJSPWiki
 page.  Seeing all the impressive ways JSPWiki is being used is a ton of
 easy advertising all by itself.

 Glen


 On 4/10/2014 8:54 PM, Siegfried Goeschl wrote:

 Hi folks,

 the question at hand is to increase JSPWiki’s publicity - how can we do
 that? Unfortunately Open Source also consists of lot of advertising
 otherwise no user will ever use it :-)

 * the presentation at ApacheCon 2014 was a start
 * I also presented JSPWiki at my local Java User Group
 * very likely I will do another presentation at the Linux Days in Vienna

 but this only reaches very few people :-(

 So what can we do to get more users?

 * Anyone in the mood to write an article and try to publish it?
 * Are there any conferences were JSPWiki can be easily presented?
 * Any other and better ideas?

 Thanks in advance

 Siegfried Goeschl

Re: Releasing 2.10.1? (was: Re: [jira] [Commented] (JSPWIKI-839) JSP-Wiki - Installation 2.10 is not possible)

[Harry Metske]

+2
 Op 19 mei 2014 22:49 schreef Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com:

 Hi,

 (switching to dev@j.a.o as this e-mail is not that issue specific)

 Before being caught by work, I thought I could incorporate WOAS into trunk
 and release 2.10.1 on a reasonable time frame, my bad.

 Right now, the only stopper for releasing 2.10.1 is the RAT report, which
 is complaining about some files without an AL header, which is
 something fast and easy to solve. I think I'll be able to do it by the
 weekend, but if anyone wants to speed up things, please feel free to
 add them O:-) And after this, let's begin with the 2.10.1 release, so it
 isn't delayed anymore.

 sounds reasonable?


 br,
 juan pablo


 On Mon, May 19, 2014 at 7:22 PM, Harry Metske (JIRA) j...@apache.org
 wrote:

 
  [
 
 https://issues.apache.org/jira/browse/JSPWIKI-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002013#comment-14002013
 ]
 
  Harry Metske commented on JSPWIKI-839:
  --
 
  According to [
 
 https://issues.apache.org/jira/browse/JSPWIKI-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13962238#comment-13962238
 ]
  I expected Juan Pablo to start the release of 2.10.1 somewhere last
 month,
  but I'm assuming he couldn't find the time yet.
 
 
 
   JSP-Wiki - Installation 2.10 is not possible
   
  
   Key: JSPWIKI-839
   URL: https://issues.apache.org/jira/browse/JSPWIKI-839
   Project: JSPWiki
Issue Type: Bug
  Reporter: Momo
  
   Hallo!
   I'am trying to install JSPWIKI 2.10 on a Windows Machine.
   Ist a Win 2008 Server witch Tomcat 8.0.5
   JSPWIKI 2.8 works fine.
   If i try to install jspwiki 2.10 i alwas get this failure:
   HTTP Status 404 - /SIPP/Install.jsp
   type Status report
   message /SIPP/Install.jsp
   description The requested resource is not available.
   I downloaded the .war FIle from here:
   http://www.apache.org/dyn/closer.cgi/jspwiki
   -- 2.10.0 -- binaries/   -- JSPWiki.war
   What are the other files`?
   Is it possible to install JSPWIKI 2.10 on a Windows Machine?
   Thanks!
 
 
 
  --
  This message was sent by Atlassian JIRA
  (v6.2#6252)
 

Re: Releasing 2.10.1? (was: Re: [jira] [Commented] (JSPWIKI-839) JSP-Wiki - Installation 2.10 is not possible)

[Harry Metske]

/jspwiki-war/src/main/styles/haddock/TOCPlugin.less
  /home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/type.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/TableX.Filter.less
  /home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/forms.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Template.SearchBox.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/tables.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Template.Sidebar.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/TableX.Sort.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/prettify.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Viewer.Carousel.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Accordion.less
  /home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Tips.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Template.Edit.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Viewer.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/WeblogPlugin.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Calendar.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Template.Diff.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/RecentChangesPlugin.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Template.Search.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Template.Nav.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Template.Attach.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/ImagePlugin.less
  /home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Tabs.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Columns.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/Category.less
  
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/styles/haddock/CommentBox.less



On 19 May 2014 22:48, Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com wrote:

 Hi,

 (switching to dev@j.a.o as this e-mail is not that issue specific)

 Before being caught by work, I thought I could incorporate WOAS into trunk
 and release 2.10.1 on a reasonable time frame, my bad.

 Right now, the only stopper for releasing 2.10.1 is the RAT report, which
 is complaining about some files without an AL header, which is
 something fast and easy to solve. I think I'll be able to do it by the
 weekend, but if anyone wants to speed up things, please feel free to
 add them O:-) And after this, let's begin with the 2.10.1 release, so it
 isn't delayed anymore.

 sounds reasonable?


 br,
 juan pablo


 On Mon, May 19, 2014 at 7:22 PM, Harry Metske (JIRA) j...@apache.org
 wrote:

 
  [
 
 https://issues.apache.org/jira/browse/JSPWIKI-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002013#comment-14002013
 ]
 
  Harry Metske commented on JSPWIKI-839:
  --
 
  According to [
 
 https://issues.apache.org/jira/browse/JSPWIKI-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13962238#comment-13962238
 ]
  I expected Juan Pablo to start the release of 2.10.1 somewhere last
 month,
  but I'm assuming he couldn't find the time yet.
 
 
 
   JSP-Wiki - Installation 2.10 is not possible
   
  
   Key: JSPWIKI-839
   URL: https://issues.apache.org/jira/browse/JSPWIKI-839
   Project: JSPWiki
Issue Type: Bug
  Reporter: Momo
  
   Hallo!
   I'am trying to install JSPWIKI 2.10 on a Windows Machine.
   Ist a Win 2008 Server witch Tomcat 8.0.5
   JSPWIKI 2.8 works fine.
   If i try to install jspwiki 2.10 i alwas get this failure:
   HTTP Status 404 - /SIPP/Install.jsp
   type Status report
   message /SIPP/Install.jsp
   description The requested resource is not available.
   I downloaded the .war FIle from here:
   http://www.apache.org/dyn/closer.cgi/jspwiki
   -- 2.10.0 -- binaries/   -- JSPWiki.war
   What are the other files`?
   Is it possible to install JSPWIKI 2.10 on a Windows Machine?
   Thanks!
 
 
 
  --
  This message was sent by Atlassian JIRA
  (v6.2#6252)
 

Re: Releasing 2.10.1? (was: Re: [jira] [Commented] (JSPWIKI-839) JSP-Wiki - Installation 2.10 is not possible)

[Harry Metske]

Yes please, go ahead with the commit of the less files.
I am currently looking at the js files...
 Op 20 mei 2014 19:42 schreef Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com:

 Hi,

 with bash, for less files you can do the appropiate magic with (assuming
 none of them contain the AL header):

 $ find . -name *.less -exec sed -i '1s:^:/*\
  *\
  * Licensed to the Apache Software Foundation (ASF) under one\
  * or more contributor license agreements.  See the NOTICE file\
  * distributed with this work for additional information\
  * regarding copyright ownership.  The ASF licenses this file\
  * to you under the Apache License, Version 2.0 (the\
  * License); you may not use this file except in compliance\
  * with the License.  You may obtain a copy of the License at\
  *\
  *   http\://www.apache.org/licenses/LICENSE-2.0\
  *\
  * Unless required by applicable law or agreed to in writing,\
  * software distributed under the License is distributed on an\
  * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\
  * KIND, either express or implied.  See the License for the\
  * specific language governing permissions and limitations\
  * under the License.\
  *\
 */\
 :' {} \;

 (just ran it into my local, if you want I can commit it)

 js files need a closer look, i.e. I recall some of then having the AL
 header, some should be excluded on RAT (f.ex., mootols and prettify should
 have a link to the license inside), but nothing that running that script
 from different subdirectories won't fix..


 br,
 juan pablo


 On Tue, May 20, 2014 at 7:13 PM, Harry Metske harry.met...@gmail.com
 wrote:

  I did a few obvious corrections, but there are loads of other (.js and
  .less) files missing AL headers.
  I will insert the AL headers there too and commit that soon.
 
  here are a couple of examples:
 
 
 
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Category.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Recents.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Findpages.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Prefs.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Group.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Search.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Dynamic-styles.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.Find.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.Font.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.Chars.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.Color.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.Selection.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.Buttons.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/Wiki.Edit.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/Snipe.Sections.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/Wiki.Snips.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/Snipe.Commands.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/UndoRedo.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/Snipe.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/Snipe.Sections.old.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Accesskey.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/String.Extend.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Form.File.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Array.Extend.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Form.MultipleFile.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Textarea.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Cookie.Flags.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Behavior.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Element.Placeholder.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/HighlightQuery.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Color.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Request.File.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Array.NaturalSort.js
 
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Tips.js
 
 
 /home/metskem

Re: Releasing 2.10.1? (was: Re: [jira] [Commented] (JSPWIKI-839) JSP-Wiki - Installation 2.10 is not possible)

[Harry Metske]

after the last commit, we have 3 files left (with MIT license) :
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/lib/mootools-more-1.4.0.1.js
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/lib/prettify4mar13.js
/home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/lib/mootools-core-1.4.5.js

They do have some sort of license text in them, should we exclude those
from RAT ?


On 20 May 2014 20:09, Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com wrote:

 Hi!

 done at r1596342


 br,
 juan pablo


 On Tue, May 20, 2014 at 7:52 PM, Harry Metske harry.met...@gmail.com
 wrote:

  Yes please, go ahead with the commit of the less files.
  I am currently looking at the js files...
   Op 20 mei 2014 19:42 schreef Juan Pablo Santos Rodríguez 
  juanpablo.san...@gmail.com:
 
   Hi,
  
   with bash, for less files you can do the appropiate magic with
 (assuming
   none of them contain the AL header):
  
   $ find . -name *.less -exec sed -i '1s:^:/*\
*\
* Licensed to the Apache Software Foundation (ASF) under one\
* or more contributor license agreements.  See the NOTICE file\
* distributed with this work for additional information\
* regarding copyright ownership.  The ASF licenses this file\
* to you under the Apache License, Version 2.0 (the\
* License); you may not use this file except in compliance\
* with the License.  You may obtain a copy of the License at\
*\
*   http\://www.apache.org/licenses/LICENSE-2.0\
*\
* Unless required by applicable law or agreed to in writing,\
* software distributed under the License is distributed on an\
* AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\
* KIND, either express or implied.  See the License for the\
* specific language governing permissions and limitations\
* under the License.\
*\
   */\
   :' {} \;
  
   (just ran it into my local, if you want I can commit it)
  
   js files need a closer look, i.e. I recall some of then having the AL
   header, some should be excluded on RAT (f.ex., mootols and prettify
  should
   have a link to the license inside), but nothing that running that
 script
   from different subdirectories won't fix..
  
  
   br,
   juan pablo
  
  
   On Tue, May 20, 2014 at 7:13 PM, Harry Metske harry.met...@gmail.com
   wrote:
  
I did a few obvious corrections, but there are loads of other (.js
 and
.less) files missing AL headers.
I will insert the AL headers there too and commit that soon.
   
here are a couple of examples:
   
   
   
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Category.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Recents.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Findpages.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Prefs.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Group.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Search.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki/Dynamic-styles.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.Find.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.Font.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.Chars.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.Color.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.Selection.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/dialog/Dialog.Buttons.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/Wiki.Edit.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/Snipe.Sections.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/Wiki.Snips.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/Snipe.Commands.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/UndoRedo.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/Snipe.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/wiki-edit/Snipe.Sections.old.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Accesskey.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/String.Extend.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend/Form.File.js
   
   
  
 
 /home/metskem/workspace/jspwiki/jspwiki-war/src/main/scripts/moo-extend

Re: Open Discussion - How to increasing JSPWiki publicity ...

[Harry Metske]

Since I am not an administrator in this JSPWiki FB group, can someone
delete this group (or make me administrator, so I can delete it) ?

kind regards,
Harry



On 16 May 2014 07:10, Jürgen Weber juer...@jwi.de wrote:

 +1
 Am 16.05.2014 02:02 schrieb Glen Mazza glen.ma...@gmail.com:

  I'm opposed to this, and would still like to see whatever Facebook page
 we
  presently have taken down/deleted.  Janne is not on the team anymore, per
  his own choice, and he shouldn't be creating additional social media
 sites
  that are just going to end up getting neglected and hence making the
  project look bad as a result.  We need fewer but better maintained sites,
  not more but poorly maintained ones.
 
  Glen
 
  On 05/13/2014 05:01 AM, Dave Koelmeyer wrote:
 
 
  On 13/04/14 19:17, Janne Jalkanen wrote:
 
  Gave you admin access on the FB group :-)
 
  /Janne
 
  On 13 Apr 2014, at 06:31 , Dave Koelmeyer
 dave.koelmeyer@davekoelmeyer.
  co.nz wrote:
 
 
  Hi Janne/All,
 
  A belated thanks for this. I believe since that group was created
  Facebook has focused far more on Pages as a business or
  organisation-specific promotion/marketing tool (cf.
  https://www.facebook.com/notes/324706977130).
 
  Would we please be able to create a fresh Facebook Page for JSPWiki? And
  do we need sign-off from Apache for this?
 
  Cheers,
  Dave
 
 
   On 4/10/2014 8:54 PM, Siegfried Goeschl wrote: Hi folks,
 
  the question at hand is to increase JSPWiki’s publicity - how can we
 do
  that? Unfortunately Open Source also consists of lot of advertising
  otherwise no user will ever use it :-)
 
  Really ramping up activity on social networks would be a good idea,
  Facebook and Twitter specifically. There is a Facebook page with a
 whopping
  four members, and activity on there is all but dead. Happy to make a
 time
  commitment here to start posting fresh content.
 
  Cheers,
  Dave
 
  --
  Dave Koelmeyer
  http://blog.davekoelmeyer.co.nz
 
 
 
 
 
 

Re: svn commit: r1597105 - in /jspwiki/trunk: ./ jspwiki-it-tests/ jspwiki-it-tests/jspwiki-it-test-cma-jdbc/ jspwiki-it-tests/jspwiki-it-test-cma/ jspwiki-it-tests/jspwiki-it-test-custom-absolute-url

[Harry Metske]

In that case, I would say go on wit 2.10.1 and drop JSPWIKI-841 for 2.10.2

regards,
Harry
Op 23 mei 2014 20:57 schreef Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com:

 Hi Harry,

 haven't performed the mvn release:perform step yet, so we could still
 rollback the release without manually reverting all the files. My intention
 was to apply the patch at JSPWIKI-841 after releasing 2.10.1 (for 2.10.2),
 as I didn't want to delay the release anymore. Also, to make JSPWIKI-841
 surface requires knowing about a property which hasn't been in
 jspwiki.properties since at least 2.4.87, which is unlikely (although not
 impossible, as demonstrated by that JIRA itself), so it didn't seem a
 showstopper for me.

 That said, we can still rollback the release, apply the patch and rearrange
 a new release; shouldn't be more than a couple of hours, so if you think is
 worth including, please confirm and I'll push the patch into 2.10.1


 thx + br,
 juan pablo


 On Fri, May 23, 2014 at 6:34 PM, Harry Metske harry.met...@gmail.com
 wrote:

  JP,
 
  shouldn't we first commit JSPWIKI-841 (container managed security not
  working) ?
 
  kind regards,
  Harry
 
 
 
  On 23 May 2014 16:30, juanpa...@apache.org wrote:
 
   Author: juanpablo
   Date: Fri May 23 14:30:03 2014
   New Revision: 1597105
  
   URL: http://svn.apache.org/r1597105
   Log:
   [maven-release-plugin] prepare for next development iteration
  
   Modified:
   jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-cma-jdbc/pom.xml
   jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-cma/pom.xml
  
  
 
 jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-custom-absolute-urls/pom.xml
   jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-custom-jdbc/pom.xml
   jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-custom/pom.xml
   jspwiki/trunk/jspwiki-it-tests/jspwiki-selenium-tests/pom.xml
   jspwiki/trunk/jspwiki-it-tests/pom.xml
   jspwiki/trunk/jspwiki-war/pom.xml
   jspwiki/trunk/jspwiki-wikipages/de/pom.xml
   jspwiki/trunk/jspwiki-wikipages/en/pom.xml
   jspwiki/trunk/jspwiki-wikipages/es/pom.xml
   jspwiki/trunk/jspwiki-wikipages/fi/pom.xml
   jspwiki/trunk/jspwiki-wikipages/fr/pom.xml
   jspwiki/trunk/jspwiki-wikipages/it/pom.xml
   jspwiki/trunk/jspwiki-wikipages/nl/pom.xml
   jspwiki/trunk/jspwiki-wikipages/pom.xml
   jspwiki/trunk/jspwiki-wikipages/pt_BR/pom.xml
   jspwiki/trunk/jspwiki-wikipages/zh_CN/pom.xml
   jspwiki/trunk/pom.xml
  
   Modified:
 jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-cma-jdbc/pom.xml
   URL:
  
 
 http://svn.apache.org/viewvc/jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-cma-jdbc/pom.xml?rev=1597105r1=1597104r2=1597105view=diff
  
  
 
 ==
   --- jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-cma-jdbc/pom.xml
   (original)
   +++ jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-cma-jdbc/pom.xml Fri
   May 23 14:30:03 2014
   @@ -22,7 +22,7 @@
  parent !-- this enables tests reuse [1/3] --
groupIdorg.apache.jspwiki.it/groupId
artifactIdjspwiki-it-builder/artifactId
   -version2.10.1/version
   +version2.10.2-SNAPSHOT/version
  /parent
  
  !-- Container Managed Authentication using JDBC instead of XML
 files
   for user and group info --
  
   Modified: jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-cma/pom.xml
   URL:
  
 
 http://svn.apache.org/viewvc/jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-cma/pom.xml?rev=1597105r1=1597104r2=1597105view=diff
  
  
 
 ==
   --- jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-cma/pom.xml
 (original)
   +++ jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-cma/pom.xml Fri May
 23
   14:30:03 2014
   @@ -22,7 +22,7 @@
  parent !-- this enables tests reuse [1/3] --
groupIdorg.apache.jspwiki.it/groupId
artifactIdjspwiki-it-builder/artifactId
   -version2.10.1/version
   +version2.10.2-SNAPSHOT/version
  /parent
  
  !-- Container Managed Authentication --
  
   Modified:
  
 
 jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-custom-absolute-urls/pom.xml
   URL:
  
 
 http://svn.apache.org/viewvc/jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-custom-absolute-urls/pom.xml?rev=1597105r1=1597104r2=1597105view=diff
  
  
 
 ==
   ---
  
 
 jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-custom-absolute-urls/pom.xml
   (original)
   +++
  
 
 jspwiki/trunk/jspwiki-it-tests/jspwiki-it-test-custom-absolute-urls/pom.xml
   Fri May 23 14:30:03 2014
   @@ -22,7 +22,7 @@
  parent !-- this enables tests reuse [1/3] --
groupIdorg.apache.jspwiki.it/groupId
artifactIdjspwiki-it-builder/artifactId
   -version2.10.1/version
   +version2.10.2-SNAPSHOT/version
  /parent
  
  artifactIdjspwiki-it-test-custom-absolute-urls

Re: steps to get jspwiki-2.10.1-rc1 running with container managed aut

[Harry Metske]

The way JSPWiki currently works is optimized for a setup where you have :
* one jspwiki instance in tomcat
* write access to tomcat's lib directory

If you miss one of these, you have to do something withing the exploded war
to get the properties file on the classpath.
In that case I would recommend to put the jspwiki-custom.properties in the
./webapp/JSPWiki/WEB-INF/classes folder. That way it is easy
visible/editable (as opposed to hiding it in the JSPWiki.jar). I just did
a minor correction on the wiki for that.

kind regards,
Harry



On 26 May 2014 16:29, Glen Mazza glen.ma...@gmail.com wrote:

 Hello Jürgen, while it will work, I recommend against placing the
 jspwiki-custom.properties file within the WAR.  Just place it in the Tomcat
 lib folder, and JSPWiki will automatically pick it up and use its values
 to override whatever is in jspwiki.properties.  (If you're inclined to
 place that file in the WAR you might as well directly edit the
 jspwiki.properties instead.)  This way you can upgrade the WAR as often as
 you want, and the values from the Tomcat lib custom.properties will
 automatically carry over.

 Also, remember your jspwiki-custom.properties file only has to have the
 (relatively few) values that you are overriding in jspwiki.properties, the
 latter's defaults will take over otherwise.

 I'll try to update our Wiki for this -- https://jspwiki-wiki.apache.
 org/Wiki.jsp?page=Documentation, right now for some reason I haven't
 write access.  :/

 Finally, in our JSPWiki source code we have an integrated test for CMA (
 http://svn.apache.org/viewvc/jspwiki/trunk/jspwiki-it-tests/), perhaps
 its settings there will be of help for you.

 Regards,
 Glen



 On 05/26/2014 05:24 AM, Jürgen Weber wrote:

 My steps to get jspwiki-2.10.1-rc1 running with container managed auth:

 explode the war to /projekte/jspwiki-2.10.1-rc1/JSPWiki

 add
 /projekte/apache-tomcat-8.0.8/conf/Catalina/localhost/JSPWiki.xml

 Context path=/JSPWiki
 docBase=/projekte/jspwiki-2.10.1-rc1/JSPWiki
 /Context

 change
 /projekte/apache-tomcat-8.0.8/conf/server.xml

role rolename=Authenticated/
role rolename=Admin/

user username=tomcat password=tomcat roles=tomcat, Admin,
 Authenticated/

 in web.xml enabled CONTAINER-MANAGED AUTHENTICATION  AUTHORIZATION

 and

 removed all annoying and useless (JSPWIKI-212):
 user-data-constraint
 transport-guaranteeCONFIDENTIAL/transport-guarantee
 /user-data-constraint


 There should be a

 jspwiki-custom.properties.template in the war.

 I used this for /projekte/apache-tomcat-8.0.8/
 lib/jspwiki-custom.properties

 jspwiki.applicationName = JSPWiki
 jspwiki.baseURL=http://linda:8080/JSPWiki
 jspwiki.urlConstructor = ShortViewURLConstructor
 jspwiki.pageProvider = VersioningFileProvider
 jspwiki.fileSystemProvider.pageDir = /projekte/jspwiki-2.10.1-rc1/
 wikipages
 jspwiki.basicAttachmentProvider.storageDir =
 /projekte/jspwiki-2.10.1-rc1/wikipages
 #
 log4j.appender.FileLog = org.apache.log4j.RollingFileAppender
 log4j.appender.FileLog.MaxFileSize= 10MB
 log4j.appender.FileLog.MaxBackupIndex = 14
 log4j.appender.FileLog.File = /projekte/jspwiki-2.10.1-rc1/jspwiki.log

jspwiki-vm is down

[Harry Metske]

Hello,

I just created https://issues.apache.org/jira/browse/INFRA-8103 because our
Virtual Machine running our wiki (https://jspwiki-wiki.apache.org) does not
respond anymore.

kind regards,
HArry

Re: Wiki spammed

[Harry Metske]

I would like to stick with the setup we currently have, meaning:
* stick with one wiki, no additional wikis, not for docu, and sure not for
a sandbox
* I am also fine with the level of freedom we currently have on the wiki,
as JP says, the spam is almost nothing, I dont have more then 5 minutes a
week doing gardening.
* can't comment on the licensing issues.

People should be able to have their own pages, as long as it is not just
for testing ( I deleted a few of those last year).
I dont understand what is meant with the heavy commits

Kind regards,
Harry
 Op 21 aug. 2014 18:39 schreef Glen Mazza glen.ma...@gmail.com:

 We really don't need to be discussing marketing with Juergen, as he's not
 yet on the team.  As for his comment: As for playing with the Wiki, there
 should be a Sandbox page, which would be world writeable and which should
 be deleted by a batch job every hour or so, he's just being generous with
 other people's time and responsibilities (nobody, after all, is stopping
 him from running his own public JSPWiki sandbox.)  The team decides whether
 we want a Sandbox, and we've already determined earlier we don't want to
 manage it and deal with the responsibilities and headaches of people
 uploading illegal or privacy-infringing content, that there is better use
 of our limited time on the project, and that people can view our own Wiki
 instance as well as test JSPWiki locally to confirm if they want it.

 Whether or not we have a sandbox or personal pages is an opportunity cost,
 marketing and legal matter that is not a concern of users, they don't need
 to get into that.  Whether or not JSPWiki works, and how it works is one
 thing for users to comment on, but marketing is not a user concern.

 Nonetheless I thank Juergen for noting the heavy commits recently
 (although from the link below I'm not sure what is the spam that he's
 talking about, it looks like normal commits), as it allowed me to notice
 someone attaching non-Apache licensed material (a Dilbert cartoon).

 Glen


 On 08/21/2014 11:43 AM, Juan Pablo Santos Rodríguez wrote:

 [Switching to dev, so everyone can hop in]

 As for now, we show an advice on the footer, stating that the content is
 AL; maybe we should reword that so it's made clearer, as it's seen on
 every
 page. If don't state that the content is AL there, I could upload my own
 plugin without knowing or linking the ContributedPlugins page and I could
 argue that the copyright notice wasn't visible.

 Regarding personal pages, right now, I'd leave them, as the
 signal-to-noise
 ratio is still high, and those pages link, or contain valuable
 info/contributed plugins. If it worsens I'd be would be in favour of being
 stricter granting rw access, but for now it seems to me ok, as a large %
 of
 those personal/sandbox pages are ending up in being proper contributions.
 In any case, I'm eager to hear what others think about this, and won't
 mind
 to change my opinion if enough people think we should be stricter / would
 be nice to have a sandbox wiki / etc.


 br,
 juan pablo




 On Wed, Aug 20, 2014 at 10:22 AM, Jürgen Weber juer...@jwi.de wrote:

  Hi Juan Pablo,

 actually I think personal pages at an apache.org site is not a good
 idea.
 We should ask Glen about this. Especially reading what he wrote here:
 https://jspwiki-wiki.apache.org/Diff.jsp?page=
 ContributedPluginsr1=13r2=12

 One could even be more strict with added content and require that it go
 via a JIRA attachment..

 As for playing with the Wiki, there should be a Sandbox page, which would
 be world writeable and which should be deleted by a batch job every hour
 or
 so.

 But we should discuss this, either via a Jira or on dev.

 Greetings, Jürgen
 Am 19.08.2014 17:27 schrieb Juan Pablo Santos Rodríguez 
 juanpablo.san...@gmail.com:

 Hi Jürgen,

 thanks for looking into this! I've checked to see what type of content
 is
 being posted, but they seem to me as personal/sandbox pages, created
 from
 different IPs, which was somewhat usual/normal when hosted at
 www.jspwiki.org. Do you think the wiki should stick to documentation
 (or
 perhaps we should use another wiki instance to host this kind of
 pages)? As
 it was difficult to get the VM and wiki running, we sticked to one
 instance, but we could set up for another redirection if needed
 (however, I
 feel that this kind of decision should be made at dev@)

 For now, let's wait to see how they evolve, or if new spam-suspicious
 pages are created. If they come to be spam, we could follow the same
 policy
 followed by the infra guys, that is, grant access to anyone who asks on
 dev@j.a.o, for instance, or whatever we decide at dev@..


 cheers,
 juan pablo


 On Tue, Aug 19, 2014 at 10:43 AM, Jürgen Weber juer...@jwi.de wrote:

  Hi Juan Pablo,

 looks like the jspwiki-wiki.apache.org is beeing spammed:
 https://jspwiki-wiki.apache.org/Wiki.jsp?page=RecentChanges

 I guess new users should be closed, which is a pity.

 How could one restrict the 

Re: [ANNOUNCE] Siegfried Goeschl as new JSPWiki PMC/Committer

[Harry Metske]

Siegfried,

Welcome to the team !

Kind regards,
Harry
 Op 21 aug. 2014 19:51 schreef Siegfried Goeschl 
siegfried.goes...@it20one.com:

 Hi folks,

 I think it is good time to finally introduce myself :-)

 * Living in Vienna, Austria
 * Doing Java backend development
 * Started my ASF career as Apache Turbine committer in 2004
 * Came across JSPWiki when meeting Jane Jalkanen during an ApacheCon
 Europe in 2008
 * Searched for a portable Java-based Wiki and tinkered with JSPWiki to
 create a “Wiki On A Stick” in 2010
 * Became a mentor during the final stage of the incubation

 Cheers,

 Siegfried Goeschl


 On 21 Aug 2014, at 17:53, Juan Pablo Santos Rodríguez 
 juanpablo.san...@gmail.com wrote:

  Hi all,
 
  we are happy to announce that we've voted to invite Siegfried Goeschl as
  PMC and committer, and he has gladly accepted, so welcome Siegfried!
 
 
  cheers,
  juan pablo

Re: Wiki spammed

[Harry Metske]

Juergen,

I agree with you on the sandbox idea, but that simply takes too much time
and attention, so that's why we decided not to do it.
Having the apache infra team gear up the infrastructure for the current
wiki took us a lot of time and attention, and we dont want to bother them
and ourselves with that again.

About spamming, I think the level of noise on the wiki is currently that
low that I even don't want to call it spam. Every now and then I delete
pages (cost me 5 minutes a week) of what I think is testing/spam (that's
why you don't see them anymore on RecentChanges).

So basically I like to stick with the current setup.
We surely do appreciate your ideas and suggestions, so keep doing that !

kind regards,
Harry


On 22 August 2014 08:26, Jürgen Weber juer...@jwi.de wrote:

 Hi,

 I take the freedom to write on this list, even if I am not member of the
 JSPWiki team (actually I do not know the definition of JSPWiki team).

 I have not the time to code a lot, but I'd like to add my ideas. If you
 think this is not good, then please do remove the following from
 https://jspwiki-wiki.apache.org/Wiki.jsp?page=Getting%20Involved

 JSPWiki needs your help! You don't need to be a software developer to help
 -- we also need people to help with documentation, coding, usability and
 graphic design, wiki gardening, organizing volunteers, validating and
 managing bugs and ideas etc. The point really is that despite your skill
 levels at coding or the time you can afford to put into helping us, there's
 always something you can do!

 As for the content of the discussion, I was not referring to David's
 content but to some other pages which do no more appear on RecentChanges.

 I still do not think that it is a good idea to open an apache.org hosted
 wiki for arbitrary content.

 Glen, if you do, please do install an instance of Apache Roller at
 apache.org and open it for the world to blog.

 Which ones of http://wiki.apache.org/general/ let you write without an
 account? As an example check the Tomcat Wiki and try to open an account:
 Unknown action newaccount.

 Greetings, Juergen
 Am 21.08.2014 23:26 schrieb David Vittor dvit...@gmail.com:

  Hi All,
 
  Sorry about the spamming, I think that might have been me, trying to
 update
  my page David Vittor.
 
  I was putting a whole bunch of links to resource pages, that might be
  useful for various plugins, and kept getting the SpamFilter message.
 
  I've stopped this now, so this should stop (if I was the culprit).
 
  I'll work on setting up my own wiki shortly, so that I can actually
 upload
  my own plugins into it, and showcase them. This will reduce the changes I
  need to make to the current public jspwiki.
 
  Although I do like the idea of a sandbox wiki, especially for new guys
 like
  me.
 
  Kind regards,
  David V
 
 
  On Fri, Aug 22, 2014 at 5:22 AM, Glen Mazza glen.ma...@gmail.com
 wrote:
 
   heavy = frequent.  Not a bad thing at all, providing it's not spam. I
   didn't see any obvious spam from the commit list, so wasn't sure what
   Juergen was concerned about.
  
   I don't have a problem with people pages either.  Ichiro's is
  particularly
   good.
  
   Glen
  
  
   On 08/21/2014 03:18 PM, Harry Metske wrote:
  
   I would like to stick with the setup we currently have, meaning:
   * stick with one wiki, no additional wikis, not for docu, and sure not
  for
   a sandbox
   * I am also fine with the level of freedom we currently have on the
   wiki,
   as JP says, the spam is almost nothing, I dont have more then 5
 minutes
  a
   week doing gardening.
   * can't comment on the licensing issues.
  
   People should be able to have their own pages, as long as it is not
 just
   for testing ( I deleted a few of those last year).
   I dont understand what is meant with the heavy commits
  
   Kind regards,
   Harry
 Op 21 aug. 2014 18:39 schreef Glen Mazza glen.ma...@gmail.com:
  
We really don't need to be discussing marketing with Juergen, as he's
  not
   yet on the team.  As for his comment: As for playing with the Wiki,
   there
   should be a Sandbox page, which would be world writeable and which
  should
   be deleted by a batch job every hour or so, he's just being generous
   with
   other people's time and responsibilities (nobody, after all, is
  stopping
   him from running his own public JSPWiki sandbox.)  The team decides
   whether
   we want a Sandbox, and we've already determined earlier we don't want
  to
   manage it and deal with the responsibilities and headaches of people
   uploading illegal or privacy-infringing content, that there is better
  use
   of our limited time on the project, and that people can view our own
  Wiki
   instance as well as test JSPWiki locally to confirm if they want it.
  
   Whether or not we have a sandbox or personal pages is an opportunity
   cost,
   marketing and legal matter that is not a concern of users, they don't
   need
   to get into that.  Whether or not JSPWiki

Re: Please remove the Dilbert cartoon (Re: Enhancing FileSystemProvider to save page attributes)

[Harry Metske]

you're right (twice :-) )


On 25 August 2014 05:31, David Vittor dvit...@gmail.com wrote:

 Thanks Harry,

 Btw I think only admins can do this, as the delete button does not appear
 for me.

 But it looks like you have done this for me.

 Cheers,
 David V



 On Fri, Aug 22, 2014 at 4:51 PM, Harry Metske harry.met...@gmail.com
 wrote:

  David,
 
  to remove attachments, you first have to login, then go to the Attachment
  tab of the page, there is now a delete button.
 
  regards,
  Harry
 
 
  On 21 August 2014 23:17, David Vittor dvit...@gmail.com wrote:
 
   Hi Glen,
  
   Thanks for pointing this out. I wan't even thinking about copyright at
  the
   time I posted it. I have now removed the image from the page.
  
   Btw - is there a way to remove attachments? I could not seem to find
  this?
  
   Kind regards,
   David V
  
  
  
   On Fri, Aug 22, 2014 at 2:05 AM, Glen Mazza glen.ma...@gmail.com
  wrote:
  
David, you have what appears to be a copyright-infringing cartoon on
  the
JSPWiki page:
   https://jspwiki-wiki.apache.org/Wiki.jsp?page=GoComicPlugin.
Can you remove that please?  It isn't needed to demonstrate your
  plugin.
Please do not post anything copyrighted, even if it's funny.
   
Glen
   
On 08/21/2014 01:15 AM, David Vittor wrote:
   
Hi devs,
   
After analysing the source code, and with a few ideas for plugins,
  I've
raised a new JIRA request, regarding saving extra properties to the
provider:
https://issues.apache.org/jira/browse/JSPWIKI-856
   
If anyone is interested, please feel free to comment. Otherwise I
 will
   go
with option 3.
   
Also is there anything I need to do be able to check in SVN changes?
  Do
   I
need an account created?
   
Thanks.
   
   
   
  
 

Fwd: Announcing the new Powered By Apache logo

[Harry Metske]

What about replacing our old logo with this new style ASF logo :
http://apache.org/foundation/press/kit/poweredBy/pb-jspwiki.jpg

regards,
Harry


-- Forwarded message --
From: Sally Khudairi s...@apache.org
Date: 1 October 2014 18:32
Subject: Announcing the new Powered By Apache logo
To: ASF Marketing  Publicity pr...@apache.org


[re-sending due to the revised rules re: emailing pmcs@]

Hello Apache PMCs --


It's my pleasure to share that that we have a new Powered By Apache logo
available at http://apache.org/foundation/press/kit/


Kindly note that whilst we have created logos for many TLPs, not all have
been included. I have asked our design partners (HotWax Media, friends of
Apache OFBiz) to see if they can complete the full set of TLPs, but we need
to be patient, as they are donating their services.


Should you need a logo for your project in the meantime, there is a
template that you can use to create your own.


I have also requested high-res versions of the template logo in both vector
and .eps formats. I'll notify you when they are available.


We encourage all projects to use the logos and to invite your communities
to do so as well under the guidelines provided. Thanks in advance for
helping spread the word!


As always, feel free to drop me a note if you need anything.


Thanks,
Sally


= = = = =
vox +1 617 921 8656
skype sallykhudairi

Re: [DRAFT] Status Report for the Apache JSPWiki project - January 2015

[Harry Metske]

+1
 Op 14 jan. 2015 14:19 schreef Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com:

 Hi all,

 below is a draft of the board's status report, meant to be sent tonight.
 Any correction, suggestions, etc. are very welcome (apologies on advance
 for having so little time to review, usually there's an automated monthly
 reminder sent by email, which hasn't been sent this month, and as a
 consequence of that I've been caught up..)


 best regards,
 juan pablo

 ---

 == Anything the board should be aware of?
 There are no Board-level issues at this time.

 == Releases / Development
 Last release, 2.10.1, on 29th May, 2014

 Regarding development, this period involved 7 JIRAs solved, most
 notable of them Wiki On a Stick functionality being merged into
 trunk.

 == Community
 Last Committer: David Vittor (dvittor), on 23rd Dec, 2014
 Last PMC: David Vittor (dvittor), on 23rd Dec, 2014

 This quarter we had another decrease on activity on MLs, with ~20
 messages per month at dev@j.a.o, when compared to previous period
 (~50), and user@j.a.o also going back to ~4 messages per month (average
 of 10 on last period). Questions are being answered, though.

 88 (=) people subscribed to dev@j.a.o, 172 (-5) people subscribed at
 user@j.a.o

Re: Old versions of the Wiki

[Harry Metske]

David,

there was a time when JSPWiki was not yet a top level Apache project, we
have been incubating for a long period (I think 3 years).
From that time period it is best to use the tags indeed.
When we became a top level project, we starting making official releases,
you can find the download links to these releases on our wiki (
https://jspwiki-wiki.apache.org/) (second link top left). These also
include binaries (for convenience only).

kind regards,
Harry


On 21 January 2015 at 13:40, David Vittor dvit...@gmail.com wrote:

 Hi Devs,

 How do I get access to old versions of the wiki?

 I've noticed there are SVN tags for the historic versions 1.4 to 2.9.1:
 http://svn.apache.org/repos/asf/jspwiki/tags/

 And then there are branches also, but not sure what these were designed
 for:
 http://svn.apache.org/repos/asf/jspwiki/branches/

 Is the best way to just check out a tag and build the source? Are there
 binary distributions available? Also do we have the source versions from
 2.9.1 to 2.10.1?

 Cheers,
 David V

JSPWiki in a docker container

[Harry Metske]

Folks,

If you are interested in running JSPWiki in a docker container, I
experimented somewhat with it and documented it at :
https://jspwiki-wiki.apache.org/Wiki.jsp?page=Docker

Let me know what you think.

kind regards,
Harry

updates jspwiki-wiki.apache.org

[Harry Metske]

Folks,

I took the liberty of updating a couple of things on jspwiki-wiki.apache.org
:

* apply the latest Linux updates
* deploy the latest JSPWiki (2.10.2-svn-14), fixing JSPWIKI-876
* configure the CleanBlue skin as the default skin

If you feel this is a bit too bleeding edge, let me know, the last 2 can be
reverted if necessary.

kind regards,
Harry

Re: [DRAFT] 04/2015 Board's report

[Harry Metske]

+1

On 8 April 2015 at 14:44, David Vittor dvit...@gmail.com wrote:

 Looks good to me.
 On 08/04/2015 9:57 PM, Juan Pablo Santos Rodríguez 
 juanpablo.san...@gmail.com wrote:

  Hi all,
 
  below is a draft for this quarter's Board report. I intend to put it on
 SVN
  this afternoon/tonight and send it @board 24h later, so any review,
  comment, etc we'll be most welcome
 
 
  thanks + br,
  juan pablo
 
  
  Report from the Apache JSPWiki project
 
  ## Description:
 
 A feature-rich and extensible WikiWiki engine built around the
 standard
  J2EE components (Java, servlets, JSP).
 
  ## Activity:
 
   - Again, slow pace of development, including (but not limited to) some
 interesting functionalities committed into trunk:
 * Portable builds of JSPWiki.
 * Complete rewrite of AJAX functionality.
 * JSPWiki configurable via environment variables, which allows easy
   dockerization.
 
   - Few questions at user@j.a.o, with their follow-ups, with dev@j.a.o
  mostly
 containing JIRA notifications.
 
  ## Issues:
 
   - there are no issues requiring board attention at this time.
 
  ## PMC/Committership changes:
 
   - Currently 15 committers and 10 PMC members in the project.
   - David Vittor was added to the PMC on Thu Jan 22 2015.
   - Last committer addition was David Vittor at Fri Jan 02 2015.
   - Glen Mazza resigned from PMC on 31/03/2015, we all thank him for his
 service.
 
  ## Releases:
 
   - Last release was 2.10.1 on Thu May 29 2014.
 
  ## Mailing list activity:
 
   - dev@jspwiki.apache.org:
  - 86 subscribers (down -2 in the last 3 months):
  - 127 emails sent to list (60 in previous quarter).
 
   - u...@jspwiki.apache.org:
  - 173 subscribers (up 1 in the last 3 months):
  - 29 emails sent to list (14 in previous quarter).
 
  ## JIRA activity:
 
   - 5 JIRA tickets created in the last 3 months.
   - 16 JIRA tickets closed/resolved in the last 3 months.
 

Re: 2.10.2? (was: Re: Introducing the PicoContainer for Dependency Injection)

[Harry Metske]

Fully agree on a new release JP !

kind regards,
Harry
 Op 23 jun. 2015 18:02 schreef Juan Pablo Santos Rodríguez 
juanpablo.san...@gmail.com:

 Hi all,

 as Dave noted below, it would be nice to have a release. Furthermore, since
 2.10.1 we have in trunk
 - support to run JSPWiki on dockerized containers
 - complete rewrite of ajax functionality
 - portable binaries

 not only all of these are interesting enough they could merit a release on
 their own, there are also a couple of fixes which have recently hit the
 user list, so it seems like a very good time to proceed with 2.10.2
 release.

 thoughts?


 br,
 juan pablo



 On Tue, Jun 23, 2015 at 2:06 PM, David (spindift) demer...@spindrift.com
 wrote:

  If you're planning on making a large-ish refactor, it would be nice to
  have an official release prior to introducing the changes. That would
  consolidate the updates-to-date into a new official baseline.
 
  Just a thought...
DaveE
 
 
  On 6/23/2015 7:47 AM, David Vittor wrote:
 
  Hi All,
 
  I've decided to remove this from trunk, as I will be unavailable to
  support this for a few weeks.
 
  I've reverted the trunk and checked in the changes to a Branch:
 
 https://svn.apache.org/repos/asf/jspwiki/branches/JSPWIKI_2_10_PICO_BRANCH
 
  I've also attached here a pico.patch in case someone wants to test this
  against their version of trunk source. Apply the patch on the current
  version 2.10.2-svn-17.
 
  Let me know your thoughts if you do get to test this, and I'll see if I
  can merge this into the trunk, when I have more time.
 
  Kind regards,
  David V
 
 
  On Tue, Jun 23, 2015 at 9:09 PM, David Vittor dvit...@gmail.com
 mailto:
  dvit...@gmail.com wrote:
 
  Hi Devs,
 
  Following close on the heels of the Haddock template rewrite, I've
  released 2.10.2-svn-18 - a small rewrite of the core WikiEngine.
 
  I've been doing a some research into Dependency Injection, I've
  decided that for JSPWiki, I think the best framework would be
  PicoContainer.
  http://picocontainer.com/
 
  This change will take a long time to complete, but I've started by
  adding it to the pom.xml, changing the ClassUtil class to create
  and list all the components (InternalModule), and changing these
  modules (SearchManager, AdminBeanManager, WorkflowManager,
  DefaultFitlerManager, etc) to have empty constructors, and a
  method called initialize( WikiEngine, Properties ).
 
  Just the above change took ages to get right, but now all test
  cases pass, and I've played with it in my dev environment and
  seems like everything works.
 
  I hope now that the core is in place, we can slowly start making
  changes to actually use the PicoContainer functionality for
  dynamic component injection.
 
  I have made a trade off however. Currently the file
  ini/classmappings.xml is no longer valid, and the core classes
  are hard coded inside ClassUtil.
 
  Let me know if anyone has any thoughts on this.
 
  Kind regards,
  David V
 
 
 
 

Re: Haddock template and bugs

[Harry Metske]

I did some testing too, works very well, could not find any real bugs, and
it looks good.
I noticed 2 things (not sure if related to the template though) :

1) the page author ( in many cases) consists of 2 IP addresses , see for
example http://digitalspider.com.au/testwiki/Wiki.jsp?page=Authortest
(created with an empty profile).

2) Is it possible to reduce the second blue area at the top (containing
pagetitle and breadcrumbtrail), can you sort of combine it into the first
blue area containing the jspwiki logo, so that the page title and
breadcrumbs appear right of the jspwiki logo?

thanks for all the work!

kind regards,
Harry


On 29 July 2015 at 16:32, David Vittor dvit...@gmail.com wrote:

 Hi All,

 If anyone is interested in doing some more testing on the haddock template,
 I've updated my wiki to use JSPWiki v2.10.2-svn-28
 http://www.digitalspider.com.au/testwiki/

 Note: Dirk I've fixed my deployment process, where I was using an old
 version of haddock.js. This should now be functioning correctly.

 Cheers,
 David V


 On Tue, Jun 30, 2015 at 1:08 PM, David Vittor dvit...@gmail.com wrote:

  Link is here:
  http://www.digitalspider.com.au/testwiki/
 
 
  On Tue, Jun 30, 2015 at 1:07 PM, David Vittor dvit...@gmail.com wrote:
 
  Hi Dirk,
 
  I've managed to update the wiki now so you can test it here. Sorry for
  the delay.
 
 
  On Wed, Jun 24, 2015 at 4:30 AM, Dirk Frederickx 
  dirk.frederi...@gmail.com wrote:
 
 
  Hi David,
 
 
  Would it be possible to refresh  digital spider.com.au/testwiki with
  the latest  Haddock template ?
 
  It would be really helpful to help testing the template on more
 browsers
  platforms.
 
 
  dirk
 
  -- Forwarded message --
  From: Dirk Frederickx dirk.frederi...@gmail.com
  Date: Mon, Jun 22, 2015 at 10:42 PM
  Subject: Re: Haddock template and bugs
  To: u...@jspwiki.apache.org
 
 
  Dave, all,
 
  I just posted a large update of the HADDOCK template. (2.10.2-svn-17)
  It stabilises the plain editor, and has many UI improvements.  (more
  detail in change notes)
 
  The HADDOCK template is now close to completion, but needs further
  hardening.
  (group related JSPs still need to be done ;  and login/preferences
 needs
  some more tweaking)
 
  I expect to post more documentation during the coming weeks.
 
 
  br,
 dirk
 
 
 
  On Wed, May 27, 2015 at 9:57 AM, Dave Koelmeyer 
  dave.koelme...@davekoelmeyer.co.nz wrote:
 
 
 
  On 27/05/15 09:13, Dirk Frederickx wrote:
 
  Dave,
 
  Yes, whenever HADDOCK gets more stabilised it's a candidate to become
  the
  new default.
  Feedback is much appreciated !  -- plse file your bugs in Jira
 
 
  Thanks, and will do :)
 
 
  --
  Dave Koelmeyer
  http://blog.davekoelmeyer.co.nz
 
 
 
 
 
 

Re: svn commit: r1689770 - /jspwiki/board/2015-07.txt

[Harry Metske]

+1
Op 8 jul. 2015 01:06 schreef juanpa...@apache.org:

 Author: juanpablo
 Date: Tue Jul  7 23:06:06 2015
 New Revision: 1689770

 URL: http://svn.apache.org/r1689770
 Log:
 Draft Report for 2015/07

 Added:
 jspwiki/board/2015-07.txt

 Added: jspwiki/board/2015-07.txt
 URL:
 http://svn.apache.org/viewvc/jspwiki/board/2015-07.txt?rev=1689770view=auto

 ==
 --- jspwiki/board/2015-07.txt (added)
 +++ jspwiki/board/2015-07.txt Tue Jul  7 23:06:06 2015
 @@ -0,0 +1,43 @@
 +Report from the Apache JSPWiki committee
 +
 +## Description:
 +   A feature-rich and extensible WikiWiki engine built around the standard
 +J2EE components (Java, servlets, JSP).
 +
 +## Activity:
 + - Started conversations about releasing 2.10.2, which should happen soon.
 + - Last month saw a burst of activity at user's ML.
 + - New SVN branch created to introduce PicoContainer to handle dependency
 +injection.
 + - Ongoing work on Haddock template, a new template/ui for Apache JSPWiki.
 +
 +## Issues:
 + - there are no issues requiring board attention at this time
 +
 +## LDAP committee/Committership changes:
 +
 + - Currently 15 committers and 10 LDAP committee members.
 + - No new LDAP committee members added in the last 3 months
 + - Last LDAP committee addition was David Vittor at Thu Jan 22 2015
 + - No new committers added in the last 3 months
 + - Last committer addition was David Vittor at Fri Jan 02 2015
 +
 +## Releases:
 +
 + - Last release was 2.10.1 on Thu May 29 2014
 +
 +## Mailing list activity:
 +
 + - dev@jspwiki.apache.org:
 +- 85 subscribers (down -1 in the last 3 months):
 +- 151 emails sent to list (124 in previous quarter)
 +
 + - u...@jspwiki.apache.org:
 +- 175 subscribers (up 2 in the last 3 months):
 +- 93 emails sent to list (29 in previous quarter)
 +
 +
 +## JIRA activity:
 +
 + - 17 JIRA tickets created in the last 3 months
 + - 13 JIRA tickets closed/resolved in the last 3 months
 \ No newline at end of file

Re: [VOTE] Release JSPWiki version 2.10.2

[Harry Metske]

+1

On 17 February 2016 at 11:17, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> This is a release vote for Apache JSPWiki, version 2.10.2. The vote will be
> open for at least 72 hours from now.
>
> It fixes the following issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732=12327049
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Everybody is encouraged to vote.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/jspwiki/2.10.2/
>
> Nexus staging repo:
> https://repository.apache.org/content/repositories/orgapachejspwiki-1002
>
> The tag to be voted upon:
> svn.apache.org/repos/asf/jspwiki/tags/jspwiki_2_10_2
>
> JSPWiki's KEYS file containing PGP keys we use to sign the release:
> http://www.apache.org/dist/jspwiki/KEYS
>
> *** Please download, test and vote:
>
> [ ] +1 Approve the release
> [ ]  0 Don't mind
> [ ] -1 Disapprove the release (please provide specific comments)
>

Re: [ANNOUNCE] Dave Koelmeyer as new JSPWiki PMC/Committer

[Harry Metske]

Welcome to the team Dave!

Kind regards,
Harry
Op 6 apr. 2016 14:51 schreef "Juan Pablo Santos Rodríguez" <
juanpablo.san...@gmail.com>:

> Hi all,
>
> We're glad to announce that the JSPWiki PMC has a new member and committer,
> Dave Koelmeyer.
>
>
> Welcome!
>
> juan pablo,
> on behalf of the JSPWiki PMC
>

Re: Wiki SpamFilter

[Harry Metske]

Then our spamfilter is a bit too agressive, I ll have a look in a few
moments..
Op 13 apr. 2016 10:20 schreef "Dave Koelmeyer" <
dave.koelme...@apertura.co.nz>:

> Hi,
>
> It appears any edits I try to make to the JSPWiki wiki at present are
> being rejected with a "Your edit has been rejected by our SpamFilter,
> sorry." message (with advice to contact this list). 24 hours ago it was
> fine, and I haven't made a heavy number of changes in the interim. Help?
>
> Cheers,
> Dave
>
> --
> Dave Koelmeyer, Owner
> Apertura Designs Ltd | www.apertura.co.nz
> Email | dave.koelme...@apertura.co.nz
> Phone | +64 21 155 0178
> Blog | www.apertura.co.nz/blog
> Facebook | www.facebook.com/AperturaDesigns
>
>

Re: Question about Wiki display

[Harry Metske]

Mike,

that could be because of caching.
The property jspwiki.usePageCache = true is default, and so you might have
page caching on.
You can verify that on your wiki by creating a page like
https://jspwiki-wiki.apache.org/Wiki.jsp?page=SystemInfo and check the *Current
Page Provider *setting.

regards,
Harry


On 18 March 2016 at 17:42, Sale, Michael  wrote:

> A quick question for the dev community and I'm sorry that this is a
> question that is probably very obvious.  As some of you might know I'm
> working with some students who are using JSPWiki as a class project.  At
> the current moment they are running into a problem trying to understand how
> Wiki posts are displayed.  What particularly confuses them is that when a
> wiki file is physically altered in the wiki-filse folder, it doesn't seem
> like the output on the screen changes when you reload a wiki page.  So they
> are thinking there is some caching going on.  Can someone lend a quick
> explanation for me to help them out?
>
> Thanks
> Mike
>
>
> --
> Michael J. Salé
> Asst. Professor of Management
> Management Information Systems Program Director
> Business Administration
> Stonehill College
>
> Email: ms...@stonehill.edu
> Phone: 508.565.5629
> Office: Stanger Hall 102
> Office Hours: M 4-5pm, T 1-2pm, R 1-2pm, F 1-2pm
>
> Break my heart for what breaks Your's, Everything I am for Your Kingdom's
> cause
>
>

Re: WorksheetPlugin

[Harry Metske]

Christian,

the page is perfectly visible, also for anonymous users.

tx,
Harry


On 25 March 2016 at 14:57, Christian Froehler <christian.froeh...@gmx.net>
wrote:

> Hi,
>
> so I spent some work on the Plugin...
>
> - Apache POI offers a class "ToHtml" in its "poi-examples.jar" which does
> an excellent job, including .css formatting.
> Therefore I removed the dependency to the "Table" plugin
>
> - Had a hard time understanding why the Plugin would break my existing
> JSPWiki installation at work
> We are still on JSPWiki 2.8.2, and the Java import statements are
> different with the old version of JSPWiki.
> Therefore I have two dev branches of the WorksheetPlugin now, one for
> JSPWiki 2.8+, the other one for JSPWiki 2.10. Haven't tried with 2.9
> (We'll update to 2.10 soon.)
>
> - License is now Apache License 2.0
>
> - Created the page
> https://jspwiki-wiki.apache.org/Wiki.jsp?page=WorksheetPlugin <
> https://jspwiki-wiki.apache.org/Wiki.jsp?page=WorksheetPlugin>, but it
> seems to be visible only when logged in.
> Could someone please review the page and make it accessible (if everything
> is fine with it).
>
> - I added the following "warning" text on the wiki page:
> While the WorksheetPlugin seems to work quite well, it is still new
> software.
> Please report any errors/problems with the plugin in the Github issue
> tracker <https://github.com/generatorr/WorksheetPlugin/issues> or on one
> of the mailing lists <
> http://jspwiki.apache.org/community/mailing_lists.html>
>
> - Source code of the Plugin is actually only 141 lines of code, including
> comments.
> With JSPWiki and POI it feels literally like standing on the shoulders of
> giants.
>
> - Feedback is very welcome
>
> best regards
>
> Christian
>
>
>
>
> > Am 21.03.2016 um 01:21 schrieb David Vittor <dvit...@gmail.com>:
> >
> > Hi Christian,
> >
> > Glad to hear you liked my "How To Write A Plugin" page :)
> >
> > Yes the log4j part I added in there for debugging and ensuring the code
> in
> > the plugin used the log4j framework, but I think Juan is right that it
> > probably does not need to be bundled into the plugin. This page will have
> > to be updated.
> >
> > I'm very excited by your plugin, as I'm currently working on something
> > similar. I'm building an Javascript/AJAX plugin for storing, adding and
> > editing data information (Excel for the cloud).
> >
> > I'll check out your plugin when I return from my holidays in a few weeks.
> > But good on you for writing and sharing it with the community!
> >
> > Cheers,
> > David V
> >
> >
> >
> >
> >
> >
> > On Mon, Mar 21, 2016 at 7:48 AM, cfr Mails 2016 <cfr2...@gmx.net> wrote:
> >
> >> Thanks Harry,  I could create my account now.
> >>
> >> Thanks Juan Pablo, for your feedback; I will do as suggested.
> >> Just one remark:
> >> I added the "log4j.properties" file because it was written here:
> >> https://jspwiki-wiki.apache.org/Wiki.jsp?page=HowToWriteAPlugin <
> >> https://jspwiki-wiki.apache.org/Wiki.jsp?page=HowToWriteAPlugin>
> >> The page was an excellent help to implement the Plugin, but in that
> point
> >> it might have to be updated.
> >>
> >> I will use and test the plugin in this week, then update repository and
> >> wiki.
> >>
> >> best regards
> >> Christian
> >>
> >>
> >>
> >>> Am 20.03.2016 um 21:26 schrieb Harry Metske <harry.met...@gmail.com>:
> >>>
> >>> I re-enabled user registration on the wiki, you should be able to
> >> register
> >>> now.
> >>>
> >>> Regards,
> >>> Harry
> >>> Op 20 mrt. 2016 9:21 p.m. schreef "Juan Pablo Santos Rodríguez" <
> >>> juanpablo.san...@gmail.com>:
> >>>
> >>>> Hi Christian,
> >>>>
> >>>> thanks for sharing your plugin!
> >>>>
> >>>> - re. packaging additional files, as you're shipping a maven project,
> >> the
> >>>> easiest way to distribute your plugin is to declare the additional
> jars
> >> as
> >>>> dependecies (as you've done). That way, anyone retrieving your plugin
> is
> >>>> going to get the additional jars as part of their build
> >>>>
> >>>> - re. adding Table plugin, IMO is ok (Dirk can correct me, as he's the
> >

Re: WorksheetPlugin

[Harry Metske]

I re-enabled user registration on the wiki, you should be able to register
now.

Regards,
Harry
Op 20 mrt. 2016 9:21 p.m. schreef "Juan Pablo Santos Rodríguez" <
juanpablo.san...@gmail.com>:

> Hi Christian,
>
> thanks for sharing your plugin!
>
> - re. packaging additional files, as you're shipping a maven project, the
> easiest way to distribute your plugin is to declare the additional jars as
> dependecies (as you've done). That way, anyone retrieving your plugin is
> going to get the additional jars as part of their build
>
> - re. adding Table plugin, IMO is ok (Dirk can correct me, as he's the
> author), but I think at least you should explicitly note it, either in the
> code or in the readme.md file..
>
> - re. licenses, AL is fine, but if you are unsure, you can check
> http://choosealicense.com/ to see which license fits you more
>
> - re. jspwiki-wiki.a.o issues, we recently got a huge wave of spam, so the
> wiki's policies have been changed in order to not allow indiscriminated
> edits, or users or groups creation. In the meantime, I'll add a link to
> https://jspwiki-wiki.apache.org/Wiki.jsp?page=ContributedPlugins pointing
> to https://github.com/generatorr/WorksheetPlugin with proper credits. As
> for the upload section, it looks like a permissions issue + a bug (you
> shouldn't see an error page). I'll try to take a look at it this week..
>
> - Finally, re. the code itself, overall it looks ok to me, only 3 small
> things:
> * I'd delete the log4j.properties file
> * add some more tests
> * on the pom.xml file, remove the use of the copy-dependencies plugin, the
> poi dependencies are going to be pushed with your plugin.
>
>
> br,
> juan pablo
>
> On Sun, Mar 20, 2016 at 7:29 PM, cfr Mails 2016  wrote:
>
> > Hi JSPWiki developers,
> >
> > I am working with JSPWiki since a few years now (as a user) and it is
> > really useful for distributing up-to-date information to the team.
> >
> > We are working a lot with Microsoft Office products, and people like
> > having their data stored in Excel tables.
> > In order to get this data into JSPWiki, I have been working with the
> > "Table" plugin.
> > It works, and looks good, but formatting is a bit time consuming.
> >
> > Now I have played around with Apache POI, which is a library to directly
> > access Excel Workbooks from Java Code:
> > The "Worksheet Plugin" extracts the data from from an Excel Workbook, and
> > generates a string which then will be parsed by the Table plugin.
> >
> > Through this, JSPWiki can have a Excel workbook as Attachment on a page,
> > and present its content in an ordinary wiki table.
> >
> > Usage:
> >
> > [{WorksheetPlugin src='NameOfAttachedExcel.xlsx' sheetName='MyData' }]
> >
> > For sure this is just a basic version, which just prints the content of
> > the cells.
> > Improvements could be:
> > - take care of cell formatting,
> > - support merged cells,
> > - Caching of the content, so that the excel doesn't need to be parsed
> > again and again;
> > - directly create html from the cells instead of using the "Table"
> plugin,
> > - support images and diagrams
> > - etc.
> > But this first version works.
> >
> > There are a few questions:
> > - the plugin requires a number of additional .jar files (poi.xml and
> > others).
> >   Can I package these additional jar files together with "my" plugin, so
> > that the user needs to copy only one .jar file into the WEB-INF/lib
> > directory?
> >
> > - As I didn't want that the user must install the "Table" Plugin
> > additionally, I have included it's unchanged source code into the new
> > plugin.
> >   Is it ok to do so? Is there a better approach?
> >
> > - under which license should I publish the plugin?
> >   Everybody should be able to use and improve free of charge. JSPWiki is
> > under Apache Software License 2.0; is this what I want for
> WorksheetPlugin?
> >
> > - I don't have access to the attachments at
> > https://jspwiki-wiki.apache.org/ . The
> > wiki won't let me create an Account.
> >   How can I get an account here? If the plugin proves useful, should I
> > create a page in that wiki?
> >
> > Sources are here. Please review. This is my first JSPWiki plugin. Looking
> > forward to feedback
> > https://github.com/generatorr/WorksheetPlugin <
> > https://github.com/generatorr/WorksheetPlugin>
> >
> > Download v0.1-alpha:
> > https://github.com/generatorr/WorksheetPlugin/releases <
> > https://github.com/generatorr/WorksheetPlugin/releases>
> >
> > Thanks!
> >
> > Christian
>

Re: Wiki SpamFilter

[Harry Metske]

No worries , glad I could help.
Op 13 apr. 2016 16:30 schreef "Dave Koelmeyer" <
dave.koelme...@davekoelmeyer.co.nz>:

> Argh – pilot error. I wasn't actually logged in. I've been using a
> private JSPWiki instance exclusively for the past couple of years so I
> guess this contributed to the brain fade. Sorry for the trouble, and
> thanks for the help.
>
> Cheers,
> Dave
>
> On 13/04/16 20:21, Harry Metske wrote:
> > Then our spamfilter is a bit too agressive, I ll have a look in a few
> > moments..
> > Op 13 apr. 2016 10:20 schreef "Dave Koelmeyer" <
> > dave.koelme...@apertura.co.nz>:
> >
> >> Hi,
> >>
> >> It appears any edits I try to make to the JSPWiki wiki at present are
> >> being rejected with a "Your edit has been rejected by our SpamFilter,
> >> sorry." message (with advice to contact this list). 24 hours ago it was
> >> fine, and I haven't made a heavy number of changes in the interim. Help?
> >>
> >> Cheers,
> >> Dave
> >>
> >> --
> >> Dave Koelmeyer, Owner
> >> Apertura Designs Ltd | www.apertura.co.nz
> >> Email | dave.koelme...@apertura.co.nz
> >> Phone | +64 21 155 0178
> >> Blog | www.apertura.co.nz/blog
> >> Facebook | www.facebook.com/AperturaDesigns
> >>
> >>
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.nz
> GPG Key ID: 0x238BFF87
>
>

Re: Blog post for review: using the Viewer style

[Harry Metske]

Great, I learned something again :-)

On 12 August 2016 at 14:01, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> +1, thanks!
>
>
> On Thu, Aug 11, 2016 at 10:03 AM, Dave Koelmeyer <
> dave.koelme...@davekoelmeyer.co.nz> wrote:
>
> > Hi All,
> >
> > Short post for review, demonstrating the new Viewer style. The
> > screengrabs are of the Elephants Dream video on Youtube and the Apache
> > Tomcat home page embedded in a wiki page, respectively.
> >
> > 
> >
> > JSPWiki feature highlight: Easily embed videos and other media with
> Viewer
> >
> > With the introduction of JSPWIki's new Haddock template comes a
> > super-easy way to add videos and other media to your wiki pages. This is
> > the new Viewer feature – one of the many available JSPWikiStyles.
> >
> > Adding videos with Viewer is as simple as wrapping your video link with
> > the %%viewer markup – a much easier method compared to previous video
> > plugins. For example, the following markup (click to enlarge):
> >
> > jspwiki-viewerstyle-1.png
> >
> > will generate the following result: (click to enlarge):
> >
> > jspwiki-viewerstyle-2.png
> >
> > Viewer supports a wide range of online services from which video content
> > will be automatically recognised (check out the full list here).
> >
> > Other neat tricks are possible with Viewer. For example, you can embed
> > content from an existing wiki link or an external webpage in the same
> > way (click to enlarge):
> >
> > jspwiki-viewerstyle-3.png
> >
> > jspwiki-viewerstyle-4.png
> >
> > For full details on how to use the Viewer style with more examples,
> > please see
> > https://jspwiki-wiki.apache.org/Wiki.jsp?page=Viewer#
> section-Viewer-Usage.
> >
> > --
> > Dave Koelmeyer
> > http://blog.davekoelmeyer.co.nz
> > GPG Key ID: 0x238BFF87
> >
> >
>

Re: Apache JSPWiki homepage template

[Harry Metske]

I remember we have had a sort of discussion with the infra team about this.
The end of the discussion was that we came to what we have now, but I
cannot remember anymore what the exact reasons were.
We could ask them what their opinion is now...

I am not so worried about having some downtime every now and then, it's not
that critical.

regards,
Harry


On 12 August 2016 at 13:59, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi,
>
> (a little bit late, but) in that case wouldn't it be easier to ask infra to
> point jspwiki.apache.org directly to the wiki? There are some brand
> requirements we should follow (most of the upper right links, the Apache
> section on the left, and the footer, if I recall correctly) and we would
> have to find a place for javadocs, but this shouldn't be a showstopper.
>
> My only concern with this is having the wiki always up, the CMS is clunkier
> to update, but it is always up, whereas the wiki VM has had a few small
> (=hours) hiccups. But other than that, it's how jspwiki.org was/is setup,
> so I'm not opposed to switch to a full wiki homepage.
>
> thoughts?
>
>
> best regards,
> juan pablo
>
> On Sat, Aug 6, 2016 at 1:28 PM, Harry Metske <harry.met...@gmail.com>
> wrote:
>
> > my suggestion was the latter (redirect from jspwiki.apache.org to
> > jspwiki-wiki.apache.org)
> >
> > On 5 August 2016 at 14:17, Juan Pablo Santos Rodríguez <
> > juanpablo.san...@gmail.com> wrote:
> >
> > > Hi Harry,
> > >
> > > technical issues aside, I'm not sure I'm following what you're
> proposing,
> > > if replacing jspwiki.a.o with our wiki, or if having something like
> > > jspwiki.a.o/wiki redirecting to the wiki?
> > >
> > > for the former I think it would be easier to ask infra to directly
> point
> > > jspwiki.a.o to the wiki vm.
> > >
> > > for the latter I think I'd be able to make a quick commit this
> > > afternoon/weekend, it's very simimlar to what we're currently doing
> with
> > > the javadocs; it's matter of adding an entry to
> > > https://svn.apache.org/repos/asf/jspwiki/site/trunk/
> content/extpaths.txt
> > > and then commiting the desired directory+file to
> > > https://svn.apache.org/repos/infra/websites/production/
> jspwiki/content/
> > ..
> > >
> > >
> > > br,
> > > juan pablo
> > >
> > > On Fri, Aug 5, 2016 at 1:42 PM, Harry Metske <harry.met...@gmail.com>
> > > wrote:
> > >
> > > > can't we just make that page empty and only put some html/js over
> there
> > > > that immediately redirects to the wiki home page?
> > > >
> > > > On 5 August 2016 at 11:28, Juan Pablo Santos Rodríguez <
> > > > juanpablo.san...@gmail.com> wrote:
> > > >
> > > > > Hi Dave,
> > > > >
> > > > > IMO there isn't any showstopper, only that generating the site
> > locally
> > > > is a
> > > > > bit complicated. The site, with instructions on how to build it
> > > locally,
> > > > is
> > > > > in SVN at https://svn.apache.org/repos/asf/jspwiki/site/trunk/
> with
> > > the
> > > > > old
> > > > > template sitting at
> > > > > https://svn.apache.org/repos/asf/jspwiki/site/trunk/templates/
> > > > >
> > > > > That said, as we're not updating very often the site, rather than
> > > > building
> > > > > locally, perhaps is easier to use the CMS bookmarklet and keep
> > pushing
> > > > > changes to staging area until the new template is ready to go.
> > > > >
> > > > > Regarding the different url for jspwiki-wiki.a.o, don't remember
> the
> > > > > specifics but, long story short, when setting up the vm to host the
> > > wiki,
> > > > > the Infra team found easier to set it up at the actual location
> and,
> > as
> > > > our
> > > > > request took several months to complete (delays on both sides), we
> > > didn't
> > > > > push to have the wiki inside jspwiki.a.o.
> > > > >
> > > > >
> > > > > br,
> > > > > juan pablo
> > > > >
> > > > > On Fri, Aug 5, 2016 at 5:31 AM, Dave Koelmeyer <
> > > > > dave.koelme...@davekoelmeyer.co.nz> wrote:
> > > > >
> > > > > > Hi All,
> > > > > >
> > > > > > Quick question, the homepage for JSPWiki is currently:
> > > > > > https://jspwiki.apache.org/ – and as can be seen it's running
> the
> > > old
> > > > > > template. Perhaps not the best first impression :) Is there any
> > > > > > show-stopper preventing switching this to Haddock?
> > > > > >
> > > > > > (On a related note I'm not quite sure why there are two separate
> > > sites,
> > > > > > when the content of https://jspwiki-wiki.apache.org/ could just
> > sit
> > > in
> > > > > > the same instance as https://jspwiki.apache.org/, but that's
> not a
> > > big
> > > > > > deal.)
> > > > > >
> > > > > > Cheers,
> > > > > > Dave
> > > > > >
> > > > > > --
> > > > > > Dave Koelmeyer
> > > > > > http://blog.davekoelmeyer.co.nz
> > > > > > GPG Key ID: 0x238BFF87
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [jira] [Commented] (JSPWIKI-1027) CorePlugin "TotalPages" unstable...

[Harry Metske]

The PageViewPlugin keeps track of pageviews, see [1] for details. It does
not the keep track of the number of pages. It stores all values in memory
and in a file. This file (PageCount.txt) is stored in the directory
designated by the jspwiki property jspwiki.workDir.
If you delete this file, all counters will be "reset" to zero (on the next
restart).

regards,
Harry




[1] - https://jspwiki-wiki.apache.org/Wiki.jsp?page=PageViewPlugin

On 23 June 2016 at 10:23, krille (JIRA)  wrote:

>
> [
> https://issues.apache.org/jira/browse/JSPWIKI-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346034#comment-15346034
> ]
>
> krille commented on JSPWIKI-1027:
> -
>
> I have in total 456 pages (*.txt) files. Is there any reference between
> the PageViewPlugin that states "Storing 671 counter values" ? Is there safe
> to stop the tomcat and empty "work" and "temp" directories? Or is there
> something else I can "reset"?
>
> > CorePlugin "TotalPages" unstable...
> > ---
> >
> > Key: JSPWIKI-1027
> > URL: https://issues.apache.org/jira/browse/JSPWIKI-1027
> > Project: JSPWiki
> >  Issue Type: Bug
> >  Components: Plugins
> >Affects Versions: 2.10.2
> > Environment: Linux
> >Reporter: krille
> >Priority: Trivial
> >
> > I upgrade 2.10.0 to 2.10.2 and now the {$totalpages} plugin is
> restarting at 0 over and over again... It takes time until it has reached
> the complete count of all pages again... Then after some time it starts at
> 0 again?
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Re: Apache JSPWiki homepage template

[Harry Metske]

can't we just make that page empty and only put some html/js over there
that immediately redirects to the wiki home page?

On 5 August 2016 at 11:28, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi Dave,
>
> IMO there isn't any showstopper, only that generating the site locally is a
> bit complicated. The site, with instructions on how to build it locally, is
> in SVN at https://svn.apache.org/repos/asf/jspwiki/site/trunk/ with the
> old
> template sitting at
> https://svn.apache.org/repos/asf/jspwiki/site/trunk/templates/
>
> That said, as we're not updating very often the site, rather than building
> locally, perhaps is easier to use the CMS bookmarklet and keep pushing
> changes to staging area until the new template is ready to go.
>
> Regarding the different url for jspwiki-wiki.a.o, don't remember the
> specifics but, long story short, when setting up the vm to host the wiki,
> the Infra team found easier to set it up at the actual location and, as our
> request took several months to complete (delays on both sides), we didn't
> push to have the wiki inside jspwiki.a.o.
>
>
> br,
> juan pablo
>
> On Fri, Aug 5, 2016 at 5:31 AM, Dave Koelmeyer <
> dave.koelme...@davekoelmeyer.co.nz> wrote:
>
> > Hi All,
> >
> > Quick question, the homepage for JSPWiki is currently:
> > https://jspwiki.apache.org/ – and as can be seen it's running the old
> > template. Perhaps not the best first impression :) Is there any
> > show-stopper preventing switching this to Haddock?
> >
> > (On a related note I'm not quite sure why there are two separate sites,
> > when the content of https://jspwiki-wiki.apache.org/ could just sit in
> > the same instance as https://jspwiki.apache.org/, but that's not a big
> > deal.)
> >
> > Cheers,
> > Dave
> >
> > --
> > Dave Koelmeyer
> > http://blog.davekoelmeyer.co.nz
> > GPG Key ID: 0x238BFF87
> >
> >
>

Fwd: Jenkins JDK Matrix - and consolidating of versions.

[Harry Metske]

Hi,

I subscribed to the bui...@apache.org mailing list.
I logged in the Jenkins and tried to check which JDK we were using, but
there is no "Configure"  option for me. Is this because I lack
authorizations?

See: https://builds.apache.org/view/All/job/JSPWiki/

regards,
Harry



-- Forwarded message --
From: Gav 
Date: 5 August 2016 at 02:13
Subject: Fwd: Jenkins JDK Matrix - and consolidating of versions.
To: gmcdon...@apache.org


Hello PMCs,

7 days ago I informed the builds@ and infrastructure@ mailing lists the
intention to consolidate JDK versions in
our Jenkins instance. I gave 7 days notice. (Anyone configuring builds
should be subscribed to the builds@
mailing list)

Today I find that there are still :-

109 jobs configured to use the 'latest1.8'
67 jobs configured to use the 'latest1.7'
7 jobs configured to use the 'latest 1.6'

45 jobs configured to use '1.8.0_66'
4 jobs configured to use '1.8.0_05'
4 jobs configured to use '1.8.0_11'


This wider distribution email to all PMC private lists is to let you know
I'm going to delay the migration for '3 more days'
at which point I will migrate any remaining jobs myself.

I prefer of course that projects make the changes themselves.

Below I include a copy of the mail I sent 7 days ago FYI.

tl;dr please take a look at :-

https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix

There are also plans to consoildate Maven and Ant versions - please do
check the
builds@ mailing list archives for these notices - these are due to be
migrated by
Sunday at the latest

Any questions please email me direct or reply to any of the builds@ mails.


HTH

Gav... (ASF Infrastructure Team)


-- Forwarded message --
From: Gav 
Date: Fri, Jul 29, 2016 at 9:03 PM
Subject: Jenkins JDK Matrix - and consolidating of versions.
To: bui...@apache.org, "infrastruct...@apache.org Infrastructure" <
infrastruct...@apache.org>


Hi All,

So 99% of our Jenkins build machines are now puppetised with our configs in
our Git repos.
Going forward this should make things easier to maintain the software (and
versions of) on the nodes.

I went through all the JDK drop down options available in the Jenkins UI
when
creating a build.The Confluence wiki page at :-

https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix

lists all them all. When choosing a version to use I hope that this
information will
prove useful - any changes made we will keep this page upto date.
However, some are not currently installed on the new puppetised
slaves (on purpose) and others we intend to consolidate down to fewer
versions.

In contrast, we will be able to make newer release versions available
quicker.

Once we are done with the JDKs, we'll move on to Maven, and then the rest.

Ok to specifics,

First major change to get out of the way is the removal of the 'auto
install' JDK
versions. They overlap with installed versions and going forward we would
rather
manage installation via Puppet and roll them out to all slaves in one hit.

Looking at the table in the linked wiki page above, this means we'll be
removing
eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
To avoid confusion we'll also be removing the auto install 'latest1.6'
'latest1.7' and 'latest1.8' options.

The best options for 'latest' versions is the ones at the top of the table
'JDK 1.x (Latest)'
which are all installed on all nodes and managed via puppet.

I'll point out also that we have installed 'unlimited security' versions of
1.6,1.7,1.8 jdks.

Very recent addition is also that of the JDK 9 b128 Early Access Build. We
hope you enjoy
this addition and please do give feedback on this version to the builds@
mailing list so we can pass it on - but certainly do not plan to base your
releases on these 'ea' builds. I'll try my best to add new ea builds as
they come through.

Last ones to mention are the IBM and Harmony versions. I'm not sure how
much in use
these are so I'm holding off on installing these for now. Please do ask for
a specific version
if needed. I'll drop the from the UI in time.

I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
along with the auto install latest links. Please plan
on migrating your builds away from these versions before then.

Any follow questions, please do concentrate your email responses to the
builds@ mailing list.

Thanks!

Gav... (On behalf of the Infrastructure Team)

Re: Apache JSPWiki homepage template

[Harry Metske]

my suggestion was the latter (redirect from jspwiki.apache.org to
jspwiki-wiki.apache.org)

On 5 August 2016 at 14:17, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi Harry,
>
> technical issues aside, I'm not sure I'm following what you're proposing,
> if replacing jspwiki.a.o with our wiki, or if having something like
> jspwiki.a.o/wiki redirecting to the wiki?
>
> for the former I think it would be easier to ask infra to directly point
> jspwiki.a.o to the wiki vm.
>
> for the latter I think I'd be able to make a quick commit this
> afternoon/weekend, it's very simimlar to what we're currently doing with
> the javadocs; it's matter of adding an entry to
> https://svn.apache.org/repos/asf/jspwiki/site/trunk/content/extpaths.txt
> and then commiting the desired directory+file to
> https://svn.apache.org/repos/infra/websites/production/jspwiki/content/..
>
>
> br,
> juan pablo
>
> On Fri, Aug 5, 2016 at 1:42 PM, Harry Metske <harry.met...@gmail.com>
> wrote:
>
> > can't we just make that page empty and only put some html/js over there
> > that immediately redirects to the wiki home page?
> >
> > On 5 August 2016 at 11:28, Juan Pablo Santos Rodríguez <
> > juanpablo.san...@gmail.com> wrote:
> >
> > > Hi Dave,
> > >
> > > IMO there isn't any showstopper, only that generating the site locally
> > is a
> > > bit complicated. The site, with instructions on how to build it
> locally,
> > is
> > > in SVN at https://svn.apache.org/repos/asf/jspwiki/site/trunk/ with
> the
> > > old
> > > template sitting at
> > > https://svn.apache.org/repos/asf/jspwiki/site/trunk/templates/
> > >
> > > That said, as we're not updating very often the site, rather than
> > building
> > > locally, perhaps is easier to use the CMS bookmarklet and keep pushing
> > > changes to staging area until the new template is ready to go.
> > >
> > > Regarding the different url for jspwiki-wiki.a.o, don't remember the
> > > specifics but, long story short, when setting up the vm to host the
> wiki,
> > > the Infra team found easier to set it up at the actual location and, as
> > our
> > > request took several months to complete (delays on both sides), we
> didn't
> > > push to have the wiki inside jspwiki.a.o.
> > >
> > >
> > > br,
> > > juan pablo
> > >
> > > On Fri, Aug 5, 2016 at 5:31 AM, Dave Koelmeyer <
> > > dave.koelme...@davekoelmeyer.co.nz> wrote:
> > >
> > > > Hi All,
> > > >
> > > > Quick question, the homepage for JSPWiki is currently:
> > > > https://jspwiki.apache.org/ – and as can be seen it's running the
> old
> > > > template. Perhaps not the best first impression :) Is there any
> > > > show-stopper preventing switching this to Haddock?
> > > >
> > > > (On a related note I'm not quite sure why there are two separate
> sites,
> > > > when the content of https://jspwiki-wiki.apache.org/ could just sit
> in
> > > > the same instance as https://jspwiki.apache.org/, but that's not a
> big
> > > > deal.)
> > > >
> > > > Cheers,
> > > > Dave
> > > >
> > > > --
> > > > Dave Koelmeyer
> > > > http://blog.davekoelmeyer.co.nz
> > > > GPG Key ID: 0x238BFF87
> > > >
> > > >
> > >
> >
>

Re: Blog post for review: ContextualDiffProvider

[Harry Metske]

+1

On 8 August 2016 at 01:41, Dave Koelmeyer <
dave.koelme...@davekoelmeyer.co.nz> wrote:

> Hi All,
>
> A small blog post lined up for enabling the ContextDiffProvider. The
> last sentence contains links to the jspwiki.properties documentation and
> setting the custom properties file, respectively.
>
> *
>
> Display JSPWiki page differences word-by-word
>
> By default, JSPWiki displays differences between page versions
> line-by-line. While serviceable for general use, this is often not
> fine-grained enough to easily identify specific changes – especially in
> pages with lots of content.
>
> In JSPWiki this setting is known as the difference provider. You can
> configure alternative difference providers, one of which is the
> ContextualDiffProvider. The ContextualDiffProvider enables displaying of
> page version differences on a word-by-word basis.
>
> Here's an example of page differences with the default
> TraditionalDiffProvider enabled (click to enlarge):
>
> jspwiki-contextualdiff-1.png
>
> Note that while only one word and one character has changed, the entire
> sentence is highlighted. By comparison here are the same changes with
> the ContextualDiffProvider enabled instead (click to enlarge):
>
> jspwiki-contextualdiff-2.png
>
> You can find more information on JSPWiki's difference providers here,
> and you can make the setting in your jspwiki-custom.properties file.
>
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.nz
> GPG Key ID: 0x238BFF87
>
>

Re: Jenkins JDK Matrix - and consolidating of versions.

[Harry Metske]

JP? Do you have access?

Op 16 aug. 2016 16:13 schreef "David Vittor" <dvit...@gmail.com>:

> Hi Harry,
>
> Yeah, I just logged in to Jenkins also, but no "Configure"  option for me
> either. Yes I think this is a authorization setting.
>
> I also had a look at the environment settings, but I'm not sure that is for
> JSPWiki directly.
> https://builds.apache.org/view/All/job/JSPWiki/414/injectedEnvVars/
>
> If we could get "configure" access, I'd be happy to update us. I think we
> can also bump maven up from 3.0.4 to 3.3.9 without any issues.
>
> Cheers,
> David V
>
>
>
> On Fri, Aug 5, 2016 at 10:05 PM, Harry Metske <harry.met...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I subscribed to the bui...@apache.org mailing list.
> > I logged in the Jenkins and tried to check which JDK we were using, but
> > there is no "Configure"  option for me. Is this because I lack
> > authorizations?
> >
> > See: https://builds.apache.org/view/All/job/JSPWiki/
> >
> > regards,
> > Harry
> >
> >
> >
> > -- Forwarded message --
> > From: Gav <gmcdon...@apache.org>
> > Date: 5 August 2016 at 02:13
> > Subject: Fwd: Jenkins JDK Matrix - and consolidating of versions.
> > To: gmcdon...@apache.org
> >
> >
> > Hello PMCs,
> >
> > 7 days ago I informed the builds@ and infrastructure@ mailing lists the
> > intention to consolidate JDK versions in
> > our Jenkins instance. I gave 7 days notice. (Anyone configuring builds
> > should be subscribed to the builds@
> > mailing list)
> >
> > Today I find that there are still :-
> >
> > 109 jobs configured to use the 'latest1.8'
> > 67 jobs configured to use the 'latest1.7'
> > 7 jobs configured to use the 'latest 1.6'
> >
> > 45 jobs configured to use '1.8.0_66'
> > 4 jobs configured to use '1.8.0_05'
> > 4 jobs configured to use '1.8.0_11'
> >
> >
> > This wider distribution email to all PMC private lists is to let you know
> > I'm going to delay the migration for '3 more days'
> > at which point I will migrate any remaining jobs myself.
> >
> > I prefer of course that projects make the changes themselves.
> >
> > Below I include a copy of the mail I sent 7 days ago FYI.
> >
> > tl;dr please take a look at :-
> >
> > https://cwiki.apache.org/confluence/display/INFRA/JDK+
> Installation+Matrix
> >
> > There are also plans to consoildate Maven and Ant versions - please do
> > check the
> > builds@ mailing list archives for these notices - these are due to be
> > migrated by
> > Sunday at the latest
> >
> > Any questions please email me direct or reply to any of the builds@
> mails.
> >
> >
> > HTH
> >
> > Gav... (ASF Infrastructure Team)
> >
> >
> > -- Forwarded message --
> > From: Gav <gmcdon...@apache.org>
> > Date: Fri, Jul 29, 2016 at 9:03 PM
> > Subject: Jenkins JDK Matrix - and consolidating of versions.
> > To: bui...@apache.org, "infrastruct...@apache.org Infrastructure" <
> > infrastruct...@apache.org>
> >
> >
> > Hi All,
> >
> > So 99% of our Jenkins build machines are now puppetised with our configs
> in
> > our Git repos.
> > Going forward this should make things easier to maintain the software
> (and
> > versions of) on the nodes.
> >
> > I went through all the JDK drop down options available in the Jenkins UI
> > when
> > creating a build.The Confluence wiki page at :-
> >
> > https://cwiki.apache.org/confluence/display/INFRA/JDK+
> Installation+Matrix
> >
> > lists all them all. When choosing a version to use I hope that this
> > information will
> > prove useful - any changes made we will keep this page upto date.
> > However, some are not currently installed on the new puppetised
> > slaves (on purpose) and others we intend to consolidate down to fewer
> > versions.
> >
> > In contrast, we will be able to make newer release versions available
> > quicker.
> >
> > Once we are done with the JDKs, we'll move on to Maven, and then the
> rest.
> >
> > Ok to specifics,
> >
> > First major change to get out of the way is the removal of the 'auto
> > install' JDK
> > versions. They overlap with installed versions and going forward we would
> > rather
> > manage installation via Puppet and roll them out to all slaves in one
> hit.
> >
> > Looking at 

Re: switching svn to git for jspwiki ?

[Harry Metske]

OK, asfinfra already has a model JIRA for this (SVN->GIT Migration), these
fields must be entered, agree with these values ?  :

Git Notification Mailing List  :  comm...@jspwiki.apache.org
Git Repository Name   : jspwiki
Git Repository Import Path  : https://svn.apache.org/repos/asf/jspwiki

And we should also have our Jenkins job changed...

regards,
Harry



On 21 August 2016 at 11:50, Dirk Frederickx <dirk.frederi...@gmail.com>
wrote:

> +1 for me too.
>
> dirk
>
> On Sat, Aug 20, 2016 at 9:00 PM, Juan Pablo Santos Rodríguez <
> juanpablo.san...@gmail.com> wrote:
>
> > Hi,
> >
> > +1 here too
> >
> > br,
> > juan pablo
> >
> > El 20 ago. 2016 5:14 a. m., "David Vittor" <dvit...@gmail.com> escribió:
> >
> > > Oops on mobile. That was meant to be +1. :)
> > > On 20/08/2016 1:13 PM, "David Vittor" <dvit...@gmail.com> wrote:
> > >
> > > > ±1 for git from me also. I use this at work now also, so am familiar
> > with
> > > > it.
> > > >
> > > > Cheers,
> > > > David V
> > > > On 20/08/2016 11:23 AM, "Dave Koelmeyer"
> <dave.koelmeyer@davekoelmeyer.
> > > > co.nz> wrote:
> > > >
> > > >> On a related note, if this goes ahead perhaps someone (at some
> stage)
> > > >> can summarise some of the pros of switching to git and I can create
> an
> > > >> announcement blog post.
> > > >>
> > > >> Cheers,
> > > >> Dave
> > > >>
> > > >> On 20/08/16 06:01, Jürgen Weber wrote:
> > > >> > Hi,
> > > >> >
> > > >> > I am for git, too.
> > > >> > But is there an apache.org repository?
> > > >> >
> > > >> > Cheers,
> > > >> > Juergen
> > > >> >
> > > >> > 2016-08-19 18:36 GMT+02:00 Harry Metske <harry.met...@gmail.com>:
> > > >> >> Hi all,
> > > >> >>
> > > >> >> how would anyone feel if we migrated our jspwiki codebase from
> svn
> > to
> > > >> git
> > > >> >> (github or somewhere else in the apache domain) ?
> > > >> >>
> > > >> >> I have a strong preference for git (I hardly use svn these
> days), I
> > > >> guess
> > > >> >> most of you feel the same.
> > > >> >>
> > > >> >> If there are no showstoppers, we could ask infra for the options.
> > > >> >>
> > > >> >> regards,
> > > >> >> Harry
> > > >>
> > > >> --
> > > >> Dave Koelmeyer
> > > >> http://blog.davekoelmeyer.co.nz
> > > >> GPG Key ID: 0x238BFF87
> > > >>
> > > >>
> > >
> >
>

Re: Fwd: [jira] [Commented] (INFRA-12577) SVN to GIT migration for JSPWiki

[Harry Metske]

Nice 

Op 13 sep. 2016 18:09 schreef "Juan Pablo Santos Rodríguez" <
juanpablo.san...@gmail.com>:

> Hi,
>
> just fyi, git repo is near :-)
>
> br,
> juan pablo
> -- Mensaje reenviado --
> De: "Daniel Takamori (JIRA)" 
> Fecha: 13 sept. 2016 6:03 p. m.
> Asunto: [jira] [Commented] (INFRA-12577) SVN to GIT migration for JSPWiki
> Para: 
> Cc:
>
>
> > [ https://issues.apache.org/jira/browse/INFRA-12577?page=
> > com.atlassian.jira.plugin.system.issuetabpanels:comment-
> > tabpanel=15487599#comment-15487599 ]
> >
> > Daniel Takamori commented on INFRA-12577:
> > -
> >
> > The migration is in progress and should complete in around 24-36 hours.
> >
> > > SVN to GIT migration for JSPWiki
> > > 
> > >
> > > Key: INFRA-12577
> > > URL: https://issues.apache.org/jira/browse/INFRA-12577
> > > Project: Infrastructure
> > >  Issue Type: SVN->GIT Migration
> > >  Components: Git
> > >Reporter: Juan Pablo Santos Rodríguez
> > >Assignee: Daniel Takamori
> > >
> >
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.3.4#6332)
> >
>

Re: switching svn to git for jspwiki ?

[Harry Metske]

Hi,

our svn to git migration is done.
New resources:
browse git repo :
https://git-wip-us.apache.org/repos/asf?p=jspwiki.git;a=summary
git clone url : https://git-wip-us.apache.org/repos/asf/jspwiki.git
github mirror: https://github.com/apache/jspwiki

I made some quick changes on our wiki to reflect this. We also need quite a
few changes on our static site, will try to do that later.

regards,
Harry


On 22 August 2016 at 07:55, Harry Metske <harry.met...@gmail.com> wrote:

> OK, asfinfra already has a model JIRA for this (SVN->GIT Migration), these
> fields must be entered, agree with these values ?  :
>
> Git Notification Mailing List  :  comm...@jspwiki.apache.org
> Git Repository Name   : jspwiki
> Git Repository Import Path  : https://svn.apache.org/repos/asf/jspwiki
>
> And we should also have our Jenkins job changed...
>
> regards,
> Harry
>
>
>
>
> On 21 August 2016 at 11:50, Dirk Frederickx <dirk.frederi...@gmail.com>
> wrote:
>
>> +1 for me too.
>>
>> dirk
>>
>> On Sat, Aug 20, 2016 at 9:00 PM, Juan Pablo Santos Rodríguez <
>> juanpablo.san...@gmail.com> wrote:
>>
>> > Hi,
>> >
>> > +1 here too
>> >
>> > br,
>> > juan pablo
>> >
>> > El 20 ago. 2016 5:14 a. m., "David Vittor" <dvit...@gmail.com>
>> escribió:
>> >
>> > > Oops on mobile. That was meant to be +1. :)
>> > > On 20/08/2016 1:13 PM, "David Vittor" <dvit...@gmail.com> wrote:
>> > >
>> > > > ±1 for git from me also. I use this at work now also, so am familiar
>> > with
>> > > > it.
>> > > >
>> > > > Cheers,
>> > > > David V
>> > > > On 20/08/2016 11:23 AM, "Dave Koelmeyer"
>> <dave.koelmeyer@davekoelmeyer.
>> > > > co.nz> wrote:
>> > > >
>> > > >> On a related note, if this goes ahead perhaps someone (at some
>> stage)
>> > > >> can summarise some of the pros of switching to git and I can
>> create an
>> > > >> announcement blog post.
>> > > >>
>> > > >> Cheers,
>> > > >> Dave
>> > > >>
>> > > >> On 20/08/16 06:01, Jürgen Weber wrote:
>> > > >> > Hi,
>> > > >> >
>> > > >> > I am for git, too.
>> > > >> > But is there an apache.org repository?
>> > > >> >
>> > > >> > Cheers,
>> > > >> > Juergen
>> > > >> >
>> > > >> > 2016-08-19 18:36 GMT+02:00 Harry Metske <harry.met...@gmail.com
>> >:
>> > > >> >> Hi all,
>> > > >> >>
>> > > >> >> how would anyone feel if we migrated our jspwiki codebase from
>> svn
>> > to
>> > > >> git
>> > > >> >> (github or somewhere else in the apache domain) ?
>> > > >> >>
>> > > >> >> I have a strong preference for git (I hardly use svn these
>> days), I
>> > > >> guess
>> > > >> >> most of you feel the same.
>> > > >> >>
>> > > >> >> If there are no showstoppers, we could ask infra for the
>> options.
>> > > >> >>
>> > > >> >> regards,
>> > > >> >> Harry
>> > > >>
>> > > >> --
>> > > >> Dave Koelmeyer
>> > > >> http://blog.davekoelmeyer.co.nz
>> > > >> GPG Key ID: 0x238BFF87
>> > > >>
>> > > >>
>> > >
>> >
>>
>
>

Re: switching svn to git for jspwiki ?

[Harry Metske]

I just entered https://issues.apache.org/jira/browse/INFRA-12628 to ask the
infra team to reflect the svn2git migration in our Jenkins job.

regards,
Harry


On 16 September 2016 at 16:45, Harry Metske <harry.met...@gmail.com> wrote:

> Sounds like a good plan!
>
> On 16 September 2016 at 13:07, David Vittor <dvit...@gmail.com> wrote:
>
>> This looks good. I've had a play with it.
>>
>> Although I think the next thing is we have to work out how branches and
>> pull requests will work.
>>
>> I'm assuming we will start using feature branches, were we will have a
>> different branch for each JIRA ticket.
>>
>> Then we need to merge these branches into some sort of a "develop" branch.
>>
>> Then when ready for release, we merge the develop branch into "master",
>> which will remain the last released version.
>> i.e. http://nvie.com/posts/a-successful-git-branching-model/
>>
>> We should probably document this on the wiki somewhere.
>>
>> Cheers,
>> David V
>>
>>
>>
>> On Fri, Sep 16, 2016 at 4:39 PM, Harry Metske <harry.met...@gmail.com>
>> wrote:
>>
>> > Hi,
>> >
>> > our svn to git migration is done.
>> > New resources:
>> > browse git repo :
>> > https://git-wip-us.apache.org/repos/asf?p=jspwiki.git;a=summary
>> > git clone url : https://git-wip-us.apache.org/repos/asf/jspwiki.git
>> > github mirror: https://github.com/apache/jspwiki
>> >
>> > I made some quick changes on our wiki to reflect this. We also need
>> quite a
>> > few changes on our static site, will try to do that later.
>> >
>> > regards,
>> > Harry
>> >
>> >
>> > On 22 August 2016 at 07:55, Harry Metske <harry.met...@gmail.com>
>> wrote:
>> >
>> > > OK, asfinfra already has a model JIRA for this (SVN->GIT Migration),
>> > these
>> > > fields must be entered, agree with these values ?  :
>> > >
>> > > Git Notification Mailing List  :  comm...@jspwiki.apache.org
>> > > Git Repository Name   : jspwiki
>> > > Git Repository Import Path  : https://svn.apache.org/repos/a
>> sf/jspwiki
>> > >
>> > > And we should also have our Jenkins job changed...
>> > >
>> > > regards,
>> > > Harry
>> > >
>> > >
>> > >
>> > >
>> > > On 21 August 2016 at 11:50, Dirk Frederickx <
>> dirk.frederi...@gmail.com>
>> > > wrote:
>> > >
>> > >> +1 for me too.
>> > >>
>> > >> dirk
>> > >>
>> > >> On Sat, Aug 20, 2016 at 9:00 PM, Juan Pablo Santos Rodríguez <
>> > >> juanpablo.san...@gmail.com> wrote:
>> > >>
>> > >> > Hi,
>> > >> >
>> > >> > +1 here too
>> > >> >
>> > >> > br,
>> > >> > juan pablo
>> > >> >
>> > >> > El 20 ago. 2016 5:14 a. m., "David Vittor" <dvit...@gmail.com>
>> > >> escribió:
>> > >> >
>> > >> > > Oops on mobile. That was meant to be +1. :)
>> > >> > > On 20/08/2016 1:13 PM, "David Vittor" <dvit...@gmail.com> wrote:
>> > >> > >
>> > >> > > > ±1 for git from me also. I use this at work now also, so am
>> > familiar
>> > >> > with
>> > >> > > > it.
>> > >> > > >
>> > >> > > > Cheers,
>> > >> > > > David V
>> > >> > > > On 20/08/2016 11:23 AM, "Dave Koelmeyer"
>> > >> <dave.koelmeyer@davekoelmeyer.
>> > >> > > > co.nz> wrote:
>> > >> > > >
>> > >> > > >> On a related note, if this goes ahead perhaps someone (at some
>> > >> stage)
>> > >> > > >> can summarise some of the pros of switching to git and I can
>> > >> create an
>> > >> > > >> announcement blog post.
>> > >> > > >>
>> > >> > > >> Cheers,
>> > >> > > >> Dave
>> > >> > > >>
>> > >> > > >> On 20/08/16 06:01, Jürgen Weber wrote:
>> > >> > > >> > Hi,
>> > >> > > >> >
>> > >> > > >> > I am for git, too.
>> > >> > > >> > But is there an apache.org repository?
>> > >> > > >> >
>> > >> > > >> > Cheers,
>> > >> > > >> > Juergen
>> > >> > > >> >
>> > >> > > >> > 2016-08-19 18:36 GMT+02:00 Harry Metske <
>> > harry.met...@gmail.com
>> > >> >:
>> > >> > > >> >> Hi all,
>> > >> > > >> >>
>> > >> > > >> >> how would anyone feel if we migrated our jspwiki codebase
>> from
>> > >> svn
>> > >> > to
>> > >> > > >> git
>> > >> > > >> >> (github or somewhere else in the apache domain) ?
>> > >> > > >> >>
>> > >> > > >> >> I have a strong preference for git (I hardly use svn these
>> > >> days), I
>> > >> > > >> guess
>> > >> > > >> >> most of you feel the same.
>> > >> > > >> >>
>> > >> > > >> >> If there are no showstoppers, we could ask infra for the
>> > >> options.
>> > >> > > >> >>
>> > >> > > >> >> regards,
>> > >> > > >> >> Harry
>> > >> > > >>
>> > >> > > >> --
>> > >> > > >> Dave Koelmeyer
>> > >> > > >> http://blog.davekoelmeyer.co.nz
>> > >> > > >> GPG Key ID: 0x238BFF87
>> > >> > > >>
>> > >> > > >>
>> > >> > >
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>
>

Re: switching svn to git for jspwiki ?

[Harry Metske]

Sounds like a good plan!

On 16 September 2016 at 13:07, David Vittor <dvit...@gmail.com> wrote:

> This looks good. I've had a play with it.
>
> Although I think the next thing is we have to work out how branches and
> pull requests will work.
>
> I'm assuming we will start using feature branches, were we will have a
> different branch for each JIRA ticket.
>
> Then we need to merge these branches into some sort of a "develop" branch.
>
> Then when ready for release, we merge the develop branch into "master",
> which will remain the last released version.
> i.e. http://nvie.com/posts/a-successful-git-branching-model/
>
> We should probably document this on the wiki somewhere.
>
> Cheers,
> David V
>
>
>
> On Fri, Sep 16, 2016 at 4:39 PM, Harry Metske <harry.met...@gmail.com>
> wrote:
>
> > Hi,
> >
> > our svn to git migration is done.
> > New resources:
> > browse git repo :
> > https://git-wip-us.apache.org/repos/asf?p=jspwiki.git;a=summary
> > git clone url : https://git-wip-us.apache.org/repos/asf/jspwiki.git
> > github mirror: https://github.com/apache/jspwiki
> >
> > I made some quick changes on our wiki to reflect this. We also need
> quite a
> > few changes on our static site, will try to do that later.
> >
> > regards,
> > Harry
> >
> >
> > On 22 August 2016 at 07:55, Harry Metske <harry.met...@gmail.com> wrote:
> >
> > > OK, asfinfra already has a model JIRA for this (SVN->GIT Migration),
> > these
> > > fields must be entered, agree with these values ?  :
> > >
> > > Git Notification Mailing List  :  comm...@jspwiki.apache.org
> > > Git Repository Name   : jspwiki
> > > Git Repository Import Path  : https://svn.apache.org/repos/asf/jspwiki
> > >
> > > And we should also have our Jenkins job changed...
> > >
> > > regards,
> > > Harry
> > >
> > >
> > >
> > >
> > > On 21 August 2016 at 11:50, Dirk Frederickx <dirk.frederi...@gmail.com
> >
> > > wrote:
> > >
> > >> +1 for me too.
> > >>
> > >> dirk
> > >>
> > >> On Sat, Aug 20, 2016 at 9:00 PM, Juan Pablo Santos Rodríguez <
> > >> juanpablo.san...@gmail.com> wrote:
> > >>
> > >> > Hi,
> > >> >
> > >> > +1 here too
> > >> >
> > >> > br,
> > >> > juan pablo
> > >> >
> > >> > El 20 ago. 2016 5:14 a. m., "David Vittor" <dvit...@gmail.com>
> > >> escribió:
> > >> >
> > >> > > Oops on mobile. That was meant to be +1. :)
> > >> > > On 20/08/2016 1:13 PM, "David Vittor" <dvit...@gmail.com> wrote:
> > >> > >
> > >> > > > ±1 for git from me also. I use this at work now also, so am
> > familiar
> > >> > with
> > >> > > > it.
> > >> > > >
> > >> > > > Cheers,
> > >> > > > David V
> > >> > > > On 20/08/2016 11:23 AM, "Dave Koelmeyer"
> > >> <dave.koelmeyer@davekoelmeyer.
> > >> > > > co.nz> wrote:
> > >> > > >
> > >> > > >> On a related note, if this goes ahead perhaps someone (at some
> > >> stage)
> > >> > > >> can summarise some of the pros of switching to git and I can
> > >> create an
> > >> > > >> announcement blog post.
> > >> > > >>
> > >> > > >> Cheers,
> > >> > > >> Dave
> > >> > > >>
> > >> > > >> On 20/08/16 06:01, Jürgen Weber wrote:
> > >> > > >> > Hi,
> > >> > > >> >
> > >> > > >> > I am for git, too.
> > >> > > >> > But is there an apache.org repository?
> > >> > > >> >
> > >> > > >> > Cheers,
> > >> > > >> > Juergen
> > >> > > >> >
> > >> > > >> > 2016-08-19 18:36 GMT+02:00 Harry Metske <
> > harry.met...@gmail.com
> > >> >:
> > >> > > >> >> Hi all,
> > >> > > >> >>
> > >> > > >> >> how would anyone feel if we migrated our jspwiki codebase
> from
> > >> svn
> > >> > to
> > >> > > >> git
> > >> > > >> >> (github or somewhere else in the apache domain) ?
> > >> > > >> >>
> > >> > > >> >> I have a strong preference for git (I hardly use svn these
> > >> days), I
> > >> > > >> guess
> > >> > > >> >> most of you feel the same.
> > >> > > >> >>
> > >> > > >> >> If there are no showstoppers, we could ask infra for the
> > >> options.
> > >> > > >> >>
> > >> > > >> >> regards,
> > >> > > >> >> Harry
> > >> > > >>
> > >> > > >> --
> > >> > > >> Dave Koelmeyer
> > >> > > >> http://blog.davekoelmeyer.co.nz
> > >> > > >> GPG Key ID: 0x238BFF87
> > >> > > >>
> > >> > > >>
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>

Re: svn commit: r1764751 - /jspwiki/board/2016-10.txt

[Harry Metske]

looks good

thanks,
Harry

On 13 October 2016 at 20:22, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi,
>
> as it says below, this is the tentative Board report for this quarter.
> Please, have a look at it in case I've missed something. If there aren't
> objections I plan to submit it tomorrow night (~24h from now)
>
>
> br,
> juan pablo
>
> -- Forwarded message --
> From: 
> Date: Thu, Oct 13, 2016 at 8:19 PM
> Subject: svn commit: r1764751 - /jspwiki/board/2016-10.txt
> To: comm...@jspwiki.apache.org
>
>
> Author: juanpablo
> Date: Thu Oct 13 18:19:20 2016
> New Revision: 1764751
>
> URL: http://svn.apache.org/viewvc?rev=1764751=rev
> Log:
> tentative board report for this quarter - open for reviews, comments,
> corrections, etc.
>
> Added:
> jspwiki/board/2016-10.txt
>
> Added: jspwiki/board/2016-10.txt
> URL: http://svn.apache.org/viewvc/jspwiki/board/2016-10.txt?rev=
> 1764751=auto
> 
> ==
> --- jspwiki/board/2016-10.txt (added)
> +++ jspwiki/board/2016-10.txt Thu Oct 13 18:19:20 2016
> @@ -0,0 +1,47 @@
> +## Description:
> + - A feature-rich and extensible WikiWiki engine built around the standard
> +JEE components (Java, servlets, JSP).
> +
> +## Issues:
> + - There are no issues requiring board attention at this time. There's
> enough
> +people to provide oversight.
> +
> +## Activity:
> + - Source code was migrated from SVN to Git (+ its integrations) in order
> to
> +ease contributions.
> +
> + - We've also talked about moving jspwiki.a.o from ASF's CMS to JSPWiki
> +(https://s.apache.org/PFXI) as a) historically it's always been that way,
> and
> +b) we could use it as showcase, having a separate wiki doesn't seem to be
> +enough (https://issues.apache.org/jira/browse/JSPWIKI-1030). I
> volunteered
> +for the task (moving content, copyright compliance, asking infra) but
> haven't
> +had time this quarter. Hopefully this will change on the upcoming quarter.
> +
> + - 5 new blog posts at https://blogs.apache.org/jspwiki/
> +
> +## Health report:
> + - All questions asked on MLs where answered, with a few JIRA issues
> solved
> +and some other fixes that went into trunk/master.
> +
> + - 3 JIRA issues fixes came from an external contributor.
> +
> +## PMC changes:
> +
> + - Currently 11 PMC members.
> + - No new PMC members added in the last 3 months
> + - Last PMC addition was Dave Koelmeyer on Wed Apr 06 2016
> +
> +## Committer base changes:
> +
> + - Currently 16 committers.
> + - No new committers added in the last 3 months
> + - Last committer addition was Dave Koelmeyer at Wed Apr 06 2016
> +
> +## Releases:
> +
> + - Last release was 2.10.2 on Sat Feb 20 2016
> +
> +## JIRA activity:
> +
> + - 6 JIRA tickets created in the last 3 months
> + - 4 JIRA tickets closed/resolved in the last 3 months
> \ No newline at end of file
>

Re: [DRAFT] ASF Board Report for JSPWiki - January 2017

[Harry Metske]

+1

also on the doc git repo.

tx JP!

regards,
Harry


On 12 January 2017 at 09:34, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi all,
>
> please find below a draft of this quarter's Board report. If there aren't
> any objections, I'm planning on submitting it somewhere in between tonight
> and tomorrow morning.
>
> Also, I'm thinking in requesting another git repo for jspwiki's ASF-related
> documentation; right now, it would only have past board reports (we're
> still having them in svn..), and the board resolution from
> https://svn.apache.org/repos/asf/jspwiki/project-mgmt/ . The repo would be
> something like jspwiki-asf-docs? jspwiki-docs?
>
>
> best regards,
> juan pablo
>
> =
>
> ## Description:
>  - A feature-rich and extensible WikiWiki engine built around the standard
> JEE components (Java, servlets, JSP).
>
> ## Issues:
>  - there are no issues requiring board attention at this time.
>
> ## Activity:
>  - This quarter has been a silent one, with all the activity mostly
> happening
>on holidays (roughly, second half of December, first half of January)
>
> ## Health report:
>  - Apache JSPWiki remains as a 100% volunteer effort, so quiet periods like
>this one are not uncommon. There were commits from 2 individuals on this
>period.
>
>  - This quarter should have seen some movement regarding the transition of
>jspwiki.a.o from ASF's CMS to JSPWiki. I voluntereed for this task, but
>have been totally away for almost all the quarter, so no progress
> here...
>
>  - All questions on ML where answered, and there are enough people to
>provide project oversight. Finally, there weren't new blog posts on this
> quarter.
>
> ## PMC changes:
>
>  - Currently 11 PMC members.
>  - No new PMC members added in the last 3 months
>  - Last PMC addition was Dave Koelmeyer on Wed Apr 06 2016
>
> ## Committer base changes:
>
>  - Currently 16 committers.
>  - No new committers added in the last 3 months
>  - Last committer addition was Dave Koelmeyer at Wed Apr 06 2016
>
> ## Releases:
>
>  - Last release was 2.10.2 on Sat Feb 20 2016
>
> ## Mailing list activity:
>
>  - As outlined on the Activity section, this has been a quiet quarter,
> which
>reflects on ML statistics:
>
>  - dev@jspwiki.apache.org:
> - 87 subscribers (down -1 in the last 3 months):
> - 47 emails sent to list (84 in previous quarter)
>
>  - u...@jspwiki.apache.org:
> - 178 subscribers (up 0 in the last 3 months):
> - 28 emails sent to list (30 in previous quarter)
>
> ## JIRA activity:
>
>  - 7 JIRA tickets created in the last 3 months
>  - 6 JIRA tickets closed/resolved in the last 3 months
>

Re: jspwiki site git repo + git integration for JIRA

[Harry Metske]

works like a charm , +1

On 25 March 2017 at 17:04, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi,
>
> well, after requesting it, seems that ASF's CMS doesn't support having git
> as backend, so I've been this couple of days exploring alternatives.
>
> Other projects having their site stored on git build their site so that it
> gets generated on an specific folder (content) on an specific branch
> (asf-site). For me, Apache guacamole website git's repo (
> https://github.com/apache/incubator-guacamole-website) contains the most
> clear explanation on what is expected on the ASF-infra side for a project
> wanting to host its site on a git repo.
>
> As the jspwiki-site git repo has already been created, already stores
> site's sources, and I really thought it would be better to have all under
> git rather than a mix of svn and git, went ahead and looked around for
> other alternatives beyond ASF's CMS. Found JBake, and I was able to
> generate an static site reusing almost all the source from the CMS, with
> little effort. After all, this site is meant to serve as backup when we
> switch to JSPWiki itself as the main site.
>
> I've pushed two branches at jspwiki-site: jbake and asf-site. The former
> contains the source and instructions on how to build and test the site
> locally (mvn clean jbake:inline, but please take a look at it), whereas the
> latter is an orphan branch containing the generated site. If we are happy
> changing from CMS to a JBake generated site, we could set up a CI job
> responsible of publishing the site whenever the repo is changed (ci.sh file
> on the jbake repo). Apache Incubator or Apache Guacamole operate this way.
>
> I'm +1 on moving the site to git+jbake, as I find it way less cumbersome
> than operating with the CMS bookmarklet, and also knowing that it is a
> short term migration; whether we stay with this site or not, it's meant to
> be used as backup in case anything happens to the
> yet-to-come-but-in-the-near-future JSPWiki-based site.
>
> Opinions, other options, WDYT?
>
>
> br,
> juan pablo
>
> On Wed, Mar 22, 2017 at 6:52 AM, Siegfried Goeschl <
> siegfried.goes...@it20one.com> wrote:
>
> > +1
> >
> >
> > Siegfried Goeschl
> >
> > > On 21 Mar 2017, at 20:51, Juan Pablo Santos Rodríguez <
> > juanpablo.san...@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > I've requested a few minutes ago one more git repo, to host the CMS
> files
> > > (current site is still on svn). The idea of this repo is, once we've
> > moved
> > > the site to a JSPWiki instance, have an alternate, backup site, just in
> > > case.
> > >
> > > I've also stumbled upon ASF's Git integration with JIRA (
> > > https://reference.apache.org/pmc/svngit2jira). The idea is to mention
> a
> > > JIRA ticket inside a commit comment and have something like this:
> > > https://issues.apache.org/jira/browse/CLOUDSTACK-1638?
> > focusedCommentId=13662469=com.atlassian.jira.
> > plugin.system.issuetabpanels:comment-tabpanel#comment-13662469
> > > Any opinions about this, shall we request it? (I'm +1 to request it,
> > seems
> > > like a nice +1 to have)
> > >
> > >
> > > br,
> > > juan pablo
> >
> >
>

Re: jspwiki site git repo + git integration for JIRA

[Harry Metske]

+1

Regards,
Harry


Op 21 mrt. 2017 20:51 schreef "Juan Pablo Santos Rodríguez" <
juanpablo.san...@gmail.com>:

> Hi,
>
> I've requested a few minutes ago one more git repo, to host the CMS files
> (current site is still on svn). The idea of this repo is, once we've moved
> the site to a JSPWiki instance, have an alternate, backup site, just in
> case.
>
> I've also stumbled upon ASF's Git integration with JIRA (
> https://reference.apache.org/pmc/svngit2jira). The idea is to mention a
> JIRA ticket inside a commit comment and have something like this:
> https://issues.apache.org/jira/browse/CLOUDSTACK-1638?
> focusedCommentId=13662469=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-13662469
> Any opinions about this, shall we request it? (I'm +1 to request it, seems
> like a nice +1 to have)
>
>
> br,
> juan pablo
>

Re: Changing default template to Haddock

[Harry Metske]

+1
I am using the haddock template a long time already too.

Regards,
Harry


Op 23 jul. 2017 13:14 schreef "Juan Pablo Santos Rodríguez" <
juanpablo.san...@gmail.com>:

> Hi,
>
> I would be +1 on that. IMHO then version should be switched to 2.11.0? it
> will most probably imply changes for people with existing default-based
> templates, they should at least specify in jspwiki-custom.properties that
> they want the default template. And re-reading the last sentence, maybe we
> should also rename the default template to clean template or something
> along those lines?
>
>
> br,
> jp
>
> On Sun, Jul 23, 2017 at 12:59 PM, Dave Koelmeyer <
> dave.koelme...@davekoelmeyer.co.nz> wrote:
>
> > Hi All,
> >
> > Apologies if this change has already been made, but if not, what are
> > folks' thoughts about enabling Haddock as the default template for new
> > JSPWiki installations? The plain vanilla template is pretty long in the
> > tooth and certainly doesn't relay a good first impression out of the box.
> >
> > Cheers,
> > Dave
> >
> > --
> > Dave Koelmeyer
> > http://blog.davekoelmeyer.co.nz
> > GPG Key ID: 0x238BFF87
> >
> >
>

Re: Search down on us-wiki

[Harry Metske]

fixed.

It looked like I fixed the permissions of the jspwiki work dir last week,
but did not restart tomcat after that.
I deleted the lucene stuff and recycled tomcat.

cheers,
Harry



On 13 May 2017 at 17:43, Dirk Frederickx  wrote:

> Seems like the Search is not functioning anymore on
> https://jspwiki-wiki.apache.org.
> Also ajax search is not working
>
> Can someone have a look at this ?
>
>
> dirk
>

Re: haddock-based version of jspwiki.apache.org

[Harry Metske]

just did the build and test locally, looks good to me.

tx,
Harry

On 27 June 2017 at 00:15, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> quick update,
>
> went through the .js code and found out the issue causing the glitch with
> the Accordion fx. It's fixed now on the jbake-haddock branch at
> https://git-wip-us.apache.org/repos/asf?p=jspwiki-site.git
>
> Would anyone mind on testing this version of jspwiki.a.o? Is it ready to
> replace our current site? This would left us with an static site of one
> page (homepage) + apidocs. The rest of the site would be served by the wiki
> (current content would also be generated, but wouldn't be linked from
> anywhere).
>
>
> best regards,
> jp
>
> On Mon, Jun 26, 2017 at 9:07 PM, Juan Pablo Santos Rodríguez <
> juanpablo.san...@gmail.com> wrote:
>
> > Hi!
> >
> > I've just pushed a haddock-based site version of jspwiki.apache.org
> > (branch jbake-haddock). As talked a few(?) months ago, the idea was to
> > retrieve the jbake-based website, as means of backup and publishing
> > apidocs, so this version is essentially the home page linking to the main
> > wiki wherever possible. The whole content of the actual site is also
> > generated, in case there's some emergency and the wiki isn't available.
> >
> > The site is almost complete, the only thing lacking is the accordion
> > effect on the sidebar's sections - it is completely missing. Would anyone
> > mind taking a look at what's happening in there and why the accordions
> > don't get animated (git checkout jbake-haddock + change site.host
> property
> > at src/main/jbake/jbake.properties + mvn jbake:inline +
> > http://localhost:8080)? I've used the haddock.js file generated by the
> > main build but, as it is compressed, I'm clueless on what's going on :-?
> > The rest of the fx seem to be ok, i.e., the header (dis)appears, the
> search
> > dialog is there, etc.
> >
> >
> > thanks in advance,
> > jp
> >
>

Re: [jira] [Created] (JSPWIKI-1063) Replace nekohtml with a different parser

[Harry Metske]

I would agree with that.
Do we then have to shift our jdk requirement to 7 or 8?
Our current requirement is Jdk 6 if I m correct (which is very old now)

Regards,
Harry


On Aug 29, 2017 00:14, "Jürgen Weber (JIRA)"  wrote:

> Jürgen Weber created JSPWIKI-1063:
> -
>
>  Summary: Replace nekohtml with a different parser
>  Key: JSPWIKI-1063
>  URL: https://issues.apache.org/jira/browse/JSPWIKI-1063
>  Project: JSPWiki
>   Issue Type: Improvement
>   Components: Core & storage
> Reporter: Jürgen Weber
> Priority: Minor
>
>
> JSPWiki has a dependency on Xerces XML parser via nekohtml.
>
> Necohtml is used for parsing the HTML that a Wysiwyg Editor produces.
>
> nekohtml should be replaced by a different implementation that has no
> large dependencies and should use the JDK XML Parser.
>
>
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)
>

Re: [jira] [Resolved] (JSPWIKI-1064) Link to non-existing page doesn't change if linked page is created

[Harry Metske]

This version of JSPWiki (2.10.3-git-45) has just been activated on
https://jspwiki-wiki.apache.org .

I also refreshed the dockerized version
 (Alpine: 3.3=>3.7
 Tomcat: 8.5.15=>8.5.24 JSPWiki: 2.10.3-git-29 => 2.10.3-git-45) .

cheers,
Harry

On 16 December 2017 at 20:26, Juan Pablo Santos Rodríguez (JIRA) <
j...@apache.org> wrote:

>
>  [ https://issues.apache.org/jira/browse/JSPWIKI-1064?page=
> com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Juan Pablo Santos Rodríguez resolved JSPWIKI-1064.
> --
>Resolution: Fixed
> Fix Version/s: 2.10.3
>
> Hi Christian,
>
> would you mind trying on 2.10.3-git-45? it should fix this issue.
>
> When a page is saved, and the cache is active, there's a process which
> looks for all the page referers, in order to wipe them from the cache, so
> they don't keep showing an outdated edit link. The problem was, in those
> cases we were asking for an incorrect key on the cache, using only the
> name, whereas the cache stores the page renders using as a key the name and
> the version. As of 2.10.3-git-45, we only wipe from cache referers' last
> version, which should be more than enough..
>
> Also, page renders are now taken/put from the cache only when there is a
> view ongoing (WikiContext is WikiContext.VIEW), doesn't make sense on other
> contexts/actions (i.e., attach, edit, preview etc.) where the page content
> / metadata / attachments may change.
>
> > Link to non-existing page doesn't change if linked page is created
> > --
> >
> > Key: JSPWIKI-1064
> > URL: https://issues.apache.org/jira/browse/JSPWIKI-1064
> > Project: JSPWiki
> >  Issue Type: Bug
> >  Components: Core & storage
> >Affects Versions: 2.10.3
> > Environment: Redhat Enterprise Linux 7; Tomcat 6;
> > Client: Internet explorer
> >Reporter: Christian Fröhler
> >Priority: Minor
> > Fix For: 2.10.3
> >
> >
> > Background:
> > Links to non-existing pages in the same wiki look differently than links
> to existing pages.
> > Clicking on a link to a non-existing page leads directly to the "Edit"
> View so that the page can easily be created.
> > Problem:
> > After the non-existing page has been created, the Link to that new page
> is still shown in the same way as a link to a non-existing page; Clicking
> the link leads to the Edit view
> > To Reproduce:
> > 1) On an existing page ("page1") create a link to a non-existing page
> ("page2")
> >  --> the link to "page2" is visible on "page1" and correctly shows
> up as a link to a non-existing page
> > 2) Create "page2", and save it
> > 3) Visit again "page1"
> > Expected behavior: Link to page2 shows up as a normal link; clicking
> the link leads to the page2 in view mode
> > Actual behavior: Link to page2 shows up as a link to a non-existing
> page; clicking the link leads to the Edit mode of page 2
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)
>

Re: 2.10.4?

[Harry Metske]

same for me too

tx,
Harry


Op zo 13 mei 2018 om 14:04 schreef Dirk Frederickx <
dirk.frederi...@gmail.com>

> +1 for 2.10.4 release.
> Much appreciated if you'd continue to take care of the delivery,  unless
> anybody else volunteers.
>
> dirk
>
>
> On Fri, May 11, 2018 at 8:56 PM Juan Pablo Santos Rodríguez <
> juanpablo.san...@gmail.com> wrote:
>
> > Hi all,
> >
> > as we're heading into mid-may now, it's time for 2.10.4, following our
> > release-each-quarter train. Current master seems ok, latest haddock
> > improvements on mobile are awesome and there are a couple of fixes
> > regarding ACLs and caching among a few others, so releasing seems
> > reasonable anyway. I'd like to begin the release next Wednesday if
> > possible.
> >
> > I'd also like to ask for a volunteer to act as a RM for this release
> (I'll
> > step up if nobody does). It's a pretty straightforward process,
> documented
> > at https://jspwiki-wiki.apache.org/Wiki.jsp?page=How%20to%20release and
> of
> > course I'll be helping with anything needed, there isn't a fixed date for
> > the release so it's ok if the release takes a little longer..
> >
> > thoughts?
> >
> >
> > br,
> > juan pablo
> >
>

Re: [jira] ASF subversion and git services mentioned you on JSPWIKI-835 (JIRA) (JIRA)

[Harry Metske]

I did :-) , in the previous mail.
But here it is again:




On 28 April 2018 at 17:50, Dirk Frederickx <dirk.frederi...@gmail.com>
wrote:

> Can you share a screenshot ?
> dirk
>
> On Sat, Apr 28, 2018 at 5:13 PM, Harry Metske <harry.met...@gmail.com>
> wrote:
>
> > this is both on Chrome and Safari on MacOS...
> >
> > On 28 April 2018 at 17:12, Harry Metske <harry.met...@gmail.com> wrote:
> >
> > > I was just testing this , but it gives me a blue "overlay" when I try
> to
> > > edit pages.
> > >
> > > see attachment
> > >
> > > cheers,
> > > Harry
> > >
> > >
> > > On 28 April 2018 at 17:10, Dirk Frederickx <dirk.frederi...@gmail.com>
> > > wrote:
> > >
> > >> All,
> > >>
> > >> With the last 2 commits, I've added support for mobile devices to the
> > >> Haddock Template.   (long overdue request)
> > >>
> > >> Would it be possible to refresh https://jspwiki-wiki.apache.org ; to
> > >> collect feedback ?
> > >>
> > >>
> > >> dirk
> > >>
> > >> On Sat, Apr 28, 2018 at 4:49 PM, ASF subversion and git services
> (JIRA)
> > <
> > >> j...@apache.org> wrote:
> > >>
> > >> >
> > >> >  [ https://issues.apache.org/jira/browse/JSPWIKI-835?page=
> > >> > com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> > >> >
> > >> > ASF subversion and git services mentioned you on JSPWIKI-835
> > >> > 
> > >> >
> > >> > Commit cba943d3a8d9f8df358a322a7207f4b63e2190fe in jspwiki's branch
> > >> > refs/heads/master from [~brushed]
> > >> > [ https://gitbox.apache.org/repos/asf?p=jspwiki.git;h=cba943d ]
> > >> >
> > >> > 2.10.4-git-09  Better support for mobile devices in HADDOCK
> > >> >
> > >> > 2.10.4-git-09   / see JSPWIKI-835
> > >> >  - Update various styles to better fit small screens.
> > >> > - Update SIDEBAR open/close behaviour for small screens.
> > >> >
> > >> >
> > >> > > Key: JSPWIKI-835
> > >> >
> > >> > > View Online: https://issues.apache.org/jira
> > >> /browse/JSPWIKI-835
> > >> > > Add Comment: https://issues.apache.org/
> > >> > jira/browse/JSPWIKI-835#add-comment
> > >> >
> > >> > Hint: You can mention someone in an issue description or comment by
> > >> > typing  "@" in front of their username.
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > This message was sent by Atlassian JIRA
> > >> > (v7.6.3#76005)
> > >> >
> > >>
> > >
> > >
> >
>

Re: [jira] ASF subversion and git services mentioned you on JSPWIKI-835 (JIRA) (JIRA)

[Harry Metske]

I was just testing this , but it gives me a blue "overlay" when I try to
edit pages.

see attachment

cheers,
Harry


On 28 April 2018 at 17:10, Dirk Frederickx 
wrote:

> All,
>
> With the last 2 commits, I've added support for mobile devices to the
> Haddock Template.   (long overdue request)
>
> Would it be possible to refresh https://jspwiki-wiki.apache.org ; to
> collect feedback ?
>
>
> dirk
>
> On Sat, Apr 28, 2018 at 4:49 PM, ASF subversion and git services (JIRA) <
> j...@apache.org> wrote:
>
> >
> >  [ https://issues.apache.org/jira/browse/JSPWIKI-835?page=
> > com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> >
> > ASF subversion and git services mentioned you on JSPWIKI-835
> > 
> >
> > Commit cba943d3a8d9f8df358a322a7207f4b63e2190fe in jspwiki's branch
> > refs/heads/master from [~brushed]
> > [ https://gitbox.apache.org/repos/asf?p=jspwiki.git;h=cba943d ]
> >
> > 2.10.4-git-09  Better support for mobile devices in HADDOCK
> >
> > 2.10.4-git-09   / see JSPWIKI-835
> >  - Update various styles to better fit small screens.
> > - Update SIDEBAR open/close behaviour for small screens.
> >
> >
> > > Key: JSPWIKI-835
> >
> > > View Online: https://issues.apache.org/jira/browse/JSPWIKI-835
> > > Add Comment: https://issues.apache.org/
> > jira/browse/JSPWIKI-835#add-comment
> >
> > Hint: You can mention someone in an issue description or comment by
> > typing  "@" in front of their username.
> >
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v7.6.3#76005)
> >
>

Re: [jira] ASF subversion and git services mentioned you on JSPWIKI-835 (JIRA) (JIRA)

[Harry Metske]

this is both on Chrome and Safari on MacOS...

On 28 April 2018 at 17:12, Harry Metske <harry.met...@gmail.com> wrote:

> I was just testing this , but it gives me a blue "overlay" when I try to
> edit pages.
>
> see attachment
>
> cheers,
> Harry
>
>
> On 28 April 2018 at 17:10, Dirk Frederickx <dirk.frederi...@gmail.com>
> wrote:
>
>> All,
>>
>> With the last 2 commits, I've added support for mobile devices to the
>> Haddock Template.   (long overdue request)
>>
>> Would it be possible to refresh https://jspwiki-wiki.apache.org ; to
>> collect feedback ?
>>
>>
>> dirk
>>
>> On Sat, Apr 28, 2018 at 4:49 PM, ASF subversion and git services (JIRA) <
>> j...@apache.org> wrote:
>>
>> >
>> >  [ https://issues.apache.org/jira/browse/JSPWIKI-835?page=
>> > com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>> >
>> > ASF subversion and git services mentioned you on JSPWIKI-835
>> > 
>> >
>> > Commit cba943d3a8d9f8df358a322a7207f4b63e2190fe in jspwiki's branch
>> > refs/heads/master from [~brushed]
>> > [ https://gitbox.apache.org/repos/asf?p=jspwiki.git;h=cba943d ]
>> >
>> > 2.10.4-git-09  Better support for mobile devices in HADDOCK
>> >
>> > 2.10.4-git-09   / see JSPWIKI-835
>> >  - Update various styles to better fit small screens.
>> > - Update SIDEBAR open/close behaviour for small screens.
>> >
>> >
>> > > Key: JSPWIKI-835
>> >
>> > > View Online: https://issues.apache.org/jira
>> /browse/JSPWIKI-835
>> > > Add Comment: https://issues.apache.org/
>> > jira/browse/JSPWIKI-835#add-comment
>> >
>> > Hint: You can mention someone in an issue description or comment by
>> > typing  "@" in front of their username.
>> >
>> >
>> >
>> >
>> > --
>> > This message was sent by Atlassian JIRA
>> > (v7.6.3#76005)
>> >
>>
>
>

Re: [VOTE] Release JSPWiki version 2.10.4

[Harry Metske]

+1

On 21 May 2018 at 13:31, Dirk Frederickx  wrote:

> Juan,  tx for pushing the release.
>
> +1
>
>
> dirk
>
> On Mon, May 21, 2018 at 10:55 AM Dave Koelmeyer <
> dave.koelme...@davekoelmeyer.co.nz> wrote:
>
> > +1
> >
> > --
> > Dave Koelmeyer
> > http://blog.davekoelmeyer.co.nz
> > GPG Key ID: 0x238BFF87
> > The Document Foundation (TDF) member
> >
> >
> > On 21/05/18 07:11, Juan Pablo Santos Rodríguez wrote:
> > > This is a release vote for Apache JSPWiki, version 2.10.4. The vote
> will
> > be
> > > open for at least 72 hours from now.
> > >
> > > It fixes the following issues:
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12310732=12342771
> > >
> > > Note that we are voting upon the source (tag), binaries are provided
> for
> > > convenience.
> > >
> > > Everybody is encouraged to vote.
> > >
> > > Source and binary files:
> > > https://dist.apache.org/repos/dist/dev/jspwiki/2.10.4-rc3
> > >
> > > Nexus staging repo:
> > > https://repository.apache.org/content/repositories/
> orgapachejspwiki-1005
> > >
> > > The tag to be voted upon:
> > > https://github.com/apache/jspwiki/tree/2.10.4-RC3
> > >
> > > JSPWiki's KEYS file containing PGP keys we use to sign the release:
> > > https://www.apache.org/dist/jspwiki/KEYS
> > >
> > > *** Please download, test and vote:
> > >
> > > [ ] +1 Approve the release
> > > [ ]  0 Don't mind
> > > [ ] -1 Disapprove the release (please provide specific comments)
> > >
> >
> >
>

Re: 2.10.4?

[Harry Metske]

thanks for the update ( and all the work)

regards
Harry


Op do 17 mei 2018 om 00:03 schreef Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com>

> Hi,
>
> due to some connectivity issues with my dsl connection this afternoon, I've
> been unable to prepare the vote until a while ago. Right now ASF's nexus
> repository seems to also be having some issues, so I can't close the
> staging repo, because I can't find it. May be it is because there have been
> several hours between mvn release:prepare and mvn release:perform, or
> because it is not exactly responsive right now, or because who knows.. I'll
> send an a-mail to infra in a while and will continue tomorrow afternoon, in
> order to start the release vote, as soon I'm able to.
>
>
> best regards,
> juan pablo
>
> On Mon, May 14, 2018 at 3:49 PM, Harry Metske <harry.met...@gmail.com>
> wrote:
>
> > same for me too
> >
> > tx,
> > Harry
> >
> >
> > Op zo 13 mei 2018 om 14:04 schreef Dirk Frederickx <
> > dirk.frederi...@gmail.com>
> >
> > > +1 for 2.10.4 release.
> > > Much appreciated if you'd continue to take care of the delivery,
> unless
> > > anybody else volunteers.
> > >
> > > dirk
> > >
> > >
> > > On Fri, May 11, 2018 at 8:56 PM Juan Pablo Santos Rodríguez <
> > > juanpablo.san...@gmail.com> wrote:
> > >
> > > > Hi all,
> > > >
> > > > as we're heading into mid-may now, it's time for 2.10.4, following
> our
> > > > release-each-quarter train. Current master seems ok, latest haddock
> > > > improvements on mobile are awesome and there are a couple of fixes
> > > > regarding ACLs and caching among a few others, so releasing seems
> > > > reasonable anyway. I'd like to begin the release next Wednesday if
> > > > possible.
> > > >
> > > > I'd also like to ask for a volunteer to act as a RM for this release
> > > (I'll
> > > > step up if nobody does). It's a pretty straightforward process,
> > > documented
> > > > at https://jspwiki-wiki.apache.org/Wiki.jsp?page=How%20to%20release
> > and
> > > of
> > > > course I'll be helping with anything needed, there isn't a fixed date
> > for
> > > > the release so it's ok if the release takes a little longer..
> > > >
> > > > thoughts?
> > > >
> > > >
> > > > br,
> > > > juan pablo
> > > >
> > >
> >
>

Re: [apache/jspwiki] Clickable buttons (#1)

[Harry Metske]

I had seen it before on the dev list.
But since it was mostly frontend, I did not comment.

cheers,
Harry


On Tue, 29 May 2018 at 00:40, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi,
>
> I was looking for the below mail at [user|dev|commits]@jspwiki.a.o. As I
> can't see it through Pony Mail, I'm resending over
> dev. Would anyone mind confirming if this is the first time receiving the
> e-mail? (if not, apologies for the noise).
>
> And regarding the PR itself, any thoughts on it? I find it useful, esp. for
> mobile devices, and would be +1 for merging it,
> but I don't have a strong opinion on it, frontend isn't one of my key
> points..
>
>
> thanks in advance,
> juan pablo
>
>
> -- Forwarded message --
> From: jonasmue 
> Date: Fri, May 25, 2018 at 1:35 PM
> Subject: [apache/jspwiki] Clickable buttons (#1)
> To: apache/jspwiki 
> Cc: Subscribed 
>
>
> Made header buttons clickable instead of hoverable. This change should
> result in increased usability since the opening boxes frequently would have
> been closed involuntarily if user's mouse movement was not precise enough
> after hovering over the buttons. Removed the carets for consistency reasons
> as they indicate a hoverable target.
> --
> You can view, comment on, or merge this pull request online at:
>
>   https://github.com/apache/jspwiki/pull/1
> Commit Summary
>
>- Clickable header buttons
>- Updated to current state and removed other changes
>- Changed indentation to original form
>
> File Changes
>
>- *M* jspwiki-war/src/main/scripts/wiki/Wiki.js
> (35)
>- *M* jspwiki-war/src/main/webapp/templates/haddock/SearchBox.jsp
> (4)
>- *M* jspwiki-war/src/main/webapp/templates/haddock/UserBox.jsp
> (4)
>
> Patch Links:
>
>- https://github.com/apache/jspwiki/pull/1.patch
>- https://github.com/apache/jspwiki/pull/1.diff
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> , or mute the thread
> <
> https://github.com/notifications/unsubscribe-auth/ABKX4v23eYQ0kCinSJj1cWhts1HVqYbUks5t1-yBgaJpZM4UN0uj
> >
> .
>

Re: [apache/jspwiki] Clickable buttons (#1)

[Harry Metske]

yup, I ll do that somewhere today

cheers,
Harry

Op wo 20 jun. 2018 om 19:40 schreef Dirk Frederickx <
dirk.frederi...@gmail.com>

> Harry, Juan,
>
> I made a commit earlier this week to resolve the hover/clickable buttons
> for devices with a touch-interface.
> Would it be possible to push the update to jspwiki-wiki.apache.org .
> Testing was done on iPad/iPhone,  but I'd like to get feedback on other
> types of touch devices.
>
>
> Not sure how to close the issue on github.
>
>
> br,
>     dirk
>
>
>
> On Tue, May 29, 2018 at 6:45 PM Harry Metske 
> wrote:
>
> > I had seen it before on the dev list.
> > But since it was mostly frontend, I did not comment.
> >
> > cheers,
> > Harry
> >
> >
> > On Tue, 29 May 2018 at 00:40, Juan Pablo Santos Rodríguez <
> > juanpablo.san...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > I was looking for the below mail at [user|dev|commits]@jspwiki.a.o. As
> I
> > > can't see it through Pony Mail, I'm resending over
> > > dev. Would anyone mind confirming if this is the first time receiving
> the
> > > e-mail? (if not, apologies for the noise).
> > >
> > > And regarding the PR itself, any thoughts on it? I find it useful, esp.
> > for
> > > mobile devices, and would be +1 for merging it,
> > > but I don't have a strong opinion on it, frontend isn't one of my key
> > > points..
> > >
> > >
> > > thanks in advance,
> > > juan pablo
> > >
> > >
> > > -- Forwarded message --
> > > From: jonasmue 
> > > Date: Fri, May 25, 2018 at 1:35 PM
> > > Subject: [apache/jspwiki] Clickable buttons (#1)
> > > To: apache/jspwiki 
> > > Cc: Subscribed 
> > >
> > >
> > > Made header buttons clickable instead of hoverable. This change should
> > > result in increased usability since the opening boxes frequently would
> > have
> > > been closed involuntarily if user's mouse movement was not precise
> enough
> > > after hovering over the buttons. Removed the carets for consistency
> > reasons
> > > as they indicate a hoverable target.
> > > --
> > > You can view, comment on, or merge this pull request online at:
> > >
> > >   https://github.com/apache/jspwiki/pull/1
> > > Commit Summary
> > >
> > >- Clickable header buttons
> > >- Updated to current state and removed other changes
> > >- Changed indentation to original form
> > >
> > > File Changes
> > >
> > >- *M* jspwiki-war/src/main/scripts/wiki/Wiki.js
> > ><https://github.com/apache/jspwiki/pull/1/files#diff-0> (35)
> > >- *M* jspwiki-war/src/main/webapp/templates/haddock/SearchBox.jsp
> > ><https://github.com/apache/jspwiki/pull/1/files#diff-1> (4)
> > >- *M* jspwiki-war/src/main/webapp/templates/haddock/UserBox.jsp
> > ><https://github.com/apache/jspwiki/pull/1/files#diff-2> (4)
> > >
> > > Patch Links:
> > >
> > >- https://github.com/apache/jspwiki/pull/1.patch
> > >- https://github.com/apache/jspwiki/pull/1.diff
> > >
> > > —
> > > You are receiving this because you are subscribed to this thread.
> > > Reply to this email directly, view it on GitHub
> > > <https://github.com/apache/jspwiki/pull/1>, or mute the thread
> > > <
> > >
> >
> https://github.com/notifications/unsubscribe-auth/ABKX4v23eYQ0kCinSJj1cWhts1HVqYbUks5t1-yBgaJpZM4UN0uj
> > > >
> > > .
> > >
> >
>

Re: [jira] ASF subversion and git services mentioned you on JSPWIKI-835 (JIRA) (JIRA)

[Harry Metske]

)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:474)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:624)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:349)
at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:478)
at
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:789)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1437)
at
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)


On 28 April 2018 at 18:37, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi,
>
> I think attachments are stripped while delivered by the ML.. FWIW I'm also
> getting a blue overlay on
> edit on windows+[firefox|chrome|edge], uploaded an screenshot here:
> https://ibb.co/fvDrBx
>
>
>
> br,
> juan pablo
>
> On Sat, Apr 28, 2018 at 5:54 PM, Harry Metske <harry.met...@gmail.com>
> wrote:
>
> > I did :-) , in the previous mail.
> > But here it is again:
> >
> >
> >
> >
> > On 28 April 2018 at 17:50, Dirk Frederickx <dirk.frederi...@gmail.com>
> > wrote:
> >
> >> Can you share a screenshot ?
> >> dirk
> >>
> >> On Sat, Apr 28, 2018 at 5:13 PM, Harry Metske <harry.met...@gmail.com>
> >> wrote:
> >>
> >> > this is both on Chrome and Safari on MacOS...
> >> >
> >> > On 28 April 2018 at 17:12, Harry Metske <harry.met...@gmail.com>
> wrote:
> >> >
> >> > > I was just testing this , but it gives me a blue "overlay" when I
> try
> >> to
> >> > > edit pages.
> >> > >
> >> > > see attachment
> >> > >
> >> > > cheers,
> >> > > Harry
> >> > >
> >> > >
> >> > > On 28 April 2018 at 17:10, Dirk Frederickx <
> dirk.frederi...@gmail.com
> >> >
> >> > > wrote:
> >> > >
> >> > >> All,
> >> > >>
> >> > >> With the last 2 commits, I've added support for mobile devices to
> the
> >> > >> Haddock Template.   (long overdue request)
> >> > >>
> >> > >> Would it be possible to refresh https://jspwiki-wiki.apache.org ;
> to
> >> > >> collect feedback ?
> >> > >>
> >> > >>
> >> > >> dirk
> >> > >>
> >> > >> On Sat, Apr 28, 2018 at 4:49 PM, ASF subversion and git services
> >> (JIRA)
> >> > <
> >> > >> j...@apache.org> wrote:
> >> > >>
> >> > >> >
> >> > >> >  [ https://issues.apache.org/jira/browse/JSPWIKI-835?page=
> >> > >> > com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> >> > >> >
> >> > >> > ASF subversion and git services mentioned you on JSPWIKI-835
> >> > >> > 
> >> > >> >
> >> > >> > Commit cba943d3a8d9f8df358a322a7207f4b63e2190fe in jspwiki's
> >> branch
> >> > >> > refs/heads/master from [~brushed]
> >> > >> > [ https://gitbox.apache.org/repos/asf?p=jspwiki.git;h=cba943d ]
> >> > >> >
> >> > >> > 2.10.4-git-09  Better support for mobile devices in HADDOCK
> >> > >> >
> >> > >> > 2.10.4-git-09   / see JSPWIKI-835
> >> > >> >  - Update various styles to better fit small screens.
> >> > >> > - Update SIDEBAR open/close behaviour for small screens.
> >> > >> >
> >> > >> >
> >> > >> > > Key: JSPWIKI-835
> >> > >> >
> >> > >> > > View Online: https://issues.apache.org/jira
> >> > >> /browse/JSPWIKI-835
> >> > >> > > Add Comment: https://issues.apache.org/
> >> > >> > jira/browse/JSPWIKI-835#add-comment
> >> > >> >
> >> > >> > Hint: You can mention someone in an issue description or comment
> by
> >> > >> > typing  "@" in front of their username.
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >> > --
> >> > >> > This message was sent by Atlassian JIRA
> >> > >> > (v7.6.3#76005)
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >
> >
>

Re: [jira] ASF subversion and git services mentioned you on JSPWIKI-835 (JIRA) (JIRA)

[Harry Metske]

I just deployed 2.10.4-git-10 to https://jspwiki-wiki.apache.org

cheers,
Harry


On 28 April 2018 at 19:20, Harry Metske <harry.met...@gmail.com> wrote:

> with the latest patch on plain.jsp the blue overlay is gone, but now I m
> getting this stacktrace on each request (I will check some more, maybe it
> is something local):
>
> 2018-04-28 19:19:22,201 ERROR wiki.WikiEngine - Unable to fetch page info
> org.apache.wiki.api.exceptions.ProviderException: Illegal page name ''
> at org.apache.wiki.PageManager.getPageInfo(PageManager.java:403)
> at org.apache.wiki.WikiEngine.getPage(WikiEngine.java:1890)
> at org.apache.wiki.WikiEngine.getPage(WikiEngine.java:1870)
> at org.apache.wiki.attachment.AttachmentManager.getAttachmentInfo(
> AttachmentManager.java:327)
> at org.apache.wiki.attachment.AttachmentManager.getAttachmentInfo(
> AttachmentManager.java:235)
> at org.apache.wiki.WikiEngine.getPage(WikiEngine.java:1894)
> at org.apache.wiki.WikiEngine.getPage(WikiEngine.java:1870)
> at org.apache.wiki.tags.LinkTag.figureOutURL(LinkTag.java:284)
> at org.apache.wiki.tags.LinkTag.doEndTag(LinkTag.java:424)
> at org.apache.jsp.templates.haddock.commonheader_jsp._
> jspx_meth_wiki_005fLink_005f3(commonheader_jsp.java:906)
> at org.apache.jsp.templates.haddock.commonheader_jsp._
> jspService(commonheader_jsp.java:290)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at org.apache.jasper.servlet.JspServletWrapper.service(
> JspServletWrapper.java:443)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(
> JspServlet.java:385)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:329)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> ApplicationFilterChain.java:230)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:165)
> at org.apache.catalina.core.ApplicationDispatcher.invoke(
> ApplicationDispatcher.java:726)
> at org.apache.catalina.core.ApplicationDispatcher.doInclude(
> ApplicationDispatcher.java:592)
> at org.apache.catalina.core.ApplicationDispatcher.include(
> ApplicationDispatcher.java:526)
> at org.apache.jasper.runtime.JspRuntimeLibrary.include(
> JspRuntimeLibrary.java:887)
> at org.apache.jasper.runtime.PageContextImpl.include(
> PageContextImpl.java:647)
> at org.apache.wiki.tags.IncludeTag.doEndTag(IncludeTag.java:84)
> at org.apache.jsp.templates.haddock.ViewTemplate_jsp._
> jspx_meth_wiki_005fInclude_005f0(ViewTemplate_jsp.java:490)
> at org.apache.jsp.templates.haddock.ViewTemplate_jsp._
> jspService(ViewTemplate_jsp.java:179)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at org.apache.jasper.servlet.JspServletWrapper.service(
> JspServletWrapper.java:443)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(
> JspServlet.java:385)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:329)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> ApplicationFilterChain.java:230)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:165)
> at org.apache.catalina.core.ApplicationDispatcher.invoke(
> ApplicationDispatcher.java:726)
> at org.apache.catalina.core.ApplicationDispatcher.doInclude(
> ApplicationDispatcher.java:592)
> at org.apache.catalina.core.ApplicationDispatcher.include(
> ApplicationDispatcher.java:526)
> at org.apache.jasper.runtime.JspRuntimeLibrary.include(
> JspRuntimeLibrary.java:887)
> at org.apache.jasper.runtime.PageContextImpl.include(
> PageContextImpl.java:647)
> at org.apache.wiki.tags.IncludeTag.doEndTag(IncludeTag.java:84)
> at org.apache.jsp.Wiki_jsp._jspService(Wiki_jsp.java:181)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at org.apache.jasper.servlet.JspServletWrapper.service(
> JspServletWrapper.java:443)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(
> JspServlet.java:385)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:329)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> ApplicationFilterChain.java:230)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:165)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at org.apache.cata

Re: Proposed ASF Board report for 2018/01

[Harry Metske]

Minor typo in the bullet about the test-jar.
For the rest +1

Tx,
Harry

Op 7 jan. 2018 22:36 schreef "Juan Pablo Santos Rodríguez" <
juanpablo.san...@gmail.com>:

> Hi,
>
> below is the proposed ASF Board report for 2018/01, I'm pushing it to
> the appropiate git repo ina  minute. I plan to send it by January 10th,
> as usual please review, comment, add, edit whatever you feel necessary.
>
>
> br,
> juan pablo
>
> ==
>
> ## Description:
>  - A feature-rich and extensible WikiWiki engine built around the standard
> JEE components (Java, servlets, JSP).
>
> ## Issues:
>  - there are no issues requiring board attention at this time.
>
> ## Activity:
>  - Compared to last report, there has been an up-tick in activity this
>quarter, where activity has been focused on these areas:
>* Initial support for Markdown: there is a new custom parser + renderer
>  for Markdown, although not complete yet (see
>  https://jspwiki-wiki.apache.org/Wiki.jsp?page=Markdown%20Support for
>  details)
>* Fixed a bug regarding the renderer cache (JSPWIKI-1064)
>* Tests were migrated from JUnit 3 to JUnit 4
>* Generation of a test-jar, with several with utilities to ease testing
>  of JSPWiki custom components.
>  - No questions unanswered on MLs, with at least 3 people from PMC showing
>up there.
>
> ## Health report:
>  - Last report highlighted some ideas to increase contributions:
>* move to Github as primary repo: done; we're also encouraging the use
> of
>  jspwiki as a topic on GitHub to increase contributions' visibility.
>* adopting something similar to a release train: we should release
> 2.10.3
>  next February.
>* lower committership barrier by granting commits rights to
>  a) any ASF committer.
>  b) any other people who simply asks for it.
>  Other than discussing the idea, we haven't done anything, as nobody
> new
>  has showed up yet..
>
> ## PMC changes:
>
>  - Currently 11 PMC members.
>  - No new PMC members added in the last 3 months
>  - Last PMC addition was Dave Koelmeyer on Wed Apr 06 2016
>
> ## Committer base changes:
>
>  - Currently 16 committers.
>  - No new committers added in the last 3 months
>  - Last committer addition was Dave Koelmeyer at Wed Apr 06 2016
>
> ## Releases:
>
>  - Last release was 2.10.2 on Sat Feb 20 2016
>
> ## Mailing list activity:
>
>  - dev@jspwiki.apache.org:
> - 83 subscribers (down -2 in the last 3 months):
> - 40 emails sent to list (39 in previous quarter)
>
>  - u...@jspwiki.apache.org:
> - 176 subscribers (down -2 in the last 3 months):
> - 52 emails sent to list (10 in previous quarter)
>
> ## JIRA activity:
>
>  - 1 JIRA tickets created in the last 3 months
>  - 3 JIRA tickets closed/resolved in the last 3 months
>

Re: [VOTE] Release JSPWiki version 2.10.3

[Harry Metske]

The CommentedPropertiesTest fails (as stated earlier on the ML).
It fails both on Linux and MacOS.
It can be easily fixed by removing the carriage returns. (send the file
through   tr -d '\r' ), then the tests succeed on both platforms. (I can't
test Windows).
Do you want me to commit these changes ? (on master ?)

For the rest all OK, and my vote:  +1

regards,
Harry


On 10 February 2018 at 01:37, Juan Pablo Santos Rodríguez <
juanpa...@apache.org> wrote:

> Hi all,
>
> this is a release vote for Apache JSPWiki, version 2.10.3. The vote
> will be open for at least 72 hours from now.
>
> It fixes the following issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12310732=12334934
>
> Note that we are voting upon the source (tag), binaries are provided
> for convenience.
>
> Everybody is encouraged to vote.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/jspwiki/2.10.3-RC2
>
> Nexus staging repo:
> https://repository.apache.org/content/repositories/orgapachejspwiki-1003
>
> The tag to be voted upon:
> https://github.com/apache/jspwiki/tree/2.10.3-RC2
>
> JSPWiki's KEYS file containing PGP keys we use to sign the release:
> https://www.apache.org/dist/jspwiki/KEYS
>
> *** Please download, test and vote:
>
> [ ] +1 Approve the release
> [ ]  0 Don't mind
> [ ] -1 Disapprove the release (please provide specific comments)
>
>
> br,
> juan pablo
>

Re: release plan for 2.10.3

[Harry Metske]

done, jspwiki-wiki.a.o is now at 2.10.3-git-48

cheers,
Harry

On 5 February 2018 at 00:15, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi Harry,
>
> that would be nice too, in fact, as most probably the RC is going to be
> based on 2.10.3-git-48, we could already deploy it to jspwiki-wiki.a.o..
> O:-D
>
>
> br,
> juan pablo
>
> On Sun, Feb 4, 2018 at 10:21 PM, Harry Metske <harry.met...@gmail.com>
> wrote:
>
> > Sounds good to me.
> > And what about deploying this release candidate to jspwiki-wiki.a.o ?
> >
> > Cheers,
> > Harry
> >
> > > Op 4 feb. 2018 om 21:02 heeft Juan Pablo Santos Rodríguez <
> > juanpablo.san...@gmail.com> het volgende geschreven:
> > >
> > > Hi,
> > >
> > > as stated on past boards reports, we're going to adopt a release train
> > > model, aiming to release from master every Feb/May/Sep/Nov, IIRC.
> > >
> > > so, how about reviewing current master for a few days, let's say until
> > next
> > > 8th, so the vote can be run through next weekend and, hopefully,
> > releasing
> > > 2.10.3 on ~12th? sounds reasonable?
> > >
> > >
> > > best regards,
> > > juan pablo
> >
>

Re: JSPWiki github repos descriptions + topics

[Harry Metske]

sounds good, maybe add a tag "docker" ?

cheers,
Harry

On 21 December 2017 at 23:09, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi all,
>
> noticed yesterday that our main (well, all) github repos currently have an
> old description + no associated topics. As this is something infra changes,
> I've thought of to requesting infra tomorrow / this weekend adding the
> following descriptions + topics. Topics with a ? mark denoting I'm not very
> sure if they would fit in, so any pointer, further topics, etc. will be
> greatly appreciated.
>
> https://github.com/apache/jspwiki
> description: Apache JSPWiki is a leading open source WikiWiki engine,
> feature-rich and built around standard JEE components (Java, servlets,
> JSP).
> topics: jspwiki, apache, asf, wiki, wiki-engine, portable?, war?, java?,
> maven?, markdown?
>
> https://github.com/apache/jspwiki-site
> description: Apache JSPWiki's website (http://jspwiki.apache.org)
> topics: jspwiki, apache, asf, website, jbake, asf-cms
>
> https://github.com/apache/jspwiki-asf-docs
> description: Apache JSPWiki's ASF related documentation
> topics: jspwiki, apache, asf
>
> WDYT?
>
>
> br,
> juan pablo
>

Re: automated dockerhub build for JSPWiki under Apache account?

[Harry Metske]

I went through this, and if I am correct we could:
* create a Dockerfile in our jspwiki project, for example:
/docker/dockerhub/Dockerfile
* request docker automated build with info:

Type: "Tag"
Name: "/jspwiki_(\d+\_\d+\_\d+)/"
Dockerfile location: "/docker/dockerhub"
Docker tag name: "{\1}"

And the Dockerfile should be changed in such a way that the 2 added
binaries (JSPWiki.war and jspwiki-wikipages.zip) are being fetched from a
remote location (pick an apache mirror site).
I wonder if that will work, I don't if we can find a download location
where the binaries will be present when the docker build is run
(automatically when we git push the new tag).

cheers,
Harry


On Wed, 1 Aug 2018 at 19:27, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi,
>
> searching for some documentation about Docker (ASF Infra) support, I've
> stumbled upon some interesting infra JIRAs, namely:
> - https://jira.apache.org/jira/browse/INFRA-13838
> - https://jira.apache.org/jira/browse/INFRA-12781
> - https://jira.apache.org/jira/browse/INFRA-14586
>
> requesting automated builds under Apache Dockerhub account. The applying
> release policy would be
> https://www.apache.org/dev/release-distribution.html#unreleased, but other
> than that, moving the JSPWiki's Docker
> support [#1] into the Apache Dockerhub account would be a nice addition for
> upcoming 2.10.5. Harry, WDYT?
>
>
> tx + br,
> juan pablo
>
> [#1] https://jspwiki-wiki.apache.org/Wiki.jsp?page=Docker
>

Re: automated dockerhub build for JSPWiki under Apache account?

[Harry Metske]

sure that sounds like a good idea.
At the moment however I am on vacation and can’t spend much time on it, but
I will take a look later.

thanks,
Harry


Op wo 1 aug. 2018 om 19:27 schreef Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com>

> Hi,
>
> searching for some documentation about Docker (ASF Infra) support, I've
> stumbled upon some interesting infra JIRAs, namely:
> - https://jira.apache.org/jira/browse/INFRA-13838
> - https://jira.apache.org/jira/browse/INFRA-12781
> - https://jira.apache.org/jira/browse/INFRA-14586
>
> requesting automated builds under Apache Dockerhub account. The applying
> release policy would be
> https://www.apache.org/dev/release-distribution.html#unreleased, but other
> than that, moving the JSPWiki's Docker
> support [#1] into the Apache Dockerhub account would be a nice addition for
> upcoming 2.10.5. Harry, WDYT?
>
>
> tx + br,
> juan pablo
>
> [#1] https://jspwiki-wiki.apache.org/Wiki.jsp?page=Docker
>

Re: switching to 2.11?

[Harry Metske]

JP,

I fully agree with this order.

cheers,
Harry


Op wo 5 sep. 2018 om 21:44 schreef Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com>

> Hi,
>
> I think now would be a good time to swicth to 2.11, meaning breaking
> changes would be allowed. My list of breaking-and-not changes would include
>
> 1.- instead of releasing 2.11.0, release 2.11.0.M1, 2.11.0.M2, etc (don't
> know how may milestones). The idea there is that M# releases would allow us
> to keep breaking compatibility with 2.10 within several releases, but other
> than that should be as ready for production as normal releases
> 2.- switching to java 8 / servlet 3.1
> 3.- haddock as default template (maybe renaming then the default template
> "white template", "lean template", "classic template" or something along
> those lines)
> 4.- remove warnings from the java source
> 5.- begin to move to a multi-module build
> 5.1.- one war module with all the JSPs, css preprocessing, js minifying,
> etc
> 5.2.- one "main" jar with almost all java files, (and as time permits)
> another with the util, package, another with the log susbsystem, another
> with plugins, etc... there are some packages classes that can be extracted
> right away to their own module
> 5.3.- the reasoning behind this is that having a multimodule would allow us
> to disentangle package/classes cycles, in order to help us preparing
> java9-module jars in a not so distant future. As a bonus point, it also
> would speed up testing (i.e., no need to execute 920+ java unit tests to
> push a change on a JSP)
>
> I'd like to begin in that order next week so, WDYT?
>
>
> thanks,
> juan pablo
>

Re: [VOTE] Release JSPWiki version 2.10.5

[Harry Metske]

+1

On Sat, 1 Sep 2018 at 01:00, Juan Pablo Santos Rodríguez <
juanpa...@apache.org> wrote:

> This is a release vote for Apache JSPWiki, version 2.10.5. The vote will be
> open for at least 72 hours from now.
>
> It fixes the following issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732=12343310
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Everybody is encouraged to vote.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/jspwiki/2.10.5-rc2
>
> Nexus staging repo:
> https://repository.apache.org/content/repositories/orgapachejspwiki-1006
>
> The tag to be voted upon:
> https://github.com/apache/jspwiki/tree/2.10.5-RC2
>
> JSPWiki's KEYS file containing PGP keys we use to sign the release:
> https://www.apache.org/dist/jspwiki/KEYS
>
> *** Please download, test and vote:
>
> [ ] +1 Approve the release
> [ ]  0 Don't mind
> [ ] -1 Disapprove the release (please provide specific comments)
>

Re: Draft for upcoming board report

[Harry Metske]

looks good!

thanks,
Harry


On Sun, 8 Jul 2018 at 21:58, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi all,
>
> below is a draft for the upcoming board report, I'm planning on sending it
> 2 or 3 days ahead of now. As always, any correction, addition, etc. is more
> than welcome
>
>
> cheers,
> juan pablo
>
>
> -- Forwarded message --
> From: 
> Date: Sun, Jul 8, 2018 at 9:52 PM
> Subject: [jspwiki-asf-docs] branch master updated: draft report for 2018/07
> To: "comm...@jspwiki.apache.org" 
>
>
> This is an automated email from the ASF dual-hosted git repository.
>
> juanpablo pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/jspwiki-asf-docs.git
>
>
> The following commit(s) were added to refs/heads/master by this push:
>  new a191aed  draft report for 2018/07
> a191aed is described below
>
> commit a191aed97e1cfe13ab5dcf086732a1917ec70594
> Author: Juan Pablo Santos Rodríguez 
> AuthorDate: Sun Jul 8 21:52:28 2018 +0200
>
> draft report for 2018/07
> ---
>  board-reports/2018-07.txt | 60 ++
> +
>  1 file changed, 60 insertions(+)
>
> diff --git a/board-reports/2018-07.txt b/board-reports/2018-07.txt
> new file mode 100755
> index 000..d785ed5
> --- /dev/null
> +++ b/board-reports/2018-07.txt
> @@ -0,0 +1,60 @@
> +## Description:
> + - A feature-rich and extensible WikiWiki engine built around the standard
> +JEE components (Java, servlets, JSP).
> +
> +## Issues:
> + - There are no issues requiring board attention at this time.
> +
> +## Activity:
> + - 2.10.4 was released on May with better support for mobile devices on
> +   Haddock, some important fixes regarding caches / ACLs and a few more
> +   features and bugfixes.
> +
> + - 2.10.5 expected for August.
> +
> + - We received our first PR on Github. It didn't make it to master because
> of
> +   that same fix being included as a part of a subsequent commit, but our
> first
> +   interaction merits a mention.
> +
> + - New code has been mostly about fine-tuning Haddock template for mobile
> +   devices; also a fix for the default template and smoothing the
> build/release
> +   process.
> +
> +## Health report:
> +
> + - No questions unanswered on MLs, with at least 3 people from PMC showing
> +   up there.
> +
> +## PMC changes:
> +
> + - Currently 11 PMC members.
> + - No new PMC members added in the last 3 months
> + - Last PMC addition was Dave Koelmeyer on Wed Apr 06 2016
> +
> +## Committer base changes:
> +
> + - Currently 16 committers.
> + - No new committers added in the last 3 months
> + - Last committer addition was Dave Koelmeyer at Wed Apr 06 2016
> +
> +## Releases:
> +
> + - 2.10.4 was released on Wed May 23 2018
> +
> +## Mailing list activity:
> +
> + - Normal quarter regarding ML activity, as shown by the statistics.
> +
> +  - dev@jspwiki.apache.org:
> +- 83 subscribers (up 0 in the last 3 months):
> +- 80 emails sent to list (83 in previous quarter)
> +
> + - u...@jspwiki.apache.org:
> +- 174 subscribers (down -1 in the last 3 months):
> +- 26 emails sent to list (19 in previous quarter)
> +
> +
> +## JIRA activity:
> +
> + - 3 JIRA tickets created in the last 3 months
> + - 5 JIRA tickets closed/resolved in the last 3 months
> \ No newline at end of file
>

Re: [apache/jspwiki] Clickable buttons (#1)

[Harry Metske]

done

regards,
Harry


On Wed, 20 Jun 2018 at 19:40, Dirk Frederickx 
wrote:

> Harry, Juan,
>
> I made a commit earlier this week to resolve the hover/clickable buttons
> for devices with a touch-interface.
> Would it be possible to push the update to jspwiki-wiki.apache.org .
> Testing was done on iPad/iPhone,  but I'd like to get feedback on other
> types of touch devices.
>
>
> Not sure how to close the issue on github.
>
>
> br,
> dirk
>
>
>
> On Tue, May 29, 2018 at 6:45 PM Harry Metske 
> wrote:
>
> > I had seen it before on the dev list.
> > But since it was mostly frontend, I did not comment.
> >
> > cheers,
> > Harry
> >
> >
> > On Tue, 29 May 2018 at 00:40, Juan Pablo Santos Rodríguez <
> > juanpablo.san...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > I was looking for the below mail at [user|dev|commits]@jspwiki.a.o. As
> I
> > > can't see it through Pony Mail, I'm resending over
> > > dev. Would anyone mind confirming if this is the first time receiving
> the
> > > e-mail? (if not, apologies for the noise).
> > >
> > > And regarding the PR itself, any thoughts on it? I find it useful, esp.
> > for
> > > mobile devices, and would be +1 for merging it,
> > > but I don't have a strong opinion on it, frontend isn't one of my key
> > > points..
> > >
> > >
> > > thanks in advance,
> > > juan pablo
> > >
> > >
> > > -- Forwarded message --
> > > From: jonasmue 
> > > Date: Fri, May 25, 2018 at 1:35 PM
> > > Subject: [apache/jspwiki] Clickable buttons (#1)
> > > To: apache/jspwiki 
> > > Cc: Subscribed 
> > >
> > >
> > > Made header buttons clickable instead of hoverable. This change should
> > > result in increased usability since the opening boxes frequently would
> > have
> > > been closed involuntarily if user's mouse movement was not precise
> enough
> > > after hovering over the buttons. Removed the carets for consistency
> > reasons
> > > as they indicate a hoverable target.
> > > --
> > > You can view, comment on, or merge this pull request online at:
> > >
> > >   https://github.com/apache/jspwiki/pull/1
> > > Commit Summary
> > >
> > >- Clickable header buttons
> > >- Updated to current state and removed other changes
> > >- Changed indentation to original form
> > >
> > > File Changes
> > >
> > >- *M* jspwiki-war/src/main/scripts/wiki/Wiki.js
> > ><https://github.com/apache/jspwiki/pull/1/files#diff-0> (35)
> > >- *M* jspwiki-war/src/main/webapp/templates/haddock/SearchBox.jsp
> > ><https://github.com/apache/jspwiki/pull/1/files#diff-1> (4)
> > >- *M* jspwiki-war/src/main/webapp/templates/haddock/UserBox.jsp
> > ><https://github.com/apache/jspwiki/pull/1/files#diff-2> (4)
> > >
> > > Patch Links:
> > >
> > >- https://github.com/apache/jspwiki/pull/1.patch
> > >- https://github.com/apache/jspwiki/pull/1.diff
> > >
> > > —
> > > You are receiving this because you are subscribed to this thread.
> > > Reply to this email directly, view it on GitHub
> > > <https://github.com/apache/jspwiki/pull/1>, or mute the thread
> > > <
> > >
> >
> https://github.com/notifications/unsubscribe-auth/ABKX4v23eYQ0kCinSJj1cWhts1HVqYbUks5t1-yBgaJpZM4UN0uj
> > > >
> > > .
> > >
> >
>

Re: removing tests suites?

[Harry Metske]

I don't use the test suites, so fine to remove them.

On Thu, 25 Oct 2018 at 22:59, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi,
>
> I've begun to migrate all tests to latest JUnit 5 (probably next week big
> commit incoming). It's being straightforward, although a bit tedious, but
> anyway. As of today there isn't a "clean" (=only JUnit5-based) replacement
> for suites, only workarounds that require the use of JUnit 4's @RunWith
> (f.ex.: https://howtodoinjava.com/junit5/junit5-test-suites-examples/).
>
> So I was wondering, does anyone use the Tests' Suites? Would it be ok to
> remove them? I'd rather remove them if the alternative is having a mix of
> both frameworks.. I don't use the tests suites, but maybe other find them
> useful. Other alternative could be tagging the tests instead of having
> suites, but I'm not very fond of it, we'd have to remember tagging each new
> test file..
>
> thoughts?
>
>
> br,
> juan pablo
>

Re: Draft board report for 2019/01

[Harry Metske]

+1

thanks,
Harry


Op vr 11 jan. 2019 om 13:30 schreef Dirk Frederickx <
dirk.frederi...@gmail.com>

> Txs for preparing the report.
> +1
>
> Happy New Year to all !
>   dirk
>
> On Fri, Jan 11, 2019 at 12:26 AM Juan Pablo Santos Rodríguez <
> juanpablo.san...@gmail.com> wrote:
>
> > Hi,
> >
> > I've just pushed a draft for the upcoming board report at
> >
> >
> https://github.com/apache/jspwiki-asf-docs/blob/master/board-reports/2019-01.txt
> >
> > As usual, comments, corrections, additions, etc. are more than welcome.
> >
> >
> > best regards (and happy new year!),
> > juan pablo
> >
>

Re: [VOTE] Release JSPWiki version 2.11.0.M1

[Harry Metske]

+1

thanks,
Harry


On Sat, 26 Jan 2019 at 18:39, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> This is a release vote for Apache JSPWiki, version 2.11.0.M1. The vote will
> be open for at least 72 hours from now.
>
> It fixes the following issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732=12343348
>
> You can see a curated changelog at
> https://jspwiki-wiki.apache.org/Wiki.jsp?page=NewIn2.11
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Everybody is encouraged to vote.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/jspwiki/2.11.0.M1-rc3
>
> Nexus staging repo:
> https://repository.apache.org/content/repositories/orgapachejspwiki-1008
>
> The tag to be voted upon:
> https://github.com/apache/jspwiki/tree/2.11.0.M1.RC3
>
> JSPWiki's KEYS file containing PGP keys we use to sign the release:
> https://www.apache.org/dist/jspwiki/KEYS
>
> *** Please download, test and vote:
>
> [ ] +1 Approve the release
> [ ]  0 Don't mind
> [ ] -1 Disapprove the release (please provide specific comments)
>

Re: Search on jspwiki-wiki.apache.org now

[Harry Metske]

hmmm, I ll try to have a look today

cheers
Harry

Op wo 3 apr. 2019 om 00:08 schreef Dirk Frederickx <
dirk.frederi...@gmail.com>

> Seems like the search on jspwiki-wiki.apache.org is broken ...
> Also the quick navigation doesn't work.
>
> Possibly Lucene is not properly indexing the site ?
>
> dirk
>

Re: Search on jspwiki-wiki.apache.org now

[Harry Metske]

fixed, Lucene was indeed broken

regards,
Harry

Op wo 3 apr. 2019 om 06:42 schreef Harry Metske 

> hmmm, I ll try to have a look today
>
> cheers
> Harry
>
> Op wo 3 apr. 2019 om 00:08 schreef Dirk Frederickx <
> dirk.frederi...@gmail.com>
>
>> Seems like the search on jspwiki-wiki.apache.org is broken ...
>> Also the quick navigation doesn't work.
>>
>> Possibly Lucene is not properly indexing the site ?
>>
>> dirk
>>
>

Re: [VOTE] Release JSPWiki version 2.11.0.M3

[Harry Metske]

+1

cheers,
Harry



On Fri, 22 Mar 2019 at 20:09, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> my +1
>
> best regards,
> juan pablo
>
> On Fri, Mar 22, 2019 at 6:53 PM Juan Pablo Santos Rodríguez <
> juanpablo.san...@gmail.com> wrote:
>
> > This is a release vote for Apache JSPWiki, version 2.11.0.M3. The vote
> > will be open for at least 72 hours from now.
> >
> > It fixes the following issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732=12344900
> >
> > You can see a curated changelog at
> > https://jspwiki-wiki.apache.org/Wiki.jsp?page=NewIn2.11
> >
> > Note that we are voting upon the source (tag), binaries are provided for
> > convenience.
> >
> > Everybody is encouraged to vote.
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/jspwiki/2.11.0.M3-rc2
> >
> > Nexus staging repo:
> > https://repository.apache.org/content/repositories/orgapachejspwiki-1011
> >
> > The tag to be voted upon:
> > https://github.com/apache/jspwiki/tree/2.11.0.M3-RC2
> >
> > JSPWiki's KEYS file containing PGP keys we use to sign the release:
> > https://www.apache.org/dist/jspwiki/KEYS
> >
> > *** Please download, test and vote:
> >
> > [ ] +1 Approve the release
> > [ ]  0 Don't mind
> > [ ] -1 Disapprove the release (please provide specific comments)
> >
>

Re: [VOTE] Release JSPWiki version 2.11.0.M2

[Harry Metske]

+1

On Mon, 4 Mar 2019 at 23:56, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> This is a release vote for Apache JSPWiki, version 2.11.0.M2. The vote will
> be open for at least 72 hours from now.
>
> It fixes the following issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732=12343994
>
> You can see a curated changelog at
> https://jspwiki-wiki.apache.org/Wiki.jsp?page=NewIn2.11
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Everybody is encouraged to vote.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/jspwiki/2.11.0.M2-rc1/
>
> Nexus staging repo:
> https://repository.apache.org/content/repositories/orgapachejspwiki-1010
>
> The tag to be voted upon:
> https://github.com/apache/jspwiki/tree/2.11.0.M2-RC1
>
> JSPWiki's KEYS file containing PGP keys we use to sign the release:
> https://www.apache.org/dist/jspwiki/KEYS
>
> *** Please download, test and vote:
>
> [ ] +1 Approve the release
> [ ]  0 Don't mind
> [ ] -1 Disapprove the release (please provide specific comments)
>

Re: releasing 2.11.0.M2?

[Harry Metske]

JP,

that would be fine I think.

tx,
Harry


Op zo 17 feb. 2019 om 23:58 schreef Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com>

> Hi,
>
> we've been some releases trying to adhere to a release train strategy, with
> stops each quarter. Q4-2018 release had issues, so we
> ended up releasing it on Jan, 29th, 2019. Given that, I felt that probably
> made sense to skip February stop.
>
> However, given that there are a couple of fixes regarding the rename of the
> haddock template to default, a new Dark appereance
> mode for Haddock, enabled by default, and a few other fixes and
> improvements, I think releasing 2.11.0.M2 on February would make
> most sense. I'd only like to extract the util package to its own submodule,
> which should be fairly easy, but other than that, that would
> be for me if we release on Feb.
>
> WDYT?
>
>
> br,
> juan pablo
>

Re: [ANNOUNCE] Apache JSPWiki 2.11.0.M4 released

[Harry Metske]

I ll deploy it on jspwiki-wiki.apache.org

cheers,
Harry


On Sun, 19 May 2019 at 17:51, Juan Pablo Santos Rodríguez <
juanpa...@apache.org> wrote:

> The Apache JSPWiki team is pleased to announce the release of JSPWiki
> 2.11.0.M4.
>
> This is the fourth release towards the 2.11 series of Apache JSPWiki, a
> feature-rich and
> extensible WikiWiki engine built around the standard JEE components. M#
> releases are as
> production-ready as any other JSPWiki release, please see [#1] to know how
> this label
> is used on Apache JSPWiki releases.
>
> The release is available here:
> https://jspwiki-wiki.apache.org/Wiki.jsp?page=Downloads
>
> JSPWiki Maven artifacts are available under org.apache.jspwiki groupId,
> version 2.11.0.M4
>
> The full change log is available here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732=12345211
>
> A curated change log is also available here:
> https://jspwiki-wiki.apache.org/Wiki.jsp?page=NewIn2.11
>
> We welcome your help and feedback. For more information on how to
> report problems, and to get involved visit the project website at
> http://jspwiki.apache.org/
>
> The Apache JSPWiki Team
>
> [#1]: https://jspwiki-wiki.apache.org/Wiki.jsp?page=VersioningProposal
>

Re: [VOTE] Release JSPWiki version 2.11.0.M4

[Harry Metske]

+1



> On 15 May 2019, at 12:04, Juan Pablo Santos Rodríguez  
> wrote:
> 
> This is a release vote for Apache JSPWiki, version 2.11.0.M4. The vote will
> be open for at least 72 hours from now.
> 
> It fixes the following issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732=12345211
> 
> You can see a curated changelog at
> https://jspwiki-wiki.apache.org/Wiki.jsp?page=NewIn2.11
> 
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
> 
> Everybody is encouraged to vote.
> 
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/jspwiki/2.11.0.M4-rc2
> 
> Nexus staging repo:
> https://repository.apache.org/content/repositories/orgapachejspwiki-1012
> 
> The tag to be voted upon:
> https://github.com/apache/jspwiki/tree/2.11.0.M4-RC2
> 
> JSPWiki's KEYS file containing PGP keys we use to sign the release:
> https://www.apache.org/dist/jspwiki/KEYS
> 
> *** Please download, test and vote:
> 
> [ ] +1 Approve the release
> [ ]  0 Don't mind
> [ ] -1 Disapprove the release (please provide specific comments)

Re: [VOTE] Release JSPWiki version 2.11.0.M5

[Harry Metske]

I downloaded the source, did a successful maven clean package, deployed to
a server and clicked around in an incognito Chrome tab. Looks fine, however
when trying to edit a page, I get this javascript error:

haddock-edit.js:1 Uncaught TypeError: $.toFunction is not a function
at Object.initialize (haddock-edit.js:1)
at Object. (haddock.js:1)
at Object.r.extend.$owner (haddock.js:1)
at new  (haddock.js:1)
at Object.initialize (haddock-edit.js:1)
at Object. (haddock.js:1)
at Object.r.extend.$owner (haddock.js:1)
at new  (haddock.js:1)
at HTMLTextAreaElement. (haddock-edit.js:1)
at Object.update (haddock.js:1)

The edit window is empty, also creating new pages does not work (page
cannot be saved).

I must be doing something wrong?

cheers,
Harry



On Tue, 10 Sep 2019 at 22:11, Juan Pablo Santos Rodríguez <
juanpa...@apache.org> wrote:

> This is a release vote for Apache JSPWiki, version 2.11.0.M5. The vote will
> be open for at least 72 hours from now.
>
> It fixes the following issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732=12345540
>
> You can see a curated changelog at
> https://jspwiki-wiki.apache.org/Wiki.jsp?page=NewIn2.11
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Everybody is encouraged to vote.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/jspwiki/2.11.0.M5-rc2
>
> Nexus staging repo:
> https://repository.apache.org/content/repositories/orgapachejspwiki-1014
>
> The tag to be voted upon:
> https://github.com/apache/jspwiki/tree/2.11.0.M5-RC2
>
> JSPWiki's KEYS file containing PGP keys we use to sign the release:
> https://www.apache.org/dist/jspwiki/KEYS
>
> *** Please download, test and vote:
>
> [ ] +1 Approve the release
> [ ]  0 Don't mind
> [ ] -1 Disapprove the release (please provide specific comments)
>