Le mar, 03/02/2004 Ã 17:34 -0500, David Walluck a Ãcrit :
> Jan Schulz wrote:
>
> > Hm, seems that the only real difference is, that in your case the JVM
> >
> >will pickup some jars because they ar ein a special dir and in my
> >case, it wll be picked up because -bootclasspath is used. One other
Hallo David,
First of all: I've written up my version of this all on
http://java.debian.net/index.php/CombinedClasspathAndRuntimeSolution
Please comment, I'm not sure, how well I've written that up...
* David Walluck wrote:
>Jan Schulz wrote:
>So far, this is the only options we use:
>$JAVACMD
Jan Schulz wrote:
Hm, seems that the only real difference is, that in your case the JVM
will pickup some jars because they ar ein a special dir and in my
case, it wll be picked up because -bootclasspath is used. One other
So far, this is the only options we use:
$JAVACMD $FLAGS -classpath $CL
Hallo David,
* David Walluck wrote:
>$ build-classpath jdbc-stdext ant bsh xerces-j2
[...]
>You can see how jdbc is a jvm extension so it exists as a symlink is
>/usr/lib/jvm-exports. Every other jar (normal jar) gets picked up in
>/usr/share/java a bit easier.
Hm, seems that the only real diff
David Walluck wrote:
> 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,
> > 1
Jan Schulz wrote:
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 u
Kenneth Pronovici <[EMAIL PROTECTED]> writes:
>> > >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 a
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
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
> > >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
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
>
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
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
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
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
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
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 :
> > >
> > > [..
David Walluck wrote:
Nicolas Mailhot wrote:
I'm done with this. The result is available at:
It says final version is forthcoming. I was afraid to make edits just
yet. And I would like to see each point numbered and lettered so that
they can be easily refered to. Like we could say, ``this is
Nicolas Mailhot wrote:
>I agree. Also it may need to be reorganised a bit (one part concerning
>deps, another concerning archives, whatever). This is just a feeling btw
>- I have no clear organisation in mind, if you can do it don't wait for
>my approval.
>
I don't have a clear idea.
An easy algo
Le dim, 01/02/2004 à 12:51 -0500, David Walluck a écrit :
> Nicolas Mailhot wrote:
>
> >I'm done with this. The result is available at:
> It says final version is forthcoming. I was afraid to make edits just
> yet.
Please do so now - I may fix a typo or two, but I finished my writup for
today.
Nicolas Mailhot wrote:
I'm done with this. The result is available at:
It says final version is forthcoming. I was afraid to make edits just
yet. And I would like to see each point numbered and lettered so that
they can be easily refered to. Like we could say, ``this is a violation
of IIa''
Le dim, 01/02/2004 à 18:25 +0100, Jan Schulz a écrit :
> Hallo Nicolas,
>
> * Nicolas Mailhot wrote:
> >I'm done with this. The result is available at:
> >I'm rather proud of myself since I merged the full JPP document, my
> >mail, added a few ideas and corrected (a bit) the result.
>
> That text
Hallo Nicolas,
* Nicolas Mailhot wrote:
>I'm done with this. The result is available at:
>I'm rather proud of myself since I merged the full JPP document, my
>mail, added a few ideas and corrected (a bit) the result.
That text is great! Thanks a lot for specifying the whole thing.
Hoepfully some
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 :
> > [...]
> >
> > Would you mind adding that to the wiki
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 :
> [...]
>
> Would you mind adding that to the wiki? Seems like a nice thing to
> have there :)
Ok
(I still owe you a clarific
Hallo Nicolas,
* Nicolas Mailhot wrote:
>face the same problems and wish for more or less the same things :
[...]
Would you mind adding that to the wiki? Seems like a nice thing to
have there :)
Jan
--
Jan Schulz [EMAIL PROTECTED]
"Wer nicht fragt, bleibt dumm."
--
T
Le ven, 30/01/2004 à 09:38 -0500, David Walluck a écrit :
> Eric Bruneton wrote:
> >if you have precise instructions (or tutorials, or example projects)
> >on how to organize Java projects, how to manage their dependencies,
> >and how to build them, so that they can easily be packaged in rpm or
27 matches
Mail list logo
