harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr." <g...@pobox.com>
Subject Re: [general] jre and hdk snapshots posted to general snapshot site
Date Thu, 28 Sep 2006 04:30:33 GMT

On Sep 27, 2006, at 10:16 AM, Alexei Zakharov wrote:

> If we plan to use HDK for supporting developers who work on single
> module (that is a good idea IMHO)

That was one of the originally stated motivations, yes.

> then we definitely need to supply
> jar with tests. We may also supply the build file with placeholders
> for user classes & tests dirs that will be prepended to
> classpath/bootclasspath.

Something like that, yes.

geir

>
> Regards,
>
> 2006/9/27, Vladimir Ivanov <ivavladimir@gmail.com>:
>> On 9/27/06, Geir Magnusson Jr. <geir@pobox.com> wrote:
>> >
>> >
>> >
>> > If I recall, the point of the test.jar was to have a pre-built  
>> jar of
>> > tests in the HDK so that someone could setup the build-test infra
>> > using the HDK so they could run tests on their platform w/o  
>> having to
>> > build everything.  Good idea.
>>
>>
>> Yes, you are correct. This idea implemented in the jira 964.
>>
>> If that's so, then something would
>> > have to be configured to have the classlib "test" target use that
>> > jar.  All I'm saying is that how we do this is important, as we  
>> don't
>> > want to cause pain for classlib developers who use the HDK for
>> > development support.
>>
>>
>>
>> Seems, we think about different use cases.
>>
>> In my case, user can download the HDK for own platform (if we have  
>> one) run
>> tests and look on results (also, may be upload it to the harmony  
>> site). Also
>> it can be used for application run to check 'enable' status. But  
>> if this
>> user interested in Harmony development he should checkout ws and use
>> built-in ant targets to build and test updated ws.
>>
>>
>>
>> How you plan to use HDK? It looks like initial miscommunication :)
>>  thanks, Vladimir
>>
>>
>>
>> > geir
>> >
>> > >
>> > > Thanks, Vladimir
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >> > Thanks, Vladimir
>> > >> >
>> > >> > geir
>> > >> >>
>> > >> >> >
>> > >> >> >
>> > >> >> >
>> > >> >> > Thanks, Vladimir
>> > >> >> >
>> > >> >> >
>> > >> >> >
>> > >> >> > On 7/23/06, Geir Magnusson Jr <geir@pobox.com>
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-
>> > >> >> 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
>> > >> >>
>> > >> >>
>> > >>
>> > >>
>> > >>  
>> ---------------------------------------------------------------------
>> > >> 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
>> >
>> >
>>
>>
>
>
> -- 
> Alexei Zakharov,
> Intel Middleware Product Division
>
> ---------------------------------------------------------------------
> 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