hi,
I thought I'd give 2.0.4 (from the 2.0.x branch) a test drive as well. While
not sure it's related to what you've indicated, the maven-idea-plugin fails
too:
[EMAIL PROTECTED] a]$ mvn -e idea:idea
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'idea'.
[INFO]
----------------------------------------------------------------------------
[INFO] Building Messages
[INFO] task-segment: [idea:idea]
[INFO]
----------------------------------------------------------------------------
[INFO] Preparing idea:idea
[INFO] No goals needed for project - skipping
[INFO] [idea:idea]
Executed project: null
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Unable to build project dependencies.
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build
project dependencies.
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(
DefaultLifecycleExecutor.java:488)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to build
project dependencies.
at org.apache.maven.plugin.idea.IdeaMojo.execute(IdeaMojo.java:188)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:534)
... 16 more
Caused by: java.lang.NullPointerException
at org.apache.maven.plugin.idea.AbstractIdeaMojo.getProjectArtifacts
(AbstractIdeaMojo.java:301)
at
org.apache.maven.plugin.idea.AbstractIdeaMojo.doDependencyResolution(
AbstractIdeaMojo.java:257)
at org.apache.maven.plugin.idea.IdeaMojo.execute(IdeaMojo.java:184)
... 18 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Tue Apr 04 13:31:19 IDT 2006
[INFO] Final Memory: 2M/5M
[INFO]
------------------------------------------------------------------------
I used it on a small test POM:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";>
<modelVersion>4.0.0</modelVersion>
<groupId>o</groupId>
<artifactId>c</artifactId>
<name>Messages</name>
<version>0.1-SNAPSHOT</version>
<dependencies>
<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<version>1.0</version>
</dependency>
</dependencies>
</project>
It seems that the "executedProject" is not injected correctly in the
AbstractIdeaMojo and remains null, hence the NPE later on...
** This pertains the maven-idea-plugin from the trunk, not a released
version....
I figured I'd better post it before you release 2.0.4, just in case it
really is another regression, so I'd save you the trouble of another patch
;-)
On 4/4/06, Vincent Massol <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I've just tried the cargo build with the latest trunk versions of
> 2.0.4-SNAPSHOT and surefire plugin, and it seems there's some
> interpolation
> issue (I don't know if the problem is with the surefire plugin or with
> maven
> core).
>
> Here's what I have:
>
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <forkMode>pertest</forkMode>
> <systemProperties>
> [...]
> <property>
> <name>cargo.target.dir</name>
> <value>${project.build.directory}</value>
> </property>
> [...]
>
> It seems the ${project.build.directory} property is no longer getting
> resolved as I got a directory named ${project.build.directory} created.
>
> It used to work fine which is why I'm asking If it's a regression. It's
> also
> possible that it's just me doing something stupid...
>
> Thanks
> -Vincent
>
>
>
>
>
>
>
> ___________________________________________________________________________
> Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les
> tarifs exceptionnels pour appeler la France et l'international.
> Téléchargez sur http://fr.messenger.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Regards,
_____________________________________
Arik Kfir [EMAIL PROTECTED]
