myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scheper, Erik-Berndt" <erik-berndt.sche...@sogeti.nl>
Subject RE: how do we handle old taglib definitions in the sandbox
Date Fri, 13 Oct 2006 09:22:33 GMT
Isn't that the risk of using components of the sandbox? IMHO, sandbox
components should always be subject to change without notice. If they
are promoted to 'production quality', then so much the better.

Therefore, my personal preference would be to remove all references in
the sandbox after the promotion. I think -correct me if I'm wrong- that
the same was done for the schedule component, which was the last to be
moved from sandbox to tomahawk.

It is easy enough to change the namespace in the jsp's after an upgrade
(global search and replace) and -as I said- everyone should know that
sandbox components are used at your own risk.



-----Oorspronkelijk bericht-----
Van: news [mailto:news@sea.gmane.org] Namens Werner Punz
Verzonden: donderdag 12 oktober 2006 23:19
Aan: dev@myfaces.apache.org
Onderwerp: how do we handle old taglib definitions in the sandbox


Now that I am finally moving the first dojo component out I have one 
last remaining structural problem, how do we handle the taglib issue. As
far as I can see, once I move a component from the sandbox to 
tomahawk I will break the namespace.

Not that I mind a clear cut on this issue, but some users already have
started to use the sandbox components. Now theoretically it should be
possible to leave the tld defs in the 
sandbox while the code is moved upwards.
for the time being, with a slow deprecation of the affected entries over

time.

How are we going to handle this issue.

I need a good answer here so that I finally can set the dojo migration
to resolved.


Disclaimer:
This message contains information that may be privileged or confidential and is the property
of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized to read, print,
retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive
this message in error, please notify the sender immediately and delete all copies of this
message.

Mime
View raw message