Fixing the 3.0.0 build

"Martin Scott Nicklous" <[email protected]>
Newsgroups gmane.comp.jakarta.pluto.devel
Message-ID <OF302FC60C.D0FBB67D-ONC12580A1.004C053A-C12580A1.004D6CAD@notes.na.collabserv.com>

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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.