harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hindess <mark.hind...@googlemail.com>
Subject Re: [tools] tools launching and javac
Date Thu, 25 May 2006 17:11:15 GMT

On 25 May 2006 at 7:46, Geir Magnusson Jr <geir@pobox.com> wrote:
> 
> Tim Ellison wrote:
> > Geir Magnusson Jr wrote:
> >> Tim Ellison wrote:
> >>> This is still work in progress, but thought it would be good to give a
> >>> quick update on where I am at the moment:
> > <snip>
> >>> Now you can run javac.
> >> Very cute!  Do you intend module/tools to remain not part of the build?
> > 
> > It will become part of the build once it is as-good-as done.
> > 
> > I'm trying to do a balancing act between /not/ dumping my junk into SVN
> > as I go along, and developing in the open | collaboratively.
> > Suggestions for re-balancing are more than welcome.
> 
> Only suggestion is to do a branches/tim/stuff1, work in there if you
> want people to comment (with the bonus of having it in SVN in case of
> problem).
>
> It's COW so the space usage won't be that bad, and you can just delete
> when done.

While that's true, I think that development on branches has other costs:

 * merging back into trunk

 * fewer people will pay attention - nothing personal but I might be
   less inclined to scan commits in branches/tim than trunk ;-)

Personally, I think development is moving fast enough that it's not a
problem having it in trunk.  If it hadn't been in trunk, I might have
been less inclined to test it ... and not had the incentive to fix the
bugs (HARMONY-510) on my platform of choice.

Obviously, we should avoid breaking things like this for too long but I
think the occasional breakage is a fair price to pay for not having the
other costs.

Of course, I seem to be the only one who even noticed this problem.

Regards,
 Mark.

> > <snip>
> > 
> >>> - For now, the o.a.h.tools.javac.Main wrapper looks for the compiler in
> >>> a hard-coded JAR filename (ecj_3.2RC5.jar).  Just wondering whether to
> >>> embed that JAR in the tools.jar, or look for the compiler in *.jar, or
> >>> ...?
> >> Can we give it a 'known' pattern like "harmony_javac_ecj_3.2rc5.jar" or
> >> such so we can mechanically find it w/o a long search, yet also remember
> >> the version that we're using?
> > 
> > The file ecj_3.2RC5.jar is the exact binary download from eclipse.org
> > (renamed from their generic ecj.jar).  Prefixing with harmony_ probably
> > isn't appropriate, but I could pick-up the first ecj_*.jar that I find.
> 
> I guess ecj_* works too...
> 
> 
> 
> 
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org



---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org


Mime
View raw message