I extended the patch to include the option:

-Declipse.limitProjectReferencesToWorkspace=true

This option will force projects that are not in the workspace but in the reactor to be used as jars.

this patch includes the original patch!

Could you check if it it is still needed? maybe even deprecate it?

included is now:

• connect to artefact's available in the workspace as projects
• use the correct default class path container depending on the compiler
• exclude artefact's from using project references (by removing them from the workspace)

I did not have the time to refactor the workspace reader stuff... Creating tests took a lot of time..

But i think we should split the workspace configuration class in a class not eclipse specific and an eclipse specific subclass.

• MECLIPSE-344.patch
• MECLIPSE-344.tgz

the others are old and included.

--------ReadWorkspaceLocations--------------
//add constant
private static final String CLASSPATHENTRY_STANDARD = CLASSPATHENTRY_DEFAULT+"/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/";
--------ReadWorkspaceLocations--------------
//change the method to add defaults known by eclipse
public static HashMap readAvailableJREs( String workspaceLocation, Log logger )
{
HashMap jreMap = new HashMap();
jreMap.put( "1.2", CLASSPATHENTRY_STANDARD+"J2SE-1.2" );
jreMap.put( "1.3", CLASSPATHENTRY_STANDARD+"J2SE-1.3" );
jreMap.put( "1.4", CLASSPATHENTRY_STANDARD+"J2SE-1.4" );
jreMap.put( "1.5", CLASSPATHENTRY_STANDARD+"J2SE-1.5" );
jreMap.put( "5", jreMap.get("1.5") );
jreMap.put( "1.6", CLASSPATHENTRY_STANDARD+"JavaSE-1.6" );
jreMap.put( "6", jreMap.get("1.6") );
--------EclipsePluginTest--------------
// changed test result in testProject38and39()
doTestProject38and39( "project-38", workspace15, "J2SE-1.3" ,null);
-----------------------------------------

Cheers,
Martin

And we will now use a dependency to the original eclipse (binaries) to read them, so i think we are on the save side here

The workspace scanning is now re factored to reader and data class.

Now also included is the RAD-7 support (that needs the workspace reading) with tests.

• MECLIPSE-344+rad7.patch contains the patch and all new text files
• MECLIPSE-344+rad7.tgz contains the new binary files

to use the RAD-7 support the option

• workspaceToConnect must point to the current workspace directory (use ${workspace_loc} in eclipse launches)
• wtpdefaultserver contains the exact name or a substring of the defined wtp server to use

Building now

<profile>
      <id>apache.snapshots</id>
      <repositories>
        <repository>
          <releases>
            <enabled>false</enabled>
          </releases>
          <snapshots/>
          <id>apache.snapshots</id>
          <name>Maven Snapshots</name>
          <url>http://people.apache.org/maven-snapshot-repository</url>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <releases>
            <enabled>false</enabled>
          </releases>
          <snapshots/>
          <id>apache.plugin.snapshots</id>
          <name>Maven Plugin Snapshots</name>
          <url>http://people.apache.org/maven-snapshot-repository</url>
        </pluginRepository>
      </pluginRepositories>
    </profile>

Then you have to call this command :

mvn org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse

<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>outboundInterfaces</artifactId>
<classifier>${environment.type}</classifier>
</dependency>
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>outboundInterfaces</artifactId>
<version>${project.version}</version>
<type>test-jar</type>
<scope>test</scope>
</dependency>

So i think it is best to make no new option but let the user decide with the eclipse means available (what's in the workspace will be linked).
I think the best solution is to import or delete (just from the workspace) the projects as needed and then let the eclipse plugin connect them.

http://jira.codehaus.org/browse/MECLIPSE-344#action_126688

If you have imported the project already into eclipse then link to it, otherwise use m2 repository.