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

2021-12-04 Thread Julian Reschke (Jira) 


[ 
https://issues.apache.org/jira/browse/MDEPLOY-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453522#comment-17453522
 ] 

Julian Reschke commented on MDEPLOY-289:


Well, you should set Content-Type if you know it. Is this the case here?

> No "Content-Type" header in PUT requests when deploying.
> 
>
> Key: MDEPLOY-289
> URL: https://issues.apache.org/jira/browse/MDEPLOY-289
> Project: Maven Deploy Plugin
>  Issue Type: Improvement
>  Components: deploy:deploy
>Affects Versions: 2.8.2
> Environment: Mac/Linux
>Reporter: J.R. Hill
>Priority: Minor
>
> Heya folks!
>  
> I work with Amazon/AWS as a build engineer. I'm researching how much effort 
> it would take to give our developers the option to build with Apache Maven. 
> (opposed to other tools like Gradle)
>  
> Right now we are blocked from an easy usage of Apache Maven because no 
> "Content-Type" header is sent in requests, and it violates some expectations 
> of our proxies. We use clones of maven repositories so we can have some 
> governance controls across our codebase and services.
>  
> We have ways we could work around around it - we could consider loosening our 
> proxies, or adding special handling. We could also build our own plugin that 
> does things the way we want. That said, I'd prefer to use off-the-shelf 
> tools, and to be able to contribute to open source projects where possible.
>  
> I looked a bit into how this plugin is performing deployments. I see it's 
> using Aether for the deploy action, and see what looks like some complicated 
> history there between Sonatype and Eclipse around the Aether project. I'm not 
> sure if this is possible to fix this _in_ the Maven Deploy Plugin or if it'd 
> have to go deeper into the Aether code base.
>  
> Any pointers? I'd love to take a crack at something here.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

2021-12-04 Thread Julian Reschke (Jira) 


[ 
https://issues.apache.org/jira/browse/MDEPLOY-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453469#comment-17453469
 ] 

Julian Reschke commented on MDEPLOY-289:


And the question is?

> No "Content-Type" header in PUT requests when deploying.
> 
>
> Key: MDEPLOY-289
> URL: https://issues.apache.org/jira/browse/MDEPLOY-289
> Project: Maven Deploy Plugin
>  Issue Type: Improvement
>  Components: deploy:deploy
>Affects Versions: 2.8.2
> Environment: Mac/Linux
>Reporter: J.R. Hill
>Priority: Minor
>
> Heya folks!
>  
> I work with Amazon/AWS as a build engineer. I'm researching how much effort 
> it would take to give our developers the option to build with Apache Maven. 
> (opposed to other tools like Gradle)
>  
> Right now we are blocked from an easy usage of Apache Maven because no 
> "Content-Type" header is sent in requests, and it violates some expectations 
> of our proxies. We use clones of maven repositories so we can have some 
> governance controls across our codebase and services.
>  
> We have ways we could work around around it - we could consider loosening our 
> proxies, or adding special handling. We could also build our own plugin that 
> does things the way we want. That said, I'd prefer to use off-the-shelf 
> tools, and to be able to contribute to open source projects where possible.
>  
> I looked a bit into how this plugin is performing deployments. I see it's 
> using Aether for the deploy action, and see what looks like some complicated 
> history there between Sonatype and Eclipse around the Aether project. I'm not 
> sure if this is possible to fix this _in_ the Maven Deploy Plugin or if it'd 
> have to go deeper into the Aether code base.
>  
> Any pointers? I'd love to take a crack at something here.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

2019-04-29 Thread Julian Reschke (JIRA) 


[ 
https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814720#comment-16814720
 ] 

Julian Reschke edited comment on MJAVADOC-539 at 4/29/19 1:02 PM:
--

I agree that the server acts strange (and I tried to get it fixed). But fact 
is, the doctool actually works with that redirect; it's the javadoc maven 
plugin that mangles the URI right now...


was (Author: reschke):
I agree that the server acts strange (and I tried to get it fixed). But fact 
is, the doctool actually works with that redirect; it's the javadoc maven 
plugin that mangles the URI right now,

