[ 
https://issues.apache.org/jira/browse/FOP-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

thoth updated FOP-3221:
-----------------------
    Description: 
FOP binary is available through a direct download link, currently it is [this 
one|https://www.apache.org/dyn/closer.cgi?filename=/xmlgraphics/fop/binaries/fop-2.10-bin.zip&action=download].
 Each time a new FOP version is released, former binary versions are removed 
from the server, and the old link is no longer valid. Only the link with the 
current version is obviously valid.

I am using the FOP binary as part of a GitLab pipeline. In this pipeline, the 
FOP binary is downloaded and unzipped, so that it can be used in further steps. 
This is necessary, since the docker images I'm supposed to use does not provide 
FOP, unfortunately.

What happens is that every time, a new FOP version is released, the link dies 
and breaks the pipeline. This requires me to update the download link to the 
FOP binary each time, which is a bit weird.

I guess this issue affects more people than just me.

It would be really super cool, if there was a place with archived FOP binaries 
with permanent links that can be referenced, and/or a sym link, e.g. 
"{{current}}", in the download directory, so that requests to 
{{/xmlgraphics/fop/binaries/current}} always point to the latest version of the 
zipped binary, in this case {{fop-2.10.zip}}.

  was:
FOP binary is available through a direct download link, currently it is [this 
one|https://www.apache.org/dyn/closer.cgi?filename=/xmlgraphics/fop/binaries/fop-2.10-bin.zip&action=download].
 Each time a new FOP version is released, former binary versions are removed 
from the server, and the old link is no longer valid. Only the link with the 
current version is obviously valid.

I am using the FOP binary as part of a GitLab pipeline. In this pipeline, the 
FOP binary is downloaded and unzipped, so that it can be used in further steps. 
This is necessary, since the docker images I'm supposed to use do not provide 
FOP, unfortunately.

What happens is that every time, a new FOP version is released, the link dies 
and breaks the pipeline. This requires me to update the download link to the 
FOP binary each time, which is a bit weird.

I guess this issue affects more people than just me.

It would be really super cool, if there was a place with archived FOP binaries 
with permanent links that can be referenced, and/or a sym link, e.g. 
"{{current}}", in the download directory, so that requests to 
{{/xmlgraphics/fop/binaries/current}} always point to the latest version of the 
zipped binary, in this case {{fop-2.10.zip}}.


> Keep download links or provide a version-independent link
> ---------------------------------------------------------
>
>                 Key: FOP-3221
>                 URL: https://issues.apache.org/jira/browse/FOP-3221
>             Project: FOP
>          Issue Type: Improvement
>         Environment: download website
>            Reporter: thoth
>            Priority: Minor
>
> FOP binary is available through a direct download link, currently it is [this 
> one|https://www.apache.org/dyn/closer.cgi?filename=/xmlgraphics/fop/binaries/fop-2.10-bin.zip&action=download].
>  Each time a new FOP version is released, former binary versions are removed 
> from the server, and the old link is no longer valid. Only the link with the 
> current version is obviously valid.
> I am using the FOP binary as part of a GitLab pipeline. In this pipeline, the 
> FOP binary is downloaded and unzipped, so that it can be used in further 
> steps. This is necessary, since the docker images I'm supposed to use does 
> not provide FOP, unfortunately.
> What happens is that every time, a new FOP version is released, the link dies 
> and breaks the pipeline. This requires me to update the download link to the 
> FOP binary each time, which is a bit weird.
> I guess this issue affects more people than just me.
> It would be really super cool, if there was a place with archived FOP 
> binaries with permanent links that can be referenced, and/or a sym link, e.g. 
> "{{current}}", in the download directory, so that requests to 
> {{/xmlgraphics/fop/binaries/current}} always point to the latest version of 
> the zipped binary, in this case {{fop-2.10.zip}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to