Hi folks,

this is more or less a follow up to MECLIPSE-120 and MECLIPSE-344.

Situation: Most projects reference released artifacts, but I want Eclipse to 
link the projects that are available in the workspace anyway. Reasons to do so 
are explained in MECLIPSE-120, solution was proposed in MECLIPSE-344 which is 
included in the current released version of the plugin. However, if I now try 
to force the links in a project, it does not work:

===== %< ======
mvn eclipe:eclipse -Declipse.workspace="D:/work/.eclipse/WS`"
[INFO] Scanning for projects...
[INFO] snapshot com.company.buildsystem.maven2:master:SNAPSHOT: checking for 
updates from company-repo-snapshot
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO] ------------------------------------------------------------------------
[INFO] Building Company Commons Lang Project
[INFO]    task-segment: [eclipse:eclipse]
[INFO] ------------------------------------------------------------------------
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse]
[INFO] Adding support for WTP version 1.5.
[INFO] no substring wtp server match.
[INFO] Using as WTP server : Apache Tomcat v4.1
[INFO] Adding default classpath contaigner: 
org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Artifact com.company.commons:company-commons-test:jar:2.1.4 already 
available as a workspace project, but with different version. Expected: 2.1.4, 
found: 1.4-SNAPSHOT
[INFO] Artifact com.company.commons:company-commons-test:jar:2.1.4 already 
available as a workspace project, but with different version. Expected: 2.1.4, 
found: 2.1.5-SNAPSHOT
[INFO] Artifact com.thoughtworks.xstream:xstream:jar:1.3 already available as a 
workspace project, but with different version. Expected: 1.3, found: 
1.3.1-SNAPSHOT
[INFO] Using source status cache: 
D:\work\standard\commons\lang\target\mvn-eclipse-cache.properties
[INFO] File D:\work\standard\commons\lang\.project already exists.
       Additional settings will be preserved, run mvn eclipse:clean if you want 
old settings to be removed.
[INFO] Wrote Eclipse project for "company-commons-lang" to 
D:\work\standard\commons\lang.
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8 seconds
[INFO] Finished at: Wed Jun 04 12:06:28 CEST 2008
[INFO] Final Memory: 8M/14M
[INFO] ------------------------------------------------------------------------
===== %< ======

In the resulting Eclipse project I have no forced inter-project links. The 
output shows that the workspace has been found and the plugin knows exaclty 
what projects are available, that it can match the referenced artifact and the 
workspace project, but it does not link them anyway. Artifacts with a deeper 
dependency tree will cause in a reactor build (and only there) the same 
artifact printed multiple times with a version mismatch for the *reactor* 
project:

===== %< ======
[INFO] ------------------------------------------------------------------------
[INFO] Building Company Commons Virtual File System Tools
[INFO]    task-segment: [eclipse:eclipse]
[INFO] ------------------------------------------------------------------------
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse]
[INFO] Adding support for WTP version 1.5.
[INFO] no substring wtp server match.
[INFO] Using as WTP server : Apache Tomcat v4.1
[INFO] Adding default classpath contaigner: 
org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Artifact com.company.commons:company-commons-lang:jar:2.0.19 already 
available as a reactor project, but with different version. Expected: 2.0.19, 
found: 2.0.20-SNAPSHOT
[INFO] Artifact com.company.commons:company-commons-lang:jar:2.0.19 already 
available as a reactor project, but with different version. Expected: 2.0.19, 
found: 2.0.20-SNAPSHOT
[INFO] Artifact com.company.commons:company-commons-lang:jar:2.0.19 already 
available as a reactor project, but with different version. Expected: 2.0.19, 
found: 2.0.20-SNAPSHOT
[INFO] Artifact com.company.commons:company-commons-lang:jar:2.0.19 already 
available as a workspace project, but with different version. Expected: 2.0.19, 
found: 1.3-SNAPSHOT
[INFO] Artifact com.company.commons:company-commons-lang:jar:2.0.19 already 
available as a workspace project, but with different version. Expected: 2.0.19, 
found: 2.0.20-SNAPSHOT
[INFO] Artifact com.company.commons:company-commons-test:jar:2.1.3 already 
available as a reactor project, but with different version. Expected: 2.1.3, 
found: 2.1.5-SNAPSHOT
[INFO] Artifact com.company.commons:company-commons-test:jar:2.1.3 already 
available as a reactor project, but with different version. Expected: 2.1.3, 
found: 2.1.5-SNAPSHOT
[INFO] Artifact com.company.commons:company-commons-test:jar:2.1.3 already 
available as a reactor project, but with different version. Expected: 2.1.3, 
found: 2.1.5-SNAPSHOT
[INFO] Artifact com.company.commons:company-commons-test:jar:2.1.3 already 
available as a workspace project, but with different version. Expected: 2.1.3, 
found: 1.4-SNAPSHOT
[INFO] Artifact com.company.commons:company-commons-test:jar:2.1.3 already 
available as a workspace project, but with different version. Expected: 2.1.3, 
found: 2.1.5-SNAPSHOT
[INFO] Artifact com.thoughtworks.xstream:xstream:jar:1.3 already available as a 
workspace project, but with different version. Expected: 1.3, found: 
1.3.1-SNAPSHOT
[INFO] Using source status cache: 
D:\work\standard\commons\vfs\target\mvn-eclipse-cache.properties
[INFO] File D:\work\standard\commons\vfs\.project already exists.
       Additional settings will be preserved, run mvn eclipse:clean if you want 
old settings to be removed.
[INFO] Wrote Eclipse project for "es-commons-vfs" to 
D:\work\standard\commons\vfs.
===== %< ======

Note the fact that workspace projects are sometimes referenced in a 
non-existent version:

===== %< ======
[INFO] Artifact com.company.commons:company-commons-lang:jar:2.0.19 already 
available as a workspace project, but with different version. Expected: 2.0.19, 
found: 1.3-SNAPSHOT
<snip>
[INFO] Artifact com.company.commons:company-commons-test:jar:2.1.3 already 
available as a workspace project, but with different version. Expected: 2.1.3, 
found: 1.4-SNAPSHOT
===== %< ======

However, the workspace projects without such a bogus version are also not 
linked.

So, does this option work for somebody? What looks like your output? Slightly 
confused.

- Jörg

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to