[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan resolved PORTLETBRIDGE-24.
----------------------------------------
Resolution: Fixed
This was done.
* The bridge code was moved to portlet-bridge/core and there is a trunk and a
trunk_2.0.x.
* A "site" project was created for the project's main site
* A "master-pom" project was created for the project's master pom file
* Documentation was added
* poms were re-organized and cleaned up
> Modify project structure to allow two trunks
> --------------------------------------------
>
> Key: PORTLETBRIDGE-24
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-24
> Project: MyFaces Portlet Bridge
> Issue Type: New Feature
> Components: General
> Affects Versions: 1.0.0-alpha
> Environment: JSF 1.2, Portlet 1.0, Portlet 1.2
> Reporter: Scott O'Bryan
> Assignee: Scott O'Bryan
> Fix For: 1.0.0, 1.1.0
>
>
> The PortletBridge project must be reorganized to allow the simultaneous
> development of multiple trunks. This will address the issue of being able to
> develop and enhance the Portlet Bridge for JSF 1.2 and Portlet 1.0 as well as
> the Portlet Bridge for JSF 1.2 and Portlet 2.0. Much of the code of these
> two code bases will be common, but some of the usecases and potential bugs
> are very different. Furthermore JSR-301 will produce two different
> specifications. Going forward we will want a different R.I. for each version
> of the Bridge Spec as it addresses different frameworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
