|
»
»
»
[jira] Created: (PLUTO-548) Move portlet apis to own svn location
|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
 |
[jira] Created: (PLUTO-548) Move portlet apis to own svn location
by JIRA jira@apache.org
::
Rate this Message:
Move portlet apis to own svn location
------------------------------------- Key: PLUTO-548 URL: https://issues.apache.org/jira/browse/PLUTO-548 Project: Pluto Issue Type: Improvement Components: general Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Fix For: 2.0.0 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Assigned: (PLUTO-548) Move portlet apis to own svn location
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/PLUTO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned PLUTO-548: -------------------------------------- Assignee: Carsten Ziegeler > Move portlet apis to own svn location > ------------------------------------- > > Key: PLUTO-548 > URL: https://issues.apache.org/jira/browse/PLUTO-548 > Project: Pluto > Issue Type: Improvement > Components: general > Affects Versions: 2.0.0 > Reporter: Carsten Ziegeler > Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Assigned: (PLUTO-548) Move portlet apis to own svn location
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/PLUTO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned PLUTO-548: -------------------------------------- Assignee: (was: Carsten Ziegeler) > Move portlet apis to own svn location > ------------------------------------- > > Key: PLUTO-548 > URL: https://issues.apache.org/jira/browse/PLUTO-548 > Project: Pluto > Issue Type: Improvement > Components: general > Affects Versions: 2.0.0 > Reporter: Carsten Ziegeler > Fix For: 2.0.0 > > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Commented: (PLUTO-548) Move portlet apis to own svn location
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/PLUTO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697541#action_12697541 ] Carsten Ziegeler commented on PLUTO-548: ---------------------------------------- I've created the folder in svn and copied/moved the api's there. We didn't store the javadocs in svn so far (at least I didn't find them at src/site/resources). As I have no idea how to setup the portals website to include these new stuff, I'm reassigning this issue. > Move portlet apis to own svn location > ------------------------------------- > > Key: PLUTO-548 > URL: https://issues.apache.org/jira/browse/PLUTO-548 > Project: Pluto > Issue Type: Improvement > Components: general > Affects Versions: 2.0.0 > Reporter: Carsten Ziegeler > Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Commented: (PLUTO-548) Move portlet apis to own svn location
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/PLUTO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697613#action_12697613 ] Ate Douma commented on PLUTO-548: --------------------------------- Carsten, The javadocs are stored in svn, under src/site/resources/javadoc (see also my proposal as you copied in the description of this issue). > Move portlet apis to own svn location > ------------------------------------- > > Key: PLUTO-548 > URL: https://issues.apache.org/jira/browse/PLUTO-548 > Project: Pluto > Issue Type: Improvement > Components: general > Affects Versions: 2.0.0 > Reporter: Carsten Ziegeler > Fix For: 2.0.0 > > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Commented: (PLUTO-548) Move portlet apis to own svn location
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/PLUTO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697616#action_12697616 ] Ate Douma commented on PLUTO-548: --------------------------------- Hmm, too fast a response :) I just checked and they *are* under src/site/resources, but their real location is: src/site/resources/portlet-1.0-apidocs src/site/resources/portlet-2.0-apidocs > Move portlet apis to own svn location > ------------------------------------- > > Key: PLUTO-548 > URL: https://issues.apache.org/jira/browse/PLUTO-548 > Project: Pluto > Issue Type: Improvement > Components: general > Affects Versions: 2.0.0 > Reporter: Carsten Ziegeler > Fix For: 2.0.0 > > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Commented: (PLUTO-548) Move portlet apis to own svn location
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/PLUTO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697620#action_12697620 ] Carsten Ziegeler commented on PLUTO-548: ---------------------------------------- Hi Ate, yes there they are...hmpf...didn't see them when I looked in the afternoon. Thanks, so I'll continue with this issue in the next days. > Move portlet apis to own svn location > ------------------------------------- > > Key: PLUTO-548 > URL: https://issues.apache.org/jira/browse/PLUTO-548 > Project: Pluto > Issue Type: Improvement > Components: general > Affects Versions: 2.0.0 > Reporter: Carsten Ziegeler > Fix For: 2.0.0 > > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Resolved: (PLUTO-548) Move portlet apis to own svn location
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/PLUTO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma resolved PLUTO-548. ----------------------------- Resolution: Fixed The move of the portlet apis to /portals/portlet_spec has been done. Additional steps are now handled through issue PORTALS-14. > Move portlet apis to own svn location > ------------------------------------- > > Key: PLUTO-548 > URL: https://issues.apache.org/jira/browse/PLUTO-548 > Project: Pluto > Issue Type: Improvement > Components: general > Affects Versions: 2.0.0 > Reporter: Carsten Ziegeler > Fix For: 2.0.0 > > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
| Free embeddable forum powered by Nabble | Forum Help |
