To reduce the risk of version conflicts and to make the release cycle
of core and tomahawk really independent, the shared classes should not
be released as JAR, but should automatically be repackaged and
inlined into impl, tomahawk, tobago, etc.
Thoughts?
Manfred
Interesting idea. Do
Once our refactoring of commons classes into namespace
org.apache.myfaces.commons.* is done we can easily change namespace
for inlining by doing String search and replace on source level:
replace org.apache.myfaces.commons by
org.apache.myfaces.impl-commons (or alike)
I already have a working
Once our refactoring of commons classes into namespace
org.apache.myfaces.commons.* is done we can easily change namespace
for inlining by doing String search and replace on source level:
replace org.apache.myfaces.commons by
org.apache.myfaces.impl-commons (or alike)
I already have a
This is a really big issue to wrap our collective heads around. Maybe
we should focus on the immediate problem first? The immediate
problem, as I see it, is that we are about to release the core and it
has shared code that will potentially conflict with the same shared
code in tomahawk.
It will
Now that I have thought about Manfred's proposal its starting to make
more sense to me. Here is my revised proposal. It will allow us to
make progress on this and still defer the final decision for several
days.
1.) Create a shared subproject. Leave the trunk empty and copy the
existing
