Yeah, I agree with that one. That was kinda my thought as well. Other
then the fact that it will be used for the R.I., we're going to have a
need to release versions of the bridge as EITHER JSF OR the portlet
framework rev. So we'll need to be a little more dynamic I'm thinking
on our branching strategy the the MyFaces core. Being a subproject
would definitely allow the bridge to have this flexibility.
Scott
Matthias Wessendorf wrote:
sure, that's fine.
I think somewhere like
-myfaces
-portal-bridge
like a regular subproject, since it should be independent from myfaces 1.2.x
-Matthias
On 8/17/07, Scott O'Bryan <[EMAIL PROTECTED]> wrote:
Sounds good to me. Should we open up a discussion though on "where"
this should be committed so that we can hit the ground running once the
paperwork is listed?
Scott
Matthias Wessendorf wrote:
On 8/17/07, Scott O'Bryan <[EMAIL PROTECTED]> wrote:
Hey everyone. After tearing though the bureaucracy much slower then I
would have liked, I uploaded the code to MYFACES-1664 for the JSR-301
Portlet Bridge. This code should comply with the latest public draft of
the JSR-301 specification and, once we figure out where to put this and
get it made available in svn, I'd like to see people get their hands on
it and try it out. It is going to change some things (for the better I
hope), but if there are any unresolvable issues with it, my hope is that
we can get those concerns voiced so that we can incorporate them into
the final draft.
That said, what are our next steps?
we have to wait with the commit, until that the paperworks (Schedule
B) is listed here:
http://incubator.apache.org/ip-clearance/index.html
-M
Scott
