Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    123Haynes
    @123Haynes
    looks like it can be automated to me
    "This execution will deploy to OSSRH and release to the Central Repository in one go, thanks to the usage of the Nexus Staging Maven Plugin with autoReleaseAfterClose set to true"
    Sidi Mohamed EL AATIFI
    @elaatifi
    Exactly
    Still GPG for signing needs to be exported (to be kept safe)
    right now the release process is a mess
    123Haynes
    @123Haynes
    yes. In gitlab ci you'd use secret variables for that.
    Sidi Mohamed EL AATIFI
    @elaatifi
    Cool
    Once we have something like that it will be easier to have at least few people to make releases and release notes
    123Haynes
    @123Haynes
    you can define any env variable you want outside of your repository and it'll get injected during the ci process. So in your maven config you'd have <gpg.passphrase>${env.the_pass_phrase}</gpg.passphrase>
    Sidi Mohamed EL AATIFI
    @elaatifi
    Yes but the keys should be generated before
    123Haynes
    @123Haynes
    yes. of course.
    Sidi Mohamed EL AATIFI
    @elaatifi
    on GitLab is it based on containers ?
    123Haynes
    @123Haynes
    yes.
    you specify any docker image that provieds what you need for a job
    Sidi Mohamed EL AATIFI
    @elaatifi
    on this case should install gpg => generate keys => export keys to public server => maven release plugin
    123Haynes
    @123Haynes
    but you'd only need to generate keys once right?
    Sidi Mohamed EL AATIFI
    @elaatifi
    Yes
    we can regenerate them not an issue, just need to be published (can be done automatically)
    GitLab CI jobs can have parameters on launch ?
    123Haynes
    @123Haynes
    yes
    Sidi Mohamed EL AATIFI
    @elaatifi
    Ok cool so we can have version of release and next snapshot
    123Haynes
    @123Haynes
    yes, of course.
    Sidi Mohamed EL AATIFI
    @elaatifi
    GitLab can do the job :)
    I need to look more closely at GitLab
    (for my education :))
    123Haynes
    @123Haynes
    basically gitlab will execute arbitrary bash scripts inside the docker container you specify for a job. So as long as you can execute it via cli, it'll work :)
    Sidi Mohamed EL AATIFI
    @elaatifi
    I have question we need to bring our own workers (machine to host containers) or provided by GitLab
    123Haynes
    @123Haynes
    you get 2000 build minutes per month for free on gitlabs runners. If you need more, you'd either need to bring your own runner, or pay for a higher tier
    Sidi Mohamed EL AATIFI
    @elaatifi
    OK thanks !
    Sidi Mohamed EL AATIFI
    @elaatifi
    The regression on Issue46 it has been caused by this commit orika-mapper/orika@7a0635f
    still looking for exactly which line change
    Sidi Mohamed EL AATIFI
    @elaatifi
    git bisect run mvn verify -Dtest=ma.glasnost.orika.test.community.Issue46TestCase
    123Haynes
    @123Haynes
    hmm weird... this should be only checkstyle changes.... If in doubt, please revert my pr.
    Sidi Mohamed EL AATIFI
    @elaatifi
    I already fixed it, the order of statements in some method has been changed
    123Haynes
    @123Haynes
    @elaatifi can you enable this for the orika repo? https://snyk.io/docs/github/
    Free vulnerability scans are always great :)
    Sidi Mohamed EL AATIFI
    @elaatifi
    Thanks done
    123Haynes
    @123Haynes
    @elaatifi regarding gitlab ci: I just finished setting up a fork of the orika-spring-boot-starter because the original author didn't react. I setup gitlab ci to automatically release a new version to maven central when you create a tag on the repository. No manual steps required at all now. :) Might be interesting for you as well:
    https://gitlab.com/haynes/orika-spring-boot-starter/blob/master/.gitlab-ci.yml
    123Haynes
    @123Haynes
    also every change to the master branch triggers a snapshot release :)
    Sidi Mohamed EL AATIFI
    @elaatifi
    Oh thanks this is neat will do the same :)
    123Haynes
    @123Haynes
    @elaatifi what do you think about adding https://github.com/marketplace/renovate ?
    It automatically creates a PR when a dependency update is available.
    I have it enabled for my projects and it always keeps my projects up to date :smile:
    See haynes/orika-spring-boot-starter!6 for the onboarding pr and
    haynes/orika-spring-boot-starter!8 how an automated update PR looks.
    joaonunoasa
    @joaonunoasa

    Hello all,

    I was wondering if there is any reporting tool for orika when trying to map a source ma.glasnost.orika.metadata.Type into a destination ma.glasnost.orika.metadata.Type.
    What I have done so far was to obtain an instance of ma.glasnost.orika.metadata.ClassMapBuilder by calling the "classMap" method in ma.glasnost.orika.MapperFactory.
    Having that, I was then able to obtain an instance of ma.glasnost.orika.metadata.ClassMap by calling the "toClassMap" method in ma.glasnost.orika.metadata.ClassMapBuilder.
    Finally, I obtained the set of ma.glasnost.orika.metadata.FieldMap by calling the "getFieldsMapping" in ma.glasnost.orika.metadata.ClassMap.
    This last set provides information about all the successful mappings performed.
    I have also managed to access all the mapping fields candidates for any given ma.glasnost.orika.metadata.Type by calling the ma.glasnost.orika.property.PropertyResolver.
    Having the list of all the fields and having the list of all the mapped fields, is it then possible to obtain the list of fields that we were not able to map.

    My question if there is any reporting tool provided by orika, that avoids writing all this code when trying to understand which fields we were not able to map and why.

    Thanks,
    Joao

    Niranjan
    @nnanda2016
    Hello Orika team, which version of Orika is JDK 11 compatible?
    Oleksandr Porunov
    @porunov
    @elaatifi Hello. Is there any ETA for the next orika release? I would like to use the functionality which was merged lately.
    RAJKUMAR NATARAJAN
    @rajcspsg
    Hi all
    I'm getting this error
    this is simple test from sample provided in the orika documentation
    ghilainm
    @ghilainm
    Hi guys, I have some issue excluding a field from mapping in orika. I am using byDefault + exclude and the getter of the excluded property is still invoked any idea? (orika-mapper/orika#348)