[jira] [Commented] (JCR-4183) Jackrabbit standalone jar isn't working under Windows 10 and JDK 8

2017-09-18 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/JCR-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171127#comment-16171127
 ] 

Julian Reschke commented on JCR-4183:
-

[~peteryuan] - sorry for not being clear: "build", not "release". There's no 
release yet; you'd need to check out the source and build yourself.

> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> --
>
> Key: JCR-4183
> URL: https://issues.apache.org/jira/browse/JCR-4183
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-standalone
>Affects Versions: 2.14.3, 2.15.6
> Environment: Microsoft Windows 10, build 15063
> Oracle JSSE  1.8.0_141, build 1.8.0_141-b15
>Reporter: Peter Yuan
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_8
> Fix For: 2.16
>
> Attachments: 2017-09-14 17_05_40-Settings.png, 2017-09-18 
> 20_37_20-Photos.png
>
>
> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> Just download Jackrabbit standalone jar file and execute command(_java -jar 
> jackrabbit-standalone-2.14.3.jar_) in Windows CMD, I get the following error 
> in Jetty log:
> Then I modify statndalone jar file name from 
> "jackrabbit-standalone-2.14.3.jar" to "jackrabbit-standalone.jar", execute 
> command(_java -jar jackrabbit-standalone.jar_), I get the following error(see 
> attached screenshot) on browser.
>  
> _2017-09-14 16:09:19.746 INFO  [main] Slf4jLog.java:67  
> jetty-6.1.x
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:76  Web 
> application not found jackrabbit-standalone.jar
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:89  Failed 
> startup of context 
> org.mortbay.jetty.webapp.WebAppContext@2ef9b8bc{/,jackrabbit-standalone.jar}
> java.io.FileNotFoundException: jackrabbit-standalone.jar
>   at 
> org.mortbay.jetty.webapp.WebAppContext.resolveWebApp(WebAppContext.java:997) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.getWebInf(WebAppContext.java:832) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebInfConfiguration.configureClassLoader(WebInfConfiguration.java:62)
>  ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:489) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.RequestLogHandler.doStart(RequestLogHandler.java:115)
>  [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.mortbay.jetty.Server.doStart(Server.java:224) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.run(Main.java:173) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.main(Main.java:60) 
> [jackrabbit-standalone-2.14.3.jar:na]_



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4183) Jackrabbit standalone jar isn't working under Windows 10 and JDK 8

2017-09-18 Thread Peter Yuan (JIRA) 

 [ 
https://issues.apache.org/jira/browse/JCR-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Yuan updated JCR-4183:

Attachment: 2017-09-18 20_37_20-Photos.png

Hi, [~julian.resc...@gmx.de]: I also try "jackrabbit-standalone-2.15.6.jar", 
it's not working, I get the same issue, the details see attached screenshot.

> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> --
>
> Key: JCR-4183
> URL: https://issues.apache.org/jira/browse/JCR-4183
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-standalone
>Affects Versions: 2.14.3, 2.15.6
> Environment: Microsoft Windows 10, build 15063
> Oracle JSSE  1.8.0_141, build 1.8.0_141-b15
>Reporter: Peter Yuan
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_8
> Fix For: 2.16
>
> Attachments: 2017-09-14 17_05_40-Settings.png, 2017-09-18 
> 20_37_20-Photos.png
>
>
> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> Just download Jackrabbit standalone jar file and execute command(_java -jar 
> jackrabbit-standalone-2.14.3.jar_) in Windows CMD, I get the following error 
> in Jetty log:
> Then I modify statndalone jar file name from 
> "jackrabbit-standalone-2.14.3.jar" to "jackrabbit-standalone.jar", execute 
> command(_java -jar jackrabbit-standalone.jar_), I get the following error(see 
> attached screenshot) on browser.
>  
> _2017-09-14 16:09:19.746 INFO  [main] Slf4jLog.java:67  
> jetty-6.1.x
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:76  Web 
> application not found jackrabbit-standalone.jar
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:89  Failed 
> startup of context 
> org.mortbay.jetty.webapp.WebAppContext@2ef9b8bc{/,jackrabbit-standalone.jar}
> java.io.FileNotFoundException: jackrabbit-standalone.jar
>   at 
> org.mortbay.jetty.webapp.WebAppContext.resolveWebApp(WebAppContext.java:997) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.getWebInf(WebAppContext.java:832) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebInfConfiguration.configureClassLoader(WebInfConfiguration.java:62)
>  ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:489) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.RequestLogHandler.doStart(RequestLogHandler.java:115)
>  [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.mortbay.jetty.Server.doStart(Server.java:224) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.run(Main.java:173) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.main(Main.java:60) 
> [jackrabbit-standalone-2.14.3.jar:na]_



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JCR-4183) Jackrabbit standalone jar isn't working under Windows 10 and JDK 8

