-
Notifications
You must be signed in to change notification settings - Fork 7
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
Comments
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. |
Technically you can deploy a pure pom to maven.central without any problems. |
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. |
Has anything happened here? |
ANY POM nowadays needs to have a developers section. Take a Payara example
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. |
This might help http://central.sonatype.org/pages/requirements.html |
The POM as in master was succesfully deployed to JCenter: http://jcenter.bintray.com/io/microprofile/microprofile/1.0.0/ |
I've created #6 to add necessary config for publishing to Sonatype, and by extension Maven Central |
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? |
The BOM was published to maven central on 04-Apr-2017: |
The 1.0.0 tag is also created, we can close this issue. |
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
The text was updated successfully, but these errors were encountered: