[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] OSGI Bundles: alternate manifest.mf location
- From: "Niclas Hedhman" <niclas@xxxxxxxxxxx>
- Date: Sun, 9 Jul 2006 11:08:06 +0800
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=B5v7M8a0DH2qzAQ6av+PZyGsAME7OItCRTlx9ufeWWMNjds14ioloWZ2due2WoOkwHkFWt9FsSr/g12R8Rlh9qKJusnYRftGqc+t7PEvjqXUd1O6avafICzURfmWl6Qryv+nEZZhtQIExJlOZN/ftjDQSL99T3dvCs0LEvjU+C4=
On 7/8/06, Peter Neubauer <peter@xxxxxxxxxxx> wrote:My main concern with using Eclipse as the primary system resolves around the "non-repeatability", hard to produce additional artifacts, lack of compile time filtering and how difficult it is to use as a continuous integration system. But that is obviously not a problem for the Eclipse lovers.
That means that
- the PDE is a slave to the CLI build system (in this case M2)
That is a feature, IMHO :o)
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.
Btw, is the PDE part of the Equinox team's responsibility, or is that handled by other folks??