[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-81) Poor encapsulation, passing around Aether (Artifact) objects when we should be using our own

[Karel Piwko (JIRA)]

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

Karel Piwko commented on SHRINKRES-81:
--------------------------------------

Yes, I've seen that comment. For me the most convenient would be to release master + SHRINKRES-78 as alpha-5 and let you remake the API to fit graph purposes. Let's see if this approach fits you and Andrew.
                
> Poor encapsulation, passing around Aether (Artifact) objects when we should be using our own
> --------------------------------------------------------------------------------------------
>
>                 Key: SHRINKRES-81
>                 URL: https://issues.jboss.org/browse/SHRINKRES-81
>             Project: ShrinkWrap Resolvers
>          Issue Type: Task
>            Reporter: Michal Matloka
>            Assignee: Michal Matloka
>
> TODO located in MavenStrategyBaseImpl
> // TODO Poor encapsulation, passing around Aether (Artifact) objects when we should be using our own
> // representation
> and
> MavenWorkingSession
> // TODO We're not really encapsulating much here, as we expose out Aether and Maven classes. Refactor this class and
> // usages to hide all implementation details of Maven and Aether *behind* this SPI facade
> Some of this refactors has to be made for SHRINKRES-27

--
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