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

Posted to dev@synapse.apache.org by "Thilini Shanika (JIRA)" <ji...@apache.org> on 2013/05/01 22:18:16 UTC

[jira] [Commented] (SYNAPSE-928) [GSoC] Versioning of Synapse config artifacts

    [ https://issues.apache.org/jira/browse/SYNAPSE-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646890#comment-13646890 ] 

Thilini Shanika commented on SYNAPSE-928:
-----------------------------------------

I need some clarification. If we consider two same artifacts in different versions, are we going to append the versioning details to artifact file name (ie:foo-v1.0.xml or foo-v2.0.xml). If so, managing artifacts would be complicated and I believe that it might be required to maintain a hash map or a table to manage the artifacts.
                
> [GSoC] Versioning of Synapse config artifacts
> ---------------------------------------------
>
>                 Key: SYNAPSE-928
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-928
>             Project: Synapse
>          Issue Type: Improvement
>            Reporter: Kasun Indrasiri
>            Assignee: Udayanga Wickramasinghe
>            Priority: Critical
>              Labels: gsoc2013, mentor
>
> Currently non of the synapse artifacts fully support versioning mechanism. This feature is to support a new versioning strategy for all such artifacts. 
> Sequence, Proxy Service, API, Endpoints 

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org