On Wed, 2018-08-15 at 00:02 +0200, Markus Koschany wrote:
> Hi folks,
>
> during DebConf18 I tried to improve our documentation how to package
> new
> Java applications and libraries.
>
> I completely rewrote most of the current documentation. I had the
> following ideas:
>
> https://wiki.debian
Hello,
`gradle-debian-helper` is your friend, you can take a look at
`uncommons-maths` [1] for example. It basically substitutes the
hardcoded versions of compile dependencies and generates Maven POM
files so that you can install them into `/usr/share/maven-repo` using
`maven-repo-helper`. Unfortu
Hi Emmanuel,
that did the trick!
Thank you very much,
Alex
On 16.10.2013, at 18:18, Emmanuel Bourg wrote:
> Hi Alex,
>
> Quite often the projects requiring Maven 3 still build fine with Maven
> 2. You just have to patch the prereq in the pom.xml.
>
> Replace:
>
>
>3.0.0
>
>
Hi Alex,
Quite often the projects requiring Maven 3 still build fine with Maven
2. You just have to patch the prereq in the pom.xml.
Replace:
3.0.0
with:
2.2.1
Emmanuel Bourg
Le 16/10/2013 17:58, Alexander Holupirek a écrit :
> Hi all,
>
> i'm in the progress of updatin
Le 10/30/12 1:32 PM, Thomas Koch a écrit :
> Hi,
>
> does anybody know how java packaging is done on the other side? What tools,
> policies does Fedora has? Could you point me to the related websites?
>
> Thank you,
>
> Thomas Koch, http://www.koch.ro
One "bad" point for Java packaging on Fedora
On Tue, 30 Oct 2012 13:32:36 +0100, Thomas Koch wrote:
> does anybody know how java packaging is done on the other side? What tools,
> policies does Fedora has? Could you point me to the related websites?
I just found https://fedoraproject.org/wiki/Packaging:Java [0];
haven't read it but maybe i
> Hello,
Hi Vincent,
>
> Gabriele Giacone wrote:
>> I'm packaging sweethome3d [1], a java application.
Ok, so my next email will start with:
'Hello,
I'm packaging a java application and some libraries' :)
> The final jar can only contain the libraries for which the source code
> is in the ori
Hello,
Gabriele Giacone wrote:
> I'm packaging sweethome3d [1], a java application.
> I have some questions regarding the best Debian way to do it.
> The upstream tarball includes many libraries which are all included
> during the build in the final jar.
> Most of these libraries are also avai
Hallo Daniel,
* Daniel Bonniot wrote:
>That's great. Will you keep both 2.1 and 3.0 in parallel in Debian, or
>simply upgrade the packages to 3.0?
My current planing looks like this:
* split the package into at several source packages, so that swt-gtk
and the eclipse compiler can go to main a
BTW: I will try to package the eclipse 3.0 stream after the next
release
That's great. Will you keep both 2.1 and 3.0 in parallel in Debian, or
simply upgrade the packages to 3.0?
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PRO
On Thu, Jan 24, 2002 at 09:55:22PM -0500, Susan G. Kleinmann wrote:
> From my various attempts to build CVS versions of java packages, it
> seems to happen again and again that a given package depends not
> only on a bunch of other java packages, but on some particular version
> of each of those pa
On Thu, Jan 24, 2002 at 09:55:22PM -0500, Susan G. Kleinmann wrote:
> From my various attempts to build CVS versions of java packages, it
> seems to happen again and again that a given package depends not
> only on a bunch of other java packages, but on some particular version
> of each of those p
What about saving it as a lib and creating a sim-link to it named
/usr/bin/saxon also?
:)
- Original Message -
From: "Mark Johnson" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, June 26, 2001 1:53 AM
Subject: java packaging questions
> Hi All,
>
> I package some of the DocBook XML stuff and wa
What about saving it as a lib and creating a sim-link to it named
/usr/bin/saxon also?
:)
- Original Message -
From: "Mark Johnson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 26, 2001 1:53 AM
Subject: java packaging questions
> Hi All,
>
> I package some of the DocB
On Monday 25 June 2001 15:53, Mark Johnson wrote:
> Hi All,
>
> I package some of the DocBook XML stuff and want to package some java
> xslt processing tools as well, but I'm not too clear on a few policy
> points. Any help/suggestions would be much appreciated. Here goes:
>
> 1. Package naming, li
* Mark Johnson
|I have similar questions for other packages I'd like to upload. The
|arbortext catalog classes (and related extensions) that provide
|catalog support for saxon and XT are an example. I could package
|the base classes as "lib-arbortext-java", the saxon extensions as
On Monday 25 June 2001 15:53, Mark Johnson wrote:
> Hi All,
>
> I package some of the DocBook XML stuff and want to package some java
> xslt processing tools as well, but I'm not too clear on a few policy
> points. Any help/suggestions would be much appreciated. Here goes:
>
> 1. Package naming, l
* Mark Johnson
|I have similar questions for other packages I'd like to upload. The
|arbortext catalog classes (and related extensions) that provide
|catalog support for saxon and XT are an example. I could package
|the base classes as "lib-arbortext-java", the saxon extensions a
18 matches
Mail list logo
