GitHub user sjcorbett opened a pull request:

    https://github.com/apache/brooklyn-server/pull/224

    Fix VanillaJavaApp's stdin and env

    The output from the classpath gathering step currently includes Brooklyn's 
"Executed ... , result: 0" info, which means that classpaths look like this:
    
    
CLASSPATH="/tmp/brooklyn-sam/apps/l8wk2l74in/entities/VanillaJavaApp_zn86w6blx8/lib/derby-10.12.1.1.jar:/tmp/brooklyn-sam/apps/l8wk2l74in/entities/VanillaJavaApp_zn86w6blx8/lib/my-app-1.0.jar:/tmp/brooklyn-sam/apps/l8wk2l74in/entities/VanillaJavaApp_zn86w6blx8/lib/**Executed**:/tmp/brooklyn-sam/apps/l8wk2l74in/entities/VanillaJavaApp_zn86w6blx8/lib**/tmp/brooklyn-20160629-191833075-b9bF-customizing-classpath_VanillaJ.sh,**:/tmp/brooklyn-sam/apps/l8wk2l74in/entities/VanillaJavaApp_zn86w6blx8/lib/**result**:/tmp/brooklyn-sam/apps/l8wk2l74in/entities/VanillaJavaApp_zn86w6blx8/lib/**0**"
    
    Did something change internally? It's hard to believe that this has always 
been the case.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sjcorbett/brooklyn-server 
fix/java-process-stdin

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/brooklyn-server/pull/224.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #224
    
----

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to