[jira] [Commented] (MDEPLOY-289) No "Content-Type" header in PUT requests when deploying.

[ https://issues.apache.org/jira/browse/MDEPLOY-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17453522#comment-17453522 ] Julian Reschke commented on MDEPLOY-289: Well, you should set Content-Type if you know it. Is

[jira] [Commented] (MDEPLOY-289) No "Content-Type" header in PUT requests when deploying.

[ https://issues.apache.org/jira/browse/MDEPLOY-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17453469#comment-17453469 ] Julian Reschke commented on MDEPLOY-289: And the question is? > No "Content-Type" header in PUT

[jira] [Comment Edited] (MJAVADOC-539) Upgrading plugin from 3.0.0 to 3.0.1 and 3.1.0 breaks certain external javadoc links

[ https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814720#comment-16814720 ] Julian Reschke edited comment on MJAVADOC-539 at 4/29/19 1:02 PM: -- I

[jira] [Updated] (MJAVADOC-539) Upgrading plugin from 3.0.0 to 3.0.1 and 3.1.0 breaks certain external javadoc links

[ https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated MJAVADOC-539: Attachment: MAJAVADOC-539.patch > Upgrading plugin from 3.0.0 to 3.0.1 and 3.1.0 breaks

[jira] [Commented] (MJAVADOC-539) Upgrading plugin from 3.0.0 to 3.0.1 and 3.1.0 breaks certain external javadoc links

[ https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827012#comment-16827012 ] Julian Reschke commented on MJAVADOC-539: - [^MAJAVADOC-539.patch] - very simple patch that

[jira] [Commented] (MJAVADOC-539) Upgrading plugin from 3.0.0 to 3.0.1 and 3.1.0 breaks certain external javadoc links

[ https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814720#comment-16814720 ] Julian Reschke commented on MJAVADOC-539: - I agree that the server acts strange (and I tried to

[jira] [Commented] (MJAVADOC-539) Upgrading plugin from 3.0.0 to 3.0.1 and 3.1.0 breaks certain external javadoc links

[ https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814157#comment-16814157 ] Julian Reschke commented on MJAVADOC-539: - Attaching

[jira] [Updated] (MJAVADOC-539) Upgrading plugin from 3.0.0 to 3.0.1 and 3.1.0 breaks certain external javadoc links

[ https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated MJAVADOC-539: Attachment: minimal.zip > Upgrading plugin from 3.0.0 to 3.0.1 and 3.1.0 breaks certain

[jira] [Comment Edited] (MJAVADOC-539) Upgrading plugin from 3.0.0 to 3.0.1 breaks certain external javadoc links

[ https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16813309#comment-16813309 ] Julian Reschke edited comment on MJAVADOC-539 at 4/9/19 12:08 PM: --

[jira] [Commented] (MJAVADOC-539) Upgrading plugin from 3.0.0 to 3.0.1 breaks certain external javadoc links

[ https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16813309#comment-16813309 ] Julian Reschke commented on MJAVADOC-539: - We still see the same issue with 3.1.0. > Upgrading

[jira] [Updated] (MJAVADOC-539) Upgrading plugin from 3.0.0 to 3.0.1 breaks certain external javadoc links

[ https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated MJAVADOC-539: Priority: Major (was: Minor) > Upgrading plugin from 3.0.0 to 3.0.1 breaks certain

[jira] [Commented] (MJAVADOC-539) Upgrading plugin from 3.0.0 to 3.0.1 breaks certain external javadoc links

[ https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16654955#comment-16654955 ] Julian Reschke commented on MJAVADOC-539: - Possible solutions:   * only use the redirect if

[jira] [Updated] (MJAVADOC-539) Upgrading plugin from 3.0.0 to 3.0.1 breaks certain external javadoc links

[ https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated MJAVADOC-539: Affects Version/s: 3.0.1 > Upgrading plugin from 3.0.0 to 3.0.1 breaks certain external

[jira] [Created] (MJAVADOC-539) Upgrading plugin from 3.0.0 to 3.0.1 breaks certain external javadoc links

Julian Reschke created MJAVADOC-539: --- Summary: Upgrading plugin from 3.0.0 to 3.0.1 breaks certain external javadoc links Key: MJAVADOC-539 URL: https://issues.apache.org/jira/browse/MJAVADOC-539

[jira] [Commented] (SUREFIRE-1512) ProcessInfo for Windows is prone to timezone offset changes

[ https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434914#comment-16434914 ] Julian Reschke commented on SUREFIRE-1512: -- Thanks, [~tibor17]. It would be great to have that

[jira] [Commented] (SUREFIRE-1512) ProcessInfo for Windows is prone to timezone offset changes

[ https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432164#comment-16432164 ] Julian Reschke commented on SUREFIRE-1512: -- [~tibor17] - right now it does. I have confirmed

[jira] [Commented] (SUREFIRE-1512) ProcessInfo for Windows is prone to timezone offset changes

[ https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432069#comment-16432069 ] Julian Reschke commented on SUREFIRE-1512: -- [~tibor17] - works for me. Any chance this could

[jira] [Commented] (SUREFIRE-1512) ProcessInfo for Windows is prone to timezone offset changes

[ https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429672#comment-16429672 ] Julian Reschke commented on SUREFIRE-1512: -- Sound like a good approach. Let me know if you

[jira] [Commented] (SUREFIRE-1512) ProcessInfo for Windows is prone to timezone offset changes

[ https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429304#comment-16429304 ] Julian Reschke commented on SUREFIRE-1512: -- [~tibor17] - the problem doesn't happen at the

[jira] [Commented] (WAGON-516) Upgrade Jackrabbit WebDAV to 2.16.1

[ https://issues.apache.org/jira/browse/WAGON-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428590#comment-16428590 ] Julian Reschke commented on WAGON-516: -- 2.16 should work for Java 9 as well. > Upgrade Jackrabbit

[jira] [Commented] (SUREFIRE-1444) /usr/bin/ps and /bin/ps not found. Forked JVM fails.

[ https://issues.apache.org/jira/browse/SUREFIRE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428342#comment-16428342 ] Julian Reschke commented on SUREFIRE-1444: -- Opened improvement request:

[jira] [Created] (SUREFIRE-1512) ProcessInfo for Windows should parse time stamp

Julian Reschke created SUREFIRE-1512: Summary: ProcessInfo for Windows should parse time stamp Key: SUREFIRE-1512 URL: https://issues.apache.org/jira/browse/SUREFIRE-1512 Project: Maven Surefire

[jira] [Commented] (WAGON-516) Upgrade Jackrabbit WebDAV to 2.17.1

[ https://issues.apache.org/jira/browse/WAGON-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428324#comment-16428324 ] Julian Reschke commented on WAGON-516: -- FWIW, you shouldn't use unstable Jackrabbit releases unless

[jira] [Commented] (SUREFIRE-1444) /usr/bin/ps and /bin/ps not found. Forked JVM fails.

[ https://issues.apache.org/jira/browse/SUREFIRE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428307#comment-16428307 ] Julian Reschke commented on SUREFIRE-1444: -- Setting the system time to UTC and disabling DST

[jira] [Comment Edited] (SUREFIRE-1444) /usr/bin/ps and /bin/ps not found. Forked JVM fails.

[ https://issues.apache.org/jira/browse/SUREFIRE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428263#comment-16428263 ] Julian Reschke edited comment on SUREFIRE-1444 at 4/6/18 12:57 PM: ---

[jira] [Commented] (SUREFIRE-1444) /usr/bin/ps and /bin/ps not found. Forked JVM fails.

[ https://issues.apache.org/jira/browse/SUREFIRE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428263#comment-16428263 ] Julian Reschke commented on SUREFIRE-1444: -- Further investigation shows that after rebooting

[jira] [Comment Edited] (SUREFIRE-1444) /usr/bin/ps and /bin/ps not found. Forked JVM fails.

[ https://issues.apache.org/jira/browse/SUREFIRE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428233#comment-16428233 ] Julian Reschke edited comment on SUREFIRE-1444 at 4/6/18 12:23 PM: --- I

[jira] [Commented] (SUREFIRE-1444) /usr/bin/ps and /bin/ps not found. Forked JVM fails.

[ https://issues.apache.org/jira/browse/SUREFIRE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428233#comment-16428233 ] Julian Reschke commented on SUREFIRE-1444: -- I have the same problem on Window (non-docker),

[jira] [Commented] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9

[ https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248469#comment-16248469 ] Julian Reschke commented on SUREFIRE-1424: -- [~rfscholte] - as a workaround, yes. But this

[jira] [Commented] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9

[ https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213718#comment-16213718 ] Julian Reschke commented on SUREFIRE-1424: -- > IIYUC you say that you added

[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9

[ https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213718#comment-16213718 ] Julian Reschke edited comment on SUREFIRE-1424 at 10/21/17 4:00 AM:

[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9

[ https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213145#comment-16213145 ] Julian Reschke edited comment on SUREFIRE-1424 at 10/20/17 8:04 PM:

[jira] [Commented] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9

[ https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213145#comment-16213145 ] Julian Reschke commented on SUREFIRE-1424: -- [~tibor17] - the problem is the default of adding

[jira] [Commented] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9

[ https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16211054#comment-16211054 ] Julian Reschke commented on SUREFIRE-1424: -- FWIW, I've for now worked around the issue by

[jira] [Commented] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9

[ https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210879#comment-16210879 ] Julian Reschke commented on SUREFIRE-1424: -- I think the magic to include --add-modules was

[jira] [Commented] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9

[ https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210827#comment-16210827 ] Julian Reschke commented on SUREFIRE-1424: -- Note there's a similar problem with