I'm wondering if the <name> information is not set in the pom ? This is not required by maven but usually set. Can it be the problem ?
On Jan 30, 2008 10:38 PM, Chris Custine <[EMAIL PROTECTED]> wrote: > The jbi-maven-plugin doesn't like something about one of the service-units > listed in your SA pom.xml, specifically the plugin couldn't figure out the > file name of the SU that it is going to include in the jbi.xml file. I am > guessing that maybe you are building the SA before the SU has been fully > built, or something like that. If thats not it you might want to post more > about your build such as pom.xml files. > > Chris > > > On Jan 30, 2008 11:46 AM, Deepak Gupta <[EMAIL PROTECTED]> wrote: > > > > > I'm using ServiceMix 3.2.1 on Windows XP, 1.5 JVM, Maven 2. > > > > I get the following error trying to run "mvn install". > > > > Any ideas why ? > > > > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 > > at java.lang.String.substring(String.java:1768) > > at > > > > org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.generateJbiDescriptor > > (GenerateServiceAssemblyDescriptorMojo.java:212) > > at > > > > org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.execute > > (GenerateServiceAssemblyDescriptorMojo.java:158) > > at > > org.apache.maven.plugin.DefaultPluginManager.executeMojo( > > DefaultPluginManager.java:447) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( > > DefaultLifecycleExecutor.java:539) > > at > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle > > (DefaultLifecycleExecutor.java:480) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( > > DefaultLifecycleExecutor.java:459) > > at > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures > > (DefaultLifecycleExecutor.java:311) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( > > DefaultLifecycleExecutor.java:278) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( > > DefaultLifecycleExecutor.java:143) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > > 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:585) > > 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) > > > > cheers, > > > > Deepak > > -- > > View this message in context: > > http://www.nabble.com/Failure-building-service-assembly-tp15189107s12049p15189107.html > > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > > > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
