Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Torsten Curdt
    @tcurdt
    But it looks like it just needs to put a few files in the right place. No need to for a daemon or something, right?
    Maybe give it a try and ask if you run into troubles, @sjha2048
    Sahil Jha
    @sjha2048
    I have to say as compared to mh_make jdeb is a life saver, yes there's no need of a daemon.
    Sure @tcurdt I'll let you know
    Thanks again
    Sahil Jha
    @sjha2048
    once again I am here with my silly questions
    today I tried the example and was successful in the building the .deb package
    and also tried to understand arthas architecture
    here are my questions
    1) arthas has many modules can I package them individually
    2)if I decide to package them individually then where should I add the plugin, the pom file inside the module or in the global one and also the deb folder
    3) if not then will I have to add plugin in every pom file or just the main one same question with the control file.
    @tcurdt I will be grateful to you if you address these.
    Sahil Jha
    @sjha2048
    It was a mere jdk error
    Fixed it
    Torsten Curdt
    @tcurdt
    @sjha2048 yay for building the example deb :)
    Packaging a modular system is a bit more tricky as - as you must maintain the metadata for every module to create the deb.
    Sahil Jha
    @sjha2048
    so what do you suggest?
    Torsten Curdt
    @tcurdt
    At this stage I don't see any other way to have control files for each individual module.
    Sahil Jha
    @sjha2048
    just like the example deb, now I am trying to package https://github.com/alibaba/arthas/tree/master/demo for starting.
    Torsten Curdt
    @tcurdt
    Whether adding a jdeb in the parent pom is an option I am actually not quite sure.
    Might be worth a try if the config is the same for all.
    Sahil Jha
    @sjha2048
    apart from modification to pom file and addition of deb folder nothing else is required right?
    Torsten Curdt
    @tcurdt
    Nope - that should be it.
    Sahil Jha
    @sjha2048
    my mentor mentioned this

    After mvn package, there is a zip file: packaging/target/arthas-3.1.2-SNAPSHOT-bin.zip

    Arthas has 'arthas.home`, by default, it try to find arthas jars like arthas-core.jar under the working directory.
    If not found, try to find jars from ~/.arthas directory.

    So I think the rpm zip contains arthas-3.1.2-SNAPSHOT-bin.zip , After install, the user can execute as.sh to start arthas.

    I don't think its relevant
    also from issues section I found Jsign
    Torsten Curdt
    @tcurdt
    Hm - this sounds very specific to Arthas. Not sure I can help there.
    Sahil Jha
    @sjha2048
    https://github.com/ebourg/jsign/tree/master/jsign
    here I wasn't able to understand how jdeb was used
    Torsten Curdt
    @tcurdt
    jdeb really goes the standard maven way of attaching the deb as additional build artifact
    Sahil Jha
    @sjha2048
    separate module for packaging thru jdeb, is that possible?
    Torsten Curdt
    @tcurdt
    @sjha2048 TBH I am not entirely sure. It's been a while I used multi module maven builds :)
    Sahil Jha
    @sjha2048
    Then I'll just stick to having a control file in each module
    thanks for the help
    Torsten Curdt
    @tcurdt
    As for jsign I guess you have to come up with concrete questions. @ebourg is the author is also a jdeb committer.
    Well, can't hurt to try if it's many modules of the exact same setup. But having a control file per module doesn't sound so bad.
    Sahil Jha
    @sjha2048
    got it, I'll build up my question first then ask.
    Torsten Curdt
    @tcurdt
    I'd just make sure to have versions numbers as properties or the jdeb declaration in a single pom. So upgrading version will be simpler.
    Sahil Jha
    @sjha2048
    I was trying the "control file for each module " approach and I was successful building deb for them but few of them contain two jar files as output
    it's like xyz.jar and xyz-dependencies.jar, only xyz.jar is included in the package but I want to include both of them, do I need to modify the config in pom file for jdeb?
    needed help
    Sahil Jha
    @sjha2048
    you can see it here
    https://github.com/sjha2048/arthas_packaging_demo/tree/master/arthas-boot/boot/target
    Torsten Curdt
    @tcurdt
    @sjha2048 Hm. If the artifacts are attached jdeb should create producers for all of them.
    https://github.com/tcurdt/jdeb/blob/master/src/main/java/org/vafer/jdeb/maven/DebMojo.java#L506
    But you can of course also just define the required producers yourself explicitly.
    Also make sure you have read https://github.com/tcurdt/jdeb/blob/master/docs/maven.md
    Ah ... maybe the maven-assembly-plugin does not make the artifacts available
    So as long as the order of execution allows just define the producers manually.
    Sahil Jha
    @sjha2048
    in the pom file right?
    I mean I have to explicitly mention it in the src tag to include it
    am I getting it right?
    Sahil Jha
    @sjha2048
    Figured it out, sorry for asking such a silly question.
    Sahil Jha
    @sjha2048
    What are the techniques for optimization with jdeb or maven in general so that I can reduce the size of my package, what do you all suggest?
    Torsten Curdt
    @tcurdt
    @sjha2048 sorry, I somehow did not get a notification that someone was asking here.
    If you are talking "java" then there is the maven shade plugin that allows optimizing jars.
    ...but that's not related to jdeb at all.
    That said: deb's are getting compressed