Hi Damien,
On Sun, Jan 18, 2009 at 11:14 PM, Damien Raude-Morvan <[email protected]> wrote: > - 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 ? you are right. I will fix that. It is more work for me but it is worth. > - 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 ? It is automatically defined by the build tool (maven-debian-helper). I'll try to make the text more verbose. > Why not use something like this : "[2.0,3.0)" ? Because Maven will pick a somewhat random version in that case. But our properties will point to the exact version installed on the system. I think that is important. Cheers, Torsten _______________________________________________ pkg-java-maintainers mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