> Upgrading plugin from 3.0.0 to 3.0.1 and 3.1.0 breaks certain external 
> javadoc links
> 
>
> Key: MJAVADOC-539
> URL: https://issues.apache.org/jira/browse/MJAVADOC-539
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Julian Reschke
>Assignee: Robert Scholte
>Priority: Major
> Attachments: MAJAVADOC-539.patch, minimal.zip
>
>
> See https://issues.apache.org/jira/browse/OAK-7789 - downgrading to 3.0.0 
> fixes the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2019-04-26 Thread Julian Reschke (JIRA) 


 [ 
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 certain external 
> javadoc links
> 
>
> Key: MJAVADOC-539
> URL: https://issues.apache.org/jira/browse/MJAVADOC-539
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Julian Reschke
>Assignee: Robert Scholte
>Priority: Major
> Attachments: MAJAVADOC-539.patch, minimal.zip
>
>
> See https://issues.apache.org/jira/browse/OAK-7789 - downgrading to 3.0.0 
> fixes the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2019-04-26 Thread Julian Reschke (JIRA) 


[ 
https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827012#comment-16827012
 ] 

Julian Reschke commented on MJAVADOC-539:
-

 [^MAJAVADOC-539.patch]  - very simple patch that removes "index.html" from 
redirects that end in "index.html".

[~rfscholte] - could you please review?

> Upgrading plugin from 3.0.0 to 3.0.1 and 3.1.0 breaks certain external 
> javadoc links
> 
>
> Key: MJAVADOC-539
> URL: https://issues.apache.org/jira/browse/MJAVADOC-539
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Julian Reschke
>Assignee: Robert Scholte
>Priority: Major
> Attachments: MAJAVADOC-539.patch, minimal.zip
>
>
> See https://issues.apache.org/jira/browse/OAK-7789 - downgrading to 3.0.0 
> fixes the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2019-04-10 Thread Julian Reschke (JIRA) 


[ 
https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814720#comment-16814720
 ] 

Julian Reschke commented on MJAVADOC-539:
-

I agree that the server acts strange (and I tried to get it fixed). But fact 
is, the doctool actually works with that redirect; it's the javadoc maven 
plugin that mangles the URI right now,

> Upgrading plugin from 3.0.0 to 3.0.1 and 3.1.0 breaks certain external 
> javadoc links
> 
>
> Key: MJAVADOC-539
> URL: https://issues.apache.org/jira/browse/MJAVADOC-539
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Julian Reschke
>Assignee: Robert Scholte
>Priority: Major
> Attachments: minimal.zip
>
>
> See https://issues.apache.org/jira/browse/OAK-7789 - downgrading to 3.0.0 
> fixes the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2019-04-10 Thread Julian Reschke (JIRA) 


[ 
https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814157#comment-16814157
 ] 

Julian Reschke commented on MJAVADOC-539:
-

Attaching 
 and 
testing with jdk 8:

Testing with 3.0.0 (pass):
{noformat}
[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building test 21
[INFO] 
[INFO]
[INFO] >>> maven-javadoc-plugin:3.0.0:javadoc (default-cli) > generate-sources 
@ test >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ test 
---
[INFO]
[INFO] <<< maven-javadoc-plugin:3.0.0:javadoc (default-cli) < generate-sources 
@ test <<<
[INFO]
[INFO]
[INFO] --- maven-javadoc-plugin:3.0.0:javadoc (default-cli) @ test ---
[INFO]
Loading source file C:\projects\apache\minimal\src\main\java\Main.java...
Constructing Javadoc information...
Standard Doclet version 1.8.0_172
Building tree for all the packages and classes...
Generating C:\projects\apache\minimal\target\site\apidocs\Main.html...
Generating C:\projects\apache\minimal\target\site\apidocs\package-frame.html...
Generating 
C:\projects\apache\minimal\target\site\apidocs\package-summary.html...
Generating C:\projects\apache\minimal\target\site\apidocs\package-tree.html...
Generating 
C:\projects\apache\minimal\target\site\apidocs\constant-values.html...
Generating C:\projects\apache\minimal\target\site\apidocs\class-use\Main.html...
Generating C:\projects\apache\minimal\target\site\apidocs\package-use.html...
Building index for all the packages and classes...
Generating C:\projects\apache\minimal\target\site\apidocs\overview-tree.html...
Generating C:\projects\apache\minimal\target\site\apidocs\index-all.html...
Generating 
C:\projects\apache\minimal\target\site\apidocs\deprecated-list.html...
Building index for all classes...
Generating 
C:\projects\apache\minimal\target\site\apidocs\allclasses-frame.html...
Generating 
C:\projects\apache\minimal\target\site\apidocs\allclasses-noframe.html...
Generating C:\projects\apache\minimal\target\site\apidocs\index.html...
Generating C:\projects\apache\minimal\target\site\apidocs\help-doc.html...
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 2.838 s
[INFO] Finished at: 2019-04-10T09:38:55+02:00
[INFO] Final Memory: 18M/307M
[INFO] 
{noformat}

Testing with 3.1.0 (fail):
{noformat}
[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building test 21
[INFO] 
[INFO]
[INFO] >>> maven-javadoc-plugin:3.1.0:javadoc (default-cli) > generate-sources 
@ test >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ test 
---
[INFO]
[INFO] <<< maven-javadoc-plugin:3.1.0:javadoc (default-cli) < generate-sources 
@ test <<<
[INFO]
[INFO]
[INFO] --- maven-javadoc-plugin:3.1.0:javadoc (default-cli) @ test ---
[INFO]
Loading source file C:\projects\apache\minimal\src\main\java\Main.java...
Constructing Javadoc information...
Standard Doclet version 1.8.0_172
Building tree for all the packages and classes...
Generating C:\projects\apache\minimal\target\site\apidocs\Main.html...
Generating C:\projects\apache\minimal\target\site\apidocs\package-frame.html...
Generating 
C:\projects\apache\minimal\target\site\apidocs\package-summary.html...
Generating C:\projects\apache\minimal\target\site\apidocs\package-tree.html...
Generating 
C:\projects\apache\minimal\target\site\apidocs\constant-values.html...
Generating C:\projects\apache\minimal\target\site\apidocs\class-use\Main.html...
Generating C:\projects\apache\minimal\target\site\apidocs\package-use.html...
Building index for all the packages and classes...
Generating C:\projects\apache\minimal\target\site\apidocs\overview-tree.html...
Generating C:\projects\apache\minimal\target\site\apidocs\index-all.html...
Generating 
C:\projects\apache\minimal\target\site\apidocs\deprecated-list.html...
Building index for all classes...
Generating 
C:\projects\apache\minimal\target\site\apidocs\allclasses-frame.html...
Generating 
C:\projects\apache\minimal\target\site\apidocs\allclasses-noframe.html...
Generating C:\projects\apache\minimal\target\site\apidocs\index.html...
Generating C:\projects\apache\minimal\target\site\apidocs\help-doc.html...
1 warning
[WARNING] Javadoc Warnings
[WARNING] javadoc: warning - Error fetching URL: 
https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/index.html/
[INFO]

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

2019-04-10 Thread Julian Reschke (JIRA) 


 [ 
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 external 
> javadoc links
> 
>
> Key: MJAVADOC-539
> URL: https://issues.apache.org/jira/browse/MJAVADOC-539
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Julian Reschke
>Assignee: Robert Scholte
>Priority: Major
> Attachments: minimal.zip
>
>
> See https://issues.apache.org/jira/browse/OAK-7789 - downgrading to 3.0.0 
> fixes the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2019-04-09 Thread Julian Reschke (JIRA) 


[ 
https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813309#comment-16813309
 ] 

Julian Reschke edited comment on MJAVADOC-539 at 4/9/19 12:08 PM:
--

[~rfscholte]: we still see the same issue with 3.1.0.

Please try with [https://svn.apache.org/repos/asf/jackrabbit/oak/trunk/] and 
the updated plugin (oak-parent/pom.xml).


was (Author: reschke):
We still see the same issue with 3.1.0.

> 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
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Julian Reschke
>Assignee: Robert Scholte
>Priority: Major
>
> See https://issues.apache.org/jira/browse/OAK-7789 - downgrading to 3.0.0 
> fixes the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2019-04-09 Thread Julian Reschke (JIRA) 


[ 
https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813309#comment-16813309
 ] 

Julian Reschke commented on MJAVADOC-539:
-

We still see the same issue with 3.1.0.

> 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
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Julian Reschke
>Assignee: Robert Scholte
>Priority: Major
>
> See https://issues.apache.org/jira/browse/OAK-7789 - downgrading to 3.0.0 
> fixes the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-10-18 Thread Julian Reschke (JIRA) 


[ 
https://issues.apache.org/jira/browse/MJAVADOC-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654955#comment-16654955
 ] 

Julian Reschke commented on MJAVADOC-539:
-

Possible solutions:

 
 * only use the redirect if it changed the URI scheme (from "http" to "https")
 * only use the redirect if the original URI is not a prefix match of the 
redirected URI

> 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
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Julian Reschke
>Priority: Minor
>
> See https://issues.apache.org/jira/browse/OAK-7789 - downgrading to 3.0.0 
> fixes the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-10-18 Thread Julian Reschke (JIRA) 


 [ 
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 external javadoc links
> --
>
> Key: MJAVADOC-539
> URL: https://issues.apache.org/jira/browse/MJAVADOC-539
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Julian Reschke
>Priority: Major
>
> See https://issues.apache.org/jira/browse/OAK-7789 - downgrading to 3.0.0 
> fixes the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-09-28 Thread Julian Reschke (JIRA) 


 [ 
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 javadoc links
> --
>
> Key: MJAVADOC-539
> URL: https://issues.apache.org/jira/browse/MJAVADOC-539
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Julian Reschke
>Priority: Minor
>
> See https://issues.apache.org/jira/browse/OAK-7789 - downgrading to 3.0.0 
> fixes the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-09-28 Thread Julian Reschke (JIRA) 
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
 Project: Maven Javadoc Plugin
  Issue Type: Bug
Reporter: Julian Reschke


See https://issues.apache.org/jira/browse/OAK-7789 - downgrading to 3.0.0 fixes 
the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-04-11 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434914#comment-16434914
 ] 

Julian Reschke commented on SUREFIRE-1512:
--

Thanks, [~tibor17]. It would be great to have that in the next release. Would 
that 2.21.1 or 3.0?

> ProcessInfo for Windows is prone to timezone offset changes
> ---
>
> Key: SUREFIRE-1512
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1512
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Julian Reschke
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> For some reason, on one of my machines, the current DST offset changes 
> between calls. See 
> .
>  This will cause surefire to think the forked VM terminated, as the string 
> compare of time stamps detects a change.
> It would be good if the comparison code would actually parse the string value 
> into a DST/TZ agnostic value for comparison. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-04-10 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16432164#comment-16432164
 ] 

Julian Reschke commented on SUREFIRE-1512:
--

[~tibor17] - right now it does. I have confirmed by having it fail with 2.21.0, 
having it pass with the snapshot version, and having it fail again with 2.21.0.

My workaround is to run with the machine running with UTC timezone (which does 
not have DST).

> ProcessInfo for Windows is prone to timezone offset changes
> ---
>
> Key: SUREFIRE-1512
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1512
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Julian Reschke
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> For some reason, on one of my machines, the current DST offset changes 
> between calls. See 
> .
>  This will cause surefire to think the forked VM terminated, as the string 
> compare of time stamps detects a change.
> It would be good if the comparison code would actually parse the string value 
> into a DST/TZ agnostic value for comparison. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-04-10 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16432069#comment-16432069
 ] 

Julian Reschke commented on SUREFIRE-1512:
--

[~tibor17] - works for me. Any chance this could also be added to 2.21.1?

> ProcessInfo for Windows is prone to timezone offset changes
> ---
>
> Key: SUREFIRE-1512
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1512
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Julian Reschke
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> For some reason, on one of my machines, the current DST offset changes 
> between calls. See 
> .
>  This will cause surefire to think the forked VM terminated, as the string 
> compare of time stamps detects a change.
> It would be good if the comparison code would actually parse the string value 
> into a DST/TZ agnostic value for comparison. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-04-08 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429672#comment-16429672
 ] 

Julian Reschke commented on SUREFIRE-1512:
--

Sound like a good approach. Let me know if you have something to test and I'll 
try on my affected machine...

> ProcessInfo for Windows is prone to timezone offset changes
> ---
>
> Key: SUREFIRE-1512
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1512
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Julian Reschke
>Assignee: Tibor Digana
>Priority: Major
>
> For some reason, on one of my machines, the current DST offset changes 
> between calls. See 
> .
>  This will cause surefire to think the forked VM terminated, as the string 
> compare of time stamps detects a change.
> It would be good if the comparison code would actually parse the string value 
> into a DST/TZ agnostic value for comparison. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-04-07 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429304#comment-16429304
 ] 

Julian Reschke commented on SUREFIRE-1512:
--

[~tibor17] - the problem doesn't happen at the time DST became active (that 
would be neglectable), but at random times. {{wmic}} just switches to a 
different TZ when reporting the timestamp. I haven't figured out why, but 
suspect there's another piece of software on the machine involved.

In any case, using the TZ offset when converting the string to a 
seconds-since-epoch (or whatever) should be sufficient. 

> ProcessInfo for Windows is prone to timezone offset changes
> ---
>
> Key: SUREFIRE-1512
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1512
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Julian Reschke
>Assignee: Tibor Digana
>Priority: Major
>
> For some reason, on one of my machines, the current DST offset changes 
> between calls. See 
> .
>  This will cause surefire to think the forked VM terminated, as the string 
> compare of time stamps detects a change.
> It would be good if the comparison code would actually parse the string value 
> into a DST/TZ agnostic value for comparison. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-04-06 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/WAGON-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428590#comment-16428590
 ] 

