I see. Makes sense. :)
-Filip
On 2008-05-21 22:36, Howard Lewis Ship wrote:
A bit disruptive and unecessary; T4 is tapestry-framework (and
tapestry-contrib) and you bring in tapestry-annotations explicitly.
T5 is tapestry-core which brings in tapestry-ioc which brings in
tapestry5-annotations.
On Wed, May 21, 2008 at 10:36 AM, Filip S. Adamsen <[EMAIL PROTECTED]> wrote:
Ah, okay. Wouldn't it make sense to rename the rest of the artifacts as
well? Or is that too disruptive?
-Filip
On 2008-05-21 18:06, Howard Lewis Ship wrote:
There's two different artifacts thgat store annotations:
tapestry-annotations (for T4) and tapestry5-annotations (for T5).
T5's name is going to stay modified (as tapestry5-annotations) so that
we can distinguish the two when using them in the same WAR.
On Wed, May 21, 2008 at 5:15 AM, Filip S. Adamsen <[EMAIL PROTECTED]> wrote:
Everything's fine.
Annotations was moved to org.apache.tapestry:tapestry5-annotations. Now
that
T5 is in org.apache.tapestry5 it should probably be moved back.
Also, some packages changed from ...annotation to ...annotations, might
be
why you can't find @Inject and @InjectService.
-Filip
9902468 skrev:
Hi,
There's something fishy going on, as the latest nightly build of
annotations
is the 16th days. Also, source control seems to be missing all together
Inject and InjectService from ioc. Is anyone else seeing this or is it
just
me? (Moved somewhere or renamed?)
- 99
Howard Lewis Ship wrote:
As a follow on to the prior discussion ... the upgrade for users from
5.0.11 to 5.0.12 (once 5.0.12 is available) will have one big wrinkle:
Package org.apache.tapestry has been renamed to org.apache.tapestry5.
The rationale behind this is the rename will allow Tapestry 3 or
Tapestry 4 applications to co-exist with a Tapestry 5 application.
Without it, there were a number of naming conflicts.
It's unfortunate that such a large change should occur so late, pretty
much on the eve of a release candidate (5.0.12 may be a second beta,
or may be the release candidate). This represents a lack of foresight
on my part, and an evolving set of priorities.
If you are on Unix, you can update your code pretty easily:
find . -name \*.java -o -name \*.xml -o -name \*.properties | xargs
sed -i s/org\\.apache\\.tapestry\\./org.apache.tapestry5./g
This finds all Java, XML and properties files and edits them in place
to replace "org.apache.tapestry." with "org.apache.tapestry5.".
This will be necessary after tonight's nightly build (if you are using
5.0.12-SNAPSHOT) or once 5.0.12 is available (as part of the upgrade
from 5.0.11).
Thanks to everyone for all the great input; it felt that the consensus
was that tapestry5 (rather than tapestry.v5 or other suggestions) was
the best approach. Tapestry5 really is a new product in the Tapestry
product line, and this naming still feels consistent to me.
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
