Aldous, I am interested in a Debian version of the "forehead" Java library, and I noticed your ITP for it (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344112). I was just wondering how it was going, and if you had an idea of when it is likely to be completed? Or, if you no longer have the time to complete the packaging, I'd be happy to help. Sorry to bother you. Thanks, Paul

... in some way of the software we package and distribute, we cannot distribute a software for Debian that could install non free software in all ~'s. We have to discuss about that. Maybe creating a "debian-restricted" mode or something like that and the user would have to add something in his/her envvars or in the pom file to override the restriction. Ideas and comments welcome,

...> fetch packages. How would this work? Having a build-dep will not install anything in the Maven repository, as I guess Maven would expect, and certainly not binary tarballs. I think the idea of Trygve was symlinks or something. We can also have a script to add every debian-java package installed in a xml file so that maven could know what is installed and where (and which version...

... packages. How would this work? Having a build-dep will not install anything in the Maven repository, as I guess Maven would expect, and certainly not binary tarballs. I think the idea of Trygve was symlinks or something. We can also have a script to add every debian-java package installed in a xml file so that maven could know what is installed and where (and which ...

...>>>> fetch packages. How would this work? Having a build-dep will not install anything in the Maven repository, as I guess Maven would expect, and certainly not binary tarballs. I think the idea of Trygve was symlinks or something. We can also have a script to add every debian-java package installed in a xml file so that maven could know what is installed and where (and ...

...>>>>fetch packages. How would this work? Having a build-dep will not install anything in the Maven repository, as I guess Maven would expect, and certainly not binary tarballs. I think the idea of Trygve was symlinks or something. We can also have a script to add every debian-java package installed in a xml file so that maven could know what is installed and where ...

... a start. You can get the summary here: http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=maven2-packaging;users=pkg-java-maintainers@lists.alioth.debian.org Thanks, thats a good idea. Cheers, Michael -- .''`. | Michael Koch <konqueror@gmx.de> : :' : | Free Java Developer <http://www.classpath.org> `. `' | `- | 1024D/BAC5 4B28 D436 95E6 F2E0 BD11 5923 A008 2763 ...

....MF file Maven cn download the software the users wants it to install and put it into some repository. Upstream Maven does this currently by putting everything into the users home directory. My idea would be to have a system-wide repository where Maven can put its downloaded software. This directory will be user writable. Perhaps only to users in some special group. That should work out ...

... archive space for one version. Now consider this software to be in Debian 10 times. You get the idea. With Maven we will give the user the opportunity to be more uptodate with Java software ... in a seamless way. You cant package the applications without packaging the needed libraries. One of main ideas behind Debian is that everything can be put onto a CD/DVD and be done. You don't...

... created the second time: JFileChooser jfc= New JFileChooser(); This line of code is in a function, and when the function is called the second time, the application hangs and does not execute the lines of code under this line. The hang causes the browser to hang too. This effekt is in IE7 und Firefox 2. Any idea, what I could do to fix this? Please help, Regards, Hans