Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [general] App-driven Improvement
Date: Mon, 24 Jul 2006 21:58:57 +0400
Message-ID: <3D8E84095C6A524A985B787423094E40196E5E@mssmsx411>
Thread-Topic: [general] App-driven Improvement
thread-index: Acauv3FcprWaAATXSWqo9rggEd97jwAircLA
From: "Zakharov, Vasily M" <vasily.m.zakharov@intel.com>
To: <harmony-dev@incubator.apache.org>

Great idea!

I'm trying to run Apache Geronimo (it's a J2EE 1.4 certified application
server, http://geronimo.apache.org) on Harmony VM/classlib. Geronimo
starts (mostly) successfully, but a number of important issues does
exist. It seems that those issues could be good candidates to
"App-Oriented Bug Reports" JIRAs.

I'm looking forward to see so powerful application as enterprise
application server be able to run with Harmony. :)

Thanks!

Vasily Zakharov
Intel Middleware Products Division


-----Original Message-----
From: Geir Magnusson Jr [mailto:geir@pobox.com]=20
Sent: Monday, July 24, 2006 5:20 AM
To: harmony-dev@incubator.apache.org
Subject: [general] App-driven Improvement

Now that we have a distribution of the VM + classlib in the JRE, we can
start encouraging people to try real applications and tell us what's
wrong.  I'm guessing this will be an avalanche of useful information :)

Obviously, the ideal is getting both tests and patches, but I think
that's a lot to ask of casual users, and we will benefit greatly from
casual users trying their applications in their environments on our JRE
and reporting the results, even at a high level.

So, I created a new category in JIRA called

    "App-Oriented Bug Reports"

which is intended for people to tell us what went wrong with their apps,
even if they can't quite identify why.  I have some time on a plane
tomorrow, so I'll add a section to the website detailing the idea and
what we're looking for.  I think we have a bit of this information in
the Wiki, so I hope to 'harvest' that too.

The idea is for users to report things to us, even if vague, and then
encourage anyone in the community to take those and hunt down the
problem in detail.  As an example, I added HARMONY-956, which reports on
what appears to be broken classpath/classloader behavior, exhibited when
running ActiveMQ with the latest snapshot build.   I've seen this with
other apps too, not just ActiveMQ

While I didn't chase it down, there should be enough information there
for someone to go and try to figure it out, and report back the real
exact problem (hopefully w/ a patch!)

I hope this will create a "virtuous cycle" of ever increasing
functionality as we fix important bugs reported by users with real
applications, as well as greater project participation as the
"app-oriented" bugs provide opportunities for contribution.

Anyway, I'm hoping this will be useful for us...

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