View Only
Expand all | Collapse all

Keep SourceForge as mirror and archive

This thread has been viewed 13 times
  • 1.  Keep SourceForge as mirror and archive

    Posted 08-28-2023 15:50


    Today I looked for the old versions for Pentaho on SourceForge and has been deleted without too much notice. 

    Pentaho from Hitachi Vantara Files

    I get the idea that you want some control and agreement for the license for download this software, but, today, Hitachi Vantara website is not responding correctly and even if I make it to find it, turns out that the oldest version available to download is 8.3, and right now I do have a bug with that specific version and works for me on 8.1 (This bug reported on this JIRA issue

    This is one of the many reasons that keeping the archive and use another service like SourceForge as a mirror is important, because it allow us the community to look at specific versions, download it without downtime, keep the workflow and automate process like docker builds that allow people to deploy containers without taking a huge bandwidth from the Hitachi Vantara servers.

    Please do reconsider this decision, if you want to start fresh even with any SourceForge competition, it's fine, I don't know any that does fill that field, but the point is to have a mirror in case something fails and allow developers to keep using the technology, despite the changes on the Hitachi Vantara website.

    Jose Sanchez
    Systems Engineer

  • 2.  RE: Keep SourceForge as mirror and archive

    Posted 09-01-2023 13:29

    On the JIRA.  Thank you for calling it out.  If you run spoon Debug you will see these errors in the log.

    12:45:06,355 ERROR [BSHExpression] Scripts are prevented from running by default in order to avoid potential remote code execution.  The system administrator must enable this capability.

    To resolve this: Simply Add 'org.pentaho.reporting.engine.classic.core.allowScriptEvaluation=true' ot kettle properties to allow the scripting to run and generate the images.

    I will update the JIRA with the same and Convert this to a documentation issue.

    Stephen Donovan
    General IT Consulting & Implementation Pre-eminent Professional
    Hitachi Vantara