Julian Reschke commented on WAGON-516:
--

2.16 should work for Java 9 as well.

> Upgrade Jackrabbit WebDAV to 2.16.1
> ---
>
> Key: WAGON-516
> URL: https://issues.apache.org/jira/browse/WAGON-516
> Project: Maven Wagon
>  Issue Type: Dependency upgrade
>  Components: wagon-webdav
>Affects Versions: 3.0.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-04-06 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428342#comment-16428342
 ] 

Julian Reschke commented on SUREFIRE-1444:
--

Opened improvement request: https://issues.apache.org/jira/browse/SUREFIRE-1512

> /usr/bin/ps and /bin/ps not found. Forked JVM fails.
> 
>
> Key: SUREFIRE-1444
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1444
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Windows 7 Pro 64 bits
> Maven 3.5.2 , jdk 1.8.0_152
>Reporter: rfs
>Assignee: Tibor Digana
>Priority: Major
> Attachments: dump.txt, mavenlog.txt
>
>
> mvn test is failed with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.20.1
> maven repository is deleted before but same result.
> mvn test is successfull with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.19.1
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 9.490 s
> [INFO] Finished at: 2017-11-16T08:58:19+01:00
> [INFO] Final Memory: 35M/290M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
> project project-name: There are test fa
> ilures.
> [ERROR]
> [ERROR] Please refer to R:\src\project-name\target\surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar 
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar 
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exi
> t called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar 
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar 
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> [ERROR] at 
> org.apache.maven.DefaultMaven.doExe

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

