On Thu, Apr 20, 2017 at 1:44 PM, Neil Griffin <neil.grif...@portletfaces.org> wrote: > Dear Apache Portals Pluto Team and community, > > I have staged a release candidate for the new Apache Portals Pluto Maven > Archetypes 3.0.0 release, > which includes the following two artifacts: > > <groupId>org.apache.portals.pluto.archetype</groupId> > <artifactId>bean-portlet-archetype</artifactId> > <packaging>maven-archetype</packaging> > > <groupId>org.apache.portals.pluto.archetype</groupId> > <artifactId>generic-portlet-archetype</artifactId> > <packaging>maven-archetype</packaging> > > Please review the release candidate which is available from the following > maven staging repository: > https://repository.apache.org/content/repositories/orgapacheportals-1016
This link doesn't work for me. I managed to find the staging repo at https://repository.apache.org/#stagingRepositories. It shows "404 - Repository "orgapacheportals-1016 (staging: open)" [id=orgapacheportals-1016] exists but is not exposed" when clicked on, regardless whether or not I signed in https://repository.apache.org/. Does anyone know the reason? > > This vote is open for the next 72 hours. > > Please cast your vote: I'm not sure if it is desirable to release this. When I downloaded the bean-portlet-archetype-3.0.0-source-release.zip from the Nexus, I could hardly find source files with Apache License header [1]. Most files are missing the license header. Wouldn't it be more desirable to correct this issue first? And, one minor thing to remark is that the archetype is using log4j v1, neither slf4j nor log4j v2. AFAIK, pluto project itself and its submodules such as container have used slf4j as logging API and log4j as a default binding. Not a major, but just something to consider later perhaps... Kind regards, Woonsan [1] http://www.apache.org/legal/src-headers.html#headers > > [ ] +1 for Release > [ ] 0 for Don't care > [ ] -1 Don't release (do provide a reason then) > > Thanks, > > Neil
