- This topic has 5 replies, 2 voices, and was last updated 14 years ago by
.
-
Posts
-
After the code is generated by scaffolding I get the below errors. Please note that the “Atomikos 3.6.1 Libraries” are in the project and include transactions-essentials-all.jar and jta-1.1.jar which can be seen in the Package Explorer as well as in the “Project Properties Libraries” tab.
Description Resource Path Location Type
Missing artifact com.atomikos:transactions-essentials-all:pom:3.6.1:compile pom.xml /PracManService line 1 Maven Problem
Class ‘com.atomikos.icatch.jta.UserTransactionManager’ not found PracManService-generated-dao-context.xml /PracManService/src/main/resources line 46 Spring Beans Problem
Class ‘com.atomikos.icatch.jta.UserTransactionImp’ not found PracManService-generated-dao-context.xml /PracManService/src/main/resources line 52 Spring Beans ProblemThere is a known issue with m2eclipse (the maven tooling included in MyEclipse), https://issues.sonatype.org/browse/MNGECLIPSE-1975 which prevents the downloading of the correct version of the atomikos jar file. You can work around this by updating your local maven repo via the command line, downloading and manually adding the atomikos 3.6.1 libraries to your local repo, or switching to the latest atomikos libraries (keeping in mind we haven’t tested with them).
If you need further help with any of these options, please let us know.
Regards,
HeflinThe link you provided has an error “The project you are trying to view does not exist.”
@hhogan wrote:
There is a known issue with m2eclipse (the maven tooling included in MyEclipse), https://issues.sonatype.org/browse/MNGECLIPSE-1975, which prevents the downloading of the correct version of the atomikos jar file. You can work around this by updating your local maven repo via the command line, downloading and manually adding the atomikos 3.6.1 libraries to your local repo, or switching to the latest atomikos libraries (keeping in mind we haven’t tested with them).
If you need further help with any of these options, please let us know.
Regards,
HeflinYou are correct. The link was picking up the comma. It is now fixed, and I’ve pasted it below for clarity.
Why is a released GA product having this problem? Shouldn’t all users have this problem with the installed jar files/product?
To answer your second question first, no. Users who do not use maven will not experience the error at all. Experienced maven users, who already have an extensive local repository (which will already has the atomikos library version in question included) will never have this issue. Maven users who do not depend on the IDE supplied tooling will never see this error. New MyEclipse for Spring users who build maven based projects will see this error though it is not our tooling that is at fault, we are happy to provide assistance.
I have previously provided you with several possible workarounds, which we will be more than willing to help you with. Please let us know which path you’d like to proceed with, and we will readily provide guidance.
As to you first question, no software hits GA without bugs, and we try very hard to minimize the number that make it out the door, as I am sure you would as well. In this particular case I would suggest that you direct your questions to the forums at sonatype.org, When they update their code, it will be incorporated into ours.
Regards,
Heflin
