Details

    • Type: New Project New Project
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Labels:
      None

      Description

      SnakeYAML is a YAML parser and emitter for Java.

      nexus id - py4fun

        Activity

        Hide
        Juven Xu added a comment -

        do you own the domain org.yaml ? if not, please use groupId org.yaml.snakeyaml or com.googlecode.snakeyaml

        Show
        Juven Xu added a comment - do you own the domain org.yaml ? if not, please use groupId org.yaml.snakeyaml or com.googlecode.snakeyaml
        Hide
        Juven Xu added a comment -

        btw, the bundle attached is not signed, please sign them if you want to sync them to central

        Show
        Juven Xu added a comment - btw, the bundle attached is not signed, please sign them if you want to sync them to central
        Hide
        Andrey Somov added a comment -

        1) I got the permission from the domain owner to use 'org.yaml' as the group name.

        http://sourceforge.net/mailarchive/forum.php?thread_name=9eb4914f0912011629r629675f3lf7c589f693bdb8fb%40mail.gmail.com&forum_name=yaml-core

        2) signed bundle can be downloaded

        http://code.google.com/p/snakeyaml/downloads/list
        PGP key here: http://code.google.com/p/snakeyaml/

        3) General comment: the way how the sync to central is implemented is far too complex. It is 10 times overkill for an open source project. I have already spent quite some time reading the documentation and fighting with PGP, but I have not moved anywhere yet.

        Show
        Andrey Somov added a comment - 1) I got the permission from the domain owner to use 'org.yaml' as the group name. http://sourceforge.net/mailarchive/forum.php?thread_name=9eb4914f0912011629r629675f3lf7c589f693bdb8fb%40mail.gmail.com&forum_name=yaml-core 2) signed bundle can be downloaded http://code.google.com/p/snakeyaml/downloads/list PGP key here: http://code.google.com/p/snakeyaml/ 3) General comment: the way how the sync to central is implemented is far too complex. It is 10 times overkill for an open source project. I have already spent quite some time reading the documentation and fighting with PGP, but I have not moved anywhere yet.
        Hide
        David Bernard added a comment - - edited

        Andrey,

        like I email you. I think it will be simpler if you deploy directly into sonatype repositories (snapshot, staging, release) and when everything will be ok to ask for central sync.

        I list bellow instructions to deploy to sonatype (I used, but adapted to you (you only need to set password, passphrase) :

        modify your $HOME/.m2/settings to include :

        <?xml version="1.0" encoding="UTF-8"?>
        <settings>
        ...
          <servers>
            <server>
              <id>oss.sonatype.org-releases</id>
              <username>py4fun</username>
              <password>xxxx</password>
            </server>
            <server>
              <id>oss.sonatype.org-snapshots</id>
              <username>py4fun</username>
              <password>xxxx</password>
            </server>
        ...
          </servers>
        ...
          <profiles>
            <profile>
              <id>gpginfo</id>
              <properties>
                <gpg.keyname>22415277</gpg.keyname>
                <gpg.passphrase>xxxx</gpg.passphrase>
              </properties>
            </profile>
        ...
          </profiles>
          <activeProfiles>
        ...  
            <activeProfile>gpginfo</activeProfile>
          </activeProfiles>
        </settings>
        

        modify the pom.xml by adding

          <profiles>
            <profile>
              <id>release</id>
              <activation>
                <property>
                  <name>performRelease</name>
                  <value>true</value>
                </property>
              </activation>
              <build>
                <plugins>
                  <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-gpg-plugin</artifactId>
                    <version>1.0-alpha-4</version>
                    <executions>
                      <execution>
                        <id>sign-artifacts</id>
                        <phase>verify</phase>
                        <goals>
                          <goal>sign</goal>
                        </goals>
                      </execution>
                    </executions>
                  </plugin>
                </plugins>
              </build>
              <distributionManagement>
                <repository>
                  <id>oss.sonatype.org-releases</id>
                  <name>OSSRH Release Repository</name>
                  <url>http://oss.sonatype.org/service/local/staging/deploy/maven2</url>
                </repository>
                <snapshotRepository>
                  <id>oss.sonatype.org-snapshots</id>
                  <name>OSSRH Snapshot Repository</name>
                  <url>http://oss.sonatype.org/content/repositories/googlecode-snapshots</url>
                  <uniqueVersion>false</uniqueVersion>
                </snapshotRepository>
              </distributionManagement>
            </profile>
          </profiles>
        

        then run

          
          mvn deploy -Prelease
        

        (should be enabled if you use "mvn release:prepare" and "mvn release:perform")

        I thinks you could try to modify pom.xml of 1.6 (from the zip archive) and run the command when you will have a repository oss.sonatype.org
        (I think, you will have http://oss.sonatype.org/content/repositories/googlecode-snapshots and http://oss.sonatype.org/content/repositories/googlecode-releases)

        when promotion from staging to release will be done, you could ask sync to central.

        If you need help to tunning the deployement, my nexus id is davidb but I don't know if several people could deploy (with different pgp signature)

        /davidB

        Show
        David Bernard added a comment - - edited Andrey, like I email you. I think it will be simpler if you deploy directly into sonatype repositories (snapshot, staging, release) and when everything will be ok to ask for central sync. I list bellow instructions to deploy to sonatype (I used, but adapted to you (you only need to set password, passphrase) : modify your $HOME/.m2/settings to include : <?xml version="1.0" encoding="UTF-8"?> <settings> ... <servers> <server> <id>oss.sonatype.org-releases</id> <username>py4fun</username> <password>xxxx</password> </server> <server> <id>oss.sonatype.org-snapshots</id> <username>py4fun</username> <password>xxxx</password> </server> ... </servers> ... <profiles> <profile> <id>gpginfo</id> <properties> <gpg.keyname>22415277</gpg.keyname> <gpg.passphrase>xxxx</gpg.passphrase> </properties> </profile> ... </profiles> <activeProfiles> ... <activeProfile>gpginfo</activeProfile> </activeProfiles> </settings> modify the pom.xml by adding <profiles> <profile> <id>release</id> <activation> <property> <name>performRelease</name> <value>true</value> </property> </activation> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-gpg-plugin</artifactId> <version>1.0-alpha-4</version> <executions> <execution> <id>sign-artifacts</id> <phase>verify</phase> <goals> <goal>sign</goal> </goals> </execution> </executions> </plugin> </plugins> </build> <distributionManagement> <repository> <id>oss.sonatype.org-releases</id> <name>OSSRH Release Repository</name> <url>http://oss.sonatype.org/service/local/staging/deploy/maven2</url> </repository> <snapshotRepository> <id>oss.sonatype.org-snapshots</id> <name>OSSRH Snapshot Repository</name> <url>http://oss.sonatype.org/content/repositories/googlecode-snapshots</url> <uniqueVersion>false</uniqueVersion> </snapshotRepository> </distributionManagement> </profile> </profiles> then run mvn deploy -Prelease (should be enabled if you use " mvn release:prepare " and " mvn release:perform ") I thinks you could try to modify pom.xml of 1.6 (from the zip archive) and run the command when you will have a repository oss.sonatype.org (I think, you will have http://oss.sonatype.org/content/repositories/googlecode-snapshots and http://oss.sonatype.org/content/repositories/googlecode-releases ) when promotion from staging to release will be done, you could ask sync to central. If you need help to tunning the deployement, my nexus id is davidb but I don't know if several people could deploy (with different pgp signature) /davidB
        Hide
        Juven Xu added a comment -

        Configuration has been prepared, now you can:

        Show
        Juven Xu added a comment - Configuration has been prepared, now you can: Deploy snapshot artifacts into repository http://oss.sonatype.org/content/repositories/snapshots Deploy release artifacts into the staging repository http://oss.sonatype.org/service/local/staging/deploy/maven2 Promote staged artifacts into repository 'Releases' Download snapshot and release artifacts from group http://oss.sonatype.org/content/groups/public Download snapshot, release and staged artifacts from staging group http://oss.sonatype.org/content/groups/staging
        Hide
        Juven Xu added a comment -

        1) I got the permission from the domain owner to use 'org.yaml' as the group name.

        http://sourceforge.net/mailarchive/forum.php?thread_name=9eb4914f0912011629r629675f3lf7c589f693bdb8fb%40mail.gmail.com&forum_name=yaml-core

        cool, repositories are prepared for you!

        2) signed bundle can be downloaded

        http://code.google.com/p/snakeyaml/downloads/list
        PGP key here: http://code.google.com/p/snakeyaml/

        I think you didn't get the point, we are not asking to sign the bundle, we are asking to sign files in the bundle.
        Now, you can try deploying bundle yourself, go to http://oss.sonatype.org, selete 'staging upload' in the left, for 'Upload Mode:', choose 'Artifact Bundle', Nexus will validate your bundle automatically. If all goes well, go to the 'Staging' page, close and promote your staging repository.

        3) General comment: the way how the sync to central is implemented is far too complex. It is 10 times overkill for an open source project. I have already spent quite some time reading the documentation and fighting with PGP, but I have not moved anywhere yet.

        I admit the whole process is complex to especially Maven newbie, but to build a healthy ecosystem, we have to require those information in POM, and PGP, which is actually another tech. There is no other easy to do this, that's why I heavily documented it at http://nexus.sonatype.org/oss-repository-hosting.html.

        Anyway, I will always help you finish set up this, once it's done, next time would be much easier.

        Show
        Juven Xu added a comment - 1) I got the permission from the domain owner to use 'org.yaml' as the group name. http://sourceforge.net/mailarchive/forum.php?thread_name=9eb4914f0912011629r629675f3lf7c589f693bdb8fb%40mail.gmail.com&forum_name=yaml-core cool, repositories are prepared for you! 2) signed bundle can be downloaded http://code.google.com/p/snakeyaml/downloads/list PGP key here: http://code.google.com/p/snakeyaml/ I think you didn't get the point, we are not asking to sign the bundle, we are asking to sign files in the bundle. Now, you can try deploying bundle yourself, go to http://oss.sonatype.org , selete 'staging upload' in the left, for 'Upload Mode:', choose 'Artifact Bundle', Nexus will validate your bundle automatically. If all goes well, go to the 'Staging' page, close and promote your staging repository. 3) General comment: the way how the sync to central is implemented is far too complex. It is 10 times overkill for an open source project. I have already spent quite some time reading the documentation and fighting with PGP, but I have not moved anywhere yet. I admit the whole process is complex to especially Maven newbie, but to build a healthy ecosystem, we have to require those information in POM, and PGP, which is actually another tech. There is no other easy to do this, that's why I heavily documented it at http://nexus.sonatype.org/oss-repository-hosting.html . Anyway, I will always help you finish set up this, once it's done, next time would be much easier.
        Hide
        Andrey Somov added a comment - - edited

        Thank you. Finally I managed to deploy the artifacts and to promote them to the repository 'Releases'.

        Can you please sync them (version 1.5 and version 1.6) to central ?

        P.S. I must say I understand now the process. It looks reasonable. I cannot say I was lost because of lack of documentation. I am afraid I was confused because it is very different with how I normally deploy my artifacts.

        Show
        Andrey Somov added a comment - - edited Thank you. Finally I managed to deploy the artifacts and to promote them to the repository 'Releases'. Can you please sync them (version 1.5 and version 1.6) to central ? P.S. I must say I understand now the process. It looks reasonable. I cannot say I was lost because of lack of documentation. I am afraid I was confused because it is very different with how I normally deploy my artifacts.
        Hide
        Juven Xu added a comment -

        central sync up is activated, it runs hourly

        thanks for using our service

        Show
        Juven Xu added a comment - central sync up is activated, it runs hourly thanks for using our service

          People

          • Assignee:
            Juven Xu
            Reporter:
            Andrey Somov
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 0.25h
              0.25h