[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Problems when trying to create Debian packages from latest Netlib

Hi Sam,

I'm writing you on behalf of the Debian Java team which maintains Netlib
for Debian.  I have a specific interest in netlib since it is a
precondition for some scientific software in Debian.

While I managed to build version 0.9.3 nicely which is also part of
Debian I have severy problems to build the Maven based 1.x series of
Netlib.  The problem is that the Debian build system does not permit
downloads of binary code (like JARs) from the internet.  A package needs
to build on an autark machine disconnected from the internet which means
in turn that Debian needs to package all predependencies which in
principle seems to be the case for Netlib.

Unfortunately due to the build system you crafted for netlib this is
not the case.

In order to build the core module the generator module is required as a
plugin or native_ref/java/pom.xml depends on the core module. We need to
build these modules first, however when we execute the current build
system, no code is generated because the generator module is not
included in pom.xml. How can we build netlib from source and avoid to
download prebuilt artifacts from maven central?

We have also discovered that the build system won't work with Maven 3
anymore. Maven requires a <version></version> for all artifacts and for
instance you haven't specified one for Lombok. When we try to run the
generator module separately, it also fails with an Maven error:

incompatible types: java.lang.Object cannot be converted to

We believe this is due to the fact that you used an older version of
Maven back then.

It would be really great if you could fix this to enable me adding
the latest and greatest Netlib to Debian.

Kind regards



Reply to: