[
https://issues.apache.org/jira/browse/POOL-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713254#action_12713254
]
Mark Thomas commented on POOL-141:
----------------------------------
Short version:
This might take a while.
Long version:
Not sure how we can do this for historical releases.
The release process requires that all release artefacts be generated from the
src tarball that was voted on and approved by the appropriate PMC. Since the
pool src contains no mechanism to generate src jars, the requested artefacts
can't be generated.
src jars could be generated manually (as a re-packaging of src release) but I'm
not sure how that would then fit with the ASF release policy. Since there are
legal liability issues behind the release process, we need to be sure we get
this right.
I'll leave this a couple of days to see if a more experienced commons developer
has experience of doing this in the past. If no-one pipes up, I'll follow up
with our legal folks.
> Please upload source jars to Maven Central
> ------------------------------------------
>
> Key: POOL-141
> URL: https://issues.apache.org/jira/browse/POOL-141
> Project: Commons Pool
> Issue Type: Bug
> Affects Versions: 1.2, 1.3, 1.4
> Reporter: Dave Syer
>
> Please upload source jars to Maven Central. Requests can be filed here:
> http://jira.codehaus.org/browse/MAVENUPLOAD
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