2017-09-18 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/JCR-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170447#comment-16170447
 ] 

Julian Reschke commented on JCR-4183:
-

[~peteryuan] - can you check whether a recent build of jackrabbit trunk works 
for you?

> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> --
>
> Key: JCR-4183
> URL: https://issues.apache.org/jira/browse/JCR-4183
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-standalone
>Affects Versions: 2.14.3, 2.15.6
> Environment: Microsoft Windows 10, build 15063
> Oracle JSSE  1.8.0_141, build 1.8.0_141-b15
>Reporter: Peter Yuan
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_8
> Fix For: 2.16
>
> Attachments: 2017-09-14 17_05_40-Settings.png
>
>
> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> Just download Jackrabbit standalone jar file and execute command(_java -jar 
> jackrabbit-standalone-2.14.3.jar_) in Windows CMD, I get the following error 
> in Jetty log:
> Then I modify statndalone jar file name from 
> "jackrabbit-standalone-2.14.3.jar" to "jackrabbit-standalone.jar", execute 
> command(_java -jar jackrabbit-standalone.jar_), I get the following error(see 
> attached screenshot) on browser.
>  
> _2017-09-14 16:09:19.746 INFO  [main] Slf4jLog.java:67  
> jetty-6.1.x
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:76  Web 
> application not found jackrabbit-standalone.jar
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:89  Failed 
> startup of context 
> org.mortbay.jetty.webapp.WebAppContext@2ef9b8bc{/,jackrabbit-standalone.jar}
> java.io.FileNotFoundException: jackrabbit-standalone.jar
>   at 
> org.mortbay.jetty.webapp.WebAppContext.resolveWebApp(WebAppContext.java:997) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.getWebInf(WebAppContext.java:832) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebInfConfiguration.configureClassLoader(WebInfConfiguration.java:62)
>  ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:489) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.RequestLogHandler.doStart(RequestLogHandler.java:115)
>  [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.mortbay.jetty.Server.doStart(Server.java:224) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.run(Main.java:173) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.main(Main.java:60) 
> [jackrabbit-standalone-2.14.3.jar:na]_



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (JCR-4184) migrate from org.mortbay.jetty to org.eclipse.jetty

2017-09-18 Thread Julian Reschke (JIRA) 

 [ 
https://issues.apache.org/jira/browse/JCR-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke resolved JCR-4184.
-
   Resolution: Fixed
Fix Version/s: 2.15.7

> migrate from org.mortbay.jetty to org.eclipse.jetty
> ---
>
> Key: JCR-4184
> URL: https://issues.apache.org/jira/browse/JCR-4184
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-jcr-server, jackrabbit-jcr2dav, 
> jackrabbit-parent, jackrabbit-standalone, jackrabbit-webdav
>Affects Versions: 2.15.6
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.15.7
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JCR-4184) migrate from org.mortbay.jetty to org.eclipse.jetty

2017-09-18 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/JCR-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170446#comment-16170446
 ] 

Julian Reschke commented on JCR-4184:
-

