harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Qiu" <sean.xx....@gmail.com>
Subject Re: [buildtest2] Shall we Integrate mauve to BTI 2.0
Date Wed, 01 Aug 2007 06:27:57 GMT
2007/8/1, Alexey Varlamov <alexey.v.varlamov@gmail.com>:
>
> 2007/8/1, Sean Qiu <sean.xx.qiu@gmail.com>:
> > Mauve test will generate results as html files.
> > Its XMLGenerate class is a empty class who did nothing at all.
> > So we cannot merge the result to our BTI,
> > since Cruise Control can only merge xml file as junit generated. (Am i
> > right?)
> Using the default publisher, yes we cannot. But you are free to create
> a custom publisher and format alerts as you like.


Great idea. Thanks Alexey.

>
> > I can write a subclass inheriting XMLGenerate to generate proper xml
> files
> > for merging.
> > But i think this is prohibited work for Harmony.
> We cannot put such class to our repository for sure :(
>
> >
> > Or we can just reformat the html files to get wanted xml results, shall
> we?
> > Any suggentions? Comments?
> It should work, but looks a bit too circuitous route. A custom
> publisher for BTI which would just attach zipped html files is a first
> simple step in right direction :)
>
> Still there is an extra inconvenience, the attachments come uuencoded
> in alerts list. Probably this can be re-configured - dev list has no
> such problem.


>
> > Thanks.
> >
> > 2007/7/26, Tim Ellison <t.p.ellison@gmail.com>:
> > >
> > > Alexei Fedotov wrote:
> > > > I'm trying to understand the link [1] you've send. Do I understand
> > > > correctly the paragraph "YOU MAY include code within the Apache
> > > > product necessary to achieve compatibility with a prohibited work
> > > > [...]" applies to this case?
> > >
> > > Well the whole document applies to our project, but in particular we
> > > should be mindful of the scenarios that describe how we can interact
> > > with Mauve code.
> > >
> > > http://people.apache.org/~cliffs/3party.html#options-scenarios
> > >
> > > Regards,
> > > Tim
> > >
> > > >
> > > > [1] http://people.apache.org/~cliffs/3party.html
> > > >
> > > > On 7/25/07, Tim Ellison <t.p.ellison@gmail.com> wrote:
> > > >> Alexei Fedotov wrote:
> > > >> > Hello Sean,
> > > >> >
> > > >> > Disclaimer: I'm not a lawyer. :-)
> > > >>
> > > >> Me neither, and when we are done discussing we might want to do a
> > > >> gut-check with the legal discuss mailing list to ensure they
> approve
> > > our
> > > >> proposed actions...that said...
> > > >>
> > > >> > Mauve has a pure GPL license [1]. Executing mauve tests is
> > > >> > establishing a dynamic link between Harmony VM an these tests.
> For me
> > > >> > this means that the linking infrastructure is tainted with GPL
> and
> > > >> > cannot be a part of BTI. In other words, if you commit such
> > > >> > infrastructure into Apache repository, the link may help FSF
to
> claim
> > > >> > that Harmony VM links to GPL-ed code and should be re-licensed
> under
> > > >> > GPL.
> > > >> >
> > > >> > All, please correct me if I'm wrong. Thanks.
> > > >>
> > > >> There is no intent to redistribute the tests from Harmony, just
> enable
> > > >> them for the end user.  There is an analogy with the performance
> > > >> infrastructure we just voted on which has adapters to SPEC
> benchmarks
> > > >> that are not part of Harmony.
> > > >>
> > > >> Regards,
> > > >> Tim
> > > >>
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Sean Qiu
> >
>



-- 
Sean Qiu

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