Hi Scott,
Those steps look correct. But I found another problem that I think should be
fixed. The build is producing the following output:
[exec] [ERROR]
[exec]
[exec] Artifact Ids of the format maven-___-plugin are reserved for
[exec] plugins in the Group Id org.apache.maven.plugins
[exec] Please change your artifactId to the format ___-maven-plugin
[exec] In the future this error will break the build.
So I think that <artifactId>maven-pluto-plugin</artifactId> should be renamed
to <artifactId>pluto-maven-plugin</artifactId> in order to be in compliance
with naming rules.
Thanks,
Neil
> On Jan 7, 2017, at 9:05 AM, Martin Scott Nicklous <[email protected]>
> wrote:
>
> Hi,
>
> I now have a fix for the TCK build problem available in a local branch. I
> would do the following:
>
> 1) Drop the current release candidate artifacts from Nexus staging
> 2) Revert the artifact versions to 3.0.0-SNAPSHOT
> 3) Integrate my fixes (POM changes, along with 3 test case updates where the
> version string was hard-coded in the expected portlet context name *sigh*)
> 4) delete the Pluto-3.0.0 tag locally as well as at the origin
> 5) Push the integrated fixes to origin
> 6) re-run the release:prepare and release:perform steps
> 7) Upload the bundle again
> 8) resend the VOTE mail
>
> Any objections?
>
> Mit freundlichen Grüßen, / Kind regards,
> Scott Nicklous
>
> WebSphere Portal Standardization Lead & Technology Consultant
> Specification Lead, JSR 362 Portlet Specification 3.0
> IBM Commerce, Digital Experience Development
>
> Phone: +49-7031-16-4808 / E-Mail:[email protected] / Schoenaicher
> Str. 220, 71032 Boeblingen, Germany
> IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats:
> Martina Koederitz / Geschäftsführung: Dirk Wittkopp
> Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
> HRB 243294
>