trunk: [r1808754|http://svn.apache.org/r1808754]


> migrate from org.mortbay.jetty to org.eclipse.jetty
> ---
>
> Key: JCR-4184
> URL: https://issues.apache.org/jira/browse/JCR-4184
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-jcr-server, jackrabbit-jcr2dav, 
> jackrabbit-parent, jackrabbit-standalone, jackrabbit-webdav
>Affects Versions: 2.15.6
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.15.7
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Jackrabbit-trunk - Build # 2516 - Failure

2017-09-18 Thread Apache Jenkins Server 
The Apache Jenkins build system has built Jackrabbit-trunk (build #2516)

Status: Failure

Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2516/ to 
view the results.

[jira] [Commented] (JCR-4185) spi2dav URIResolverImpl should check status code before attempting to parse multistatus

2017-09-18 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/JCR-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170362#comment-16170362
 ] 

Julian Reschke commented on JCR-4185:
-

spi2dav URIResolverImpl should check status code before attempting to parse 
multistatus

> spi2dav URIResolverImpl should check status code before attempting to parse 
> multistatus
> ---
>
> Key: JCR-4185
> URL: https://issues.apache.org/jira/browse/JCR-4185
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-spi2dav
>Affects Versions: 2.15.6
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.15.7
>
>
> The server might be returning 404 + HTML and this needs to be handled 
> properly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (JCR-4185) spi2dav URIResolverImpl should check status code before attempting to parse multistatus

2017-09-18 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/JCR-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170362#comment-16170362
 ] 

Julian Reschke edited comment on JCR-4185 at 9/18/17 5:31 PM:
--

trunk: [r1808752|http://svn.apache.org/r1808752]



was (Author: reschke):
spi2dav URIResolverImpl should check status code before attempting to parse 
multistatus

> spi2dav URIResolverImpl should check status code before attempting to parse 
> multistatus
> ---
>
> Key: JCR-4185
> URL: https://issues.apache.org/jira/browse/JCR-4185
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-spi2dav
>Affects Versions: 2.15.6
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.15.7
>
>
> The server might be returning 404 + HTML and this needs to be handled 
> properly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (JCR-4185) spi2dav URIResolverImpl should check status code before attempting to parse multistatus

2017-09-18 Thread Julian Reschke (JIRA) 

 [ 
https://issues.apache.org/jira/browse/JCR-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke resolved JCR-4185.
-
   Resolution: Fixed
Fix Version/s: 2.15.7

> spi2dav URIResolverImpl should check status code before attempting to parse 
> multistatus
> ---
>
> Key: JCR-4185
> URL: https://issues.apache.org/jira/browse/JCR-4185
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-spi2dav
>Affects Versions: 2.15.6
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.15.7
>
>
> The server might be returning 404 + HTML and this needs to be handled 
> properly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4185) spi2dav URIResolverImpl should check status code before attempting to parse multistatus

2017-09-18 Thread Julian Reschke (JIRA) 

 [ 
https://issues.apache.org/jira/browse/JCR-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated JCR-4185:

Labels: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_14 
candidate_jcr_2_6 candidate_jcr_2_8  (was: )

> spi2dav URIResolverImpl should check status code before attempting to parse 
> multistatus
> ---
>
> Key: JCR-4185
> URL: https://issues.apache.org/jira/browse/JCR-4185
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-spi2dav
>Affects Versions: 2.15.6
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16
>
>
> The server might be returning 404 + HTML and this needs to be handled 
> properly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (JCR-4185) spi2dav URIResolverImpl should check status code before attempting to parse multistatus

2017-09-18 Thread Julian Reschke (JIRA) 
Julian Reschke created JCR-4185:
---

 Summary: spi2dav URIResolverImpl should check status code before 
attempting to parse multistatus
 Key: JCR-4185
 URL: https://issues.apache.org/jira/browse/JCR-4185
 Project: Jackrabbit Content Repository
  Issue Type: Bug
  Components: jackrabbit-spi2dav
Affects Versions: 2.15.6
Reporter: Julian Reschke
Assignee: Julian Reschke
Priority: Minor
 Fix For: 2.16


The server might be returning 404 + HTML and this needs to be handled properly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4184) migrate from org.mortbay.jetty to org.eclipse.jetty

2017-09-18 Thread Julian Reschke (JIRA) 

 [ 
https://issues.apache.org/jira/browse/JCR-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated JCR-4184:

Labels: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_14 
candidate_jcr_2_6 candidate_jcr_2_8  (was: )

> migrate from org.mortbay.jetty to org.eclipse.jetty
> ---
>
> Key: JCR-4184
> URL: https://issues.apache.org/jira/browse/JCR-4184
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-jcr-server, jackrabbit-jcr2dav, 
> jackrabbit-parent, jackrabbit-standalone, jackrabbit-webdav
>Affects Versions: 2.15.6
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (JCR-4184) migrate from org.mortbay.jetty to org.eclipse.jetty

2017-09-18 Thread Julian Reschke (JIRA) 
Julian Reschke created JCR-4184:
---

 Summary: migrate from org.mortbay.jetty to org.eclipse.jetty
 Key: JCR-4184
 URL: https://issues.apache.org/jira/browse/JCR-4184
 Project: Jackrabbit Content Repository
  Issue Type: Task
  Components: jackrabbit-jcr2dav, jackrabbit-jcr-server, 
jackrabbit-parent, jackrabbit-standalone, jackrabbit-webdav
Affects Versions: 2.15.6
Reporter: Julian Reschke
Assignee: Julian Reschke
Priority: Minor
 Fix For: 2.16






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: OAK-6575 - A word of caution

2017-09-18 Thread Davide Giannella 
On 18/09/2017 12:40, Ian Boston wrote:
> can be evaluated
> as part of the release process, ideally before the next stable release.

I mostly do releases here, let me drop a consideration. Our release
process is already long. Let's not add too much stuff even more,
specially if we have to do it at every release. Otherwise I don't think
we'll be able to cope with the bi-weekly release.

So let's be considerate about what adding to the release process.

A word of caution ;)

Cheers
Davide

[jira] [Commented] (JCR-4183) Jackrabbit standalone jar isn't working under Windows 10 and JDK 8

2017-09-18 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/JCR-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169944#comment-16169944
 ] 

