Stefan Drissen (Exact) asked a question.

February 6, 2026 at 2:37 PM
propack classpath?

So, thanks to @Gilles Querret (Riverside Software)​ I am looking at using apl instead of pl to package r-code. The propack documentation example shows:

  1. <taskdef name="propack"
  2. classname="com.progress.oeant.task.ProPack"
  3. classpath="${env.DLC}/java/oe/oeant-12.7.0.jar" />

Which, surprise, surprise, does not work on my 12.8.9 installation since it does not have an oeant-12.7.0.jar. I can point the classpath at oeant-12.8.9.jar which does exist, but this seems like an awful idea waiting to trip itself up after every upgrade.

 

What is the normal way for resolving this?

 

  • 3 answers
  • 143 views
Simon Prinsloo, Rob Fitzpatrick, and Mike Fechner like this.

  • Lieven De Foor (TVH Parts Holding)

    You can probably adjust this to use shortVersion instead of the hard coded version number?

    1. <pct:progress_version shortVersion="short"/>
    2. <taskdef name="propack"
    3. classname="com.progress.oeant.task.ProPack"
    4. classpath="${env.DLC}/java/oe/oeant-${short}.jar" />

     

    Selected as Best

  • Gilles Querret (Riverside Software)

    You already mentioned it on GitHub but the standard Jar task can be used to create apl files. I have to admit I didn't know propack was also available as an Ant task ; curious to know what propack brings over the Jar task.

  • Lieven De Foor (TVH Parts Holding)

    You can probably adjust this to use shortVersion instead of the hard coded version number?

    1. <pct:progress_version shortVersion="short"/>
    2. <taskdef name="propack"
    3. classname="com.progress.oeant.task.ProPack"
    4. classpath="${env.DLC}/java/oe/oeant-${short}.jar" />

     

    Selected as Best

  • Stefan Drissen (Exact)

    Beware that the 13.0 version file contains:

    1. OpenEdge Release 13.0 as of Fri Jan 23 10:42:24 EST 2026

    While the jar is named oeant-13.0.0.