Re: maven eclipse plugin workspace dependencies resolution
I happen to know a little bit about this (mainly because my colleague created
these options ;-) ).
I believe that version of the plugin hasn't been released yet, although it
could be that a SNAPSHOT-release has been made. If not, check out the latest
sources and build it for yourself, it should work like a charm!
On Thursday 07 February 2008 15:49, da Costa Oliveira, Pedro Manuel wrote:
Hi All,
I'm trying to find a better way of using maven and eclipse in my team
(m2eclipse just creates to many problems with transient dependencies,
even in 0.0.12).
So .. while trying to use maven-eclipse-plugin, I came across the
-Declipse.workspaceToConnect=${workspace_loc} option
in http://jira.codehaus.org/browse/MECLIPSE-344.
I've tried to use it so that the project dependencies inside my eclipse
would be resolved and added to my library path.
However that is not working, it still resolves the artifact jar in my
local repository.
Has anyone been able to make this work?
Regards,
Pedro
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven eclipse plugin workspace dependencies resolution
Refreshes are configured.
I tried your suggestion, but .. No luck ;)
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 16:39
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
It appears there are still some bugs. My colleague suggests adding the
parameter 'eclipse.projectDir=${basedir}', although he isn't 100% sure this
will fix your problems...
He also suggests setting some (if not most) of these properties inside your
POM instead of in the launch.
One point I have to add: make sure eclipse refreshes the projects after your
build, that could cause this kind of behavior as well!
If nothing else works, you'd have to wait until the release, but I believe
that will happen pretty soon.
On Thursday 07 February 2008 16:25, da Costa Oliveira, Pedro Manuel wrote:
Hi,
I'm running it from inside eclipse.
I've tried using
org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
eclipse:clean eclipse:eclipse -Dmaven.test.skip.exec=true
-Declipse.workspaceToConnect=${workspace_loc}
-Declipse.useProjectReferences=true
-Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml
org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
-X eclipse:clean eclipse:eclipse -Dmaven.test.skip.exec=true
-Declipse.workspaceToConnect=d:\eclipse_home\workspace\trunk
-Declipse.useProjectReferences=true
-Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml
And replacing eclipse.workspaceToConnect with eclipse.workspace. It still
doesn't add the workspace projects as project dependencies.
For a lot of reasons, my projects are not set up as module projects (don't
know if that makes any difference in this case). I just want that if my
project - webservices - dependes on - common - and common is in the
workspace, that it is added to the webservices project library as a project
dependency (can debug easily any changes done to dependant projects) and
not as an artifact dependency.
Thanks a lot,
Pedro
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 16:06
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
I asked my colleague, it could be that the parameter has changed. He
suggests trying 'eclipse.workspace'.
I presume you are running Maven from inside Eclipse, right? Or filling out
the correct path instead of '${workspace_loc}', because that is an
Eclipse-variable! (Forgot to mention that before, sorry!)
On Thursday 07 February 2008 16:00, da Costa Oliveira, Pedro Manuel wrote:
I'm using maven-eclipse-plugin 2.5-SNAPSHOT.
Shouldn't it contain the latest code/fixes?
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 15:58
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
I happen to know a little bit about this (mainly because my colleague
created these options ;-) ).
I believe that version of the plugin hasn't been released yet, although
it could be that a SNAPSHOT-release has been made. If not, check out the
latest sources and build it for yourself, it should work like a charm!
On Thursday 07 February 2008 15:49, da Costa Oliveira, Pedro Manuel wrote:
Hi All,
I'm trying to find a better way of using maven and eclipse in my team
(m2eclipse just creates to many problems with transient dependencies,
even in 0.0.12).
So .. while trying to use maven-eclipse-plugin, I came across the
-Declipse.workspaceToConnect=${workspace_loc} option
in http://jira.codehaus.org/browse/MECLIPSE-344.
I've tried to use it so that the project dependencies inside my eclipse
would be resolved and added to my library path.
However that is not working, it still resolves the artifact jar in my
local repository.
Has anyone been able to make this work?
Regards,
Pedro
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven eclipse plugin workspace dependencies resolution
Hi,
I'm running it from inside eclipse.
I've tried using
org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
eclipse:clean eclipse:eclipse -Dmaven.test.skip.exec=true
-Declipse.workspaceToConnect=${workspace_loc}
-Declipse.useProjectReferences=true
-Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml
org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
-X eclipse:clean eclipse:eclipse -Dmaven.test.skip.exec=true
-Declipse.workspaceToConnect=d:\eclipse_home\workspace\trunk
-Declipse.useProjectReferences=true
-Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml
And replacing eclipse.workspaceToConnect with eclipse.workspace. It still
doesn't add the workspace projects as project dependencies.
For a lot of reasons, my projects are not set up as module projects (don't know
if that makes any difference in this case).
I just want that if my project - webservices - dependes on - common - and
common is in the workspace,
that it is added to the webservices project library as a project dependency
(can debug easily any changes done to dependant projects) and not as an
artifact dependency.
Thanks a lot,
Pedro
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 16:06
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
I asked my colleague, it could be that the parameter has changed. He suggests
trying 'eclipse.workspace'.
I presume you are running Maven from inside Eclipse, right? Or filling out the
correct path instead of '${workspace_loc}', because that is an
Eclipse-variable! (Forgot to mention that before, sorry!)
On Thursday 07 February 2008 16:00, da Costa Oliveira, Pedro Manuel wrote:
I'm using maven-eclipse-plugin 2.5-SNAPSHOT.
Shouldn't it contain the latest code/fixes?
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 15:58
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
I happen to know a little bit about this (mainly because my colleague
created these options ;-) ).
I believe that version of the plugin hasn't been released yet, although it
could be that a SNAPSHOT-release has been made. If not, check out the
latest sources and build it for yourself, it should work like a charm!
On Thursday 07 February 2008 15:49, da Costa Oliveira, Pedro Manuel wrote:
Hi All,
I'm trying to find a better way of using maven and eclipse in my team
(m2eclipse just creates to many problems with transient dependencies,
even in 0.0.12).
So .. while trying to use maven-eclipse-plugin, I came across the
-Declipse.workspaceToConnect=${workspace_loc} option
in http://jira.codehaus.org/browse/MECLIPSE-344.
I've tried to use it so that the project dependencies inside my eclipse
would be resolved and added to my library path.
However that is not working, it still resolves the artifact jar in my
local repository.
Has anyone been able to make this work?
Regards,
Pedro
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven eclipse plugin workspace dependencies resolution
It appears there are still some bugs. My colleague suggests adding the
parameter 'eclipse.projectDir=${basedir}', although he isn't 100% sure this
will fix your problems...
He also suggests setting some (if not most) of these properties inside your
POM instead of in the launch.
One point I have to add: make sure eclipse refreshes the projects after your
build, that could cause this kind of behavior as well!
If nothing else works, you'd have to wait until the release, but I believe
that will happen pretty soon.
On Thursday 07 February 2008 16:25, da Costa Oliveira, Pedro Manuel wrote:
Hi,
I'm running it from inside eclipse.
I've tried using
org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
eclipse:clean eclipse:eclipse -Dmaven.test.skip.exec=true
-Declipse.workspaceToConnect=${workspace_loc}
-Declipse.useProjectReferences=true
-Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml
org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
-X eclipse:clean eclipse:eclipse -Dmaven.test.skip.exec=true
-Declipse.workspaceToConnect=d:\eclipse_home\workspace\trunk
-Declipse.useProjectReferences=true
-Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml
And replacing eclipse.workspaceToConnect with eclipse.workspace. It still
doesn't add the workspace projects as project dependencies.
For a lot of reasons, my projects are not set up as module projects (don't
know if that makes any difference in this case). I just want that if my
project - webservices - dependes on - common - and common is in the
workspace, that it is added to the webservices project library as a project
dependency (can debug easily any changes done to dependant projects) and
not as an artifact dependency.
Thanks a lot,
Pedro
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 16:06
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
I asked my colleague, it could be that the parameter has changed. He
suggests trying 'eclipse.workspace'.
I presume you are running Maven from inside Eclipse, right? Or filling out
the correct path instead of '${workspace_loc}', because that is an
Eclipse-variable! (Forgot to mention that before, sorry!)
On Thursday 07 February 2008 16:00, da Costa Oliveira, Pedro Manuel wrote:
I'm using maven-eclipse-plugin 2.5-SNAPSHOT.
Shouldn't it contain the latest code/fixes?
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 15:58
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
I happen to know a little bit about this (mainly because my colleague
created these options ;-) ).
I believe that version of the plugin hasn't been released yet, although
it could be that a SNAPSHOT-release has been made. If not, check out the
latest sources and build it for yourself, it should work like a charm!
On Thursday 07 February 2008 15:49, da Costa Oliveira, Pedro Manuel wrote:
Hi All,
I'm trying to find a better way of using maven and eclipse in my team
(m2eclipse just creates to many problems with transient dependencies,
even in 0.0.12).
So .. while trying to use maven-eclipse-plugin, I came across the
-Declipse.workspaceToConnect=${workspace_loc} option
in http://jira.codehaus.org/browse/MECLIPSE-344.
I've tried to use it so that the project dependencies inside my eclipse
would be resolved and added to my library path.
However that is not working, it still resolves the artifact jar in my
local repository.
Has anyone been able to make this work?
Regards,
Pedro
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven eclipse plugin workspace dependencies resolution
I asked my colleague, it could be that the parameter has changed. He suggests
trying 'eclipse.workspace'.
I presume you are running Maven from inside Eclipse, right? Or filling out the
correct path instead of '${workspace_loc}', because that is an
Eclipse-variable! (Forgot to mention that before, sorry!)
On Thursday 07 February 2008 16:00, da Costa Oliveira, Pedro Manuel wrote:
I'm using maven-eclipse-plugin 2.5-SNAPSHOT.
Shouldn't it contain the latest code/fixes?
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 15:58
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
I happen to know a little bit about this (mainly because my colleague
created these options ;-) ).
I believe that version of the plugin hasn't been released yet, although it
could be that a SNAPSHOT-release has been made. If not, check out the
latest sources and build it for yourself, it should work like a charm!
On Thursday 07 February 2008 15:49, da Costa Oliveira, Pedro Manuel wrote:
Hi All,
I'm trying to find a better way of using maven and eclipse in my team
(m2eclipse just creates to many problems with transient dependencies,
even in 0.0.12).
So .. while trying to use maven-eclipse-plugin, I came across the
-Declipse.workspaceToConnect=${workspace_loc} option
in http://jira.codehaus.org/browse/MECLIPSE-344.
I've tried to use it so that the project dependencies inside my eclipse
would be resolved and added to my library path.
However that is not working, it still resolves the artifact jar in my
local repository.
Has anyone been able to make this work?
Regards,
Pedro
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven eclipse plugin workspace dependencies resolution
Sorry to hear that. I guess there's nothing left but wait for the next
release. Although, I could ask my colleague if we have a working copy of that
plugin and send it to you. You'll have to wait a bit though, 'cause he
already left. ;-)
On Thursday 07 February 2008 17:33, da Costa Oliveira, Pedro Manuel wrote:
Refreshes are configured.
I tried your suggestion, but .. No luck ;)
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 16:39
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
It appears there are still some bugs. My colleague suggests adding the
parameter 'eclipse.projectDir=${basedir}', although he isn't 100% sure this
will fix your problems...
He also suggests setting some (if not most) of these properties inside your
POM instead of in the launch.
One point I have to add: make sure eclipse refreshes the projects after
your build, that could cause this kind of behavior as well!
If nothing else works, you'd have to wait until the release, but I believe
that will happen pretty soon.
On Thursday 07 February 2008 16:25, da Costa Oliveira, Pedro Manuel wrote:
Hi,
I'm running it from inside eclipse.
I've tried using
org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
eclipse:clean eclipse:eclipse -Dmaven.test.skip.exec=true
-Declipse.workspaceToConnect=${workspace_loc}
-Declipse.useProjectReferences=true
-Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml
org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
-X eclipse:clean eclipse:eclipse -Dmaven.test.skip.exec=true
-Declipse.workspaceToConnect=d:\eclipse_home\workspace\trunk
-Declipse.useProjectReferences=true
-Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml
And replacing eclipse.workspaceToConnect with eclipse.workspace. It still
doesn't add the workspace projects as project dependencies.
For a lot of reasons, my projects are not set up as module projects
(don't know if that makes any difference in this case). I just want that
if my project - webservices - dependes on - common - and common is in the
workspace, that it is added to the webservices project library as a
project dependency (can debug easily any changes done to dependant
projects) and not as an artifact dependency.
Thanks a lot,
Pedro
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 16:06
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
I asked my colleague, it could be that the parameter has changed. He
suggests trying 'eclipse.workspace'.
I presume you are running Maven from inside Eclipse, right? Or filling
out the correct path instead of '${workspace_loc}', because that is an
Eclipse-variable! (Forgot to mention that before, sorry!)
On Thursday 07 February 2008 16:00, da Costa Oliveira, Pedro Manuel wrote:
I'm using maven-eclipse-plugin 2.5-SNAPSHOT.
Shouldn't it contain the latest code/fixes?
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 15:58
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
I happen to know a little bit about this (mainly because my colleague
created these options ;-) ).
I believe that version of the plugin hasn't been released yet, although
it could be that a SNAPSHOT-release has been made. If not, check out
the latest sources and build it for yourself, it should work like a
charm!
On Thursday 07 February 2008 15:49, da Costa Oliveira, Pedro Manuel
wrote:
Hi All,
I'm trying to find a better way of using maven and eclipse in my team
(m2eclipse just creates to many problems with transient dependencies,
even in 0.0.12).
So .. while trying to use maven-eclipse-plugin, I came across the
-Declipse.workspaceToConnect=${workspace_loc} option
in http://jira.codehaus.org/browse/MECLIPSE-344.
I've tried to use it so that the project dependencies inside my
eclipse would be resolved and added to my library path.
However that is not working, it still resolves the artifact jar in my
local repository.
Has anyone been able to make this work?
Regards,
Pedro
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
