[
http://jira.codehaus.org/browse/MWEBSTART-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186010#action_186010
]
Andrew Thorburn edited comment on MWEBSTART-8 at 8/4/09 11:51 PM:
------------------------------------------------------------------
I'm also interested in this issue being fixed. It's making things very tricky
with regards to being able to deploy a SWT application...
EDIT: And I'm quite surprised that this issue has been around for *3 years*
without being fixed.
All I need is some simple way of being able to do the following:
Assuming I have a set of profiles that load the Linux JARs for SWT and the
Windows JARs for SWT depending on the operating system of the developer, I want
to be able to manually load all the dependencies for the operating system(s)
I'm targeting.
I then need to be able to specify (somehow) that those JARs should be added to
their own resource elements, with a specific OS/Arch attribute.
e.g.
I have the following dependencies:
<dependency>
<groupId>org.eclipse.swt.gtk.linux</groupId>
<artifactId>gtk-x86</artifactId>
<version>3.3.0-v3346</version>
</dependency>
<dependency>
<groupId>org.eclipse.swt.win32.win32</groupId>
<artifactId>win32-x86</artifactId>
<version>3.3.0-v3346</version>
</dependency>
I want most of my dependencies to be listed as normal, but I want some way (I'm
not very fussy - as long as it's possible, I don't care about the details :))
of turning the above JARs into the following:
<resources os="Linux" arch="i386">
<jar href="gtk-x86-3.3.0-v3346.jar" />
</resources>
<resources os="Windows">
<jar href="win32-x86-3.3.0-v3346.jar" />
</resources>
Ideally, whatever method I use should be compatible with the jnlp-single goal.
As it stands now, I'm not sure I'm going to be able to use Maven to build this
project, which is a real shame because I really like Maven, but if I can't get
it to include some OS-specific deps in the right way, it's not all that useful
to me.
was (Author: ipsi):
I'm also interested in this issue being fixed. It's making things very
tricky with regards to being able to deploy a SWT application...
All I need is some simple way of being able to do the following:
Assuming I have a set of profiles that load the Linux JARs for SWT and the
Windows JARs for SWT depending on the operating system of the developer, I want
to be able to manually load all the dependencies for the operating system(s)
I'm targeting.
I then need to be able to specify (somehow) that those JARs should be added to
their own resource elements, with a specific OS/Arch attribute.
e.g.
I have the following dependencies:
<dependency>
<groupId>org.eclipse.swt.gtk.linux</groupId>
<artifactId>gtk-x86</artifactId>
<version>3.3.0-v3346</version>
</dependency>
<dependency>
<groupId>org.eclipse.swt.win32.win32</groupId>
<artifactId>win32-x86</artifactId>
<version>3.3.0-v3346</version>
</dependency>
I want most of my dependencies to be listed as normal, but I want some way (I'm
not very fussy - as long as it's possible, I don't care about the details :))
of turning the above JARs into the following:
<resources os="Linux" arch="i386">
<jar href="gtk-x86-3.3.0-v3346.jar" />
</resources>
<resources os="Windows">
<jar href="win32-x86-3.3.0-v3346.jar" />
</resources>
Ideally, whatever method I use should be compatible with the jnlp-single goal.
As it stands now, I'm not sure I'm going to be able to use Maven to build this
project, which is a real shame because I really like Maven, but if I can't get
it to include some OS-specific deps in the right way, it's not all that useful
to me.
> support native libraries
> ------------------------
>
> Key: MWEBSTART-8
> URL: http://jira.codehaus.org/browse/MWEBSTART-8
> Project: Maven 2.x Webstart Plugin
> Issue Type: New Feature
> Components: jnlps
> Reporter: Jerome Lacoste
> Assignee: Jerome Lacoste
> Fix For: 1.0-alpha-3
>
> Attachments: jnlpMaven.diff, MWEBSTART-8.diff, MWEBSTART-8a.diff,
> MWEBSTART-8b.patch, MWEBSTART-8c.patch
>
>
> nativelib are resiyrces that are tagged in the following way in a jnlp file:
> <resources os="Windows">
> <nativelib href="thedll.jar"/>
> </resources>
> To support nativelib at the same level of simplicity that the usual
> dependencies are supported requires to:
> - automatically identify them from
> - automatically wrap .dll .so files in jar files
> Q: what about jar files that are architecture dependent?
> In maven 1 it was possible to attach some properties to the dependencies. But
> we cannot use that anymore.
> We could
> 1- mark the dependencies in the pom using the correct <type> in the pom. E.g.
> <type>dll</type>
> 2- make the plugin automatically wrap the native dependency inside a jar.
> 3- automatically fill up the <nativelib> elements using some sort of filter
> mecanism
> <resources os="Windows">
> $allDependencies.filter("dll")
> </resources>
> ??
> $dependencies would implicitly map to $allDependencies.filter("jar") for
> backward compatibility.
> Better: the filter() argument might be a JDK 1.4 regex matching a dependency
> notation. That way we solve the architecture issue (we can match names,
> types, etc..)
> That's just one idea. We can perhaps do better? Let me know how you see it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
