You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Robin Vanderhallen <ro...@gmail.com> on 2019/12/19 16:05:23 UTC
building Camel in IntelliJ
Hello,
I’m having trouble building Camel from source in IntelliJ. I followed the instructions on https://camel.apache.org/manual/latest/building.html
However, mvn idea:idea is throwing an exception:
Failed to execute goal org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea (default-cli) on project camel-parent: Execution default-cli of goal org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea failed.: NullPointerException
Caused by: java.lang.NullPointerException
at org.apache.maven.plugin.idea.IdeaModuleMojo.getLibraryUrl (IdeaModuleMojo.java:1141)
at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteDependencies (IdeaModuleMojo.java:531)
at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteModule (IdeaModuleMojo.java:423)
at org.apache.maven.plugin.idea.IdeaMojo.rewriteModule (IdeaMojo.java:236)
at org.apache.maven.plugin.idea.IdeaMojo.execute (IdeaMojo.java:216)
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:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
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:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
It looks like the Maven IDEA plugin is no longer maintained.
I’m sure there must be other IntelliJ users building Camel. How are you handling this?
Best regards,
Robin
Re: building Camel in IntelliJ
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Yeah that doc page is a bit out of date. I have created a ticket.
https://issues.apache.org/jira/browse/CAMEL-14320
Contributions is welcome to update the page
On Thu, Dec 19, 2019 at 5:22 PM Omar Al-Safi <om...@oalsafi.com> wrote:
>
> Oh yeah I never actually ran mvn:idea, I just open it directly in intellj,
> most importantly by submodules. Not sure if that is still valid though
>
> On Thu, Dec 19, 2019, 17:20 Omar Al-Safi <om...@oalsafi.com> wrote:
>
> > Which camel version are you referring to? Also, I hope you are not opening
> > the full project in intellj as that may cause problems. You can try only
> > opening the submodules of the project, e.g: only one component to open in
> > intellj.
> >
> > Regards,
> > Omar
> >
> > On Thu, Dec 19, 2019, 17:05 Robin Vanderhallen <
> > robinvanderhallen@gmail.com> wrote:
> >
> >> Hello,
> >>
> >> I’m having trouble building Camel from source in IntelliJ. I followed the
> >> instructions on https://camel.apache.org/manual/latest/building.html
> >> However, mvn idea:idea is throwing an exception:
> >>
> >> Failed to execute goal
> >> org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea
> >> (default-cli) on project camel-parent: Execution default-cli of goal
> >> org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea failed.:
> >> NullPointerException
> >>
> >> Caused by: java.lang.NullPointerException
> >> at org.apache.maven.plugin.idea.IdeaModuleMojo.getLibraryUrl
> >> (IdeaModuleMojo.java:1141)
> >> at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteDependencies
> >> (IdeaModuleMojo.java:531)
> >> at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteModule
> >> (IdeaModuleMojo.java:423)
> >> at org.apache.maven.plugin.idea.IdeaMojo.rewriteModule
> >> (IdeaMojo.java:236)
> >> at org.apache.maven.plugin.idea.IdeaMojo.execute (IdeaMojo.java:216)
> >> 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:956)
> >> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> >> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> >> 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:289)
> >> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> >> (Launcher.java:229)
> >> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> >> (Launcher.java:415)
> >> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> >> (Launcher.java:356)
> >>
> >> It looks like the Maven IDEA plugin is no longer maintained.
> >>
> >> I’m sure there must be other IntelliJ users building Camel. How are you
> >> handling this?
> >>
> >> Best regards,
> >>
> >> Robin
> >>
> >>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: building Camel in IntelliJ
Posted by Robin Vanderhallen <ro...@gmail.com>.
I’m sure it’s JDK 8. The module class path shows /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home.
For some reason, the jdk9+-build profile was enabled automatically in IntelliJ (the checkbox is greyed out). This happens for every module I’m opening.
It’s working fine after I uncheck the JDK9 profile and manually select jdk8-build.
Regards,
Robin
On 20 Dec 2019, 09:16 +0100, Claus Ibsen <cl...@gmail.com>, wrote:
> Sounds a bit like you get it build with a java 9 or higher. Can you
> double check that its all JDK 8 in IDEA.
>
> Camel 2.x only support java 8. Java 11 was not fully supported, use
> Camel 3 for that.
>
> On Fri, Dec 20, 2019 at 8:22 AM Robin Vanderhallen
> <ro...@gmail.com> wrote:
> >
> > I was trying to build the 2.24.x branch. I did open the entire project. It works better when I build the sources and open a single module.
> > But when I try to run a test in IntelliJ, I get the following error: Error:java: invalid flag: -Jjava.xml.bind
> >
> > It’s one of the arguments of the maven-compiler-plugin in the parent POM.
> >
> > <compilerArgs>
> > <arg>-J--add-modules</arg>
> > <arg>-Jjava.xml.bind</arg>
> > <!-- SB2 actuator endpoint requires MethodParameter metadata -->
> > <arg>-parameters</arg>
> > </compilerArgs>
> >
> > I’m using OpenJDK 1.8.0_202.
> >
> > Regards,
> >
> > Robin
> > On 19 Dec 2019, 17:23 +0100, Omar Al-Safi <om...@oalsafi.com>, wrote:
> > > Oh yeah I never actually ran mvn:idea, I just open it directly in intellj,
> > > most importantly by submodules. Not sure if that is still valid though
> > >
> > > On Thu, Dec 19, 2019, 17:20 Omar Al-Safi <om...@oalsafi.com> wrote:
> > >
> > > > Which camel version are you referring to? Also, I hope you are not opening
> > > > the full project in intellj as that may cause problems. You can try only
> > > > opening the submodules of the project, e.g: only one component to open in
> > > > intellj.
> > > >
> > > > Regards,
> > > > Omar
> > > >
> > > > On Thu, Dec 19, 2019, 17:05 Robin Vanderhallen <
> > > > robinvanderhallen@gmail.com> wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > I’m having trouble building Camel from source in IntelliJ. I followed the
> > > > > instructions on https://camel.apache.org/manual/latest/building.html
> > > > > However, mvn idea:idea is throwing an exception:
> > > > >
> > > > > Failed to execute goal
> > > > > org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea
> > > > > (default-cli) on project camel-parent: Execution default-cli of goal
> > > > > org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea failed.:
> > > > > NullPointerException
> > > > >
> > > > > Caused by: java.lang.NullPointerException
> > > > > at org.apache.maven.plugin.idea.IdeaModuleMojo.getLibraryUrl
> > > > > (IdeaModuleMojo.java:1141)
> > > > > at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteDependencies
> > > > > (IdeaModuleMojo.java:531)
> > > > > at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteModule
> > > > > (IdeaModuleMojo.java:423)
> > > > > at org.apache.maven.plugin.idea.IdeaMojo.rewriteModule
> > > > > (IdeaMojo.java:236)
> > > > > at org.apache.maven.plugin.idea.IdeaMojo.execute (IdeaMojo.java:216)
> > > > > 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:956)
> > > > > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> > > > > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> > > > > 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:289)
> > > > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> > > > > (Launcher.java:229)
> > > > > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> > > > > (Launcher.java:415)
> > > > > at org.codehaus.plexus.classworlds.launcher.Launcher.main
> > > > > (Launcher.java:356)
> > > > >
> > > > > It looks like the Maven IDEA plugin is no longer maintained.
> > > > >
> > > > > I’m sure there must be other IntelliJ users building Camel. How are you
> > > > > handling this?
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Robin
> > > > >
> > > > >
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
Re: building Camel in IntelliJ
Posted by Claus Ibsen <cl...@gmail.com>.
Sounds a bit like you get it build with a java 9 or higher. Can you
double check that its all JDK 8 in IDEA.
Camel 2.x only support java 8. Java 11 was not fully supported, use
Camel 3 for that.
On Fri, Dec 20, 2019 at 8:22 AM Robin Vanderhallen
<ro...@gmail.com> wrote:
>
> I was trying to build the 2.24.x branch. I did open the entire project. It works better when I build the sources and open a single module.
> But when I try to run a test in IntelliJ, I get the following error: Error:java: invalid flag: -Jjava.xml.bind
>
> It’s one of the arguments of the maven-compiler-plugin in the parent POM.
>
> <compilerArgs>
> <arg>-J--add-modules</arg>
> <arg>-Jjava.xml.bind</arg>
> <!-- SB2 actuator endpoint requires MethodParameter metadata -->
> <arg>-parameters</arg>
> </compilerArgs>
>
> I’m using OpenJDK 1.8.0_202.
>
> Regards,
>
> Robin
> On 19 Dec 2019, 17:23 +0100, Omar Al-Safi <om...@oalsafi.com>, wrote:
> > Oh yeah I never actually ran mvn:idea, I just open it directly in intellj,
> > most importantly by submodules. Not sure if that is still valid though
> >
> > On Thu, Dec 19, 2019, 17:20 Omar Al-Safi <om...@oalsafi.com> wrote:
> >
> > > Which camel version are you referring to? Also, I hope you are not opening
> > > the full project in intellj as that may cause problems. You can try only
> > > opening the submodules of the project, e.g: only one component to open in
> > > intellj.
> > >
> > > Regards,
> > > Omar
> > >
> > > On Thu, Dec 19, 2019, 17:05 Robin Vanderhallen <
> > > robinvanderhallen@gmail.com> wrote:
> > >
> > > > Hello,
> > > >
> > > > I’m having trouble building Camel from source in IntelliJ. I followed the
> > > > instructions on https://camel.apache.org/manual/latest/building.html
> > > > However, mvn idea:idea is throwing an exception:
> > > >
> > > > Failed to execute goal
> > > > org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea
> > > > (default-cli) on project camel-parent: Execution default-cli of goal
> > > > org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea failed.:
> > > > NullPointerException
> > > >
> > > > Caused by: java.lang.NullPointerException
> > > > at org.apache.maven.plugin.idea.IdeaModuleMojo.getLibraryUrl
> > > > (IdeaModuleMojo.java:1141)
> > > > at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteDependencies
> > > > (IdeaModuleMojo.java:531)
> > > > at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteModule
> > > > (IdeaModuleMojo.java:423)
> > > > at org.apache.maven.plugin.idea.IdeaMojo.rewriteModule
> > > > (IdeaMojo.java:236)
> > > > at org.apache.maven.plugin.idea.IdeaMojo.execute (IdeaMojo.java:216)
> > > > 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:956)
> > > > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> > > > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> > > > 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:289)
> > > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> > > > (Launcher.java:229)
> > > > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> > > > (Launcher.java:415)
> > > > at org.codehaus.plexus.classworlds.launcher.Launcher.main
> > > > (Launcher.java:356)
> > > >
> > > > It looks like the Maven IDEA plugin is no longer maintained.
> > > >
> > > > I’m sure there must be other IntelliJ users building Camel. How are you
> > > > handling this?
> > > >
> > > > Best regards,
> > > >
> > > > Robin
> > > >
> > > >
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: building Camel in IntelliJ
Posted by Robin Vanderhallen <ro...@gmail.com>.
I was trying to build the 2.24.x branch. I did open the entire project. It works better when I build the sources and open a single module.
But when I try to run a test in IntelliJ, I get the following error: Error:java: invalid flag: -Jjava.xml.bind
It’s one of the arguments of the maven-compiler-plugin in the parent POM.
<compilerArgs>
<arg>-J--add-modules</arg>
<arg>-Jjava.xml.bind</arg>
<!-- SB2 actuator endpoint requires MethodParameter metadata -->
<arg>-parameters</arg>
</compilerArgs>
I’m using OpenJDK 1.8.0_202.
Regards,
Robin
On 19 Dec 2019, 17:23 +0100, Omar Al-Safi <om...@oalsafi.com>, wrote:
> Oh yeah I never actually ran mvn:idea, I just open it directly in intellj,
> most importantly by submodules. Not sure if that is still valid though
>
> On Thu, Dec 19, 2019, 17:20 Omar Al-Safi <om...@oalsafi.com> wrote:
>
> > Which camel version are you referring to? Also, I hope you are not opening
> > the full project in intellj as that may cause problems. You can try only
> > opening the submodules of the project, e.g: only one component to open in
> > intellj.
> >
> > Regards,
> > Omar
> >
> > On Thu, Dec 19, 2019, 17:05 Robin Vanderhallen <
> > robinvanderhallen@gmail.com> wrote:
> >
> > > Hello,
> > >
> > > I’m having trouble building Camel from source in IntelliJ. I followed the
> > > instructions on https://camel.apache.org/manual/latest/building.html
> > > However, mvn idea:idea is throwing an exception:
> > >
> > > Failed to execute goal
> > > org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea
> > > (default-cli) on project camel-parent: Execution default-cli of goal
> > > org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea failed.:
> > > NullPointerException
> > >
> > > Caused by: java.lang.NullPointerException
> > > at org.apache.maven.plugin.idea.IdeaModuleMojo.getLibraryUrl
> > > (IdeaModuleMojo.java:1141)
> > > at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteDependencies
> > > (IdeaModuleMojo.java:531)
> > > at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteModule
> > > (IdeaModuleMojo.java:423)
> > > at org.apache.maven.plugin.idea.IdeaMojo.rewriteModule
> > > (IdeaMojo.java:236)
> > > at org.apache.maven.plugin.idea.IdeaMojo.execute (IdeaMojo.java:216)
> > > 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:956)
> > > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> > > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> > > 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:289)
> > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> > > (Launcher.java:229)
> > > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> > > (Launcher.java:415)
> > > at org.codehaus.plexus.classworlds.launcher.Launcher.main
> > > (Launcher.java:356)
> > >
> > > It looks like the Maven IDEA plugin is no longer maintained.
> > >
> > > I’m sure there must be other IntelliJ users building Camel. How are you
> > > handling this?
> > >
> > > Best regards,
> > >
> > > Robin
> > >
> > >
Re: building Camel in IntelliJ
Posted by Omar Al-Safi <om...@oalsafi.com>.
Oh yeah I never actually ran mvn:idea, I just open it directly in intellj,
most importantly by submodules. Not sure if that is still valid though
On Thu, Dec 19, 2019, 17:20 Omar Al-Safi <om...@oalsafi.com> wrote:
> Which camel version are you referring to? Also, I hope you are not opening
> the full project in intellj as that may cause problems. You can try only
> opening the submodules of the project, e.g: only one component to open in
> intellj.
>
> Regards,
> Omar
>
> On Thu, Dec 19, 2019, 17:05 Robin Vanderhallen <
> robinvanderhallen@gmail.com> wrote:
>
>> Hello,
>>
>> I’m having trouble building Camel from source in IntelliJ. I followed the
>> instructions on https://camel.apache.org/manual/latest/building.html
>> However, mvn idea:idea is throwing an exception:
>>
>> Failed to execute goal
>> org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea
>> (default-cli) on project camel-parent: Execution default-cli of goal
>> org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea failed.:
>> NullPointerException
>>
>> Caused by: java.lang.NullPointerException
>> at org.apache.maven.plugin.idea.IdeaModuleMojo.getLibraryUrl
>> (IdeaModuleMojo.java:1141)
>> at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteDependencies
>> (IdeaModuleMojo.java:531)
>> at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteModule
>> (IdeaModuleMojo.java:423)
>> at org.apache.maven.plugin.idea.IdeaMojo.rewriteModule
>> (IdeaMojo.java:236)
>> at org.apache.maven.plugin.idea.IdeaMojo.execute (IdeaMojo.java:216)
>> 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:956)
>> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
>> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
>> 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:289)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
>> (Launcher.java:229)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
>> (Launcher.java:415)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.main
>> (Launcher.java:356)
>>
>> It looks like the Maven IDEA plugin is no longer maintained.
>>
>> I’m sure there must be other IntelliJ users building Camel. How are you
>> handling this?
>>
>> Best regards,
>>
>> Robin
>>
>>
Re: building Camel in IntelliJ
Posted by Omar Al-Safi <om...@oalsafi.com>.
Which camel version are you referring to? Also, I hope you are not opening
the full project in intellj as that may cause problems. You can try only
opening the submodules of the project, e.g: only one component to open in
intellj.
Regards,
Omar
On Thu, Dec 19, 2019, 17:05 Robin Vanderhallen <ro...@gmail.com>
wrote:
> Hello,
>
> I’m having trouble building Camel from source in IntelliJ. I followed the
> instructions on https://camel.apache.org/manual/latest/building.html
> However, mvn idea:idea is throwing an exception:
>
> Failed to execute goal
> org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea
> (default-cli) on project camel-parent: Execution default-cli of goal
> org.apache.maven.plugins:maven-idea-plugin:2.3-atlassian-10:idea failed.:
> NullPointerException
>
> Caused by: java.lang.NullPointerException
> at org.apache.maven.plugin.idea.IdeaModuleMojo.getLibraryUrl
> (IdeaModuleMojo.java:1141)
> at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteDependencies
> (IdeaModuleMojo.java:531)
> at org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteModule
> (IdeaModuleMojo.java:423)
> at org.apache.maven.plugin.idea.IdeaMojo.rewriteModule
> (IdeaMojo.java:236)
> at org.apache.maven.plugin.idea.IdeaMojo.execute (IdeaMojo.java:216)
> 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:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> 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:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
>
> It looks like the Maven IDEA plugin is no longer maintained.
>
> I’m sure there must be other IntelliJ users building Camel. How are you
> handling this?
>
> Best regards,
>
> Robin
>
>