Atomikos Forum |
|
Hi,
I noticed that syncing with the central maven repo now works. At least, I did find release 3.6.4 there (on repo1.maven.org). Unfortunately, the new parent pom makes atomikos-util invalid (and probably others as well), because it now depends on itself via the parent pom (transactions-essentials-all). atomikos-util-3.6.4.pom contains: <parent> <groupId>com.atomikos</groupId> <artifactId>transactions-essentials-all</artifactId> <version>3.6.4</version> </parent> But transactions-essentials-all-3.6.4.pom contains: <dependency> <groupId>com.atomikos</groupId> <artifactId>atomikos-util</artifactId> <version>3.6.4</version> </dependency>
As I suspected, the POMS of other modules are invalid as well.
It would be better to have a separate parent pom, with its own version number (since parent poms usually don't change). See for example revision 14 of the parent POM for the apache commons project: http://repo1.maven.org/maven2/org/apache/commons/commons-parent/14/commons-parent-14.pom Regards, Erik-Berndt
So essentially, this would lead to the following structure:
A new parent POM (with groupId=com.atomikos, artifactId=transactions-essentials-parent, version=1) where all shared third party dependencies are declared (such as the servlet api, jta api, connector api, etc). All modules should then depend on this parent POM. And the optional transaction-essentials-all POM should depend on the parent, and a series of modules. |