maven2-repository
  1. maven2-repository
  2. MAVEN2_REPOSITORY-113

Prepare a repository on maven.java.net for deploying EL 3.0 artifacts

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: migration-cleanup
    • Labels:
      None

      Description

      Project: http://java.net/projects/el-spec/

      Two artifacts need to be staged and release:

      group id: javax.el
      artifact id: javax.el-api
      scm:svn:https://svn.java.net/svn/el-spec~source-code/trunk/api

      group id: org.glassfish
      artifact id: javax.el
      scm:svn:https://svn.java.net/svn/el-spec~source-code/trunk

        Activity

        Hide
        jorlina added a comment -

        Repositories have already been prepared for both javax.el and org.glassfish. In order for you to be able to stage and deploy artifacts to those groupIds, you need be a dev/admin in the projects bound to those groupIds, specifically uel and glassfish. You will need to contact the administrators of those projects to help get you access.

        Show
        jorlina added a comment - Repositories have already been prepared for both javax.el and org.glassfish. In order for you to be able to stage and deploy artifacts to those groupIds, you need be a dev/admin in the projects bound to those groupIds, specifically uel and glassfish. You will need to contact the administrators of those projects to help get you access.
        Hide
        kchung added a comment -

        Don't know if this makes any difference, this is for the el-spec project, not for uel project, and I am the adminstrator for this project.

        The only difference between uel artifacts and el-spec artifacts is that for uel, the group id for the implementation is org.glassfish.web, whereas for el-spec, the corresponding group id is org.glassfish. The api artifacts is the same. In fact I was able to deploy the api to the maven repository, but when I tried deploying the impl artifacts, I got the following error. This led me to believe that the there is something wrong with the way the repo on maven.java.set was set up.

        [INFO] [deploy:deploy

        {execution: default-deploy}

        ]
        Uploading: https://maven.java.net/service/local/staging/deploy/maven2//org/glassfish/javax.el/3.0-b01/javax.el-3.0-b01.jar
        [INFO] ------------------------------------------------------------------------
        [ERROR] BUILD ERROR
        [INFO] ------------------------------------------------------------------------
        [INFO] Error deploying artifact: Failed to transfer file: https://maven.java.net/service/local/staging/deploy/maven2/org/glassfish/javax.el/3.0-b01/javax.el-3.0-b01.jar. Return code is: 400

        ANy idea why I am getting a 400?

        Show
        kchung added a comment - Don't know if this makes any difference, this is for the el-spec project, not for uel project, and I am the adminstrator for this project. The only difference between uel artifacts and el-spec artifacts is that for uel, the group id for the implementation is org.glassfish.web, whereas for el-spec, the corresponding group id is org.glassfish. The api artifacts is the same. In fact I was able to deploy the api to the maven repository, but when I tried deploying the impl artifacts, I got the following error. This led me to believe that the there is something wrong with the way the repo on maven.java.set was set up. [INFO] [deploy:deploy {execution: default-deploy} ] Uploading: https://maven.java.net/service/local/staging/deploy/maven2//org/glassfish/javax.el/3.0-b01/javax.el-3.0-b01.jar [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error deploying artifact: Failed to transfer file: https://maven.java.net/service/local/staging/deploy/maven2/org/glassfish/javax.el/3.0-b01/javax.el-3.0-b01.jar . Return code is: 400 ANy idea why I am getting a 400?
        Hide
        jorlina added a comment -

        I've tweaked the permissions. Can you try again now?

        Show
        jorlina added a comment - I've tweaked the permissions. Can you try again now?
        Hide
        kchung added a comment -

        Great! It seems to be working now. Thanks a lot for the help.

        Show
        kchung added a comment - Great! It seems to be working now. Thanks a lot for the help.
        Hide
        kchung added a comment -

        Now I am having another problem.

        I am following the instructions in http://aseng-wiki.us.oracle.com/asengwiki/display/GlassFish/Migrating+Maven+deployment+to+maven.java.net

        When I tried prepare for stagging, I issue a
        "mvn -Prelease release:prepare", I got the error

        [INFO] [gpg:sign

        {execution: sign-artifacts}

        ]
        gpg: WARNING: unsafe ownership on configuration file `/home/kichung/.gnupg/gpg.conf'
        gpg: WARNING: using insecure memory!
        gpg: please see http://www.gnupg.org/faq.html for more information
        gpg: no default secret key: bad passphrase
        gpg: signing failed: bad passphrase
        [INFO] ------------------------------------------------------------------------
        [ERROR] BUILD ERROR
        [INFO] ------------------------------------------------------------------------
        [INFO] Exit code: 2

        According to step 7, the passphrase should be glassfish. Has this been changed?

        Show
        kchung added a comment - Now I am having another problem. I am following the instructions in http://aseng-wiki.us.oracle.com/asengwiki/display/GlassFish/Migrating+Maven+deployment+to+maven.java.net When I tried prepare for stagging, I issue a "mvn -Prelease release:prepare", I got the error [INFO] [gpg:sign {execution: sign-artifacts} ] gpg: WARNING: unsafe ownership on configuration file `/home/kichung/.gnupg/gpg.conf' gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information gpg: no default secret key: bad passphrase gpg: signing failed: bad passphrase [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Exit code: 2 According to step 7, the passphrase should be glassfish. Has this been changed?
        Show
        Romain Grécourt added a comment - does this help ? https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven#HowToGeneratePGPSignaturesWithMaven-GenerateaKeyPair
        Hide
        kchung added a comment -

        I've gone through that also. I a way, the instructions here tell users how to generate key paire, which is fine. The other instruction tell the user to just use the key generated for java_re, which I followed. This is the case that giving too much options ends up confusing the users.

        I think my problem is I have more than one keys in the keyring, and I don't know how to tell the plugin to use the one for java_re.

        I'll try deleting the other key pairs and see if that helps.

        Show
        kchung added a comment - I've gone through that also. I a way, the instructions here tell users how to generate key paire, which is fine. The other instruction tell the user to just use the key generated for java_re, which I followed. This is the case that giving too much options ends up confusing the users. I think my problem is I have more than one keys in the keyring, and I don't know how to tell the plugin to use the one for java_re. I'll try deleting the other key pairs and see if that helps.
        Hide
        kchung added a comment -

        Deleting other key pairs works. I am sure there must be a way to specify a particular key for signing the artifact, but I don't know what it is.

        Show
        kchung added a comment - Deleting other key pairs works. I am sure there must be a way to specify a particular key for signing the artifact, but I don't know what it is.

          People

          • Assignee:
            jorlina
            Reporter:
            kchung
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: