Uploaded image for project: 'repository.jboss.org/nexus'
  1. repository.jboss.org/nexus
  2. NEXUS-100

org.wildfly.extras.creaper sync to Central

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • Great. Joel sent me an e-mail he identified the problem, and mentioned, that the sync needs to be done again. When I looked to Maven Central in the morning, it was not yet synced. I am closing the issue now.

      I'd like to enable Maven Central synchronization for the groupId org.wildfly.extras.creaper.

      But before we set that up, I'd like to ask for an advise: Creaper depends on EAP 6 artifacts from the Red Hat's Maven repo (http://maven.repository.redhat.com/techpreview/all). Is it OK for Central-synchronized artifacts to have such <repository> in the POM?

      If no, we'd probably be able to find a way around it, but I didn't want to spend too much time on it before I know that I have to.

      Also, Creaper artifacts are not GPG-signed. I think this is a requirement when going through Sonatype. Is it a requirement as well when synchronizing to Central from JBoss.org?

              dhladky@redhat.com David Hladky
              lthon@redhat.com Ladislav Thon
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: