History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEADEV-32617
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Normal Normal
Assignee: Anton Makeev
Reporter: Erik Pragt
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
IDEA: Development

Cannot run install goal from within IntelliJ

Created: 15 Aug 08 18:26   Updated: 10 Nov 08 11:48
Component/s: Maven Integration
Fix Version/s: Diana Final

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Zip Archive MavenDependencyExporter.zip (23 kb)


Build: 8,664
Fixed in build: 9,018
Severity: High


 Description  « Hide
Hi, I configured IntelliJ to use Maven 2.0.9, but running a goal from within IntelliJ doesn't work. When I use the internal Maven, it also doesn't work.

I've attached a project which has that problem.

This is the produced stacktrace:

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Example Maven Plugin
[INFO]
[INFO] Id: com.xebia.maven.plugin:dependency-exporter:maven-plugin:1.0-SNAPSHOT
[INFO] task-segment: [package]
[INFO] ------------------------------------------------------------------------
[INFO] [groovy:generateStubs]
[WARN] Failed to load provider from: org.codehaus.groovy.maven.runtime.loader.artifact.ArtifactProviderLoader@30e694
java.lang.NullPointerException
org.codehaus.plexus.DefaultPlexusContainer.construct(DefaultPlexusContainer.java:308)
org.codehaus.plexus.DefaultPlexusContainer.<init>(DefaultPlexusContainer.java:198)
org.codehaus.plexus.aspect.CompatibilityAspect.ajc$interMethod$org_codehaus_plexus_aspect_CompatibilityAspect$org_codehaus_plexus_PlexusContainer$createChildContainer(CompatibilityAspect.aj:69)
org.codehaus.plexus.DefaultPlexusContainer.createChildContainer(DefaultPlexusContainer.java:1)
org.codehaus.plexus.aspect.CompatibilityAspect.ajc$interMethodDispatch1$org_codehaus_plexus_aspect_CompatibilityAspect$org_codehaus_plexus_PlexusContainer$createChildContainer(CompatibilityAspect.aj)
org.codehaus.plexus.aspect.CompatibilityAspect.ajc$interMethod$org_codehaus_plexus_aspect_CompatibilityAspect$org_codehaus_plexus_PlexusContainer$createChildContainer(CompatibilityAspect.aj:28)
org.codehaus.plexus.DefaultPlexusContainer.createChildContainer(DefaultPlexusContainer.java:1)
org.codehaus.groovy.maven.runtime.loader.artifact.ArtifactProviderLoader.findContainer(ArtifactProviderLoader.java:179)
org.codehaus.groovy.maven.runtime.loader.artifact.ArtifactProviderLoader.load(ArtifactProviderLoader.java:78)
org.codehaus.groovy.maven.runtime.loader.artifact.ArtifactProviderLoader.load(ArtifactProviderLoader.java:72)
org.codehaus.groovy.maven.runtime.loader.DefaultProviderSelector.load(DefaultProviderSelector.java:192)
org.codehaus.groovy.maven.runtime.loader.DefaultProviderSelector.discover(DefaultProviderSelector.java:154)
org.codehaus.groovy.maven.runtime.loader.DefaultProviderSelector.register(DefaultProviderSelector.java:98)
org.codehaus.groovy.maven.runtime.loader.DefaultProviderSelector.select(DefaultProviderSelector.java:47)
org.codehaus.groovy.maven.runtime.loader.DefaultProviderManager.select(DefaultProviderManager.java:91)
org.codehaus.groovy.maven.plugin.ProviderMojoSupport.provider(ProviderMojoSupport.java:107)
org.codehaus.groovy.maven.plugin.ComponentMojoSupport.doExecute(ComponentMojoSupport.java:58)
org.codehaus.groovy.maven.plugin.MojoSupport.execute(MojoSupport.java:69)
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
org.jetbrains.idea.maven.embedder.MavenEmbedderWrapper.execute(MavenEmbedderWrapper.java:83)
org.jetbrains.idea.maven.runner.executor.MavenEmbeddedExecutor.execute(MavenEmbeddedExecutor.java:95)
org.jetbrains.idea.maven.runner.MavenRunner$2.run(MavenRunner.java:122)
com.intellij.openapi.progress.impl.ProgressManagerImpl$TaskRunnable.run(ProgressManagerImpl.java:6)
com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:14)
com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:65)
com.intellij.openapi.progress.impl.ProgressManagerImpl.runProcess(ProgressManagerImpl.java:52)
com.intellij.openapi.progress.impl.ProgressManagerImpl$6.run(ProgressManagerImpl.java:8)
com.intellij.openapi.application.impl.ApplicationImpl$5.run(ApplicationImpl.java:6)
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
java.util.concurrent.FutureTask.run(FutureTask.java:138)
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
java.lang.Thread.run(Thread.java:619)
com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:2)
[ERROR] BUILD FAILED
[INFO] Mojo execution failed.

To view full stack traces, please go to the Maven Settings->Runner and check the 'Print stack traces' box.



 All   Comments   Work Log   Change History      Sort Order:
Erik Pragt - 15 Aug 08 18:42
Btw, running it from a console doesn't produce any errors, and builds fine.