Hi,
Sorry for bringing this up again, but this is becoming a real problem
for us. Here's why:
1. Every time we create a new workspace, the subclipse.core plug-in must
be imported into that workspace or our compilation fails. When asked,
Eclipse answers that their compiler doesn't handle embedded jars at all.
2. When the subclipse.core plug-in is imported into the workspace,
self-hosting fails. It is necessary to change the launch configuration
and force the launcher to select the one that is in the target platform
instead of defaulting to the one in the workspace.
3. There seems to be little or no activity going on around your Eclipse
proposal??
4. We (the Buckminster project) is one of the first projects to move the
whole code base from CVS to SVN at Eclipse.org. Needless to say, we'd
like to use the latest and greatest Subclipse technology in our
development environment. Item #1 - #3 makes that so cumbersome we now
feel forced to stay behind on Subclipse 1.0.4 (it is unpacked when
installed).
I've even tried to manually unpack the subclipse.core plug-in and change
the unpack directive in the "feature.xml" but that doesn't help. The
classpath construct (using a dot) in the MANIFEST.MF seems to have
special meaning. Now the compiler complains on the classes that are not
in any of the jars.
So my humble request is; please repackage your 1.2 release so that it
unpacks when installed (and does not use '.' in the bundle classpath).
The current embedding of jars creates a lot of problems and it doesn't
give your users any advantages.
Kind Regards,
Thomas Hallgren
Thomas Hallgren wrote:
> Mark Phippard wrote:
>> In the version we submitted for our Eclipse proposal, each of these
>> JARS within a JAR is now its own plugin. So the issue would go away
>> anyway once we get moved to that architecture.
>>
> Great. I can certainly bring the subclipse.core plugin into my
> workspace until that happens. Thanks for finding the problem.
>
> - thomas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Thu Feb 22 09:51:08 2007