Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make "control" optional, move as much parameters as possible into the pom #99

Open
carrot-garden opened this issue Feb 7, 2013 · 10 comments
Milestone

Comments

@carrot-garden
Copy link

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

@tcurdt
Copy link
Owner

tcurdt commented Feb 11, 2013

this probably isn't possible for all and everything - but I share the intend for the next major release.

@tmortagne
Copy link
Collaborator

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).

@tcurdt
Copy link
Owner

tcurdt commented Feb 11, 2013

indeed

@carrot-garden
Copy link
Author

great! thank you for considering this.

@kamorin
Copy link

kamorin commented Feb 20, 2013

I would second this, having the control file generated by maven would allow for much easier versioning.

@leourbina
Copy link

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.

@tcurdt
Copy link
Owner

tcurdt commented Feb 20, 2013

I've created a new milestone for the 2.x release. Let's assign the issue an track them like that.

@ebourg
Copy link
Collaborator

ebourg commented Apr 23, 2013

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 snapshots
  • Section: defaults to java
  • Priority : defaults to optional
  • Architecture : defaults to all
  • Maintainer: defaults to the first developer found in the pom? Or the user.name system property?
  • Depends : defaults to default-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.

@tmortagne tmortagne reopened this Apr 30, 2013
@tmortagne
Copy link
Collaborator

(sorry guys not fully awake)

@ghost
Copy link

ghost commented Oct 9, 2014

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants