On Sep 27, 2006, at 7:58 AM, Vladimir Ivanov wrote:

On 9/27/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:


On Sep 27, 2006, at 3:10 AM, Vladimir Ivanov wrote:

> Some times ago we discussed (and agreed?) that the HDK should
> include tests
> (also as support.jar which already included) and issue 984 was
> filed to
> build test.jar.
>
> It will nice if test.jar will be added to the new version of HDK :)

I think it's good to have the tests there too.  However, is there any
downside to this?  might we cause trouble for people using the HDK
for development (rather than the build test infra?)



If some doubts exist we can vote about it.

LOL. No reason to vote - it's a technical issue with a single true'false answer - would having a single jar of tests screw up a developer using the HDK as originally intended, namely as a means to allow them to just checking one classlib module, and use HDK to supply the rest of the required headers, libraries and classes needed for building and testing.

if the answer is "yes", then we need to figure out how to deal with it. If "no", then there's no problem and we go forward.

The question here isn't "do we want the test.jar" - because I think we all do. The question is "how do we do this conveniently and safely?"


I can not see any downside to have one more jar in the HDK.

The problem could arise if that test.jar was used before the classes in the checked-out module, masking any changes or such that the developer was making.


Thanks, Vladimir

geir

>
>
>
> Thanks, Vladimir
>
>
>
> On 7/23/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
>>
>> They are at the regular place
>>
>> http://people.apache.org/dist/incubator/harmony/snapshots
>>
>> I moved all the old classlib snapshots into /old and I'll update the
>> website accordingly.  I'll be automating this.  Also, lets not
>> make much
>> noise about this for a little while so we can test to make sure
>> there's
>> no major errors. Things seem good. I have a list of more things to
>> fix, but I realized today that I was obsessing over the snapshot
>> contents - it's not a release, and it's "good enough".
>>
>> I'd like to ditch both /old and the remaining classlib snapshots, as
>>
>> 1) they are snapshots - history doesn't matter
>>
>> 2) the classlib is now in the HDK, so we just need to adjust the
>> docs to
>> match.
>>
>> I'll do the latter, but wanted to see if anyone has a problem w/ me
>> removing /old and the last classlib snapshot.  I'll do this if I
>> don't
>> hear any protest, so either positively acknowledge this action if you
>> support it, dont' do a thing if you support or dont' care, or say
>> why we
>> shouldn't :)
>>
>> geir
>>
>> ---------------------------------------------------------------------
>> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> To unsubscribe, e-mail: harmony-dev- [EMAIL PROTECTED]
>> For additional commands, e-mail: harmony-dev-
>> [EMAIL PROTECTED]
>>
>>


---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev- [EMAIL PROTECTED]




---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to