AEM 6.1 dependencies - build error (Invalid syntax for version: null, for cmd: range, arguments; [range, [==,+)] ) - maven-bundle-plugin | Community
Skip to main content
R
Ruben_Thys1
October 16, 2015
Solved

AEM 6.1 dependencies - build error (Invalid syntax for version: null, for cmd: range, arguments; [range, [==,+)] ) - maven-bundle-plugin

  • October 16, 2015
  • 3 replies
  • 1829 views

I'm trying to build an AEM6 project using the new AEM6.1 dependencies. However I'm stuck with some pretty nasty build errors...

When I use the following new AEM6.1 dependency (why is this moved (the other way around again) from com.adobe.aem to com.day.cq?) :

<dependency>
    <groupId>com.day.cq</groupId>
    <artifactId>cq-quickstart</artifactId>
    <version>6.1.0</version>
    <scope>provided</scope>
    <classifier>apis</classifier>
</dependency>

However when I build the project I get these errors : 

[WARNING] Bundle sample:aem-services:bundle:1.0.0-SNAPSHOT : No translation found for macro: range;[==,+)
[ERROR] Bundle sample:aem-services:bundle:1.0.0-SNAPSHOT : null, for cmd: range, arguments; [range, [==,+)]
[ERROR] Bundle sample:aem-services:bundle:1.0.0-SNAPSHOT : No version specified for ${version} or ${range} and no implicit version ${@} either, mask===
[ERROR] Bundle sample:aem-services:bundle:1.0.0-SNAPSHOT : No version specified for ${version} or ${range} and no implicit version ${@} either, mask=+

[ERROR] Failed to execute goal org.apache.felix:maven-bundle-plugin:2.3.7:bundle (default-bundle) on project sample-aem-services: Error(s) found in bundle configuration -> [Help 1]
[ERROR] 

What I already tried to do ? 

  • Clean my local Maven repository 
  • Check the version numbers of the "maven-bundle-plugin" (2.3.7)-> updated this one to 2.5.3 but will result in a similar error : " Invalid syntax for version: null, for cmd: range, arguments; [range, [==,+)] "

Looks like I have an issue that is very familiar to the one that was mentioned related to the AEM 6.1 beta : http://www.minzdravkub.ru/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.1.html/forum__qlk9-hi_i_have_beena.html 
Somebody who was able to get this fixed? 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

Are you following online AEM documentation?  I am looking at the 6.1 docs here:

http://docs.adobe.com/docs/en/aem/6-1/develop/dev-tools/ht-projects-maven.html#How-To Add Dependencies

and i am not seeing mention of this dependency. Instead - it says to use dep finder:

To find the Maven coordinates for a class or package, you can use the Web Console's "Packages" screen athttp://<host>:<port>/system/console/depfinder.

3 replies

smacdonald2008
smacdonald2008Accepted solution
October 16, 2015

Are you following online AEM documentation?  I am looking at the 6.1 docs here:

http://docs.adobe.com/docs/en/aem/6-1/develop/dev-tools/ht-projects-maven.html#How-To Add Dependencies

and i am not seeing mention of this dependency. Instead - it says to use dep finder:

To find the Maven coordinates for a class or package, you can use the Web Console's "Packages" screen athttp://<host>:<port>/system/console/depfinder.

sudheeras
sudheeras
October 16, 2015

Just to isolate the problem, could you try with maven-bundle-plugin version 2.3.4 please ?

 

-Sudheera

R
Ruben_Thys1Author
October 16, 2015

Well actually I'm using this dependency based on a blog post from the official Adobe blog: http://blogs.adobe.com/experiencedelivers/experience-management/aem6-maven-dependencies-simplicity/ 
So I would assume they support this (much cleaner) way of managing AEM dependencies ?

Terms & ConditionsAccessibility statement

Loading footer...