[
https://issues.apache.org/jira/browse/OPENJPA-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249300#comment-14249300
]
Sebb commented on OPENJPA-2548:
-------------------------------
Please don't add 2.1.1 and 2.0.1 unless there are definite planned releases.
They have not been updated in over 3 years, so it seems unlikely, and there are
other releases that support the same JSR.
Remember that these files are published to every single 3rd party mirror, all
of whom provide their bandwidth and storage for free.
If there ever is a new release in the 2.0.x or 2.1.x series, by all means add
the new release then.
But please don't upload the existing old releases "just in case" - thanks.
> Download links for current releases are broken
> ----------------------------------------------
>
> Key: OPENJPA-2548
> URL: https://issues.apache.org/jira/browse/OPENJPA-2548
> Project: OpenJPA
> Issue Type: Bug
> Reporter: Sebb
> Assignee: Rick Curtis
> Priority: Blocker
>
> The links on the download pages to versions 2.2.2 and 2.3.0 are broken.
> This is because release publishing now must use svnpubsub, as per the e-mail
> from David Nalley dated Oct 24th.
> Releases are now published by adding files to the appropriate SVN directory,
> in this case
> https://dist.apache.org/repos/dist/release/openjpa/
> However this is empty, and so the ASF dist area is also empty, as are the
> mirrors.
> Existing releases are stored in the archives server, so the currently active
> releases (i.e. 2.2.2 & 2.3.0) can be copied from there [1] to the SVN dist
> release area. By default only PMC members have the karma to do this.
> [1] http://archive.apache.org/dist/openjpa/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
