[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] Bug in "Run As Equinox"
- From: Niclas Hedhman <niclas@xxxxxxxxxxx>
- Date: Wed, 11 Oct 2006 17:24:51 +0800
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender; b=MfniQir8XTCiUbLu8vqqWdNfaLF/tGE+VqGOM3UDn55hdUDETpfskpxhwpN6qFH94a7JXZ78mi1jaeYMRkwNY1fgw4uwkDa5pm5hg4oPPbR9RRy2pg2687L0T1OOVF7so0DHrut2U+GBWhtpZ1YzX/VcasWyaWeT/Z5ft5U+xMo=
- User-agent: KMail/1.9.4
If we "Run As Equinox" and don't specify a start level for the bundles, we see
very strange behavior.
The PDE creates for instance
but Equinox has great difficulty in understanding that and although it loads
the bundle to a RESOLVED state, it will not start it, nor will I be able to
start it manually from the console.
If we manually add the startlevel (e.g @2:start) in the config.ini file,
Equinox runs as expected.
This behaviour is observed for both 3.2.1  and 3.3-M2 .
And it is much worse in "Run As Eclipse Application", since we can't specify
the start levels at all, and the same behaviour is seen.
Is there something to this that we are missing? Will file bug report if not a