[jbosstools-issues] [JBoss JIRA] (JBIDE-14370) Add 32bit swt libraries to eclipse64 module as a result of the build

[Yahor Radtsevich (JIRA)]

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

Yahor Radtsevich commented on JBIDE-14370:
------------------------------------------

A more detailed explanation follows.

The idea is to allow BrowserSim to work on 64-bit Eclipse under Windows. The problem with it is that there is no 64-bit Safari. Thus, the only way to run BrowserSim on 64-bit Eclipse is to run it on 32-bit JVM with 32-bit SWT in the java classpath.

We would like to use a BrowserSim fragment to provide 32-bit SWT bundles. The fragment should look like this:
{code}
\org.jboss.tools.vpe.browsersim.win32.win32.x86_64
   \lib
       \org.eclipse.swt_x.xxx.xx.jar
       \org.eclipse.swt.win32.win32.x86_x.xxx.xx.jar
{code}
Our BrowserSim launcher will automatically add these SWT jars to the BrowserSim's classpath and then everything is fine.

Of course we could commit this fragment with SWT jars to git repository, but it is obviously not a good idea.
[~mickael_istria], is it possible to *automatically add 32-bit SWT libraries to this fragment during the building process*?
                
> Add 32bit swt libraries to eclipse64 module as a result of the build
> --------------------------------------------------------------------
>
>                 Key: JBIDE-14370
>                 URL: https://issues.jboss.org/browse/JBIDE-14370
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: browsersim
>            Reporter: Konstantin Marmalyukov
>            Assignee: Mickael Istria
>             Fix For: 4.1.0.Beta1
>
>
> We need to have latest 32-bit SWT libraries in resources folder of eclipse64 browsersim module to make user able to run browserSim from x64 eclipse.

--
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