avalon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From blorit...@apache.org
Subject cvs commit: jakarta-avalon/src/proposal/avalon5 discussion-points.txt
Date Tue, 17 Dec 2002 13:07:18 GMT
bloritsch    2002/12/17 05:07:18

  Modified:    src/proposal/avalon5 discussion-points.txt
  incorporating comments from Peter D. since he can't do it himself
  Revision  Changes    Path
  1.2       +44 -0     jakarta-avalon/src/proposal/avalon5/discussion-points.txt
  Index: discussion-points.txt
  RCS file: /home/cvs/jakarta-avalon/src/proposal/avalon5/discussion-points.txt,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- discussion-points.txt	16 Dec 2002 17:16:12 -0000	1.1
  +++ discussion-points.txt	17 Dec 2002 13:07:17 -0000	1.2
  @@ -28,6 +28,11 @@
       figure out what is the best solution.
  +    pdonald - Nah. For the sharing of one interface
  +        it does not seem useful to couple the projects.
  +	    Commons also passes down objects which is not a
  +	    great idea as it means that you are binding to
  +	    specific subsystems if you use that "feature".
  @@ -46,7 +51,38 @@
       bloritsch - We are in desparate need of a unified
           and simple build architecture.  IMO, Maven is
           the best choice we have available.
  +    pdonald - I am using maven to build the site for
  +        all the stuff I am moving out of Avalon. It is
  +        absolutely fantastic. There is a few hickups
  +        and it is definetly still alpha quality but it
  +        is better than what we have now. The great thing
  +        about it is that a lot of people have already
  +        done all the integration work and it is easy
  +        enough to get coverage, junit etc all integrated
  +        in.
  +    pdonald - The negatives:
  +        - speed (not a great problem in CVS version because
  +          of "console" plugin)
  +        - project inheritance is not fully done so we have
  +          to copy a 3 line property file around when we are
  +          using - however this is supposed to be fixed before 
  +          next release
  +        - inheritance of maven.xmls is not possibel as far as
  +          I know so you can end up copying some around. Not
  +          sure if this will be fixed .. but will become 
  +          irrelevent if next point picked up ...
  +        - painful to manage your own plugins if not in maven
  +          CVS. I believe this will hopefully be fixed sometime
  +          in the future ... maybe :)
  +        I am using their last release and it seems to work
  +        well. However it may be best to wait till next release
  +        before converting Avalon (Just to avoid a few bugs that
  +        the last Maven has). However I suggest we keep our current
  +        ant build system around until Maven gets the ability to
  +        easily install plugins on per project basis at which
  +        point we can dump our exisitng build system.
  @@ -65,6 +101,10 @@
           longer supported or needed (like Testlet).
           It would be a good way to clean out the cruft,
           and help manage the focus and scope of Avalon.
  +    pdonald - Yes, BUT Maybe we should wait for subversion
  +        (subversion.tigris.org) - it looks like a much
  +        better tool and if we go to that we can do the
  +        big re-arrange then.
  @@ -80,6 +120,7 @@
       bloritsch - It would help establish the
           Avalon brand instead of Jakarta.
  +    pdonald - +1 (aka me too)
  @@ -94,5 +135,8 @@
       sure we have mirror friendly distributions.
       bloritsch - Again we are solidifying Avalon.
  +    pdonald - +1, though personally I would prefer
  +        that our website removed some of the crap 
  +        that it has about.

To unsubscribe, e-mail:   <mailto:avalon-cvs-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-cvs-help@jakarta.apache.org>

View raw message