Publish Maven Artifacts

[ghost]

Hi,

Could you please upload bitronix 3.0 to central maven repository.

Thanks

[marcus-nl]

I agree, a release of version 3 would be great.

[raupachz]

Any updates?

[lorban]

Unfortunately, the BTM team ran out of steam - we don't any enough time anymore to devote to the project. If someone is willing to volunteer taking over maintenance of the project, please drop me an email.

[liniu]

I'm waiting for bitronix 3.0 a long time.

[brettwooldridge]

Ludovic,

If you don't mind, I'm going to move the publication of artifacts from
Codehaus to Sonatype. Following this process:

http://central.sonatype.org/pages/ossrh-guide.html
(
http://central.sonatype.org/articles/2014/Feb/27/migrating-a-project-to-ossrh/
)

They have a human review process, but I don't anticipate any issues. I'll
let you know if there is anything I need. Once the approval is in, I'll
fix-up the pom for publication. Cool?

Regards,
Brett

On Thu, Apr 9, 2015 at 3:48 PM, liniu [email protected] wrote:

I'm waiting for bitronix 3.0 a long time.

—
Reply to this email directly or view it on GitHub
#37 (comment).

[lorban]

Sure, go ahead.

But if my memory serves, Stephane already got a "be.bitronix" group name
from Sonatype. Hopefully he'll chime-in pretty soon with more deails about
what's been done and what's left. He's very familiar with those processes
which explains why I've solely relied on him w.r.t new releases.

On Thu, Apr 9, 2015 at 9:40 AM, Brett Wooldridge [email protected]
wrote:

Ludovic,

If you don't mind, I'm going to move the publication of artifacts from
Codehaus to Sonatype. Following this process:

http://central.sonatype.org/pages/ossrh-guide.html
(

http://central.sonatype.org/articles/2014/Feb/27/migrating-a-project-to-ossrh/
)

They have a human review process, but I don't anticipate any issues. I'll
let you know if there is anything I need. Once the approval is in, I'll
fix-up the pom for publication. Cool?

Regards,
Brett

On Thu, Apr 9, 2015 at 3:48 PM, liniu [email protected] wrote:

I'm waiting for bitronix 3.0 a long time.

—
Reply to this email directly or view it on GitHub
#37 (comment).

—
Reply to this email directly or view it on GitHub
#37 (comment).

[lorban]

Hey guys.

I meant to release and asked if master was ok but I don't remember
receiving any answer. Sorry if I overlooked that.

I do have the publish rights on that namespace and we can add you Brett.
Just ask the sonatype guys and mention me. I can help over the week end as
well.

S.

On Thursday, April 9, 2015, Ludovic Orban [email protected] wrote:

Sure, go ahead.

But if my memory serves, Stephane already got a "be.bitronix" group name
from Sonatype. Hopefully he'll chime-in pretty soon with more deails about
what's been done and what's left. He's very familiar with those processes
which explains why I've solely relied on him w.r.t new releases.

On Thu, Apr 9, 2015 at 9:40 AM, Brett Wooldridge <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

Ludovic,

If you don't mind, I'm going to move the publication of artifacts from
Codehaus to Sonatype. Following this process:

http://central.sonatype.org/pages/ossrh-guide.html
(

http://central.sonatype.org/articles/2014/Feb/27/migrating-a-project-to-ossrh/
)

They have a human review process, but I don't anticipate any issues. I'll
let you know if there is anything I need. Once the approval is in, I'll
fix-up the pom for publication. Cool?

Regards,
Brett

On Thu, Apr 9, 2015 at 3:48 PM, liniu <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

I'm waiting for bitronix 3.0 a long time.

—
Reply to this email directly or view it on GitHub
#37 (comment).

—
Reply to this email directly or view it on GitHub
#37 (comment).

Sent from my phone

[brettwooldridge]

Stephane,

I think the master branch pom is not setup currently for sonatype. In
fact, I think my last commits of a month or so ago were to try to make it
publishable to codehaus. But I think that is the wrong direction to go
given that codehaus is shutting down, so you'll need to follow the sonatype
maven guide to setup btm for publication. I've got a couple of projects
that publish to sonatype, but they are pretty simple (single artifact),
compared to btm's various artifacts.

-Brett

On Thu, Apr 9, 2015 at 4:50 PM, lorban [email protected] wrote:

Hey guys.

I meant to release and asked if master was ok but I don't remember
receiving any answer. Sorry if I overlooked that.

I do have the publish rights on that namespace and we can add you Brett.
Just ask the sonatype guys and mention me. I can help over the week end as
well.

S.

On Thursday, April 9, 2015, Ludovic Orban [email protected] wrote:

Sure, go ahead.

But if my memory serves, Stephane already got a "be.bitronix" group name
from Sonatype. Hopefully he'll chime-in pretty soon with more deails
about
what's been done and what's left. He's very familiar with those processes
which explains why I've solely relied on him w.r.t new releases.

On Thu, Apr 9, 2015 at 9:40 AM, Brett Wooldridge <
[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

Ludovic,

If you don't mind, I'm going to move the publication of artifacts from
Codehaus to Sonatype. Following this process:

http://central.sonatype.org/pages/ossrh-guide.html
(

http://central.sonatype.org/articles/2014/Feb/27/migrating-a-project-to-ossrh/
)

They have a human review process, but I don't anticipate any issues.
I'll
let you know if there is anything I need. Once the approval is in, I'll
fix-up the pom for publication. Cool?

Regards,
Brett

On Thu, Apr 9, 2015 at 3:48 PM, liniu <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

I'm waiting for bitronix 3.0 a long time.

—
Reply to this email directly or view it on GitHub
#37 (comment).

—
Reply to this email directly or view it on GitHub
#37 (comment).

Sent from my phone

—
Reply to this email directly or view it on GitHub
#37 (comment).

[jitpack-io]

Btw, you can already install btm as a Maven dependency from:
https://jitpack.io/#bitronix/btm/1072c3042c

Using the commit id '1072c3042c' here but you could use a release tag as well.

[marcus-nl]

What is holding back the release of version 3 to Maven Central?

I see there is already a ticket on Sonatype registering the be.bitronix groupId (https://issues.sonatype.org/browse/OSSRH-7707). However, the declared groupId in the poms was recently changed back to org.codehaus.btm.

Therefore, either the org.codehaus.btm groupId needs to be registered at Sonatype, or the declared groupId must be changed back to be.bitronix. (I personally would be in favour of the last option, but more important is that a choice is made).

I've also created a PR configuring maven-gpg-plugin: #43

[lorban]

What is holding back the release of version 3? Lack of time.

[jacobbeasley]

Looks like Marcus got something out: https://mvnrepository.com/artifact/com.github.marcus-nl.btm

[marcus-nl]

Oh yes, that's right. I created a release a while back using the groupId "com.github.marcus-nl.btm" from what were the latest sources at that time. See https://github.com/marcus-nl/btm.

[lorban]

Would you guys want to take over the project?

[jacobbeasley]

I'm not in a position to, but I'm founding a tech startup that uses this (it is so much faster than Atomikos in my testing) and once we get off the ground and have a stable base of revenue coming in, I might look into having my tech startup put a little effort into taking over maintenance of the project. I'm just too heads-down right now building out our product right now.

In the meantime, could we update the readme to say com.github.marcus-nl.btm is the latest version for those who want to use 3.0.0?

Also, is the version that Marcus put out relatively stable?

[lorban]

I honestly have no idea how stable current master is or isn't. I believe it should be okay as @brettwooldridge is using on production AFAIK. I also don't know what version was built and released at the coordinates you mentioned but I've nevertheless updated the readme to include a link.

I haven't actively used or needed BTM for the last 6 or 7 years and never managed to find the time to maintain it in my spare time, so if anyone feels like taking over the mantle, I'd be very glad to pass it on.

[marcus-nl]

Thank you for the offer @lorban, but I started my own company last month, so I'm basically in the same boat as @jacobbeasley, with not a lot of time to spare :)

The release is only 4 commits behind the current master. Those commits seem to be exclusively documentation updates.

We've used that version for our Development and Test environments since it was made, and haven't encountered any errors. So it seems quite stable to me.