Unresolved requirement for non-existing version https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&threadId=114473933 2026-04-06T11:32:24Z 2026-04-06T11:32:24Z Andrew Jardine https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=114485768 2019-07-29T15:45:28Z 2019-07-29T15:45:28Z

Hey Tom,Just to give you another reference (sometimes we don&#39;t have internet connections!) .. you can look it up in the bnd file with the module in the portal source of course, but there is also a file in the portal source called <strong>module.properties</strong> which contains a list that easy peasy to look up. The only thing you have to remember to do is subtract 1 point version off the value listed. So for example, I am looking at the file for 7.1 GA4 source and it has <strong>com.liferay.journal.api=3.5.8</strong> .. so in my dependencies I would specify <strong>com.liferay.journal.api=3.5.7</strong>

Andrew Jardine 2019-07-29T15:45:28Z Tom Jacobs https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=114478083 2019-07-29T10:48:37Z 2019-07-29T10:48:37Z

Ok good to know! I&#39;m working with Liferay 7.2, changed the com.liferay.journal.api version to 4.3.0 (for June 2019) and it works!Thank you!

Tom Jacobs 2019-07-29T10:48:37Z Christoph Rabel https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=114477350 2019-07-29T10:19:20Z 2019-07-29T10:19:20Z

It&#39;s a bit misleading.<br />Each jar file has a bundle version. That version is what you request using gradle/maven. But each package inside also has a version. And with Liferay, this version usually is different from the bundle version.<br />You probably need <br />compile group: &#39;com.liferay&#39;, name: &#39;com.liferay.journal.api&#39;, version: &#39;3.0.0&#39;<br />As a rule of thumb:<br />Look at the release time of your Liferay version. e.g. for 7.1 that was early July 2018. When a new version is released, Liferay bumps the bundle version. In maven repository you see that com.liferay.journal.api 3.0.0 was released in June 2018. That&#39;s probably the version you need. Using the lowest major version is usually fine in OSGI since it allows you to support the most installations.

Christoph Rabel 2019-07-29T10:19:20Z Tom Jacobs https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=114473932 2019-07-29T09:29:22Z 2019-07-29T09:29:22Z

Hi,<br /><br />I&#39;m trying to work with the journalArticleLocalService in a custom module. For this I added a dependency to my build.gradle file: <br />compile group: &#39;com.liferay&#39;, name: &#39;com.liferay.journal.api&#39;, version: &#39;4.4.0&#39;<br /><br />When I try to deploy this module, I&#39;m getting an error:<br />org.osgi.framework.BundleException: Could not resolve module: content.manager [1098]_ Unresolved requirement: Import-Package: com.liferay.journal.service; version=&#34;[2.7.0,3.0.0)&#34;_ [Sanitized]<br /><br />So I go to mvnrepository and look for the correct dependency for com.liferay.journal.service: <a href="https://mvnrepository.com/artifact/com.liferay/com.liferay.journal.service">https://mvnrepository.com/artifact/com.liferay/com.liferay.journal.service</a><br /><br />But there is no version between 2.7.0 and 3.0.0<br /><br />What do I do now?

Tom Jacobs 2019-07-29T09:29:22Z