2018-04-06 Thread Julian Reschke (JIRA) 
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
  Issue Type: Improvement
Affects Versions: 2.21.0
Reporter: Julian Reschke


For some reason, on one of my machines, the current DST offset changes between 
calls. See 
.
 This will cause surefire to think the forked VM terminated, as the string 
compare of time stamps detects a change.

It would be good if the comparison code would actually parse the string value 
into a DST/TZ agnostic value for comparison. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-04-06 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/WAGON-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428324#comment-16428324
 ] 

Julian Reschke commented on WAGON-516:
--

FWIW, you shouldn't use unstable Jackrabbit releases unless you really have 
to... See http://jackrabbit.apache.org/jcr/jackrabbit-roadmap.html

> Upgrade Jackrabbit WebDAV to 2.17.1
> ---
>
> Key: WAGON-516
> URL: https://issues.apache.org/jira/browse/WAGON-516
> Project: Maven Wagon
>  Issue Type: Dependency upgrade
>  Components: wagon-webdav
>Affects Versions: 3.0.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-04-06 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428307#comment-16428307
 ] 

Julian Reschke commented on SUREFIRE-1444:
--

Setting the system time to UTC and disabling DST seems to fix the issue...

> /usr/bin/ps and /bin/ps not found. Forked JVM fails.
> 
>
> Key: SUREFIRE-1444
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1444
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Windows 7 Pro 64 bits
> Maven 3.5.2 , jdk 1.8.0_152
>Reporter: rfs
>Assignee: Tibor Digana
>Priority: Major
> Attachments: dump.txt, mavenlog.txt
>
>
> mvn test is failed with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.20.1
> maven repository is deleted before but same result.
> mvn test is successfull with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.19.1
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 9.490 s
> [INFO] Finished at: 2017-11-16T08:58:19+01:00
> [INFO] Final Memory: 35M/290M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
> project project-name: There are test fa
> ilures.
> [ERROR]
> [ERROR] Please refer to R:\src\project-name\target\surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar 
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar 
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exi
> t called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar 
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar 
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(

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

2018-04-06 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428263#comment-16428263
 ] 

