Atomikos Forum

Confused by atomikos sources in distributions


I recently downloaded the latest Atomikos transactions essentials release from your maven repo. However, again I'm a bit confused by the source distributions.
The problem is that when debugging the MessageDrivenContainer, I found that the Eclipse debugger did not align with the jars.

At first sight, it looks like the license header is causing this. Maybe you add these after compilation?

Then I downloaded the complete distribution, and found to my dismay that the sources there are once again different from those in the maven repo. Apparently these are missing the revision changes.

Can you have a look at this?

Many thanks,
Erik-Berndt Scheper Send private email
Tuesday, March 02, 2010

Noted - thanks. Will have a thorough look for the next release or so.

Guy Pardon Send private email
Tuesday, March 02, 2010

I've retested the latest release and I see this issue has been improved. But unfortunately it's still not fixed with release 3.6.3 from the Maven repository.

I see that the revision info has been removed from the sources in the maven repo; at least for atomikos-util-3.6.3-sources.jar and transactions-jms-3.6.3-sources.jar.

But the compiled .class files (in atomikos-util-3.6.3.jar and transactions-jms-3.6.3.jar) (AKA 'dist jars') still don't match the source jars.
In every file I've tested there's an offset of 28 lines between the .class file and the .java file. This EXACTLY matches the size of the Apache 2 license header in the source files.

Therefore I now believe that the 'dist jars' have been compiled from .java files WITHOUT the Apache 2 header, and the 'source jars' have been built from jars WITH the Apache 2 header.

Does this make sense?
Erik-Berndt Scheper Send private email
Tuesday, March 16, 2010

Yes, this makes sense; it is what we currently do.
Guy Pardon Send private email
Saturday, March 20, 2010
Ok, thanks for the confirmation.
This does make debugging very difficult, because the source jars don't match the 'dist' jars.

Any chance you can fix this?
Erik-Berndt Scheper Send private email
Monday, March 22, 2010
Well, it is on our backlog but no the highest priority. Nevertheless we will consider this. The outcome will also depend on the legal implications.

Guy Pardon Send private email
Monday, March 22, 2010

Heres some workaround for the moment i am using to debug things:

Rebuild the sources and add this one to build.xml:

<target name="sources">
        <jar jarfile="${jars.destination.dir}/transactions-essentials-all-${build.version}-sources.jar" basedir="${sources.dir}">
            <fileset dir="${sources.dir}" includes="**/*.java" />

"ant sources" will build you the sources jar you can copy them along with the build binary jar to your custom / home maven repository.
Not a real solution to the problem but a nice workaround to get debugging work.
Torsten Krah Send private email
Wednesday, March 31, 2010

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics