Jahia in English > When Creating a...

0 (0 Good)
0 (0 Bad)

When Creating a new Module (jahia 7.2.2.0) dependencies not resolved

by  julio@newneuronalpathways.com »  2018/03/08 17:05

Hi, when creating a new module I see a maven build trying to download some artifacts that are not found:

  • JAHIA 7.2.2.0
  • Maven 3.5.0
  • JDK 8

[ERROR] Failed to execute goal on project mymodule11: Could not resolve dependencies for project org.jahia.modules:mymodule11:bundle:1.0-SNAPSHOT: Failed to collect dependencies at org.jahia.server:jahia-impl:jar:7.2.2.2-SNAPSHOT -> org.apache.tika:tika-parsers:jar:1.14 -> com.drewnoakes:metadata-extractor:jar:2.9.1 -> com.adobe.xmp:xmpcore:jar:5.1.2: Failed to read artifact descriptor for com.adobe.xmp:xmpcore:jar:5.1.2: Failure to find com.adobe.granite:parent:pom:60 in http://repo.adobe.com/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of Adobe Central has elapsed or updates are forced -> [Help 1]

  (julio@newneuronalpathways.com)

Number of messages  3
Registration date
0 (0 Good)
0 (0 Bad)

Re: When Creating a new Module (jahia 7.2.2.0) dependencies not resolved

by  shyrkov »  2018/03/13 12:49

Hello julio,

could you, please, provide some more details on how you've created the module? Was it using the DX Studio or using the mvn archetype:generate from command line?

Which DX version are you using? I am wondering, why in the module build output you have the reference to the latest 7.2.2.2-SNAPSHOT of DX artifacts, instead of the latest released one (7.2.2.0).

Thank you in advance!

 

Kind regards

Sergiy

Sergiy Shyrkov (shyrkov)

Number of messages  407
Registration date
0 (0 Good)
0 (0 Bad)

Re: When Creating a new Module (jahia 7.2.2.0) dependencies not resolved

by  julio@newneuronalpathways.com »  2018/03/13 13:54

Dear Sergiy Shyrkov , here's answers to your questions:

1) how you've created the Module? Was it using the DX Studio or using the mvn archetype:generate from command like? I created the module using DX Studio. Once I saw the issue on the command prompt i switched to the command line continue to use "mvn clean install"

2) Which DX version are you using? I'm using both versions 7.2.2.0 release and 67.2.2.2.2-SNAPSHOT. I was initially using the relase version but once the problem arose I switched to a most recent build to see if this was a known issue and fixed in later builds.

I have already tried removing my maven local repository but that did not help.

Thank you

  (julio@newneuronalpathways.com)

Number of messages  3
Registration date
0 (0 Good)
0 (0 Bad)

Re: Re: When Creating a new Module (jahia 7.2.2.0) dependencies not resolved

by  shyrkov »  2018/03/13 15:53

Quite strange error.

The artifact in your stack trace is actually present on our repository: https://devtools.jahia.com/nexus/content/groups/public/com/adobe/xmp/xmpcore/5.1.2/

Do you have under your local Maven repository folder a dependency-cache folder? Could you renamed it please and start the module build again (with mvn -U clean install)?

Sergiy Shyrkov (shyrkov)

Number of messages  407
Registration date
1 (1 Good)
0 (0 Bad)

Re: When Creating a new Module (jahia 7.2.2.0) dependencies not resolved

by  julio@newneuronalpathways.com »  2018/03/13 22:58

You Nailed it Sergiy Shyrkov , thank you. you see, it was sort of a "rookie mistake" where my settings.xml accesses multiple artifact repositories and one of these repositores has a different pom file for the com.adobe.xmp:xmpcore:5.1.2:pom artifiact, basically the pom file i was getting has a reference to the com.adobe.granite:parten:60:pom; which is an artifact not publicly available.

I removed all other repositories out of my maven profile and was able to build.

Thank you,

  (julio@newneuronalpathways.com)

Number of messages  3
Registration date
Contact
Share
Feedback

Get in touch

Whether you are a current user or if you are just evaluating Jahia, we are here to help.

Contact us

Share this page