Julian Reschke edited comment on SUREFIRE-1444 at 4/6/18 12:57 PM:
---

Further investigation shows that after rebooting the machine, I'm getting the 
expected "+120" offset, but it falls back to "+060" later. Both timestamps are 
correct of course, but would cause surefire to assume the process indeed 
changed (as it is only doing a string compare). So this would explain why 
surefire thinks the process died - however it's mysterious why the tz format 
changes between two calls.

First call (PID is of a cygwin bash that was running all the time):
{noformat}
> wmic process where "(ProcessId=11460)" get CreationDate
CreationDate
20180406142327.741074+120
{noformat}

But later:
{noformat}
> wmic process where "(ProcessId=11460)" get CreationDate
CreationDate
20180406132327.741074+060
{noformat}

surefire probably could work around the issue by parsing the date.


was (Author: reschke):
Further investigation shows that after rebooting the machine, I'm getting the 
expected "+120" offset, but it falls back to "+060" later. Both timestamps are 
correct of course, but would cause surefire to assume the process indeed 
changed (as it is only doing a string compare). So this would explain why 
surefire thinks the process died - however it's mysterious why the tz format 
changes between two calls.

> /usr/bin/ps and /bin/ps not found. Forked JVM fails.
> 
>
> Key: SUREFIRE-1444
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1444
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Windows 7 Pro 64 bits
> Maven 3.5.2 , jdk 1.8.0_152
>Reporter: rfs
>Assignee: Tibor Digana
>Priority: Major
> Attachments: dump.txt, mavenlog.txt
>
>
> mvn test is failed with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.20.1
> maven repository is deleted before but same result.
> mvn test is successfull with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.19.1
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 9.490 s
> [INFO] Finished at: 2017-11-16T08:58:19+01:00
> [INFO] Final Memory: 35M/290M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
> project project-name: There are test fa
> ilures.
> [ERROR]
> [ERROR] Please refer to R:\src\project-name\target\surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar 
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar 
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exi
> t called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar 
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar 
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
>

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

