[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] Testing single plugin export/deployment
|
I'm running into cascading dependency issues trying to add or replace individual features. Building a full PTP update site might be my only option. What is the procedure? Is there a single over-feature that will bring in everything else?
Thanks,
Wyatt
On Wed, Jan 25, 2012 at 5:02 PM, Greg Watson
<g.watson@xxxxxxxxxxxx> wrote:
Wyatt,
Dopping plugins into the plugins or dropins folders is equivalent to installing the plugins. This means that any conflict with existing plugins or other dependency problem will prevent them from being installed. I've had problems getting this to work also. You could check the error log or .log file to see if there are any messages. You can also try adding -clean -console -consoleLog to the eclipse command line.
The best way to get this to work is to create an archive update site and install using the update manager. Now that we're using maven, creating a local update site is not that difficult. If you'd like to try this approach, let me know.
Google "eclipse dropins" will give you some useful information also.
On Jan 25, 2012, at 3:18 PM, Wyatt Spear wrote:
Specifically, our updated rm.lml.da.server isn't showing up, even when the original plugin is removed. rm.lml.da is successfully overriding the installed plugin. We're not sure what the difference is...
=Wyatt
On Tue, Jan 24, 2012 at 4:50 PM, Wyatt Spear
<wspear@xxxxxxxxxxxxxx> wrote:
Greetings,
We need to test our modified lml.da plugins on an actual eclipse installation rather than in a debug environment. This means exporting the plugins and dropping them into the dropins or plugins folder of a real eclipse install. When we do this with a new plugin (one not already present in the installation) it will show up. If a version the plugin was already present as part of the PTP update site or the PTP package, then it will not override the original version so we can't test it out. Is there any way we can force eclipse to recognize a new version of a PTP plugin that has already been installed? Removing the older versions from the plugins folder doesn't work and we're not sure what else to try.
Thanks,
Wyatt
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
