Hi,
how did you create the upstream tarball? I've created it manually and
uploaded the package.
Cheers,
Torsten
--
To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Torsten Werner wrote:
Hi,
how did you create the upstream tarball? I've created it manually and
uploaded the package.
Cheers,
Torsten
Hi
Thanks for the uploads; I created the tarball manually as well.
~Niels
signature.asc
Description: OpenPGP digital signature
Hi
I am (partly) reviving jetty5 for the sake of keeping eclipse in main. I
have reduced the tar.gz and removed (to eclipse) all irrelevant
binary-packages/jars.
Here is the changelog entry:
jetty5 (5.1.15+dfsg-1) unstable; urgency=low
* New upstream release.
* Renamed source package to
Hello,
Le samedi 06 février 2010 à 16:51 +0100, Niels Thykier a écrit :
Hi
I am (partly) reviving jetty5 for the sake of keeping eclipse in main. I
have reduced the tar.gz and removed (to eclipse) all irrelevant
binary-packages/jars.
Here is the changelog entry:
jetty5 (5.1.15+dfsg-1)
Hello,
Le samedi 06 février 2010 à 16:51 +0100, Niels Thykier a écrit :
Hi
I am (partly) reviving jetty5 for the sake of keeping eclipse in main. I
have reduced the tar.gz and removed (to eclipse) all irrelevant
binary-packages/jars.
Here is the changelog entry:
jetty5 (5.1.15+dfsg-1)
I would not have revived this (nor jasper/tomcat5.5) if I could have
made eclipse build without it. Particularly the team has already gotten
tomcat5.5 removed due to lack of interest/security issues with the
web-server. But to answer your question: It used to build two different
packages (jetty
6 matches
Mail list logo