You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2012/11/27 16:37:58 UTC

[jira] [Created] (SLING-2682) JarExecutor should take java.home into account

Bertrand Delacretaz created SLING-2682:
------------------------------------------

             Summary: JarExecutor should take java.home into account
                 Key: SLING-2682
                 URL: https://issues.apache.org/jira/browse/SLING-2682
             Project: Sling
          Issue Type: Bug
          Components: Testing
    Affects Versions: org.apache.sling.testing.tools 1.0.4
            Reporter: Bertrand Delacretaz
            Priority: Minor


The JarExecutor should prepend the value of the java.home system property to the name of the java executable - currently it simply executes java or java.exe and as such always gets the default JVM, even if the JarExecutor was started from a different VM

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2682) JarExecutor should take java.home into account

Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz updated SLING-2682:
---------------------------------------

    Fix Version/s: org.apache.sling.testing.tools 1.0.6
    
> JarExecutor should take java.home into account
> ----------------------------------------------
>
>                 Key: SLING-2682
>                 URL: https://issues.apache.org/jira/browse/SLING-2682
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: org.apache.sling.testing.tools 1.0.4
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: org.apache.sling.testing.tools 1.0.6
>
>
> The JarExecutor should prepend the value of the java.home system property to the name of the java executable - currently it simply executes java or java.exe and as such always gets the default JVM, even if the JarExecutor was started from a different VM

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2682) JarExecutor should take java.home into account

Posted by "Robert Munteanu (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504681#comment-13504681 ] 

Robert Munteanu commented on SLING-2682:
----------------------------------------

See also SLING-2551


                
> JarExecutor should take java.home into account
> ----------------------------------------------
>
>                 Key: SLING-2682
>                 URL: https://issues.apache.org/jira/browse/SLING-2682
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: org.apache.sling.testing.tools 1.0.4
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>
> The JarExecutor should prepend the value of the java.home system property to the name of the java executable - currently it simply executes java or java.exe and as such always gets the default JVM, even if the JarExecutor was started from a different VM

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2682) JarExecutor should take java.home into account

Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504693#comment-13504693 ] 

Bertrand Delacretaz commented on SLING-2682:
--------------------------------------------

[~rombert] sorry I was too quick, and fixed this in a contrary way than what I suggested in SLING-2551 ;-)

Does this fix work for you? If so, can we mark SLING-2551 as won't fix?
                
> JarExecutor should take java.home into account
> ----------------------------------------------
>
>                 Key: SLING-2682
>                 URL: https://issues.apache.org/jira/browse/SLING-2682
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: org.apache.sling.testing.tools 1.0.4
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: org.apache.sling.testing.tools 1.0.6
>
>
> The JarExecutor should prepend the value of the java.home system property to the name of the java executable - currently it simply executes java or java.exe and as such always gets the default JVM, even if the JarExecutor was started from a different VM

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-2682) JarExecutor should take java.home into account

Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz resolved SLING-2682.
----------------------------------------

    Resolution: Fixed
      Assignee: Bertrand Delacretaz

Fixed in revision 1414230
                
> JarExecutor should take java.home into account
> ----------------------------------------------
>
>                 Key: SLING-2682
>                 URL: https://issues.apache.org/jira/browse/SLING-2682
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: org.apache.sling.testing.tools 1.0.4
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: org.apache.sling.testing.tools 1.0.6
>
>
> The JarExecutor should prepend the value of the java.home system property to the name of the java executable - currently it simply executes java or java.exe and as such always gets the default JVM, even if the JarExecutor was started from a different VM

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2682) JarExecutor should take java.home into account

Posted by "Robert Munteanu (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504695#comment-13504695 ] 

Robert Munteanu commented on SLING-2682:
----------------------------------------

Yes, this is fine for me.
                
> JarExecutor should take java.home into account
> ----------------------------------------------
>
>                 Key: SLING-2682
>                 URL: https://issues.apache.org/jira/browse/SLING-2682
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: org.apache.sling.testing.tools 1.0.4
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: org.apache.sling.testing.tools 1.0.6
>
>
> The JarExecutor should prepend the value of the java.home system property to the name of the java executable - currently it simply executes java or java.exe and as such always gets the default JVM, even if the JarExecutor was started from a different VM

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira