Atomikos Forum

Hi,

I just noticed that 3.6.6 has appeared on the 'old' atomikos maven repository. However, I haven't read a notification on the atomikos blog or anywhere else.

Is there a changelog or release notes available with the bugs fixed etc?

Kind regards,
Erik-Berndt Scheper

Where is this Atomikos Maven repository?  I cannot find any Maven repository for Atomikos specifically.

In Maven central, they have Atomikos 3.6.4 (which is what we are currently using), but I am wondering if there is anything newer out there.

For what it's worth, I just downloaded Atomikos 3.7.0M4 and it has all the historical release notes, but it jumps from 3.5.9 to 3.7.0M2.  It is missing the release notes in between!  Help!

Fortunately it is just the release notes - we checked that already.

Between 3.6.x and now, we have been migrating to maven builds (from ant). As part of that, our maven repo is being phased out and no more builds should go there. It might be that 3.6.6 went there by accident during the migration process to maven.

Also, the 3.6.6 is meant for support subscribers, which is why there was no public announcement about it :-)

Before anybody asks:

our maven repo is being phased out in favor of the public maven repo (for community builds) and an Atomikos nexus instance (for support subscribers)...

Just to clarify my last post.

@Guy -- It looks like 3.6.4 is the latest version in Maven central.  Will you be putting any of the 3.7.0-M builds in there?  Or will you be waiting for an official release of 3.7.0?

Dave,

We've just been discussing this a few hours back, and thought that pushing to oss.sonatype.org was better for testing the 3.7.0Mx release publication process. What is your view on this?

Thanks

To me, it depends on what these "-Mx" release really are. 

Assume they are akin to release candidates, then I think publishing to oss.sonatype.org makes a lot of sense.  You could use a staging repository there for these releases and people like myself could proxy that repo from my own version of Nexus. (Today I do not proxy oss.sonatype.org).  Once you are satisfied with an RC, you'd migrate it over to the oss.sonatype.org release repository where they will be sync'd over to Maven central.  All very nice.

In this way you won't pollute Maven central with a ton of intermediate releases that people really shouldn't be using.  Appfuse has a lot of release in Maven central and I gotta believe its confusing for everyone:

http://repo1.maven.org/maven2/org/appfuse/appfuse-data/

If these "-Mx" release are officially sanctioned and production worthy versions of transaction-essentials then I'd probably skip oss.sonatype.org and go straight to Maven.

My 2 cents.

BTW-- Maven central has amped up their requirements lately.  See this:

https://docs.sonatype.org/display/Repository/Central+Sync+Requirements