[overlord-issues] [JBoss JIRA] (SRAMP-509) Unify s-ramp maven code

Brett Meyer (JIRA) issues at jboss.org
Wed Jul 16 10:56:29 EDT 2014


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

Brett Meyer commented on SRAMP-509:
-----------------------------------

See https://github.com/Governance/s-ramp/pull/454/files for examples

> Unify s-ramp maven code
> -----------------------
>
>                 Key: SRAMP-509
>                 URL: https://issues.jboss.org/browse/SRAMP-509
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>
> Both the S-ramp Wagon, Maven Repository Servlet Facade and Deploy Command (shell) uses the s-ramp client to store maven artifacts in the system.
> They make more or less the same, use the same methods to find existing artifacts and to save the artifact. Also all of them have methods that parse the input string that contains the gav, and store this info in different  mojos. 
> This means there is lot of common duplicate code. The idea is to create in s-ramp common project a new package maven and there include only one MavenMetadata class, and include one Factory class that transform from Metadata to BaseArtifactType.
> Also it is required a MavenUtil class where will be included the common operations.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the overlord-issues mailing list