maven-eclipse-plugin configuration for pom packaging

[james.w.jackson]

I'm using maven 2.2.1 and maven-eclipse-plugin 2.7 with a multi-module
project.

When I run 'mvn eclipse:eclipse' in the multi-module project, it doesn't
generate .project eclipse files for the projects that are marked as
<packaging>pom</packaging>.

How can I configure the plugin to generate .project files for projects that
have the pom packaging?

Thanks,
Jim
--
View this message in context: http://old.nabble.com/maven-eclipse-plugin-configuration-for-pom-packaging-tp26215800p26215800.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Arnaud HERITIER]

The plugin doesn't support it.
I think there's a an issue already opened about that.
You can vote for it.

It is supported by m2eclipse or Q4E.

Cheers,

Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net


On Thu, Nov 5, 2009 at 5:39 PM, james.w.jackson <
[hidden email]> wrote:

>
> I'm using maven 2.2.1 and maven-eclipse-plugin 2.7 with a multi-module
> project.
>
> When I run 'mvn eclipse:eclipse' in the multi-module project, it doesn't
> generate .project eclipse files for the projects that are marked as
> <packaging>pom</packaging>.
>
> How can I configure the plugin to generate .project files for projects that
> have the pom packaging?
>
> Thanks,
> Jim
> --
> View this message in context:
> http://old.nabble.com/maven-eclipse-plugin-configuration-for-pom-packaging-tp26215800p26215800.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

[james.w.jackson]

I was afraid of that.

I eventually manhandled the plugin in my pom.xml files that had pom
packaging to get the .project files, but it doesn't feel right:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-eclipse-plugin</artifactId>
    <configuration>
        <packaging>jar</packaging>
    </configuration>
</plugin>

In the end it was a pyrrhic victory.  I was hoping to use the eclipse
Import...->Existing Projects into Workspace, but it stops recursing once it
finds a folder with a .project file--which is not terribly useful for a
multi-module projects with many component and sub-component parent poms.

Thanks for the response,
Jim


Arnaud HERITIER wrote:

>
> The plugin doesn't support it.
> I think there's a an issue already opened about that.
> You can vote for it.
>
> It is supported by m2eclipse or Q4E.
>
> Cheers,
>
> Arnaud Héritier
> Software Factory Manager
> eXo platform - http://www.exoplatform.com
> ---
> http://www.aheritier.net
>
>
> On Thu, Nov 5, 2009 at 5:39 PM, james.w.jackson <
> [hidden email]> wrote:
>
>>
>> I'm using maven 2.2.1 and maven-eclipse-plugin 2.7 with a multi-module
>> project.
>>
>> When I run 'mvn eclipse:eclipse' in the multi-module project, it doesn't
>> generate .project eclipse files for the projects that are marked as
>> <packaging>pom</packaging>.
>>
>> How can I configure the plugin to generate .project files for projects
>> that
>> have the pom packaging?
>>
>> Thanks,
>> Jim
>> --
>> View this message in context:
>> http://old.nabble.com/maven-eclipse-plugin-configuration-for-pom-packaging-tp26215800p26215800.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>

--
View this message in context: http://old.nabble.com/maven-eclipse-plugin-configuration-for-pom-packaging-tp26215800p26222157.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Barrie Treloar]

If you checkout your project from your revision control system via
eclipse, it should already be available as a project.

Otherwise, you have to cheat to get it into eclipse.

File > New Project
General > Project
Specify "Project name"
Uncheck "Use default location"
Browse to where the top level project is.
Click "Finish"

You should now have your top level project in eclipse.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Barrie Treloar]

On Fri, Nov 6, 2009 at 7:34 AM, james.w.jackson
<[hidden email]> wrote:
> In the end it was a pyrrhic victory.  I was hoping to use the eclipse
> Import...->Existing Projects into Workspace, but it stops recursing once it
> finds a folder with a .project file--which is not terribly useful for a
> multi-module projects with many component and sub-component parent poms.

p.s. I missed this.
See http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html
Right towards the bottom is this

"Note, you have to delete the .project-file of your parent project
before. The result is the same as checking out the whole project from
the command line, running mvn eclipse:eclipse and finally importing
the projects into your Eclipse workspace. In both cases you will be
able to synchronize your changes using Eclipse."

Eclipse doesn't really support projects within projects, but by
deleting the .project file of the parent project you can then use
Import Existing and it will find the modules.
Don't worry about deleting this file, it is regenerated via Eclipse for you.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]