Marcus Better writes: > Matthias Klose wrote: > > Marcus Better writes: > >> instance we ship a lot of packages that build with Maven, but since we > >> don't have Maven in Debian, we use the included, pre-generated, Ant build > >> file instead. What should we do about those? > > > > if these packages are in main, file a RC report and remove them, at > > least from testing. > > That's a bit drastic, no? Those packages are no different from packages with > pre-generated configure scripts and the like, and those are accepted in > main, IIRC.
you can recreate them using packages in main. you can't do this with the maven jars. > > Then package maven and maven2. > > "Good idea, why don't you try it?", to quote someone on -project > recently. :-) > > Actually I'm planning to have a go at those, but they are rather > complicated. > > > which packages are these? > > AFAICT, all of Jakarta Commons, dom4j, jaxen, and probably a lot more. Plus looked at libcommons-logging-java, jaxen, dom4j, which do not use maven for the build. so which sources are actually including maven jars? > upcoming Tomcat 6. that's easy. package it for non-free or don't package it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]