Menu

#293 Automatically check for updates

4.1
closed-fixed
5
2018-06-08
2006-12-11
No

It would be nice if OmegaT could check for itself whether there are newer versions available on SF, and offer the user to download and install them automatically. The user should then be able to choose to download and install, to defer a certain amount of time, or to never be bothered with that @%(*&$!(@*& message again.

Seeing the vast number of SF projects available, perhaps some clever person already created such functionality.

Related

Feature Requests: #1378
Feature Requests: #653

Discussion

  • Didier Briel

    Didier Briel - 2007-01-21

    Logged In: YES
    user_id=1343245
    Originator: NO

    There is a specific project:
    http://sourceforge.net/projects/luau/

    Luau (Lib Update/AutoUpdate) provides basic autoupdate functionality to software projects, allowing not only software updates to propagate quickly through ones user base but also messages and configuration updates.

    In C, unfortunately.

    I found also something related (in Java):
    http://jnlp.sourceforge.net/netx/

    Netx is a high-quality implementation of the Java Network Launching Protocol (JNLP). It downloads code over the network for applications and applets, caches it, and runs it in a secure environment.

    General Features of netx and JNLP:
    Quality: Highest quality open-source JNLP client.
    Modular: Easily add JNLP capabilities to any applications.
    Security: Run code in a sandbox or log its activities.
    Small Size: Loads from a ~130K JAR file.
    Auto-Update: No special code needed to auto-update apps.

    Didier

     
  • Aaron Madlon-Kay

    • summary: Auto-update --> Automatically check for updates
    • assigned_to: Aaron Madlon-Kay
     
  • Aaron Madlon-Kay

    I have a prototype of this functionality prepared:
    https://omegat.ci.cloudbees.com/job/omegat-prototype/88/

    It is currently blocked due to the following issue:

    OmegaT must look up the current newest version online; the way to do so that makes the most sense is to fetch a "blessed" copy of Version.properties (sourceforge.net) published to the project's SourceForge web hosting area.

    For security purposes this fetching should be done over HTTPS, never HTTP. SourceForge does support HTTPS, but only with settings that Java is incompatible with prior to 1.8u161.

    The "standard" version of OmegaT requires Java 6; until we can move the current "latest" version up to "standard" status, we can't switch SourceForge to HTTPS without breaking the Java Web Start distribution.

     
  • Didier Briel

    Didier Briel - 2018-06-01
    • status: open --> open-fixed
    • Group: future --> 4.1
     
  • Didier Briel

    Didier Briel - 2018-06-01

    Implemented in SVN [r10401]

    Didier

     

    Related

    Commit: [r10401]

  • Didier Briel

    Didier Briel - 2018-06-08
    • status: open-fixed --> closed-fixed
     
  • Didier Briel

    Didier Briel - 2018-06-08

    Closed in the released version 4.1.5 of OmegaT.

    Didier

     

Log in to post a comment.

MongoDB Logo MongoDB