...- at package *build* time (e.g. when you run debuild). I think using the information at package *creation* time is a good idea; I listed a few ideas in my original email. The automatic tools would create a skeleton packaging which could be amended by the packager. But I'm not so sure about dynamically ...

... to "debian/.m2/repository", and call maven's bootstrap shell script. (this process is described in http://maven.apache.org/guides/development/guide-building-m2.html) It might be a good idea to create a "company" pom for Debian that contains all settings and so on that apply to all Debian packages that are build with Maven. Otherwise a debian profile in a settings.xml could achieve ...

... a Debian package, we will have to look at this sort of thing. To run maven in offline mode there is a -o flag. Thanks - that's one we will need. It might be a good idea to create a "company" pom for Debian that contains all settings and so on that apply to all Debian packages that are build with Maven. Otherwise a debian profile in a settings.xml could achieve similar ...

... leverage the project's meta-data and start working on integration Maven into the build process until it is properly into main and those files can be generated build-time. I don't like the idea of generating those files at build time. But maybe I don't understand what you mean. Anyway, tools used to generate and build debian package are in main so if we want to include maven calls in...

...> project's meta-data and start working on integration Maven into the build process until it is properly into main and those files can be generated build-time. I don't like the idea of generating those files at build time. But maybe I don't understand what you mean. Sorry to be unclear. I meant at the time when you are first assembling the package from the upstream source. ...

...the project's meta-data and start working on integration Maven into the build process until it is properly into main and those files can be generated build-time. I don't like the idea of generating those files at build time. But maybe I don't understand what you mean. I think you understood me correctly. There is nothing wrong with generated files, there are already lots of ...

Suddenly I get the infamous "java.lang.Object cannot be resolved" when building on amd64. Any ideas? I'm not using any chroots or anything. ~$ /usr/lib/jvm/java-gcj/bin/javac Test.java ---------- 1. ERROR in Test.java (at line 1) public class Test ^ The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files ~$ dpkg -l java-gcj...

...: Cannot locate class java.lang.Object referenced in class org.fontbox.afm.AFMParser ... tony Marcus Better wrote: Suddenly I get the infamous "java.lang.Object cannot be resolved" when building on amd64. Any ideas? I'm not using any chroots or anything. ~$ /usr/lib/jvm/java-gcj/bin/javac Test.java ---------- 1. ERROR in Test.java (at line 1) public class ...

On Thu, May 31, 2007 at 04:20:50PM +0200, Marcus Better wrote: Suddenly I get the infamous "java.lang.Object cannot be resolved" when building on amd64. Any ideas? I'm not using any chroots or anything. ~$ /usr/lib/jvm/java-gcj/bin/javac Test.java ---------- 1. ERROR in Test.java (at line 1) public class Test ^ The type java.lang.Object cannot be ...

... este mensaje. Recuerde de hacer esto en forma CORRECTA , LIMPIA Y HONESTAMENTE y funcionará con toda seguridad. Solamente tiene que ser honesto.Recuerde, HONESTIDAD ES EL MEJOR METODO. No necesitas hacer trucos con la idea básica de hacer dinero en esto! **Dicho sea de paso, si Ud. defrauda a las personas poniendo mensajes con su nombre y no envía ningún dinero a los demás en esa lista,...