Eclipse update manager TUM released

Home

News: Eclipse update manager TUM released

  1. Eclipse update manager TUM released (9 messages)

    Tikal, an open source provider of development and deployment suites, has released Tikal Update Manager (TUM), an Eclipse update manager for installing and updating Eclipse distributions of open source application development and deployment plug-ins and tools. Tikal compares TUM to Yellow dog Updater (YUM), an open source command line package management utility for RPM-compatible Linux systems. TUM's GUI provides a quick overview of all available plug-ins and tools. You can then browse, install, update or remove a variety of open source plug-ins, as well as runtime products and components such as JBoss AS and MySQL DB (downloadable as plug-ins). TUM connects to any Eclipse update site, including a Callisto-like repository, allowing interaction with the repository's contents and categorization metadata. Tikal also provides additional repositories where you can download and install free open source tools like Tikal's pre-integrated suites for application development, configuration management, QA and delivery. TUM is open source under LGPL and is fully documented. What do you think of TUM?

    Threaded Messages (9)

  2. splash screen[ Go to top ]

    Eclipse could have a better install/update manager. Maybe integration with eclipse-plugins or eclipseplugincentral , that would be nice :) Managing remote sites should be like how maven manages projects. But Tikal did something evil, they messed with eclipse's splashscreen!!!
  3. splash screen[ Go to top ]

    splash can be removed, just uninstall "tikal eclipse platform" feature patch, at your initial install it's selected by default, we will fix that
  4. Re: splash screen[ Go to top ]

    Yes, that works! (after the second launch of eclipse) The update manager works very nice, took me just a few seconds to install all of my favorite plugins. I really like the option "Add required" in the in queue-tab.
  5. Re: splash screen[ Go to top ]

    Yes, that works! (after the second launch of eclipse)

    The update manager works very nice, took me just a few seconds to install all of my favorite plugins. I really like the option "Add required" in the in queue-tab.
    Thanks for the feedback. Now the "Tikal Eclipse Platform" is not selected by default.
  6. I just used TUM to update thru the Callisto discovery update site, which has several mirror sites just like other eclipse-dot-org made plugins, but TUM did not ask me to choose a mirror site, it just used the first site of all mirror sites instead, which made the updating slow enough to force me interrupt it. Has anyone met this problem?
  7. I just used TUM to update thru the Callisto discovery update site, which has several mirror sites just like other eclipse-dot-org made plugins, but TUM did not ask me to choose a mirror site, it just used the first site of all mirror sites instead, which made the updating slow enough to force me interrupt it. Has anyone met this problem?
    TUM select mirror sites automatically, you can disable it by unchecking "Automatically select mirrors" at "Repos" pane.
  8. can not start Tikal Update Manager[ Go to top ]

    I use eclipse 3.2 on Windows. After I installed Tikal Update Manager the menu item "TUM Updates" shows up in Help menu however when I try to run it I get a pop-up window with the following error message: "The chosen operation is not currently available.". What would be the problem? I am behind a corporate firewall and standard eclipse updates work fine.
  9. I have opened a bug at sourceforge http://sourceforge.net/tracker/index.php?func=detail&aid=1544356&group_id=145305&atid=761524 Could you provide more information there ?
  10. I use eclipse 3.2 on Windows. After I installed Tikal Update Manager the menu item "TUM Updates" shows up in Help menu however when I try to run it I get a pop-up window with the following error message: "The chosen operation is not currently available.". What would be the problem? I am behind a corporate firewall and standard eclipse updates work fine.
    The error occur due to JDK 1.4.x usage, please launch your eclipse using JDK5. we will update our docs.