make "control" optional, move as much parameters as possible into the pom
make "control" optional, move as much parameters as possible into the pom
the intent is to have unified deb/rpm information source
and use pom.xml as single repository for this information
this probably isn't possible for all and everything - but I share the intend for the next major release.
Yea there is very specific stuff but being able to fallback on what can be found on the pom.xml for some things would indeed be nice. And btw it's not only for supporting several packaging format but it's also a lot easier to inherit things in maven pom (I have a lot of different deb packages and a lot of copy/paste right now).
indeed
great! thank you for considering this.
I would second this, having the control file generated by maven would allow for much easier versioning.
This sounds like a great idea. I am currently using jdeb for packaging at work and this would simplify our build and packaging process significantly.
I've created a new milestone for the 2.x release. Let's assign the issue an track them like that.
The description and the url in the pom are now used by default in the control file.
The other mandatory fields left to initialize from the pom are:
Package: defaults to the artifactId?Version: project version + tweaks for snapshotsSection: defaults tojavaPriority: defaults tooptionalArchitecture: defaults toallMaintainer: defaults to the first developer found in the pom? Or theuser.namesystem property?Depends: defaults todefault-jre | java<n>-runtime, where n = the Java version derived from the compile target.
We'll also need additional configuration elements to overrides these values.
(sorry guys not fully awake)
Actually, it would be interesting to drive the control file optional for the Ant task too and I find the parser very picky. I had to tinker my control file for several days to make it work: http://sourceforge.net/p/tuer/code/925/tree//pre_beta/build.xml?diff=516fd70b271846340a79c27a:924