[ https://issues.apache.org/jira/browse/FELIX-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved FELIX-2770. ------------------------------------- Resolution: Fixed Fix Version/s: maven-scr-plugin-1.6.2 > maven-scr-plugin 1.6.0 incompatible with <packaging>pom</packaging> projects > ---------------------------------------------------------------------------- > > Key: FELIX-2770 > URL: https://issues.apache.org/jira/browse/FELIX-2770 > Project: Felix > Issue Type: Bug > Components: Maven SCR Plugin > Affects Versions: scr-1.6.0 > Environment: Apache Maven 2.2.1 (rdebian-4) > Java version: 1.6.0_22 > Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre > Default locale: en_AU, platform encoding: UTF-8 > OS name: "linux" version: "2.6.35-23-generic" arch: "i386" Family: "unix" > Reporter: Ben Alex > Assignee: Carsten Ziegeler > Fix For: maven-scr-plugin-1.6.2 > > > maven-scr-plugin 1.6.0 when defined in a pom.xml that is of type > <packaging>pom</packaging> yields an exception during a Maven 2.2.1 reactor > build: > {code} > java.lang.IllegalStateException: basedir > /home/balex/projects/roo/osgi-roo-bundle/src/main/java does not exist > at > org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:290) > at > org.apache.felix.scrplugin.mojo.MavenJavaClassDescriptorManager.getSourceFiles(MavenJavaClassDescriptorManager.java:97) > at > org.apache.felix.scrplugin.JavaClassDescriptorManager.getSources(JavaClassDescriptorManager.java:109) > at > org.apache.felix.scrplugin.JavaClassDescriptorManager.getJavaClassesFromSources(JavaClassDescriptorManager.java:446) > at > org.apache.felix.scrplugin.JavaClassDescriptorManager.getSourceDescriptions(JavaClassDescriptorManager.java:362) > at > org.apache.felix.scrplugin.SCRDescriptorGenerator.execute(SCRDescriptorGenerator.java:233) > at > org.apache.felix.scrplugin.mojo.SCRDescriptorMojo.execute(SCRDescriptorMojo.java:184) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > {code} > It is typical to use a <packaging>pom</package> in a parent module in large > OSGi systems such as Spring Roo. Such modules don't have src/main/java > directories as there is no Java code contained within them. > This bug is not present when using maven-scr-plugin 1.4.4 and below. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.