Julian Reschke commented on JCR-4183:
-

apparently caused by using a version of Jetty which does not support Java 8 
properly

> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> --
>
> Key: JCR-4183
> URL: https://issues.apache.org/jira/browse/JCR-4183
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-standalone
>Affects Versions: 2.14.3, 2.15.6
> Environment: Microsoft Windows 10, build 15063
> Oracle JSSE  1.8.0_141, build 1.8.0_141-b15
>Reporter: Peter Yuan
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_8
> Fix For: 2.16
>
> Attachments: 2017-09-14 17_05_40-Settings.png
>
>
> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> Just download Jackrabbit standalone jar file and execute command(_java -jar 
> jackrabbit-standalone-2.14.3.jar_) in Windows CMD, I get the following error 
> in Jetty log:
> Then I modify statndalone jar file name from 
> "jackrabbit-standalone-2.14.3.jar" to "jackrabbit-standalone.jar", execute 
> command(_java -jar jackrabbit-standalone.jar_), I get the following error(see 
> attached screenshot) on browser.
>  
> _2017-09-14 16:09:19.746 INFO  [main] Slf4jLog.java:67  
> jetty-6.1.x
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:76  Web 
> application not found jackrabbit-standalone.jar
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:89  Failed 
> startup of context 
> org.mortbay.jetty.webapp.WebAppContext@2ef9b8bc{/,jackrabbit-standalone.jar}
> java.io.FileNotFoundException: jackrabbit-standalone.jar
>   at 
> org.mortbay.jetty.webapp.WebAppContext.resolveWebApp(WebAppContext.java:997) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.getWebInf(WebAppContext.java:832) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebInfConfiguration.configureClassLoader(WebInfConfiguration.java:62)
>  ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:489) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.RequestLogHandler.doStart(RequestLogHandler.java:115)
>  [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.mortbay.jetty.Server.doStart(Server.java:224) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.run(Main.java:173) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.main(Main.java:60) 
> [jackrabbit-standalone-2.14.3.jar:na]_



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: OAK-6575 - A word of caution

2017-09-18 Thread Ian Boston 
Hi Angela,
Thank you for the clarification.

To summarize, I think consensus has been reached.

1. Move forward with the patch in OAK-6575 discussed in this thread.
2. Develop a thread model so that this and future changes can be evaluated
as part of the release process, ideally before the next stable release.

If anyone feels consensus has not been reached, please continue this thread.

Best Regards
Ian

On 15 September 2017 at 07:52, Angela Schreiber 
wrote:

> Hi Ian
>
> On 13/09/17 23:34, "Ian Boston"  wrote:
>
> >Hi Angela,
> >
> >On 13 September 2017 at 06:50, Angela Schreiber
> >
> >wrote:
> >
> >> Hi Ian
> >>
> >> The new proposal looks a lot better to me.
> >>
> >> The only concern from a security perspective I could come up with is the
> >> one we expressed already with the very first proposal (see initial word
> >>of
> >> caution mail sent by Francesco): applications built on top of Oak can up
> >> to now be sure that all access to the repository content is subject to
> >>the
> >> same permission evaluation as configured with the repository setup. This
> >> is no longer guaranteed when we offer the ability to plug application
> >>code
> >> that may or may not by-pass the evaluation by allowing it to directly
> >> access binaries.
> >>
> >
> >I don't think this patch bypasses Oak security, and since the API can only
> >be implemented by Oak itself. I am sure any future patch would be subject
> >to the same scrutiny. If it can be implemented outside Oak, then Oak has
> >already been breached, something I can see no evidence of.
> >
> >In this case, the signed url is only issued after Oak security has granted
> >access to the binary, and only returned over the JCR API to the JCR
> >Session
> >that made the call, in the same way that an InputStream allows the bytes
> >of
> >the binary to be read by that session. The URL only allows read access.
> >
> >What the session does with that data, is outside the control of Oak.
> >Unlike the byte[] from the  that has no protection, the signed URL is
> >protected. It may only be used unmodified for the purpose it was intended
> >by Oak and only for a well defined period of time. In that respect,
> >arguably, its is more secure than the byte[] or InputStream.
>
> I am not worried about the security of the approach and maybe I am even
> mistaken if I think this changes our threat model. But even if it actually
> changes our threat model wouldn't mean that your proposal isn't secure.
> Those are two quite distinct things.
>
> That's why i would love us to finally reserve some time to create a threat
> model. It will help us with this discussion and with similar requests in
> the future. and even the threat model itself can evolve over time... but
> it allows us to review features from a different angle.
>
> >
> >>
> >> While I know that this is actually the goal of the whole exercise, we
> >>have
> >> to be aware that this also is a change in our Oak security model. As
> >>such
> >> this may look like a security breach and I have been told by my
> >>colleagues
> >> at Adobe that the 'single-way-to-access' is a relevant security question
> >> with a lot of potential customers.
> >>
> >> That doesn't mean that I am opposed to the patch in it's current form
> >>as I
> >> see the benefits from an Oak pov, I just want to highlight that we are
> >> going to make a fundamental change and we should treat and document it
> >> with the necessary care... maybe we should take this opportunity to
> >> finally create a threat model for Oak? Doing so at this stage would
> >>allow
> >> us to visualise the proposed change to all parties involved.
> >>
> >> wdyt?
> >>
> >
> >Agreed.
> >Having a fully developed threat model which clarified all the risks for
> >every aspect of Oak would, imho, be much better than not defining the
> >risks
> >that exist. Even the most secure application has risks, best exposed in a
> >threat model, however brief.
> >
> >Unfortunately Oak now exists in a world which is distributed, where
> >applications need to embrace the network. This is a fundamental change,
> >which Oak has to embrace. An Oak Threat model that recognises this will be
> >a great step forwards.
> >
> >On the other hand, if you are saying that the Oak Threat model has to be
> >developed and agreed, before this patch can be added, then I am concerned
> >that will take too long. Doing justice to an Oak Treat model will require
> >resource.
>
> No... that's not what I am saying :-)
> What I would strongly advocate though is that we start working on the
> threat model in parallel and make sure we have it completed before we
> create any stable release (1.8.x, 1.6.x, etc) that includes your patch.
> This will allow the whole Oak team to take a final look at it from a
> design of view. Since this has been subject to a lot of disputes in the
> past and actually got rejected then, I think having a threat model will be
>

[jira] [Commented] (JCRVLT-202) Import Adobe's content package maven plugin

2017-09-18 Thread Robert Munteanu (JIRA) 

[ 
https://issues.apache.org/jira/browse/JCRVLT-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169901#comment-16169901
 ] 

Robert Munteanu commented on JCRVLT-202:


There is already one other package manager, provided by Composum - 
https://ist-software.atlassian.net/wiki/spaces/CMP/pages/46140125/Package+Manager
 . Given that, maybe it would be a good idea to provide some abstract 
install/uninstall/etc goals which require an additional dependency to work 
properly, maven-scr-plugin requires an annotations dependency.

Then this is a good entry point for the future Adobe maven plugin and can be 
reused to work with Composum as well, if the desire comes up.

> Import Adobe's content package maven plugin
> ---
>
> Key: JCRVLT-202
> URL: https://issues.apache.org/jira/browse/JCRVLT-202
> Project: Jackrabbit FileVault
>  Issue Type: Task
>  Components: package maven plugin
>Reporter: Tobias Bocanegra
>Assignee: Tobias Bocanegra
> Fix For: package-maven-plugin-1.0.0
>
>
> The content-package maven plugin is a maven plugin that simplifies the 
> creation of content package maven artifacts. The content packages can later 
> be used to install content into a JCR repository using the Apache Jackrabbit 
> FileVault packaging runtime.
> Filevault was contributed 4 years ago, but we never had a tool to create the 
> packaged during runtime. Adobe's plugin is publicly available, but only in 
> binary form. With this contribution, we want to bring the source and 
> development closer to the filevault core and to leverage the community better 
> in driving this plugin further.
> *details*
> java package space: 
> {code}
> org.apache.jackrabbit.filevault.maven.packaging
> {code}
> plugin name:
> {code}
> org.apache.jackrabbit.filevault
> package-maven-plugin
> {code}
> scm location: 
> - a) SVN: 
> https://svn.apache.org/repos/asf/jackrabbit/commons/package-maven-plugin
> - b) GIT: 
> https://git-wip-us.apache.org/repos/asf?p=jackrabbit-filevault-package-plugin.git;a=tree



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (JCRVLT-203) Invalid links in the package-maven-plugin readme

