> On May 18, 2018, at 3:30 PM, Michael Osipov wrote:
>
> Am 2018-05-17 um 15:12 schrieb Rob Tompkins:
> > Hello maven guys,
> >
> > Over on commons we’ve been writing our own release-plugin
>
> What is wrong with the current Maven Release Plugin and why are y
Hello maven guys,
Over on commons we’ve been writing our own release-plugin, and have the idea to
do the release promotion using a mojo. The goal here would be do do something
analogous to svn mv . Is that available in the [maven-scm-api]?
At first read it doesn’t look like it. Would you inste
I’ve found some success now using
org.apache.maven.plugin-testing:maven-plugin-testing-harness:3.3.0. You may
disregard the following questions.
Cheers,
-Rob
> On Jan 6, 2018, at 2:03 PM, Rob Tompkins wrote:
>
> Hello again Maven Team,
>
> I’ve made substantive progress towa
our release automation.
Many thanks and all the best,
-Rob
> On Dec 28, 2017, at 4:53 PM, Rob Tompkins wrote:
>
>
>
>> On Dec 28, 2017, at 4:05 AM, Hervé BOUTEMY wrote:
>>
>> Hi Rob,
>>
>> one additional point: currently, for Maven itself, instead of
M-R/view/Maven/job/dist-tool-plugin/site/
> dist-tool-check-source-release.html
>
> [3] https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/
> dist-tool-check-index-page.html
>
> [4] https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/
> dis
Stephen,
I can’t thank you enough for your reply. I’ll take your suggestions and
continue to sandbox around using the maven-release-plugin as a guideline.
All the best and happy holidays,
-Rob
> On Dec 26, 2017, at 5:27 AM, Stephen Connolly
> wrote:
>
> On Tue 26 Dec 2017 a
Hello all,
Pardon, maybe this should have gone to your @user list, but why not ping the
dev crew. I’ve been playing around the ideas surrounding our fairly manual
release process for the components in Commons, and I was hoping for some
insights.
Scripting the version changes isn’t really that
