You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Chris (JIRA)" <ji...@apache.org> on 2019/01/24 21:02:00 UTC

[jira] [Updated] (CRYPTO-143) Release a new version to maven central

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

Chris updated CRYPTO-143:
-------------------------
    Description: 
I've been maintaining my own fork of commons-crypto for over 2 years, shortly after forking someone merged the change I wanted into the master branch.

 

It would be nice to no longer have to maintain or build my fork, or even build the master branch myself. There have been a number of fixes and enhancements in the last 2 years... Could we get a 1.0.1 release to maven central?

 

Thanks.

  was:
I've been maintaining my own fork of commons-crypto for over 2 years, shortly after forking someone merged the change I wanted into the master branch.

 

It would be nice to no longer have to maintain or build my fork, or even build the master branch myself. There have been a number of fixes and enhancements in the last 2 years... Could we get a 1.01 release to maven central?

 

Thanks.


> Release a new version to maven central
> --------------------------------------
>
>                 Key: CRYPTO-143
>                 URL: https://issues.apache.org/jira/browse/CRYPTO-143
>             Project: Commons Crypto
>          Issue Type: Task
>            Reporter: Chris
>            Priority: Major
>
> I've been maintaining my own fork of commons-crypto for over 2 years, shortly after forking someone merged the change I wanted into the master branch.
>  
> It would be nice to no longer have to maintain or build my fork, or even build the master branch myself. There have been a number of fixes and enhancements in the last 2 years... Could we get a 1.0.1 release to maven central?
>  
> Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)