tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Chiumenti" <kium...@gmail.com>
Subject Re: SVN reorganization
Date Tue, 24 Apr 2007 16:55:45 GMT
I know that a lot of ppl use eclipse, but refactoring a project based on an
ide limitation, remind me that evil of MSIE.
Do we really want a weak project structure because of an ide limitation ?

On 4/24/07, Howard Lewis Ship <hlship@gmail.com> wrote:
>
> Eclipse doesn't do nested projects, otherwise I would structure it that
> way.  And it is important to me to allow everything to be built seperately
> and in layers (I expect tapestry-ioc to be used outside of Tapestry, for
> example).
>
> On 4/24/07, Massimo Lusetti <mlusetti@gmail.com> wrote:
> >
> > On 4/24/07, Howard Lewis Ship <hlship@gmail.com> wrote:
> >
> > > I think things are back the way they should be.
> >
> > Great news!
> > I've only one question, why you have kept the
> > tapestry-(project|core|ioc...) distinction ? Personally i would have
> > preferred that trunk would have become -project which contained all
> > other submodules (core, ioc etc). Any reason why to keep that besides
> > keeping unchanched poms?
> >
> > --
> > Massimo
> > http://meridio.blogspot.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
> --
> Howard M. Lewis Ship
> TWD Consulting, Inc.
> Independent J2EE / Open-Source Java Consultant
> Creator and PMC Chair, Apache Tapestry
> Creator, Apache HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work.  http://howardlewisship.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message