Re: [Fwd: Re: [architecture] Re: JPackages and ObjectWeb]

2004-02-02 Thread Jan Schulz
Hallo David, * David Walluck wrote: >>So if 1.5 is API compatible to 1.4, the the jar should still be >>name-1.4.jar (or at least a symlink :) But if 1.5.3 breaks something, >>it should get name-1.5.3.jar. >But libraries have the concept of software version, and then totally >apart from this is t

Re: [Fwd: Re: [architecture] Re: JPackages and ObjectWeb]

2004-02-02 Thread Jan Schulz
Hallo Nicolas, * Nicolas Mailhot wrote: >jsse.libs=$(build-classpath jsse) >javamail.libs=$(build-classpath javamail) >test.libs=$(build-classpath junit xerces-j2 httpunit) ^^^ I thought you don't have such a script. Thats exactly what I propose to use, but on runtime. And

Re: [Fwd: Re: [architecture] Re: JPackages and ObjectWeb]

2004-02-02 Thread Kenneth Pronovici
> > >For #8: > > >We should add that all jars should have a manifest (but without > > >Class-Path). Ant can autogenerate a manifest, or does, I forget? > > > > BTW: I never yet touched Manifests, what are they actually for? :) > > Manifests are a child of java applets. Sun needed a place to put

Re: [Fwd: Re: [architecture] Re: JPackages and ObjectWeb]

2004-02-02 Thread Nicolas Mailhot
Le lun, 02/02/2004 à 23:28 +0100, Jan Schulz a écrit : > Hallo David, > > * David Walluck wrote: > >``Make specifying the build classpath easy using either command line > >switches of property files (and document it).'' > >currently we use `export CLASSPATH', how does this fit in? Note that a >

Results of your commands

2004-02-02 Thread List Manager
> Warning: This message has had one or more attachments removed Command not understood: ignoring end of message. No command found in message -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [Fwd: Re: [architecture] Re: JPackages and ObjectWeb]

2004-02-02 Thread David Walluck
Jan Schulz wrote: IMO, they should go with the same strategy as the normal libaries: Changing names only when a API changed. So if 1.5 is API compatible to 1.4, the the jar should still be name-1.4.jar (or at least a symlink :) But if 1.5.3 breaks something, it should get name-1.5.3.jar. This is a

Re: [Fwd: Re: [architecture] Re: JPackages and ObjectWeb]

2004-02-02 Thread Jan Schulz
Hallo Jan, * Jan Schulz wrote: >>``Make specifying the build classpath easy using either command line >>switches of property files (and document it).'' >>currently we use `export CLASSPATH', how does this fit in? Note that a >>build.xml using only properties cannot easily be used with our >>`bui

Re: [Fwd: Re: [architecture] Re: JPackages and ObjectWeb]

2004-02-02 Thread Jan Schulz
Hallo David, * David Walluck wrote: >``Make specifying the build classpath easy using either command line >switches of property files (and document it).'' >currently we use `export CLASSPATH', how does this fit in? Note that a >build.xml using only properties cannot easily be used with our >`bui

Re: [Fwd: Re: [architecture] Re: JPackages and ObjectWeb]

2004-02-02 Thread David Walluck
Eric Bruneton wrote: I think so. I'm trying to update the ASM project to take these guidelines into account (I attach the corresponding source package). I think it follows items 1, 2, 3 (see build.properties), 4, 5, 6 (see build.properties again), 7, 8, 9, 10, 11, 14, 16 & 17. Tell me if something

Automatic response to your mail

2004-02-02 Thread TIE
The experimentalcinema.com e-mail address that you recently sent email to, is now used only to send occasional out-going email and is rarely, if at all, checked for incoming. Therefore, please send and/or resend your email(s) to Catherine Smith, Director of Public Relations, with any public

Maven and Unix

2004-02-02 Thread Daniel Bonniot
It would be great if maven was part of the solution, and wouldn't turn into a road block. It has great potential in both directions, as far as I can see it. I completely agree with this. While I understand the griefs expressed in this thread about Maven not playing nicely with the OS, I also th

Re: upstream guidelines for easy packaging (was: JPackages and ObjectWeb)

2004-02-02 Thread Nicolas Mailhot
Le lun, 02/02/2004 Ã 12:22 +0100, [EMAIL PROTECTED] a Ãcrit : > Hallo, > > Nicolas Mailhot wrote: > > I've added a few more points that should answer your questions. Please > > tell me if it is so (and other JPP/Debian/Gentoo... folks please check > > if it also represents your packaging processes

upstream guidelines for easy packaging (was: JPackages and ObjectWeb)

2004-02-02 Thread debian
Hallo, Nicolas Mailhot wrote: > I've added a few more points that should answer your questions. Please > tell me if it is so (and other JPP/Debian/Gentoo... folks please check > if it also represents your packaging processes) >From some discussion on normal debian packages, I would say, that ups

Re: [Fwd: Re: [architecture] Re: JPackages and ObjectWeb]

2004-02-02 Thread Nicolas Mailhot
Le lun, 02/02/2004 Ã 10:26 +0100, Eric Bruneton a Ãcrit : > Nicolas Mailhot wrote: > > I'm done with this. The result is available at: > > > > http://java.debian.net/index.php/What%20is%20required%20from%20upst > >ream > Thanks for these guidelines. I have a few questions: [...] I've added a f

Re: [Fwd: Re: [architecture] Re: JPackages and ObjectWeb]

2004-02-02 Thread Eric Bruneton
Nicolas Mailhot wrote: > Le dim, 01/02/2004 à 16:24 +0100, Nicolas Mailhot a écrit : > > Le dim, 01/02/2004 à 16:15 +0100, Jan Schulz a écrit : > > > Hallo Nicolas, > > > > > > * Nicolas Mailhot wrote: > > > >face the same problems and wish for more or less the same > > > > things : > > > > > > [..