[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] OSGI Bundles: alternate manifest.mf location

Niclas,

On 7/9/06, Niclas Hedhman <niclas@xxxxxxxxxxx> wrote:
I think that the best way forward is a command-line driven tool that
understands OSGi, yet have the power of standardization that Maven offers. I
know Peter Kriens has advocated this previously, but not keen to push real
hard.
Yes, we are always getting to this point again. I fully agree.
Question is if there is more help to get from the PDE team? I
previously asked a bit and it seems the Eclipse team thinks the
current ant system and export features are sufficient at least for the
Eclipse development horizon, but there sems to be some degree of power
inside Equinox and Adapter and Resolver parts to hook into:
http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg01168.html

So, if we could get a project financing for it, probably one could
start playing with putting in Hansa as the resolver etc. Btw there
seems to be a common issue with Eclipse not treating everything as
URLs, and especially not being able to handle nested Jar URLs, giving
problems in e.g. mounting custom URL formats as source jars, javadoc,
and resolve nested jars from library bundles that are not expanded on
disk.

/peter