[
https://issues.apache.org/jira/browse/DERBY-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709977#action_12709977
]
Myrna van Lunteren commented on DERBY-4220:
-------------------------------------------
Thanks for tracking this down, David.
I can't change the 10.3.3.0 files, but I modified the permissions on the
10.5.1.1 jars to match the 10.4.2.0 distro.
I had assumed that having an appropriate umask would've been enough to get the
correct permissions - apparently not. I added a note to the release process
instructions.
I also wonder if perhaps this is the reason why the automatic conversion to
maven2 has not happened?
Interestingly, as in your comment, while all the 10.4.2.0 files have group
apcvs, the ones I put out for 10.5.1.1 are of group db, and only the .asc files
are of apcvs. I changed all of the 10.5.1.1 files to be db. Can you check
please and report back if that is a problem?
> Derby 10.5.1.1 is not available in the maven repositories
> ---------------------------------------------------------
>
> Key: DERBY-4220
> URL: https://issues.apache.org/jira/browse/DERBY-4220
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.5.1.1
> Reporter: H.-Dirk Schmitt
> Priority: Minor
>
> I'm not able to find the artifacts via mvn.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
