Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <47820797.9090404@apache.org>
Date: Mon, 07 Jan 2008 12:05:59 +0100
From: Felix Knecht <felixk@apache.org>
User-Agent: Thunderbird 2.0.0.9 (X11/20071118)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [Studio] [Mavenization] Exception when running the studio:eclipse
 task
References: <98d8c0860801070249u69e87564j3af7f0ac86fe47f8@mail.gmail.com>
In-Reply-To: <98d8c0860801070249u69e87564j3af7f0ac86fe47f8@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Pierre-Arnaud Marcelot schrieb:
> Hi,
>
> I've just found that an exception was raised when running the
> 'studio:eclipse' task on any project.
>
I thought having fixed this some time ago.

Can you try to re-install locally the latest studio-plugin and try again?

Thanks
Felix

> Here's the output for the schemaeditor project (as an example):
> [INFO] Preparing studio:eclipse
> [INFO] [remote-resources:process {execution: default}]
> [INFO] [studio:eclipse]
> [ERROR]
> java.lang.NullPointerException
>     at
> org.apache.directory.studio.maven.plugins.AbstractStudioMojo.createArtifactList
> (AbstractStudioMojo.java:416)
>     at
> org.apache.directory.studio.maven.plugins.StudioEclipseMojo.execute(StudioEclipseMojo.java:104)
>     at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java
> :443)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java
> :493)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
>     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:334)
>     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>     at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>     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)
>
> Looks like the 'project' variable at line 416 of the class
> AbstractStudioMojo is null.
>
> Is there someting I can do to get it working ?
>
> Thanks,
> Pierre-Arnaud Marcelot
>