The Artima Developer Community
Sponsored Link

Java Buzz Forum
Eclipse EquinoxP2 and TopCased

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Fred Grott

Posts: 4361
Nickname: shareme
Registered: Jan, 2003

Fred Grott is Lead Developer-CEO of ShareMe Technologies LLC -The Mobile Future
Eclipse EquinoxP2 and TopCased Posted: May 23, 2008 8:43 PM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by Fred Grott.
Original Post: Eclipse EquinoxP2 and TopCased
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology.
Latest Java Buzz Posts
Latest Java Buzz Posts by Fred Grott
Latest Posts From ShareMe Technologies LLC-The Mobile Future

Advertisement
Now for a different approach to plug-in migration to Eclipse Equinox P2. Basically, I am going to start with Topcased manually dropped in the drop-ins folder. Than, I will load all my simple 3d party plug-ins. Than add rest of update sites to 3rd party plug-ins.

Okay, UI wise what I have noticed thus far and have to turn a bug report in is that sometimes your choice selection in the update manager gets lost or disappears. On Capabilities Preferences the classic update choice is never remembered after the re-starting of Eclipse.

I should have better luck this time in getting plug-ins to load and thus should have some screen shots up tonight. the whole idea is to develop a labor cost saving way to migrate that 3rd party folder of plug-ins we all have to Eclipse 3.4 using the Equinox P2 Update manager. My first thought was pull in that 3rd party plug-in folder as an update url and just read the plug-ins in either via the update url in folder or etc.

But, the problem with that approach is that you might have such items as Acceleo in the mix which has not updated to eclipse 3.4 yet and you may have other similar problems with other complex plug-ins. Maybe vary the approach and only load in the simple plug-ins I absolutely know will work in Eclipse 3.4 for example, Lint4j and etc?

On a side note I am searching for paid start up telecommuting project/gig work and yo can contact me through my linkedin profile on the right side of this blog.

Read: Eclipse EquinoxP2 and TopCased

Topic: RIA Round-table at RedMonkOne from PeopleOverProcess.com Previous Topic   Next Topic Topic: Enterprise vs. Consumer

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use