You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2019/03/12 13:30:00 UTC
[jira] [Commented] (COMMONSSITE-129) [build-plugin, release-plugin]
Merge codebases
[ https://issues.apache.org/jira/browse/COMMONSSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790538#comment-16790538 ]
Gary Gregory commented on COMMONSSITE-129:
------------------------------------------
I am thinking we merge 'release' into 'build' only because the build plugin is older and maybe we should have put the release code into it in the first place. But I am on open to either. Clearly, to me, one plugin is simpler. If someone has an argument for keeping them separate or having more plugins, I'd like to hear it.
> [build-plugin, release-plugin] Merge codebases
> ----------------------------------------------
>
> Key: COMMONSSITE-129
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-129
> Project: Commons All
> Issue Type: New Feature
> Components: Commons Build Plugin, Commons Release Plugin
> Reporter: Rob Tompkins
> Priority: Major
>
> These need to both be in the same codebase. The only question remaining is which codebase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)