FYI,
Have managed to get m2eclipse building with maven inside eclipse :)
The problem was that the eclipse plugin was not finding the local
repository:
15/12/06 12:27:37 GMT: [DEBUG] Building Maven global-level settings from:
'/home/murphdg/conf/settings.xml'
Linking it to the one in my
Thanks all,
Seems like the general opinion is that building with maven in eclipse
(m2eclipse is meant to do this) seems like a path less well trodden
I've got the external svn, mvn eclipse, import method working so I guess
I'll just leave the maven building to the command line... same 'cos
Dan,
I just stumbled on this
http://www-128.ibm.com/developerworks/opensource/library/os-maven/index.html
-- not sure if its relevant, but the title looks to be so.
Regards, Kelvin.
On 08/11/06, Dan Murphy [EMAIL PROTECTED] wrote:
Thanks all,
Seems like the general opinion is that building
Hi,
Has anyone out there had any sucess building inside eclipse using the
subversion (http://subclipse.tigris.org/) and maven2 (
http://m2eclipse.codehaus.org/) plug-ins ?
I'd like to be able to sync and build without stepping into command line
mode... but this looks like wishful thinking.
On 11/7/06, Dan Murphy [EMAIL PROTECTED] wrote:
Hi,
Has anyone out there had any sucess building inside eclipse using the
subversion (http://subclipse.tigris.org/) and maven2 (
http://m2eclipse.codehaus.org/) plug-ins ?
I'd like to be able to sync and build without stepping into command line
Hi Ant,
one Q... if you svn outside eclipse what do you do to get team sync working
in eclipse ?
sounds like a good compromise, though would still prefer to work purely in
eclipse - I'll do this if no-one else can help with my q
Thanks,
Dan
On 07/11/06, ant elder [EMAIL PROTECTED] wrote:
On
You don't have to do anything, it just works as the eclipse svn plugin uses
the same .svn info as the command line one.
If you really don't want to use the command line at all you should be able
to checkout the tuscany code from the svn repo from the eclipse svn
repository exploring perspective,
Hi,
I too use a mix of Eclipse plug in and SVN. Initially, I checked out the
source using command line SVN and after building the eclipse projects using
commandline mavein (as Ant has described) I import the projects into
eclipse. From then on all of SVN interactions - update, commit, patch