Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of alexei.fedotov@gmail.com
 designates 209.85.146.183 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=h/dzFDb7FDRtLC0WGrfwM2MDyNfObZdw9zjY1zA5FG6HmWlJpKfSn1s1+DmFWvFMeCehavFKOi1I8wjaX9kZJTxWVpYHD5C3YjOYKjEbNsYdRhYZPTYQguZSnF91SrrgB2VfTLXyIIuQnAUm2xuhFjgXvT2DMv1t9jz8Lf4dQdA=
Message-ID: <c30d70960804220335r641a6ffar65066a6938f96bef@mail.gmail.com>
Date: Tue, 22 Apr 2008 14:35:00 +0400
From: "Alexei Fedotov" <alexei.fedotov@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [classlib][archive] Parsing invalid manifest (was: Re: classlib
 archive changed broke EUT/update)
In-Reply-To: <480DBDF7.2060504@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <587698b80804170142x29028cb6vc2a8869832d9e0c3@mail.gmail.com>
	 <48085A1B.2030603@gmail.com>
	 <c30d70960804180127h5b3dcff2m6d798912eac8d3fb@mail.gmail.com>
	 <587698b80804180145j7e90557dwb327e1b66acd52a6@mail.gmail.com>
	 <3b3f27c60804180925v602c5799hc116ca6a1ba8a0d9@mail.gmail.com>
	 <480DBDF7.2060504@gmail.com>

Hello Tim,
I believe it worth considering a kludge after a problematic app
manifests itself.

Thanks.

On Tue, Apr 22, 2008 at 2:29 PM, Tim Ellison <t.p.ellison@gmail.com> wrote:
> Even though the manifest is invalid according to the spec, shouldn't we be
> parsing it the same way as the RI for compatibility reasons?
>
>  I wonder how many apps have invalid manifests.
>
>  Regards,
>  Tim
>
>  Nathan Beyer wrote:
>
> > Careful, the test isn't necessarily invalid - that's quick assumption. It
> > needs to be verified that the test isn't dyanamically generating a
> manifest
> > with Harmony's classlib; it's possible that Harmony's classlib is creating
> > the invalid manifest, which later causes a failure when reading the
> > manifest.
> >
> > -Nathan
> >
> > On Fri, Apr 18, 2008 at 3:45 AM, Vladimir Beliaev <
> > vladimir.k.beliaev@gmail.com> wrote:
> >
> >
> > > According to the issue quick evaluation the tests are invalid, so noted
> > > revision helped to detect them. The tests are to be excluded now.
> > >
> > > Tim, Alexei, thank you for your input.
> > >
> > > Thanks
> > > Vladimir
> > >
> > > 2008/4/18, Alexei Fedotov
> <alexei.fedotov@gmail.com<https://mail.google.com/mail?view=cm&tf=0&to=alexei.fedotov@gmail.com>
> > >
> > > > :
> > > >
> > > > Tim,
> > > > We are sorting that out.
> > > >
> > > > Thanks.
> > > >
> > > > On Fri, Apr 18, 2008 at 12:21 PM, Tim Ellison
> <t.p.ellison@gmail.com<https://mail.google.com/mail?view=cm&tf=0&to=t.p.ellison@gmail.com>
> > > >
> > > > wrote:
> > > >
> > > > > It'll be a couple of days before I can look at it as I'm going away.
> > > > >
> > > > I'll
> > > >
> > > > > take a look when I get back if nobody beats me to it.
> > > > >
> > > > >  Regards,
> > > > >  Tim
> > > > >
> > > > >
> > > > >
> > > > >  Vladimir Beliaev wrote:
> > > > >
> > > > >
> > > > > > Tim,
> > > > > >
> > > > > > I've opened
> > > > > >
> > > > > HARMONY-5747<https://issues.apache.org/jira/browse/HARMONY-5747>
> > > > >
> > > > > > which
> > > > > > reports regression in EUT/update suite due to r641928
> > > > > >
> > > > > >      [apply patch
> > > > > > HARMONY-4569<https://issues.apache.org/jira/browse/HARMONY-4569>
> > > > > > ([classlib][performance]
> > > > > > Ineffecient manifest parsing results in slowdown when debugging
> java
> > > > > >
> > > > > code)]
> > > > >
> > > > > > Could you take a look at regression & get it resolved, please?
> > > > > >
> > > > > > Thanks
> > > > > > Vladimir
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > With best regards,
> > > > Alexei
> > > >
> > > >
> > >
> >
> >
>


-- 
With best regards,
Alexei