Re: [VOTE] Release Apache Portals Pluto 3.0.0

Actually, the Security Mapping Test passes if you login with the tomcat
userid rather than the pluto user. The other messages #3, #4, #5, and #6
are informational warnings rather failures, I believe.

Unfortunately, I found another problem that I believe we need to fix. I
tried to deploy and run the TCK on the 3.0.0. driver candidate and
discovered that for the TCK modules that provide a page file containing
multiple pages (such as V2RequestTests), the additionalPages.xml file
contains hard coded versions in the context name as follows:

======
...
<page xmlns="" name="V2RequestTestsRender" uri=
"/WEB-INF/themes/pluto-default-theme.jsp">
<portlet context="/tck-V2RequestTests-3.0-SNAPSHOT" name=
"RequestTests_PortletRequest_ApiRender"/>
<portlet context="/tck-V2RequestTests-3.0-SNAPSHOT" name=
"RequestTests_RenderRequest_ApiRender"/>
</page>
...
======

This renders the affected TCK modules unusable with the generated TCK page
file, because the generated TCK page file contains the hard-coded versions
in the context name. To fix it, I'm going to have to edit the TCK POM to
provide filtering and edit all of the additionalPages.xml files
accordingly.

So  I feel I need to vote -1 for the release. Sorry ... Unless someone sees
a way around the problem, I think we need to do it over.

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




From:	Woonsan Ko <[email protected]>
To:	Portals PMC <[email protected]>
Cc:	[email protected]
Date:	05.01.2017 21:45
Subject:	Re: [VOTE] Release Apache Portals Pluto 3.0.0



+1 for Release.

I don't think this can block the release, but just FYI, when I run the
tomcat8 bundle zip locally, I observe the following TCK tests failing:
- Test Portlet: #14. Security Mapping Test
- JSR 286 Tests: #3. EventFilterTest: PLT [unknown] -
checkTriggerEventFromActionPhase
- JSR 286 Tests: #4. SimplePayloadEventTest: PLT 15.2.3 -
checkFireEventsFromActionPhase
- JSR 286 Tests: # 5.Complex Payload Event Test: PLT 15.2.3 -
checkFireEventsFromActionPhase
- JSR 286 Tests: # 6.Public Render Parameter Test

Are those known?

Regards,

Woonsan


On Thu, Jan 5, 2017 at 3:09 PM, DavidSeanTaylor <[email protected]>
wrote:
> Dear Apache Portals Pluto Team and community,
>
> I've staged a release candidate for the new Apache Portals Pluto 3.0.0
> release.
>
> This release candidate includes:
>
> * a fully compliant Reference Implementation of the new Portlet 3.0
> Specification per JCR-362
>     https://www.jcp.org/en/jsr/detail?id=362
> * a completed TCK (Test Compatibility Kit) for Portlet Spec 3.0
>
> The Portlet API 3.0 specification has been approved by the JCP (JSR 362
> Public Review Ballot), see:
>
> https://www.jcp.org/en/jsr/results?id=5896
>
>
>
> Please review the release candidate for this project which is available
from
> the following maven staging repository:
>
> https://repository.apache.org/content/repositories/orgapacheportals-1012/
>
> There you will find all source distributions, as well as all Pluto 3.0
jar
> and javadocs artifacts.
>
>
> Additionally, the Portlet API 3.0 (javax.portlet) source, jar and javadoc
> artifacts are packaged here:
>
>
https://repository.apache.org/content/repositories/orgapacheportals-1012/javax/portlet/portlet-api/3.0.0/

>
>
> We are also providing a binary bundle of the Pluto Container with an
Tomcat8
> ready to use built from the 3.0.0 release candidate:
>
>
https://repository.apache.org/content/repositories/orgapacheportals-1013/org/apache/portals/pluto/pluto-bundle/3.0.0/

>
>
> The bundle can be tested by unzipping it, and running start.sh from the
bin
> directory, then navigating to http://localhost:8080/pluto, and login as
> pluto/pluto.
>
>
> The release notes are available here:
>
>
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10560&version=12338869

>
>
> The KEYS file to verify the release artifacts signature can be found
here:
>
> https://dist.apache.org/repos/dist/release/portals/pluto/KEYS
>
>
> Please review the release candidates and vote on releasing Apache Portals
> Pluto 3.0.0
>
> This vote is open for the next 72 hours.
>
> Please cast your vote:
>
> [ ] +1 for Release
> [ ]  0  for Don't care
> [ ] -1 Don't release (do provide a reason then)
>
> Regards,
>
> David Sean Taylor
>
>