Major Description
As discussed in the mailing list and suggested by Ate:
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.
Oh, one more and very important point: the maven pom.xml for the portlet-api source modules of course needs to be setup independent of the portals pom and use groupid "javax.portlet" (same as we currently have for the portlet2-api module under pluto/trunk).
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.
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".
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.