ICEpdf
  1. ICEpdf
  2. PDF-989

Release ICEpdf release jars to central maven repository

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 6.1, 6.1.1, 6.4
    • Fix Version/s: 6.1.2, 6.1.3
    • Component/s: Release
    • Labels:
      None
    • Environment:
      maven

      Description

      The ICEfaces and ICEmobile jars are already available on maven central repo. The releases maven repo on our own servers is not. To allow users to use maven in their builds for ICEpdf, previous as well as future releases should be made available in an indexed (maven central) repo.

      steps to follow to get jars into central maven repo:-
      https://maven.apache.org/guides/mini/guide-central-repository-upload.html

        Activity

        Hide
        Ken Fyten added a comment -

        I've applied on sonatype for the org.icepdf domain under this JIRA: https://issues.sonatype.org/browse/OSSRH-23188.

        Will take up to a couple of days to get approval.

        Show
        Ken Fyten added a comment - I've applied on sonatype for the org.icepdf domain under this JIRA: https://issues.sonatype.org/browse/OSSRH-23188 . Will take up to a couple of days to get approval.
        Hide
        Judy Guglielmin added a comment - - edited

        rev 48965. has the following:-
        The poms in the maven2 repo now get filtered with the version and product id's found in the top level build.properties.
        so..
        BEFORE you start....
        must use /maven2 folder ant script to "get-maven". This puts the correct jar in the /lib folder and on the classpath.

        step 1) modify the version number in build.properties to appropriate version of open source product
        step 2) modify maven2/build.xml to set the "snapshot.repo" to test the top level ant script target of "maven.deploy"...will put this property in other build.properties at some point if this is useful.
        step 3) run the top level ant script icepdf/build.xml with target maven.deploy and this will deploy to local specified "snapshot.repo".
        step 4) need to ensure that settings.xml has gpg key as well as ossrh-server-id specified id (currently used "sonatype-nexus-staging" id in your settings.xml as per http://www.icesoft.org/wiki/display/facesDev/Maven+Release+Procedures
        step 5) run the top level ant script icepdf/build.xml with target stage.nexus.

        Show
        Judy Guglielmin added a comment - - edited rev 48965. has the following:- The poms in the maven2 repo now get filtered with the version and product id's found in the top level build.properties. so.. BEFORE you start.... must use /maven2 folder ant script to "get-maven". This puts the correct jar in the /lib folder and on the classpath. step 1) modify the version number in build.properties to appropriate version of open source product step 2) modify maven2/build.xml to set the "snapshot.repo" to test the top level ant script target of "maven.deploy"...will put this property in other build.properties at some point if this is useful. step 3) run the top level ant script icepdf/build.xml with target maven.deploy and this will deploy to local specified "snapshot.repo". step 4) need to ensure that settings.xml has gpg key as well as ossrh-server-id specified id (currently used "sonatype-nexus-staging" id in your settings.xml as per http://www.icesoft.org/wiki/display/facesDev/Maven+Release+Procedures step 5) run the top level ant script icepdf/build.xml with target stage.nexus.
        Hide
        Ken Fyten added a comment -

        Having issue running the 'ant maven.deploy' and 'ant nexus.deploy' targets on Jenkins because currently in order for them to work you must first run "ant get-maven" from the maven2 dir. This step needs to be integrated into these builds automagically.

        Show
        Ken Fyten added a comment - Having issue running the 'ant maven.deploy' and 'ant nexus.deploy' targets on Jenkins because currently in order for them to work you must first run "ant get-maven" from the maven2 dir. This step needs to be integrated into these builds automagically.
        Hide
        Judy Guglielmin added a comment -

        rev 48990 has sub-ant task now in root level to "get-maven" jar

        Show
        Judy Guglielmin added a comment - rev 48990 has sub-ant task now in root level to "get-maven" jar
        Hide
        Ken Fyten added a comment -

        One more issue is that the viewer-ri.pom doesn't get it's icepdf.jar dependency version string automatically updated:

        <dependency>
        <groupId>org.icepdf.os</groupId>
        <artifactId>icepdf-core</artifactId>
        <version>X.X.X</version>
        </dependency>

        Show
        Ken Fyten added a comment - One more issue is that the viewer-ri.pom doesn't get it's icepdf.jar dependency version string automatically updated: <dependency> <groupId>org.icepdf.os</groupId> <artifactId>icepdf-core</artifactId> <version>X.X.X</version> </dependency>
        Hide
        Ken Fyten added a comment -

        Inaugural attempt to release this to sonatype nexus public maven repo has failed due to an invalid pom file:

        Event: Failed: POM Validation
        Wednesday, June 29, 2016 13:34:13 MDT (GMT-0600)
        typeId pom-staging
        failureMessage Invalid POM: /org/icepdf/os/icepdf-core/6.1.2/icepdf-core-6.1.2.pom: Developer information missing
        failureMessage Invalid POM: /org/icepdf/os/icepdf-viewer/6.1.2/icepdf-viewer-6.1.2.pom: Developer information missing

        Show
        Ken Fyten added a comment - Inaugural attempt to release this to sonatype nexus public maven repo has failed due to an invalid pom file: Event: Failed: POM Validation Wednesday, June 29, 2016 13:34:13 MDT (GMT-0600) typeId pom-staging failureMessage Invalid POM: /org/icepdf/os/icepdf-core/6.1.2/icepdf-core-6.1.2.pom: Developer information missing failureMessage Invalid POM: /org/icepdf/os/icepdf-viewer/6.1.2/icepdf-viewer-6.1.2.pom: Developer information missing
        Hide
        Ken Fyten added a comment -

        Resolved via adding Developers section to the pom files.

        Show
        Ken Fyten added a comment - Resolved via adding Developers section to the pom files.
        Hide
        Ken Fyten added a comment -
        Show
        Ken Fyten added a comment - ICEpdf 6.1.2 is now available http://search.maven.org/#search%7Cga%7C1%7Corg.icepdf
        Hide
        Judy Guglielmin added a comment -

        need to correct jai_core artifact in maven pom (mistakenly was called jai-core)

        Show
        Judy Guglielmin added a comment - need to correct jai_core artifact in maven pom (mistakenly was called jai-core)
        Hide
        Judy Guglielmin added a comment -

        rev 49149 has resolved this issue.

        Show
        Judy Guglielmin added a comment - rev 49149 has resolved this issue.
        Hide
        Judy Guglielmin added a comment -

        up to you Ken to republish this on maven repo.

        Show
        Judy Guglielmin added a comment - up to you Ken to republish this on maven repo.
        Hide
        Ken Fyten added a comment -

        I attempted to republish but it hasn't shown up in the staging area on sonatype nexus yet. Possible that we are not allowed to resubmit the same release once it's been published. I've opened a Nexus JIRA for this, will see if they respond or the staged release shows up by Tuesday.

        https://issues.sonatype.org/browse/MVNCENTRAL-1233

        Show
        Ken Fyten added a comment - I attempted to republish but it hasn't shown up in the staging area on sonatype nexus yet. Possible that we are not allowed to resubmit the same release once it's been published. I've opened a Nexus JIRA for this, will see if they respond or the staged release shows up by Tuesday. https://issues.sonatype.org/browse/MVNCENTRAL-1233
        Hide
        Ken Fyten added a comment -

        Okay, the only way to correct the pom once it's been released is with a subsequent release. So targeting the upcoming ICEpdf 6.1.3 release to include the corrected pom file.

        Show
        Ken Fyten added a comment - Okay, the only way to correct the pom once it's been released is with a subsequent release. So targeting the upcoming ICEpdf 6.1.3 release to include the corrected pom file.
        Hide
        Patrick Corless added a comment -

        Marking as fixed.

        Show
        Patrick Corless added a comment - Marking as fixed.
        Hide
        Ken Fyten added a comment -

        Re-opened.

        Show
        Ken Fyten added a comment - Re-opened.
        Hide
        Ken Fyten added a comment -

        Resolved.

        The ICEpdf 6.1.3 release has been approved for distribution on the sonatype maven repository.

        Show
        Ken Fyten added a comment - Resolved. The ICEpdf 6.1.3 release has been approved for distribution on the sonatype maven repository.

          People

          • Assignee:
            Ken Fyten
            Reporter:
            Judy Guglielmin
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: