[jbosstools-issues] [JBoss JIRA] (JBIDE-13812) openshift-java-client: get rid of external class to (de)code base64

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762263#comment-12762263 ] 

RH Bugzilla Integration commented on JBIDE-13812:
-------------------------------------------------

Gerard Ryan <gerard at ryan.lt> made a comment on [bug 902017|https://bugzilla.redhat.com/show_bug.cgi?id=902017]

Spec URL: http://galileo.fedorapeople.org/openshift-java-client/2.0.3-2/openshift-java-client.spec
SRPM URL: http://galileo.fedorapeople.org/openshift-java-client/2.0.3-2/openshift-java-client-2.0.3-2.20130320git7073708.fc18.src.rpm

Scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=5150244
(license tag in spec is wrong for this build, but is correct for the spec/srpm above)

- Updated to include all the changes that have happened upstream
-- Licensing fixed.
-- André has removed the bundled Base64Coder class

- Updated to use new maven macros.
                
> openshift-java-client: get rid of external class to (de)code base64
> -------------------------------------------------------------------
>
>                 Key: JBIDE-13812
>                 URL: https://issues.jboss.org/browse/JBIDE-13812
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 4.1.0.Alpha2
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>             Fix For: 4.1.0.Alpha2
>
>
> We're currently using a class that we copied from a different project to (de)code base64. This contradicts the fedora project which wants to package us into an rpm. They suggested to package the full library instead. 
> Since we dont want to agument the numbers of dependencies, I'll switch to JDK means to (de)code base64. This will bind us to >= JDK6 which is IMHO perfectly fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira