Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish this MP 1.0 BOM #3

Open
kwsutter opened this issue Feb 24, 2017 · 11 comments
Open

Publish this MP 1.0 BOM #3

kwsutter opened this issue Feb 24, 2017 · 11 comments
Assignees

Comments

@kwsutter
Copy link
Member

Per our Google Hangout discussion on 02/21, David volunteered to get this initial pom.xml for MP 1.0 into the maven repo. We talked about following this process to get it published:
http://central.sonatype.org/pages/ossrh-guide.html

@kwsutter
Copy link
Member Author

Can we just publish the pom.xml to maven? Or, do we have to publish an empty jar file along with it? Empty meaning only to include the META-INF/maven/.. directories. Do we also need a pom.properties file? I'd like to keep this to a minimum delivery for 1.0.

I've experimented on my own system and I know I can install just the pom.xml into my local .m2 repo, but I don't know if that's sufficient for a real publish out to maven.

@struberg
Copy link
Member

Technically you can deploy a pure pom to maven.central without any problems.

@keilw
Copy link

keilw commented Mar 2, 2017

I think @dblevins requested to do so for the existing GroupId. You need to have approval by the SonaType system for a particular groupId, otherwise it won't work. Also someone (e.g. @dblevins or @kwsutter) should put a 1.0 tag here https://github.com/microprofile/microprofile-bom/releases to mark what's going into the Maven repos for 1.0 before the repository may join others at Eclipse.

@keilw
Copy link

keilw commented Mar 14, 2017

Has anything happened here?

@keilw
Copy link

keilw commented Mar 20, 2017

ANY POM nowadays needs to have a developers section. Take a Payara example

 <developers>
      <developer>
          <name>Payara Team</name>
          <email>info@payara.fish</email>
          <organization>Payara Foundation</organization>
          <organizationUrl>http://www.payara.fish</organizationUrl>
      </developer>
  </developers>

What's in there, frankly nobody cares at least not technically, so it could be "Microprofile.io" "Donald Duck" or Trump or whatever. So write what you prefer.

It goes as far as JCenter without that, if it's sufficient for 1.0, then fine for me, if Sonatype/MavenCentral was desired, then @dblevins shall do it as it was intended.

@keilw
Copy link

keilw commented Mar 20, 2017

@keilw
Copy link

keilw commented Mar 21, 2017

The POM as in master was succesfully deployed to JCenter: http://jcenter.bintray.com/io/microprofile/microprofile/1.0.0/

@kenfinnigan
Copy link
Member

I've created #6 to add necessary config for publishing to Sonatype, and by extension Maven Central

@keilw
Copy link

keilw commented Mar 21, 2017

Thanks. Cannot say if it was very urgent to do it for the 1.0 BOM but ideally it should work for the next version. And no later than before switching over to org.eclipse can somebody please also tag it 1.0.0 first?

@OndroMih
Copy link

OndroMih commented Jun 6, 2017

The BOM was published to maven central on 04-Apr-2017:
http://search.maven.org/#artifactdetails%7Cio.microprofile%7Cmicroprofile%7C1.0.0%7Cpom

@OndroMih
Copy link

OndroMih commented Jun 6, 2017

The 1.0.0 tag is also created, we can close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants