Ate Douma wrote: > Hi Carsten, > > I'm +1 on doing this. > > My suggestion is to create a /portals/portlet-spec svn folder. > Underneath that, we then could have: > /portlet-api-1.0/ > /portlet-api-2.0/ > /src/site/ > /pom.xml > > The portlet-api-1.0/src/main/java folder should be a svn *copy* from: > /portals/pluto/tags/import/src/api > > The portlet-api-2.0/src/main/java folder should be a svn *move* from: > /portals/pluto/trunk/portlet2-api/src/main/java > > The /src/site/resources/javadoc/portlet-api-1.0/ folder should be a svn > *move* from: > /portals/pluto/trunk/src/site/resources/portlet-1.0-apidocs/ > > The /src/site/resources/javadoc/portlet-api-2.0/ folder should be a svn > *move* from: > /portals/pluto/trunk/src/site/resources/portlet-2.0-apidocs/ > > And of course, for all the above new appropriate maven 2 build > configurations will need to be setup. > > This way, we can publish the portlet-api javadocs through: > > http://portals.apache.org/porlet-spec/portlet-api-1.0/ > http://portals.apache.org/porlet-spec/portlet-api-2.0/ > > and of course provide a general overview page (possibly with further > pointers and info) at: > > http://portals.apache.org/portlet-spec/ > > I think that would be *very* helpful. > Good plan! I'll add an issue for this and try to move/copy the stuff in the next days.
> Finding the right portlet api javadoc online always has been "messy", > and using the above would finally give them a very clear and easy to > remember "home". Yepp > > One more thing with regard to the api *source*: Its obvious we cannot do > "releases" of these as they are JCP spec bound. > So, IMO there is no need for using /trunk, /tags, etc. svn sub folders > for them. Agreed. > However, as you know the portlet-api-2.0 OSGi meta-data configuration > currently in pluto trunk is different from the *currently* provided > download at the JCP, but that will be fixed (hopefully soon) by the > JSR-286 spec lead with an errata. > Furthermore, the new JSR-286 spec lead (Scott Nicklous) gave his OK for > us (Portals) to push out a newly build portlet-api-2.0.jar with (only) > the fixed OSGi configuration to Maven central repository. > This however would still be a "2.0" release. Which is not really possible as we can change the central maven repo or any local copies of people, but an updated errata release will fix this. Carsten -- Carsten Ziegeler [email protected]