2018-04-06 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428263#comment-16428263
 ] 

Julian Reschke commented on SUREFIRE-1444:
--

Further investigation shows that after rebooting the machine, I'm getting the 
expected "+120" offset, but it falls back to "+060" later. Both timestamps are 
correct of course, but would cause surefire to assume the process indeed 
changed (as it is only doing a string compare). So this would explain why 
surefire thinks the process died - however it's mysterious why the tz format 
changes between two calls.

> /usr/bin/ps and /bin/ps not found. Forked JVM fails.
> 
>
> Key: SUREFIRE-1444
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1444
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Windows 7 Pro 64 bits
> Maven 3.5.2 , jdk 1.8.0_152
>Reporter: rfs
>Assignee: Tibor Digana
>Priority: Major
> Attachments: dump.txt, mavenlog.txt
>
>
> mvn test is failed with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.20.1
> maven repository is deleted before but same result.
> mvn test is successfull with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.19.1
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 9.490 s
> [INFO] Finished at: 2017-11-16T08:58:19+01:00
> [INFO] Final Memory: 35M/290M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
> project project-name: There are test fa
> ilures.
> [ERROR]
> [ERROR] Please refer to R:\src\project-name\target\surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar 
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar 
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exi
> t called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar 
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar 
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.builder

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

2018-04-06 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428233#comment-16428233
 ] 

Julian Reschke edited comment on SUREFIRE-1444 at 4/6/18 12:23 PM:
---

I have the same problem on Window (non-docker), and apparently it only started 
a few days ago, so something else must have changed on this machine. Reverting 
to an old Surefire version fixes the issue. Running {{wmic}} seems to work.

What I did find out so far is that my two Windows machines differ in the 
reported time zone offset (one says +060, the other one +120), so the one that 
does show the problem may have started to misbehave due to the DST change in 
Germany.


was (Author: reschke):
I have the same problem on Window (non-docker), and apparently it only started 
a few days ago, so something else must have changed on this machine. Reverting 
to an old Surefire version fixes the issue. Running {{wmic}} yields:
{noformat}
> wmic
wmic:root\cli>
{noformat}

What can I do to debug this?

> /usr/bin/ps and /bin/ps not found. Forked JVM fails.
> 
>
> Key: SUREFIRE-1444
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1444
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Windows 7 Pro 64 bits
> Maven 3.5.2 , jdk 1.8.0_152
>Reporter: rfs
>Assignee: Tibor Digana
>Priority: Major
> Attachments: dump.txt, mavenlog.txt
>
>
> mvn test is failed with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.20.1
> maven repository is deleted before but same result.
> mvn test is successfull with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.19.1
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 9.490 s
> [INFO] Finished at: 2017-11-16T08:58:19+01:00
> [INFO] Final Memory: 35M/290M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
> project project-name: There are test fa
> ilures.
> [ERROR]
> [ERROR] Please refer to R:\src\project-name\target\surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar 
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar 
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exi
> t called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar 
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar 
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecu

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

