[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8461) Editing AS Launch Configuration -Djava.library.path

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593789#comment-12593789 ] 

Max Rydahl Andersen commented on JBIDE-8461:
--------------------------------------------

Before I forget after some digging we can solve the specific issue with java.library.path by utilizing the Native Library support for Eclipse classpath containers.

Thus instead of us "tweaking" the launchconfig we simply declare on jboss's classpath container that it has a native library part; then if users does not specify anything that is what will be used but if users does declare -Djava.library.path then that will override anything we provide.

That should give the best balance of magically working out of the box and explicit control if needed.



> Editing AS Launch Configuration -Djava.library.path
> ---------------------------------------------------
>
>                 Key: JBIDE-8461
>                 URL: https://issues.jboss.org/browse/JBIDE-8461
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.2.0.CR1
>         Environment: Win7 64-bit, 32-bit 1.6 JVM
>            Reporter: Burr Sutter
>            Assignee: Rob Stryker
>              Labels: as_backwards
>             Fix For: 3.2.1, 3.3.0.M1
>
>         Attachments: native_lib_editing1.png, native_lib_editing2.png
>
>
> It seems that you can not make changes to -Djava.library.path on the Launch configuration properties.  In addition, dropping your native libs into this directory are not recognized when the server is launched - I am trying to add the JBoss Native tc-native1.dll to my AS6
> The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: D:\servers\jboss-6.0.0.Final\bin\native;

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira