On Fri, Jan 23, 2015 at 10:37:26AM -0800, tony wrote:
> On Fri, Jan 23, 2015 at 07:15:50PM +0100, Emmanuel Bourg wrote:
> > Le 23/01/2015 18:59, Miguel Landaeta a écrit :
> > 
> > > Additionally, the native jar must be available in the maven repo.
> > 
> > It may not be necessary to deploy the native lib in the Maven
> > repository. If the native lib is in the expected multi arch path it can
> > be loaded easily without messing with Maven and a complex library
> > loading logic. It avoids installing arch specific jars containing native
> > libraries in the Maven repository.
> 
> Hi,
> 
> Tim and I have been discussing this via email.  In this situation, I
> think we'll have an arch-all package containing the -native JAR in
> /usj + maven meta-data, but the actual native library contains the .so
> be an arch-any package.

Awesome, I see Tim & Tony are taking care of this.

Cheers,

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche

Attachment: signature.asc
Description: Digital signature

__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
Please use
[email protected] for discussions and questions.

Reply via email to