[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] A bit disappointing dependency...
- From: Niclas Hedhman <niclas@xxxxxxxxxxx>
- Date: Mon, 24 Oct 2005 23:18:29 +0800
- Delivered-to: firstname.lastname@example.org
- Organization: Independent
- User-agent: KMail/1.8
On Monday 24 October 2005 08:27, Jeff McAffer wrote:
> - you can write custom Ant scripts to do the build. ÂThis will be
> reasonable for a small set of bundles low down in the dependency graph. As
> you try to build things higher and higher in the graph the classpath
> becomes very hard to manage.
> - There is some hope that the Maven2 folks will come up with a mechanism
> for building OSGi bundles. ÂIf so, this would be useful/usable here.
> Make sense?
Hold on a second... I have no problems that Eclipse provide superior
plugin/bundle build tools, just like I don't feel I have problems building my
own bundles, using my own tools.
What I find 'irritating' is that the OSGi platform itself require such
advanced tooling. I don't generally have Eclipse downloaded, and find it
"amuzing" that [Product A]t0 has a dependency on [Product A]t-n.
Well, instead of complaining so much about, I'll dig in and see how hard this
could possibly be...