2018-04-06 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428233#comment-16428233
 ] 

Julian Reschke commented on SUREFIRE-1444:
--

I have the same problem on Window (non-docker), and apparently it only started 
a few days ago, so something else must have changed on this machine. Reverting 
to an old Surefire version fixes the issue. Running {{wmic}} yields:
{noformat}
> wmic
wmic:root\cli>
{noformat}

What can I do to debug this?

> /usr/bin/ps and /bin/ps not found. Forked JVM fails.
> 
>
> Key: SUREFIRE-1444
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1444
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 2.20.1
> Environment: Windows 7 Pro 64 bits
> Maven 3.5.2 , jdk 1.8.0_152
>Reporter: rfs
>Assignee: Tibor Digana
>Priority: Major
> Attachments: dump.txt, mavenlog.txt
>
>
> mvn test is failed with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.20.1
> maven repository is deleted before but same result.
> mvn test is successfull with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.19.1
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 9.490 s
> [INFO] Finished at: 2017-11-16T08:58:19+01:00
> [INFO] Final Memory: 35M/290M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
> project project-name: There are test fa
> ilures.
> [ERROR]
> [ERROR] Please refer to R:\src\project-name\target\surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar 
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar 
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exi
> t called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar 
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar 
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [ERROR] at 
> org.apache.

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

2017-11-11 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248469#comment-16248469
 ] 

Julian Reschke commented on SUREFIRE-1424:
--

[~rfscholte] - as a workaround, yes. But this should really be fixed.

[~russgold] - this is what I did in Jackrabbit: 
http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-parent/pom.xml?r1=1812543&r2=1812634&pathrev=1812634&diff_format=h

> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks 
> like Maven specific. I've managed to trim down the problem to [a simple class 
> that doesn't involve Spring 
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<< 
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests)  Time 
> elapsed: 0.006 s  <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException: 
> javax.transaction.TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has 
> also a simple Gradle build that shows it works with Gradle as well.



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

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

2017-10-20 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213718#comment-16213718
 ] 

Julian Reschke commented on SUREFIRE-1424:
--

> IIYUC you say that you added javax.transaction.UserTransaction via Maven 
> dependency on classpath but because of Java 9 already associated 
> javax.transaction package with internal module having same module/package 
> name as in your dependency, your dependency does not take precedence?

Yes.

> How many decisions the new configuration should do?

Not sure what you're getting at. The current situation where 
{{\-\-add-modules}} is added silently definitively causes harm in cases like 
this, though. An override would be appreciated.


> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks 
> like Maven specific. I've managed to trim down the problem to [a simple class 
> that doesn't involve Spring 
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<< 
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests)  Time 
> elapsed: 0.006 s  <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException: 
> javax.transaction.TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has 
> also a simple Gradle build that shows it works with Gradle as well.



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

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

2017-10-20 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213718#comment-16213718
 ] 

Julian Reschke edited comment on SUREFIRE-1424 at 10/21/17 4:00 AM:


bq. IIYUC you say that you added javax.transaction.UserTransaction via Maven 
dependency on classpath but because of Java 9 already associated 
javax.transaction package with internal module having same module/package name 
as in your dependency, your dependency does not take precedence?

Yes.

bq. How many decisions the new configuration should do?

Not sure what you're getting at. The current situation where 
{{\-\-add-modules}} is added silently definitively causes harm in cases like 
this, though. An override would be appreciated.



was (Author: reschke):
> IIYUC you say that you added javax.transaction.UserTransaction via Maven 
> dependency on classpath but because of Java 9 already associated 
> javax.transaction package with internal module having same module/package 
> name as in your dependency, your dependency does not take precedence?

Yes.

> How many decisions the new configuration should do?

Not sure what you're getting at. The current situation where 
{{\-\-add-modules}} is added silently definitively causes harm in cases like 
this, though. An override would be appreciated.


> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks 
> like Maven specific. I've managed to trim down the problem to [a simple class 
> that doesn't involve Spring 
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<< 
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests)  Time 
> elapsed: 0.006 s  <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException: 
> javax.transaction.TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has 
> also a simple Gradle build that shows it works with Gradle as well.



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

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

