Hi, I just uploaded new versions of maven-*-helper to experimental to fix a NullPointerException but I did not even test them. - Because it's to hard to test them.
maven-debian-helper can only be tested if it is installed because it has hard coded paths in it. I wanted to remove the hard codings, but I can't easily handle the case that maven is invoked as part of mh_make. mh_make invokes maven with the GenerateDebianFilesMojo and expects to find it in a jar somewhere in /u/s/maven-repo. The GenerateDebianFilesMojo needs maven only to do the Dependency Resolution and then generates the files under debian/. I want to try to do the same outside of a mojo. Only call maven to get the dependency list without a debian specific mojo and do the rest in some shell/perl/python code. There are also some mojos in debian-maven-plugin. What is their purpose? Who uses them? They look a lot like dead code or code that is trivial to do with some lines of shell script. Can those mojos be removed too? Regards, Thomas Koch, http://www.koch.ro -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
