[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[pdt-dev] Re: resolving PDT build issues
- From: Nick Boldt <nickboldt@xxxxxxxxx>
- Date: Wed, 06 May 2009 12:16:22 -0400
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=KQztVkM5Pv9slT8kw/zd9H+p+AeB+gt8VsgE3viuVUFG6NaFIRXRl3ucWkSxftkxLy 5/eJkwWi6K+ESev4h+BoZ3Ux+L8jkB8u/MFrDsq0NfA/qlJOYzmJ5NDKunAnkdLtoGnY sd7jEB53yFyrug+neMOLli1RKhMzwrSAy/eR0=
- User-agent: Thunderbird 22.214.171.124 (X11/20090320)
Do you know whether internal Jars are signed as well? We have JFlex &
JavaCup jars that reside in org.eclipse.php.core plug-in...
I'm not sure if it recurses INTO jars; I would guess no.
BTW, I'm going to pretend that the aforementioned jars have already been
approved bby the Eclipse Legal team, documented in IPzilla with CQs, and
not mention that redistribution of non-CQ-approved code at eclipse.org
is illegal, since you already know that.
I'm going to further NOT mention that code released under GPL (or
GPL-equivalents) is not compatible w/ EPL and therefore cannot be
approved in IPzilla for redistribution.
Of course if you want to redistribute these jars you can do so @
sourceforge or a similar place, but eclipse.org != GPL-land. That's how
CDT gets around this limitation for redistribution of MinGW.
Nick Boldt :: http://wiki.eclipse.org/User:Nickb
Release Engineer :: Eclipse Modeling & Dash Athena