Rather than providing a prefix, we should use a property for the whole name; something like this:

on plugin.properties:

maven.eclipse.project.name=${pom.artifactId}

on project.jelly:

<name>${maven.eclipse.project.name}</name>

Could you update your code (including the test cases) with this property and send a new patch so I could apply it to SVN? (unfortunately, I'm lacking the time to do the change myself).

Tks,

– Felipe

We have a custom modified eclipse plugin at use where I work. (We like maven-proxy!)

The pattern we see is as such ...

• We have a large multi-project to work with. (depending on branch, from 49 to 71 artifacts)
• Some of us have to work in more than 1 branch of the project at a time.
• Some of us have local branches for experimental work, while the HEAD branch is for active work.
• We wanted a way to uniquely identify and/or group an entire multi-project from within eclipse.
• Each developer can place a build.properties file in the root of the multiproject with a single entry like such ...
  $ maven.eclipse.project.prefix=B32
• Then when we run ...
  $ maven -Dgoal=eclipse:eclipse multiproject:goal
  we generate a whole set of projects suitable for importing into eclipse.
• Having this property be merely a prefix to the existing artifactId name, makes all of the projects belonging to each other 'group' together from within eclipse, instead of interleaving themselves.

This has proven to be extremely convenient for all of us using this modification and having to work with multiple version of the same artifact.

NOTE: With the release of eclipse 3.1 it is now possible to maintain different workspaces for the different branches reliably.

What about this:

1.Instead of setting maven.eclipse.project.prefix=B32, every developer set something like: mycompany.prefix=B32

2.On the project.properties inherited by all multi-projects, you set:

maven.eclipse.project.name=${mycompany.prefix}-${pom.artifactId}

Would it work?

– Felipe