2017-09-18 Thread Robert Munteanu (JIRA) 
Robert Munteanu created JCRVLT-203:
--

 Summary: Invalid links in the package-maven-plugin readme
 Key: JCRVLT-203
 URL: https://issues.apache.org/jira/browse/JCRVLT-203
 Project: Jackrabbit FileVault
  Issue Type: Bug
  Components: package maven plugin
Reporter: Robert Munteanu


* https://svn.apache.org/repos/asf/commons/filevault/trunk
* https://svn.apache.org/viewvc/commons/filevault/trunk
* https://svn.apache.org/repos/asf/commons/filevault/trunk filevault




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4183) Jackrabbit standalone jar isn't working under Windows 10 and JDK 8

2017-09-18 Thread Julian Reschke (JIRA) 

 [ 
https://issues.apache.org/jira/browse/JCR-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated JCR-4183:

Labels: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_14 
candidate_jcr_2_8  (was: )

> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> --
>
> Key: JCR-4183
> URL: https://issues.apache.org/jira/browse/JCR-4183
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-standalone
>Affects Versions: 2.14.3, 2.15.6
> Environment: Microsoft Windows 10, build 15063
> Oracle JSSE  1.8.0_141, build 1.8.0_141-b15
>Reporter: Peter Yuan
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_8
> Fix For: 2.16
>
> Attachments: 2017-09-14 17_05_40-Settings.png
>
>
> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> Just download Jackrabbit standalone jar file and execute command(_java -jar 
> jackrabbit-standalone-2.14.3.jar_) in Windows CMD, I get the following error 
> in Jetty log:
> Then I modify statndalone jar file name from 
> "jackrabbit-standalone-2.14.3.jar" to "jackrabbit-standalone.jar", execute 
> command(_java -jar jackrabbit-standalone.jar_), I get the following error(see 
> attached screenshot) on browser.
>  
> _2017-09-14 16:09:19.746 INFO  [main] Slf4jLog.java:67  
> jetty-6.1.x
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:76  Web 
> application not found jackrabbit-standalone.jar
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:89  Failed 
> startup of context 
> org.mortbay.jetty.webapp.WebAppContext@2ef9b8bc{/,jackrabbit-standalone.jar}
> java.io.FileNotFoundException: jackrabbit-standalone.jar
>   at 
> org.mortbay.jetty.webapp.WebAppContext.resolveWebApp(WebAppContext.java:997) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.getWebInf(WebAppContext.java:832) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebInfConfiguration.configureClassLoader(WebInfConfiguration.java:62)
>  ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:489) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.RequestLogHandler.doStart(RequestLogHandler.java:115)
>  [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.mortbay.jetty.Server.doStart(Server.java:224) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.run(Main.java:173) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.main(Main.java:60) 
> [jackrabbit-standalone-2.14.3.jar:na]_



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4183) Jackrabbit standalone jar isn't working under Windows 10 and JDK 8

