Hi
It seems we need a goal on myfaces javascript plugin that do the namespace
remapping.
Right now we have this configuration in shared
shared/trunk
core
shared-impl
shared-tomahawk
shared-orchestra
Why that code lives in shared? I was thinking that "shared core" code should
be on myfaces-impl, and "shared core" project should just unpack the sources
(including the javascript ones), but not on a temporal directory, rather on
src/main/java. Then, from that project we can build shared-tomahawk and
shared-orchestra (or anyone required) and from that one move to tomahawk. In
that way we can release that code in a independent way, but all that
foundation code lives where it should be: on myfaces impl. After all, almost
all changes of myfaces shared code comes from myfaces-impl.
regards,
Leonardo
2010/9/3 Werner Punz <[email protected]>
> Hi everyone, I want to start a thinktank here on how to proceed.
> First of all I personally think we have some great stuff in our javascripts
> which might come in handy for Tomahawk and co, like meta logging,
> inheritance, very fast dom routines,which revert to browser fallbacks and
> html5 selectors wherever present, easy to use ajax (which does not need to
> be used necessarily within a jsf.js context) and so on. In the long run it
> also would make sense to crossport a selector API from one of the big libs,
> but not in the sense of being in the core but being in one of the
> extensions.
>
> But my problem for now is following, is every change in a core version
> might then break something in our subprojects. So here is a proposal of
> me...
>
> To be shared into a subproject we have to do a namespace remapping.
> This probably can easily be done by a simple regexp search and replace on
> the source files.
>
> For instance myfaces.core. would become myfaces.tomahawk.core.10 etc...
> That way we can safely branch a version for tomahawk and then move on...
>
> I am not sure how we reorganize that, it is either manual branching or done
> somehow in the build process. Moving the scripts to shared might be a way,
> but this would make things more complicated I guess.
> Manual branching from time to time for a tomahawk release might be another
> one, if we really want to use the core stuff in Tom...
>
> But that all depends on whether the complibs want to use our stuff or want
> to stay entirely indepdendend.
>
>
>
