Hi Matthew,
Matthew Johnson schrieb:
It's unclear to me what they want to be configured at runtime by
changing the classpath.
I'll ask them and report back.
I talked about the classpath issue with the jpackage guys. We didn't go
into detailed arguments as it is a minor policy issue that do
On Mon, June 30, 2008 14:26, Matthew Johnson wrote:
>
> Sufficiently clever build systems should propagate the build CLASSPATH
> to the manifest automatically anyway.
I'm a bit confused by this. Doesn't that assume that the build and runtime
classpaths are identical?
--
To UNSUBSCRIBE, email
Thanks Matt for taking the time to look through my package. Your
comments helped a lot. I've updated the package:
deb http://debian.richcole.org.s3.amazonaws.com unstable/
deb-src http://debian.richcole.org.s3.amazonaws.com unstable/
in line with your suggestions. I had originally mistakenl
Hi Matthew,
Matthew Johnson schrieb:
Ah, hmm, I think it only looks in /usr/share/java, since this was a tool
for Debian, and thats where all our jars are stored.
I forgot to mention that I modified your script to look into "my"
directory. This is a very simple modification and makes your scr
Hi Matthew,
Matthew Johnson schrieb:
It's unclear to me what they want to be configured at runtime by
changing the classpath.
I'll ask them and report back.
Wrapper scripts without classpath manifest items also result in
large classpaths containing items you shouldn't have to know about (you
On Mon Jun 30 10:01, Florian Grandel wrote:
> Hi Java developers,
>
>> One problem that I haven't solved so far is how to get the classpath
>> into the MANIFEST file as was proposed earlier in this thread.
>
> As you may have remarked from my earlier posts I am working with the
> JPackage guys rec
Hi Java developers,
One problem that I haven't solved so far is how to get the classpath
into the MANIFEST file as was proposed earlier in this thread.
As you may have remarked from my earlier posts I am working with the
JPackage guys recently. Their "recommendation to Java developers"
argum
On Sun Jun 29 23:25, Richard Cole wrote:
>
> I'd be pleased if you (the collective of debian java packagers) would
> look over what I've done and provide comments, hints and suggestions.
Well, some general observations just looking at the packaging. There is
a built jar in the source, which isn't
To better understand debian packaging java libraries I used javahelper
to package joda-time which is a pretty nice date-time library for
java.
I've put my effort at:
deb http://debian.richcole.org.s3.amazonaws.com unstable/
deb-src http://debian.richcole.org.s3.amazonaws.com unstable/
You
On Sun, Jun 29, 2008 at 11:56:52PM +0100, Matthew Johnson wrote:
> On Sun Jun 29 15:04, Richard Cole wrote:
> > I've started looking into javahelper, very nice package.
> >
> > I tried to package a small library (jarjar) following the javahelper
> > tutorial but I got stuck. I was trying to build
On Sun Jun 29 15:04, Richard Cole wrote:
> I've started looking into javahelper, very nice package.
>
> I tried to package a small library (jarjar) following the javahelper
> tutorial but I got stuck. I was trying to build with sun-j2sdk1.6. I
by which you presumably mean sun-java6-jdk, if you ha
I've started looking into javahelper, very nice package.
I tried to package a small library (jarjar) following the javahelper
tutorial but I got stuck. I was trying to build with sun-j2sdk1.6. I
tried calling jh_build from debian/rules:
jh_build jarjar.jar src/main
jh_build then tried to call
Richard Cole wrote:
So I'm still wondering how the packaging of java packages in Debian works.
Lets say that I do some more research on Hibernate and discover it
really cannot run without Log4j because classes in Hibernate directly
reference Log4j. [1] Then I submit a bug report and the dependen
On Tue Jun 24 09:39, Richard Cole wrote:
> So I'm still wondering how the packaging of java packages in Debian works.
Hi, I am very interested in improving the state of Java packaging in
Debian. In fact, I have written a set of tools to help with it which do
some of the things you described below.
So I'm still wondering how the packaging of java packages in Debian works.
Lets say that I do some more research on Hibernate and discover it
really cannot run without Log4j because classes in Hibernate directly
reference Log4j. [1] Then I submit a bug report and the dependency
gets added. Where's
Hi Richard,
Right now I see that hibernate is available as a library package that
has put jars in /usr/share/java. If I depend on these jars and write a
unit test I discover that there are more dependencies, I need some of
the apache commons libraries and the log4j library, but I can't see
those
Richard wrote:
> This is a bit of a newby question.
>
> What I'm wondering is whether one can use the debian package system as
> a kind of build system. Let me illustrate with an example, say for
> example I want to write an app and package it with debian and this app
> uses Hibernate, then I woul
17 matches
Mail list logo
