| AW: [jwt-dev] Plugin mode check |
|
Hi, I agree that this is
indeed a bit annoying. Probably there is a better way to identify whether JWT
is running in RCP mode. We’ll try to fix this for the next release. As a
workaround, as Florian said, it can be changed to match the name of your
product. Regards, Chris Von: jwt-dev-bounces@xxxxxxxxxxx
[mailto:jwt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Florian Lautenbacher Hi Ravi, I also stumbled about
that a few weeks ago. Actually, this is in my opinion a bug. I have it on my to
do list to open a new bug for that in the Eclipse bugzilla. In my solution
(where I also built an RCP application on top of JWT), I changed the JWT
locally and said that if the name contains “RCP” then it should be in another
mode than if only in plugin-mode. But I didn’t commit
that patch yet and are not completely sure that it is the best way to work with
that. Maybe there is a better idea? Something which is always present when
having an application? Maybe we could create an extension point for that? As Chris implemented
this, I guess, he might have further ideas... Best regards, Florian Von:
jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im Auftrag
von RAVI K. THAPLIYAL Hi, The plugin mode check done by GeneralHelper has been hard
coded for “agilpro” as below: if
(Platform.getProduct().getName() != null &&
Platform.getProduct().getName().toLowerCase().contains("agilpro"))
//$NON-NLS-1$ {
return false; } else {
return true; } I’m trying to integrate JWT with my RCP app
and unless I have “agilpro” in my product name the “workflow editor”
perspective opens up the “Package Explorer” view which fails. In JWT 0.5 the
code checked for “eclipse” in the product name which seems to be the right
approach. So, how do I get around this in JWT 0.6? Regards, Ravi
|