2017-09-18 Thread Julian Reschke (JIRA) 

 [ 
https://issues.apache.org/jira/browse/JCR-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated JCR-4183:

Affects Version/s: 2.15.6

> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> --
>
> Key: JCR-4183
> URL: https://issues.apache.org/jira/browse/JCR-4183
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-standalone
>Affects Versions: 2.14.3, 2.15.6
> Environment: Microsoft Windows 10, build 15063
> Oracle JSSE  1.8.0_141, build 1.8.0_141-b15
>Reporter: Peter Yuan
>Assignee: Julian Reschke
> Fix For: 2.16
>
> Attachments: 2017-09-14 17_05_40-Settings.png
>
>
> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> Just download Jackrabbit standalone jar file and execute command(_java -jar 
> jackrabbit-standalone-2.14.3.jar_) in Windows CMD, I get the following error 
> in Jetty log:
> Then I modify statndalone jar file name from 
> "jackrabbit-standalone-2.14.3.jar" to "jackrabbit-standalone.jar", execute 
> command(_java -jar jackrabbit-standalone.jar_), I get the following error(see 
> attached screenshot) on browser.
>  
> _2017-09-14 16:09:19.746 INFO  [main] Slf4jLog.java:67  
> jetty-6.1.x
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:76  Web 
> application not found jackrabbit-standalone.jar
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:89  Failed 
> startup of context 
> org.mortbay.jetty.webapp.WebAppContext@2ef9b8bc{/,jackrabbit-standalone.jar}
> java.io.FileNotFoundException: jackrabbit-standalone.jar
>   at 
> org.mortbay.jetty.webapp.WebAppContext.resolveWebApp(WebAppContext.java:997) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.getWebInf(WebAppContext.java:832) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebInfConfiguration.configureClassLoader(WebInfConfiguration.java:62)
>  ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:489) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.RequestLogHandler.doStart(RequestLogHandler.java:115)
>  [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.mortbay.jetty.Server.doStart(Server.java:224) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.run(Main.java:173) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.main(Main.java:60) 
> [jackrabbit-standalone-2.14.3.jar:na]_



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JCR-4183) Jackrabbit standalone jar isn't working under Windows 10 and JDK 8

