RE: Why the "shared" package renaming?

[Coloma Escribano, Ignacio]

Is the extra jar in the lib really an annoyance? Hibernate alone has 10+ jars, and a standard project has bigger problems than an extra jar. But right now if I want to create a custom component tag class, to choose the parent class (ctrl + spc) the following options are available:   HtmlInputTextTag (from two sources, taglib.html and taglib.html.ext)  which inherits from HtmlInputTextTagBase HtmlInputTextTagBase (from myfaces.shared_impl and myfaces.shared_tomahawk).   The real showstopper here is that I cannot browse the sources for the shared classes inside Eclipse (because the binaries and the sources package names do not match), and am forced to do it by hand. This is really an annoyance, because a standard project integrates more than ten frameworks; if a couple of them did the same, my performance would drop to a crawl.   Are you sure that the package renaming gives Tomahawk more independence? I would understand it if we were talking about separating layers and using interfaces, but how does the package name isolate changes?   Sorry if I sound inquisitive :)   De: Cagatay Civici [mailto:[EMAIL PROTECTED] Enviado el: martes, 20 de junio de 2006 13:08 Para: MyFaces Discussion Asunto: Re: Why the "shared" package renaming?   Hi, To get rid of another shared jar in the lib actually, also make the tomahawk more independent from the implementation. Cagatay, On 6/20/06, Coloma Escribano, Ignacio <[EMAIL PROTECTED]> wrote: Does anybody know why the shared package gets renamed for tomahawk and core?   I'm trying to use the myfaces jar in a project and link the sources to the jar (standard procedure, prepare a zip with the corresponding sources and attach it to the jar so that framework debugging is possible), but since the package names do not match I have to install/launch maven to obtain the correct package names, and repeat the procedure for each new release.   Anybody knows the rationale behind the package rename? Just asking here :)   ------------------------------------------------------------------------------------------------------------------- Este correo electrónico y, en su caso, cualquier fichero anexo al mismo, contiene información de carácter confidencial exclusivamente dirigida a su destinatario o destinatarios. Queda prohibida su divulgación, copia o distribución a terceros sin la previa autorización escrita de Indra. En el caso de haber recibido este correo electrónico por error, se ruega notificar inmediatamente esta circunstancia mediante reenvío a la dirección electrónica del remitente. POR FAVOR, ANTES DE IMPRIMIR ESTE CORREO ELECTRÓNICO CONSIDERE SU APORTACIÓN A LA CONSERVACIÓN DEL MEDIO AMBIENTE POR LA REDUCCIÓN DE CONSUMO DE PAPEL. The information in this e-mail and in any attachments is confidential and solely for the attention and use of the named addressee(s). You are hereby notified that any dissemination, distribution or copy of this communication is prohibited without the prior written consent of Indra. If you have received this communication in error, please, notify the sender by reply e-mail. PLEASE CONSIDER YOUR ENVIRONMENTAL RESPONSIBILITY BEFORE PRINTING THIS E-MAIL.