---------- Forwarded message ---------- From: Martin Marinschek <[EMAIL PROTECTED]> Date: Jun 9, 2005 9:04 AM Subject: Re: Proposed SVN Reorg To: John Fallows <[EMAIL PROTECTED]>
Sounds tedious for developing, though... If I do a change in the share package, I will need to run this mechanism to generate the share packages from that. Plus: we really have two codebases then. I'd rather have a possibility where we just program against the common share package, and then, upon build, the share-code is moved to a new package and the tomahawk code is refactored to use this package. I haven't got a clue though if this is possible with the available build tools! regards, Martin On 6/9/05, John Fallows <[EMAIL PROTECTED]> wrote: > > You are right, the runtime problem with share persists... > > > I assume you are proposing something like Sun does in its JWSDP - > > packaging Xerces along and refactoring it to com.sun.* classes? > > This is one possibility, other suggestions are also welcome. :-) > > > And you are only proposing it for the deployed jar-files, not for > > development? > > We would need to consider the impact of all code in other parts of the > Tomahawk implementation that reference the shared codebase. Would it > use the Core package or the Tomahawk package? > > This code sharing technique is more self-contained if the Tomahawk > codebase only references the Tomahawk packages. Therefore, we might > be better off treating the shared codebase as a set of templates that > are used to generate code for the appropriate package in each of the > Core and Tomahawk projects. > > Kind Regards, > John Fallows. > >