2017-09-18 Thread Julian Reschke (JIRA) 

 [ 
https://issues.apache.org/jira/browse/JCR-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated JCR-4183:

Fix Version/s: 2.16

> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> --
>
> Key: JCR-4183
> URL: https://issues.apache.org/jira/browse/JCR-4183
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-standalone
>Affects Versions: 2.14.3, 2.15.6
> Environment: Microsoft Windows 10, build 15063
> Oracle JSSE  1.8.0_141, build 1.8.0_141-b15
>Reporter: Peter Yuan
>Assignee: Julian Reschke
> Fix For: 2.16
>
> Attachments: 2017-09-14 17_05_40-Settings.png
>
>
> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> Just download Jackrabbit standalone jar file and execute command(_java -jar 
> jackrabbit-standalone-2.14.3.jar_) in Windows CMD, I get the following error 
> in Jetty log:
> Then I modify statndalone jar file name from 
> "jackrabbit-standalone-2.14.3.jar" to "jackrabbit-standalone.jar", execute 
> command(_java -jar jackrabbit-standalone.jar_), I get the following error(see 
> attached screenshot) on browser.
>  
> _2017-09-14 16:09:19.746 INFO  [main] Slf4jLog.java:67  
> jetty-6.1.x
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:76  Web 
> application not found jackrabbit-standalone.jar
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:89  Failed 
> startup of context 
> org.mortbay.jetty.webapp.WebAppContext@2ef9b8bc{/,jackrabbit-standalone.jar}
> java.io.FileNotFoundException: jackrabbit-standalone.jar
>   at 
> org.mortbay.jetty.webapp.WebAppContext.resolveWebApp(WebAppContext.java:997) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.getWebInf(WebAppContext.java:832) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebInfConfiguration.configureClassLoader(WebInfConfiguration.java:62)
>  ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:489) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.RequestLogHandler.doStart(RequestLogHandler.java:115)
>  [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.mortbay.jetty.Server.doStart(Server.java:224) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.run(Main.java:173) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.main(Main.java:60) 
> [jackrabbit-standalone-2.14.3.jar:na]_



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (JCR-4183) Jackrabbit standalone jar isn't working under Windows 10 and JDK 8

2017-09-18 Thread Julian Reschke (JIRA) 

 [ 
https://issues.apache.org/jira/browse/JCR-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke reassigned JCR-4183:
---

Assignee: Julian Reschke

> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> --
>
> Key: JCR-4183
> URL: https://issues.apache.org/jira/browse/JCR-4183
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-standalone
>Affects Versions: 2.14.3
> Environment: Microsoft Windows 10, build 15063
> Oracle JSSE  1.8.0_141, build 1.8.0_141-b15
>Reporter: Peter Yuan
>Assignee: Julian Reschke
> Attachments: 2017-09-14 17_05_40-Settings.png
>
>
> Jackrabbit standalone jar isn't working under Windows 10 and JDK 8
> Just download Jackrabbit standalone jar file and execute command(_java -jar 
> jackrabbit-standalone-2.14.3.jar_) in Windows CMD, I get the following error 
> in Jetty log:
> Then I modify statndalone jar file name from 
> "jackrabbit-standalone-2.14.3.jar" to "jackrabbit-standalone.jar", execute 
> command(_java -jar jackrabbit-standalone.jar_), I get the following error(see 
> attached screenshot) on browser.
>  
> _2017-09-14 16:09:19.746 INFO  [main] Slf4jLog.java:67  
> jetty-6.1.x
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:76  Web 
> application not found jackrabbit-standalone.jar
> 2017-09-14 16:09:19.762 WARN  [main] Slf4jLog.java:89  Failed 
> startup of context 
> org.mortbay.jetty.webapp.WebAppContext@2ef9b8bc{/,jackrabbit-standalone.jar}
> java.io.FileNotFoundException: jackrabbit-standalone.jar
>   at 
> org.mortbay.jetty.webapp.WebAppContext.resolveWebApp(WebAppContext.java:997) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.getWebInf(WebAppContext.java:832) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebInfConfiguration.configureClassLoader(WebInfConfiguration.java:62)
>  ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:489) 
> ~[jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.RequestLogHandler.doStart(RequestLogHandler.java:115)
>  [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.mortbay.jetty.Server.doStart(Server.java:224) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.run(Main.java:173) 
> [jackrabbit-standalone-2.14.3.jar:na]
>   at org.apache.jackrabbit.standalone.Main.main(Main.java:60) 
> [jackrabbit-standalone-2.14.3.jar:na]_



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)