make
someone a committer, just do the reverse I guess. I think you did this
earlier in 2015 when you removed my PMC membership:
https://lists.apache.org/thread.html/ad1f0bc1d9287abb0c5a89e0f9d5cbe0105e81799b1a89557c5dfe8f%401427384374%40%3Cdev.jspwiki.apache.org%3E
Thanks,
Glen
On 7/3/20 3:46
d we'll get you onboard again, as merit doesn't expire at
> Apache, we won't need an additional vote.
>
>
> best regards + best luck with TightBlog!
>
> On Thu, Jul 2, 2020 at 1:51 AM Glen Mazza wrote:
>
> > Hi all, I've been inactive on JSPWiki for
Hi all, I've been inactive on JSPWiki for several years and no longer
need to be a committer. (I've been busy with my Apache Roller fork
"TightBlog".) Could someone revoke my write access and remove my name
from the current committer list on the People page? Should you create
an Emeritus Comm
Please do, thanks! No offense to the team, it's just the last tweet has
been filling up my inbox, and I've long left Twitter (cancelled my own
account).
Cheers,
Glen
Am 02/22/2016 um 07:59 PM schrieb Dave Koelmeyer:
Hi All,
Janne has suggested we register a shared Apache address with the Tw
Hi all, would a JSPWiki team member please log into the JSPWiki twitter
account and switch the email from mine to yours? I'm getting bombarded
with retweet and "we got a login from an unexpected region" emails.
(Congrats on the new release of JSPWiki, btw... :)
Thanks,
Glen
Hi Team, I don't have the time so much to be keeping up-to-date on
JSPWiki matters (and am trying to streamline my email inbox a bit) so
I've decided to resign from the JSPWiki PMC. I unsubscribed from the
private@ email and updated the website people page. At any time in the
future, should a
[
https://issues.apache.org/jira/browse/JSPWIKI-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227674#comment-14227674
]
Glen Mazza commented on JSPWIKI-873:
Is this limit per-page (in which case
[
https://issues.apache.org/jira/browse/JSPWIKI-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195640#comment-14195640
]
Glen Mazza commented on JSPWIKI-870:
Albrecht, why would you put a space in
[
https://issues.apache.org/jira/browse/JSPWIKI-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161748#comment-14161748
]
Glen Mazza commented on JSPWIKI-205:
I don't know enough about encryptio
[
https://issues.apache.org/jira/browse/JSPWIKI-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160129#comment-14160129
]
Glen Mazza commented on JSPWIKI-205:
Hi David, your patch is hardcoding a salt v
I'd leave it as-is but nothing vetoable of course if you want to switch
to it. Looking at all the logos
(http://apache.org/foundation/press/kit/poweredBy/) it looks like it
wasn't done with much thought, as it shrinks the project name/logo while
over-emphasizing the Apache brand. For marketin
[
https://issues.apache.org/jira/browse/JSPWIKI-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146378#comment-14146378
]
Glen Mazza commented on JSPWIKI-205:
"...which is encrypted with a masterk
[
https://issues.apache.org/jira/browse/JSPWIKI-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14140450#comment-14140450
]
Glen Mazza commented on JSPWIKI-835:
For our small project, it would probabl
[
https://issues.apache.org/jira/browse/JSPWIKI-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130810#comment-14130810
]
Glen Mazza commented on JSPWIKI-865:
I'm not sure what it matters (who ca
[
https://issues.apache.org/jira/browse/JSPWIKI-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124465#comment-14124465
]
Glen Mazza commented on JSPWIKI-811:
On Apache Roller, we don't put
It would be nice if the Apache license headers were added to its source
files, I can't see a license, possibly reducing its adoption.
Glen
On 08/31/2014 01:24 AM, David Vittor wrote:
Hi All,
I'd like to let you all know that I've released the first 0.1 version of
the JIRA plugin.
https://jspw
[
https://issues.apache.org/jira/browse/JSPWIKI-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113619#comment-14113619
]
Glen Mazza commented on JSPWIKI-864:
Could we use this: http://commons.apache
quot;
Kind regards,
Harry
Op 21 aug. 2014 18:39 schreef "Glen Mazza" :
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 w
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 wi
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
On 07/20/2014 02:57 AM, Dave Koelmeyer wrote:
On 13/05/14 21:01, 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
wrote:
Hi Janne/All,
A belated thanks for this. I believe since t
08.07.2014 16:15 schrieb "Glen Mazza" :
The Apache license does not require contributed plugins to be ASL or even
open source, they can be whatever license, we don't care, that's the beauty
of the ASL license. (You may have been thinking about (L)GPL.) Should we
restrict t
The Apache license does not require contributed plugins to be ASL or
even open source, they can be whatever license, we don't care, that's
the beauty of the ASL license. (You may have been thinking about
(L)GPL.) Should we restrict that page to only non-commercial products?
I don't see a need
[
https://issues.apache.org/jira/browse/JSPWIKI-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009551#comment-14009551
]
Glen Mazza commented on JSPWIKI-212:
Oh, now I remember, there is a differ
s 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 wrote:
Hello Jürgen, while it will work, I recommend against placing the
jspwiki-custom.properties file within the WAR. Just p
[
https://issues.apache.org/jira/browse/JSPWIKI-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009013#comment-14009013
]
Glen Mazza commented on JSPWIKI-212:
Oh, now I see. OK, I don't care e
[
https://issues.apache.org/jira/browse/JSPWIKI-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza closed JSPWIKI-842.
--
Resolution: Fixed
More documentation added on jspwiki-custom.properties.
> deliver a template
[
https://issues.apache.org/jira/browse/JSPWIKI-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009008#comment-14009008
]
Glen Mazza commented on JSPWIKI-842:
Hi, I updated our documentation page with
[
https://issues.apache.org/jira/browse/JSPWIKI-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008983#comment-14008983
]
Glen Mazza commented on JSPWIKI-212:
I'm not sure I understand your poi
[
https://issues.apache.org/jira/browse/JSPWIKI-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008895#comment-14008895
]
Glen Mazza commented on JSPWIKI-842:
Hi, Juergen, some concerns I have on this
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 t
+1
Glen
On 05/25/2014 06:19 PM, Juan Pablo Santos Rodríguez wrote:
Hi Brian,
thanks for looking + voting :-)
Here's my +1 as well
Anybody trying to use the staging repo, please mind that the ASF's Nexus is
currently having some problems [#1] which prevent
its use. Source and binaries still a
[
https://issues.apache.org/jira/browse/JSPWIKI-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza closed JSPWIKI-838.
--
Resolution: Incomplete
Please ask support questions on the JSPWiki User's mailing list. When
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 pr
Hi Dave, you're a big booster of JSPWiki on the 'Net, we appreciate your
enthusiasm and willingness to help out. (Code patches welcome too... :-)
Regards,
Glen
On 4/12/2014 11:31 PM, Dave Koelmeyer wrote:
On 4/10/2014 8:54 PM, Siegfried Goeschl wrote: Hi folks,
the question at hand is to i
Can we just shut down (delete) the facebook page instead, and put those
efforts into improving our home page and wiki instead? I didn't even
know we were on Facebook. We're spreading ourselves too thin by
maintaining too many sites (we have Ohloh and Wikipedia as well), which
results in the
uca
On 4/11/2014 8:05 AM, Harry Metske wrote:
sounds like a good idea to me !
On 11 April 2014 03:42, Glen Mazza 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.or
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
[
https://issues.apache.org/jira/browse/JSPWIKI-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941243#comment-13941243
]
Glen Mazza commented on JSPWIKI-834:
I wouldn't mind a plugin for this but
According to JIRA, the status of your issues are "OPEN", the same as
130+ other issues. So long as they are open they will never be
forgotten. It's just that we're volunteers with limited time and our
own JSPWiki priorities which may not be in sync with yours. If you need
faster response tim
Excellent!! :) Happy to see JSPWiki get some publicity at ApacheCon.
Glen
On 03/02/2014 04:58 AM, Siegfried Goeschl wrote:
Hi folks,
the good news are that Apache JSP Wiki will be presented at ApacheCon 2014
http://events.linuxfoundation.org/events/apachecon-north-america/program/schedule
h
ikely excluded from the regular JSPWiki M2 build
Happily I'm now in the situation to be active for JSPWiki so I will
through the new Maven build over the weekend :-)
Cheers,
Siegfried Goeschl
PS: Juan Pablo - thanks for you help integrating my patch :-)
On 20.02.14 05:23, Glen Mazza w
Brian, if you'd like a larger role on the team, best to start submitting
patches on actual code functionality enhancements -- as you gain more
"cred" on the project, you'll naturally gain more influence on matters
such as code style, especially if you become a committer. I felt your
arguments
mbox/incubator-jspwiki-user/200810.mbox/%3c48efb9b8.4050...@it20one.at%3E
[#3] http://people.apache.org/~sgoeschl/presentations/jspwiki-20100506.pdf
On Thu, Feb 20, 2014 at 5:23 AM, Glen Mazza wrote:
Hi JP, what do you mean by "portable JSPWiki binaries for several
OS/platforms"? JSPWiki, b
Hi JP, what do you mean by "portable JSPWiki binaries for several
OS/platforms"? JSPWiki, being Java, is already portable. I hope it is
not your intention to start distributing application servers such as
Tomcat, we are not in a position to be securing application servers on
everybody's machi
+1
Glen
On 01/15/2014 03:48 PM, Harry Metske wrote:
+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
To a point, once the bulk of necessary information is on on Apache
servers I feel it would be better to sever the link to the ecyrd site;
it's loaded with a lot of obsolete stuff. We want JSPWiki to be a Wiki
for the future, not that of the past, and detailed instructions of how
to configure J
[
https://issues.apache.org/jira/browse/JSPWIKI-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863845#comment-13863845
]
Glen Mazza commented on JSPWIKI-811:
Kono ii suggestion o arigatou, Ichiro. :
p; br,
juan pablo
On Sun, Dec 22, 2013 at 8:31 PM, Glen Mazza wrote:
Same errors for me on port 9001 as mentioned earlier. I'm not aware of
using any firewall, this is just my personal laptop with an Internet
connection.
Glen
On 12/22/2013 02:27 PM, Juan Pablo Santos Rodríguez wrot
3 06:33 PM, Juan Pablo Santos Rodríguez wrote:
Hi,
finished the 72 hours, the vote carries 2 -1 and 1 0, so no 2.10.0 release
yet
I'll revert the poms to 2.10.0-SNAPSHOT and once the issues raised are
fixed we'll re-roll the vote again.
thanks & br,
juan pablo
On Mon, Dec 23, 201
s are quite an eyesore.
Glen
On 12/22/2013 04:45 PM, Glen Mazza wrote:
Hmm, getting the same NPE exception as below when deploying to
OpenShift. This is my configuration entry in my
jspwiki-custom.properties:
# Authorization file
jspwiki.policy.file=jspwiki-custom.policy
I'll look more in
the process), and (3) allow the user
to rapidly deploy new upgrades of JSPWiki without needing to re-insert
his properties file each time.
Glen
Ichiro
On Mon, Dec 23, 2013 at 12:19 AM, Glen Mazza wrote:
We made a change a few months back to Apache Roller-style configuration,
you should be lea
an do so. I'll change my vote from a -1 to a 0, this
is inconvenient but not a show-stopper.
Thanks,
Glen
On 12/22/2013 09:02 AM, Glen Mazza wrote:
Awesome, thanks Harry! I'll test today and respond back, hopefully soon.
Glen
On 12/22/2013 08:44 AM, Harry Metske wrote:
this NPE s
e error is persisting on
analysis.a.o/jenkins (I'll ask later on infra to see if something running
on that port on that machine)
br,
juan pablo
On Sun, Dec 22, 2013 at 8:20 PM, Glen Mazza wrote:
Thanks for the report, so it's not just me. I may need to check out older
versions to try and de
name: "linux", version: "3.5.0-17-generic", arch: "i386", family: "unix"
On 22 December 2013 14:32, Glen Mazza wrote:
What Maven version are you running? I'm on 3.1...
Glen
On 12/22/2013 08:13 AM, Harry Metske wrote:
I am running Ubuntu, and ha
: UTF-8
OS name: "linux", version: "3.5.0-17-generic", arch: "i386", family: "unix"
On 22 December 2013 14:32, Glen Mazza wrote:
What Maven version are you running? I'm on 3.1...
Glen
On 12/22/2013 08:13 AM, Harry Metske wrote:
I am running Ubun
ember 2013 00:43, Glen Mazza wrote:
-1 right now, just one thing, I hope to fix soon unless someone else can
get to it. Namely, the "jspwiki.policy.file" property in
jspwiki-custom.properties doesn't seem to be working--I get an NPE on just
about any value I put there (unless I
On 22 December 2013 14:01, Glen Mazza 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 ou
(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 wrote:
Hi all, I can't build trunk--doing JDK 1.7.0_25 on Ubuntu. With a fresh
checkout of j
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)
[Serve
We made a change a few months back to Apache Roller-style configuration,
you should be leaving the ini/jspwiki.properties file alone and instead
place a jspwiki-custom.properties file in Tomcat's "lib" folder,
containing just the values you're choosing to override from that default
file. The j
-1 right now, just one thing, I hope to fix soon unless someone else can
get to it. Namely, the "jspwiki.policy.file" property in
jspwiki-custom.properties doesn't seem to be working--I get an NPE on
just about any value I put there (unless I use "jspwiki.policy" itself,
in which case it proba
I disagree. Half a year old is perfectly reasonable, anything less than
18 months or so is acceptable, especially for a largely complete and
sleepy application like JSPWiki.
What a developer doesn't want to do is compromise his integrity by
releasing something functionally equivalent but just
Perhaps WatchDog can be taken out of 2.10, and revisited later if it's
actually useful/helpful. Looking at it
(http://people.apache.org/~metskem/JSPWiki/javadoc/org/apache/wiki/WatchDog.html),
I wonder if its messages constitute something that a modern servlet
container would already report on.
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 s
[
https://issues.apache.org/jira/browse/JSPWIKI-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832195#comment-13832195
]
Glen Mazza commented on JSPWIKI-768:
Yes, we're now using standard Mav
the apache-release
profile, so the minimizing stuff would only get done when we're about to
release. WDYT?
br,
juan pablo
On Sun, Nov 10, 2013 at 9:49 PM, Glen Mazza wrote:
Hi Team, presently whenever building JSPWiki via "mvn clean install" or
even running a single JUnit
Hi Team, presently whenever building JSPWiki via "mvn clean install" or
even running a single JUnit test via "mvn test -Dtest=" I lose about
20-25 seconds compiling and compressing the JavaScript stuff (jslint and
wro4j and seeing the output of the various mootools errors), code which
I'm n
Just FYI, entered a new bug w/INFRA for this problem:
https://issues.apache.org/jira/browse/INFRA-6985
Glen
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
No, not if we have nothing significant to add. Volunteers can't afford
to be engaging in busywork. And, yes, projects are allowed to go on
snooze between releases.
Glen
On 11/08/2013 03:08 PM, Jürgen Weber wrote:
no difference, but it should be soon. Last incubating is from May, so it
looks
Incidentally, I wonder if JSPWiki even needs ehcache. I was primarily
interested in switching from oscache to ehcache because the former was
obsolete, but app-level caching may be redundant today if most app
servers/servlet containers already take care of it for us.
Glen
On 09/17/2013 03:09
[
https://issues.apache.org/jira/browse/JSPWIKI-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza closed JSPWIKI-787.
--
> jspwiki.apache.org is broken now that JSPWiki has become an Apache
[
https://issues.apache.org/jira/browse/JSPWIKI-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza resolved JSPWIKI-787.
Resolution: Fixed
jspwiki.apache.org is now displaying the website
e of record and see if that helps in being able to edit the site. We
can look after automating site's publishing after we got a working site
br,
juan pablo
On Sat, Sep 7, 2013 at 4:43 PM, Glen Mazza wrote:
JP, no response, I'm taking this as a "yes" from you (or at least
JP, no response, I'm taking this as a "yes" from you (or at least no
veto) that we can go back to one source of record for the docs and close
5943.
Regards,
Glen
On 09/05/2013 03:14 PM, Glen Mazza wrote:
OK, I'll ask if they're OK with us reverting to the old locati
nstraints
[#3]:
https://issues.apache.org/jira/browse/INFRA-6577?focusedCommentId=13724554&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13724554
On Wed, Sep 4, 2013 at 3:09 PM, Glen Mazza wrote:
JP, if I understand what you're saying, "If we could have one working
location+configu
Hi Ichiro, yes, please keep your work, someone may wish to look at it in
the future. (Perhaps you can enter it as a JIRA as an enhancement
request and supply a patch giving a general idea of what you're thinking
about.) My time is now also constrained due to other needs and it may
be awhile b
now, it's CMS
configuration problem; I'm not 100% sure, but seems it has to be
recreated (cfr. with INFRA-6492, duplicate of 6611). If we could have
one working location+configuration, be it A' or B' or whatever, I'd be
fine with it, it'll be better than our current situa
[
https://issues.apache.org/jira/browse/JSPWIKI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755768#comment-13755768
]
Glen Mazza commented on JSPWIKI-792:
Hi Harry, apparently up to 2.6.6 they calle
[
https://issues.apache.org/jira/browse/JSPWIKI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752576#comment-13752576
]
Glen Mazza commented on JSPWIKI-800:
I am unsure whether you're a software
[
https://issues.apache.org/jira/browse/JSPWIKI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752537#comment-13752537
]
Glen Mazza commented on JSPWIKI-800:
It would be nice if you could get rid of
Updated, in trunk the property is now named jspwiki.custom.cascade.#.
Glen
On 08/19/2013 01:07 AM, Harry Metske wrote:
+1
regards,
Harry
On 19 August 2013 05:13, Glen Mazza wrote:
Actually, I'd give this a day or two until I confirm the cascade stuff
still works on trunk. Team: mi
[
https://issues.apache.org/jira/browse/JSPWIKI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745756#comment-13745756
]
Glen Mazza commented on JSPWIKI-792:
Great you're looking at this.
for what you have in mind so it gets
implemented there in a standard fashion for all teams.
Regards,
Glen
On 07/31/2013 08:46 PM, Glen Mazza wrote:
OK, good, you're clearly aware of the issue. I'll focus on code
instead...
Glen
On 07/31/2013 06:43 PM, Juan Pablo Santos Rodríguez
g both properties will do more harm than good (too many ways to
declare the same thing adds too much confusion).
Glen
On 08/18/2013 05:50 PM, Glen Mazza wrote:
Thanks for the explanation. It would be good to check if the latest
changes will still work with your setup.
In yo
Thanks for the explanation. It would be good to check if the latest
changes will still work with your setup.
In your case, you'd remove the jspwiki.propertyfile parameter element
from each of your five config files and rename the
jspwiki-common.properties to jspwiki-custom.properties, and jus
loading
configuration more convenient than specifying file paths.
It simply depends on the usage scenario and also is a matter of personal
preference.
kind regards,
Harry
On 14 August 2013 22:06, Glen Mazza wrote:
I don't think so, you're reading too far down in the code, *just* abo
Tests running fine on my machine, so unsure of the problem. I'm running
the test again on Jenkins, hope it works this time. If not, it may not
be until this weekend until I can get to it. All my changes except
removing an unused variable in the the unit tests'
jspwiki-custom.properties file
s = getDefaultProperties();
On 9 August 2013 09:50, Harry Metske wrote:
Glen,
thanks, looks good.
I will do some testing too if time permits the coming week.
regards,
Harry
On 9 August 2013 00:27, Glen Mazza wrote:
Hi All,
OK, converted. Main issue was that I had to move
bsites/production/jspwiki/content/index.html Sat Aug 10 15:10:37 2013
@@ -20,19 +20,19 @@
- http://incubator.apache.org"; alt="Apache Incubator">
-
+ http://www.apache.org"; alt="Apache Software Foundation">
+
[
https://issues.apache.org/jira/browse/JSPWIKI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735637#comment-13735637
]
Glen Mazza commented on JSPWIKI-792:
That would be great. If it would help, Ro
desires. I don't think
performance is
generally an issue here - the wiki isn't slowed down much by delivering
what is in
actuality a rather small stylesheet.
Anyway, my 2c.
Ichiro
On Thu, Aug 8, 2013 at 11:31 PM, Glen Mazza wrote:
On 08/07/2013 05:47 AM, Dirk Frederickx wrote:
One of
x27;m +1 on your approach
br,
juan pablo
On Thu, Aug 8, 2013 at 2:43 PM, Glen Mazza wrote:
Umm, I really would *not* want to go that route, there's no practical
benefit to providing both options (never has been on Roller for over a
decade now), it would raise unnecessary confusion among users,
ies, loaded first, from war (unless -Djspwiki.propertyfile
is given)
- jspwiki-custom.properties, loaded afterwards, from classpath (unless
-Djspwiki.custom.config is given)
br,
juan pablo
On Thu, Aug 8, 2013 at 2:14 PM, Glen Mazza wrote:
Yes, I like -Djspwiki.custom.config too. I'll see what I c
w_ these things play
together, both in documentation and logging.
kind regards,
Harry
On 8 August 2013 13:56, Glen Mazza wrote:
Yes, [#1] would be the [3] I mentioned below. But would it be a problem
if I renamed our "-Djspwiki.propertyfile" setting to
"-Djspw
ty values are
going to be active.
(and, similar to what Ichiro already mentioned, it should play nice with
JSPWiki System property mechanism, see [#1].
[#1] https://issues.apache.org/jira/browse/JSPWIKI-568
kind regards,
Harry
On 7 August 2013 05:43, Glen Mazza wrote:
Hi Team,
Apache Roller m
On 08/07/2013 06:10 AM, Dirk Frederickx wrote:
I recommend to only run JSLINT on the javascript written dedicated for
JSPWiki. JSLINT should not be run on the external libraries ( such as
mootools.js, prettify.js ) on which we are not having any impact anyway.
+1. The errors reported by jshin
On 08/07/2013 05:47 AM, Dirk Frederickx wrote:
One of the main advantages for using wro4j at RUNTIME, is that the wro4j
filter also GZIP's the JS and CSS files. This has an enormous impact on
the size of these files, and we should definitely consider to add this to
JSPWiki in the future.
( ei
spwiki/trunk/ChangeLog (original)
+++ jspwiki/trunk/ChangeLog Wed Aug 7 13:17:48 2013
@@ -1,3 +1,9 @@
+2013-08-07 Glen Mazza (gmazza AT apache DOT org)
+
+ * 2.10.0-svn-34
+
+ * Upgrade from Jetty used in unit test cases from v. 7.6.7 to v.
9.0.4
+
2013-08-06 Juan Pablo Santos (juanp
1 - 100 of 139 matches
Mail list logo
