So we had got configuration in which billing project references old billing-api artifact. We replaced old value in parent's pom.xml and in sections of both modules. We had an aggregator project ( billing-parent) with two modules ( billing-api, billing): :billing-parent In our case the error appeared because of the incorrect groupId renaming while some of the projects in multi-module Maven configuration references to others. I tend to think that this happened cause I had B checked out in my local workspace. I came up to this solution after reading answer from ZuillĮDIT: One more thing here to note that if I didn't had B project checked out in Local environment then this issue might not have occurred for me. You will need to clean-install complete B. Here important point was if b4 is in your workspace do not only install b4. And this worked! a2 module got compiled, installed, (packaged later) succesfully. After this I ran "mvn -U clean install" for my parent project which is A. As B is the parent, clean install command ran for all modules including b4 and it ran successfully. Only thing is there was b4's name for sure in logs.Īfter trying for many solutions for many hours, I ran "mvn -U clean install" from console in my B's project directoty (i.e. These errors were also not very user friendly. I ran "package" on a2's pom.xml and BAM!! errors n errors for a2 module. I also ran pom.xml of module b4 with targets like clean, package etc.Īfter some time when I finishedd my coding I needed to create a JAR of my module a2. I needed to check the source code of b4 for some purpose and as I already had B checked out on my local eclipse I updated it from SVN and checked out module b4. Eclipse downloaded the reuqired artifact from repo and I could import the classes in it. I included the dependancy to my module's POM i.e. B/ĭeveloper of b4 have deployed this b4 module as an artifact in our org's repository. I came to know that there is a good common functionality (b4) developed in B and I needed to use it.
and Parent projects A, B have their own pom.xml as per standard maven rules of parent and child)īoth projects are checked out on my local eclipse (from SVN). Now there is another project in our org B/ Which appears to be correct to me - the POM doesn't report any errors either when it is viewed in Eclipse.Ĭan some one tell me what I am missing here or doing wrong? I have reindexed my repository in Eclipse also. I am able to build :test-data-utils without issue, I can see the entry it makes in the. The common.test-data-utils jar is created by a separate project and shared between this and another project (the other project doesn't build either, but that is down to another problem). When I try to build my project from the terminal I get this error: Failed to read artifact descriptor for :test-data-utils:jar:0.3b-SNAPSHOT: Could not find artifact :merchandising:pom:0.3b-SNAPSHOT I am hoping someone can help me with a problem I am struggling with.
0 kommentar(er)
