[jira] [Commented] (JSPWIKI-825) Integration tests fail on Mac OS X due to "IllegalAccessException for stop method in class org.apache.tomcat.maven.plugin.tomcat7.run.ExtendedTomcat"
[
https://issues.apache.org/jira/browse/JSPWIKI-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749369#comment-16749369
]
Siegfried Goeschl commented on JSPWIKI-825:
---
Will try tomorrow :)
> Integration tests fail on Mac OS X due to "IllegalAccessException for stop
> method in class org.apache.tomcat.maven.plugin.tomcat7.run.ExtendedTomcat"
> -
>
> Key: JSPWIKI-825
> URL: https://issues.apache.org/jira/browse/JSPWIKI-825
> Project: JSPWiki
> Issue Type: Bug
> Components: Integration Testing
>Affects Versions: 2.10.1
> Environment: Mac OS X 10.9.2
> java -version
> java version "1.7.0_45"
> Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
> Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
>Reporter: Siegfried Goeschl
>Priority: Major
>
> Started the integration tests and got a failure indicating some problem with
> the tests setup - is there something I have to do/prepare in oder to run the
> integration tests?
> {noformat)
> jspwiki-it-tests> mvn clean install -Pintegration-tests
> ...
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] jspwiki-it-builder SUCCESS [1.800s]
> [INFO] jspwiki-selenium-tests SUCCESS [2.756s]
> [INFO] jspwiki-it-test-custom FAILURE [43.273s]
> [INFO] jspwiki-it-test-custom-absolute-urls .. SKIPPED
> [INFO] jspwiki-it-test-custom-jdbc ... SKIPPED
> [INFO] jspwiki-it-test-cma ... SKIPPED
> [INFO] jspwiki-it-test-cma-jdbc .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 48.095s
> [INFO] Finished at: Mon Mar 10 18:50:57 CET 2014
> [INFO] Final Memory: 51M/329M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:selenium-maven-plugin:2.3:selenese (test) on project
> jspwiki-it-test-custom: Tests failed, see result file for details:
> /Users/sgoeschl/work/github/apache-jspwiki/jspwiki-it-tests/jspwiki-it-test-custom/target/results-googlechrome-TestSuite.html
> -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :jspwiki-it-test-custom
> ERROR: IllegalAccessException for stop method in class
> org.apache.tomcat.maven.plugin.tomcat7.run.ExtendedTomcat
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.tomcat.maven.common.run.EmbeddedRegistry.shutdownAll(EmbeddedRegistry.java:110)
> at
> org.apache.tomcat.maven.common.run.EmbeddedRegistry$1.run(EmbeddedRegistry.java:69)
> Caused by: org.apache.catalina.LifecycleException: Failed to stop component
> [StandardServer[-1]]
> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
> at org.apache.catalina.startup.Tomcat.stop(Tomcat.java:345)
> ... 6 more
> Caused by: org.apache.catalina.LifecycleException: Failed to stop component
> [StandardService[Tomcat]]
> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
> at
> org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:753)
> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
> ... 7 more
> Caused by: org.apache.catalina.LifecycleException: Failed to stop component
> [StandardEngine[Tomcat]]
> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
> at
> org.apache.catalina.core.StandardService.stopInternal(StandardService.java:502)
> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
> ... 9 more
> Caused by: java.lang.NoClassDefFoundError:
>
[jira] [Commented] (JSPWIKI-1073) Upgrade the jspwiki-portable build
[ https://issues.apache.org/jira/browse/JSPWIKI-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16576373#comment-16576373 ] Siegfried Goeschl commented on JSPWIKI-1073: * Tomcat 7.0.90 was already used - thanks to everybody taking care of it :) * Enabled Haddock templates for the two preconfigured wikis * Improved the `readme.md` * Impoved the `.gitignore` to handle IntelliJ project files > Upgrade the jspwiki-portable build > --- > > Key: JSPWIKI-1073 > URL: https://issues.apache.org/jira/browse/JSPWIKI-1073 > Project: JSPWiki > Issue Type: Task > Components: Build system >Affects Versions: 2.10.4 >Reporter: Siegfried Goeschl >Assignee: Siegfried Goeschl >Priority: Major > Fix For: 2.10.5 > > > Since I'm updating my local JSPWiki installation I noticed that the > `jspwiki-portable` needs some love > * Update to latest Tomcat 7.x > * Enable the Haddock templates out of the box -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JSPWIKI-1073) Upgrade the jspwiki-portable build
[ https://issues.apache.org/jira/browse/JSPWIKI-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siegfried Goeschl updated JSPWIKI-1073: --- Assignee: Siegfried Goeschl > Upgrade the jspwiki-portable build > --- > > Key: JSPWIKI-1073 > URL: https://issues.apache.org/jira/browse/JSPWIKI-1073 > Project: JSPWiki > Issue Type: Task > Components: Build system >Affects Versions: 2.10.4 >Reporter: Siegfried Goeschl >Assignee: Siegfried Goeschl >Priority: Major > Fix For: 2.10.5 > > > Since I'm updating my local JSPWiki installation I noticed that the > `jspwiki-portable` needs some love > * Update to latest Tomcat 7.x > * Enable the Haddock templates out of the box -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (JSPWIKI-1073) Upgrade the jspwiki-portable build
Siegfried Goeschl created JSPWIKI-1073: -- Summary: Upgrade the jspwiki-portable build Key: JSPWIKI-1073 URL: https://issues.apache.org/jira/browse/JSPWIKI-1073 Project: JSPWiki Issue Type: Task Components: Build system Affects Versions: 2.10.4 Reporter: Siegfried Goeschl Fix For: 2.10.5 Since I'm updating my local JSPWiki installation I noticed that the `jspwiki-portable` needs some love * Update to latest Tomcat 7.x * Enable the Haddock templates out of the box -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JSPWIKI-1035) get rid of jspwiki.baseURL
[ https://issues.apache.org/jira/browse/JSPWIKI-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783527#comment-15783527 ] Siegfried Goeschl commented on JSPWIKI-1035: [~metskem] I played with JSPWiki portable from the JSPWIKI-1035 branch and it looks good :-) > get rid of jspwiki.baseURL > -- > > Key: JSPWIKI-1035 > URL: https://issues.apache.org/jira/browse/JSPWIKI-1035 > Project: JSPWiki > Issue Type: Improvement > Components: Core & storage >Affects Versions: 2.10.2 >Reporter: Jürgen Weber >Assignee: Harry Metske > Attachments: DefaultURLConstructor.java.patch, WikiEngine.java.patch, > jspwiki.properties.patch > > > Could we get rid of jspwiki.baseURL and calculate it on > HttpServletRequest#getContextPath() ? > It's the only mandatory property you have to set for JSPWiki, so removing it > would make installation much easier. > And, first and foremost, it makes JSPWiki only work on exactly this URL, i.e. > you cannot use the same JSPWiki instance in an intranet and on the internet > (e.g. wiki.firm.com and wiki.firm.private), neither with and without JK'ed > Apache, neither SSL and non-SSL. > If you look at the source of https://jspwiki-wiki.apache.org/ > there are not many places where the whole base url is used. So, I wonder, if > context relative links could be sufficient. > http://stackoverflow.com/questions/4764405/how-to-use-relative-paths-without-including-the-context-root-name -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JSPWIKI-1035) get rid of jspwiki.baseURL
[ https://issues.apache.org/jira/browse/JSPWIKI-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15648016#comment-15648016 ] Siegfried Goeschl commented on JSPWIKI-1035: That would be awesome :-) > get rid of jspwiki.baseURL > -- > > Key: JSPWIKI-1035 > URL: https://issues.apache.org/jira/browse/JSPWIKI-1035 > Project: JSPWiki > Issue Type: Improvement > Components: Core & storage >Affects Versions: 2.10.2 >Reporter: Jürgen Weber > > Could we get rid of jspwiki.baseURL and calculate it on > HttpServletRequest#getContextPath() ? > It's the only mandatory property you have to set for JSPWiki, so removing it > would make installation much easier. > And, first and foremost, it makes JSPWiki only work on exactly this URL, i.e. > you cannot use the same JSPWiki instance in an intranet and on the internet > (e.g. wiki.firm.com and wiki.firm.private), neither with and without JK'ed > Apache, neither SSL and non-SSL. > If you look at the source of https://jspwiki-wiki.apache.org/ > there are not many places where the whole base url is used. So, I wonder, if > context relative links could be sufficient. > http://stackoverflow.com/questions/4764405/how-to-use-relative-paths-without-including-the-context-root-name -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JSPWIKI-922) java.io.IOException: Upload Files to a Page with german Umlaute
[ https://issues.apache.org/jira/browse/JSPWIKI-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14992179#comment-14992179 ] Siegfried Goeschl commented on JSPWIKI-922: --- I'm not exactly able to reproduce the issue * I'm using an English locale (sorry, have to find out how to switch to that German thingie) * Created a page "üäöß" and added wiki markup * The displayed page title is wrong it shows "" so there seems to be another issue * I can successfully upload a file having no "german umlaut" * but if I upload a file, e.g. "österreich.json" I get a 404 - Attachment 'ÃSterreich.json', version -1 does not exist. Quick question * any idea what file encoding your JVM is using (see JSPWiki System Info Page) > java.io.IOException: Upload Files to a Page with german Umlaute > --- > > Key: JSPWIKI-922 > URL: https://issues.apache.org/jira/browse/JSPWIKI-922 > Project: JSPWiki > Issue Type: Bug >Affects Versions: 2.10.1 >Reporter: Christopher Janitschke > > I have several pages with german umlaute in the pagename. > If i try to upload a file to one of these pages i get an exception. > - > java.io.IOException: Upload failed because the provider failed: Die > übergeordnete Seite existiert nicht. > > org.apache.wiki.attachment.AttachmentServlet.upload(AttachmentServlet.java:565) > > org.apache.wiki.attachment.AttachmentServlet.doPost(AttachmentServlet.java:416) > javax.servlet.http.HttpServlet.service(HttpServlet.java:648) > javax.servlet.http.HttpServlet.service(HttpServlet.java:729) > org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) > > org.apache.wiki.ui.WikiServletFilter.doFilter(WikiServletFilter.java:177) > - > I tried it with UTF-8 and ISO-8859-1. > For now we rename those pages, but it would be nice if this would work in the > future. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (JSPWIKI-907) [Portable] Remove GPLed build tools
Siegfried Goeschl created JSPWIKI-907:
-
Summary: [Portable] Remove GPLed build tools
Key: JSPWIKI-907
URL: https://issues.apache.org/jira/browse/JSPWIKI-907
Project: JSPWiki
Issue Type: Bug
Components: Build system
Affects Versions: 2.10.1
Reporter: Siegfried Goeschl
Assignee: Siegfried Goeschl
Priority: Blocker
Fix For: 2.10.2
When creating the JSPWiki portable build I completely missed the fact that some
of the stuff is GPL-2.0
Currently we have the following dependencies for the jspwiki-portable build
{noformat}
appbundler-1.0.jar
=
License:GPL-2.0
Homepage: https://java.net/projects/appbundler
Download:
https://java.net/projects/appbundler/downloads/download/appbundler-1.0.jar
jarbundler-2.2.0.jar
=
License:GPL-2.0
Homepage: http://informagen.com/JarBundler/index.html
Download:
http://downloads.sourceforge.net/project/jarbundler/JarBundler/v2.3.1/jarbundler.tar.gz
launch4j-3.1.0-beta-2
=
Licence:BSD License, MIT License
Homepage: http://launch4j.sourceforge.net
Download: https://sourceforge.net/projects/launch4j/files/launch4j-3/3.8/
Notes: Includes GPL-2.0 binaries so need to download
JavaApplicationStub
=
Licence:
/System/Library/Frameworks/JavaVM.framework/Resources/Documentation/JavaApplicationStub-License.rtf
{noformat}
The idea is to either download the things dynamically (or force the build
manager to have the tools installed)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JSPWIKI-893) Cannot search for bold words with GermanAnalyzer
[
https://issues.apache.org/jira/browse/JSPWIKI-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695748#comment-14695748
]
Siegfried Goeschl commented on JSPWIKI-893:
---
Could be a bug in Lucene 4.7.0 - the current version is 5.2.1
Cannot search for bold words with GermanAnalyzer
Key: JSPWIKI-893
URL: https://issues.apache.org/jira/browse/JSPWIKI-893
Project: JSPWiki
Issue Type: Bug
Affects Versions: 2.10
Reporter: Arend v. Reinersdorff
Reproduce:
* in jspwiki-custom.properties set
{{jspwiki.lucene.analyzer = org.apache.lucene.analysis.de.GermanAnalyzer}}
* in a wiki page include {{\_\_mysearchterm\_\_}}
Result:
* Searching for {{mysearchterm}} doesn't find the text
* Searching for {{\_\_mysearchterm\_\_}} finds the text
Expected:
Searching for {{mysearchterm}} should find the text, as it does with
{{org.apache.lucene.analysis.standard.StandardAnalyzer}}
See also the thread on the mailinglist:
http://mail-archives.apache.org/mod_mbox/jspwiki-user/201506.mbox/%3CCAJCBYx0M_Xqm1jt8Pr466rRb8sLLLf28eygn9FrA4%3Dhrb6aHeg%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JSPWIKI-893) Cannot search for bold words with GermanAnalyzer
[
https://issues.apache.org/jira/browse/JSPWIKI-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695745#comment-14695745
]
Siegfried Goeschl commented on JSPWIKI-893:
---
From Arend's email
{noformat}
The problem is
jspwiki.lucene.analyzer = org.apache.lucene.analysis.de.GermanAnalyzer
When I turn that off and delete the Lucene index files, I can find bold words.
When I turn it on again and delete the Lucene index files, I cannot find bold
words anymore.
Siegfried, thanks for pointing me in the direction of search related properties
:-)
{noformat}
Cannot search for bold words with GermanAnalyzer
Key: JSPWIKI-893
URL: https://issues.apache.org/jira/browse/JSPWIKI-893
Project: JSPWiki
Issue Type: Bug
Affects Versions: 2.10
Reporter: Arend v. Reinersdorff
Reproduce:
* in jspwiki-custom.properties set
{{jspwiki.lucene.analyzer = org.apache.lucene.analysis.de.GermanAnalyzer}}
* in a wiki page include {{\_\_mysearchterm\_\_}}
Result:
* Searching for {{mysearchterm}} doesn't find the text
* Searching for {{\_\_mysearchterm\_\_}} finds the text
Expected:
Searching for {{mysearchterm}} should find the text, as it does with
{{org.apache.lucene.analysis.standard.StandardAnalyzer}}
See also the thread on the mailinglist:
http://mail-archives.apache.org/mod_mbox/jspwiki-user/201506.mbox/%3CCAJCBYx0M_Xqm1jt8Pr466rRb8sLLLf28eygn9FrA4%3Dhrb6aHeg%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JSPWIKI-907) [Portable] Remove GPLed build tools
[
https://issues.apache.org/jira/browse/JSPWIKI-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695868#comment-14695868
]
Siegfried Goeschl commented on JSPWIKI-907:
---
Removed the launch4j stuff but it currently only works when executed under Mac
OS X
[Portable] Remove GPLed build tools
---
Key: JSPWIKI-907
URL: https://issues.apache.org/jira/browse/JSPWIKI-907
Project: JSPWiki
Issue Type: Bug
Components: Build system
Affects Versions: 2.10.1
Reporter: Siegfried Goeschl
Assignee: Siegfried Goeschl
Priority: Blocker
Fix For: 2.10.2
When creating the JSPWiki portable build I completely missed the fact that
some of the stuff is GPL-2.0
Currently we have the following dependencies for the jspwiki-portable build
{noformat}
appbundler-1.0.jar
=
License:GPL-2.0
Homepage: https://java.net/projects/appbundler
Download:
https://java.net/projects/appbundler/downloads/download/appbundler-1.0.jar
jarbundler-2.2.0.jar
=
License:GPL-2.0
Homepage: http://informagen.com/JarBundler/index.html
Download:
http://downloads.sourceforge.net/project/jarbundler/JarBundler/v2.3.1/jarbundler.tar.gz
launch4j-3.1.0-beta-2
=
Licence:BSD License, MIT License
Homepage: http://launch4j.sourceforge.net
Download: https://sourceforge.net/projects/launch4j/files/launch4j-3/3.8/
Notes: Includes GPL-2.0 binaries so need to download
JavaApplicationStub
=
Licence:
/System/Library/Frameworks/JavaVM.framework/Resources/Documentation/JavaApplicationStub-License.rtf
{noformat}
The idea is to either download the things dynamically (or force the build
manager to have the tools installed)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JSPWIKI-303) JSPWiki-API library creation
[ https://issues.apache.org/jira/browse/JSPWIKI-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14606353#comment-14606353 ] Siegfried Goeschl commented on JSPWIKI-303: --- Anyone who can move the fix version to 3.1?! Somehow I can't do that :-) JSPWiki-API library creation Key: JSPWIKI-303 URL: https://issues.apache.org/jira/browse/JSPWIKI-303 Project: JSPWiki Issue Type: New Feature Components: Core storage Reporter: Janne Jalkanen Assignee: Juan Pablo Santos Rodríguez Priority: Critical Fix For: 2.10.2 The proposal is to create a jspwiki-api.jar, which would contain all the interfaces and classes from com.ecyrd.jspwiki.api -package. This would be a new package, which contains a set of interfaces (and probably some basic datacontainer classes) to provide access to JSPWiki innards. The design of the API set is available in http://www.jspwiki.org/wiki/JSPWiki3APIDesignProposal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JSPWIKI-303) JSPWiki-API library creation
[ https://issues.apache.org/jira/browse/JSPWIKI-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siegfried Goeschl updated JSPWIKI-303: -- Fix Version/s: 3.1 JSPWiki-API library creation Key: JSPWIKI-303 URL: https://issues.apache.org/jira/browse/JSPWIKI-303 Project: JSPWiki Issue Type: New Feature Components: Core storage Reporter: Janne Jalkanen Assignee: Juan Pablo Santos Rodríguez Priority: Critical Fix For: 3.0 The proposal is to create a jspwiki-api.jar, which would contain all the interfaces and classes from com.ecyrd.jspwiki.api -package. This would be a new package, which contains a set of interfaces (and probably some basic datacontainer classes) to provide access to JSPWiki innards. The design of the API set is available in http://www.jspwiki.org/wiki/JSPWiki3APIDesignProposal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JSPWIKI-303) JSPWiki-API library creation
[ https://issues.apache.org/jira/browse/JSPWIKI-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siegfried Goeschl updated JSPWIKI-303: -- Fix Version/s: (was: 3.1) 3.0 JSPWiki-API library creation Key: JSPWIKI-303 URL: https://issues.apache.org/jira/browse/JSPWIKI-303 Project: JSPWiki Issue Type: New Feature Components: Core storage Reporter: Janne Jalkanen Assignee: Juan Pablo Santos Rodríguez Priority: Critical Fix For: 3.0 The proposal is to create a jspwiki-api.jar, which would contain all the interfaces and classes from com.ecyrd.jspwiki.api -package. This would be a new package, which contains a set of interfaces (and probably some basic datacontainer classes) to provide access to JSPWiki innards. The design of the API set is available in http://www.jspwiki.org/wiki/JSPWiki3APIDesignProposal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JSPWIKI-888) Enable cache timeouts for Portable JSPWiki
[ https://issues.apache.org/jira/browse/JSPWIKI-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siegfried Goeschl updated JSPWIKI-888: -- Description: When running the Portable JSPWiki it is common that some wiki pages are updated on the file system level, e.g. Dropbox. JSPWiki currently doesn't doing any checks (as documented) and the default ehcache.xml does not provide a value for timeToLiveSeconds - in this case the cache entry will never expire. For the portable scenario a custom ehache.xml will be provided setting * maxElementsInMemory=128 * timeToLiveSeconds=7200 was: When running the Portable JSPWiki it is common that some wiki pages are updated on the file system level, e.g. Dropbox. JSPWiki currently doesn't doing any checks (as documented) and the default ehcache.xml does not provide a value for timeToLiveSeconds - in this case the cache entry will never expire. For the portable scenario a custom ehache.xml will be provided setting * maxElementsInMemory=100 * timeToLiveSeconds=3600 Enable cache timeouts for Portable JSPWiki -- Key: JSPWIKI-888 URL: https://issues.apache.org/jira/browse/JSPWIKI-888 Project: JSPWiki Issue Type: Improvement Components: Core storage Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Fix For: 2.10.2 When running the Portable JSPWiki it is common that some wiki pages are updated on the file system level, e.g. Dropbox. JSPWiki currently doesn't doing any checks (as documented) and the default ehcache.xml does not provide a value for timeToLiveSeconds - in this case the cache entry will never expire. For the portable scenario a custom ehache.xml will be provided setting * maxElementsInMemory=128 * timeToLiveSeconds=7200 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (JSPWIKI-888) Enable cache timeouts for Portable JSPWiki
Siegfried Goeschl created JSPWIKI-888: - Summary: Enable cache timeouts for Portable JSPWiki Key: JSPWIKI-888 URL: https://issues.apache.org/jira/browse/JSPWIKI-888 Project: JSPWiki Issue Type: Improvement Components: Core storage Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Fix For: 2.10.2 When running the Portable JSPWiki it is common that some wiki pages are updated on the file system level, e.g. Dropbox. JSPWiki currently doesn't doing any checks (as documented) and the default ehcache.xml does not provide a value for timeToLiveSeconds - in this case the cache entry will never expire. For the portable scenario a custom ehache.xml will be provided setting * maxElementsInMemory=100 * timeToLiveSeconds=3600 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JSPWIKI-888) Enable cache timeouts for Portable JSPWiki
[ https://issues.apache.org/jira/browse/JSPWIKI-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14602864#comment-14602864 ] Siegfried Goeschl commented on JSPWIKI-888: --- Done Enable cache timeouts for Portable JSPWiki -- Key: JSPWIKI-888 URL: https://issues.apache.org/jira/browse/JSPWIKI-888 Project: JSPWiki Issue Type: Improvement Components: Core storage Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Fix For: 2.10.2 When running the Portable JSPWiki it is common that some wiki pages are updated on the file system level, e.g. Dropbox. JSPWiki currently doesn't doing any checks (as documented) and the default ehcache.xml does not provide a value for timeToLiveSeconds - in this case the cache entry will never expire. For the portable scenario a custom ehache.xml will be provided setting * maxElementsInMemory=128 * timeToLiveSeconds=7200 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (JSPWIKI-837) [Portable] Create native Mac OS X launcher for Oracle JDK 1.7+
[ https://issues.apache.org/jira/browse/JSPWIKI-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siegfried Goeschl resolved JSPWIKI-837. --- Resolution: Fixed Migrated to appbundler in April and happily using it [Portable] Create native Mac OS X launcher for Oracle JDK 1.7+ -- Key: JSPWIKI-837 URL: https://issues.apache.org/jira/browse/JSPWIKI-837 Project: JSPWiki Issue Type: New Feature Components: Build system Affects Versions: 2.10.1 Environment: Mac OS X Reporter: Siegfried Goeschl Fix For: 2.10.2 The current launcher relies on the Apple JDK 1.6 but the JDK is basically dead and the Oracle JDK is used causing a few issues * Oracle JDK uses different installation directories * jarbundler does not support Oracle JDK * need to migrate to appbundler -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JSPWIKI-304) Workflows are not Serializable
[ https://issues.apache.org/jira/browse/JSPWIKI-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14601941#comment-14601941 ] Siegfried Goeschl commented on JSPWIKI-304: --- Since the next maintenance release is near - any progress on that? Workflows are not Serializable -- Key: JSPWIKI-304 URL: https://issues.apache.org/jira/browse/JSPWIKI-304 Project: JSPWiki Issue Type: Improvement Components: Core storage Affects Versions: 2.8.1 Environment: All Reporter: Andrew Jaquith Fix For: 2.10.2 At the moment, workflows cannot be serialized. This makes it fairly useless because moderated page-save operations and user profile creations cannot persist between WikiEngine restarts. We provided a partial fix for this problem, which made most of the com.ecyrd.jspwiki.workflow package serializable. This filing addresses the rest of it: - Parameters passed to Workflow.setAttribute(String,Object) -- change Object to Serializable - Parameters passed to Step.setAttribute(String,Object) and all implementations -- change Object to Serializable - Value returned by Workflow.getAttribute(String) -- change return type from Object to Serializable - Value returned by Step.getAttribute(String) and all implementations -- change return type from Object to Serializable We will also provide a mechanism for serializing the workflow objects to disk, perhaps similar to the way ReferenceManager works. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (JSPWIKI-828) [Portable] Make the jspwiki-portable (aka WOAS) contribution a proper part of JSPWiki
[ https://issues.apache.org/jira/browse/JSPWIKI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siegfried Goeschl resolved JSPWIKI-828. --- Resolution: Fixed Tested on Mac Windows (thanks to Juan Pablo Santos Rodríguez) so I'm closing the task [Portable] Make the jspwiki-portable (aka WOAS) contribution a proper part of JSPWiki --- Key: JSPWIKI-828 URL: https://issues.apache.org/jira/browse/JSPWIKI-828 Project: JSPWiki Issue Type: Task Components: Build system Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Fix For: 2.10.2 Originally the portable JSPWiki (aka WOAS) was based on JSPWiki 2.8.x using Ant * we are now on 2.10.1 * we migrated from Ant to Maven * the native launchers for Windows Mac OS X are outdated * the embedded Jetty is outdated -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JSPWIKI-828) [Portable] Make the jspwiki-portable (aka WOAS) contribution a proper part of JSPWiki
[ https://issues.apache.org/jira/browse/JSPWIKI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237870#comment-14237870 ] Siegfried Goeschl commented on JSPWIKI-828: --- Over the time I made the following changes in https://github.com/sgoeschl/apache-jspwiki * Using Oracle's AppBundler Task to work with an existing JDK 1.7+ on Mac OS X * Using Tomcat instead of Jetty since the memory foot-print is smaller and I'm more familiar with Tomcat anyway All the contributed bugfixes are committed in trunk so it is a good time to move the stuff to SVN :-) [Portable] Make the jspwiki-portable (aka WOAS) contribution a proper part of JSPWiki --- Key: JSPWIKI-828 URL: https://issues.apache.org/jira/browse/JSPWIKI-828 Project: JSPWiki Issue Type: Task Components: Build system Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Fix For: 2.10.2 Originally the portable JSPWiki (aka WOAS) was based on JSPWiki 2.8.x using Ant * we are now on 2.10.1 * we migrated from Ant to Maven * the native launchers for Windows Mac OS X are outdated * the embedded Jetty is outdated -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (JSPWIKI-829) [Portable] Integrate jspwiki-portable into the jspwiki maven build
[ https://issues.apache.org/jira/browse/JSPWIKI-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siegfried Goeschl resolved JSPWIKI-829. --- Resolution: Fixed Committed the changes and jspwiki-portable is now build from the top-level project [Portable] Integrate jspwiki-portable into the jspwiki maven build -- Key: JSPWIKI-829 URL: https://issues.apache.org/jira/browse/JSPWIKI-829 Project: JSPWiki Issue Type: Sub-task Components: Build system Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Fix For: 2.10.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JSPWIKI-828) [Portable] Make the jspwiki-portable (aka WOAS) contribution a proper part of JSPWiki
[ https://issues.apache.org/jira/browse/JSPWIKI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237922#comment-14237922 ] Siegfried Goeschl commented on JSPWIKI-828: --- Committed my changes - anyone having some spare cycles to build the whole project on his/her box? [Portable] Make the jspwiki-portable (aka WOAS) contribution a proper part of JSPWiki --- Key: JSPWIKI-828 URL: https://issues.apache.org/jira/browse/JSPWIKI-828 Project: JSPWiki Issue Type: Task Components: Build system Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Fix For: 2.10.2 Originally the portable JSPWiki (aka WOAS) was based on JSPWiki 2.8.x using Ant * we are now on 2.10.1 * we migrated from Ant to Maven * the native launchers for Windows Mac OS X are outdated * the embedded Jetty is outdated -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JSPWIKI-205) Obfuscate on disk content type
[ https://issues.apache.org/jira/browse/JSPWIKI-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14139403#comment-14139403 ] Siegfried Goeschl commented on JSPWIKI-205: --- Hi folks, the relevant link is [http://www.apache.org/dev/crypto.html] having the following requirement Software using a symmetric algorithm employing a key length in excess of 56-bits; in other words - if you use DES you are fine (56 bit key) but using AES or Blowfish requires the legal stuff Obfuscate on disk content type -- Key: JSPWIKI-205 URL: https://issues.apache.org/jira/browse/JSPWIKI-205 Project: JSPWiki Issue Type: Improvement Components: Core storage Reporter: Chris Lialios Priority: Trivial Attachments: BasicOverview.doc, EncryptingProviderSource.zip, encryption.patch We would like to store passwords within the wiki pages. Securing the page is trivial, however the contents on disk remain clear text. It would be very nice to have a page type that could be stored in an obfuscated form on disk. As an addition have a secondary password to display/edit the encrypted contents on disk for those who do not want to use wiki security on the page. I suspect this will have potentially drastic effects on the revisions process, but it would be a small price to pay for security. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JSPWIKI-828) [Portable] Make the jspwiki-portable (aka WOAS) contribution a proper part of JSPWiki
[ https://issues.apache.org/jira/browse/JSPWIKI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siegfried Goeschl updated JSPWIKI-828: -- Summary: [Portable] Make the jspwiki-portable (aka WOAS) contribution a proper part of JSPWiki (was: Make the jspwiki-portable (aka WOAS) contribution a proper part of JSPWiki) [Portable] Make the jspwiki-portable (aka WOAS) contribution a proper part of JSPWiki --- Key: JSPWIKI-828 URL: https://issues.apache.org/jira/browse/JSPWIKI-828 Project: JSPWiki Issue Type: Task Components: Build system Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Fix For: 2.10.1 Originally the portable JSPWiki (aka WOAS) was based on JSPWiki 2.8.x using Ant * we are now on 2.10.1 * we migrated from Ant to Maven * the native launchers for Windows Mac OS X are outdated * the embedded Jetty is outdated -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (JSPWIKI-832) [Portable] Problems setting up multiple wikis using a shared JSPWiki libraries
[
https://issues.apache.org/jira/browse/JSPWIKI-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siegfried Goeschl updated JSPWIKI-832:
--
Summary: [Portable] Problems setting up multiple wikis using a shared
JSPWiki libraries (was: Problems setting up multiple wikis using a shared
JSPWiki libraries)
[Portable] Problems setting up multiple wikis using a shared JSPWiki libraries
--
Key: JSPWIKI-832
URL: https://issues.apache.org/jira/browse/JSPWIKI-832
Project: JSPWiki
Issue Type: Task
Components: Core storage
Affects Versions: 2.10
Reporter: Siegfried Goeschl
Fix For: 2.10.1
Attachments:
JSPWIKI-832_Problems_setting_up_multiple_wikis_using_a_shared_JSPWiki_libraries.patch
For “jspwiki-portable” I try to
* run the JSPWiki libraries and its dependencies from CATALINA_HOME/lib
* run the wiki pages from a separate WAR whereas each WAR contains the
required configuration files
AFAIK that worked with JSPWiki 2.9.x but is broken for the current trunk :-(
The main problem seems to be that EHCache Manager is only available once for
the whole Tomcat and therefore the same caches are used for multiple wikis.
What I'm trying to do is the following
{noformat}
String documentCacheName = engine.getApplicationName() + . +
DOCUMENTCACHE_NAME;
if (m_cacheManager.cacheExists(documentCacheName)) {
m_documentCache = m_cacheManager.getCache(documentCacheName);
} else {
log.info(cache with name + documentCacheName + not found in
ehcache.xml, creating it with defaults.);
m_documentCache = new Cache(documentCacheName, DEFAULT_CACHESIZE,
false, false, m_cacheExpiryPeriod, m_cacheExpiryPeriod);
m_cacheManager.addCache(m_documentCache);
}
{noformat}
which is to use a prefix for the cache based on the application name
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (JSPWIKI-832) Problems setting up multiple wikis using a shared JSPWiki libraries
Siegfried Goeschl created JSPWIKI-832:
-
Summary: Problems setting up multiple wikis using a shared JSPWiki
libraries
Key: JSPWIKI-832
URL: https://issues.apache.org/jira/browse/JSPWIKI-832
Project: JSPWiki
Issue Type: Task
Components: Core storage
Affects Versions: 2.10
Reporter: Siegfried Goeschl
Fix For: 2.10.1
For “jspwiki-portable” I try to
* run the JSPWiki libraries and its dependencies from CATALINA_HOME/lib
* run the wiki pages from a separate WAR whereas each WAR contains the required
configuration files
AFAIK that worked with JSPWiki 2.9.x but is broken for the current trunk :-(
The main problem seems to be that EHCache Manager is only available once for
the whole Tomcat and therefore the same caches are used for multiple wikis.
What I'm trying to do is the following
{noformat}
String documentCacheName = engine.getApplicationName() + . +
DOCUMENTCACHE_NAME;
if (m_cacheManager.cacheExists(documentCacheName)) {
m_documentCache = m_cacheManager.getCache(documentCacheName);
} else {
log.info(cache with name + documentCacheName + not found in
ehcache.xml, creating it with defaults.);
m_documentCache = new Cache(documentCacheName, DEFAULT_CACHESIZE,
false, false, m_cacheExpiryPeriod, m_cacheExpiryPeriod);
m_cacheManager.addCache(m_documentCache);
}
{noformat}
which is to use a prefix for the cache based on the application name
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (JSPWIKI-832) Problems setting up multiple wikis using a shared JSPWiki libraries
[
https://issues.apache.org/jira/browse/JSPWIKI-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siegfried Goeschl updated JSPWIKI-832:
--
Attachment:
JSPWIKI-832_Problems_setting_up_multiple_wikis_using_a_shared_JSPWiki_libraries.patch
Using the app name to prefix the cache name
Problems setting up multiple wikis using a shared JSPWiki libraries
---
Key: JSPWIKI-832
URL: https://issues.apache.org/jira/browse/JSPWIKI-832
Project: JSPWiki
Issue Type: Task
Components: Core storage
Affects Versions: 2.10
Reporter: Siegfried Goeschl
Fix For: 2.10.1
Attachments:
JSPWIKI-832_Problems_setting_up_multiple_wikis_using_a_shared_JSPWiki_libraries.patch
For “jspwiki-portable” I try to
* run the JSPWiki libraries and its dependencies from CATALINA_HOME/lib
* run the wiki pages from a separate WAR whereas each WAR contains the
required configuration files
AFAIK that worked with JSPWiki 2.9.x but is broken for the current trunk :-(
The main problem seems to be that EHCache Manager is only available once for
the whole Tomcat and therefore the same caches are used for multiple wikis.
What I'm trying to do is the following
{noformat}
String documentCacheName = engine.getApplicationName() + . +
DOCUMENTCACHE_NAME;
if (m_cacheManager.cacheExists(documentCacheName)) {
m_documentCache = m_cacheManager.getCache(documentCacheName);
} else {
log.info(cache with name + documentCacheName + not found in
ehcache.xml, creating it with defaults.);
m_documentCache = new Cache(documentCacheName, DEFAULT_CACHESIZE,
false, false, m_cacheExpiryPeriod, m_cacheExpiryPeriod);
m_cacheManager.addCache(m_documentCache);
}
{noformat}
which is to use a prefix for the cache based on the application name
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (JSPWIKI-823) JSPWiki tests fail under Mac OS X due to permissions for TMP directory
[ https://issues.apache.org/jira/browse/JSPWIKI-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925907#comment-13925907 ] Siegfried Goeschl commented on JSPWIKI-823: --- Good idea - I'm preparing a patch JSPWiki tests fail under Mac OS X due to permissions for TMP directory -- Key: JSPWIKI-823 URL: https://issues.apache.org/jira/browse/JSPWIKI-823 Project: JSPWiki Issue Type: Bug Components: Build system Affects Versions: 2.10.1 Environment: Mac OS X 10.9.2 java version 1.7.0_45 Java(TM) SE Runtime Environment (build 1.7.0_45-b18) Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode) Reporter: Siegfried Goeschl Fix For: 2.10.1 Attachments: JSPWIKI-823_-_JSPWiki_tests_fail_under_Mac_OS_X_due_to_permissions_for_TMP_directory_-_usi.patch Running the regression tests using mvn clean install fails - somehow no permission to write stuff which affects the following tests * FileSystemProviderTest * WikiEngineTest Any objection to use ./target/tmpdir instead - this would be also deleted using mvn clean? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (JSPWIKI-823) JSPWiki tests fail under Mac OS X due to permissions for TMP directory
[ https://issues.apache.org/jira/browse/JSPWIKI-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925929#comment-13925929 ] Siegfried Goeschl commented on JSPWIKI-823: --- Can someone with the right karma give it a try and commit the changes (assuming that it works)? JSPWiki tests fail under Mac OS X due to permissions for TMP directory -- Key: JSPWIKI-823 URL: https://issues.apache.org/jira/browse/JSPWIKI-823 Project: JSPWiki Issue Type: Bug Components: Build system Affects Versions: 2.10.1 Environment: Mac OS X 10.9.2 java version 1.7.0_45 Java(TM) SE Runtime Environment (build 1.7.0_45-b18) Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode) Reporter: Siegfried Goeschl Fix For: 2.10.1 Attachments: JSPWIKI-823_-_JSPWiki_tests_fail_under_Mac_OS_X_due_to_permissions_for_TMP_directory_-_usi.patch, JSPWIKI-823_JSPWiki_tests_fail_under_Mac_OS_X_due_to_permissions_for_TMP_directory.patch Running the regression tests using mvn clean install fails - somehow no permission to write stuff which affects the following tests * FileSystemProviderTest * WikiEngineTest Any objection to use ./target/tmpdir instead - this would be also deleted using mvn clean? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (JSPWIKI-823) JSPWiki tests fail under Mac OS X due to permissions for TMP directory
[ https://issues.apache.org/jira/browse/JSPWIKI-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925933#comment-13925933 ] Siegfried Goeschl commented on JSPWIKI-823: --- * @Harry - not 100% sure but the tempdir on Mac OS X is only writable by root * a proper Maven build shall not leave any traces after mvn clean :-) JSPWiki tests fail under Mac OS X due to permissions for TMP directory -- Key: JSPWIKI-823 URL: https://issues.apache.org/jira/browse/JSPWIKI-823 Project: JSPWiki Issue Type: Bug Components: Build system Affects Versions: 2.10.1 Environment: Mac OS X 10.9.2 java version 1.7.0_45 Java(TM) SE Runtime Environment (build 1.7.0_45-b18) Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode) Reporter: Siegfried Goeschl Fix For: 2.10.1 Attachments: JSPWIKI-823_-_JSPWiki_tests_fail_under_Mac_OS_X_due_to_permissions_for_TMP_directory_-_usi.patch, JSPWIKI-823_JSPWiki_tests_fail_under_Mac_OS_X_due_to_permissions_for_TMP_directory.patch Running the regression tests using mvn clean install fails - somehow no permission to write stuff which affects the following tests * FileSystemProviderTest * WikiEngineTest Any objection to use ./target/tmpdir instead - this would be also deleted using mvn clean? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (JSPWIKI-825) Integration tests fail on Mac OS X due to IllegalAccessException for stop method in class org.apache.tomcat.maven.plugin.tomcat7.run.ExtendedTomcat
Siegfried Goeschl created JSPWIKI-825:
-
Summary: Integration tests fail on Mac OS X due to
IllegalAccessException for stop method in class
org.apache.tomcat.maven.plugin.tomcat7.run.ExtendedTomcat
Key: JSPWIKI-825
URL: https://issues.apache.org/jira/browse/JSPWIKI-825
Project: JSPWiki
Issue Type: Bug
Components: Integration Testing
Affects Versions: 2.10.1
Environment: Mac OS X 10.9.2
java -version
java version 1.7.0_45
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
Reporter: Siegfried Goeschl
Fix For: 2.10.1
Started the integration tests and got a failure indicating some problem with
the tests setup - is there something I have to do/prepare in oder to run the
integration tests?
{noformat)
jspwiki-it-tests mvn clean install -Pintegration-tests
...
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] jspwiki-it-builder SUCCESS [1.800s]
[INFO] jspwiki-selenium-tests SUCCESS [2.756s]
[INFO] jspwiki-it-test-custom FAILURE [43.273s]
[INFO] jspwiki-it-test-custom-absolute-urls .. SKIPPED
[INFO] jspwiki-it-test-custom-jdbc ... SKIPPED
[INFO] jspwiki-it-test-cma ... SKIPPED
[INFO] jspwiki-it-test-cma-jdbc .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 48.095s
[INFO] Finished at: Mon Mar 10 18:50:57 CET 2014
[INFO] Final Memory: 51M/329M
[INFO]
[ERROR] Failed to execute goal
org.codehaus.mojo:selenium-maven-plugin:2.3:selenese (test) on project
jspwiki-it-test-custom: Tests failed, see result file for details:
/Users/sgoeschl/work/github/apache-jspwiki/jspwiki-it-tests/jspwiki-it-test-custom/target/results-googlechrome-TestSuite.html
- [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn goals -rf :jspwiki-it-test-custom
ERROR: IllegalAccessException for stop method in class
org.apache.tomcat.maven.plugin.tomcat7.run.ExtendedTomcat
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.tomcat.maven.common.run.EmbeddedRegistry.shutdownAll(EmbeddedRegistry.java:110)
at
org.apache.tomcat.maven.common.run.EmbeddedRegistry$1.run(EmbeddedRegistry.java:69)
Caused by: org.apache.catalina.LifecycleException: Failed to stop component
[StandardServer[-1]]
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
at org.apache.catalina.startup.Tomcat.stop(Tomcat.java:345)
... 6 more
Caused by: org.apache.catalina.LifecycleException: Failed to stop component
[StandardService[Tomcat]]
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
at
org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:753)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
... 7 more
Caused by: org.apache.catalina.LifecycleException: Failed to stop component
[StandardEngine[Tomcat]]
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
at
org.apache.catalina.core.StandardService.stopInternal(StandardService.java:502)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
... 9 more
Caused by: java.lang.NoClassDefFoundError:
org/apache/catalina/core/ContainerBase$StopChild
at
org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:1173)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
... 11 more
Caused by: java.lang.ClassNotFoundException:
org.apache.catalina.core.ContainerBase$StopChild
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
[jira] [Created] (JSPWIKI-826) PropertyReader ignores the web app class loader
Siegfried Goeschl created JSPWIKI-826: - Summary: PropertyReader ignores the web app class loader Key: JSPWIKI-826 URL: https://issues.apache.org/jira/browse/JSPWIKI-826 Project: JSPWiki Issue Type: Bug Components: Core storage Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Fix For: 2.10.1 For the Portable JSPWiki I'm deploying the JSPWiki stuff to the Tomcat library folder and run the wikis as sort of skinny wars pulling all libraries from Tomcat. The problem here is that any class path loading needs to look at the web app class loader before looking at the current class loader which is shared through all my wiki instances. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (JSPWIKI-823) JSPWiki tests fail under Mac OS X due to permissions for TMP directory
[ https://issues.apache.org/jira/browse/JSPWIKI-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13926070#comment-13926070 ] Siegfried Goeschl commented on JSPWIKI-823: --- @Craig - never trust a developer (as our QA stuff is saying) JSPWiki tests fail under Mac OS X due to permissions for TMP directory -- Key: JSPWIKI-823 URL: https://issues.apache.org/jira/browse/JSPWIKI-823 Project: JSPWiki Issue Type: Bug Components: Build system Affects Versions: 2.10.1 Environment: Mac OS X 10.9.2 java version 1.7.0_45 Java(TM) SE Runtime Environment (build 1.7.0_45-b18) Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode) Reporter: Siegfried Goeschl Fix For: 2.10.1 Attachments: JSPWIKI-823_-_JSPWiki_tests_fail_under_Mac_OS_X_due_to_permissions_for_TMP_directory_-_usi.patch, JSPWIKI-823_JSPWiki_tests_fail_under_Mac_OS_X_due_to_permissions_for_TMP_directory.patch Running the regression tests using mvn clean install fails - somehow no permission to write stuff which affects the following tests * FileSystemProviderTest * WikiEngineTest Any objection to use ./target/tmpdir instead - this would be also deleted using mvn clean? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (JSPWIKI-827) Migrate the mvn_cheatsheet.txt to Markdown
Siegfried Goeschl created JSPWIKI-827: - Summary: Migrate the mvn_cheatsheet.txt to Markdown Key: JSPWIKI-827 URL: https://issues.apache.org/jira/browse/JSPWIKI-827 Project: JSPWiki Issue Type: Task Components: Documentation website Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Priority: Minor Fix For: 2.10.1 Markdown allows automatic lay-outing when opening with a Markdown Viewer :-) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (JSPWIKI-827) Migrate the mvn_cheatsheet.txt to Markdown
[ https://issues.apache.org/jira/browse/JSPWIKI-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siegfried Goeschl updated JSPWIKI-827: -- Attachment: mvn_cheat-sheet.md The mvn_cheat-sheet as Markdown document (actually Multi-Markdown) Migrate the mvn_cheatsheet.txt to Markdown -- Key: JSPWIKI-827 URL: https://issues.apache.org/jira/browse/JSPWIKI-827 Project: JSPWiki Issue Type: Task Components: Documentation website Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Priority: Minor Fix For: 2.10.1 Attachments: mvn_cheat-sheet.md Markdown allows automatic lay-outing when opening with a Markdown Viewer :-) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (JSPWIKI-826) PropertyReader ignores the web app class loader
[ https://issues.apache.org/jira/browse/JSPWIKI-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siegfried Goeschl updated JSPWIKI-826: -- Attachment: (was: JSPWIKI-826_PropertyReader_ignores_the_web_app_class_loader.patch) PropertyReader ignores the web app class loader --- Key: JSPWIKI-826 URL: https://issues.apache.org/jira/browse/JSPWIKI-826 Project: JSPWiki Issue Type: Bug Components: Core storage Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Fix For: 2.10.1 Attachments: JSPWIKI-826_PropertyReader_ignores_the_web_app_class_loader.patch For the Portable JSPWiki I'm deploying the JSPWiki stuff to the Tomcat library folder and run the wikis as sort of skinny wars pulling all libraries from Tomcat. The problem here is that any class path loading needs to look at the web app class loader before looking at the current class loader which is shared through all my wiki instances. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (JSPWIKI-824) Add English Wiki Pages when executing mvn tomcat7:run-war
[ https://issues.apache.org/jira/browse/JSPWIKI-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siegfried Goeschl updated JSPWIKI-824: -- Attachment: JSPWIKI-824_Add_English_Wiki_Pages_when_executing__mvn_tomcat7_run-war_.patch Add English Wiki Pages when executing mvn tomcat7:run-war --- Key: JSPWIKI-824 URL: https://issues.apache.org/jira/browse/JSPWIKI-824 Project: JSPWiki Issue Type: Improvement Components: Build system Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Priority: Minor Fix For: 2.10.1 Attachments: JSPWIKI-824_Add_English_Wiki_Pages_when_executing__mvn_tomcat7_run-war_.patch Executing the command mvn tomcat7:run-war allows to run a Tomcat loaded with JSPWiki but there is no wiki content available - I think the Maven build should simply deploy the current pages -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (JSPWIKI-824) Add English Wiki Pages when executing mvn tomcat7:run-war
[ https://issues.apache.org/jira/browse/JSPWIKI-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siegfried Goeschl updated JSPWIKI-824: -- Attachment: (was: JSPWIKI-824_-_Add_English_Wiki_Pages_when_executing__mvn_tomcat7_run-war_.patch) Add English Wiki Pages when executing mvn tomcat7:run-war --- Key: JSPWIKI-824 URL: https://issues.apache.org/jira/browse/JSPWIKI-824 Project: JSPWiki Issue Type: Improvement Components: Build system Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Priority: Minor Fix For: 2.10.1 Attachments: JSPWIKI-824_Add_English_Wiki_Pages_when_executing__mvn_tomcat7_run-war_.patch Executing the command mvn tomcat7:run-war allows to run a Tomcat loaded with JSPWiki but there is no wiki content available - I think the Maven build should simply deploy the current pages -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (JSPWIKI-824) Add English Wiki Pages when executing mvn tomcat7:run-war
[ https://issues.apache.org/jira/browse/JSPWIKI-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13926341#comment-13926341 ] Siegfried Goeschl commented on JSPWIKI-824: --- I'm injecting the jspwiki-custom.properties as /WEB-INF/classes/jspwiki-custom.properties but exclude it from the generated WAR file Add English Wiki Pages when executing mvn tomcat7:run-war --- Key: JSPWIKI-824 URL: https://issues.apache.org/jira/browse/JSPWIKI-824 Project: JSPWiki Issue Type: Improvement Components: Build system Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Priority: Minor Fix For: 2.10.1 Attachments: JSPWIKI-824_Add_English_Wiki_Pages_when_executing__mvn_tomcat7_run-war_.patch Executing the command mvn tomcat7:run-war allows to run a Tomcat loaded with JSPWiki but there is no wiki content available - I think the Maven build should simply deploy the current pages -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (JSPWIKI-824) Add English Wiki Pages when executing mvn tomcat7:run-war
[ https://issues.apache.org/jira/browse/JSPWIKI-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919541#comment-13919541 ] Siegfried Goeschl commented on JSPWIKI-824: --- Added patch to do this with the Maven build Add English Wiki Pages when executing mvn tomcat7:run-war --- Key: JSPWIKI-824 URL: https://issues.apache.org/jira/browse/JSPWIKI-824 Project: JSPWiki Issue Type: Improvement Components: Build system Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Priority: Minor Fix For: 2.10.1 Attachments: JSPWIKI-824_-_Add_English_Wiki_Pages_when_executing__mvn_tomcat7_run-war_.patch Executing the command mvn tomcat7:run-war allows to run a Tomcat loaded with JSPWiki but there is no wiki content available - I think the Maven build should simply deploy the current pages -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (JSPWIKI-824) Add English Wiki Pages when executing mvn tomcat7:run-war
[ https://issues.apache.org/jira/browse/JSPWIKI-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siegfried Goeschl updated JSPWIKI-824: -- Attachment: JSPWIKI-824_-_Add_English_Wiki_Pages_when_executing__mvn_tomcat7_run-war_.patch Add English Wiki Pages when executing mvn tomcat7:run-war --- Key: JSPWIKI-824 URL: https://issues.apache.org/jira/browse/JSPWIKI-824 Project: JSPWiki Issue Type: Improvement Components: Build system Affects Versions: 2.10.1 Reporter: Siegfried Goeschl Priority: Minor Fix For: 2.10.1 Attachments: JSPWIKI-824_-_Add_English_Wiki_Pages_when_executing__mvn_tomcat7_run-war_.patch Executing the command mvn tomcat7:run-war allows to run a Tomcat loaded with JSPWiki but there is no wiki content available - I think the Maven build should simply deploy the current pages -- This message was sent by Atlassian JIRA (v6.2#6252)
