On Saturday 17 January 2009 15:24:26 Torsten Werner wrote: > Hi, Hi Torsten,
> I have already used maven-debian-helper on more than 2 dozen packages > on my local system (including jetty 6.1.9). Information about > maven-debian-helper can be found at > <http://wiki.debian.org/Java/MavenBuilder> but the specification > should be applicable to packages that are not using Maven for > building, too. The major ideas of the spec are: > - install the artifacts into a Maven repository at /usr/share/maven-repo/ > - create unversioned symlinks to binary jars in /usr/share/java/ > - replace hard coded version numbers in pom.xml files by properties > - use the <systemPath> element as a temporary workaround in the pom.xml Some various comments : - Repository layout Your proposal seems okay for me. It mimic Maven central repo structure which seams reasonable and maven-user-friendly. - Usage of system scope dependencies I'm really reluctant to use system scope + systemPath to replace missing POM descriptors, especially when we'll need to replace some "test" scope dependencies. Those system scope dependencies will end up into $REPO/.../$myProject-$version.pom and increase transitive dependencies of $myProject. Maybe we should clearly remove test dependencies when they need missing POM ? - Version properties Your spec. isn't really clear about patching of POM to remove/replace version information. What do you intend to do with "<version>${org.apache.maven.maven- core.version}</version>" ? Where is org.apache.maven.maven-core.version property is defined ? Why not use something like this : "[2.0,3.0)" ? Thank for your work on Maven Debian packaging. [1] http://maven.apache.org/guides/introduction/introduction-to-dependency- mechanism.html#Dependency_Scope -- Damien Raude-Morvan / www.drazzib.com
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ pkg-java-maintainers mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