2017-10-20 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213145#comment-16213145
 ] 

Julian Reschke edited comment on SUREFIRE-1424 at 10/20/17 8:04 PM:


[~tibor17] - the problem is the default of adding {{\-\-add-modules}} under 
Java 9. Because it does,  {{javax.transaction.UserTransaction}} becomes 
invisible, *although* it is on the classpath. My workaround is to set 
{\{-\-add-modules java.xml.bind}}, so that surefire does not add 
{{\-\-add-modules}} itself. A config parameter that disables this behavior 
would help a lot.

If you want to reproduce this, checkout 
https://svn.apache.org/repos/asf/jackrabbit/trunk/ with a revision prior to 
http://svn.apache.org/r1812634, and then try to build with jdk-9.



was (Author: reschke):
[~tibor17] - the problem is the default of adding "--add-modules" under Java 9. 
Because it does,  javax.transaction.UserTransaction becomes invisible, 
*although* it is on the classpath. My workaround is to set "--add-modules 
java.xml.bind", so that surefire does not add "--add-modules" itself.

If you want to reproduce this, checkout 
https://svn.apache.org/repos/asf/jackrabbit/trunk/ with a revision prior to 
http://svn.apache.org/r1812634, and then try to build with jdk-9.


> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks 
> like Maven specific. I've managed to trim down the problem to [a simple class 
> that doesn't involve Spring 
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<< 
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests)  Time 
> elapsed: 0.006 s  <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException: 
> javax.transaction.TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has 
> also a simple Gradle build that shows it works with Gradle as well.



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

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

2017-10-20 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213145#comment-16213145
 ] 

Julian Reschke commented on SUREFIRE-1424:
--

[~tibor17] - the problem is the default of adding "--add-modules" under Java 9. 
Because it does,  javax.transaction.UserTransaction becomes invisible, 
*although* it is on the classpath. My workaround is to set "--add-modules 
java.xml.bind", so that surefire does not add "--add-modules" itself.

If you want to reproduce this, checkout 
https://svn.apache.org/repos/asf/jackrabbit/trunk/ with a revision prior to 
http://svn.apache.org/r1812634, and then try to build with jdk-9.


> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks 
> like Maven specific. I've managed to trim down the problem to [a simple class 
> that doesn't involve Spring 
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<< 
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests)  Time 
> elapsed: 0.006 s  <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException: 
> javax.transaction.TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has 
> also a simple Gradle build that shows it works with Gradle as well.



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

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

2017-10-19 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211054#comment-16211054
 ] 

Julian Reschke commented on SUREFIRE-1424:
--

FWIW, I've for now worked around the issue by always specifying:
{noformat}
-XX:+IgnoreUnrecognizedVMOptions --add-modules=java.xml.bind
{noformat}

(Note the "=" because otherwise Java 8 will see two arguments)

> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks 
> like Maven specific. I've managed to trim down the problem to [a simple class 
> that doesn't involve Spring 
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<< 
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests)  Time 
> elapsed: 0.006 s  <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException: 
> javax.transaction.TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has 
> also a simple Gradle build that shows it works with Gradle as well.



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

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

2017-10-19 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210879#comment-16210879
 ] 

Julian Reschke commented on SUREFIRE-1424:
--

I think the magic to include --add-modules was indeed well-intended, but if the 
edge cases affect you it's becoming hard to use 2.20.1 with Java 9. A potential 
compromise would be to leave the magic in, but to have a way to disable it.

> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks 
> like Maven specific. I've managed to trim down the problem to [a simple class 
> that doesn't involve Spring 
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<< 
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests)  Time 
> elapsed: 0.006 s  <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException: 
> javax.transaction.TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has 
> also a simple Gradle build that shows it works with Gradle as well.



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

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

2017-10-19 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210827#comment-16210827
 ] 

Julian Reschke commented on SUREFIRE-1424:
--

Note there's a similar problem with javax.transaction.UserTransaction - see 
.

> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks 
> like Maven specific. I've managed to trim down the problem to [a simple class 
> that doesn't involve Spring 
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<< 
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests)  Time 
> elapsed: 0.006 s  <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException: 
> javax.transaction.TransactionManager
>   at 
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has 
> also a simple Gradle build that shows it works with Gradle as well.



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