vimplugin-devel

Re: [vimplugin-devel] [Vimplugin-commits] SF.net SVN: vimplugin: [172] trunk/plugin

[Sebastian M. <seb...@un...>]

Am Tue, 06 Nov 2007 22:33:05 -0800
schrieb dt...@us...:

> Log Message:
> -----------
> Created ant build file for the project.
> 
> Can build, package and install the plugin.
 
Great, works like a charm ... :-)

I thought about using maven2 for this. We had very good results with JEE
Projects recently. But I never built eclipse plugins using maven. Has anyone
more experience with it?

Sebastian.

Re: [vimplugin-devel] [Vimplugin-commits] SF.net SVN: vimplugin: [172] trunk/plugin

[David T. <dav...@gm...>]

Sebastian Menge wrote:
> Am Tue, 06 Nov 2007 22:33:05 -0800
> schrieb dt...@us...:
> 
>> Log Message:
>> -----------
>> Created ant build file for the project.
>>
>> Can build, package and install the plugin.
>  
> Great, works like a charm ... :-)

Thanks. I thought about trying to add some 'launch eclipse' target but 
didn't think the effort would be worth it. You can launch Eclipse 
without too much effort though from Java so if anyone wants to debug 
Eclipse with only one instance running this would be the way about it I 
think.

> 
> I thought about using maven2 for this. We had very good results with JEE
> Projects recently. But I never built eclipse plugins using maven. Has anyone
> more experience with it?

Never used maven. Its exact purpose always confused me. Has one of those 
websites that has a lot of information of which doesn't make sense 
unless your familiar with the product or a similar one. What advatage 
would maven provide over ant though? Maven always seemed to be a 'build 
tool + more' to me and I'm not sure if we need the + more?

~ David

Re: [vimplugin-devel] [Vimplugin-commits] SF.net SVN: vimplugin: [172] trunk/plugin

[Sebastian M. <seb...@un...>]

Am Fri, 09 Nov 2007 17:36:51 +1100
schrieb David Terei <dav...@gm...>:
> Never used maven. Its exact purpose always confused me. Has one of those 
> websites that has a lot of information of which doesn't make sense 
> unless your familiar with the product or a similar one. What advatage 
> would maven provide over ant though? Maven always seemed to be a 'build 
> tool + more' to me and I'm not sure if we need the + more?

It has 

1) standardized the build process
2) huge repositories of external libs (like jakarta commons, jee and the like)

You have to use the standard directory layout and _declare_ a "project object model" (pom.xml) that contains information about:

  * SCM (CVS, SVN)
  * Dependencies
  * developers
  * deployment locations
  * etc.

And maven performs the standard build-process when launching goals (targets) like:

  * compile
  * deploy
  * javadoc
  * test

Given a good pom, it really works out of the box ...

Think about of how much standard code is in your build.xml, wouldn't a generic solution (one that is valid for all other projects too) be much better than build.xmls that are 90% similar to each other?

But we are getting too OT, I will look at it when I have time :-/

Sebastian.