[jboss-jira] [JBoss JIRA] Updated: (JBWEB-213) JBoss Web Native Connectors bundles contain wrong paths

[Dan Mazzell (JIRA)]

     [ https://issues.jboss.org/browse/JBWEB-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Mazzell updated JBWEB-213:
------------------------------

        Environment: Non-Windows, Linux x86, X64, IA64, Solaris,   (was: Non-Winows, Linux x86, X64, IA64, Solaris, )
    Forum Reference: http://community.jboss.org/thread/141882?tstart=0, http://community.jboss.org/wiki/HowToAddAprToJBoss  (was: http://community.jboss.org/thread/141882?tstart=0, http://community.jboss.org/wiki/HowToAddAprToJBoss)


> JBoss Web Native Connectors bundles contain wrong paths
> -------------------------------------------------------
>
>                 Key: JBWEB-213
>                 URL: https://issues.jboss.org/browse/JBWEB-213
>             Project: JBoss Web
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: Non-Windows, Linux x86, X64, IA64, Solaris, 
>            Reporter: Dan Mazzell
>            Assignee: Remy Maucherat
>            Priority: Minor
>
> When extracting the jboss-native 2.x tar bundles, the location of the libs should match what the startup script, (run.sh) is expecting.
> For example, for a Linux x64 system, the run.sh expects the native libraries to be placed into the jboss/bin/META-INF/lib/linux2/x64/ directory, however when tar-gunzipping the jboss-native-2.0.10-linux2-x64-ssl.tar.gz, the binaries are placed in the bin/naitive dir. 
> The tar file path should match what JBoss's run.sh sets up the path as.

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