Yes. It sounds like we should just wait until the 'plugin
refactoring' happens to worry about this.
This week, I'm trying to find some free time to get the 'nightly'
profile finished. I'd like to fix up s2 to do the same.
--
James Mitchell
678.910.8017
On Oct 16, 2006, at 2:59 PM, Craig McClanahan wrote:
On 10/16/06, James Mitchell <[EMAIL PROTECTED]> wrote:
Assuming we move to 1.5 (with comparable -j4 bits), would we even
have a 'tiger' or an 'annotations' project?
Probably not as a single unit ... but there's really a set of
independent
parts that might need to go in separate places:
* Annotated managed beans ... makes sense for shale-core unless we
wanted
to factor this into a separate shale-jsf-extensions module.
* Annotated view controllers ... would go into the shale-view module.
* Annotated JSF artifacts (components, renderers, etc) ... should
go the
same
place that annotated managed beans go (either shale-core or
shale-jsf-extensions).
* There is some common code for parsing faces-config.xml files that
would
need to be accessible to both worlds ... simplest approach might
be to put
that with the jsf extensions stuff and make shale-view (with the
moved
annotation
stuff) depend on it.
The thinking about shale-jsf-extensions is that this kind of
functionality
is not at all Shale specific, and should be usable in any JSF
application
that either runs on SE 5 or uses the retroweaver approach for
1.4compatibility. So, that would be my inclination for how to sort
things
out. (On the other hand, if we just moved the view controller
stuff into
shale-view, what's left in shale-tiger would essentially *be*
shale-jsf-extensions).
But, I'd also like to think of this as a 1.1 feature, so we can get
1.0.xout the door as a GA release. This will also allow a lot more
time for
experimenting to make sure the retro stuff really does work for
more than
just shale-sql-browser.
Does that make sense?
--
James Mitchell
678.910.8017
Craig
On Oct 13, 2006, at 4:51 PM, Craig McClanahan wrote:
> On 10/13/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
>>
>> + 0.9
>>
>> should tiger really be a tiger?
>
>
> C'mon, we gotta have at least *one* cool name :-). The original
> motivation
> here was that Tiger was the codename for Java SE 5.
>
> shale annotations ?
>
>
> My concern here would be that there's both annotations, and a
bunch of
> functionality that processes those annotations, in the same module.
>
> Craig
>
> On 10/13/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
>> > On 10/13/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
>> > >
>> > > Here's the abbreviated reactor summary on the framework build:
>> > >
>> > > [INFO] Shale Test Framework
>> > > [INFO] Shale Core Library
>> > > [INFO] Shale Application Controller Support
>> > > [INFO] Shale Clay Plugin
>> > > [INFO] Shale Dialog Manager Integration
>> > > [INFO] Shale Dialog Manager (Basic Implementation)
>> > > [INFO] Shale Dialog Manager (SCXML Implementation)
>> > > [INFO] Shale Remoting Support
>> > > [INFO] Shale-Spring Integration
>> > > [INFO] Shale View Controller Support
>> > > [INFO] Shale Tiger Extensions
>> > > [INFO] Shale Tiles Integration
>> > > [INFO] Shale Validator Support
>> > >
>> > > We have frameworks, libraries, supports, integrations,
>> extensions,
>> > > plugins.
>> > > * What in clay gives it a plugin status?
>> > > * What differentiates support from say, library?
>> > > * Integration means value-add based on an "outside" artifact,
>> but why
>> > > is shale-dialog an integration (we have a "native" impl)?
>> > >
>> > > Quibbling, but before someone asks me, I must ask you.
>> > >
>> > > How about ditching the library, support and plugin qualifiers?
>> How
>> > > does this look:
>> > >
>> > > [INFO] Shale Test Framework
>> > > [INFO] Shale Core
>> > > [INFO] Shale Application Controller
>> > > [INFO] Shale Clay
>> > > [INFO] Shale Dialog Manager
>> > > [INFO] Shale Dialog Manager (Basic Implementation)
>> > > [INFO] Shale Dialog Manager (SCXML Implementation)
>> > > [INFO] Shale Remoting
>> > > [INFO] Shale Spring Integration
>> > > [INFO] Shale View Controller
>> > > [INFO] Shale Tiger Extensions
>> > > [INFO] Shale Tiles Integration
>> > > [INFO] Shale Validator Integration
>> >
>> >
>> > These names work for me. +1.
>> >
>> > Craig
>> >
>> >
>> > -Rahul
>> > >
>> >
>> >
>>
>>
>> --
>> Matthias Wessendorf
>> http://tinyurl.com/fmywh
>>
>> further stuff:
>> blog: http://jroller.com/page/mwessendorf
>> mail: mwessendorf-at-gmail-dot-com
>>
