Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

Failed to execute goal org.apache.felix:maven-bundle-plugin:4.1.0:bundle (default-bundle) on project acme-store.core: Error(s) found in bundle configuration : AEM Version 6.4.0

Heena91
Level 3
Level 3

Hi,

 

I m getting below error message while building my project. Please suggest.

 

[ERROR] Bundle com.acme.cif:acme-store.core:bundle:0.0.1-SNAPSHOT : Got unexpected exception while analyzing:java.lang.NoClassDefFoundError: com/day/cq/search/impl/util/InvalidDateException
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.getDeclaredMethod(Class.java:2128)
at org.apache.felix.scrplugin.helper.Validator.getMethod(Validator.java:597)
at org.apache.felix.scrplugin.helper.Validator.getMethod(Validator.java:226)
at org.apache.felix.scrplugin.helper.Validator.findLifecycleMethod(Validator.java:246)
at org.apache.felix.scrplugin.SCRDescriptorGenerator.createComponent(SCRDescriptorGenerator.java:437)
at org.apache.felix.scrplugin.SCRDescriptorGenerator.execute(SCRDescriptorGenerator.java:161)
at org.apache.felix.scrplugin.bnd.SCRDescriptorBndPlugin.analyzeJar(SCRDescriptorBndPlugin.java:178)
at aQute.bnd.osgi.Analyzer.doPlugins(Analyzer.java:820)
at aQute.bnd.osgi.Analyzer.analyze(Analyzer.java:229)
at aQute.bnd.osgi.Builder.analyze(Builder.java:408)
at aQute.bnd.osgi.Analyzer.calcManifest(Analyzer.java:850)
at aQute.bnd.osgi.Builder.build(Builder.java:116)
at org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:972)
at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:467)
at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:384)
at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:375)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
Caused by: java.lang.ClassNotFoundException: com.day.cq.search.impl.util.InvalidDateException
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
... 40 more

[ERROR] Error(s) found in bundle configuration
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for acme-store 0.0.1-SNAPSHOT:
[INFO]
[INFO] acme-store ......................................... SUCCESS [ 0.383 s]
[INFO] Acme Store - Core .................................. FAILURE [ 11.751 s]
[INFO] Acme Store - UI apps ............................... SKIPPED
[INFO] Acme Store - UI content ............................ SKIPPED
[INFO] Acme Store - Sample Content ........................ SKIPPED
[INFO] Acme Store - All-in-one package .................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 14.353 s
[INFO] Finished at: 2020-10-08T16:18:57+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.felix:maven-bundle-plugin:4.1.0:bundle (default-bundle) on project acme-store.core: Error(s) found in bundle configuration -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :acme-store.core

 

Heena91_0-1602154363934.png

 

Thanks,

Heena

5 Replies
santhosh_kumark
Community Advisor
Community Advisor

Hi @Heena91 ,

 

It looks like there are issues with executing maven bundle plugin. 

https://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html

the <plugins> section of the POM file for this bundle project would look like this: 

  <plugin>
    <groupId>org.apache.felix</groupId>
    <artifactId>maven-bundle-plugin</artifactId>
    <extensions>true</extensions>
    <configuration>
      <instructions>
        <Export-Package>com.acme.prime.speaker.api</Export-Package>
        <Private-Package>com.acme.prime.speaker.provider.*</Private-Package>
        <_dsannotations>*</_dsannotations>
      </instructions>
    </configuration>
  </plugin>

https://bnd.bndtools.org/tools/felix-maven.html

 

Regards,

Santosh

Heena91
Level 3
Level 3
Hi @santhosh_kumark I have used below plugin in my project's parent pom.xml, could you please help me to find out what can be the issue??? <plugins> <!-- Create the bundle of the Sling API --> <plugin> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <extensions>true</extensions> <configuration> <instructions> <Bundle-DocURL> http://sling.apache.org/site/sling-api.html </Bundle-DocURL> <Export-Package> org.apache.sling.api;version=2.1, org.apache.sling.api.adapter;version=2.2, org.apache.sling.api.auth;version=1.0, org.apache.sling.api.request;version=2.1, org.apache.sling.api.resource;version=2.11, org.apache.sling.spi.resource.provider;version=1.2, org.apache.sling.api.scripting;version=2.1, org.apache.sling.api.servlets;version=2.1, org.apache.sling.api.wrappers;version=2.1, org.apache.sling.api.wrappers.impl;version=2.1, com.adobe.granite.ui.components;version=1.19, com.adobe.granite.ui.components.ds;version=1.3, com.day.cq.search;version=1.3, com.day.cq.search.impl.builder;version=1.19, com.adobe.granite.ui.components.impl;version=1.19, com.day.cq.search.eval;version=1.3 </Export-Package> <!-- Require explicit version of the servlet API --> <Import-Package> javax.servlet.*;version=2.4,* </Import-Package> </instructions> </configuration> </plugin>
Anudeep_Garnepudi
Community Advisor
Community Advisor

Hi @Heena91 

Check and make sure Adobe CQ Search QueryBuilder (com.day.cq.cq-search) version 5.11.2 bundle is available and active. NoClassDefFoundError is a run time error, as it mentioned scope as provided for cq-search bundle. Maven will ignore InvalidDateException class at compile time. We should make sure that the provided jar/bundle with version is available at runtime.

<dependency>
    <groupId>com.day.cq</groupId>
    <artifactId>cq-search</artifactId>
   <version>5.11.2</version>
    <scope>provided</scope>
</dependency>

AG

Anudeep_Garnepudi
Community Advisor
Community Advisor

Hi @Heena91 

May I know which version of uber jar you are using? Try using uber-jar 6.4 once.

AG