RE: [doc] What should be improved in DRLVM Doxygen documentation?

[Morozova, Nadezhda]

Do you think we can add RED ALERT to the files that have only one
warning - not documented? I'd say such files should be addressed in the
first place


>-Original Message-
>From: Andrey Yakushev [mailto:[EMAIL PROTECTED]
>Sent: Friday, November 17, 2006 1:23 PM
>To: harmony-dev@incubator.apache.org
>Subject: Re: [doc] What should be improved in DRLVM Doxygen
documentation?
>
>Alexei,
>
>Metric is simply the number of Doxygen warnings for file. Sorry for
>not mentioning this in my letter.
>If some file doesn't have Doxygen comments at all then metric can show
>only one problem, like in your examples:
>
>vm/gc_cc/src/timer.h:27: Warning: Compound Timer is not documented.
>vm/include/slot.h:48: Warning: Compound Slot is not documented.
>
>All warning need attention I think. If doc is generated without
>warning, then file is not presented in this list. So this metric
>separates bad documented files. Yours estimates quality of good
>documented files.
>
>I consider this as some king of QA for documentation. The more tests -
>the better. :)
>
>Thanks
>Andrey
>
>On 11/16/06, Alexei Fedotov <[EMAIL PROTECTED]> wrote:
>> Andrey,
>>
>> I'm trying to understand your metric and have got a question about
>> your it. Conssider the following file:
>> drlvm/trunk/vm/vmcore/include/Class.h. It has metric of 126. Does it
>> mean that this file has worse documentation than one of the folloiwng
>> files?
>>
>> vm/gc_cc/src/timer.h (1) or vm/gc_cc/src/slot.h (1)
>>
>> > Seems like this metric likes big narrative text.
>> So do I :-)
>>
>> Thanks!
>>
>>
>> On 11/16/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
>> > Andrey,
>> > I personally like the metric. It does not always reflect the
>> > proportional amount of documentation, but the files at the top of
the
>> > list (the worst files) indeed require attention :)
>> > I guess the metric shows both undocumented files and those that are
>> > pretty verbose but require more attention.
>> >
>> > Suggestion: in addition to the big metric, have a more refined
listing
>-
>> > which ignores some warnings of minor importance. For example, a
metric
>> > that only reports undocumented members. What do you say?
>> >
>> >
>> > Thank you,
>> > Nadya Morozova
>> >
>> > >-Original Message-
>> > >From: Andrey Yakushev [mailto:[EMAIL PROTECTED]
>> > >Sent: Thursday, November 16, 2006 7:46 PM
>> > >To: harmony-dev@incubator.apache.org
>> > >Subject: Re: [doc] What should be improved in DRLVM Doxygen
>> > documentation?
>> > >
>> > >Alexei's metric is interesting, but sometimes shows strange
results
>> > >for pretty good docs, like for quite commented files:
>> > >
>> > >0 verifier_8h.html
>> > >0 structVerifier_1_1vf__Graph.html
>> > >
>> > >Seems like this metric likes big narrative text.
>> > >
>> > >
>> > >I also agree that comments quality could be estimated through
Doxygen
>> > >warnings. I attempted to use such a metric for DRLVM.
>> > >
>> > >I used generated DoxygenDrlvmLog.txt file and parser string:
>> > >
>> > >---8<--
>> > >cat DoxygenDrlvmLog.txt | grep Warning | awk -F ":" '{print $1}' >
>> > >~/tmp/r ; for f in `cat ~/tmp/r | sort | uniq` ; do ( echo `cat
>> > >~/tmp/r | grep $f | wc -l` " " $f ) ; done | sort -n -r
>> > >---8<--
>> > >
>> > >The result is placed at
>> >
>>http://wiki.apache.org/harmony/DRLVM_Documentation_Quality_Doxygen_War
n
>> > ing_
>> > >Rating
>> > >
>> > >If it suits our needs we can think about regular testing.
>> > >
>> > >Thanks,
>> > >Andrey
>> > >
>> > >
>> > >On 07 Nov 2006 14:23:20 +0600, Egor Pasko <[EMAIL PROTECTED]>
>wrote:
>> > >> On the 0x216 day of Apache Harmony Alexei A. Fedotov wrote:
>> > >> > Nadya wrote,
>> > >> > > we could check for required Doxygen tags in certain
elements.
>> > >> >
>> > >> > I wasn't asked, but cannot resist, sorry. You may achieve this
>> > right
>> > >now
>> > >> > without additional coding

RE: [doc] What should be improved in DRLVM Doxygen documentation?

[Morozova, Nadezhda]

He-he.
There's truth in what you say. But I ran the same metric with
EXTRACT_ALL option enabled, and class.h had ~10 warnings instead of 126
:) that's why I think the warning about undocumented members that
directly relies on EXTRALL_ALL setting should be considered with care.

Thank you, 
Nadya Morozova
 

>-Original Message-
>From: Alexei Fedotov [mailto:[EMAIL PROTECTED]
>Sent: Thursday, November 16, 2006 8:48 PM
>To: harmony-dev@incubator.apache.org
>Subject: Re: [doc] What should be improved in DRLVM Doxygen
documentation?
>
>Andrey,
>
>I'm trying to understand your metric and have got a question about
>your it. Conssider the following file:
>drlvm/trunk/vm/vmcore/include/Class.h. It has metric of 126. Does it
>mean that this file has worse documentation than one of the folloiwng
>files?
>
>vm/gc_cc/src/timer.h (1) or vm/gc_cc/src/slot.h (1)
>
>> Seems like this metric likes big narrative text.
>So do I :-)
>
>Thanks!
>
>
>On 11/16/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
>> Andrey,
>> I personally like the metric. It does not always reflect the
>> proportional amount of documentation, but the files at the top of the
>> list (the worst files) indeed require attention :)
>> I guess the metric shows both undocumented files and those that are
>> pretty verbose but require more attention.
>>
>> Suggestion: in addition to the big metric, have a more refined
listing -
>> which ignores some warnings of minor importance. For example, a
metric
>> that only reports undocumented members. What do you say?
>>
>>
>> Thank you,
>> Nadya Morozova
>>
>> >-Original Message-
>> >From: Andrey Yakushev [mailto:[EMAIL PROTECTED]
>> >Sent: Thursday, November 16, 2006 7:46 PM
>> >To: harmony-dev@incubator.apache.org
>> >Subject: Re: [doc] What should be improved in DRLVM Doxygen
>> documentation?
>> >
>> >Alexei's metric is interesting, but sometimes shows strange results
>> >for pretty good docs, like for quite commented files:
>> >
>> >0 verifier_8h.html
>> >0 structVerifier_1_1vf__Graph.html
>> >
>> >Seems like this metric likes big narrative text.
>> >
>> >
>> >I also agree that comments quality could be estimated through
Doxygen
>> >warnings. I attempted to use such a metric for DRLVM.
>> >
>> >I used generated DoxygenDrlvmLog.txt file and parser string:
>> >
>> >---8<--
>> >cat DoxygenDrlvmLog.txt | grep Warning | awk -F ":" '{print $1}' >
>> >~/tmp/r ; for f in `cat ~/tmp/r | sort | uniq` ; do ( echo `cat
>> >~/tmp/r | grep $f | wc -l` " " $f ) ; done | sort -n -r
>> >---8<--
>> >
>> >The result is placed at
>>
>http://wiki.apache.org/harmony/DRLVM_Documentation_Quality_Doxygen_Warn
>> ing_
>> >Rating
>> >
>> >If it suits our needs we can think about regular testing.
>> >
>> >Thanks,
>> >Andrey
>> >
>> >
>> >On 07 Nov 2006 14:23:20 +0600, Egor Pasko <[EMAIL PROTECTED]>
wrote:
>> >> On the 0x216 day of Apache Harmony Alexei A. Fedotov wrote:
>> >> > Nadya wrote,
>> >> > > we could check for required Doxygen tags in certain elements.
>> >> >
>> >> > I wasn't asked, but cannot resist, sorry. You may achieve this
>> right
>> >now
>> >> > without additional coding. Doxygen warns about many problems you
>> >> > describe, when you have the following option set.
>> >> >
>> >> > # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will
generate
>> >> > warnings
>> >> > # for undocumented members. If EXTRACT_ALL is set to YES then
this
>> flag
>> >> > will
>> >> > # automatically be disabled.
>> >> > WARN_IF_UNDOCUMENTED   = YES
>> >> >
>> >> > The resulting log consists of warning messages about different
>> >problems.
>> >> > My DoxygenDrlvmLog.txt, for example, contains the following one:
>> >> >
>> >> >
>>
>drlvm/trunk/vm/MMTk/ext/vm/HarmonyDRLVM/org/apache/HarmonyDRLVM/mm/mmtk
>> /
>> >> > Scanning.java:47: Warning: The following parameters of
>> >> >
>>
>org::apache::HarmonyDRLVM::mm::mmtk::Scanning::precopyChildren(TraceLoc
>> a
>> >&g

RE: [doc] What should be improved in DRLVM Doxygen documentation?

[Morozova, Nadezhda]

One more question:
Many warnings are produced for 'undocumented members' which do not
require documentation. What to do with these? 

For example, you add a comment to a struct and insert a reference to
spec. you do not want to document struct members - everything is in the
spec, but Doxygen produces warnings. 
Another example would be enums. Often, a definition of the enum is
enough because the names of enum's members are quite transparent.

One suggestion would be to add the reference to spec to every member or
add ///some-text-that-is-parsed-as-comment to elements that, in your
opinion, are self-explanatory. Another way out is to ignore these errors
or exclude specific elements/files from the metric. 


Thank you, 
Nadya Morozova
 

>-Original Message-
>From: Andrey Yakushev [mailto:[EMAIL PROTECTED]
>Sent: Thursday, November 16, 2006 7:46 PM
>To: harmony-dev@incubator.apache.org
>Subject: Re: [doc] What should be improved in DRLVM Doxygen
documentation?
>
>Alexei's metric is interesting, but sometimes shows strange results
>for pretty good docs, like for quite commented files:
>
>0 verifier_8h.html
>0 structVerifier_1_1vf__Graph.html
>
>Seems like this metric likes big narrative text.
>
>
>I also agree that comments quality could be estimated through Doxygen
>warnings. I attempted to use such a metric for DRLVM.
>
>I used generated DoxygenDrlvmLog.txt file and parser string:
>
>---8<--
>cat DoxygenDrlvmLog.txt | grep Warning | awk -F ":" '{print $1}' >
>~/tmp/r ; for f in `cat ~/tmp/r | sort | uniq` ; do ( echo `cat
>~/tmp/r | grep $f | wc -l` " " $f ) ; done | sort -n -r
>---8<--
>
>The result is placed at
>http://wiki.apache.org/harmony/DRLVM_Documentation_Quality_Doxygen_Warn
ing_
>Rating
>
>If it suits our needs we can think about regular testing.
>
>Thanks,
>Andrey
>
>
>On 07 Nov 2006 14:23:20 +0600, Egor Pasko <[EMAIL PROTECTED]> wrote:
>> On the 0x216 day of Apache Harmony Alexei A. Fedotov wrote:
>> > Nadya wrote,
>> > > we could check for required Doxygen tags in certain elements.
>> >
>> > I wasn't asked, but cannot resist, sorry. You may achieve this
right
>now
>> > without additional coding. Doxygen warns about many problems you
>> > describe, when you have the following option set.
>> >
>> > # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate
>> > warnings
>> > # for undocumented members. If EXTRACT_ALL is set to YES then this
flag
>> > will
>> > # automatically be disabled.
>> > WARN_IF_UNDOCUMENTED   = YES
>> >
>> > The resulting log consists of warning messages about different
>problems.
>> > My DoxygenDrlvmLog.txt, for example, contains the following one:
>> >
>> >
>drlvm/trunk/vm/MMTk/ext/vm/HarmonyDRLVM/org/apache/HarmonyDRLVM/mm/mmtk
/
>> > Scanning.java:47: Warning: The following parameters of
>> >
>org::apache::HarmonyDRLVM::mm::mmtk::Scanning::precopyChildren(TraceLoc
a
>> > l trace, ObjectReference object) are not documented:
>> >   parameter trace
>>
>> does it make sense to convert warnings to quality metrics and put on
>> harmonytest.org (or even Wiki) regularly? It should encourage people
>> (like me) to document sources better. Or it is too much effort?
>>
>> > With best regards,
>> > Alexei Fedotov,
>> > Intel Java & XML Engineering
>> >
>> > >-Original Message-
>> > >From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED]
>> > >Sent: Friday, November 03, 2006 6:26 PM
>> > >To: harmony-dev@incubator.apache.org
>> > >Subject: RE: Re: [doc] What should be improved in DRLVM Doxygen
>> > >documentation?
>> > >
>> > >Egor,
>> > >I agree with you on the idea of simplicity: documented vs.
>> > >non-documented.
>> > >An additional point: do you think we need/want to evaluate quality
of
>> > >comments? we could check for required Doxygen tags in certain
>elements.
>> > >For example, a function is almost certain to include @param and
>> > @return.
>> > >Surely, this is heuristics and does not solve all our problems.
But
>the
>> > >Doxygen quality check sometimes shows that the file does have
>comments,
>> > >but they are not processed properly by Doxygen - which results in
a
>low
>> > >rating for an html file. Maybe this is a crazy idea - I'd be glad
to
>>

RE: [doc] What should be improved in DRLVM Doxygen documentation?

[Morozova, Nadezhda]

Andrey, 
I personally like the metric. It does not always reflect the
proportional amount of documentation, but the files at the top of the
list (the worst files) indeed require attention :)
I guess the metric shows both undocumented files and those that are
pretty verbose but require more attention.

Suggestion: in addition to the big metric, have a more refined listing -
which ignores some warnings of minor importance. For example, a metric
that only reports undocumented members. What do you say?


Thank you, 
Nadya Morozova
 
>-Original Message-
>From: Andrey Yakushev [mailto:[EMAIL PROTECTED]
>Sent: Thursday, November 16, 2006 7:46 PM
>To: harmony-dev@incubator.apache.org
>Subject: Re: [doc] What should be improved in DRLVM Doxygen
documentation?
>
>Alexei's metric is interesting, but sometimes shows strange results
>for pretty good docs, like for quite commented files:
>
>0 verifier_8h.html
>0 structVerifier_1_1vf__Graph.html
>
>Seems like this metric likes big narrative text.
>
>
>I also agree that comments quality could be estimated through Doxygen
>warnings. I attempted to use such a metric for DRLVM.
>
>I used generated DoxygenDrlvmLog.txt file and parser string:
>
>---8<--
>cat DoxygenDrlvmLog.txt | grep Warning | awk -F ":" '{print $1}' >
>~/tmp/r ; for f in `cat ~/tmp/r | sort | uniq` ; do ( echo `cat
>~/tmp/r | grep $f | wc -l` " " $f ) ; done | sort -n -r
>---8<--
>
>The result is placed at
>http://wiki.apache.org/harmony/DRLVM_Documentation_Quality_Doxygen_Warn
ing_
>Rating
>
>If it suits our needs we can think about regular testing.
>
>Thanks,
>Andrey
>
>
>On 07 Nov 2006 14:23:20 +0600, Egor Pasko <[EMAIL PROTECTED]> wrote:
>> On the 0x216 day of Apache Harmony Alexei A. Fedotov wrote:
>> > Nadya wrote,
>> > > we could check for required Doxygen tags in certain elements.
>> >
>> > I wasn't asked, but cannot resist, sorry. You may achieve this
right
>now
>> > without additional coding. Doxygen warns about many problems you
>> > describe, when you have the following option set.
>> >
>> > # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate
>> > warnings
>> > # for undocumented members. If EXTRACT_ALL is set to YES then this
flag
>> > will
>> > # automatically be disabled.
>> > WARN_IF_UNDOCUMENTED   = YES
>> >
>> > The resulting log consists of warning messages about different
>problems.
>> > My DoxygenDrlvmLog.txt, for example, contains the following one:
>> >
>> >
>drlvm/trunk/vm/MMTk/ext/vm/HarmonyDRLVM/org/apache/HarmonyDRLVM/mm/mmtk
/
>> > Scanning.java:47: Warning: The following parameters of
>> >
>org::apache::HarmonyDRLVM::mm::mmtk::Scanning::precopyChildren(TraceLoc
a
>> > l trace, ObjectReference object) are not documented:
>> >   parameter trace
>>
>> does it make sense to convert warnings to quality metrics and put on
>> harmonytest.org (or even Wiki) regularly? It should encourage people
>> (like me) to document sources better. Or it is too much effort?
>>
>> > With best regards,
>> > Alexei Fedotov,
>> > Intel Java & XML Engineering
>> >
>> > >-Original Message-
>> > >From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED]
>> > >Sent: Friday, November 03, 2006 6:26 PM
>> > >To: harmony-dev@incubator.apache.org
>> > >Subject: RE: Re: [doc] What should be improved in DRLVM Doxygen
>> > >documentation?
>> > >
>> > >Egor,
>> > >I agree with you on the idea of simplicity: documented vs.
>> > >non-documented.
>> > >An additional point: do you think we need/want to evaluate quality
of
>> > >comments? we could check for required Doxygen tags in certain
>elements.
>> > >For example, a function is almost certain to include @param and
>> > @return.
>> > >Surely, this is heuristics and does not solve all our problems.
But
>the
>> > >Doxygen quality check sometimes shows that the file does have
>comments,
>> > >but they are not processed properly by Doxygen - which results in
a
>low
>> > >rating for an html file. Maybe this is a crazy idea - I'd be glad
to
>> > >know your opinion.
>> > >
>> > >Thank you,
>> > >Nadya Morozova
>> > >
>> > >
>> > >-Original Message-
>> > >From: news [mailto

RE: Re: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

Hi all,
I have attached an updated version of the patch for the getting started
page to the JIRA. If someone knowledgeable takes a look and evaluates,
that would be great.
I am not the reporter of the issue, so I cannot set the 'patch
available' setting. However, if no requests for fixes arrive, I suggest
that we consider the issue ready to be closed.

Thank you, 
Nadya Morozova
 

>-Original Message-
>From: Pavel Ozhdikhin [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, November 14, 2006 9:43 AM
>To: harmony-dev@incubator.apache.org
>Subject: Re: Re: [doc][drlvm] The document "Getting started with DRL"
is
>outdated
>
>OK then for Configuring VM section JIT options proposed by Egor will be
>suitable:
>
>"-Xem:jet <- use only baseline JIT compiler"
>"-Xem:opt <- use only optimising JIT compiler"
>"-Xtrace:em <- print method compilation events"
>
>I'd also add:
>
>"-Xem:server" - enable dynamic optimization mode tuned for long-running
>server-side applications (default optimization mode is tuned for fast
>start-up and client-side applications)
>"-Xem server_static" - enable static optimization mode tuned for
>long-running server-side applications
>
>Thanks,
>Pavel
>
>On 11/14/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
>>
>> Pavel,
>> Thanks for your comments. I'll work through the examples and post an
>> updated patch soon.
>> As for the Configuring VM operation - can we at least have a couple
of
>> examples in the form of scenarios or something? The wiki page only
gives
>> a reference, an enumeration of available options. Using these might
not
>> always be transparent. I know it's tutorial-level info, but why not
have
>> it? Giving a show-case of customizing vm to a specific need would be
>> great.
>>
>> Thank you,
>> Nadya Morozova
>>
>> >-Original Message-
>> >From: Pavel Ozhdikhin [mailto:[EMAIL PROTECTED]
>> >Sent: Tuesday, November 14, 2006 9:23 AM
>> >To: harmony-dev@incubator.apache.org
>> >Subject: Re: Re: [doc][drlvm] The document "Getting started with
DRL"
>> is
>> >outdated
>> >
>> >Nadya,
>> >
>> >I've looked through your patch. Please see my comments in JIRA:
>> >http://issues.apache.org/jira/browse/HARMONY-2150
>> >
>> >> Do you think we can add a link to debugging vm&jit doc (or to
wiki)?
>> >
>> >I don't think we need it - it is rather info for developers than for
>> users.
>> >
>> >> Any ideas on what to write in Configuring vm operation?
>> >
>> >This section will duplicate the info from the Wiki page. Since we
gave
>> a
>> >link to that page in the "overview" we may skip creation of a
separate
>> >section here.
>> >
>> >Thanks,
>> >Pavel
>> >
>> >
>> >On 11/13/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Successfully added a patch to fix getting Started outdated content
to
>> >> http://issues.apache.org/jira/browse/HARMONY-2150.
>> >> The patch is not final - need help to add more content. The
current
>> >> structure is:
>> >> - overview
>> >> - running an app
>> >> - eclipse-related (now much shorter)
>> >>-- running an app
>> >>-- debugging an app
>> >> - configuring vm operation (empty)
>> >>
>> >> Questions: how do you like the current patch? Do you think we can
add
>> a
>> >> link to debugging vm&jit doc (or to wiki)? Any ideas on what to
write
>> in
>> >> Configuring vm operation?
>> >>
>> >> Thank you,
>> >> Nadya Morozova
>> >>
>> >> >-Original Message-
>> >> >From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
>> >> >Sent: Monday, November 13, 2006 1:00 PM
>> >> >To: harmony-dev@incubator.apache.org
>> >> >Subject: Re: [doc][drlvm] The document "Getting started with DRL"
is
>> >> >outdated
>> >> >
>> >> >On the 0x220 day of Apache Harmony Nadezhda Morozova wrote:
>> >> >> >-Original Message-
>> >> >> >From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
>> >> >> >Sent: Monday, November 13, 2006 12:40 PM
>> >> >> >To: harmony-dev@incubator.apache.org
>> >> >> >Subject: R

RE: Re: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

Pavel,
Thanks for your comments. I'll work through the examples and post an
updated patch soon. 
As for the Configuring VM operation - can we at least have a couple of
examples in the form of scenarios or something? The wiki page only gives
a reference, an enumeration of available options. Using these might not
always be transparent. I know it's tutorial-level info, but why not have
it? Giving a show-case of customizing vm to a specific need would be
great. 

Thank you, 
Nadya Morozova
 
>-Original Message-
>From: Pavel Ozhdikhin [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, November 14, 2006 9:23 AM
>To: harmony-dev@incubator.apache.org
>Subject: Re: Re: [doc][drlvm] The document "Getting started with DRL"
is
>outdated
>
>Nadya,
>
>I've looked through your patch. Please see my comments in JIRA:
>http://issues.apache.org/jira/browse/HARMONY-2150
>
>> Do you think we can add a link to debugging vm&jit doc (or to wiki)?
>
>I don't think we need it - it is rather info for developers than for
users.
>
>> Any ideas on what to write in Configuring vm operation?
>
>This section will duplicate the info from the Wiki page. Since we gave
a
>link to that page in the "overview" we may skip creation of a separate
>section here.
>
>Thanks,
>Pavel
>
>
>On 11/13/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
>>
>> Successfully added a patch to fix getting Started outdated content to
>> http://issues.apache.org/jira/browse/HARMONY-2150.
>> The patch is not final - need help to add more content. The current
>> structure is:
>> - overview
>> - running an app
>> - eclipse-related (now much shorter)
>>-- running an app
>>-- debugging an app
>> - configuring vm operation (empty)
>>
>> Questions: how do you like the current patch? Do you think we can add
a
>> link to debugging vm&jit doc (or to wiki)? Any ideas on what to write
in
>> Configuring vm operation?
>>
>> Thank you,
>> Nadya Morozova
>>
>> >-Original Message-
>> >From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
>> >Sent: Monday, November 13, 2006 1:00 PM
>> >To: harmony-dev@incubator.apache.org
>> >Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
>> >outdated
>> >
>> >On the 0x220 day of Apache Harmony Nadezhda Morozova wrote:
>> >> >-Original Message-
>> >> >From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
>> >> >Sent: Monday, November 13, 2006 12:40 PM
>> >> >To: harmony-dev@incubator.apache.org
>> >> >Subject: Re: [doc][drlvm] The document "Getting started with DRL"
is
>> >> >outdated
>> >> >
>> >> >On the 0x220 day of Apache Harmony Nadezhda Morozova wrote:
>> >> >> Ok,
>> >> >> I'll use http://issues.apache.org/jira/browse/HARMONY-2150 to
get
>> an
>> >> >> initial patch for the getting started document, and we can then
>> work
>> >> to
>> >> >> improve it.
>> >> >
>> >> >OK, I am "watching" it
>> >> >
>> >> >> Let's make it a short page with links to wiki and maybe some
>> how-tos.
>> >> >
>> >> >To summarize:
>> >> >* we agreed that there will be no eclipse screenshots (they are
for
>> >> >  eclipse+drlvm page)
>> >> >* we agreed that there should be something like "see what kind of
>> >> >  links we have"
>> >> >
>> >> >Am I right?
>> >>
>> >> [Nadya]
>> >> Yop, quite right. An additional enhancement would be to comment
out
>> >> copyrights and update info that is incorrect.
>> >
>> >remove these annoyed substances? I am not an expert in copyright
law,
>> >not sure we can remove them. But copyright notices are not what I
>> >desire to look at on the "getting started" page.
>> >
>> >> Not sure I'll fix everything, but can give a start. Thanks for all
>> your
>> >> help.
>> >
>> >u r welcome
>> >
>> >> >
>> >> >> Thank you,
>> >> >> Nadya Morozova
>> >> >>
>> >> >>
>> >> >> -Original Message-
>> >> >> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
>> >> >> Sent: Monday, November 

RE: [doc] site.css

[Morozova, Nadezhda]

My two cents below. 

Thank you, 
Nadya Morozova
 

>-Original Message-
>From: Ivanov, Alexey A [mailto:[EMAIL PROTECTED]
>Sent: Monday, November 13, 2006 5:56 PM
>To: harmony-dev@incubator.apache.org
>Subject: [doc] site.css
>
>Hi all,
>
>I've updated formatting of definition lists  on site:
>https://issues.apache.org/jira/browse/HARMONY-2173
>
>The new formatting looks more natural to me; the screenshots can be found
>in the JIRA issue.
>
[Nadya] good patch! I checked it on IE and Opera and Netscape. Works fine.
>
>When editing site.css I faced that there are many different styles of
>indentation used:
>* Some statements are indented using tabs,
>* Some -- using spaces,
>* And a mixture of tabs and space, in the worse case.
>
>There are also inconsistencies in formatting of rules, and trailing white-
>space.
>
>Let's agree on using either tabs or spaces for indentation of CSS
>statements. If they are different, it causes inconveniences when creating
>patches because some lines look changed while nothing was modified there.
>
>I have no strong opinion on which one to use here. But let it be one:
>either tabs or spaces.
>
>What do you think about it?
>
[Nadya] I agree it looks dirty with a mixture of spaces and tabs. I like 
spaces, they are more reliable.
>
>Thank you in advance,
>--
>Alexey A. Ivanov
>Intel Enterprise Solutions Software Division

RE: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

Ok, thanks.
I somehow feel dumb with anything that deals with legal - copyrights,
contracts, licenses...oh! I'd erase all excess disclaimers from our
website with pleasure :) 

Thank you, 
Nadya Morozova
 

>-Original Message-
>From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
>Sent: Monday, November 13, 2006 5:45 PM
>To: harmony-dev@incubator.apache.org
>Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
>outdated
>
>"Additional terms from the Database" ? LOL
>
>Just get rid of it all.  Those terms are in our notice file, and that's
>enough.  Unicode didn't put them there, anyway.
>
>geir
>
>
>Morozova, Nadezhda wrote:
>>
http://incubator.apache.org/harmony/subcomponents/drlvm/getting_started.
>> html#Disclaimer
>>
http://incubator.apache.org/harmony/subcomponents/drlvm/developers_guide
>> .html - these seem to have apache and intel copyright (can be
resolved)
>> + the Unicode disclaimer.
>>
>> Thank you,
>> Nadya Morozova
>>
>>
>>> -Original Message-
>>> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
>>> Sent: Monday, November 13, 2006 5:14 PM
>>> To: harmony-dev@incubator.apache.org
>>> Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
>>> outdated
>>>
>>> what's the link we're talking about?
>>>
>>> Morozova, Nadezhda wrote:
>>>> What about the portions of the Unicode copyright?
>>>>
>>>> Thank you,
>>>> Nadya Morozova
>>>>
>>>>
>>>>> -Original Message-
>>>>> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
>>>>> Sent: Monday, November 13, 2006 5:06 PM
>>>>> To: harmony-dev@incubator.apache.org
>>>>> Subject: Re: [doc][drlvm] The document "Getting started with DRL"
is
>>>>> outdated
>>>>>
>>>>> as an intel person, you can remove an intel copyright.  if it's an
>> ASF
>>>>> copyright, you can remove that too from the document (it should be
>>>>> auto-generated at the bottom anyway)
>>>>>
>>>>>
>>>>> geir
>>>>>
>>>>>
>>>>> Egor Pasko wrote:
>>>>>> On the 0x220 day of Apache Harmony Nadezhda Morozova wrote:
>>>>>>>> -Original Message-
>>>>>>>> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
>>>>>>>> Sent: Monday, November 13, 2006 12:40 PM
>>>>>>>> To: harmony-dev@incubator.apache.org
>>>>>>>> Subject: Re: [doc][drlvm] The document "Getting started with
DRL"
>>>> is
>>>>>>>> outdated
>>>>>>>>
>>>>>>>> On the 0x220 day of Apache Harmony Nadezhda Morozova wrote:
>>>>>>>>> Ok,
>>>>>>>>> I'll use http://issues.apache.org/jira/browse/HARMONY-2150 to
>> get
>>>> an
>>>>>>>>> initial patch for the getting started document, and we can
then
>>>> work
>>>>>>> to
>>>>>>>>> improve it.
>>>>>>>> OK, I am "watching" it
>>>>>>>>
>>>>>>>>> Let's make it a short page with links to wiki and maybe some
>>>> how-tos.
>>>>>>>> To summarize:
>>>>>>>> * we agreed that there will be no eclipse screenshots (they are
>> for
>>>>>>>>  eclipse+drlvm page)
>>>>>>>> * we agreed that there should be something like "see what kind
of
>>>>>>>>  links we have"
>>>>>>>>
>>>>>>>> Am I right?
>>>>>>> [Nadya]
>>>>>>> Yop, quite right. An additional enhancement would be to comment
>> out
>>>>>>> copyrights and update info that is incorrect.
>>>>>> remove these annoyed substances? I am not an expert in copyright
>> law,
>>>>>> not sure we can remove them. But copyright notices are not what I
>>>>>> desire to look at on the "getting started" page.
>>>>>>
>>>>>>> Not sure I'll fix everything, but can give a start. Thanks for
all
>>>> your
>>>>>>> help.
>>>>>> u r welcome

RE: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

http://incubator.apache.org/harmony/subcomponents/drlvm/getting_started.
html#Disclaimer 
http://incubator.apache.org/harmony/subcomponents/drlvm/developers_guide
.html - these seem to have apache and intel copyright (can be resolved)
+ the Unicode disclaimer.

Thank you, 
Nadya Morozova
 

>-Original Message-
>From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
>Sent: Monday, November 13, 2006 5:14 PM
>To: harmony-dev@incubator.apache.org
>Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
>outdated
>
>what's the link we're talking about?
>
>Morozova, Nadezhda wrote:
>> What about the portions of the Unicode copyright?
>>
>> Thank you,
>> Nadya Morozova
>>
>>
>>> -Original Message-
>>> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
>>> Sent: Monday, November 13, 2006 5:06 PM
>>> To: harmony-dev@incubator.apache.org
>>> Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
>>> outdated
>>>
>>> as an intel person, you can remove an intel copyright.  if it's an
ASF
>>> copyright, you can remove that too from the document (it should be
>>> auto-generated at the bottom anyway)
>>>
>>>
>>> geir
>>>
>>>
>>> Egor Pasko wrote:
>>>> On the 0x220 day of Apache Harmony Nadezhda Morozova wrote:
>>>>>> -Original Message-
>>>>>> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
>>>>>> Sent: Monday, November 13, 2006 12:40 PM
>>>>>> To: harmony-dev@incubator.apache.org
>>>>>> Subject: Re: [doc][drlvm] The document "Getting started with DRL"
>> is
>>>>>> outdated
>>>>>>
>>>>>> On the 0x220 day of Apache Harmony Nadezhda Morozova wrote:
>>>>>>> Ok,
>>>>>>> I'll use http://issues.apache.org/jira/browse/HARMONY-2150 to
get
>> an
>>>>>>> initial patch for the getting started document, and we can then
>> work
>>>>> to
>>>>>>> improve it.
>>>>>> OK, I am "watching" it
>>>>>>
>>>>>>> Let's make it a short page with links to wiki and maybe some
>> how-tos.
>>>>>> To summarize:
>>>>>> * we agreed that there will be no eclipse screenshots (they are
for
>>>>>>  eclipse+drlvm page)
>>>>>> * we agreed that there should be something like "see what kind of
>>>>>>  links we have"
>>>>>>
>>>>>> Am I right?
>>>>> [Nadya]
>>>>> Yop, quite right. An additional enhancement would be to comment
out
>>>>> copyrights and update info that is incorrect.
>>>> remove these annoyed substances? I am not an expert in copyright
law,
>>>> not sure we can remove them. But copyright notices are not what I
>>>> desire to look at on the "getting started" page.
>>>>
>>>>> Not sure I'll fix everything, but can give a start. Thanks for all
>> your
>>>>> help.
>>>> u r welcome
>>>>
>>>>>>> Thank you,
>>>>>>> Nadya Morozova
>>>>>>>
>>>>>>>
>>>>>>> -Original Message-
>>>>>>> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
>>>>>>> Sent: Monday, November 13, 2006 11:10 AM
>>>>>>> To: harmony-dev@incubator.apache.org
>>>>>>> Subject: Re: [doc][drlvm] The document "Getting started with
DRL"
>> is
>>>>>>> outdated
>>>>>>>
>>>>>>> On the 0x21D day of Apache Harmony Nadezhda Morozova wrote:
>>>>>>>> Egor,
>>>>>>>> I think we're mixing things up a bit, or at least our
perceptions
>>>>> of
>>>>>>>> various docs. I'd not call what you're suggesting a tutorial -
>> it's
>>>>>>> more
>>>>>>>> of a howto doc, right? We are lucky to have Salikh write this
>> "How
>>>>> to
>>>>>>>> write a GC?" Doc - do you mean something similar for "DRLVM
>>>>>>> Command-line
>>>>>>>> Args Tutorial"?
>>>>>>> on Wikipedia:
>>>>>>> * A _ho

RE: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

che Harmony Nadezhda Morozova wrote:
>>>>>>>>>>> Good day to you, Egor!
>>>>>>>>>> evening, dark and snowy evening :)
>>>>>>>>>>
>>>>>>>>>>> What do you say about the getting started doc?
>>>>>>>>>> I expressed it recently. General idea is that Harmony
>>> operates
>>>>>> near
>>>>>>>>>> the same as other JSE implementations. Almost all specifics
>>> is
>>>>> in
>>>>>>>>>> extra options which we started collecting on Wiki for an
>>> extra
>>>>>>>>>> HOWTO-like page (BTW, thanks to Salikh for starting the
>>> page).
>>>>>>>>>> I believe, it is time to remove the "Getting Started". So,
>>> +1
>>>>> to
>>>>>>> Pavel
>>>>>>>>>> Ozhdikhin here.
>>>>>>>>>>
>>>>>>>>>> BTW, I asked my dad to look at the website. Ideas for
>>>>> improvement
>>>>>>> from
>>>>>>>>>> him:
>>>>>>>>>> 1) site-local search is useful for a beginner. Hm, Tomcat
>>> has
>>>>> it
>>>>>>> with
>>>>>>>>>> links to google search. We can have something as soon as we
>>> get
>>>>>> to
>>>>>>> the
>>>>>>>>>> desired TLP :)
>>>>>>>>>> 2) it is not obvious that site misprints/problems should be
>>>>>>> reported
>>>>>>>>>> to the mailing list. Commercial websites have something like
>>>>>>>>>> "support/suggestions mailto". We can point mailto to the
>>>>> mailing
>>>>>>> list
>>>>>>>> :)
>>>>>>>>>>> Thank you,
>>>>>>>>>>> Nadya Morozova
>>>>>>>>>>>
>>>>>>>>>>> -Original Message-
>>>>>>>>>>> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor
>>>>> Pasko
>>>>>>>>>>> Sent: Friday, November 10, 2006 8:55 AM
>>>>>>>>>>> To: harmony-dev@incubator.apache.org
>>>>>>>>>>> Subject: Re: [doc][drlvm] The document "Getting started
>>> with
>>>>>> DRL"
>>>>>>> is
>>>>>>>>>>> outdated
>>>>>>>>>>>
>>>>>>>>>>> On the 0x21D day of Apache Harmony Nadezhda Morozova
>>> wrote:
>>>>>>>>>>>> Egor,
>>>>>>>>>>>> I generally like the idea of improving navigation over
>>> the
>>>>>> site
>>>>>>> -
>>>>>>>>>>>> there's never too much of that. However, I am not sure
>>>>>> whether
>>>>>>> we
>>>>>>>> need
>>>>>>>>>>>> yet another separate page for introductory/guidance
>>> info. I
>>>>>>> hope
>>>>>>>> the
>>>>>>>>>>>> starting page + the generic pages we have are mostly
>>> fine.
>>>>>>> However,
>>>>>>>>>>>> adding a link here and there to lead site visitors.
>>>>>>>>>>>>
>>>>>>>>>>>> Getting started could be a more specific
>>> project-oriented
>>>>>> page.
>>>>>>>> There,
>>>>>>>>>>>> you can tell people to go download,
>>>>>>> build
>>>>>>>>>>> the
>>>>>>>>>>>> code. After which, they can start using it just as any
>>>>> other
>>>>>>>>>>>> RI-compatible jdk. With the exceptions, see
>>>>> our
>>>>>>>>>>>> wiki pages.
>>>>>>>>>>>> To use the vm, readers might need to use the following
>>>>>>> options...
>>>>>>>>>>>> If they want to read more on our VM, they can visit the
>>

RE: Re: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

; >> > > >> > On the 0x21D day of Apache Harmony Nadezhda Morozova
wrote:
>> >> > > >> > > Good day to you, Egor!
>> >> > > >> >
>> >> > > >> > evening, dark and snowy evening :)
>> >> > > >> >
>> >> > > >> > > What do you say about the getting started doc?
>> >> > > >> >
>> >> > > >> > I expressed it recently. General idea is that Harmony
>> operates
>> >> > near
>> >> > > >> > the same as other JSE implementations. Almost all
specifics
>> is
>> >> in
>> >> > > >> > extra options which we started collecting on Wiki for an
>> extra
>> >> > > >> > HOWTO-like page (BTW, thanks to Salikh for starting the
>> page).
>> >> > > >> >
>> >> > > >> > I believe, it is time to remove the "Getting Started".
So,
>> +1
>> >> to
>> >> > > Pavel
>> >> > > >> > Ozhdikhin here.
>> >> > > >> >
>> >> > > >> > BTW, I asked my dad to look at the website. Ideas for
>> >> improvement
>> >> > > from
>> >> > > >> > him:
>> >> > > >> > 1) site-local search is useful for a beginner. Hm, Tomcat
>> has
>> >> it
>> >> > > with
>> >> > > >> > links to google search. We can have something as soon as
we
>> get
>> >> > to
>> >> > > the
>> >> > > >> > desired TLP :)
>> >> > > >> > 2) it is not obvious that site misprints/problems should
be
>> >> > > reported
>> >> > > >> > to the mailing list. Commercial websites have something
like
>> >> > > >> > "support/suggestions mailto". We can point mailto to the
>> >> mailing
>> >> > > list
>> >> > > >:)
>> >> > > >> >
>> >> > > >> > > Thank you,
>> >> > > >> > > Nadya Morozova
>> >> > > >> > >
>> >> > > >> > > -Original Message-
>> >> > > >> > > From: news [mailto:[EMAIL PROTECTED] On Behalf Of
Egor
>> >> Pasko
>> >> > > >> > > Sent: Friday, November 10, 2006 8:55 AM
>> >> > > >> > > To: harmony-dev@incubator.apache.org
>> >> > > >> > > Subject: Re: [doc][drlvm] The document "Getting started
>> with
>> >> > DRL"
>> >> > > is
>> >> > > >> > > outdated
>> >> > > >> > >
>> >> > > >> > > On the 0x21D day of Apache Harmony Nadezhda Morozova
>> wrote:
>> >> > > >> > > > Egor,
>> >> > > >> > > > I generally like the idea of improving navigation
over
>> the
>> >> > site
>> >> > > -
>> >> > > >> > > > there's never too much of that. However, I am not
sure
>> >> > whether
>> >> > > we
>> >> > > >need
>> >> > > >> > > > yet another separate page for introductory/guidance
>> info. I
>> >> > > hope
>> >> > > >the
>> >> > > >> > > > starting page + the generic pages we have are mostly
>> fine.
>> >> > > However,
>> >> > > >> > > > adding a link here and there to lead site visitors.
>> >> > > >> > > >
>> >> > > >> > > > Getting started could be a more specific
>> project-oriented
>> >> > page.
>> >> > > >There,
>> >> > > >> > > > you can tell people to go download,
>> >> > > build
>> >> > > >> > > the
>> >> > > >> > > > code. After which, they can start using it just as
any
>> >> other
>> >> > > >> > > > RI-compatible jdk. With the exceptions,
see
>> >> our
>> >> > > >> > > > wiki pages.
>> >> > > >> > > > To use the

RE: Re: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

 Getting Started as is with minor changes
>> > >
>> > > Why Eclipse was chosen for the tutorial? Our goal was to use
Harmony
>> > for
>> > > Harmony development. I liked that idea.
>> > >
>> > > With best regards,
>> > > Alexei Fedotov,
>> > > Intel Java & XML Engineering
>> > >
>> > > >-Original Message-
>> > > >From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
>> > > >Sent: Friday, November 10, 2006 1:29 PM
>> > > >To: harmony-dev@incubator.apache.org
>> > > >Subject: Re: [doc][drlvm] The document "Getting started with
DRL"
>> is
>> > > >outdated
>> > > >
>> > > >On the 0x21D day of Apache Harmony Pavel Ozhdikhin wrote:
>> > > >> Nadya,
>> > > >>
>> > > >> One more proposal about "Getting Started": let's remove all
>> current
>> > > >content
>> > > >> and write something like following:
>> > > >>
>> > > >> "To the moment we got rid of all major differences from other
>> Java
>> > > >> implementations, so to use DRLVM you can just build it (here
goes
>> > > link to
>> > > >> readme with build instructions) and run as any other Java VM.
For
>> > > >commonly
>> > > >> used command-line options please look into the Wiki page (link
to
>> > > >Salikh's
>> > > >> page or to the document)."
>> > > >>
>> > > >> What do you think?
>> > > >
>> > > >1 page to hold only 4 lines of text? :)
>> > > >
>> > > >> Thanks,
>> > > >> Pavel
>> > > >>
>> > > >>
>> > > >> On 10 Nov 2006 14:29:59 +0600, Egor Pasko
<[EMAIL PROTECTED]>
>> > > wrote:
>> > > >> >
>> > > >> > On the 0x21D day of Apache Harmony Nadezhda Morozova wrote:
>> > > >> > > Good day to you, Egor!
>> > > >> >
>> > > >> > evening, dark and snowy evening :)
>> > > >> >
>> > > >> > > What do you say about the getting started doc?
>> > > >> >
>> > > >> > I expressed it recently. General idea is that Harmony
operates
>> > near
>> > > >> > the same as other JSE implementations. Almost all specifics
is
>> in
>> > > >> > extra options which we started collecting on Wiki for an
extra
>> > > >> > HOWTO-like page (BTW, thanks to Salikh for starting the
page).
>> > > >> >
>> > > >> > I believe, it is time to remove the "Getting Started". So,
+1
>> to
>> > > Pavel
>> > > >> > Ozhdikhin here.
>> > > >> >
>> > > >> > BTW, I asked my dad to look at the website. Ideas for
>> improvement
>> > > from
>> > > >> > him:
>> > > >> > 1) site-local search is useful for a beginner. Hm, Tomcat
has
>> it
>> > > with
>> > > >> > links to google search. We can have something as soon as we
get
>> > to
>> > > the
>> > > >> > desired TLP :)
>> > > >> > 2) it is not obvious that site misprints/problems should be
>> > > reported
>> > > >> > to the mailing list. Commercial websites have something like
>> > > >> > "support/suggestions mailto". We can point mailto to the
>> mailing
>> > > list
>> > > >:)
>> > > >> >
>> > > >> > > Thank you,
>> > > >> > > Nadya Morozova
>> > > >> > >
>> > > >> > > -Original Message-
>> > > >> > > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor
>> Pasko
>> > > >> > > Sent: Friday, November 10, 2006 8:55 AM
>> > > >> > > To: harmony-dev@incubator.apache.org
>> > > >> > > Subject: Re: [doc][drlvm] The document "Getting started
with
>> > DRL"
>> > > is
>> > > >> > > outdated
>> > > >> > >
>> > > >> > > On the 0x21D day of Apache Harmony Nadezhda Morozova
wrote:

RE: Re: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

;
> > >>
> > >> On 10 Nov 2006 14:29:59 +0600, Egor Pasko <[EMAIL PROTECTED]>
> > wrote:
> > >> >
> > >> > On the 0x21D day of Apache Harmony Nadezhda Morozova wrote:
> > >> > > Good day to you, Egor!
> > >> >
> > >> > evening, dark and snowy evening :)
> > >> >
> > >> > > What do you say about the getting started doc?
> > >> >
> > >> > I expressed it recently. General idea is that Harmony operates
> near
> > >> > the same as other JSE implementations. Almost all specifics is
in
> > >> > extra options which we started collecting on Wiki for an extra
> > >> > HOWTO-like page (BTW, thanks to Salikh for starting the page).
> > >> >
> > >> > I believe, it is time to remove the "Getting Started". So, +1
to
> > Pavel
> > >> > Ozhdikhin here.
> > >> >
> > >> > BTW, I asked my dad to look at the website. Ideas for
improvement
> > from
> > >> > him:
> > >> > 1) site-local search is useful for a beginner. Hm, Tomcat has
it
> > with
> > >> > links to google search. We can have something as soon as we get
> to
> > the
> > >> > desired TLP :)
> > >> > 2) it is not obvious that site misprints/problems should be
> > reported
> > >> > to the mailing list. Commercial websites have something like
> > >> > "support/suggestions mailto". We can point mailto to the
mailing
> > list
> > >:)
> > >> >
> > >> > > Thank you,
> > >> > > Nadya Morozova
> > >> > >
> > >> > > -Original Message-
> > >> > > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor
Pasko
> > >> > > Sent: Friday, November 10, 2006 8:55 AM
> > >> > > To: harmony-dev@incubator.apache.org
> > >> > > Subject: Re: [doc][drlvm] The document "Getting started with
> DRL"
> > is
> > >> > > outdated
> > >> > >
> > >> > > On the 0x21D day of Apache Harmony Nadezhda Morozova wrote:
> > >> > > > Egor,
> > >> > > > I generally like the idea of improving navigation over the
> site
> > -
> > >> > > > there's never too much of that. However, I am not sure
> whether
> > we
> > >need
> > >> > > > yet another separate page for introductory/guidance info. I
> > hope
> > >the
> > >> > > > starting page + the generic pages we have are mostly fine.
> > However,
> > >> > > > adding a link here and there to lead site visitors.
> > >> > > >
> > >> > > > Getting started could be a more specific project-oriented
> page.
> > >There,
> > >> > > > you can tell people to go download,
> > build
> > >> > > the
> > >> > > > code. After which, they can start using it just as any
other
> > >> > > > RI-compatible jdk. With the exceptions, see
our
> > >> > > > wiki pages.
> > >> > > > To use the vm, readers might need to use the following
> > options...
> > >> > > > If they want to read more on our VM, they can visit the
> > >> > > > component page. If no website page contains an
> > answer
> > >-
> > >> > > > they can read wiki faqa.
> > >> > > > .. or something like that :)
> > >> > >
> > >> > > Nadya, I really appreciate our efforts :) But this morning I
> woke
> > up
> > >> > > and looked the site structure with the eye of a beginner. And
> > could
> > >> > > not find any obvius flaws in the main structure. Left-side
> > collection
> > >> > > of links is in a very good shape, good for beginner-level
> > navigation
> > >> > > and contains almost all links you listed here.
> > >> > >
> > >> > > This was a really refreshing morning :)
> > >> > >
> > >> > > I'll ask some guys who are new to the project, how they feel
> > about
> > >the
> > >> > > site. And will report back, if I find something.
> > >> > >
> > >> > > Refreshing morning is over, now back to work..

[doc] Anybody tried DRLVM+Eclipse and can share? [WAS: Re: FW: [build] Building on Eclipse - FYI]

[Morozova, Nadezhda]

Resending the email. Really sad that we haven't received any feedback
yet. 

Thank you, 
Nadya Morozova
 

-Original Message-
From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 09, 2006 11:11 PM
To: harmony-dev@incubator.apache.org
Subject: Anybody tried DRLVM+Eclipse and can share? [WAS: Re: FW:
[build] Building on Eclipse - FYI]

Folks, 

Has anybody tried working with DRLVM in Eclipse? did you have to screw
it before it ran ok? Do you have anything to share? Let's write a doc! 

Background
We've been trying to gather useful info on working with Eclipse and our
code base. Eclipse+classlib page has been updated, see JIRA H2009.
The only drlvm-oriented doc that mentions Eclipse is Getting Started
with DRLVM. The doc is terrifically outdated. 

If anybody has relevant updates, we could update the document/write a
new one/add to eclipse+classlib page to make it cover both vm and
classlib. Volunteers? 

Thank you, 
Nadya Morozova

 
 

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
Sent: Thursday, November 09, 2006 7:41 PM
To: harmony-dev@incubator.apache.org
Subject: Re: FW: [build] Building on Eclipse - FYI

On the 0x21C day of Apache Harmony Geir Magnusson, Jr. wrote:
> Egor Pasko wrote:
> > On the 0x21C day of Apache Harmony Geir Magnusson, Jr. wrote:
> >> Egor Pasko wrote:
> >>> On the 0x21C day of Apache Harmony Geir Magnusson, Jr. wrote:
> >>>> Egor Pasko wrote:
> >>>>> On the 0x21C day of Apache Harmony Sian January wrote:
> >>>>>> Hello again,
> >>>>>>
> >>>>>> I have had a closer look at the  "Developing Apache Harmony
Class-library
> >>>>>> Code with Eclipse" page, and I have noticed that the
"Configuring Eclipse"
> >>>>>> and "Develop and Test Code" sections are quite class-library
specific.
> >>>>>> Would it be better to leave those sections as they are and add
a "Developing
> >>>>>> DRLVM with Eclipse" section on the same page?
> >>>>> To the moment I am not aware of anybody who would use Eclipse
for
> >>>>> DRLVM development. So, it's too early to add a page like this.
> >>>> This will ensure that no one does then - if it's simple to add,
lets
> >>>> add it...
> >>> Does it help anybody? I see no point in doing redundant work even
if
> >>> it is small.
> >> Why is it redundant?
> > Nobody uses, nobody reads -> redundant. Am I missing something? :)
> 
> if we don't have it, of course nobody uses or reads it...

OK. Let me put it the other way. If someone has something valuable,
not obvious to write about DRLVM+Eclipse, I am for it. If the page is
going to be just a long-living stub, I am not happy.

-- 
Egor Pasko

RE: Re: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

; > > >
> > > > On the 0x21D day of Apache Harmony Nadezhda Morozova wrote:
> > > > > Egor,
> > > > > I generally like the idea of improving navigation over the
site
> -
> > > > > there's never too much of that. However, I am not sure whether
> we need
> > > > > yet another separate page for introductory/guidance info. I
hope
> the
> > > > > starting page + the generic pages we have are mostly fine.
> However,
> > > > > adding a link here and there to lead site visitors.
> > > > >
> > > > > Getting started could be a more specific project-oriented
page.
> There,
> > > > > you can tell people to go download,
> build
> > > > the
> > > > > code. After which, they can start using it just as any other
> > > > > RI-compatible jdk. With the exceptions, see our
> > > > > wiki pages.
> > > > > To use the vm, readers might need to use the following
> options...
> > > > > If they want to read more on our VM, they can visit the
> > > > > component page. If no website page contains an
> answer -
> > > > > they can read wiki faqa.
> > > > > .. or something like that :)
> > > >
> > > > Nadya, I really appreciate our efforts :) But this morning I
woke
> up
> > > > and looked the site structure with the eye of a beginner. And
> could
> > > > not find any obvius flaws in the main structure. Left-side
> collection
> > > > of links is in a very good shape, good for beginner-level
> navigation
> > > > and contains almost all links you listed here.
> > > >
> > > > This was a really refreshing morning :)
> > > >
> > > > I'll ask some guys who are new to the project, how they feel
about
> the
> > > > site. And will report back, if I find something.
> > > >
> > > > Refreshing morning is over, now back to work..
> > > >
> > > > > Thank you,
> > > > > Nadya Morozova
> > > > >
> > > > > -Original Message-
> > > > > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
> > > > > Sent: Thursday, November 09, 2006 5:33 PM
> > > > > To: harmony-dev@incubator.apache.org
> > > > > Subject: Re: [doc][drlvm] The document "Getting started with
> DRL" is
> > > > > outdated
> > > > >
> > > > > On the 0x21C day of Apache Harmony Pavel Ozhdikhin wrote:
> > > > > > On 11/9/06, Morozova, Nadezhda <[EMAIL PROTECTED]>
> wrote:
> > > > > > >
> > > > > > > Egor,
> > > > > > > +1 for
> > > > > > > Just idea: "Getting Started" may contain a collection of
> links to
> > > > > the
> > > > > > > main website and other resources with short descriptions
> ("Site
> > > > Map"
> > > > > > > or something) so that people are comfortable floating
around
> in
> > > > the
> > > > > web.
> > > > > >
> > > > > >
> > > > > >
> > > > > > We already have one page having links to the resources about
> DRLVM:
> > > > > >
> http://incubator.apache.org/harmony/subcomponents/drlvm/index.html
> > > > > > Why do you think we need another one?
> > > > >
> > > > > because it is only DRLVM.
> > > > > I think of something like "site map", a collection of links.
> Short
> > > > > descriptions to some basic ones.
> > > > >
> > > > > >
> > > > > > +1 for
> > > > > > > * preparing the "Commonly Used Options for DRLVM"
(omitting
> the
> > > > word
> > > > > > > "supported" intentionally)
> > > > > > > Question on this one: will the page contain vm-only
options?
> What
> > > > > about
> > > > > > > JIT, GC, other? I'd have them all in one place, but we
have
> > > > separate
> > > > > > > docs for EM/jit stuff. What do you say?
> > > > > >
> > > > > >
> > > > > > I think we can describe basic options for every component
> there.
> > > > Only
> > > > > those
> > > > > >

RE: Re: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

ng list. Commercial websites have something like
> >> > "support/suggestions mailto". We can point mailto to the mailing
> list
> >:)
> >> >
> >> > > Thank you,
> >> > > Nadya Morozova
> >> > >
> >> > > -Original Message-
> >> > > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
> >> > > Sent: Friday, November 10, 2006 8:55 AM
> >> > > To: harmony-dev@incubator.apache.org
> >> > > Subject: Re: [doc][drlvm] The document "Getting started with
DRL"
> is
> >> > > outdated
> >> > >
> >> > > On the 0x21D day of Apache Harmony Nadezhda Morozova wrote:
> >> > > > Egor,
> >> > > > I generally like the idea of improving navigation over the
site
> -
> >> > > > there's never too much of that. However, I am not sure
whether
> we
> >need
> >> > > > yet another separate page for introductory/guidance info. I
> hope
> >the
> >> > > > starting page + the generic pages we have are mostly fine.
> However,
> >> > > > adding a link here and there to lead site visitors.
> >> > > >
> >> > > > Getting started could be a more specific project-oriented
page.
> >There,
> >> > > > you can tell people to go download,
> build
> >> > > the
> >> > > > code. After which, they can start using it just as any other
> >> > > > RI-compatible jdk. With the exceptions, see our
> >> > > > wiki pages.
> >> > > > To use the vm, readers might need to use the following
> options...
> >> > > > If they want to read more on our VM, they can visit the
> >> > > > component page. If no website page contains an
> answer
> >-
> >> > > > they can read wiki faqa.
> >> > > > .. or something like that :)
> >> > >
> >> > > Nadya, I really appreciate our efforts :) But this morning I
woke
> up
> >> > > and looked the site structure with the eye of a beginner. And
> could
> >> > > not find any obvius flaws in the main structure. Left-side
> collection
> >> > > of links is in a very good shape, good for beginner-level
> navigation
> >> > > and contains almost all links you listed here.
> >> > >
> >> > > This was a really refreshing morning :)
> >> > >
> >> > > I'll ask some guys who are new to the project, how they feel
> about
> >the
> >> > > site. And will report back, if I find something.
> >> > >
> >> > > Refreshing morning is over, now back to work..
> >> > >
> >> > > > Thank you,
> >> > > > Nadya Morozova
> >> > > >
> >> > > > -Original Message-
> >> > > > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor
Pasko
> >> > > > Sent: Thursday, November 09, 2006 5:33 PM
> >> > > > To: harmony-dev@incubator.apache.org
> >> > > > Subject: Re: [doc][drlvm] The document "Getting started with
> DRL"
> >is
> >> > > > outdated
> >> > > >
> >> > > > On the 0x21C day of Apache Harmony Pavel Ozhdikhin wrote:
> >> > > > > On 11/9/06, Morozova, Nadezhda
<[EMAIL PROTECTED]>
> >wrote:
> >> > > > > >
> >> > > > > > Egor,
> >> > > > > > +1 for
> >> > > > > > Just idea: "Getting Started" may contain a collection of
> links
> >to
> >> > > > the
> >> > > > > > main website and other resources with short descriptions
> ("Site
> >> > > Map"
> >> > > > > > or something) so that people are comfortable floating
> around in
> >> > > the
> >> > > > web.
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > We already have one page having links to the resources
about
> >DRLVM:
> >> > > > >
> >http://incubator.apache.org/harmony/subcomponents/drlvm/index.html
> >> > > > > Why do you think we need another one?
> >> > > >
> >> > > > because it is only DRLVM.
> >> > > > I thi

RE: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

Geir, all,
I did not mean to delete info that is relevant. It's just that the old
getting started is old and not so good. Specifics: 
- all cmd options are out of date; recent options are stored on wiki and
explained in jit-related docs (we'll seem them once the unresolved jiras
are applied); old stuff should be deleted
- working with eclipse scenarios are now huge (too many screenshots with
little value) and give info not related to our project; we decided to
remove the bulk of screenshots and info that is about eclipse and not
about us; the drlvm+eclipse specifics will be stored on the page devoted
to eclipse - so we keep the important stuff and send readers to
eclipse.org for eclipse generics - a patch is now available and I also
launched a poll to see if anyone has info to share.
- many specific items are out of date 

If you go over the content of the old getting started doc and flesh out
all the unneeded stuff, it only leaves a small heap of useful info. We
shall try not to lose those bits. 
I also got it that we'll have some getting started info, but probably
different from what we used to have. I'd try my best to produce a draft
next week, but I'm not a guru to know what a tutorial for beginners
should include :(

Thank you, 
Nadya Morozova
 
-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 10, 2006 5:55 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
outdated



Morozova, Nadezhda wrote:
> Alexei,
> Tutorials might be fine for mature projects, but I do not think ours
is
> ready for a big flow of users yet, that would require a tutorial.
> So +1 for having a nice good  tutorial ... one day. 
> If there are volunteers to write the tutorial now, I'd be happy to
help
> though.

Isn't that what the getting started page for DRLVM is?  why take 
information away?  I agre, we should clean things up if they are wrong, 
but as long as it's organized, we should keep stuff.

geir

> 
> Thank you, 
> Nadya Morozova
>  
> -Original Message-
> From: Fedotov, Alexei A [mailto:[EMAIL PROTECTED] 
> Sent: Friday, November 10, 2006 1:40 PM
> To: harmony-dev@incubator.apache.org
> Subject: RE: Re: [doc][drlvm] The document "Getting started with DRL"
is
> outdated
> 
> Guys,
> 
> I like good tutorials. I learned VIM using a tutorial. I don't need
the
> VIM tutorial any longer, but at the beginning it was useful.
> 
>   +1 for maintain Getting Started as is with minor changes
> 
> Why Eclipse was chosen for the tutorial? Our goal was to use Harmony
for
> Harmony development. I liked that idea.
> 
> With best regards,
> Alexei Fedotov,
> Intel Java & XML Engineering
> 
>> -Original Message-
>> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
>> Sent: Friday, November 10, 2006 1:29 PM
>> To: harmony-dev@incubator.apache.org
>> Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
>> outdated
>>
>> On the 0x21D day of Apache Harmony Pavel Ozhdikhin wrote:
>>> Nadya,
>>>
>>> One more proposal about "Getting Started": let's remove all current
>> content
>>> and write something like following:
>>>
>>> "To the moment we got rid of all major differences from other Java
>>> implementations, so to use DRLVM you can just build it (here goes
> link to
>>> readme with build instructions) and run as any other Java VM. For
>> commonly
>>> used command-line options please look into the Wiki page (link to
>> Salikh's
>>> page or to the document)."
>>>
>>> What do you think?
>> 1 page to hold only 4 lines of text? :)
>>
>>> Thanks,
>>> Pavel
>>>
>>>
>>> On 10 Nov 2006 14:29:59 +0600, Egor Pasko <[EMAIL PROTECTED]>
> wrote:
>>>> On the 0x21D day of Apache Harmony Nadezhda Morozova wrote:
>>>>> Good day to you, Egor!
>>>> evening, dark and snowy evening :)
>>>>
>>>>> What do you say about the getting started doc?
>>>> I expressed it recently. General idea is that Harmony operates near
>>>> the same as other JSE implementations. Almost all specifics is in
>>>> extra options which we started collecting on Wiki for an extra
>>>> HOWTO-like page (BTW, thanks to Salikh for starting the page).
>>>>
>>>> I believe, it is time to remove the "Getting Started". So, +1 to
> Pavel
>>>> Ozhdikhin here.
>>>>
>>>> BTW, I asked my dad to look at the website. Ideas for improvem

RE: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

+1 to write a new getting started page. 

Distribution of its old content:
- start an application: same as in other vms, might not need it
- start an app in eclipse, 
- debug an app in eclipse: nowhere, need to expand the Working with
Eclipse page instead
- cmd options: wiki page 
Did I miss anything? 

Thank you, 
Nadya Morozova
 

-Original Message-
From: Pavel Ozhdikhin [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 10, 2006 12:19 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
outdated

Nadya,

One more proposal about "Getting Started": let's remove all current
content
and write something like following:

"To the moment we got rid of all major differences from other Java
implementations, so to use DRLVM you can just build it (here goes link
to
readme with build instructions) and run as any other Java VM. For
commonly
used command-line options please look into the Wiki page (link to
Salikh's
page or to the document)."

What do you think?

Thanks,
Pavel


On 10 Nov 2006 14:29:59 +0600, Egor Pasko <[EMAIL PROTECTED]> wrote:
>
> On the 0x21D day of Apache Harmony Nadezhda Morozova wrote:
> > Good day to you, Egor!
>
> evening, dark and snowy evening :)
>
> > What do you say about the getting started doc?
>
> I expressed it recently. General idea is that Harmony operates near
> the same as other JSE implementations. Almost all specifics is in
> extra options which we started collecting on Wiki for an extra
> HOWTO-like page (BTW, thanks to Salikh for starting the page).
>
> I believe, it is time to remove the "Getting Started". So, +1 to Pavel
> Ozhdikhin here.
>
> BTW, I asked my dad to look at the website. Ideas for improvement from
> him:
> 1) site-local search is useful for a beginner. Hm, Tomcat has it with
> links to google search. We can have something as soon as we get to the
> desired TLP :)
> 2) it is not obvious that site misprints/problems should be reported
> to the mailing list. Commercial websites have something like
> "support/suggestions mailto". We can point mailto to the mailing list
:)
>
> > Thank you,
> > Nadya Morozova
> >
> > -Original Message-
> > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
> > Sent: Friday, November 10, 2006 8:55 AM
> > To: harmony-dev@incubator.apache.org
> > Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
> > outdated
> >
> > On the 0x21D day of Apache Harmony Nadezhda Morozova wrote:
> > > Egor,
> > > I generally like the idea of improving navigation over the site -
> > > there's never too much of that. However, I am not sure whether we
need
> > > yet another separate page for introductory/guidance info. I hope
the
> > > starting page + the generic pages we have are mostly fine.
However,
> > > adding a link here and there to lead site visitors.
> > >
> > > Getting started could be a more specific project-oriented page.
There,
> > > you can tell people to go download,
build
> > the
> > > code. After which, they can start using it just as any other
> > > RI-compatible jdk. With the exceptions, see our
> > > wiki pages.
> > > To use the vm, readers might need to use the following options...
> > > If they want to read more on our VM, they can visit the
> > > component page. If no website page contains an answer
-
> > > they can read wiki faqa.
> > > .. or something like that :)
> >
> > Nadya, I really appreciate our efforts :) But this morning I woke up
> > and looked the site structure with the eye of a beginner. And could
> > not find any obvius flaws in the main structure. Left-side
collection
> > of links is in a very good shape, good for beginner-level navigation
> > and contains almost all links you listed here.
> >
> > This was a really refreshing morning :)
> >
> > I'll ask some guys who are new to the project, how they feel about
the
> > site. And will report back, if I find something.
> >
> > Refreshing morning is over, now back to work..
> >
> > > Thank you,
> > > Nadya Morozova
> > >
> > > -Original Message-
> > > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
> > > Sent: Thursday, November 09, 2006 5:33 PM
> > > To: harmony-dev@incubator.apache.org
> > > Subject: Re: [doc][drlvm] The document "Getting started with DRL"
is
> > > outdated
> > >
> > > On the 0x21C day of Apache Harmony Pavel Ozhdikhin wrote:
> > > > On 11/9/06, Moroz

RE: Re: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

+1 for having some getting started info on a separate page. 
There are some things that need to stand out promptly, and probably
newbie info is one of them (I mean, I'd want to have such a page when I
got started with this project). 

We can expand the text suggested by Pavel by adding:
* links to nice tutorials for other vms
* a short section to say how is a vm used with a couple of examples;
this won't take too much effort/maintenance but would be a nice clear
intro, that's not another click away on some site of another project

Thank you, 
Nadya Morozova
 

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
Sent: Friday, November 10, 2006 1:29 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
outdated

On the 0x21D day of Apache Harmony Pavel Ozhdikhin wrote:
> Nadya,
> 
> One more proposal about "Getting Started": let's remove all current
content
> and write something like following:
> 
> "To the moment we got rid of all major differences from other Java
> implementations, so to use DRLVM you can just build it (here goes link
to
> readme with build instructions) and run as any other Java VM. For
commonly
> used command-line options please look into the Wiki page (link to
Salikh's
> page or to the document)."
> 
> What do you think?

1 page to hold only 4 lines of text? :)

> Thanks,
> Pavel
> 
> 
> On 10 Nov 2006 14:29:59 +0600, Egor Pasko <[EMAIL PROTECTED]>
wrote:
> >
> > On the 0x21D day of Apache Harmony Nadezhda Morozova wrote:
> > > Good day to you, Egor!
> >
> > evening, dark and snowy evening :)
> >
> > > What do you say about the getting started doc?
> >
> > I expressed it recently. General idea is that Harmony operates near
> > the same as other JSE implementations. Almost all specifics is in
> > extra options which we started collecting on Wiki for an extra
> > HOWTO-like page (BTW, thanks to Salikh for starting the page).
> >
> > I believe, it is time to remove the "Getting Started". So, +1 to
Pavel
> > Ozhdikhin here.
> >
> > BTW, I asked my dad to look at the website. Ideas for improvement
from
> > him:
> > 1) site-local search is useful for a beginner. Hm, Tomcat has it
with
> > links to google search. We can have something as soon as we get to
the
> > desired TLP :)
> > 2) it is not obvious that site misprints/problems should be reported
> > to the mailing list. Commercial websites have something like
> > "support/suggestions mailto". We can point mailto to the mailing
list :)
> >
> > > Thank you,
> > > Nadya Morozova
> > >
> > > -Original Message-
> > > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
> > > Sent: Friday, November 10, 2006 8:55 AM
> > > To: harmony-dev@incubator.apache.org
> > > Subject: Re: [doc][drlvm] The document "Getting started with DRL"
is
> > > outdated
> > >
> > > On the 0x21D day of Apache Harmony Nadezhda Morozova wrote:
> > > > Egor,
> > > > I generally like the idea of improving navigation over the site
-
> > > > there's never too much of that. However, I am not sure whether
we need
> > > > yet another separate page for introductory/guidance info. I hope
the
> > > > starting page + the generic pages we have are mostly fine.
However,
> > > > adding a link here and there to lead site visitors.
> > > >
> > > > Getting started could be a more specific project-oriented page.
There,
> > > > you can tell people to go download,
build
> > > the
> > > > code. After which, they can start using it just as any other
> > > > RI-compatible jdk. With the exceptions, see our
> > > > wiki pages.
> > > > To use the vm, readers might need to use the following
options...
> > > > If they want to read more on our VM, they can visit the
> > > > component page. If no website page contains an
answer -
> > > > they can read wiki faqa.
> > > > .. or something like that :)
> > >
> > > Nadya, I really appreciate our efforts :) But this morning I woke
up
> > > and looked the site structure with the eye of a beginner. And
could
> > > not find any obvius flaws in the main structure. Left-side
collection
> > > of links is in a very good shape, good for beginner-level
navigation
> > > and contains almost all links you listed here.
> > >
> > > This was a really refreshing morning :)

RE: Re: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

t to read more on our VM, they can visit the
>> > > > component page. If no website page contains an
answer
>-
>> > > > they can read wiki faqa.
>> > > > .. or something like that :)
>> > >
>> > > Nadya, I really appreciate our efforts :) But this morning I woke
up
>> > > and looked the site structure with the eye of a beginner. And
could
>> > > not find any obvius flaws in the main structure. Left-side
collection
>> > > of links is in a very good shape, good for beginner-level
navigation
>> > > and contains almost all links you listed here.
>> > >
>> > > This was a really refreshing morning :)
>> > >
>> > > I'll ask some guys who are new to the project, how they feel
about
>the
>> > > site. And will report back, if I find something.
>> > >
>> > > Refreshing morning is over, now back to work..
>> > >
>> > > > Thank you,
>> > > > Nadya Morozova
>> > > >
>> > > > -Original Message-
>> > > > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
>> > > > Sent: Thursday, November 09, 2006 5:33 PM
>> > > > To: harmony-dev@incubator.apache.org
>> > > > Subject: Re: [doc][drlvm] The document "Getting started with
DRL"
>is
>> > > > outdated
>> > > >
>> > > > On the 0x21C day of Apache Harmony Pavel Ozhdikhin wrote:
>> > > > > On 11/9/06, Morozova, Nadezhda <[EMAIL PROTECTED]>
>wrote:
>> > > > > >
>> > > > > > Egor,
>> > > > > > +1 for
>> > > > > > Just idea: "Getting Started" may contain a collection of
links
>to
>> > > > the
>> > > > > > main website and other resources with short descriptions
("Site
>> > > Map"
>> > > > > > or something) so that people are comfortable floating
around in
>> > > the
>> > > > web.
>> > > > >
>> > > > >
>> > > > >
>> > > > > We already have one page having links to the resources about
>DRLVM:
>> > > > >
>http://incubator.apache.org/harmony/subcomponents/drlvm/index.html
>> > > > > Why do you think we need another one?
>> > > >
>> > > > because it is only DRLVM.
>> > > > I think of something like "site map", a collection of links.
Short
>> > > > descriptions to some basic ones.
>> > > >
>> > > > >
>> > > > > +1 for
>> > > > > > * preparing the "Commonly Used Options for DRLVM" (omitting
the
>> > > word
>> > > > > > "supported" intentionally)
>> > > > > > Question on this one: will the page contain vm-only
options?
>What
>> > > > about
>> > > > > > JIT, GC, other? I'd have them all in one place, but we have
>> > > separate
>> > > > > > docs for EM/jit stuff. What do you say?
>> > > > >
>> > > > >
>> > > > > I think we can describe basic options for every component
there.
>> > > Only
>> > > > those
>> > > > > that might be interesting for any user. The place for other
>options
>> > > is
>> > > > in
>> > > > > the run-time help or Developer's Guide for a component.
>> > > >
>> > > > I thought of "most commonly used" options. They can possibly be
>> > > > grouped by components, but not necessary. I would group them by
>> > > > use-cases. BTW, "any user" is not an obvious substance for me.
>> > > >
>> > > > So, the list is not obvious, we need to work it out.
>> > > >
>> > > > I see it like HOWTOs. For example:
>> > > > "-Xem:jet <- use only baseline JIT compiler"
>> > > > "-Xem:opt <- use only optimising JIT compiler"
>> > > > "-Xtrace:em <- print method compilation events"
>> > > >
>> > > > The 'big' question is: "does 'any user' need to know about JITs
>> > > > switching?". I say YES, it helps users to investigate problems,
>which
>> > > > helps us, developers, to react o

RE: Re: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

Good day to you, Egor! 
What do you say about the getting started doc?

Thank you, 
Nadya Morozova
 
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
Sent: Friday, November 10, 2006 8:55 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
outdated

On the 0x21D day of Apache Harmony Nadezhda Morozova wrote:
> Egor,
> I generally like the idea of improving navigation over the site -
> there's never too much of that. However, I am not sure whether we need
> yet another separate page for introductory/guidance info. I hope the
> starting page + the generic pages we have are mostly fine. However,
> adding a link here and there to lead site visitors. 
> 
> Getting started could be a more specific project-oriented page. There,
> you can tell people to go download, build
the
> code. After which, they can start using it just as any other
> RI-compatible jdk. With the exceptions, see our
> wiki pages.
> To use the vm, readers might need to use the following options...
> If they want to read more on our VM, they can visit the
> component page. If no website page contains an answer -
> they can read wiki faqa. 
> .. or something like that :) 

Nadya, I really appreciate our efforts :) But this morning I woke up
and looked the site structure with the eye of a beginner. And could
not find any obvius flaws in the main structure. Left-side collection
of links is in a very good shape, good for beginner-level navigation
and contains almost all links you listed here.

This was a really refreshing morning :)

I'll ask some guys who are new to the project, how they feel about the
site. And will report back, if I find something.

Refreshing morning is over, now back to work..

> Thank you, 
> Nadya Morozova
>  
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
> Sent: Thursday, November 09, 2006 5:33 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
> outdated
> 
> On the 0x21C day of Apache Harmony Pavel Ozhdikhin wrote:
> > On 11/9/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
> > >
> > > Egor,
> > > +1 for
> > > Just idea: "Getting Started" may contain a collection of links to
> the
> > > main website and other resources with short descriptions ("Site
Map"
> > > or something) so that people are comfortable floating around in
the
> web.
> > 
> > 
> > 
> > We already have one page having links to the resources about DRLVM:
> > http://incubator.apache.org/harmony/subcomponents/drlvm/index.html
> > Why do you think we need another one?
> 
> because it is only DRLVM.
> I think of something like "site map", a collection of links. Short
> descriptions to some basic ones.
> 
> > 
> > +1 for
> > > * preparing the "Commonly Used Options for DRLVM" (omitting the
word
> > > "supported" intentionally)
> > > Question on this one: will the page contain vm-only options? What
> about
> > > JIT, GC, other? I'd have them all in one place, but we have
separate
> > > docs for EM/jit stuff. What do you say?
> > 
> > 
> > I think we can describe basic options for every component there.
Only
> those
> > that might be interesting for any user. The place for other options
is
> in
> > the run-time help or Developer's Guide for a component.
> 
> I thought of "most commonly used" options. They can possibly be
> grouped by components, but not necessary. I would group them by
> use-cases. BTW, "any user" is not an obvious substance for me. 
> 
> So, the list is not obvious, we need to work it out.
> 
> I see it like HOWTOs. For example:
> "-Xem:jet <- use only baseline JIT compiler"
> "-Xem:opt <- use only optimising JIT compiler"
> "-Xtrace:em <- print method compilation events"
> 
> The 'big' question is: "does 'any user' need to know about JITs
> switching?". I say YES, it helps users to investigate problems, which
> helps us, developers, to react on users' input faster.
> 
> Other options? I can enlist the set of most commonly used by me. If
> many of us put their lists here, we can sum them up quickly and make
> a good (really useful) list of popular options. How about that?
> 
> BTW, the list should not be too big. 25 options is a kind of limit
> 
> > Thanks,
> > Pavel
> > 
> > Thank you,
> > > Nadya Morozova
> > >
> > > -Original Message-
&g

RE: [build] Building on Eclipse - FYI

[Morozova, Nadezhda]

Sian, 
As I understand, thanks to your patches, we now have a nice webpage that
describes generics + classlib specifics, with a few items for drlvm.
This is an achievement as it is, so perhaps, we can hold off rolling
back to classlib only :)
I sent an email just now to ask people whether anybody has anything to
share on eclipse+drlvm. Depending on what comes out of this little poll,
we could decide on distributed content. What do you say?

Thank you, 
Nadya Morozova
 

-Original Message-
From: Sian January [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 09, 2006 6:41 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [build] Building on Eclipse - FYI

Yes that sounds fine.  Shall I update my patch to remove the DRLVM
references, or would you prefer to?  Since I did not write very much
about
DRLVM we could leave that out for now and then the person who updates
"Getting Started with DRLVM" could choose to add something there if
people
feel it's appropriate.

Regards,

Sian


On 09/11/06, Konovalova, Svetlana <[EMAIL PROTECTED]> wrote:
>
> Folks,
> Looking through the site and figuring out how to improve the docs that
> include info on Eclipse, the following ideas came up to my mind:
> 1) Since the "Developing Apache Harmony Class-library
> Code with Eclipse" page [1] is mostly class-library oriented, I
suggest
> reviewing it to remove purely DRLVM-oriented info and leave the page
> where it is now [subcomponents/classlibrary/dev_eclipse.html].
> 2) Add the link from the Quick Help pages to the "Developing Apache
> Harmony Class-library Code with Eclipse" page [1].
> 3) Gather purely DRLVM-oriented info to store it in the "Getting
Started
> with DRL" doc (hope it won't be wiped off the face of the earth; for
> details, see the discussion thread: [doc][drlvm] The document "Getting
> started with DRL" is outdated)
> In this case, we'll get two docs providing info on developing with
> Eclipse:
> [1] - describing how to develop class-library code with Eclipse, and
"GS
> with DRL"(or whatever it'll be) describing how to develop DRLVM
> application in Eclipse.
> Any objections? What do you think? Please right me if I'm wrong.
>
> Best regards,
> Sveta Konovalova
>
> [1]
>
http://incubator.apache.org/harmony/subcomponents/classlibrary/dev_eclip
> se.html
>
>
> -Original Message-
> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 09, 2006 3:58 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: FW: [build] Building on Eclipse - FYI
>
>
>
> Egor Pasko wrote:
> > On the 0x21C day of Apache Harmony Sian January wrote:
> >> Hello again,
> >>
> >> I have had a closer look at the  "Developing Apache Harmony
> Class-library
> >> Code with Eclipse" page, and I have noticed that the "Configuring
> Eclipse"
> >> and "Develop and Test Code" sections are quite class-library
> specific.
> >> Would it be better to leave those sections as they are and add a
> "Developing
> >> DRLVM with Eclipse" section on the same page?
> >
> > To the moment I am not aware of anybody who would use Eclipse for
> > DRLVM development. So, it's too early to add a page like this.
>
> This will ensure that no one does then - if it's simple to add, lets
add
>
> it...
>
> geir
>
> >
> >> Thanks,
> >>
> >> Sian
> >>
> >>
> >>
> >> On 07/11/06, Konovalova, Svetlana <[EMAIL PROTECTED]>
> wrote:
> >>>
> >>> Sian,
> >>> Sorry for delay in response.
>  I'd like to help with documentation but I don't want to duplicate
> any
> >>> work
>  that you are in the middle of, so let me know if there's anything
> >>> specific >I can do...
> >>> Thanks for your desire to help!
> >>> Well, let's work at the page "Developing Apache Harmony
> Class-library
> >>> Code with Eclipse"
> >>>
>
[http://incubator.apache.org/harmony/subcomponents/classlibrary/dev_ecli
> >>> pse.html] first, if you do not mind.
> >>> AFAIK the majority of items on the page can equally apply to DRLVM
> and
> >>> classlib. IMHO would be great to edit the page to remove
unnecessary
> >>> focus on classlib, to make the page equally relevant for vm
> developers.
> >>> To my mind, the introductory sections should be removed, as they
are
> >>> about generalities that do not always relate to the header of the
> page.
> >>> Could you please take a close look at the page and create the
patch
> to
> >>> improve the content and to remove all classlib-specific info? You
> can
> >>> use Harmony-2009 for it. It would be a great impact into
development
> of
> >>> the site documentation for sure! If you need my help, just let me
> know.
> >>> The second idea is to move the page up, not to store it in
> >>> subcomponents/classlib. To make it easily accessible, we can store
> it in
> >>> top xdocs folder and link to the page from documentation.html,
quick
> >>> helps and other build-development web pages.
> >>> If you do not have any objections, I can create a patch with the
> >>> necessary links.
> >>> What do you think?
> >>>
> >>> Best regards,
> >>> S

Anybody tried DRLVM+Eclipse and can share? [WAS: Re: FW: [build] Building on Eclipse - FYI]

[Morozova, Nadezhda]

Folks, 

Has anybody tried working with DRLVM in Eclipse? did you have to screw
it before it ran ok? Do you have anything to share? Let's write a doc! 

Background
We've been trying to gather useful info on working with Eclipse and our
code base. Eclipse+classlib page has been updated, see JIRA H2009.
The only drlvm-oriented doc that mentions Eclipse is Getting Started
with DRLVM. The doc is terrifically outdated. 

If anybody has relevant updates, we could update the document/write a
new one/add to eclipse+classlib page to make it cover both vm and
classlib. Volunteers? 

Thank you, 
Nadya Morozova

 
 

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
Sent: Thursday, November 09, 2006 7:41 PM
To: harmony-dev@incubator.apache.org
Subject: Re: FW: [build] Building on Eclipse - FYI

On the 0x21C day of Apache Harmony Geir Magnusson, Jr. wrote:
> Egor Pasko wrote:
> > On the 0x21C day of Apache Harmony Geir Magnusson, Jr. wrote:
> >> Egor Pasko wrote:
> >>> On the 0x21C day of Apache Harmony Geir Magnusson, Jr. wrote:
>  Egor Pasko wrote:
> > On the 0x21C day of Apache Harmony Sian January wrote:
> >> Hello again,
> >>
> >> I have had a closer look at the  "Developing Apache Harmony
Class-library
> >> Code with Eclipse" page, and I have noticed that the
"Configuring Eclipse"
> >> and "Develop and Test Code" sections are quite class-library
specific.
> >> Would it be better to leave those sections as they are and add
a "Developing
> >> DRLVM with Eclipse" section on the same page?
> > To the moment I am not aware of anybody who would use Eclipse
for
> > DRLVM development. So, it's too early to add a page like this.
>  This will ensure that no one does then - if it's simple to add,
lets
>  add it...
> >>> Does it help anybody? I see no point in doing redundant work even
if
> >>> it is small.
> >> Why is it redundant?
> > Nobody uses, nobody reads -> redundant. Am I missing something? :)
> 
> if we don't have it, of course nobody uses or reads it...

OK. Let me put it the other way. If someone has something valuable,
not obvious to write about DRLVM+Eclipse, I am for it. If the page is
going to be just a long-living stub, I am not happy.

-- 
Egor Pasko

RE: [jira] Good issue resolution guideline (was: [classlib]volunteer to supply patches for old JIRAs)

[Morozova, Nadezhda]

Alexey,
I agree  that the structure of the resulting HTML website page does not
appear too linear. When editing the structure, I saw the additional
table - and left as is; maybe, because I hoped somebody added it on some
purpose. For me, the only matter of convenience is that all content that
is varied on the page is in a separate table. 
If nobody has an idea why the structure is so complex, we can simplify
it. The structure is defined in file site.vsl in site/xdocs/stylesheets.
A JIRA with patch is welcome as usual.

Thank you, 
Nadya Morozova
 

-Original Message-
From: Ivanov, Alexey A [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 09, 2006 5:20 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)

Sveta, all,

I've attached the updated patch to the JIRA.

Please review.

Regards,
Alexey.


P.S. By the way, do we really need to place all the main content into
another table? I've just looked at the source of the generated HTML
file, and found it quite confusing. I agree to have a table to format
the heading of the page and the list of contents on the left, but why
there's another table where the main content is. I am about this one:

 
 




   
 
Good Issue
Resolution Guideline

   
   ... 

The comments here are added by me, and the source is slightly
reformatted.
I believe, the  part of the XML can be placed almost as is in the
content cell of the top-level table without the need for another table
because it's useless here. Or is it just Anakia limitation?

--
Alexey A. Ivanov
Intel Enterprise Solutions Software Division


>-Original Message-
>From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED]
>Sent: Thursday, November 09, 2006 3:50 PM
>To: harmony-dev@incubator.apache.org
>Subject: RE: [jira] Good issue resolution guideline (was:
>[classlib]volunteer to supply patches for old JIRAs)
>
>Alexey,
>
>>>I'd change the heading "Reporting the Issue" to "Reporting an Issue",
>>>or omit article at all.
>>> Well, both articles seem to be fine. Let it be "a/an"
>>Maybe just omit articles then?
>Well, how about the third variant: "Reporting Issues"?
>
>
>>I'm still for 'reproduce' because a bug can be (non-)reproducible but
>>not recreatable.
>>Any other opinions?
>Ok, "reproduce" is fine
>
>>>I'd say: "If you have any questions, discuss them...
>>That's even better :)
>Cool!:)
>
>>>All patches, such as tests and fixes, should be
>>Good! It's clearer.
>Fine!
>
>>OK. I'll prepare patch update then.
>Good luck! I'd be glad to review it, if you do not mind. :)
>
>Cheers,
>Sveta
>
>Thanks,
>Alexey.
>
>>
>>
>>Best regards,
>>Sveta
>>
>>-Original Message-
>>From: Ivanov, Alexey A [mailto:[EMAIL PROTECTED]
>>Sent: Thursday, November 09, 2006 1:33 PM
>>To: harmony-dev@incubator.apache.org
>>Subject: RE: [jira] Good issue resolution guideline (was:
>>[classlib]volunteer to supply patches for old JIRAs)
>>
>>>-Original Message-
>>>From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED]
>>>Sent: Wednesday, November 08, 2006 7:01 PM
>>>To: harmony-dev@incubator.apache.org
>>>Subject: RE: [jira] Good issue resolution guideline (was:
>>>[classlib]volunteer to supply patches for old JIRAs)
>>>
>>>
>>>I've just submitted a new JIRA
>>>[http://issues.apache.org/jira/browse/HARMONY-2110].
>>>I've added the necessary links from the website to the new page and
>>have
>>>tried to perfect it a little.
>>>It would be great, if you could find a chance to look through the
>>patch.
>>>Thanks in advance.
>>
>>Sveta,
>>
>>I've taken a look and added my comments to the JIRA itself.
>>
>>
>>Regards,
>>Alexey.
>>
>>>
>>>Best regards,
>>>Sveta
>>>
>>>-Original Message-
>>>From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED]
>>>Sent: Wednesday, November 08, 2006 11:18 AM
>>>To: harmony-dev@incubator.apache.org
>>>Subject: RE: [jira] Good issue resolution guideline (was:
>>>[classlib]volunteer to supply patches for old JIRAs)
>>>
>>>Good! Go ahead. Do you need help? I can review the patch - just let
me
>>>know when you submit the JIRA.
>>>
>>>Thank you,
>>>Nadya Morozova
>>>
>>>-Original Message-
>>

RE: Re: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

Egor,
I generally like the idea of improving navigation over the site -
there's never too much of that. However, I am not sure whether we need
yet another separate page for introductory/guidance info. I hope the
starting page + the generic pages we have are mostly fine. However,
adding a link here and there to lead site visitors. 

Getting started could be a more specific project-oriented page. There,
you can tell people to go download, build the
code. After which, they can start using it just as any other
RI-compatible jdk. With the exceptions, see our
wiki pages.
To use the vm, readers might need to use the following options...
If they want to read more on our VM, they can visit the
component page. If no website page contains an answer -
they can read wiki faqa. 
.. or something like that :) 

Thank you, 
Nadya Morozova
 
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
Sent: Thursday, November 09, 2006 5:33 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
outdated

On the 0x21C day of Apache Harmony Pavel Ozhdikhin wrote:
> On 11/9/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
> >
> > Egor,
> > +1 for
> > Just idea: "Getting Started" may contain a collection of links to
the
> > main website and other resources with short descriptions ("Site Map"
> > or something) so that people are comfortable floating around in the
web.
> 
> 
> 
> We already have one page having links to the resources about DRLVM:
> http://incubator.apache.org/harmony/subcomponents/drlvm/index.html
> Why do you think we need another one?

because it is only DRLVM.
I think of something like "site map", a collection of links. Short
descriptions to some basic ones.

> 
> +1 for
> > * preparing the "Commonly Used Options for DRLVM" (omitting the word
> > "supported" intentionally)
> > Question on this one: will the page contain vm-only options? What
about
> > JIT, GC, other? I'd have them all in one place, but we have separate
> > docs for EM/jit stuff. What do you say?
> 
> 
> I think we can describe basic options for every component there. Only
those
> that might be interesting for any user. The place for other options is
in
> the run-time help or Developer's Guide for a component.

I thought of "most commonly used" options. They can possibly be
grouped by components, but not necessary. I would group them by
use-cases. BTW, "any user" is not an obvious substance for me. 

So, the list is not obvious, we need to work it out.

I see it like HOWTOs. For example:
"-Xem:jet <- use only baseline JIT compiler"
"-Xem:opt <- use only optimising JIT compiler"
"-Xtrace:em <- print method compilation events"

The 'big' question is: "does 'any user' need to know about JITs
switching?". I say YES, it helps users to investigate problems, which
helps us, developers, to react on users' input faster.

Other options? I can enlist the set of most commonly used by me. If
many of us put their lists here, we can sum them up quickly and make
a good (really useful) list of popular options. How about that?

BTW, the list should not be too big. 25 options is a kind of limit

> Thanks,
> Pavel
> 
> Thank you,
> > Nadya Morozova
> >
> > -Original Message-
> > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
> > Sent: Thursday, November 09, 2006 5:51 AM
> > To: harmony-dev@incubator.apache.org
> > Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
> > outdated
> >
> > On the 0x21B day of Apache Harmony Nadezhda Morozova wrote:
> > > All,
> > > I'd like to share everyone's grief at the sight of outdated
Getting
> > > Started document. However, I'd not hurry to eliminate the page as
> > such.
> > > We might reconsider some of its contents, change structure, and
update
> > > individual bits, but please think carefully before removing the
page.
> > >
> > > I think Getting Started (as the title shows) is aimed to help a
newbie
> > > work with our vm. I know that many primarily interested in other
> > things
> > > - conformance, architecture, internal specifics. However, we
should
> > also
> > > think how the vm is used. AFAIK, Getting started is now the *only*
doc
> > > that tries to show how to use our vm. You tell people how to
download
> > > and build, but almost nothing about how to run and configure (with
the
> > > exception of EM/JIT).
> > >
> > > My suggestion would be to think of what you want to tel

RE: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

Those were the copyrights required by our legal at the donation time. I
share your concern. We probably need a massive review/cleanup of our
legal lines. The disclaimers (number and placement) varies between
different docs.

Thank you, 
Nadya Morozova
 

-Original Message-
From: Alexei Fedotov [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 09, 2006 12:22 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
outdated

Nadya,

I have failed to find web pages copyrighted by IBM on Apache using
Google. Apache copyright usually contains no more than two lines. This
page has fourty lines of legal staff. Is it really needed?

Thanks!


On 11/8/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
> All,
> I'd like to share everyone's grief at the sight of outdated Getting
> Started document. However, I'd not hurry to eliminate the page as
such.
> We might reconsider some of its contents, change structure, and update
> individual bits, but please think carefully before removing the page.
>
> I think Getting Started (as the title shows) is aimed to help a newbie
> work with our vm. I know that many primarily interested in other
things
> - conformance, architecture, internal specifics. However, we should
also
> think how the vm is used. AFAIK, Getting started is now the *only* doc
> that tries to show how to use our vm. You tell people how to download
> and build, but almost nothing about how to run and configure (with the
> exception of EM/JIT).
>
> My suggestion would be to think of what you want to tell people about
> usage - with or without eclipse specifics. And store this info on the
> page. I know it is hard - and I offer my help and support in this
> burdensome initiative. Any thoughts? i might be inobjective and
> emotional :)
>
> Thank you,
> Nadya Morozova
>
> -Original Message-
> From: Mikhail Fursov [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 08, 2006 6:03 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
> outdated
>
> It's not a hard to write a documenation once, it's hard to support it
:)
> More problems:
> 1) -Xem options are obsolete.
> 2) -Xjit options are also obsolete.
> 3) Do we really need this page today? AFAIU users expect Harmony VM is
> able
> to run the same apps as RI..
> ?
>
> On 11/8/06, Pavel Ozhdikhin <[EMAIL PROTECTED]> wrote:
> >
> > Hello all,
> > I've read through the "Getting Started with
> > DRL<
> >
>
http://incubator.apache.org/harmony/subcomponents/drlvm/getting_started.
> html
> > >"
> > document on the Harmony web and found it completely outdated, for
> example:
> >
> >
> >- the term DRL is used instead of DRLVM
> >- eclipse.bat and eclipse.sh are obsolete - we don't need them
> anymore
> >to run Eclipse. It can be started with DRLVM the same way as with
> any
> > other
> >VM.
> >- We don't need to set PATH and LD_LIBRARY_PATH anymore, at least
> on
> >Windows/MSVC
> >- ij was renamed to java
> >
> > We took a big step to unification with other Java VMs and now
> > we don't need anything specific to run Eclipse, for example. After
> > removing
> > all irrelevant info the document would contain only the list of
> > command-line
> > options. I think we can move this list to a separate document (Wiki,
> > Developer's Guide?) and remove the "Getting Started" itself.
> >
> > Any opinions?
> >
> > Thanks,
> > Pavel
> > <
> >
>
http://incubator.apache.org/harmony/subcomponents/drlvm/getting_started.
> html
> > >
> >
> >
>
>
> --
> Mikhail Fursov
>


-- 
Thank you,
Alexei

RE: Re: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

Egor, 
+1 for 
Just idea: "Getting Started" may contain a collection of links to the
main website and other resources with short descriptions ("Site Map"
or something) so that people are comfortable floating around in the web.

+1 for 
* preparing the "Commonly Used Options for DRLVM" (omitting the word
  "supported" intentionally)
Question on this one: will the page contain vm-only options? What about
JIT, GC, other? I'd have them all in one place, but we have separate
docs for EM/jit stuff. What do you say?

Thank you, 
Nadya Morozova
 
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
Sent: Thursday, November 09, 2006 5:51 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
outdated

On the 0x21B day of Apache Harmony Nadezhda Morozova wrote:
> All,
> I'd like to share everyone's grief at the sight of outdated Getting
> Started document. However, I'd not hurry to eliminate the page as
such.
> We might reconsider some of its contents, change structure, and update
> individual bits, but please think carefully before removing the page.
> 
> I think Getting Started (as the title shows) is aimed to help a newbie
> work with our vm. I know that many primarily interested in other
things
> - conformance, architecture, internal specifics. However, we should
also
> think how the vm is used. AFAIK, Getting started is now the *only* doc
> that tries to show how to use our vm. You tell people how to download
> and build, but almost nothing about how to run and configure (with the
> exception of EM/JIT). 
> 
> My suggestion would be to think of what you want to tell people about
> usage - with or without eclipse specifics. And store this info on the
> page. I know it is hard - and I offer my help and support in this
> burdensome initiative. Any thoughts? i might be inobjective and
> emotional :)

Nadya,

I believe, almost everyone coming across Harmony knows how to use
J5SE. We are striving for this compatibility, and we are happy that
all DRLVM-specific pecularities are gone.

So, I vote for:
* removing the "Getting Started" (also because of irritating windows
  screenshots:)
* preparing the "Commonly Used Options for DRLVM" (omitting the word
  "supported" intentionally)

Just idea: "Getting Started" may contain a collection of links to the
main website and other resources with short descriptions ("Site Map"
or something) so that people are comfortable floating around in the web.

> -Original Message-
> From: Mikhail Fursov [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, November 08, 2006 6:03 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
> outdated
> 
> It's not a hard to write a documenation once, it's hard to support it
:)
> More problems:
> 1) -Xem options are obsolete.
> 2) -Xjit options are also obsolete.
> 3) Do we really need this page today? AFAIU users expect Harmony VM is
> able
> to run the same apps as RI..
> ?
> 
> On 11/8/06, Pavel Ozhdikhin <[EMAIL PROTECTED]> wrote:
> >
> > Hello all,
> > I've read through the "Getting Started with
> > DRL<
> >
>
http://incubator.apache.org/harmony/subcomponents/drlvm/getting_started.
> html
> > >"
> > document on the Harmony web and found it completely outdated, for
> example:
> >
> >
> >- the term DRL is used instead of DRLVM
> >- eclipse.bat and eclipse.sh are obsolete - we don't need them
> anymore
> >to run Eclipse. It can be started with DRLVM the same way as with
> any
> > other
> >VM.
> >- We don't need to set PATH and LD_LIBRARY_PATH anymore, at least
> on
> >Windows/MSVC
> >- ij was renamed to java
> >
> > We took a big step to unification with other Java VMs and now
> > we don't need anything specific to run Eclipse, for example. After
> > removing
> > all irrelevant info the document would contain only the list of
> > command-line
> > options. I think we can move this list to a separate document (Wiki,
> > Developer's Guide?) and remove the "Getting Started" itself.
> >
> > Any opinions?
> >
> > Thanks,
> > Pavel
> > <
> >
>
http://incubator.apache.org/harmony/subcomponents/drlvm/getting_started.
> html
> > >
> >
> >
> 
> 
> -- 
> Mikhail Fursov
> 

-- 
Egor Pasko

RE: FW: [build] Building on Eclipse - FYI

[Morozova, Nadezhda]

About strange things in the website structure: good catch!

I guess the site is just in the middle of some transition:
dev_eclipse_movie.html and dev_eclipse.html probably should be under
documentation, not under subcomponents/classlib. And build_classlib is
just outdated and should not be there at all. We have the quick helps
instead now + wiki for temporary issues. 

Thank you, 
Nadya Morozova
 

-Original Message-
From: Sian January [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 08, 2006 8:34 PM
To: harmony-dev@incubator.apache.org
Subject: Re: FW: [build] Building on Eclipse - FYI

Hi Sveta,

Yes - I'm happy to take a look at that page.  I was just thinking that
if we
remove the "Am I Eligible?" section we should probably make sure it is
somewhere else.  My proposal is to add it to the "Get Involved" page -
http://incubator.apache.org/harmony/get-involved.html as I think it's
more
relevant there.  What do you think?

I have also noticed that there are two versions of dev_eclipse.html -
one
under documentation and one under subcomponents/classlib.
dev_eclipse_movie.html and build_classlib.html are also duplicated and I
was
just wondering if anyone knows why this is?

Thanks,

Sian



On 07/11/06, Konovalova, Svetlana <[EMAIL PROTECTED]> wrote:
>
>
> Sian,
> Sorry for delay in response.
> >I'd like to help with documentation but I don't want to duplicate any
> work
> >that you are in the middle of, so let me know if there's anything
> specific >I can do...
> Thanks for your desire to help!
> Well, let's work at the page "Developing Apache Harmony Class-library
> Code with Eclipse"
>
[http://incubator.apache.org/harmony/subcomponents/classlibrary/dev_ecli
> pse.html] first, if you do not mind.
> AFAIK the majority of items on the page can equally apply to DRLVM and
> classlib. IMHO would be great to edit the page to remove unnecessary
> focus on classlib, to make the page equally relevant for vm
developers.
> To my mind, the introductory sections should be removed, as they are
> about generalities that do not always relate to the header of the
page.
> Could you please take a close look at the page and create the patch to
> improve the content and to remove all classlib-specific info? You can
> use Harmony-2009 for it. It would be a great impact into development
of
> the site documentation for sure! If you need my help, just let me
know.
> The second idea is to move the page up, not to store it in
> subcomponents/classlib. To make it easily accessible, we can store it
in
> top xdocs folder and link to the page from documentation.html, quick
> helps and other build-development web pages.
> If you do not have any objections, I can create a patch with the
> necessary links.
> What do you think?
>
> Best regards,
> Sveta
>
> -Original Message-
> From: Sian January [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 02, 2006 2:23 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [build] Building on Eclipse - FYI
>
> Hi Sveta,
>
> Thanks for all your work on this.  I think you're right about the
> Eclipse
> information - I think most of it is fairly generic and it would be
good
> to
> have it in the "Project Documentation" section.  I believe the new
> details
> about the ecj jar and the PDE-related settings are classlib-specific
(-
> Dpde.jreProfile=none etc), but that could probably be mentioned in the
> document.
>
> I'd like to help with documentation but I don't want to duplicate any
> work
> that you are in the middle of, so let me know if there's anything
> specific I
> can do, or if you're nearly finished then I can leave this area to you
> and
> get involved in the future.
>
> Regards,
>
> Sian
>
> On 31/10/06, Konovalova, Svetlana <[EMAIL PROTECTED]>
wrote:
> >
> > Sian,
> >
> > Thank you so much for your positive feedback and appreciating the
> page.
> >
> > This page is only related to classlib. But IMHO many of the things
are
> > pretty generic, and with minimal edits can be fit
> > for VM as well. I suggest that we move this doc up to make it more
> > visible and edit it so as to apply to the whole project, rather than
> to
> > classlib only. To my mind, the "Project Documentation" section is a
> good
> > place
> > for this doc
> >
>
[http://incubator.apache.org/harmony/documentation/documentation.html].
> >
> > How about that?
> >
> > As for the "GS with DRLVM" doc, it needs an update, and can be
> abridged
> > to reduce purely eclipse-oriented content. We can remove unnecessary
> > screenshots as well.
> >
> > Feel free to take an active part in updating the doc, if you have
time
> > and desire :)
> >
> > Best regards,
> > Sveta
> >
> > -Original Message-
> > From: Sian January [mailto:[EMAIL PROTECTED]
> > Sent: Monday, October 30, 2006 8:14 PM
> > To: harmony-dev@incubator.apache.org
> > Subject: Re: [build] Building on Eclipse - FYI
> >
> > Hi Sveta,
> >
> > Thanks for doing that - I have had a look through your patch and it
> > looks
> > really good.
> >

RE: [doc][drlvm] The document "Getting started with DRL" is outdated

[Morozova, Nadezhda]

All,
I'd like to share everyone's grief at the sight of outdated Getting
Started document. However, I'd not hurry to eliminate the page as such.
We might reconsider some of its contents, change structure, and update
individual bits, but please think carefully before removing the page.

I think Getting Started (as the title shows) is aimed to help a newbie
work with our vm. I know that many primarily interested in other things
- conformance, architecture, internal specifics. However, we should also
think how the vm is used. AFAIK, Getting started is now the *only* doc
that tries to show how to use our vm. You tell people how to download
and build, but almost nothing about how to run and configure (with the
exception of EM/JIT). 

My suggestion would be to think of what you want to tell people about
usage - with or without eclipse specifics. And store this info on the
page. I know it is hard - and I offer my help and support in this
burdensome initiative. Any thoughts? i might be inobjective and
emotional :)

Thank you, 
Nadya Morozova
 
-Original Message-
From: Mikhail Fursov [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 08, 2006 6:03 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc][drlvm] The document "Getting started with DRL" is
outdated

It's not a hard to write a documenation once, it's hard to support it :)
More problems:
1) -Xem options are obsolete.
2) -Xjit options are also obsolete.
3) Do we really need this page today? AFAIU users expect Harmony VM is
able
to run the same apps as RI..
?

On 11/8/06, Pavel Ozhdikhin <[EMAIL PROTECTED]> wrote:
>
> Hello all,
> I've read through the "Getting Started with
> DRL<
>
http://incubator.apache.org/harmony/subcomponents/drlvm/getting_started.
html
> >"
> document on the Harmony web and found it completely outdated, for
example:
>
>
>- the term DRL is used instead of DRLVM
>- eclipse.bat and eclipse.sh are obsolete - we don't need them
anymore
>to run Eclipse. It can be started with DRLVM the same way as with
any
> other
>VM.
>- We don't need to set PATH and LD_LIBRARY_PATH anymore, at least
on
>Windows/MSVC
>- ij was renamed to java
>
> We took a big step to unification with other Java VMs and now
> we don't need anything specific to run Eclipse, for example. After
> removing
> all irrelevant info the document would contain only the list of
> command-line
> options. I think we can move this list to a separate document (Wiki,
> Developer's Guide?) and remove the "Getting Started" itself.
>
> Any opinions?
>
> Thanks,
> Pavel
> <
>
http://incubator.apache.org/harmony/subcomponents/drlvm/getting_started.
html
> >
>
>


-- 
Mikhail Fursov

RE: [jira] Good issue resolution guideline (was: [classlib]volunteer to supply patches for old JIRAs)

[Morozova, Nadezhda]

Good! Go ahead. Do you need help? I can review the patch - just let me
know when you submit the JIRA.

Thank you, 
Nadya Morozova
 
-Original Message-
From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 08, 2006 9:13 AM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)

Nadya wrote:
>Candidates:
>http://incubator.apache.org/harmony/guidelines.html 
>http://incubator.apache.org/harmony/get-involved.html
+1

>it's not quite convenient for me just now to add patches, so if someone
>volunteers to help, I'd be grateful.
If you do not mind, I can create the necessary patches.

Best regards,
Sveta Konovalova

-Original Message-
From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 07, 2006 8:24 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)

Well, 
I guess the simplest solution would be to add the link to the
Conventions section on the front page of wiki. You can do it yourself!
Adding a link from the static website would also be useful. Candidates:
http://incubator.apache.org/harmony/guidelines.html 
http://incubator.apache.org/harmony/get-involved.html 

it's not quite convenient for me just now to add patches, so if someone
volunteers to help, I'd be grateful.

Thank you, 
Nadya Morozova
 

-Original Message-
From: Alexey Petrenko [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 07, 2006 4:44 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)

Nadya,

we definetly need a link to this page. That's not a question.
Question is where to place the link.
And as I said in previous email link place suggestions are welcome.

SY, Alexey

2006/11/7, Morozova, Nadezhda <[EMAIL PROTECTED]>:
> Alexey,
> Would be great if there we some page that had a link to the page;
> otherwise, you cannot find it from within wiki, only from the link in
> your mail :(
>
> Thank you,
> Nadya Morozova
>
>
> -Original Message-
> From: Alexey Petrenko [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 07, 2006 1:32 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [jira] Good issue resolution guideline (was:
> [classlib]volunteer to supply patches for old JIRAs)
>
> I've published "Good issue resolution guideline" on Harmony site:
> http://incubator.apache.org/harmony/issue_resolution_guideline.html
> (wait for a while for the web site synchronization). It is not linked
> to other pages yet.
>
> So comments to guideline and link place suggestions are welcome.
>
> SY, Alexey
>
> 2006/9/28, Geir Magnusson Jr. <[EMAIL PROTECTED]>:
> >
> > On Sep 28, 2006, at 3:21 AM, Alexey Petrenko wrote:
> >
> > > Guys,
> > >
> > > Since there is no additional comments on this guideline...
> > >
> > > Let's put it somewhere.
> > > We got two options: Harmony site and wiki.
> > > I prefer wiki because it will be easy to edit it and I can put it
> > > there myself :)
> >
> > And if you put in a patch for website, we can get it there too :)
if
> > you put in wiki, I'm going to take and put on site, so maybe save us
> > some effort? (ok, save me the effort...)
> >
> > geir
> >
> > >
> > > Thoughts?
> > >
> > > SY, Alexey
> > >
> > > 2006/9/26, Alexey Petrenko <[EMAIL PROTECTED]>:
> > >> I've combined all the comments again.
> > >>
> > >> And here is the last version. I hope... :)
> > >>
> > >> === cut ===
> > >> Preface
> > >> This guideline covers a wide range of issues but not all of them.
> > >> If you cannot do one of the steps, then write a comment to the
> issue.
> > >> Use your common sense!
> > >>
> > >> Issue reporter:
> > >> 1. Explicitly state the expected behavior and the
> > >> actual behavior of Harmony code. Use links to specs, rfcs, etc.
> > >> 2. Try to create as small a test case as possible. A patch
> > >> to test will be highly appreciated.
> > >> 3. Provide max. information about steps necessary to recreate the
> > >> bug.
> > >> If a patch for the test has not been supplied, provide as much
> > >> diagnostic information about the failure as possible (stack
trace,
> > >> failure output, expected output etc).
> > >> 4. Remember to use issue links if applicable.

RE: [jira] Good issue resolution guideline (was: [classlib]volunteer to supply patches for old JIRAs)

[Morozova, Nadezhda]

Well, 
I guess the simplest solution would be to add the link to the
Conventions section on the front page of wiki. You can do it yourself!
Adding a link from the static website would also be useful. Candidates:
http://incubator.apache.org/harmony/guidelines.html 
http://incubator.apache.org/harmony/get-involved.html 

it's not quite convenient for me just now to add patches, so if someone
volunteers to help, I'd be grateful.

Thank you, 
Nadya Morozova
 

-Original Message-
From: Alexey Petrenko [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 07, 2006 4:44 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)

Nadya,

we definetly need a link to this page. That's not a question.
Question is where to place the link.
And as I said in previous email link place suggestions are welcome.

SY, Alexey

2006/11/7, Morozova, Nadezhda <[EMAIL PROTECTED]>:
> Alexey,
> Would be great if there we some page that had a link to the page;
> otherwise, you cannot find it from within wiki, only from the link in
> your mail :(
>
> Thank you,
> Nadya Morozova
>
>
> -Original Message-
> From: Alexey Petrenko [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 07, 2006 1:32 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [jira] Good issue resolution guideline (was:
> [classlib]volunteer to supply patches for old JIRAs)
>
> I've published "Good issue resolution guideline" on Harmony site:
> http://incubator.apache.org/harmony/issue_resolution_guideline.html
> (wait for a while for the web site synchronization). It is not linked
> to other pages yet.
>
> So comments to guideline and link place suggestions are welcome.
>
> SY, Alexey
>
> 2006/9/28, Geir Magnusson Jr. <[EMAIL PROTECTED]>:
> >
> > On Sep 28, 2006, at 3:21 AM, Alexey Petrenko wrote:
> >
> > > Guys,
> > >
> > > Since there is no additional comments on this guideline...
> > >
> > > Let's put it somewhere.
> > > We got two options: Harmony site and wiki.
> > > I prefer wiki because it will be easy to edit it and I can put it
> > > there myself :)
> >
> > And if you put in a patch for website, we can get it there too :)
if
> > you put in wiki, I'm going to take and put on site, so maybe save us
> > some effort? (ok, save me the effort...)
> >
> > geir
> >
> > >
> > > Thoughts?
> > >
> > > SY, Alexey
> > >
> > > 2006/9/26, Alexey Petrenko <[EMAIL PROTECTED]>:
> > >> I've combined all the comments again.
> > >>
> > >> And here is the last version. I hope... :)
> > >>
> > >> === cut ===
> > >> Preface
> > >> This guideline covers a wide range of issues but not all of them.
> > >> If you cannot do one of the steps, then write a comment to the
> issue.
> > >> Use your common sense!
> > >>
> > >> Issue reporter:
> > >> 1. Explicitly state the expected behavior and the
> > >> actual behavior of Harmony code. Use links to specs, rfcs, etc.
> > >> 2. Try to create as small a test case as possible. A patch
> > >> to test will be highly appreciated.
> > >> 3. Provide max. information about steps necessary to recreate the
> > >> bug.
> > >> If a patch for the test has not been supplied, provide as much
> > >> diagnostic information about the failure as possible (stack
trace,
> > >> failure output, expected output etc).
> > >> 4. Remember to use issue links if applicable.
> > >> 5. Check the issue resolution when it is committed. Add a
comment.
> > >>
> > >> Resolution provider :) :
> > >> Depending on the type of issue, do the following:
> > >>
> > >> 1. Issue is probably a non-bug difference, not a bug or invalid:
> > >>   1.1. Discuss on the dev list.
> > >>   1.2. Add a link to the discussion thread as a comment to issue.
> > >> 2. Issue is a bug:
> > >>   2.1. Notify the community that you started investigation by
> adding
> > >> a comment to the issue and send a message to dev list. If you
> cannot
> > >> produce a patch, add another comment with the results of your
> > >> investigation.
> > >>   2.2. If reporter did not provide a patch to test:
> > >>   2.2.1. Try to create a patch to test.
> > >>   2.2.2. If you cannot produce a patch, write a comment about
> it.
> > &g

RE: [doc] What should be improved in DRLVM Doxygen documentation?

[Morozova, Nadezhda]

Mikhail,
Do you think it is part of 'culture' to update a comment when changing
behavior of its function? Otherwise, you can erase all comments
altogether since you don't guarantee they're up-to-date :) 

Thank you, 
Nadya Morozova
 
-Original Message-
From: Mikhail Fursov [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 07, 2006 4:30 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] What should be improved in DRLVM Doxygen
documentation?

On 07 Nov 2006 19:08:35 +0600, Egor Pasko <[EMAIL PROTECTED]> wrote:
>
>
> > Another problem: anyone who changes a document behaviour must update
> > comments too :(
>
> excuse me, what is "document behaviour"? :)
>

Read it as 'method/function behaviour'.  I mean if you have good
comments in
file you can't submit a patch with code refactoring without update in
comments. Does it become a new requirement?

IMO we should start to collect metrics and add comments for
intercomponent
interfaces only (vm/include/*).


-- 
Mikhail Fursov

RE: Re: [doc] What should be improved in DRLVM Doxygen documentation?

[Morozova, Nadezhda]

+1.
Doxygen has a @todo tag that we can use.
Quote from manual:
\todo { paragraph describing what is to be done }
Starts a paragraph where a TODO item is described. The description will
also add an item to a separate TODO list. The two instances of the
description will be cross-referenced. Each item in the TODO list will be
preceded by a header that indicates the origin of the item.



Thank you, 
Nadya Morozova
 
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
Sent: Tuesday, November 07, 2006 4:09 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] What should be improved in DRLVM Doxygen
documentation?

On the 0x21A day of Apache Harmony Mikhail Fursov wrote:
> On 11/7/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
> >
> > +1
> >
> > "For in much wisdom is much grief: and he that increaseth knowledge
> increaseth sorrow"
> 
> I'm also +1 to document all of our sources. But it's not always
possible to
> write a meaningful comment  without a lot of "TODO", "this is a
workaround",
> "due to historical reasons" or "I do not remember why this way is the
best"
> comments :).

so, there should be a special dictionary for "TODO", "workaround",
etc. Found a bad word, decrease the doc quality.

Seriously, we do not need to fight for numbers. But quick quality
estimations would help us to make the next step in Doxygen docs, IMHO.

> Another problem: anyone who changes a document behaviour must update
> comments too :(

excuse me, what is "document behaviour"? :)

-- 
Egor Pasko

RE: Re: [doc] What should be improved in DRLVM Doxygen documentation?

[Morozova, Nadezhda]

+1

Thank you, 
Nadya Morozova
 

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
Sent: Tuesday, November 07, 2006 11:23 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] What should be improved in DRLVM Doxygen
documentation?

On the 0x216 day of Apache Harmony Alexei A. Fedotov wrote:
> Nadya wrote,
> > we could check for required Doxygen tags in certain elements.
> 
> I wasn't asked, but cannot resist, sorry. You may achieve this right
now
> without additional coding. Doxygen warns about many problems you
> describe, when you have the following option set.
> 
> # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate
> warnings
> # for undocumented members. If EXTRACT_ALL is set to YES then this
flag
> will
> # automatically be disabled.
> WARN_IF_UNDOCUMENTED   = YES
> 
> The resulting log consists of warning messages about different
problems.
> My DoxygenDrlvmLog.txt, for example, contains the following one:
> 
>
drlvm/trunk/vm/MMTk/ext/vm/HarmonyDRLVM/org/apache/HarmonyDRLVM/mm/mmtk/
> Scanning.java:47: Warning: The following parameters of
>
org::apache::HarmonyDRLVM::mm::mmtk::Scanning::precopyChildren(TraceLoca
> l trace, ObjectReference object) are not documented:
>   parameter trace

does it make sense to convert warnings to quality metrics and put on
harmonytest.org (or even Wiki) regularly? It should encourage people
(like me) to document sources better. Or it is too much effort?

> With best regards,
> Alexei Fedotov,
> Intel Java & XML Engineering
> 
> >-Original Message-
> >From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED]
> >Sent: Friday, November 03, 2006 6:26 PM
> >To: harmony-dev@incubator.apache.org
> >Subject: RE: Re: [doc] What should be improved in DRLVM Doxygen
> >documentation?
> >
> >Egor,
> >I agree with you on the idea of simplicity: documented vs.
> >non-documented.
> >An additional point: do you think we need/want to evaluate quality of
> >comments? we could check for required Doxygen tags in certain
elements.
> >For example, a function is almost certain to include @param and
> @return.
> >Surely, this is heuristics and does not solve all our problems. But
the
> >Doxygen quality check sometimes shows that the file does have
comments,
> >but they are not processed properly by Doxygen - which results in a
low
> >rating for an html file. Maybe this is a crazy idea - I'd be glad to
> >know your opinion.
> >
> >Thank you,
> >Nadya Morozova
> >
> >
> >-Original Message-
> >From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
> >Sent: Friday, November 03, 2006 12:18 PM
> >To: harmony-dev@incubator.apache.org
> >Subject: Re: [doc] What should be improved in DRLVM Doxygen
> >documentation?
> >
> >On the 0x216 day of Apache Harmony Alexei Fedotov wrote:
> >> Egor,
> >>
> >> Thank you for your interest.
> >
> >We definitely need to improve our documentation. Necessity is not a
> >real interest :)
> >
> >> Here is an algorithm:
> >>
> >> 1. Create a list of words from HTML files.
> >> 2. Merge a dictionary of all words used in documentation.
> >> 3. Remove a half of the most frequently used words from the
> dictionary
> >> - I believe they do not add much sense.
> >> 4. Remove misspelled words (including identifiers) from the
> >dictionary.
> >> 5. Give a page +1 for each rare, correctly spelled word according
to
> >> the dictionary.
> >> 6. Divide to the total number of words on the page.
> >
> >hm, strange heuristic. More unique correctly spelled words is
> >beneficial. It does not give a clue on the overall quality of
> >documentation, which is rather confusing..
> >
> >I thought of something more natural. Number of documented items
> >vs. number of non-documented. Plus a penalty to the relative number
of
> >misspelled words.
> >
> >> I've collected nice RFEs from your letter. Most of them make me
think
> >> and I like them.
> >> a. Update an ASF block comment
> >> b. Improve readability. Some things are really easy - like removing
> >> awk and rewriting most things in perl. Others are a bit more
complex
> -
> >> I targeted script performance when created auto-generated perl
> script.
> >> Also, initial algorithm was a bit more complex - different words
had
> a
> >> different cost based on their popularity.
> >> c. Use junit test output format to integrate with
> >> http://harmonytest.org. I believe I need a feature re

RE: [jira] Good issue resolution guideline (was: [classlib]volunteer to supply patches for old JIRAs)

[Morozova, Nadezhda]

Alexey,
Would be great if there we some page that had a link to the page;
otherwise, you cannot find it from within wiki, only from the link in
your mail :(

Thank you, 
Nadya Morozova
 

-Original Message-
From: Alexey Petrenko [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 07, 2006 1:32 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)

I've published "Good issue resolution guideline" on Harmony site:
http://incubator.apache.org/harmony/issue_resolution_guideline.html
(wait for a while for the web site synchronization). It is not linked
to other pages yet.

So comments to guideline and link place suggestions are welcome.

SY, Alexey

2006/9/28, Geir Magnusson Jr. <[EMAIL PROTECTED]>:
>
> On Sep 28, 2006, at 3:21 AM, Alexey Petrenko wrote:
>
> > Guys,
> >
> > Since there is no additional comments on this guideline...
> >
> > Let's put it somewhere.
> > We got two options: Harmony site and wiki.
> > I prefer wiki because it will be easy to edit it and I can put it
> > there myself :)
>
> And if you put in a patch for website, we can get it there too :)  if
> you put in wiki, I'm going to take and put on site, so maybe save us
> some effort? (ok, save me the effort...)
>
> geir
>
> >
> > Thoughts?
> >
> > SY, Alexey
> >
> > 2006/9/26, Alexey Petrenko <[EMAIL PROTECTED]>:
> >> I've combined all the comments again.
> >>
> >> And here is the last version. I hope... :)
> >>
> >> === cut ===
> >> Preface
> >> This guideline covers a wide range of issues but not all of them.
> >> If you cannot do one of the steps, then write a comment to the
issue.
> >> Use your common sense!
> >>
> >> Issue reporter:
> >> 1. Explicitly state the expected behavior and the
> >> actual behavior of Harmony code. Use links to specs, rfcs, etc.
> >> 2. Try to create as small a test case as possible. A patch
> >> to test will be highly appreciated.
> >> 3. Provide max. information about steps necessary to recreate the
> >> bug.
> >> If a patch for the test has not been supplied, provide as much
> >> diagnostic information about the failure as possible (stack trace,
> >> failure output, expected output etc).
> >> 4. Remember to use issue links if applicable.
> >> 5. Check the issue resolution when it is committed. Add a comment.
> >>
> >> Resolution provider :) :
> >> Depending on the type of issue, do the following:
> >>
> >> 1. Issue is probably a non-bug difference, not a bug or invalid:
> >>   1.1. Discuss on the dev list.
> >>   1.2. Add a link to the discussion thread as a comment to issue.
> >> 2. Issue is a bug:
> >>   2.1. Notify the community that you started investigation by
adding
> >> a comment to the issue and send a message to dev list. If you
cannot
> >> produce a patch, add another comment with the results of your
> >> investigation.
> >>   2.2. If reporter did not provide a patch to test:
> >>   2.2.1. Try to create a patch to test.
> >>   2.2.2. If you cannot produce a patch, write a comment about
it.
> >>   2.3. Create a patch to fix the issue
> >>   2.3.1. Any concerns? Discuss on the dev list. Add a link to
> >> discussion as a comment.
> >>   2.4. All the pacthes (test and fix) should be relative to the
> >> directory where the main build.xml is:
> >> https://svn.apache.org/repos/asf/incubator/harmony/enhanced/
> >> classlib/trunk.
> >> Or to the module root directory.
> >>   2.5. Test and fix patches should be in different files.
> >>   2.6. If the patch requires to add, remove or move some files in
the
> >> repository, add the appropriate script.
> >>   2.6. Check that all unit tests pass.
> >>   2.8. If it is an application-oriented issue, check the
application.
> >>   2.9. Remember to use issue links if applicable.
> >>
> >> Committer:
> >> Depending on the issue type, do:
> >> 1. Issue is a non-bug difference, not a bug or invalid:
> >> Close the issue.
> >> 2. Issue is a bug:
> >>   2.1. If a patch to test is available, apply it.
> >>   2.2. Check that the test fails.
> >>   2.3. Apply the fix for the issue.
> >>   2.4. Check that test succeeds now.
> >>   2.5. Make sure that all unit tests pass.
> >>   2.6. For application-oriented issues, check the application.
> >>   2.7. If there are problems on previous steps, post a comment to
> >> JIRA and let "resolution provider" to resolve.
> >>   2.8. Make sure that the issue reporter is happy with the
> >> resolution.
> >>   2.9. Add revision info into JIRA issue
> >> === cut ===
> >>
> >
> >
> > --
> > Alexey A. Petrenko
> > Intel Middleware Products Division
> >
> >
-
> > Terms of use : http://incubator.apache.org/harmony/mailing.html
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail:
[EMAIL PROTECTED]
> >
>
>
> -
> Terms of use : http://incubator.apache.org/harmony/mailing

RE: [doc][drlvm] new docs added - JIT compiler

[Morozova, Nadezhda]

Geir, all,
Could you please find time and look into JIRA 1882 and JIRA 2003. These
contain content updates for the website -  one for the devguide,
removing outdated info, etc; and the other one for JIT - introducing a
more-or-less comprehensive description of this component. Adding these
to the website does not affect structure/ideology of website, but only
adds more info. If somebody volunteers to review, I'd be happy to help
and work to improve the docs further. 

h-2003 http://issues.apache.org/jira/browse/HARMONY-2003 
h-1882 http://issues.apache.org/jira/browse/HARMONY-1882 

Thank you, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 31, 2006 2:18 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc][drlvm] new docs added - JIT compiler

oh, thankyou thankyou thankyou

Morozova, Nadezhda wrote:
> Yeah! No problem, I was just thinking a zip would not look as
> transparent and safe. I'd turn the images from the other doc issue
into
> an archive as well.
> 
> Thank you, 
> Nadya Morozova
>  
> 
> -Original Message-
> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, October 31, 2006 5:20 AM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [doc][drlvm] new docs added - JIT compiler
> 
> is there any chance you could put a zip of the images into the jira, 
> rather than a  dozen or so images?  That's actually what turned me off

> from one of the other doc issues - I said to myself "oh, heck, I don't

> want to download each of those separate thingies... I just want a zip
or
> 
> tgz of them... easier to handle..."
> 
> So please? :)
> 
> geir
> 
> Morozova, Nadezhda wrote:
>> All, 
>>
>> New documents have been added to HARMONY-2003. These are a
description
>> of the Jitrino.OPT and .JET compilers, with a supplementary doc on
the
>> pipeline management framework inside the JITs. The docs describe the
>> architecture, processes and usage of the components.
>>
>>  
>>
>> It would be great if somebody took a look, expressed an opinion, and,
> if
>> favorable, committed to the website.
>>
>> Your review or any other feedback are most welcome,
>>
>>  
>>
>> Thanks, 
>>
>> Nadya Morozova
>>
>>  
>>
>> PS: this JIRA is not the only one unresolved doc issue. Find more
> useful
>> pending patches in our database :-)
>>
>>
> 

RE: Re: [doc] What should be improved in DRLVM Doxygen documentation?

[Morozova, Nadezhda]

Alexei,
I think we're talking about different things here :) I fully support
your idea and I know about the Doxygen config options you have
mentioned. 
I was just curious to know: is there interest to produce/evaluate
produce Doxygen-style comments. 
My case was that, say, a function can have a line of text, we consider
it documented, etc. however, the function comment is only a draft that
does not produce meaningful documentation. A sign of better comment is
@param and/or @return tag included in the function comment. 
Never mind, I think this type of info is not necessary at this stage:)

Thank you, 
Nadya Morozova
 

-Original Message-
From: Fedotov, Alexei A [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 03, 2006 7:36 PM
To: harmony-dev@incubator.apache.org
Subject: RE: Re: [doc] What should be improved in DRLVM Doxygen
documentation?

Nadya wrote,
> we could check for required Doxygen tags in certain elements.

I wasn't asked, but cannot resist, sorry. You may achieve this right now
without additional coding. Doxygen warns about many problems you
describe, when you have the following option set.

# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate
warnings
# for undocumented members. If EXTRACT_ALL is set to YES then this flag
will
# automatically be disabled.
WARN_IF_UNDOCUMENTED   = YES

The resulting log consists of warning messages about different problems.
My DoxygenDrlvmLog.txt, for example, contains the following one:

drlvm/trunk/vm/MMTk/ext/vm/HarmonyDRLVM/org/apache/HarmonyDRLVM/mm/mmtk/
Scanning.java:47: Warning: The following parameters of
org::apache::HarmonyDRLVM::mm::mmtk::Scanning::precopyChildren(TraceLoca
l trace, ObjectReference object) are not documented:
  parameter trace

With best regards,
Alexei Fedotov,
Intel Java & XML Engineering

>-Original Message-----
>From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED]
>Sent: Friday, November 03, 2006 6:26 PM
>To: harmony-dev@incubator.apache.org
>Subject: RE: Re: [doc] What should be improved in DRLVM Doxygen
>documentation?
>
>Egor,
>I agree with you on the idea of simplicity: documented vs.
>non-documented.
>An additional point: do you think we need/want to evaluate quality of
>comments? we could check for required Doxygen tags in certain elements.
>For example, a function is almost certain to include @param and
@return.
>Surely, this is heuristics and does not solve all our problems. But the
>Doxygen quality check sometimes shows that the file does have comments,
>but they are not processed properly by Doxygen - which results in a low
>rating for an html file. Maybe this is a crazy idea - I'd be glad to
>know your opinion.
>
>Thank you,
>Nadya Morozova
>
>
>-Original Message-
>From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
>Sent: Friday, November 03, 2006 12:18 PM
>To: harmony-dev@incubator.apache.org
>Subject: Re: [doc] What should be improved in DRLVM Doxygen
>documentation?
>
>On the 0x216 day of Apache Harmony Alexei Fedotov wrote:
>> Egor,
>>
>> Thank you for your interest.
>
>We definitely need to improve our documentation. Necessity is not a
>real interest :)
>
>> Here is an algorithm:
>>
>> 1. Create a list of words from HTML files.
>> 2. Merge a dictionary of all words used in documentation.
>> 3. Remove a half of the most frequently used words from the
dictionary
>> - I believe they do not add much sense.
>> 4. Remove misspelled words (including identifiers) from the
>dictionary.
>> 5. Give a page +1 for each rare, correctly spelled word according to
>> the dictionary.
>> 6. Divide to the total number of words on the page.
>
>hm, strange heuristic. More unique correctly spelled words is
>beneficial. It does not give a clue on the overall quality of
>documentation, which is rather confusing..
>
>I thought of something more natural. Number of documented items
>vs. number of non-documented. Plus a penalty to the relative number of
>misspelled words.
>
>> I've collected nice RFEs from your letter. Most of them make me think
>> and I like them.
>> a. Update an ASF block comment
>> b. Improve readability. Some things are really easy - like removing
>> awk and rewriting most things in perl. Others are a bit more complex
-
>> I targeted script performance when created auto-generated perl
script.
>> Also, initial algorithm was a bit more complex - different words had
a
>> different cost based on their popularity.
>> c. Use junit test output format to integrate with
>> http://harmonytest.org. I believe I need a feature request for that
>> site as well - we need some way to import performance-like rankings
to
>> the site.
>
>Yes, I thought of the RFE to harmonytest. At le

RE: [doc] What should be improved in DRLVM Doxygen documentation?

[Morozova, Nadezhda]

Recommended well-documented source code (personal preference)
Ongoing development: Class.h - see JIRA-1558 for latest patch 
Done: in vm - StackIterator.h, Verifier.h, vm_gc.h; in jit - jet,
ControlFlowGraph.h; JPDA sources... 

Thank you, 
Nadya Morozova
 

-Original Message-
From: Alexei Fedotov [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 03, 2006 11:27 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] What should be improved in DRLVM Doxygen
documentation?

Egor,

Thank you for your interest. Here is an algorithm:

1. Create a list of words from HTML files.
2. Merge a dictionary of all words used in documentation.
3. Remove a half of the most frequently used words from the dictionary
- I believe they do not add much sense.
4. Remove misspelled words (including identifiers) from the dictionary.
5. Give a page +1 for each rare, correctly spelled word according to
the dictionary.
6. Divide to the total number of words on the page.

I've collected nice RFEs from your letter. Most of them make me think
and I like them.
a. Update an ASF block comment
b. Improve readability. Some things are really easy - like removing
awk and rewriting most things in perl. Others are a bit more complex -
I targeted script performance when created auto-generated perl script.
Also, initial algorithm was a bit more complex - different words had a
different cost based on their popularity.
c. Use junit test output format to integrate with
http://harmonytest.org. I believe I need a feature request for that
site as well - we need some way to import performance-like rankings to
the site.
d. I will think of parsing sources. But I don't think we need to
maintain both scripts. The generic rule is simple - improve your .h
and .java files - .cpp files don't count. I suggest better to link
.html files to contributors.

Thank you for ideas. I will certainly update the script. I just want
to wait a bit - many scripts die just because people are not
interested to run them a second time. Also, if anyone suggest any
changes in algorithm or any other RFEs, I want to implement them all
at once.

Nadya, could you please point us a good documentation file so we can
use it as a pattern?

-- Alexei

RE: [doc] What should be improved in DRLVM Doxygen documentation?

[Morozova, Nadezhda]

Alexei,
Thanks for your answers. A couple of comments below, and a generic
concern: 
I still cannot understand why we should evaluate pages, not code
comments in source files. 

Example: the Wiki page now suggests that we improve the auto-generated
pages: modules.html (list of groups), annotated.html (list of classes),
files.html (list of files), etc. 
Now, these do not map to any specific header(s) - they are
auto-generated by analyzing all headers. For instance, modules.html is
about modules; any module maps to a @devgroup tag in code, and you can
use "@devgroup optional" to separate all optional functions in your
interface. Now, these modules are optional; creating them is not always
needed/good/easy. How exactly can you improve the page that is an
assembly of all modules? I'd say, we can have a recommendation for the
community to group any related functionality - but we cannot improve the
page or oblige authors to use groups :)
The same is for files, structures, etc. You can ask the whole authoring
lot to write definitions of headers using @file; @struct, etc in their
files. However, I don't see a way for 1-2 people volunteering and doing
an improvement to the files.html page, etc.

I guess a more realistic approach would be to measure amount of
documentation in headers. This way, we can have people volunteer to fix
things - like David L. did for bytecode.h! see - my way is working
already :0

Thank you, 
Nadya Morozova
 

-Original Message-
From: Alexei Fedotov [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 03, 2006 1:56 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] What should be improved in DRLVM Doxygen
documentation?

Nadya,

You asked good questions. Here are few answers:

1. Grouping of results is implied by documentation grouping. Scripts
can process any documentation bundle, so if one creates a smaller or
specific bundle, the list will be shorter, or more specific.Creating
several documentation bundles in different directories makes their
comparison an easy task - I can do this comparison.
[NM] yeah, good idea!

2. Personally I like @page tags and package.html files. I appreciate
Salikh's efforts of creating wonderful technical descriptions - I
referred to them as masterpieces. I also remember that you asked me to
create a narrative section for a component manager few months ago. All
Doxygen documentation will be on the web site. Why these narrative
sections shouldn't be evaluated?
[NM] I always say - the more docs the better. If you still feel you can
write a description of component manager, do so. My idea is that the
higher-level conceptual info does not have to be part of Doxygen. You
can write it on the website - with more HTML and XML presentation
opportunities. Doxygen is so tightly bound with code that you don't
really have to fit generics into it. You can place links back and fro
but write the stabler stuff on the website. Surely, @page, @section,
@devgroup, and @file tags are needed sometimes to tie definitions of
methods and classes into interfaces and components. Please don't think
that I am totally against them. I just think we can differentiate :)

3. I don't think the rating of pages such as a list of functions
should be neglected. Any .html page which can be viewed by a user
should be readable. That is a reason why I parse .html files in the
script, not sources.
[NM] I doubt that a really well-documented source can produce a poor
html :) 

4. I believe establishing connection between .html files and source
files can be automated. I don't know how to write a short script for
that, because sometimes .html page depends from several source files,
and vice versa.

5. You can imagine the following pie chart from the data: 2680 pages
of 2922 (91%) are not good and should be revised.
[NM] :(

6.  Today the community discussed removing GC V4. This would
immediately decrease GC documentation size. It would also decrease a
number of well documented pages on garbage collection, since new GCs
don't have as much comments in their code as old GC V4.
[NM] yeah, I read the news :)

Thank you for nice catches,
Alexei



On 11/2/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
> Wow! Alexei, great start!
> ... and so many pages marked with 0 rank. I really appreciate your
> effort - it sets me back on earth and to work. I hope this rating
would
> also make owners of code more ambitious, and would inspire them to
write
> more/better comments to get a better rating :)
>
> Question on output measurement: can we rate source files or code
> elements (structure, functions, etc) instead of html files?
> My concerns:
> - Many html files are autogenerated, their rating is N/A. examples:
> todo.html, functions_vars_0x68.html (listing of links to functions in
> alphabetical order - there are many pages like that)
> - Some results are duplicated, because each struct/function has a

RE: Re: [doc] What should be improved in DRLVM Doxygen documentation?

[Morozova, Nadezhda]

Egor, 
I agree with you on the idea of simplicity: documented vs.
non-documented. 
An additional point: do you think we need/want to evaluate quality of
comments? we could check for required Doxygen tags in certain elements.
For example, a function is almost certain to include @param and @return.
Surely, this is heuristics and does not solve all our problems. But the
Doxygen quality check sometimes shows that the file does have comments,
but they are not processed properly by Doxygen - which results in a low
rating for an html file. Maybe this is a crazy idea - I'd be glad to
know your opinion. 

Thank you, 
Nadya Morozova
 

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
Sent: Friday, November 03, 2006 12:18 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] What should be improved in DRLVM Doxygen
documentation?

On the 0x216 day of Apache Harmony Alexei Fedotov wrote:
> Egor,
> 
> Thank you for your interest. 

We definitely need to improve our documentation. Necessity is not a
real interest :)

> Here is an algorithm:
> 
> 1. Create a list of words from HTML files.
> 2. Merge a dictionary of all words used in documentation.
> 3. Remove a half of the most frequently used words from the dictionary
> - I believe they do not add much sense.
> 4. Remove misspelled words (including identifiers) from the
dictionary.
> 5. Give a page +1 for each rare, correctly spelled word according to
> the dictionary.
> 6. Divide to the total number of words on the page.

hm, strange heuristic. More unique correctly spelled words is
beneficial. It does not give a clue on the overall quality of
documentation, which is rather confusing..

I thought of something more natural. Number of documented items
vs. number of non-documented. Plus a penalty to the relative number of
misspelled words.

> I've collected nice RFEs from your letter. Most of them make me think
> and I like them.
> a. Update an ASF block comment
> b. Improve readability. Some things are really easy - like removing
> awk and rewriting most things in perl. Others are a bit more complex -
> I targeted script performance when created auto-generated perl script.
> Also, initial algorithm was a bit more complex - different words had a
> different cost based on their popularity.
> c. Use junit test output format to integrate with
> http://harmonytest.org. I believe I need a feature request for that
> site as well - we need some way to import performance-like rankings to
> the site.

Yes, I thought of the RFE to harmonytest. At least, put the doc items
on a separate page from the build items.

> d. I will think of parsing sources. But I don't think we need to
> maintain both scripts. The generic rule is simple - improve your .h
> and .java files - .cpp files don't count. I suggest better to link
> .html files to contributors.

can you calculate a list of relevant filenames from a doc page? give
filename +1 for each documented item, give a -1 for each undocumented,
divide on the number of items. Is it easy to implement?  Maybe doxygen
has some features to assist this?

> Thank you for ideas. I will certainly update the script. I just want
> to wait a bit - many scripts die just because people are not
> interested to run them a second time. Also, if anyone suggest any
> changes in algorithm or any other RFEs, I want to implement them all
> at once.
> 
> Nadya, could you please point us a good documentation file so we can
> use it as a pattern?

-- 
Egor Pasko

RE: [doc] What should be improved in DRLVM Doxygen documentation?

[Morozova, Nadezhda]

Great to hear that! Let me know if you need help.

Thank you, 
Nadya Morozova
 

-Original Message-
From: Leviev, Ilia A [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 03, 2006 3:35 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [doc] What should be improved in DRLVM Doxygen
documentation?



Geir Magnusson Jr. wrote:
>Have fun.  :)
>
>But to be clear, you'd be improving the source that makes bytecodes_8h?
>
>geir
>


Yes, I am going to add to bytecode.h some comments and hyperlinks to Sun
docs.

Best regards,
Leviev Ilia


>Leviev, Ilia A wrote:
> Hi,
> I volunteer for improving bytecodes_8h.html in my spare time. 
> Objections?
> 
> Best regards,
> Ilia Leviev
> Intel Java & XML Engineering
> 
> 
> 
> -Original Message-
> From: Fedotov, Alexei A [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, November 02, 2006 11:33 PM
> To: harmony-dev@incubator.apache.org
> Subject: [doc] What should be improved in DRLVM Doxygen documentation?
> 
> Nadya, All,
> I have ranked the quality of Doxygen-generated DRLVM documentation and
> posted it to the following Wiki page: 
> 
> http://wiki.apache.org/harmony/DRLVM_Documentation_Quality
> 
> All are welcome to check masterpieces of our documentation. All
> volunteers are welcome to improve page ranks by editing comments in
> DRLVM sources. 
> 
> With best regards,
> Alexei Fedotov,
> Intel Java & XML Engineering
> 

RE: [doc] What should be improved in DRLVM Doxygen documentation?

[Morozova, Nadezhda]

Wow! Alexei, great start! 
... and so many pages marked with 0 rank. I really appreciate your
effort - it sets me back on earth and to work. I hope this rating would
also make owners of code more ambitious, and would inspire them to write
more/better comments to get a better rating :)

Question on output measurement: can we rate source files or code
elements (structure, functions, etc) instead of html files? 
My concerns:
- Many html files are autogenerated, their rating is N/A. examples:
todo.html, functions_vars_0x68.html (listing of links to functions in
alphabetical order - there are many pages like that)
- Some results are duplicated, because each struct/function has an
individual rating + rating of the file/group reference it belongs to. 
- Some files have a high rating (see the top candidate, for example),
but it's generated from comments marked with @page. These don't belong
to specific code, but create a narrative section. Evaluating these is
complex, and perhaps, should not be done. My personal preference would
be to move such generic explanations to component docs on the website
and reserve Doxygen docs to API reference as much as possible (this is a
subject for further discussion).
- the listing of files is SO LONG... grouping them by
file/component/type or otherwise organizing the output would make the
whole rating more readable. I mean, from the current version, I can only
make out the leaders (not files even, individual bits of them), and
understand that the majority have 0 rating. This has its instructional
impact, but I cannot see the areas where we are the best - bearable -
worst, or see the approx distribution of powers... missing that info
leaves me without direction on what to do.

Question on data presentation: do you think we can have some post
processing of the raw data that your script produces - to see the big
picture? We have some metrics: graphics, pie charts, anything. This
would instantly show the most important conclusions. I could do such
metrics and post them regularly on Wiki. If anybody says they need such
kind of info, I'd volunteer to help. 

Thank you, 
Nadya Morozova
 

-Original Message-
From: Fedotov, Alexei A [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 02, 2006 11:33 PM
To: harmony-dev@incubator.apache.org
Subject: [doc] What should be improved in DRLVM Doxygen documentation?

Nadya, All,
I have ranked the quality of Doxygen-generated DRLVM documentation and
posted it to the following Wiki page: 

http://wiki.apache.org/harmony/DRLVM_Documentation_Quality

All are welcome to check masterpieces of our documentation. All
volunteers are welcome to improve page ranks by editing comments in
DRLVM sources. 

With best regards,
Alexei Fedotov,
Intel Java & XML Engineering

RE: [classlib][portlib] Docs?

[Morozova, Nadezhda]

My two cents and food for programmer's thought:

1. Doxygen can get the version from a versioning system. Quote from
manual:
The FILE_VERSION_FILTER tag can be used to specify a program or script
that doxygen should invoke to get the current version for each file
(typically from the version control system). Doxygen will invoke the
program by executing (via popen()) the command command input-file, where
command is the value of the FILE_VERSION_FILTER tag, and input-file is
the name of an input file provided by doxygen. Whatever the program
writes to standard output is used as the file version.
Example of using a shell script as a filter for Unix: 

 FILE_VERSION_FILTER = "/bin/sh versionfilter.sh"

Example shell script for Subversion: 

#!/bin/sh
svn stat -v $1 | sed -n 's/^[ A-Z?\*|!]\{1,15\}/r/;s/ \{1,15\}/\/r/;s/
.*//p'

2. Doxygen can process a custom header/footer to display the info you
need. Quote from manual:
HTML_FOOTER 
The HTML_FOOTER tag can be used to specify a user-defined HTML footer
for each generated HTML page. To get valid HTML the footer file should
contain at least a  and a  tag. The following commands
have a special meaning inside the footer: $title, $datetime, $date,
$doxygenversion, $projectname, $projectnumber. Doxygen will replace them
by respectively the title of the page, the current date and time, only
the current date, the version number of doxygen, the project name (see
PROJECT_NAME), or the project number (see PROJECT_NUMBER).


Thank you, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 02, 2006 4:59 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib][portlib] Docs?



Paulex Yang wrote:
> Geir Magnusson Jr. wrote:
>>
>>
>> Paulex Yang wrote:
>>> Geir Magnusson Jr. wrote:
>>>> yeah - someone generate, and we can hang them on the website.  I'm 
>>>> not sure we'd want to check them in though...
>>> Is it possible to add documents into website but not to commit them 
>>> in SVN?
>>
>> Yep.  I was thinking the same for the Doxygen docs.
>>
>> Basically, you just create locally, review, and then tar and put up
on 
>> site manually.
> +1 to go for that
>>
>> It does remove the ability for group oversight (IOW, no commit msgs),

>> but if the generation process isn't very stale (small changes to one 
>> page have repercussions all over...) then it keeps the SVN churn to a

>> minimum.
> Actually I have no idea what kind of commit msgs needed for API 
> document...they are just generated by tools from codes. I think the
most 
> important information is the svn revision number against which the 
> document is generated, any doxygen guru can help to find a way? Any 
> chance to pass a revision number to doxygen and to get it added into 
> footer of every page?

That's a very smart idea.  +1

geir

>>
>> geir
>>
>>
>>  We removed them from classlib/trunk/doc because the SVN metadata
>>> get in the way when updating the document.
>>>>
>>>> I've done this before for API docs...
>>>>
>>>> geir
>>>>
>>>>
>>>> Alexey Petrenko wrote:
>>>>> Having these docs on website will be really good!
>>>>>
>>>>> SY, Alexey
>>>>>
>>>>> 2006/11/1, Paulex Yang <[EMAIL PROTECTED]>:
>>>>>> If you get Doxygen installed, you can create it by running "ant
>>>>>> doxygen-natives" in classlib/trunk/doc. There were discussions to

>>>>>> move
>>>>>> the document to somewhere on website, but seems it is still to be

>>>>>> done.
>>>>>>
>>>>>> Morozova, Nadezhda wrote:
>>>>>> > Not that I know of :( bits of things are in the devguide,
maybe. 
>>>>>> But you
>>>>>> > probably won't find that of much notice.
>>>>>> > Anyone, please tell me it's not true!
>>>>>> >
>>>>>> > Thank you,
>>>>>> > Nadya Morozova
>>>>>> >
>>>>>> >
>>>>>> > -Original Message-
>>>>>> > From: Alexey Petrenko [mailto:[EMAIL PROTECTED]
>>>>>> > Sent: Wednesday, November 01, 2006 4:15 PM
>>>>>> > To: harmony-dev@incubator.apache.org
>>>>>> > Subject: [classlib][portlib] Docs?
>>>>>> >
>>>>>> > Guys,
>>>>>> >
>>>>>> > do we have any docs on portlib?
>>>>>> >
>>>>>> > SY, Alexey
>>>>>> >
>>>>>> >
>>>>>>
>>>>>>
>>>>>> -- 
>>>>>> Paulex Yang
>>>>>> China Software Development Lab
>>>>>> IBM
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>
> 
> 

RE: [doc]Please help to remove outdated info from the site

[Morozova, Nadezhda]

I was hoping to. Just wanted to see people's discussion before creating
a patch. Otherwise, there's just somebody doing docs and not much
response/agreement on whether the docs are good/correct ;) 

Thank you, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 02, 2006 2:21 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc]Please help to remove outdated info from the site

Nice - buy why not put the tasks in JIRA?

Morozova, Nadezhda wrote:
> Thanks all who helped with the "what can we do now" page - the new
page is shorter but none the less useful. 
> My suggestion is to add more links to the page. It now only links to
the applist. More candidates: classlib status page [1], wiki drlvm todo
items [2], website & doc development [3]. What do you think?
> 
> [1]
http://incubator.apache.org/harmony/subcomponents/classlibrary/status.ht
ml 
> [2] http://wiki.apache.org/harmony/TODO_List_for_DRLVM 
> [3] http://wiki.apache.org/harmony/Documentation_TODO 
> 
> Thank you, 
> Nadya Morozova
>  
> 
> -Original Message-
> From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, November 01, 2006 5:31 PM
> To: harmony-dev@incubator.apache.org
> Subject: [doc]Please help to remove outdated info from the site 
> 
> Folks,
> 
> You might know that certain Harmony pages are out-of-date and need to
be modified. 
> One of such pages is http://incubator.apache.org/harmony/status.html .
> Now I'm working at creating the "Build our Own Website Using Ant"
section for this very page.
> Would be great, if someone can find a chance to look at it to help me
through away outdated info.
> 
> Thanks in advance!
> 
> Best regards,
> Sveta Konovalova
>  
>  
> 

RE: [drlvm] more self-dependent VM tasks, newbies welcome

[Morozova, Nadezhda]

Great to hear that! I'll go take a look and fix any grammar/nice
formatting in a while.

Thank you, 
Nadya Morozova
 

-Original Message-
From: Alexey Varlamov [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 02, 2006 1:26 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [drlvm] more self-dependent VM tasks, newbies welcome

Nadya,

Thanks for the links, I added new subpage to TODO_List_for_DRLVM.

2006/11/2, Morozova, Nadezhda <[EMAIL PROTECTED]>:
> Alexey,
> Do you think you can post these on Wiki? We actually have several
pages
> there that can help arrange and store such development items:
> Starting point, choose your subpage
> http://wiki.apache.org/harmony/TODO_List_for_DRLVM
> Sample http://wiki.apache.org/harmony/JIT_Development_Tasks
> Wiki seems easier to find and use than an email thread on the list.
What
> do you say?
> Do you need my help with this?
>
> Thank you,
> Nadya Morozova
>
>
> -Original Message-
> From: Alexey Varlamov [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 02, 2006 9:24 AM
> To: harmony-dev
> Subject: [drlvm] more self-dependent VM tasks, newbies welcome
>
> Below is a list of isolated development tasks which do not require
> advanced knowledge of VM and could be a nice start for newbies to get
> acquainted with the code. All items are targeted for better code
> sharing.
>
> 1) Eliminate duplicate implementation of j.l.Runtime.Process in kernel
> classes of DRLVM [1]. The classlib provides neat portlib-based
> reference implementation [2], which should be reused. These 2 impls
> are roughly identical, so one needs to made more scrupulous comparison
> and squeeze some features/fixes of [1] which may be missing in [2],
> then employ [2] in j.l.Runtime of DRLVM and drop [1].
>
> 2) Improve/re-implement a parser of generic signatures in DRLVM kernel
> classes [3], and move this functionality to classlib (luni ?), so
> other VMs could reuse it for 1.5 support. The current impl is somewhat
> messy and half-baked, one need to invent more shaped and modular API
> to the parser. One more possible issue is parser's dependency on
> antlr, which may be considered overkill for this duty. I think antlr
> has its pros, like more illustrative code with clear correlation to
> formal grammar [4]; unfortunately this is not the case with the impl
> in question. OTOH minimizing number of dependencies for VM is always
> good.
>
> 3) Classlib's j.u.TimeZone expects "user.timezone" property value
> initialized during VM startup (BTW I did not find explicit statement
> in VMI docs for that, only indirect reference in kernel stub for
> j.l.System). I believe this action should be done by hyluni natives
> during JNI_OnLoad, no reason to burden VM with it. Therefore I suggest
> to move "port_user_timezone()" function [5] from DRLVM to classlib
> (luni/port), and fix DRLVM & hyluni accordingly.
>
> [1]
> working_vm\vm\vmcore\src\kernel_classes\javasrc\java\lang\Runtime.java
> + working_vm\vm\vmcore\src\kernel_classes\native\Runtime_[lnx|win].cpp
> [2]
>
working_classlib\modules\luni\src\main\java\org\apache\harmony\luni\inte
> rnal\process\*
> + working_classlib\modules\luni\src\main\native\luni\shared\process.c
> [3]
>
working_vm\vm\vmcore\src\kernel_classes\javasrc\org\apache\harmony\lang\
> reflect\**
> [4]
>
http://java.sun.com/docs/books/vmspec/2nd-edition/ClassFileFormat-Java5.
> pdf
> Para 4.4.4
> [5] working_vm\vm\port\src\misc\[win|linux]\timezone.c
>
> Comments? Should I put this somewhere on the Wiki?
>

RE: [doc]Please help to remove outdated info from the site

[Morozova, Nadezhda]

Thanks all who helped with the "what can we do now" page - the new page is 
shorter but none the less useful. 
My suggestion is to add more links to the page. It now only links to the 
applist. More candidates: classlib status page [1], wiki drlvm todo items [2], 
website & doc development [3]. What do you think?

[1] http://incubator.apache.org/harmony/subcomponents/classlibrary/status.html 
[2] http://wiki.apache.org/harmony/TODO_List_for_DRLVM 
[3] http://wiki.apache.org/harmony/Documentation_TODO 

Thank you, 
Nadya Morozova
 

-Original Message-
From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 01, 2006 5:31 PM
To: harmony-dev@incubator.apache.org
Subject: [doc]Please help to remove outdated info from the site 

Folks,

You might know that certain Harmony pages are out-of-date and need to be 
modified. 
One of such pages is http://incubator.apache.org/harmony/status.html .
Now I'm working at creating the "Build our Own Website Using Ant" section for 
this very page.
Would be great, if someone can find a chance to look at it to help me through 
away outdated info.

Thanks in advance!

Best regards,
Sveta Konovalova
 
 

RE: [drlvm] more self-dependent VM tasks, newbies welcome

[Morozova, Nadezhda]

Alexey,
Do you think you can post these on Wiki? We actually have several pages
there that can help arrange and store such development items:
Starting point, choose your subpage
http://wiki.apache.org/harmony/TODO_List_for_DRLVM 
Sample http://wiki.apache.org/harmony/JIT_Development_Tasks 
Wiki seems easier to find and use than an email thread on the list. What
do you say?
Do you need my help with this?

Thank you, 
Nadya Morozova
 

-Original Message-
From: Alexey Varlamov [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 02, 2006 9:24 AM
To: harmony-dev
Subject: [drlvm] more self-dependent VM tasks, newbies welcome

Below is a list of isolated development tasks which do not require
advanced knowledge of VM and could be a nice start for newbies to get
acquainted with the code. All items are targeted for better code
sharing.

1) Eliminate duplicate implementation of j.l.Runtime.Process in kernel
classes of DRLVM [1]. The classlib provides neat portlib-based
reference implementation [2], which should be reused. These 2 impls
are roughly identical, so one needs to made more scrupulous comparison
and squeeze some features/fixes of [1] which may be missing in [2],
then employ [2] in j.l.Runtime of DRLVM and drop [1].

2) Improve/re-implement a parser of generic signatures in DRLVM kernel
classes [3], and move this functionality to classlib (luni ?), so
other VMs could reuse it for 1.5 support. The current impl is somewhat
messy and half-baked, one need to invent more shaped and modular API
to the parser. One more possible issue is parser's dependency on
antlr, which may be considered overkill for this duty. I think antlr
has its pros, like more illustrative code with clear correlation to
formal grammar [4]; unfortunately this is not the case with the impl
in question. OTOH minimizing number of dependencies for VM is always
good.

3) Classlib's j.u.TimeZone expects "user.timezone" property value
initialized during VM startup (BTW I did not find explicit statement
in VMI docs for that, only indirect reference in kernel stub for
j.l.System). I believe this action should be done by hyluni natives
during JNI_OnLoad, no reason to burden VM with it. Therefore I suggest
to move "port_user_timezone()" function [5] from DRLVM to classlib
(luni/port), and fix DRLVM & hyluni accordingly.

[1]
working_vm\vm\vmcore\src\kernel_classes\javasrc\java\lang\Runtime.java
+ working_vm\vm\vmcore\src\kernel_classes\native\Runtime_[lnx|win].cpp
[2]
working_classlib\modules\luni\src\main\java\org\apache\harmony\luni\inte
rnal\process\*
+ working_classlib\modules\luni\src\main\native\luni\shared\process.c
[3]
working_vm\vm\vmcore\src\kernel_classes\javasrc\org\apache\harmony\lang\
reflect\**
[4]
http://java.sun.com/docs/books/vmspec/2nd-edition/ClassFileFormat-Java5.
pdf
Para 4.4.4
[5] working_vm\vm\port\src\misc\[win|linux]\timezone.c

Comments? Should I put this somewhere on the Wiki?

RE: [doc] No Doxygen reference for code :(

[Morozova, Nadezhda]

+1

Thank you, 
Nadya Morozova
 

-Original Message-
From: Paulex Yang [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 01, 2006 7:55 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] No Doxygen reference for code :(

Alexey Petrenko wrote:
> I think that we can place the docs here:
>
http://incubator.apache.org/harmony/subcomponents/classlibrary/index.htm
l
Yes, that's one of my candidate, another one is here: 
standard/site/docs/documentation/documentation.html, because I think it 
is also a reasonable idea for the user to go for "documentation" if you 
wanna some API explanation. How about we put the API document in each 
subcomponents(classlib/drlvm/jchevm), but also add their link in 
documentation/documentation.html?
>
> 2006/11/1, Paulex Yang <[EMAIL PROTECTED]>:
>> Morozova, Nadezhda wrote:
>> > Hi everyone,
>> >
>> > I've noticed that there's no API reference documentation for
Harmony
>> > code - generated by Doxygen/Javadoc.  I guess many will agree that
>> > having API reference is very useful and convenient.
>> >
>> >
>> >
>> > This issue was discussed a while ago [1] for kernel classes and vmi
>> > interface in classlib. We agreed to store the Doxygen docs on the
>> > website by generating them manually from code and placing there. It
>> > seems that the old version of the docs was removed from SVN but
never
>> > made its way to the website, so it's just NOWHERE now :-(. Let's 
>> fix it!
>> >
>> >
>> > AFAIU, we want to have the following:
>> >
>> > 1.Ability to generate docs locally from source code as part of
>> > build - need to change existing build files or write new ones.
>> > 2.Ability to see docs on the website - manually copy a local
>> > bundle of docs to the website and add a link. Geir has been 
>> planning to
>> > include the website into the next snapshot; supplying ready
reference
>> > with it seem nice.
>> >
>> > Volunteers?
>>
>> > I can work on item 2 for sure to get a nice config file and patch
the
>> > website to link to our new Doxygen API. Item 1 -fixing the build - 
>> might
>> > be more extravagant, so your aid's welcome ;)
>> >
>> It is me that removed the original document in classlib/trunk/doc as
we
>> discussed before, so seems it should be my responsibility to make the
>> work complete:). Sorry for delaying so long. But I still have no
strong
>> feelings where to put them in standard/site, any suggestions?
>>
>> You can create all the API document by run "ant" in
classlib/trunk/doc,
>> you can get all document created, assuming Doxygen is installed. If
you
>> kindly provide the patch, I will look at it and merge it into SVN.
>> >
>> >
>> > [1] mail thread
>> > 
>>
http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/200609.mb
>> > ox/[EMAIL PROTECTED]
>> >
>> >
>> >
>> > Thanks,
>> >
>> > Nadya Morozova
>> >
>> >
>> >
>>
>>
>> -- 
>> Paulex Yang
>> China Software Development Lab
>> IBM
>>
>>
>>
>


-- 
Paulex Yang
China Software Development Lab
IBM

RE: [doc] No Doxygen reference for code :(

[Morozova, Nadezhda]

+1 my idea exactly

Thank you, 
Nadya Morozova
 

-Original Message-
From: Alexey Petrenko [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 01, 2006 4:55 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] No Doxygen reference for code :(

I think that we can place the docs here:
http://incubator.apache.org/harmony/subcomponents/classlibrary/index.htm
l

2006/11/1, Paulex Yang <[EMAIL PROTECTED]>:
> Morozova, Nadezhda wrote:
> > Hi everyone,
> >
> > I've noticed that there's no API reference documentation for Harmony
> > code - generated by Doxygen/Javadoc.  I guess many will agree that
> > having API reference is very useful and convenient.
> >
> >
> >
> > This issue was discussed a while ago [1] for kernel classes and vmi
> > interface in classlib. We agreed to store the Doxygen docs on the
> > website by generating them manually from code and placing there. It
> > seems that the old version of the docs was removed from SVN but
never
> > made its way to the website, so it's just NOWHERE now :-(. Let's fix
it!
> >
> >
> > AFAIU, we want to have the following:
> >
> > 1.Ability to generate docs locally from source code as part of
> > build - need to change existing build files or write new ones.
> > 2.Ability to see docs on the website - manually copy a local
> > bundle of docs to the website and add a link. Geir has been planning
to
> > include the website into the next snapshot; supplying ready
reference
> > with it seem nice.
> >
> > Volunteers?
>
> > I can work on item 2 for sure to get a nice config file and patch
the
> > website to link to our new Doxygen API. Item 1 -fixing the build -
might
> > be more extravagant, so your aid's welcome ;)
> >
> It is me that removed the original document in classlib/trunk/doc as
we
> discussed before, so seems it should be my responsibility to make the
> work complete:). Sorry for delaying so long. But I still have no
strong
> feelings where to put them in standard/site, any suggestions?
>
> You can create all the API document by run "ant" in
classlib/trunk/doc,
> you can get all document created, assuming Doxygen is installed. If
you
> kindly provide the patch, I will look at it and merge it into SVN.
> >
> >
> > [1] mail thread
> >
http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/200609.mb
> > ox/[EMAIL PROTECTED]
> >
> >
> >
> > Thanks,
> >
> > Nadya Morozova
> >
> >
> >
>
>
> --
> Paulex Yang
> China Software Development Lab
> IBM
>
>
>

RE: [doc] No Doxygen reference for code :(

[Morozova, Nadezhda]

Alexei,
One note: I'm *not* writing requirements for engineering on the doc
build system. I'm just sharing my thoughts on an issue that interests
me. Discussion is welcome. Please don't consider my ideas as "the way it
should be".

Thank you, 
Nadya Morozova
 

-Original Message-
From: Fedotov, Alexei A [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 01, 2006 4:52 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [doc] No Doxygen reference for code :(

Nadya,

Thanks for answers. You have a nice approach to the requirement
engineering for the documentation build system. It would be great if you
also add priorities for your requirements.

Looking into your original list of requirements, I've noticed I haven't
addressed the second one:
>2. Ability to see docs on the website

Yesterday I'd added an archive with documentation to HARMONY-2024
http://issues.apache.org/jira/browse/HARMONY-2024, so committers could
now put documentation to the web site and everyone could contribute to
the documentation quality. 

With best regards,
Alexei Fedotov,
Intel Java & XML Engineering

>-----Original Message-
>From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, October 31, 2006 9:02 PM
>To: harmony-dev@incubator.apache.org
>Subject: RE: [doc] No Doxygen reference for code :(
>
>Alexei,
>
>Thanks for meaningful and numerous questions, Alexei. I have thought of
>some of these, but you give it a systematic touch :)
>Others' opinions are welcome, mine in below - marked with [NM].
>
>Related question: do we want to have some version of API doc on the
site
>now? I've experimented with building docs, and could produce a working
>bundle. We can work to enable the build create API docs locally in
>parallel with that.
>
>PS: Geir, there's a specific question for you below.
>
>Thank you,
>Nadya Morozova
>
>
>-Original Message-
>From: Fedotov, Alexei A [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, October 31, 2006 7:49 PM
>To: harmony-dev@incubator.apache.org
>Subject: RE: [doc] No Doxygen reference for code :(
>
>Nadya, All,
>
>Suggestion to generate Doxygen from DRLVM code sounds very interesting.
>I posted a quick solution for Linux to
>http://issues.apache.org/jira/browse/HARMONY-2024
>
>[NM] great news, I'll see if I can do smth similar for Windows.
>
>If you want to have this integrated into build.xml, it would be great
to
>define a correct scope. Could you please give more details what do you
>expect from the documentation build file?
>[NM] I'd give it a try. Please don't expect me to write a design doc
for
>you
>
>A volunteer can try doing some things important for you first, and then
>add new features gradually.
>[NM] yeah, I like the idea of a gradual step-by-step process.
>
> * Should doxygen build documentation for inter-component interfaces?
>[NM] sure, and I guess it's the better-documented part ;)
>
> * What are components? I assume vm, jit, gc are out of the question.
Is
>am execution manager or an interpreter a separate component?
>[NM] see dev guide; we've thought components roughly match to top-level
>folders:  EM, Interpreter, TM are all components. Not sure what to do
>with the three GCs now, though.
>
> * Should doxygen build documentation for each component like vm, jit,
>interpreter, gc?
>[NM] It's my dream and very convenient. Getting Doxygen to run for
>half-hour and get hung doesn't seem an attractive prospect. However, I
>guess we can get some primitive build as a start and add
>component-specific build targets later. For me, an ideal list of
targets
>for Doxygen would be something like:
> - all headers for DRLVM/classlib (one of two, not both in one
>bundle)
> - headers in include/ folder basically. Do we have
any
>high-level interfaces in other places? This could show the "big
picture"
>and somehow map to the arch description.
> - headers for the component name specified.
>We might concentrate on the first two now for simplicity and smaller
>scope.
>
> * Should we put documentation into doc/_doc dirs as class
>library code does?
>[NM] this is a complex issue. I know Geir has wanted to add website to
>the snapshot. *Geir*, could you express your view on where to place
>docs? I guess separating "normal" docs and "autogenerated" docs would
be
>good, like the /doc/ folder for all files, with /doc/Doxygen/ subfolder
>for API reference. When we are ready to build component-specific
>reference, /doc/Doxygen/ can have subfolders for each.
>
> * Should we use the same formatting as a class library documentation?
>[NM] why not? as I've noticed, default formatting is ok, but there are
>many options

RE: [doc] No Doxygen reference for code :(

[Morozova, Nadezhda]

About your question

> It is me that removed the original document in classlib/trunk/doc as
we 
> discussed before, so seems it should be my responsibility to make the 
> work complete:). Sorry for delaying so long. But I still have no
strong 
> feelings where to put them in standard/site, any suggestions?

I'd say, we can place classlib docs inside
standard/site/xdocs/subcomponents/classlib/Doxygen. Do you think we'll
need subfolders for classlib modules inside that? 

> You can create all the API document by run "ant" in
classlib/trunk/doc, 
> you can get all document created, assuming Doxygen is installed. If
you 
> kindly provide the patch, I will look at it and merge it into SVN.

I'd be glad to help. What kind of patch do you need? 
I can build the docs locally and post a JIRA with the archive. I can
also fix the site to have a link to the index.html produced by Doxygen.
Is that what you mean? 

Thank you, 
Nadya Morozova
 

-Original Message-
From: Paulex Yang [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 01, 2006 4:33 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] No Doxygen reference for code :(

Morozova, Nadezhda wrote:
> Hi everyone,
>
> I've noticed that there's no API reference documentation for Harmony
> code - generated by Doxygen/Javadoc.  I guess many will agree that
> having API reference is very useful and convenient.
>
>  
>
> This issue was discussed a while ago [1] for kernel classes and vmi
> interface in classlib. We agreed to store the Doxygen docs on the
> website by generating them manually from code and placing there. It
> seems that the old version of the docs was removed from SVN but never
> made its way to the website, so it's just NOWHERE now :-(. Let's fix
it!
>
>
> AFAIU, we want to have the following:
>
> 1.Ability to generate docs locally from source code as part of
> build - need to change existing build files or write new ones.
> 2.Ability to see docs on the website - manually copy a local
> bundle of docs to the website and add a link. Geir has been planning
to
> include the website into the next snapshot; supplying ready reference
> with it seem nice.
>
> Volunteers? 

> I can work on item 2 for sure to get a nice config file and patch the
> website to link to our new Doxygen API. Item 1 -fixing the build -
might
> be more extravagant, so your aid's welcome ;) 
>   
It is me that removed the original document in classlib/trunk/doc as we 
discussed before, so seems it should be my responsibility to make the 
work complete:). Sorry for delaying so long. But I still have no strong 
feelings where to put them in standard/site, any suggestions?

You can create all the API document by run "ant" in classlib/trunk/doc, 
you can get all document created, assuming Doxygen is installed. If you 
kindly provide the patch, I will look at it and merge it into SVN.
>  
>
> [1] mail thread
>
http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/200609.mb
> ox/[EMAIL PROTECTED] 
>
>  
>
> Thanks,
>
> Nadya Morozova
>
>
>   


-- 
Paulex Yang
China Software Development Lab
IBM

RE: [classlib][portlib] Docs?

[Morozova, Nadezhda]

Not that I know of :( bits of things are in the devguide, maybe. But you
probably won't find that of much notice.
Anyone, please tell me it's not true! 

Thank you, 
Nadya Morozova
 

-Original Message-
From: Alexey Petrenko [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 01, 2006 4:15 PM
To: harmony-dev@incubator.apache.org
Subject: [classlib][portlib] Docs?

Guys,

do we have any docs on portlib?

SY, Alexey

-- 
Alexey A. Petrenko
Intel Middleware Products Division

RE: [build] Building on Eclipse - FYI

[Morozova, Nadezhda]

I join Geir in the compliment. Keep up the good job. Let me know if you
need support - I'd be glad to help.

Thank you, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 31, 2006 7:55 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [build] Building on Eclipse - FYI

thanks for volunteering.  The only thing I'm concerned about is that you

get the input from others about general project documentation "vision", 
rather than just re-doing things.

You're doing a good job of it out here on the -dev list.

geir


Konovalova, Svetlana wrote:
> Geir,
> 
> I've checked a brief webcast for those who want to see a step-by-step
> guide to configuring Eclipse, and it seems to be up-to-date.
> But we still have food for thought: "Getting Started with DRLVM" is
> outdated, and "Working with Classlib in Eclipse" seems misplaced. 
> The first doc needs an update (see Nadya's mail: Mon 10/30/2006 6:53
> PM), and can be abridged to reduce purely eclipse-oriented content. We
> can reference Eclipse docs instead
> [http://help.eclipse.org/help32/index.jsp]. And the second doc has
been
> updated (see HARMONY-2009), but only related to classlib. 
> Many of the things are pretty generic, and with minimal edits can be
fit
> for vm as well. I suggest that we move this doc up to make it more
> visible and edit it so as to apply to the whole project, rather than
to
> classlib only. IMHO the "Project Documentation" section is a good
place
> for this doc
>
[http://incubator.apache.org/harmony/documentation/documentation.html].
> 
> What do you say?
> 
> If you do not mind, I can try to update the doc.
>  
> Best regards,
> Svetlana
> 
> -Original Message-
> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, October 31, 2006 2:18 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [build] Building on Eclipse - FYI
> 
> 
> 
> Konovalova, Svetlana wrote:
>> Nadya,
>>
>> AFAIU the given page is purely classlib-oriented...though I might be
>> wrong here. 
>> It provides info on how to set up Eclipse to develop Java code in
>> Harmony and IMHO doesn't include any tips applying to harmony code in
>> general.
>> I absolutely agree with you that we should have one page describing
> how
>> to work with harmony code in Eclipse. It goes without saying that we
>> need to update info and the help from engineers' side is of great
>> importance here. You might know that there is a brief webcast for
> those
>> who want to see a step-by-step guide to configuring Eclipse. On the
> one
>> hand, it's great, but on the other hand, many screenshots can quickly
>> become outdated. IMHO it's rather complicated to update the video.
> What
>> would you say? Should we keep it as it is?
> 
> Is it actually out of date?
> 
>>
>> Cheers,
>> Sveta
>>
>> -Original Message-
>> From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED] 
>> Sent: Monday, October 30, 2006 6:45 PM
>> To: harmony-dev@incubator.apache.org
>> Subject: RE: [build] Building on Eclipse - FYI
>>
>> Sveta,
>> I've taken a brief look at the patch, and I like most of your
>> corrections. The page looks neater this way, and holds important
data.
>>
>> One question: can't we say that some of the tips given on the page
> apply
>> to harmony code in general, not just classlib? So a side idea would
be
>> to have one page: how to work with harmony code in Eclipse. What do
> you
>> say? 
>>
>> Thank you, 
>> Nadya Morozova
>>  
>>
>> -Original Message-
>> From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED] 
>> Sent: Monday, October 30, 2006 6:23 PM
>> To: harmony-dev@incubator.apache.org
>> Subject: RE: [build] Building on Eclipse - FYI
>>
>> Sian,
>>
>> Taking into consideration your comments, I've opened a new JIRA issue
>> [http://issues.apache.org/jira/browse/HARMONY-2009] and have created
a
>> patch for the page "Developing Apache Harmony Class-library Code with
>> Eclipse". Would be great, if you find a chance to look it through. 
>> Hope we'll continue working at developing this aspect of
> documentation.
>> :)
>>
>> Cheers,
>> Sveta
>>
>> -Original Message-
>> From: Sian January [mailto:[EMAIL PROTECTED] 
>> Sent: Friday, October 27, 2006 3:34 PM
>> To: harmony-dev@incubator.apache.org
>> Subject: Re: [build] Building on Eclipse - FYI
>>
>> Hi Sveta,
>&g

RE: [doc] No Doxygen reference for code :(

[Morozova, Nadezhda]

 for now, what should be added in future?
[NM] I don't know - it's the future!
 
 * Is there any choice for user to affect resulting documentation?
[NM] I don't have a strong opinion about it, but Doxygen's main idea is
to get docs straight from code. So any change to doxygen's input should
probably be a patch in JIRA. We've had such patches before. 

With best regards,
Alexei Fedotov,
Intel Java & XML Engineering

>-Original Message-
>From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, October 31, 2006 4:34 PM
>To: harmony-dev@incubator.apache.org
>Subject: [doc] No Doxygen reference for code :(
>
>Hi everyone,
>
>I've noticed that there's no API reference documentation for Harmony
>code - generated by Doxygen/Javadoc.  I guess many will agree that
>having API reference is very useful and convenient.
>
>
>
>This issue was discussed a while ago [1] for kernel classes and vmi
>interface in classlib. We agreed to store the Doxygen docs on the
>website by generating them manually from code and placing there. It
>seems that the old version of the docs was removed from SVN but never
>made its way to the website, so it's just NOWHERE now :-(. Let's fix
it!
>
>
>AFAIU, we want to have the following:
>
>1. Ability to generate docs locally from source code as part of
>build - need to change existing build files or write new ones.
>2. Ability to see docs on the website - manually copy a local
>bundle of docs to the website and add a link. Geir has been planning to
>include the website into the next snapshot; supplying ready reference
>with it seem nice.
>
>Volunteers?
>
>I can work on item 2 for sure to get a nice config file and patch the
>website to link to our new Doxygen API. Item 1 -fixing the build -
might
>be more extravagant, so your aid's welcome ;)
>
>
>
>[1] mail thread
>http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/200609.m
b
>ox/[EMAIL PROTECTED]
>
>
>
>Thanks,
>
>Nadya Morozova

[doc] No Doxygen reference for code :(

[Morozova, Nadezhda]

Hi everyone,

I've noticed that there's no API reference documentation for Harmony
code - generated by Doxygen/Javadoc.  I guess many will agree that
having API reference is very useful and convenient.

 

This issue was discussed a while ago [1] for kernel classes and vmi
interface in classlib. We agreed to store the Doxygen docs on the
website by generating them manually from code and placing there. It
seems that the old version of the docs was removed from SVN but never
made its way to the website, so it's just NOWHERE now :-(. Let's fix it!


AFAIU, we want to have the following:

1.  Ability to generate docs locally from source code as part of
build - need to change existing build files or write new ones.
2.  Ability to see docs on the website - manually copy a local
bundle of docs to the website and add a link. Geir has been planning to
include the website into the next snapshot; supplying ready reference
with it seem nice.

Volunteers? 

I can work on item 2 for sure to get a nice config file and patch the
website to link to our new Doxygen API. Item 1 -fixing the build - might
be more extravagant, so your aid's welcome ;) 

 

[1] mail thread
http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/200609.mb
ox/[EMAIL PROTECTED] 

 

Thanks,

Nadya Morozova

RE: [doc][drlvm] new docs added - JIT compiler

[Morozova, Nadezhda]

Don't mention it :)
Because packaging images seems to have such a magic effect, I did the
same for the other open doc issue
http://issues.apache.org/jira/browse/HARMONY-1882 could you please apply
that as well? The .patch and the .zip file should be enough.

Thank you, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 31, 2006 2:18 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc][drlvm] new docs added - JIT compiler

oh, thankyou thankyou thankyou

Morozova, Nadezhda wrote:
> Yeah! No problem, I was just thinking a zip would not look as
> transparent and safe. I'd turn the images from the other doc issue
into
> an archive as well.
> 
> Thank you, 
> Nadya Morozova
>  
> 
> -Original Message-
> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, October 31, 2006 5:20 AM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [doc][drlvm] new docs added - JIT compiler
> 
> is there any chance you could put a zip of the images into the jira, 
> rather than a  dozen or so images?  That's actually what turned me off

> from one of the other doc issues - I said to myself "oh, heck, I don't

> want to download each of those separate thingies... I just want a zip
or
> 
> tgz of them... easier to handle..."
> 
> So please? :)
> 
> geir
> 
> Morozova, Nadezhda wrote:
>> All, 
>>
>> New documents have been added to HARMONY-2003. These are a
description
>> of the Jitrino.OPT and .JET compilers, with a supplementary doc on
the
>> pipeline management framework inside the JITs. The docs describe the
>> architecture, processes and usage of the components.
>>
>>  
>>
>> It would be great if somebody took a look, expressed an opinion, and,
> if
>> favorable, committed to the website.
>>
>> Your review or any other feedback are most welcome,
>>
>>  
>>
>> Thanks, 
>>
>> Nadya Morozova
>>
>>  
>>
>> PS: this JIRA is not the only one unresolved doc issue. Find more
> useful
>> pending patches in our database :-)
>>
>>
> 

RE: [doc][drlvm] new docs added - JIT compiler

[Morozova, Nadezhda]

Yeah! No problem, I was just thinking a zip would not look as
transparent and safe. I'd turn the images from the other doc issue into
an archive as well.

Thank you, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 31, 2006 5:20 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc][drlvm] new docs added - JIT compiler

is there any chance you could put a zip of the images into the jira, 
rather than a  dozen or so images?  That's actually what turned me off 
from one of the other doc issues - I said to myself "oh, heck, I don't 
want to download each of those separate thingies... I just want a zip or

tgz of them... easier to handle..."

So please? :)

geir

Morozova, Nadezhda wrote:
> All, 
> 
> New documents have been added to HARMONY-2003. These are a description
> of the Jitrino.OPT and .JET compilers, with a supplementary doc on the
> pipeline management framework inside the JITs. The docs describe the
> architecture, processes and usage of the components.
> 
>  
> 
> It would be great if somebody took a look, expressed an opinion, and,
if
> favorable, committed to the website.
> 
> Your review or any other feedback are most welcome,
> 
>  
> 
> Thanks, 
> 
> Nadya Morozova
> 
>  
> 
> PS: this JIRA is not the only one unresolved doc issue. Find more
useful
> pending patches in our database :-)
> 
> 

RE: [build] Building on Eclipse - FYI

[Morozova, Nadezhda]

Geir, about your suggestion

> I think that if we have an eclipse document, and the info is accurate,
I 
> say why not?

I also think that the more docs the better :) issues that I see with
this particular doc:
- info is not always up-to-date: old cmd options, old java executable
name, many other things I might not know of
- too many dependencies on Eclipse - many screenshots that quickly
become (or have become) outdated because UI in Eclipse can change. These
are sometimes just not needed because they clutter up the page and don't
explain much.
- other pages, like the Classlib page for eclipse, edited in issue
HARMONY-2009 today, repeat some info.

I like the idea of having a nice getting started - as a logical
continuation of your Quick Helps. All I wanted to say: don't think that
effort and further maintenance are minimal here :) I might try to help
with the doc, though there seem to be many other things I'll need to do.

Thank you, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 30, 2006 3:23 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [build] Building on Eclipse - FYI



Sian January wrote:
> I'm actually not sure if that first page is up to date or not  (
>
http://incubator.apache.org/harmony/subcomponents/classlibrary/dev_eclip
se.html). 
> 
> I think it should be but I have not ever been able to get it to work
> myself.  Can anyone else confirm whether it is still in date or not?
> 
> Also I'm just wondering whether we really need steps 5-14 of "Running
an
> Application in Eclipse" or any of "Debugging an Application in
Eclipse"?
> There doesn't seem to be anything Harmony-specific in those steps,
it's 
> just
> about using Eclipse.  I know Eclipse itself contains that kind of
> documentation in its help system so IMHO it seems like it could be a
little
> redundant to duplicate that on the Harmony website.
> 

I think that if we have an eclipse document, and the info is accurate, I

say why not?

We're trying to suck people into the whirling vortex that is our little 
project, and if it's someone that isn't an eclipse user, but was 
intrigued by our ability to run it, etc, etc, it seem to be harmless.  I

assume that it won't change often, so the maintenance is minor?

geir

> Thanks,
> 
> Sian
> 
> 
> On 27/10/06, Konovalova, Svetlana <[EMAIL PROTECTED]>
wrote:
>>
>> Sian,
>>
>> Thanks a lot for the detailed description of what I should do. I'll
>> follow your recommendations. :)
>>
>> I'll investigate what we have already written about Eclipse to avoid
>> redundant info and repeating pages.
>>
>> What I've just come across are:
>> 1) The page describing how to set up Eclipse to develop Java code in
>> Apache Harmony
>>
[http://incubator.apache.org/harmony/subcomponents/classlibrary/dev_ecli
>> pse.html];
>> 2) The sections "Running an Application in Eclipse" and "Debugging an
>> Application in Eclipse "in the Getting Started with DRL
>>
[file:///C:/SVN-23-10/docs/subcomponents/drlvm/getting_started.html#Ecli
>> pse_Hello_world]
>>
>> Would be great, if you find a chance to check whether the
aforementioned
>> info is up-to-date :)
>>
>> Cheers,
>> Sveta
>> -Original Message-
>> From: Sian January [mailto:[EMAIL PROTECTED]
>> Sent: Friday, October 27, 2006 3:34 PM
>> To: harmony-dev@incubator.apache.org
>> Subject: Re: [build] Building on Eclipse - FYI
>>
>> Hi Sveta,
>>
>> That sounds like a great idea.  I think the two main things you need
to
>> do
>> extra on Eclipse on Windows are as follows:
>>
>> 1. Make a copy of vsvars32.bat from your Visual Studio install
>> directory.
>> If you have chosen the defaults when installing you will find it in
>> "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools".
>> Copy it
>> to somewhere convenient such as the desktop and add the following
line
>> (just
>> below the last line that begins "@set..."):
>> start C:\...\eclipse\eclipse.exe -vmargs -Xmx512M
>> (where ... is the path to your eclipse installation).  NB. using
>> "-vmargs
>> -Xmx512M" is optional, but helpful to stop Eclipse running out of
>> memory.
>> Now just double click on this file to start Eclipse.
>>
>> 2. After you have started Eclipse and checked out Harmony from SVN,
copy
>> ecj_3.2.jar into ..\eclipse\plugins\org.apache.ant_1.6.5\lib and
change
>> the
>> Ant settings to include this jar (Window > Preferences > Ant >
Runtime
>> then
>> select 'Global Entries' then 'Add External Jars' and add ecj_3.2.jar
>> from
>> the org.apache.ant_1.6.5\lib directory).
>>
>> If you're happy to add that to the document that would be great.
>>
>> On Linux you will also need to do 2, but I'm not sure if there's an
>> equivalent to 1 or not.  Has anyone else tried building in Eclipse on
>> Linux?
>>
>> Thanks,
>>
>> Sian
>>
>>
>> On 26/10/06, Konovalova, Svetlana <[EMAIL PROTECTED]>
wrote:
>> >
>> > Folks,
>> >
>> > I see that we do need one more building doc describing Eclipse
>> > specifics.
>> > The ma

RE: [build] Building on Eclipse - FYI

[Morozova, Nadezhda]

+1

Thank you, 
Nadya Morozova
 

-Original Message-
From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 30, 2006 5:05 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [build] Building on Eclipse - FYI

Well, my 2cents:

>My concern is that if there is too much documentation and it's not well
>structured then people won't be inclined to read any of it.  If 50% of
the
>"Getting Started with DRLVM" page is actually about Eclipse, my feeling
is
>that it won't be as useful for people who actually want to get started
with
>DRLVM than it would be if it was half the size and more concise.  

I'm with you here. It goes without saying that when a person comes
across a long description, he/she just skips it. In our documentation we
should provide DRLVM-related information only. My suggestions are:
1) To remove "just-using-Eclipse" information from the "Getting Started
with DRLVM" doc
[http://incubator.apache.org/harmony/subcomponents/drlvm/getting_started
] to make the doc purely DRLVM-oriented;
2) To add certain links from the doc to external sources providing
general information about Eclipse.

How about that?

AFAIU we should get two docs guiding the Eclipse users:
1) The "Getting Started with DRLVM" doc including step-by-step
instructions on running a Java application in the Eclipse environment.
[http://incubator.apache.org/harmony/subcomponents/drlvm/getting_started
];
2) The "Developing Apache Harmony class library code with Eclipse" page
providing instructions to help users set up Eclipse to develop Java code
in Apache Harmony.  
[http://incubator.apache.org/harmony/subcomponents/classlibrary/dev_ecli
pse.html]

Any comments?

Cheers,
Sveta

-Original Message-
From: Sian January [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 30, 2006 4:07 PM
To: harmony-dev@incubator.apache.org; [EMAIL PROTECTED]
Subject: Re: [build] Building on Eclipse - FYI

My concern is that if there is too much documentation and it's not well
structured then people won't be inclined to read any of it.  If 50% of
the
"Getting Started With DRLVM" page is actually about Eclipse, my feeling
is
that it won't be as useful for people who actually want to get started
with
DRLVM than it would be if it was half the size and more concise.  In
general
I think having Eclipse-related documentation on its own page (or
inline where it's relevant) is a good thing, I was just commenting on
the
amount of seemingly unrelated Eclipse documentation that is currently
included in the DRLVM page (
http://incubator.apache.org/harmony/subcomponents/drlvm/getting_started.
html).
Just my 2p worth...

Thanks,

Sian


On 30/10/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
>
>
>
> Sian January wrote:
> > I'm actually not sure if that first page is up to date or not  (
> >
>
http://incubator.apache.org/harmony/subcomponents/classlibrary/dev_eclip
se.html
> ).
> >
> > I think it should be but I have not ever been able to get it to work
> > myself.  Can anyone else confirm whether it is still in date or not?
> >
> > Also I'm just wondering whether we really need steps 5-14 of
"Running an
> > Application in Eclipse" or any of "Debugging an Application in
Eclipse"?
> > There doesn't seem to be anything Harmony-specific in those steps,
it's
> > just
> > about using Eclipse.  I know Eclipse itself contains that kind of
> > documentation in its help system so IMHO it seems like it could be a
> little
> > redundant to duplicate that on the Harmony website.
> >
>
> I think that if we have an eclipse document, and the info is accurate,
I
> say why not?
>
> We're trying to suck people into the whirling vortex that is our
little
> project, and if it's someone that isn't an eclipse user, but was
> intrigued by our ability to run it, etc, etc, it seem to be harmless.
I
> assume that it won't change often, so the maintenance is minor?
>
> geir
>
> > Thanks,
> >
> > Sian
> >
> >
> > On 27/10/06, Konovalova, Svetlana <[EMAIL PROTECTED]>
wrote:
> >>
> >> Sian,
> >>
> >> Thanks a lot for the detailed description of what I should do. I'll
> >> follow your recommendations. :)
> >>
> >> I'll investigate what we have already written about Eclipse to
avoid
> >> redundant info and repeating pages.
> >>
> >> What I've just come across are:
> >> 1) The page describing how to set up Eclipse to develop Java code
in
> >> Apache Harmony
> >> [
>
http://incubator.apache.org/harmony/subcomponents/classlibrary/dev_ecli
> >> pse.html];
> >> 2) The sections "Running an Application in Eclipse" and "Debugging
an
> >> Application in Eclipse "in the Getting Started with DRL
> >> [
>
file:///C:/SVN-23-10/docs/subcomponents/drlvm/getting_started.html#Ecli
> >> pse_Hello_world]
> >>
> >> Would be great, if you find a chance to check whether the
> aforementioned
> >> info is up-to-date :)
> >>
> >> Cheers,
> >> Sveta
> >> -Original Message-
> >> From: Sian January [mailto:[EMAIL PROTECTED]
> >> Sent: Friday, October 27, 2006 3:34 PM
> >> To: harmony-de

RE: [build] Building on Eclipse - FYI

[Morozova, Nadezhda]

Sveta,
I've taken a brief look at the patch, and I like most of your
corrections. The page looks neater this way, and holds important data.

One question: can't we say that some of the tips given on the page apply
to harmony code in general, not just classlib? So a side idea would be
to have one page: how to work with harmony code in Eclipse. What do you
say? 

Thank you, 
Nadya Morozova
 

-Original Message-
From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 30, 2006 6:23 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [build] Building on Eclipse - FYI

Sian,

Taking into consideration your comments, I've opened a new JIRA issue
[http://issues.apache.org/jira/browse/HARMONY-2009] and have created a
patch for the page "Developing Apache Harmony Class-library Code with
Eclipse". Would be great, if you find a chance to look it through. 
Hope we'll continue working at developing this aspect of documentation.
:)

Cheers,
Sveta

-Original Message-
From: Sian January [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 27, 2006 3:34 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [build] Building on Eclipse - FYI

Hi Sveta,

That sounds like a great idea.  I think the two main things you need to
do
extra on Eclipse on Windows are as follows:

1. Make a copy of vsvars32.bat from your Visual Studio install
directory.
If you have chosen the defaults when installing you will find it in
"C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools".
Copy it
to somewhere convenient such as the desktop and add the following line
(just
below the last line that begins "@set..."):
start C:\...\eclipse\eclipse.exe -vmargs -Xmx512M
(where ... is the path to your eclipse installation).  NB. using
"-vmargs
-Xmx512M" is optional, but helpful to stop Eclipse running out of
memory.
Now just double click on this file to start Eclipse.

2. After you have started Eclipse and checked out Harmony from SVN, copy
ecj_3.2.jar into ..\eclipse\plugins\org.apache.ant_1.6.5\lib and change
the
Ant settings to include this jar (Window > Preferences > Ant > Runtime
then
select 'Global Entries' then 'Add External Jars' and add ecj_3.2.jar
from
the org.apache.ant_1.6.5\lib directory).

If you're happy to add that to the document that would be great.

On Linux you will also need to do 2, but I'm not sure if there's an
equivalent to 1 or not.  Has anyone else tried building in Eclipse on
Linux?

Thanks,

Sian


On 26/10/06, Konovalova, Svetlana <[EMAIL PROTECTED]> wrote:
>
> Folks,
>
> I see that we do need one more building doc describing Eclipse
> specifics.
> The main doc containing building instructions now is the "Getting
> Started for Contributors" page.
> [http://incubator.apache.org/harmony/quickhelp_contributors.html].
> My suggestion is to add one more section to it describing building
> instructions for Eclipse. How about that?
>
> If you need my help, I'll be glad to manage the doc creation:)
>
> Cheers,
> Sveta
>
> -Original Message-
> From: Sian January [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 26, 2006 4:06 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [build] Building on Eclipse - FYI
>
> Hi Nathan,
>
> Yes - I was trying to run the enitre build in Eclipse and this is
always
> my
> preferred method of building.  There is at least one other extra step
> apart
> from the one discussed in this thread so I think some additional
> documentation would be useful.
>
> Thanks,
>
> Sian
>
>
>
> On 25/10/06, Nathan Beyer <[EMAIL PROTECTED]> wrote:
> >
> > Are you referring to running the build scripts via Eclipse? Just
> > wanted to make sure I understand.
> >
> > Personally, I only import the module projects one at a time and run
> > the full builds outside of Eclipse, so I've never tried this.
Perhaps
> > some additional documentation on using Eclipse in this fashion. This
> > might be helpful additionally.
> >
> > On 10/24/06, Sian January <[EMAIL PROTECTED]> wrote:
> > > Hello,
> > >
> > > I encountered a problem today building on Eclipse, and I just
> thought
> > I'd
> > > post about it here in case anyone sees the same problem in the
> > future.  I
> > > was getting the error:
> > >
> > >
> > > BUILD FAILED
> > > *
> > >
> > > C:\eclipse32harmony\eclipse\workspace\Harmony\build.xml:108: The
> > following
> > > error occurred while executing this line:
> > >
> > >
> C:\eclipse32harmony\eclipse\workspace\Harmony\make\build-java.xml:127:
> > The
> > > Eclipse compiler class for Ant could not be found. Please place
the
> ECJ
> > JAR
> > > in ANT_HOME/lib. The JAR can copied from
> > CLASSLIB_TRUNK/depends/jars/ecj_3.2
> > > folder after the fetch-depends target has been run.
> > > *
> > >
> > > The solution to this is to copy ecj_3.2.jar into
> > > ..\plugins\org.apache.ant_1.6.5\lib and *also* change the Ant
> settings
> > to
> > > include this jar (Window > Preferences > Ant > Runtime then select
> > 'Global
> > > Entries' then 'Add External Jars' and add ecj_

[doc][drlvm] new docs added - JIT compiler

[Morozova, Nadezhda]

All, 

New documents have been added to HARMONY-2003. These are a description
of the Jitrino.OPT and .JET compilers, with a supplementary doc on the
pipeline management framework inside the JITs. The docs describe the
architecture, processes and usage of the components.

 

It would be great if somebody took a look, expressed an opinion, and, if
favorable, committed to the website.

Your review or any other feedback are most welcome,

 

Thanks, 

Nadya Morozova

 

PS: this JIRA is not the only one unresolved doc issue. Find more useful
pending patches in our database :-)

RE: [doc] List of current open doc issues

[Morozova, Nadezhda]

Perhaps, you can store it on JIRA? I do get an email a third time, and
none of them has an attachment:(

Thank you, 
Nadya Morozova
 

-Original Message-
From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 26, 2006 5:01 PM
To: harmony-dev@incubator.apache.org
Subject: FW: [doc] List of current open doc issues


Now with attachment. 

(Sorry if you get this letter for the second/third time. I do attach the
doc, but it's rejected all the time...)

Cheers,
Sveta

-Original Message-
From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 26, 2006 3:47 PM
To: harmony-dev@incubator.apache.org; [EMAIL PROTECTED]
Subject: RE: [doc] List of current open doc issues

>I committed 3 5 and 7, but I'd like some other opinions about changing 
>the classlibrary section - if things need to be fixed, should we fix 
>them rather than remove them?  I'd like the opinions of the authors of 
>that stuff...

Geir, thanks for committing the patches 3,5,7. 

As for the classlibrary section, I'd like to ask its authors to check
the patches 1 and 2 (unfortunately I do not them by names...). 

Speaking about the Building the Apache Harmony Class Library page
[http://incubator.apache.org/harmony/subcomponents/classlibrary/build_cl
asslib.html], which I suggest to remove because it's out-of-date, I'd
like to mention that its important bits of info were removed to the
patches 3 and 5. IMHO we can delete the aforementioned page without any
harm... 


>> 2. To improve the "How to write GC" doc and update its content:
>> 
>>http://issues.apache.org/jira/browse/HARMONY-1881 
>> 
>> Would be great if someone can decide its fate. :)

>The patch was wrong - it included the navigation.  That's added in the 
>rendering process

I'm so sorry about that. I've created another patch, hope it's the right
one. But since I have a problem with logging in to JIRA that is
connected with the machine died in the move, I'd like to ask someone to
apply the attached patch. 

Thanks in advance!  

Cheers,
Sveta

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 25, 2006 3:01 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] List of current open doc issues



Konovalova, Svetlana wrote:
> Folks,
> 
> I do not want to be too pushy, just have a suggestion to close certain
JIRAs (whenever you'll find a chance). 
> 
> 1. To reduce the number of places describing the building process, to
update the content:
> 
> http://issues.apache.org/jira/browse/HARMONY-1730 and
http://issues.apache.org/jira/browse/HARMONY-1828 depended from the
first JIRA.
> I've integrated the patches from JIRA-1828 into the ones from
JIRA-1730. So, we can close JIRA-1828 without loosing important info. 
> 
> As the result we'll get the following building instructions docs: 
> 
> "Getting Started for Contributors" describing how to get configured to
build and work with the Apache Harmony source code.
> Please apply quickhelp_contrib.patch (3)/JIRA-1730
> 
> "Getting Started for Users" providing basic instructions for users
that
> wish to use Apache Harmony for running their Java programs.
> Please apply quickhelp_users.patch (5) /JIRA-1730
> 
> README providing instructions on how to point to local 
>versions instead of making the build download new ones from the
net.
> Please, apply README.patch (7) /JIRA-1730
> 
> I've removed the Building the Apache Harmony Class Library page
[http://incubator.apache.org/harmony/subcomponents/classlibrary/build_cl
asslib.html]   because it's out-of-date. In this connection we need to
remove the build_classlib.xml file from the repository.
> I've removed all references to this page from wiki and other site
pages (it increased the number of patches...sorry about that..)
> Please, apply downloads.patch (1) and index.patch (2) /JIRA-1730
> 

I committed 3 5 and 7, but I'd like some other opinions about changing 
the classlibrary section - if things need to be fixed, should we fix 
them rather than remove them?  I'd like the opinions of the authors of 
that stuff...


> 
> 2. To improve the "How to write GC" doc and update its content:
> 
> http://issues.apache.org/jira/browse/HARMONY-1881 
> 
> Would be great if someone can decide its fate. :)

The patch was wrong - it included the navigation.  That's added in the 
rendering process

> 
> 3. To make "DRLVM Dev Guide" more up-to-date and nice-to-read:
> 
> http://issues.apache.org/jira/browse/HARMONY-1882 
> 
> I'll be glad if you find a chance to look at the patches and apply
them :).
> Thanks in advance!
> 
> Best regards,
> Sveta Konovalova
> 

RE: [general] POLL : supported platforms

[Morozova, Nadezhda]

Ok, thanks all, I see now.
Can I suggest that we define the supported platforms (the term itself +
the list of currently supported combinations) on the site. We can also
keep a Wiki page for related issues.
The platform support info could go to the download-snapshots page.

Thank you, 
Nadya Morozova
 

-Original Message-
From: Tim Ellison [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 25, 2006 7:02 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [general] POLL : supported platforms

I agree with Salikh -- the wiki will never keep up if you expect such
frequent manual updates.  That's a job for the test results' collator.

Regards,
Tim

Salikh Zakirov wrote:
> Morozova, Nadezhda wrote:
>> My two cents...
>>
>>>> I do not understand the lifecycle of this page. If I report today
>> that
>>> my
>>>> platform works OK, but the next commit brokes it, who will update
the
>>> page?
>>>
>>> IMHO if the next commit breakes the work-ok-platform and if you
notice
>>> it, why not to update the wiki page? Or you can let me know about
this
>>> bug and I'll make the update:)
>> Do you think we can add a note with the revision number? This way,
you
>> at least know that the code of  revision worked ok/failed on this
>> platform. Because such tests are done systematically, changing
revisions
>> would not take much time to update. 
> 
> -1
> 
> I think this is a conceptually incorrect approach
> to try to keep a relatively slowly changing wiki page up-to-date with
fast-paced commits.
> I believe this approach is doomed, and the status page is going to get
out-of-date 
> while it is being edited.
> 
> I would suggest the following "fix" to the approach:
> * Reserve the "supported platforms" notion for the developer releases
or snapshots,
> and do not use the term with respect to SVN trunk
> * Relate the list of "supported platforms" with the release management
process,
>   and describe the status of particular snapshots, and not SVN trunk
in general.
>  
> 
> 

-- 

Tim Ellison ([EMAIL PROTECTED])

RE: [general] POLL : supported platforms

[Morozova, Nadezhda]

My two cents...

> >I do not understand the lifecycle of this page. If I report today
that
> my
> >platform works OK, but the next commit brokes it, who will update the
> page?
>
> IMHO if the next commit breakes the work-ok-platform and if you notice
> it, why not to update the wiki page? Or you can let me know about this
> bug and I'll make the update:)
Do you think we can add a note with the revision number? This way, you
at least know that the code of  revision worked ok/failed on this
platform. Because such tests are done systematically, changing revisions
would not take much time to update. 

-Original Message-
From: Konovalova, Svetlana [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 25, 2006 12:59 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [general] POLL : supported platforms


>Wow! the only platform with bugs we have is  "Windows XP with VS.NET
2005
>Community Edition" ! :)

 Well... are you sure? Or do you make this supposition judging by the
"Platforms to Run Harmony Development Kit on" page? The point is that I
didn't have enough info to fill in the empty table cells. My aim was to
create a field for developers' comments and the table there is right for
their convenience. :) I'd like to ask developers using different
platforms to leave their comments there to get the clear picture of what
we have for now. Does it make sense?

>I do not understand the lifecycle of this page. If I report today that
my
>platform works OK, but the next commit brokes it, who will update the
page?

IMHO if the next commit breakes the work-ok-platform and if you notice
it, why not to update the wiki page? Or you can let me know about this
bug and I'll make the update:) 



Cheers,
Sveta

-Original Message-
From: Mikhail Fursov [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 25, 2006 12:11 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [general] POLL : supported platforms

On 10/25/06, Konovalova, Svetlana <[EMAIL PROTECTED]> wrote:
>
> Comments? Objections?


Wow! the only platform with bugs we have is  "Windows XP with VS.NET
2005
Community Edition" ! :)


I do not understand the lifecycle of this page. If I report today that
my
platform works OK, but the next commit brokes it, who will update the
page?
What is "works OK"? Builds and runs classlib/drlvm tests only?

Thanks,
> Stepan.
>
>
> Windows
> > ===
> > Windows XP x86
> >
> > Linux
> > =
> > Ubuntu 6 x86
> > Ubuntu 5 x86
> > RHEL  (version ?) x86
> > FC (version ?) x86
> > SUSE (verion ?) x86
> >
> >
> >
>
>
> --
> Stepan Mishura
> Intel Middleware Products Division
>
> --
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>



-- 
Mikhail Fursov

RE: [vote] Graduate Apache Harmony podling from the Incubator

[Morozova, Nadezhda]

+1

Thank you, 
Nadya Morozova
 
-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 20, 2006 11:30 PM
To: harmony-dev@incubator.apache.org
Subject: [vote] Graduate Apache Harmony podling from the Incubator

We're trying something a little different.  I think Roy Fielding one 
said something along the lines of "when a community gets organized 
enough to vote itself out of the Incubator, it's appropriate."

So to bring the Harmony community and the Incubator community together 
for this important event in Harmony's life, I'm calling for a vote on 
graduating Harmony here on our own -dev list.  The objective is for all 
in both the Harmony community and the Incubator community that have an 
opinion to vote together, in the same place, and have it "hosted" by the

Harmony podling.

This is an unconventional way to do this, but I think that it's valid 
and could provide one example to the Incubator on how it can work going 
forward.

So, without any further ado :

[ ] +1 Graduate Apache Harmony from incubation, and let it petition the 
board for Top Level Project status

[ ] 0 No opinion

[ ] -1 No, don't graduate Harmony.  Here's why :


This vote will end 72 hours from now + time of Apache mail outage.  It 
will therefore end on Monday, October 23, at 3:30 PM eastern, + delta 
for mail outage.

Thanks

geir


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

RE: Re: [drlvm] How to debug the drlvm with gdb?

[Morozova, Nadezhda]

Yeo-hoo! Great news, Mikhail.
Do you think you can also take a look at our Debugging guide on the
website? I think it also gives some debugging tips on MSVS. Are any of
them still valid? :)

Thank you, 
Nadya Morozova
 

-Original Message-
From: Mikhail Fursov [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 20, 2006 4:59 PM
To: harmony-dev@incubator.apache.org
Subject: Re: Re: [drlvm] How to debug the drlvm with gdb?

On 10/20/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
>
> Summing up: the decision for now = Add new pages for Wiki =
> - Debugging on Linux - Egor has volunteered; anybody else?
> - Debugging on Windows - Mikhail has been recommended; how's that?


Nadya,
yes I have a text that describes how to localize bugs in JIT. Also I
support
Microsoft Visual Studion 2003 build for Windows (in SVN) - it's very
convenient to use it for debugging.

I'll post these documents this weekend to our Wiki and will let you
know.

-- 
Mikhail Fursov

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

RE: Re: [drlvm] How to debug the drlvm with gdb?

[Morozova, Nadezhda]

Egor,
Thanks for a detailed an proactive response. 
Surely, I think we can start accumulating new content on Wiki - this is
more visible and editable than patches to website. When we're done with
the bulk of content, I'll migrate the stable stuff to the site.

> * Thaking the one above into account, I would suggest to start "Linux
> debugging" on Wiki. Does it make sense to put it in the FAQ? How do
> you like the idea of Harmony_Debug_Troubleshooting on Wiki?
I do like the idea. However, I think, pure debug tips is one thing and
troubleshooting debug is another. Now, troubleshooting debug is when
pure debug doesn't work :) or so it seems. So, perhaps, the title of the
suggested page can be changed.

Summing up: the decision for now = Add new pages for Wiki =
- Debugging on Linux - Egor has volunteered; anybody else?
- Debugging on Windows - Mikhail has been recommended; how's that?

Additional question:
Can we have Debugging page for some basic relatively stable stuff and
Advanced Tasks+Troubleshooting (hacks and
things-that-should-not-be-there-but-are) in a separate page?

Thank you, 
Nadya Morozova
 

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
Sent: Friday, October 20, 2006 4:16 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [drlvm] How to debug the drlvm with gdb?

On the 0x208 day of Apache Harmony Nadezhda Morozova wrote:
> Egor, 
> You're a treasure keeper, so many useful tips :) 

Actually, I am not any more :)

> As you mentioned yourself, this info should be on the website, and I
> side with you on this.

thank you for helping!

> We actually have some debugging tips already:
>
http://incubator.apache.org/harmony/subcomponents/drlvm/debugging_VM_and
> _JIT.html 
> However, they don't mention the launcher and all those tiny little
> things you mentioned, like the format of paths, etc. the doc is also
> partially outdated (mentions ij). 

To sum up my thoughts:

* debugging_VM_and_JIT 
  + is outdated
  + covers both linux and windows debugging tips intermixed
  + has instructions for JET tracing (quite valid)

* Let's make make it 2 separate docs: "Linux debugging" and "Windows
  debugging". A new guy reading one of these two docs will most likely
  not want to read another. The interection between the two would be
  rather small (promise)

* I listed a number of linux quickstart HOWTOs which, I think, is a
  good base for the "Linux debugging" part.

* Mikhail supports the MSVC project file(s) and can add something to
  "Windows debugging" doc (Mikhail, do you love technical writing?:)

* Let's make the 3rd doc "DRLVM Advanced Debugging and Bug Isolation"
  (Some people around are having good ideas on it). JET traceing would
  move here.

* there are some shortcomings (in both classlib and DRLVM) that do not
  allow us to enable a usable debug build quickly. And description
  falls into a category like "hack here and there if you like". That's
  not what the ideal instructions should be. Maybe, it makes sense to
  postpone the task until we enable default debug builds everywhere.

* Thaking the one above into account, I would suggest to start "Linux
  debugging" on Wiki. Does it make sense to put it in the FAQ? How do
  you like the idea of Harmony_Debug_Troubleshooting on Wiki?

did I forget something?

> Do you think we can use this doc as the basis for storing more
content?

yes, as the basis to "Linux debugging" or for something that we find
better.

> Thank you, 
> Nadya Morozova
>  
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
> Sent: Friday, October 20, 2006 1:34 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [drlvm] How to debug the drlvm with gdb?
> 
> On the 0x208 day of Apache Harmony Tonny Lau wrote:
> > Hi,
> > 
> > I checked out the latest drlvm, and failed to set breakpoint when I
> used
> > gdb. It seems the
> >
>
"harmony/enhanced/drlvm/trunk/build/lnx_ia32_gcc_debug/deploy/jre/bin/ja
> va"
> > is copied from
> "harmony/enhanced/classlib/trunk/deploy/jdk/jre/bin/java",
> > i.e., it is not a debug version. Does anyone know how to debug it?
> Thanks!
> 
> Oh! should be on the site!! some day .. some day ..
> 
> Yes, it's the launcher. It is taken from classlib (which is not built
> in debug mode even if DRLVM is built in debug (=default)). If you want
> to build the launcher in debug mode, change:
> working_classlib/depends/build/makefile.include
> (put -O0 -g instead of -O1)
> 
> pretty, huh? :)
> 
> to debug on linux you should export LD_LIBRARY_PATH for GDB:
> 
> export LD_LIBRARY_PATH=$jre/bin:$jre/bin/default
> (you know what $jre is:)
> (news is that tere should be no slashess at the end of each path, and
no
> soft links inside, surprize, surprize:)
> 
> then you can run GDB and, at least, see threads created, etc..
> 
> DRLVM is quite distributed between shared libraries, so it is not easy
> to set breakpoints somewhere in libraries' code. There are 2
> approaches: 
> 

RE: Re: [drlvm] How to debug the drlvm with gdb?

[Morozova, Nadezhda]

Egor, 
You're a treasure keeper, so many useful tips :) 
As you mentioned yourself, this info should be on the website, and I
side with you on this.
We actually have some debugging tips already:
http://incubator.apache.org/harmony/subcomponents/drlvm/debugging_VM_and
_JIT.html 
However, they don't mention the launcher and all those tiny little
things you mentioned, like the format of paths, etc. the doc is also
partially outdated (mentions ij). 

Do you think we can use this doc as the basis for storing more content?

Thank you, 
Nadya Morozova
 
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
Sent: Friday, October 20, 2006 1:34 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [drlvm] How to debug the drlvm with gdb?

On the 0x208 day of Apache Harmony Tonny Lau wrote:
> Hi,
> 
> I checked out the latest drlvm, and failed to set breakpoint when I
used
> gdb. It seems the
>
"harmony/enhanced/drlvm/trunk/build/lnx_ia32_gcc_debug/deploy/jre/bin/ja
va"
> is copied from
"harmony/enhanced/classlib/trunk/deploy/jdk/jre/bin/java",
> i.e., it is not a debug version. Does anyone know how to debug it?
Thanks!

Oh! should be on the site!! some day .. some day ..

Yes, it's the launcher. It is taken from classlib (which is not built
in debug mode even if DRLVM is built in debug (=default)). If you want
to build the launcher in debug mode, change:
working_classlib/depends/build/makefile.include
(put -O0 -g instead of -O1)

pretty, huh? :)

to debug on linux you should export LD_LIBRARY_PATH for GDB:

export LD_LIBRARY_PATH=$jre/bin:$jre/bin/default
(you know what $jre is:)
(news is that tere should be no slashess at the end of each path, and no
soft links inside, surprize, surprize:)

then you can run GDB and, at least, see threads created, etc..

DRLVM is quite distributed between shared libraries, so it is not easy
to set breakpoints somewhere in libraries' code. There are 2
approaches: 
1. drop asm("int3") in your code, rebuild and catch it via an
   ordinary run from within GDB
2. stop at position when nothing interesting happend, but all
   libraries are loaded (my favourite)

for (2) I use 2 custom GDB scripts "hstart" and "hrun". "hstart" makes
the first stop on my favourite start point. "hrun" uses those
breakpoints to stop on the point with further runs in the GDB session.

To get these two, drop these lines into your ~/.gdbinit:
---
define hstart
break main
run
break hysl_open_shared_library
continue
finish
disable
break compile_jit_a_method
continue
disable
end

define hrun
en 1
run
en 2
continue
finish
disable
en 3
continue
disable
end
---

good luck! ;)

-- 
Egor Pasko, Intel Managed Runtime Division


-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

RE: Re: "Hot to Write GC" requires improvement

[Morozova, Nadezhda]

Salikh, 
Thanks for a detailed and constructive response :) I am sorry if I
sounded too oppressive or negative about Asciidoc. I have used it
successfully and have nothing against it, though I can't say it's a
preference with me :)

Your advice helps me understand how to best customize it to our needs. 
> I am sure configuring it for producing XML is perfectly possible.
Great to hear it! 

> In fact, this is not an asciidoc limitation, this was just the first 
> solution that I came up with. There may be better ways, for example 
> something like adding a explicit cut markers to the code that is
supposed
> to be included verbatim into other documents
Ok, maybe, we can have something like 
//cut-function-start 
//cut-function-end 
This way, each such string will be unique and easy-to-find. What do you
say?

Thank you, 
Nadya Morozova
 

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Salikh Zakirov
Sent: Tuesday, October 17, 2006 9:42 PM
To: harmony-dev@incubator.apache.org
Subject: Re: "Hot to Write GC" requires improvement

First of all, I would like to make it clear
that I am *for* committing HARMONY-1881 changes.

My point was just a little bit of advertising
the tool which I personally consider the best
for the purposes of documentation authoring. 

Morozova, Nadezhda wrote:
> About concern for updating resulting HTML and not the source TXT
> for Asciidoc-generated documents: 

> However, for the How to Write a GC document, I do not think that the
> issue is big enough because the doc seems quite stable, no frequent
> changes are intended.

Personally, I don't intend adding anything just now.

But, perhaps, Xiao Feng may want to share some of his experience
of creating generational and/or parallel collectors?

> If we manage to have AsciiDoc produce XML that is valid for site
> purposes = that would be great. It would reduce the whole chain to TXT
+
> CONFIG > XML > HTML for website! I do not know AsciiDoc internals that
> well now to say whether that's possible.

Looking from the dumped config file ('asciidoc -c some.text >
some.conf'),
I see that asciidoc is configurable inside out: starting from the
configurable
syntax (you can configure what kinds of quotes are recognized as
quotes),
and through to configuring the exact output templates.

I am sure configuring it for producing XML is perfectly possible.

> Here are a couple of my personal considerations about using the tool
for
> Harmony docs:
> 
> Strong points: 
> * Asciidoc enables using code chunks by references the source file,
not
> copy=and=paste from code.
> * Asciidoc is a freeware common tool, why not use it?
> * Asciidoc gets TXT as input, so patching is very easy.
> 
> Weak points:
> * We have two technologies for writing for website now: XML directly
and
> HTML with  to add to XML. Adding a new one can be another
> option (good!) or another confusion (bad!). is the effort worth the
> goal?

Let's "vote with our feet" :)
Anyone writing new documentation picks his/her favourite tool.

> * Asciidoc formatting is unique, resembles Wiki formatting but is
> actually different - confused me when I was starting with it.

In fact, every wiki's formatting is unique. 
It never was a problem for me, as getting used to any given wiki
syntax usually took just a couple of hours.

> * Asciidoc references into the source code (to get the code snippet
> directly from the file) rely on a specific line in code - see the
> GC-howto.txt we've been discussing. For example, the comment before
the
> function to include the function body into the doc. Now, if you update
> the code, you'll probably update the comment as well - the reference
> gets broken. This does not seem much better than manually copying the
> code into the doc. Don't know how to overcome this.

In fact, this is not an asciidoc limitation, this was just the first
solution
that I came up with. There may be better ways, for example something
like
adding a explicit cut markers to the code that is supposed to be
included verbatim
into other documents
, e.g.

 // cut-function-start
 void function() {
...
 }
 // cut-function-end

It would be obvious that these things should not be touched.
And in case of major changes like function rename, the document will
need an update anyway.


-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

RE: [drlvm] A list of drlvm enhancements and limitations

[Morozova, Nadezhda]

I side with all those who suggest that we write things down on Wiki.
Grouping issues by component might also work out fine. 

Another suggestion: distinguish between Known Issues and TODOs - that
is, between bugs and non-implemented features. I think this will allow
us to see what needs to be fixed to ensure the code runs and what needs
to be done to make it run better :)

Thank you, 
Nadya Morozova
 

-Original Message-
From: Gregory Shimansky [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 17, 2006 11:18 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [drlvm] A list of drlvm enhancements and limitations

On Tuesday 17 October 2006 19:26 Rana Dasgupta wrote:
> Mikhail,
>Makes sense. BTW, we need to change the IA-64 to IPF( IA-64 is not
an
> external term ) on any posted list. IA32 to x86-32 bit and Intel 64 to
> x86-64 bit. Sorry for the typo's.

I agree with Mikhail, the list looks quite big with your contribution. I
think 
we can already start building a page which I've created [1] but didn't
write 
anything on it yet. If you want you can start creating sublinks on it
and 
submit your list in parts. I didn't have time to write down my 3
enhancement 
suggestions so the page is basically clean so far.

[1] http://wiki.apache.org/harmony/DrlvmKnownInssuesAndLimitations

> On 10/17/06, Geir Magnusson Jr. <[EMAIL PROTECTED] > wrote:
> > Mikhail Fursov wrote:
> > > Rana,
> > > the JIT list is really good. Thanks for collecting it.
> > >
> > > I propose to create a single page for DRLVM tasks and list only
> >
> > components
> >
> > > on it. And for every component from the list create another page
with
> >
> > its
> >
> > > tasks. The reason is that after Rana's post we have too much open
tasks
> >
> > for
> >
> > > a single page.
> >
> > +1

-- 
Gregory Shimansky, Intel Middleware Products Division

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

RE: "Hot to Write GC" requires improvement

[Morozova, Nadezhda]

:) thanks for appreciating the docs. This really sounds encouraging ;) 

Thank you, 
Nadya Morozova
 

-Original Message-
From: Weldon Washburn [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 17, 2006 6:03 PM
To: harmony-dev@incubator.apache.org
Subject: Re: "Hot to Write GC" requires improvement

On 10/17/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
>
> Weldon, all,
> I've a question about the GC interface (just double-checking):
> We currently have gc_cc, gc_gen, and gcv4 folders in VM, corresponding
> to three different collectors, right?


Coorect.

 Do then all use an identical API?
> do they all work exactly as the doc describes?


"Do they all work exactly as the doc describes?"  My guess is probably
not
_exactly_ as the doc describes.   But all in all, its close.   IMHO your
documentation is good enough for this stage of the project.  Note that
the
GC/JIT/VM interface will evolve as time goes on.  Thus its impossible to
have an absolutely perfect document.  Thanks for cleaning it up.

Thank you,
> Nadya Morozova
>
>
> -Original Message-
> From: Weldon Washburn [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 17, 2006 4:46 PM
> To: harmony-dev@incubator.apache.org
> Cc: [EMAIL PROTECTED]
> Subject: Re: "Hot to Write GC" requires improvement
>
> I agree with Rana's, Geir's and Salikh's comments.  One minor comment.
> Section 2 is titled, "Implementing the GC interface".  A better
> description
> might be something like, "Implementing a collector that uses the GC
> interface".
>
>
> On 10/16/06, Konovalova, Svetlana <[EMAIL PROTECTED]>
wrote:
> >
> >
> > Folks,
> >
> > I took a close look at "Hot to Write GC" [1] and created a patch for
> this
> > doc [JIRA 1881]. I fixed formatting, brushed up the code, removed
> out-dated
> > tags etc.
> > It would be great if someone can find a chance to look at the patch.
> >
> > Thanks in advance!
> >
> > [1]
> http://incubator.apache.org/harmony/subcomponents/drlvm/gc-howto.html
> > [JIRA 1881] http://issues.apache.org/jira/browse/HARMONY-1881
> >
> >
> > Cheers,
> > Sveta Konovalova
> >
> >
-
> > Terms of use : http://incubator.apache.org/harmony/mailing.html
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail:
[EMAIL PROTECTED]
> >
> >
>
>
> --
> Weldon Washburn
> Intel Middleware Products Division
>
> -
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Weldon Washburn
Intel Middleware Products Division

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

RE: "Hot to Write GC" requires improvement

[Morozova, Nadezhda]

Weldon, all, 
I've a question about the GC interface (just double-checking):
We currently have gc_cc, gc_gen, and gcv4 folders in VM, corresponding
to three different collectors, right? Do then all use an identical API?
do they all work exactly as the doc describes?

Thank you, 
Nadya Morozova
 

-Original Message-
From: Weldon Washburn [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 17, 2006 4:46 PM
To: harmony-dev@incubator.apache.org
Cc: [EMAIL PROTECTED]
Subject: Re: "Hot to Write GC" requires improvement

I agree with Rana's, Geir's and Salikh's comments.  One minor comment.
Section 2 is titled, "Implementing the GC interface".  A better
description
might be something like, "Implementing a collector that uses the GC
interface".


On 10/16/06, Konovalova, Svetlana <[EMAIL PROTECTED]> wrote:
>
>
> Folks,
>
> I took a close look at "Hot to Write GC" [1] and created a patch for
this
> doc [JIRA 1881]. I fixed formatting, brushed up the code, removed
out-dated
> tags etc.
> It would be great if someone can find a chance to look at the patch.
>
> Thanks in advance!
>
> [1]
http://incubator.apache.org/harmony/subcomponents/drlvm/gc-howto.html
> [JIRA 1881] http://issues.apache.org/jira/browse/HARMONY-1881
>
>
> Cheers,
> Sveta Konovalova
>
> -
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Weldon Washburn
Intel Middleware Products Division

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

RE: Re: "Hot to Write GC" requires improvement

[Morozova, Nadezhda]

Salikh, 
About your concern for updating resulting HTML and not the source TXT
for Asciidoc-generated documents: 
I agree that technically Sveta's approach is not "professional" :)
However, for the How to Write a GC document, I do not think that the
issue is big enough because the doc seems quite stable, no frequent
changes are intended.
We only have a couple of code snippets in the doc so the dependency on
the reference source code is not big. 

Generally, Asciidoc might be a nice tool, it's just that we don't use it
well:) The current chain that we use with it is TXT + CONFIG > XHTML >
XHTML with manual edits to fit to site settings/presentation > XML >
output HTML for website. Now, this is LONG :) 
If we manage to have AsciiDoc produce XML that is valid for site
purposes = that would be great. It would reduce the whole chain to TXT +
CONFIG > XML > HTML for website! I do not know AsciiDoc internals that
well now to say whether that's possible.
 
Here are a couple of my personal considerations about using the tool for
Harmony docs:

Strong points: 
* Asciidoc enables using code chunks by references the source file, not
copy=and=paste from code.
* Asciidoc is a freeware common tool, why not use it?
* Asciidoc gets TXT as input, so patching is very easy.

Weak points:
* We have two technologies for writing for website now: XML directly and
HTML with  to add to XML. Adding a new one can be another
option (good!) or another confusion (bad!). is the effort worth the
goal?
* Asciidoc formatting is unique, resembles Wiki formatting but is
actually different - confused me when I was starting with it.
* Asciidoc references into the source code (to get the code snippet
directly from the file) rely on a specific line in code - see the
GC-howto.txt we've been discussing. For example, the comment before the
function to include the function body into the doc. Now, if you update
the code, you'll probably update the comment as well - the reference
gets broken. This does not seem much better than manually copying the
code into the doc. Don't know how to overcome this.

Your comments are most welcome :)

Thank you, 
Nadya Morozova
 

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Salikh Zakirov
Sent: Tuesday, October 17, 2006 1:29 PM
To: harmony-dev@incubator.apache.org
Subject: Re: "Hot to Write GC" requires improvement

Svetlana,

I've looked through your changes.
Mostly they look okay, and they greatly improve the visual presentation.

Originally, GC-howto was created using AsciiDoc[1] toolchain from the
source
text file and source .cpp file. Modifying .html file directly means that
we cannot
update the document to keep it in sync with the source code.

I guess this is acceptable, since nobody is changing source code inlets
in GC-howto now,
but be warned: if anyone is to introduce source changes, it would
tedious
task to synchronize visual and content changes.

Have you tried to configure asciidoc to produce the content you want?

I will send you the version of gc-howto.txt and gc.cpp that I have,
but Nadya may have a later version, so please check with her.
Since I am not sure attachment will make it to the list, I'll send it to
you
directly. (* or to anyone else who might be interested, just ask *)

[1] http://www.methods.co.nz/asciidoc/

Konovalova, Svetlana wrote:
> Sorry about that! 
> I've created a new patch, hope it's the right one you need. Please let
> me know if you still have any problems. 
> 
> [JIRA 1881] http://issues.apache.org/jira/browse/HARMONY-1881
> 
> Cheers,
> Sveta Konovalova
> 
> -Original Message-
> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, October 17, 2006 8:50 AM
> To: harmony-dev@incubator.apache.org
> Subject: Re: "Hot to Write GC" requires improvement
> 
> The problem with the patch is that it's to the rendered output
> 
> site/xdoc/subcomponent/drlvm/gc-howto.html
> 
> when what we need is the patch to the source document
> 
> site/xdoc/subcomponent/drlvm/gc-howto-content.html
> 
> Can you add a new patch with that please?
> 
> geir
> 
> Rana Dasgupta wrote:
>> This is a good document, thanks Svetlana. Even if a lot of custom
gc's
> 
>> don't
>> get written, it helps in understanding the current collecor farmework
> and
>> how it plugs into DRLVM.
>>
>> Rana
>>
>>
>>
>>> On 10/16/06, Konovalova, Svetlana <[EMAIL PROTECTED]>
> wrote:

 Folks,

 I took a close look at "Hot to Write GC" [1] and created a patch
> for
 this doc [JIRA 1881]. I fixed formatting, brushed up the code,
> removed
 out-dated tags etc.
 It would be great if someone can find a chance to look at the
> patch.
 Thanks in advance!

 [1]

> http://incubator.apache.org/harmony/subcomponents/drlvm/gc-howto.html
 [JIRA 1881] http://issues.apache.org/jira/browse/HARMONY-1881


 Cheers,
 Sveta Konovalova


> 
> -
> Ter

FW: [doc]too many building instructions?

[Morozova, Nadezhda]

Sorry for confusion, my mailer broke some of the links. Resending: 
[1]
http://incubator.apache.org/harmony/subcomponents/classlibrary/build_cla
sslib.html 
[2] http://incubator.apache.org/harmony/quickhelp_contributors.html 
[3] and [4] seem to work normally.

Thank you, 
Nadya Morozova
 

-Original Message-
From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 17, 2006 1:26 PM
To: harmony-dev@incubator.apache.org
Subject: [doc]too many building instructions?

Folks, 

I've had a strange impression just now that we have too many building
instructions for Harmony sources: 

[1]
http://incubator.apache.org/harmony/subcomponents/classlibrary/build_cla
sslib.html Building Class Library only

[2] http://incubator.apache.org/harmony/quickhelp_contributors.htm 

[3] http://incubator.apache.org/harmony/quickhelp_users.html - building
instructions for the whole bundle (VM + Classlib), in a short and
detailed versions; the detailed version (for contributors) has specifics
for building classlib and vm in addition to common steps

[4] http://wiki.apache.org/harmony/FrontPage - startup Wiki page that
has a link to [1], a placeholder for a future page
BuildingHintsForClasslib and VMBuildTroubleshooting. The last two pages
seem to have similar intentions - show specifics/typical errors when
building code.

[5] READMEs for Classlib and for VM, with links to some of the sources
above or repetition of these sources.

 

Does this not seem like writing about actually the same thing in many
places? My suggestion on improving this would be:

1.  Remove [1], migrate unique bits (not repeated elsewhere) to [2]
or [3] as fits better.
2.  Edit [4] to replace the BuildingInstructions link from [1] to
[2], so that instructions for both classlib and vm are retrievable.
3.  Place a More Details link at [3] to [2], work to minimize
repetition between these.
4.  Name BuildingHintsForClasslib and VMBuildTroubleshooting in a
similar way to show that they are about the same thing. 

I am sorry if this all sounds confusing or if I missed/misunderstood
some things. Just trying to keep things in a minimal number of places -
for easier maintenance and browsing.

 

Cheers,

Nadya Morozova

 

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

RE: Re: "Hot to Write GC" requires improvement

[Morozova, Nadezhda]

Folks, 

Yes, I do have a newer version of the source file that produced the
GC-howto document currently on the site - see attached. 

I am not sure we actually need to sync up with the original
Asciidoc-input file. Will send a separate email with my thoughts soon.

Thank you, 
Nadya Morozova
 

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Salikh Zakirov
Sent: Tuesday, October 17, 2006 1:29 PM
To: harmony-dev@incubator.apache.org
Subject: Re: "Hot to Write GC" requires improvement

Svetlana,

I've looked through your changes.
Mostly they look okay, and they greatly improve the visual presentation.

Originally, GC-howto was created using AsciiDoc[1] toolchain from the
source
text file and source .cpp file. Modifying .html file directly means that
we cannot
update the document to keep it in sync with the source code.

I guess this is acceptable, since nobody is changing source code inlets
in GC-howto now,
but be warned: if anyone is to introduce source changes, it would
tedious
task to synchronize visual and content changes.

Have you tried to configure asciidoc to produce the content you want?

I will send you the version of gc-howto.txt and gc.cpp that I have,
but Nadya may have a later version, so please check with her.
Since I am not sure attachment will make it to the list, I'll send it to
you
directly. (* or to anyone else who might be interested, just ask *)

[1] http://www.methods.co.nz/asciidoc/

Konovalova, Svetlana wrote:
> Sorry about that! 
> I've created a new patch, hope it's the right one you need. Please let
> me know if you still have any problems. 
> 
> [JIRA 1881] http://issues.apache.org/jira/browse/HARMONY-1881
> 
> Cheers,
> Sveta Konovalova
> 
> -Original Message-
> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, October 17, 2006 8:50 AM
> To: harmony-dev@incubator.apache.org
> Subject: Re: "Hot to Write GC" requires improvement
> 
> The problem with the patch is that it's to the rendered output
> 
> site/xdoc/subcomponent/drlvm/gc-howto.html
> 
> when what we need is the patch to the source document
> 
> site/xdoc/subcomponent/drlvm/gc-howto-content.html
> 
> Can you add a new patch with that please?
> 
> geir
> 
> Rana Dasgupta wrote:
>> This is a good document, thanks Svetlana. Even if a lot of custom
gc's
> 
>> don't
>> get written, it helps in understanding the current collecor farmework
> and
>> how it plugs into DRLVM.
>>
>> Rana
>>
>>
>>
>>> On 10/16/06, Konovalova, Svetlana <[EMAIL PROTECTED]>
> wrote:

 Folks,

 I took a close look at "Hot to Write GC" [1] and created a patch
> for
 this doc [JIRA 1881]. I fixed formatting, brushed up the code,
> removed
 out-dated tags etc.
 It would be great if someone can find a chance to look at the
> patch.
 Thanks in advance!

 [1]

> http://incubator.apache.org/harmony/subcomponents/drlvm/gc-howto.html
 [JIRA 1881] http://issues.apache.org/jira/browse/HARMONY-1881


 Cheers,
 Sveta Konovalova


> 
> -
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [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]
> 
> 

How to write DRL GC
===
[EMAIL PROTECTED], [EMAIL PROTECTED]
revision 1.0


//
//  Copyright 2006 The Apache Software Foundation or its licensors, as 
applicable.
//
//  Licensed under the Apache License, Version 2.0 (the "License");
//  you may not use this file except in compliance with the License.
//  You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
//  Unless required by applicable law or agreed to in writing, software
//  distributed under the License is distributed on an "AS IS" BASIS,
//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
//  See the License for the specific language governing permissions and
//  limitations under the License.
//
//
//  Generate HTML version of this document from text source
//  and configuration file GC-howto.conf using the command
//
//  asciidoc -f GC-howto.conf --unsafe GC-howto.txt
//
//  Download Asciidoc generic distribution archive from
//
//  http://www.methods.co.nz/asciidoc/downloads.html
//
//  unpack it somewhere (e.g. /usr/local/opt/asciidoc), and
//  symlink /usr/local/opt/asciidoc/asciidoc.py to /usr/local/bin/asciidoc
//

This section provides instructions on creating a custom garbage collector 
implementation
in C++ and configuring the DRL virtual machine to use it. The section describes
the major steps of this procedure, namely: 

- Establishing the build infrastructure
- Implement

[doc]too many building instructions?

[Morozova, Nadezhda]

Folks, 

I've had a strange impression just now that we have too many building
instructions for Harmony sources: 

[1]
http://incubator.apache.org/harmony/subcomponents/classlibrary/build_cla
sslib.html Building Class Library only

[2] http://incubator.apache.org/harmony/quickhelp_contributors.htm 

[3] http://incubator.apache.org/harmony/quickhelp_users.html - building
instructions for the whole bundle (VM + Classlib), in a short and
detailed versions; the detailed version (for contributors) has specifics
for building classlib and vm in addition to common steps

[4] http://wiki.apache.org/harmony/FrontPage - startup Wiki page that
has a link to [1], a placeholder for a future page
BuildingHintsForClasslib and VMBuildTroubleshooting. The last two pages
seem to have similar intentions - show specifics/typical errors when
building code.

[5] READMEs for Classlib and for VM, with links to some of the sources
above or repetition of these sources.

 

Does this not seem like writing about actually the same thing in many
places? My suggestion on improving this would be:

1.  Remove [1], migrate unique bits (not repeated elsewhere) to [2]
or [3] as fits better.
2.  Edit [4] to replace the BuildingInstructions link from [1] to
[2], so that instructions for both classlib and vm are retrievable.
3.  Place a More Details link at [3] to [2], work to minimize
repetition between these.
4.  Name BuildingHintsForClasslib and VMBuildTroubleshooting in a
similar way to show that they are about the same thing. 

I am sorry if this all sounds confusing or if I missed/misunderstood
some things. Just trying to keep things in a minimal number of places -
for easier maintenance and browsing.

 

Cheers,

Nadya Morozova

 

RE: [doc] need help: lost classlib porting docs

[Morozova, Nadezhda]

Oh, I see. Yes, I remember about the discussion - but thanks for
pointing this out. So we're just in transition :) and I've chosen the
wrong moment to try and find the doc.

Sorry for bothering, 
Cheers, Nadya
 

-Original Message-
From: Tony Wu [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 13, 2006 5:12 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] need help: lost classlib porting docs

yes, there is a discussion already, you can refer to
http://www.mail-archive.com/harmony-dev@incubator.apache.org/msg14494.ht
ml

I think we can find it on website soon:)

On 10/13/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
> Thanks.
> But I think it would be also nice if the doc is available from the
site
> somehow, like, via a link to the index.html file. Someone might just
> want the big picture without downloading the sources. And other docs
> might want to link to this one - I know at least one such doc, the big
> VM developer's guide.
>
> Best regards,
> Nadya Morozova
>
>
> -Original Message-
> From: Tony Wu [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 13, 2006 4:57 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [doc] need help: lost classlib porting docs
>
> it generates for you when you build the classlib. so I believe you can
> find it in your local working copy.
>
> On 10/13/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
> > Folks,
> >
> > I've a problem. We used to have the class library porting
> documentation
> > generated automatically and stored in
> > enhanced/classlib/trunk/doc/vm_doc. It is not there any more. I
> vaguely
> > recollect that we had a decision to port the docs to the website. Is
> > this done? The old place does not have it and I can't find it in the
> > website ;( I must be missing something evident.
> >
> >
> >
> > Thanks,
> >
> > Nadya Morozova
> >
> >
> >
> >
> >
>
>
> --
> Tony Wu
> China Software Development Lab, IBM
>
> -
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [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]
>
>


-- 
Tony Wu
China Software Development Lab, IBM

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

RE: [doc] need help: lost classlib porting docs

[Morozova, Nadezhda]

Thanks. 
But I think it would be also nice if the doc is available from the site
somehow, like, via a link to the index.html file. Someone might just
want the big picture without downloading the sources. And other docs
might want to link to this one - I know at least one such doc, the big
VM developer's guide.

Best regards, 
Nadya Morozova
 

-Original Message-
From: Tony Wu [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 13, 2006 4:57 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] need help: lost classlib porting docs

it generates for you when you build the classlib. so I believe you can
find it in your local working copy.

On 10/13/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
> Folks,
>
> I've a problem. We used to have the class library porting
documentation
> generated automatically and stored in
> enhanced/classlib/trunk/doc/vm_doc. It is not there any more. I
vaguely
> recollect that we had a decision to port the docs to the website. Is
> this done? The old place does not have it and I can't find it in the
> website ;( I must be missing something evident.
>
>
>
> Thanks,
>
> Nadya Morozova
>
>
>
>
>


-- 
Tony Wu
China Software Development Lab, IBM

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

[doc] need help: lost classlib porting docs

[Morozova, Nadezhda]

Folks, 

I've a problem. We used to have the class library porting documentation
generated automatically and stored in
enhanced/classlib/trunk/doc/vm_doc. It is not there any more. I vaguely
recollect that we had a decision to port the docs to the website. Is
this done? The old place does not have it and I can't find it in the
website ;( I must be missing something evident.

 

Thanks,

Nadya Morozova

 

RE: [doc] no progress on patches for the website

[Morozova, Nadezhda]

Geir, 
I have a question: 
The Quick Help guides (with patches applied) now list the required and
additional tools that are needed to get and build our sources. 
Do you think we can also include some "sure-to-work configurations" that
are now discussed in thread "[general] version of gcc and other tools"?
this might serve as some guidance for users.

Best regards, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 13, 2006 1:01 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] no progress on patches for the website

I promise, they've been looked at.

But there was continuing discussion after the original submission, that 
resulted in additional patches to the same JIRA.



Konovalova, Svetlana wrote:
> Folks, 
> 
>  
> 
> I have been wondering about the patches to the website and
> 
> documentation: could somebody please take a look and apply them if
> 
> they're ok? 
> 
>  
> 
> Please go to JIRA-1730
>   to find a new
> README patch and Quick Help patches 
> 
> posted there several days ago. They are really important as they
contain
> updated info 
> 
> and can improve our website. Why not just look into them? 
> 
>  
> 
> Thanks in advance!
> 
> Cheers,
> 
> Sveta Konovalova
> 
>  
> 
> 

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

RE: FW: Images missing from webpages

[Morozova, Nadezhda]

Thanx a lot

Best regards, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 12, 2006 10:44 PM
To: harmony-dev@incubator.apache.org
Subject: Re: FW: Images missing from webpages

fixed - pushed out to site...  will be there in next few hours...

geir


Morozova, Nadezhda wrote:
> Geir, 
> I seem to have replied to a wrong address, and so the issue was not
> resolved :( could you please look below 
> 
> There's one webpage, the description of the thread manager, that has
no
> graphics displayed with it ;(
> It would be great if you found a minute to fix this.
> 
> Best regards, 
> Nadya Morozova
>  
> -----Original Message-
> From: Morozova, Nadezhda 
> Sent: Saturday, September 23, 2006 2:43 PM
> To: 'Geir Magnusson Jr (JIRA)'
> Subject: RE: [jira] Closed: (HARMONY-1520) Images missing from
webpages
> 
> Geir, 
> I haven't verified all graphics, though the random checks show that
this
> looks fine. The only remaining set of graphics missing, for the Thread
> Manager doc. The doc itself has been deployed by Tim in JIRA 1443, but
> the graphics are not there. 
> Could you please add the graphics to folder site/docs/subcomponents/
> drlvm/images - from folder /enhanced/drlvm/trunk/vm/thread/doc/images?
> 
> Best regards, 
> Nadya Morozova
>  
> 
> -Original Message-
> From: Geir Magnusson Jr (JIRA) [mailto:[EMAIL PROTECTED] 
> Sent: Friday, September 22, 2006 8:45 PM
> To: Morozova, Nadezhda
> Subject: [jira] Closed: (HARMONY-1520) Images missing from webpages
> 
>  [ http://issues.apache.org/jira/browse/HARMONY-1520?page=all ]
> 
> Geir Magnusson Jr closed HARMONY-1520.
> --
> 
> 
>> Images missing from webpages
>> 
>>
>> Key: HARMONY-1520
>> URL:
http://issues.apache.org/jira/browse/HARMONY-1520
>> Project: Harmony
>>  Issue Type: Bug
>>  Components: Website
>>Reporter: Nadya Morozova
>> Assigned To: Geir Magnusson Jr
>>
>> Images of docs migrated to the website don't display. Need to move
the
> images into the site module. 
>> suggested directory structure: 
>> site/docs
>> images/ - for general docs' images
>> site/docs/subcomponents
>>classlib/images
>>drlvm/images
>> ... - for component-specific images; images from all docs for one
> component can be there. 
> 

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

FW: Images missing from webpages

[Morozova, Nadezhda]

Geir, 
I seem to have replied to a wrong address, and so the issue was not
resolved :( could you please look below 

There's one webpage, the description of the thread manager, that has no
graphics displayed with it ;(
It would be great if you found a minute to fix this.

Best regards, 
Nadya Morozova
 
-Original Message-
From: Morozova, Nadezhda 
Sent: Saturday, September 23, 2006 2:43 PM
To: 'Geir Magnusson Jr (JIRA)'
Subject: RE: [jira] Closed: (HARMONY-1520) Images missing from webpages

Geir, 
I haven't verified all graphics, though the random checks show that this
looks fine. The only remaining set of graphics missing, for the Thread
Manager doc. The doc itself has been deployed by Tim in JIRA 1443, but
the graphics are not there. 
Could you please add the graphics to folder site/docs/subcomponents/
drlvm/images - from folder /enhanced/drlvm/trunk/vm/thread/doc/images?

Best regards, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr (JIRA) [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 22, 2006 8:45 PM
To: Morozova, Nadezhda
Subject: [jira] Closed: (HARMONY-1520) Images missing from webpages

 [ http://issues.apache.org/jira/browse/HARMONY-1520?page=all ]

Geir Magnusson Jr closed HARMONY-1520.
--


> Images missing from webpages
> 
>
> Key: HARMONY-1520
> URL: http://issues.apache.org/jira/browse/HARMONY-1520
> Project: Harmony
>  Issue Type: Bug
>  Components: Website
>Reporter: Nadya Morozova
> Assigned To: Geir Magnusson Jr
>
> Images of docs migrated to the website don't display. Need to move the
images into the site module. 
> suggested directory structure: 
> site/docs
> images/ - for general docs' images
> site/docs/subcomponents
>classlib/images
>drlvm/images
> ... - for component-specific images; images from all docs for one
component can be there. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira



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

RE: README.txt patch Was: [drlvm] NPE is thrown when the kernel tests are run on Windows at revision 448448

[Morozova, Nadezhda]

Dear all,

Please go to https://issues.apache.org/jira/browse/HARMONY-1631  to find a 
patch for README.txt. Could you please find a chance to check whether the 
information is up-to date?   
(pay special attention to KNOWN ISSUES and TODO sections) 
In this connection I'd like to ask you to:

1. Check whether we need info about the compilers described below:
 
  + Microsoft 32-bit C/C++ Compiler, version 7 or higher
+ Windows platform SDK
+ Microsoft Visual Studio .NET 2003 or higher
+ Intel C++ Compiler, version 9.0

2. If we really need the aforementioned compilers, should we mention the
following:

3.7 You can switch between the different compilers and modes by using 
the environment variables, as follows:
   
On Windows*: |  On Linux*:
-+--
MSVC compiler : set CXX=msvc   # |  N/A 
Intel(R) compiler : set CXX=icl  |  export CXX=icc 
GCC compiler  : N/A  |  export CXX=gcc 
etc



3. Is this still a dependency for Linux?
   
   libxml2 package

4. Do we really need all stuff specified as additional (section 2.TOOLS AND   
ENVIRONMENT VARIABLES REQUIRED FOR THE BUILD)?

Your suggestions/comments/ideas are very welcome. :)

Best regards, 
Nadya Morozova

 
-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 06, 2006 1:18 PM
To: harmony-dev@incubator.apache.org
Subject: Re: README.txt patch Was: [drlvm] NPE is thrown when the kernel tests 
are run on Windows at revision 448448

I was looking at the patch, and think we should just chuck the whole
README.txt, salvage what's good, put it on the website, and put a
pointer in the README.txt to the website.

geir


Morozova, Nadezhda wrote:
> Thanks for the fix, Alexei. I think this is a good start for updating the 
> README. 
> I've looked at the current version, and many other things are out-of-date 
> (such as ij as the name of our executable). Some things are also duplicated - 
> we now have the nice Quick Help pages for users [1] and developers [2]. As I 
> see it, the Quick Start you've been referring to roughly matches [1], whereas 
> [2] is for those who have to 'read this README and follow building 
> instructions to the point.' :) 
> 
> I suggest that we edit the README file more to improve it. What do you think? 
> Do you think we can use JIRA 1730 for these changes? 
> 
> [1] http://incubator.apache.org/harmony/quickhelp_users.html 
> [2] http://incubator.apache.org/harmony/quickhelp_contributors.html 
> 
> Best regards, 
> Nadya Morozova
>  
> -Original Message-----
> From: Fedotov, Alexei A 
> Sent: Friday, October 06, 2006 12:23 AM
> To: Morozova, Nadezhda
> Cc: harmony-dev@incubator.apache.org
> Subject: README.txt patch Was: [drlvm] NPE is thrown when the kernel tests 
> are run on Windows at revision 448448
> 
> BTW,
> I really enjoyed the last item of the "Quick Start" section:
> 
>> 7. If building the DRLVM fails, read this README and follow building 
>> instructions to the point.
> 
> A hardcore programmer can loop infinitely here. :-)
> 
> With best regards,
> Alexei Fedotov,
> Intel Middleware Products Division
> 
>> -Original Message-
>> From: Fedotov, Alexei A
>> Sent: Friday, October 06, 2006 12:20 AM
>> To: =SMTP:[EMAIL PROTECTED]
>> Cc: harmony-dev@incubator.apache.org
>> Subject: RE: [drlvm] NPE is thrown when the kernel tests are run on Windows
>> at revision 448448
>>
>> Hi, Nadya,
>>
>> I tried to build DRLVM, faced the issue from the thread below, and filed a
>> JIRA issue: https://issues.apache.org/jira/browse/HARMONY-1730. Does the
>> patch worth to be applied to the README.txt?
>>
>> With best regards,
>> Alexei Fedotov,
>> Intel Middleware Products Division
>>
>>> -Original Message-
>>> From: Spark Shen [mailto:[EMAIL PROTECTED]
>>> Sent: Friday, September 22, 2006 9:56 AM
>>> To: harmony-dev@incubator.apache.org
>>> Subject: Re: [drlvm] NPE is thrown when the kernel tests are run on
>> Windows
>>> at revision 448448
>>>
>>> Thank you, I am trying :-).
>>>
>>> 2006/9/22, Vladimir Gorr <[EMAIL PROTECTED]>:
>>>> On 9/22/06, Spark Shen <[EMAIL PROTECTED]> wrote:
>>>>> Vladimir Gorr 写道:
>>>>>> When I roll away the latest changes for Character.java (H-1500
>>>> *Refactor
>>>>>> some methods in java.lang.Character*)
>>>>>> this issue disappears. It mean

RE: README.txt patch Was: [drlvm] NPE is thrown when the kernel tests are run on Windows at revision 448448

[Morozova, Nadezhda]

+1
PS: we have a pointer to README, but it goes into SVN. I don't see anything 
wrong with that - there should be some docs with sources.

Best regards, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 06, 2006 1:18 PM
To: harmony-dev@incubator.apache.org
Subject: Re: README.txt patch Was: [drlvm] NPE is thrown when the kernel tests 
are run on Windows at revision 448448

I was looking at the patch, and think we should just chuck the whole
README.txt, salvage what's good, put it on the website, and put a
pointer in the README.txt to the website.

geir


Morozova, Nadezhda wrote:
> Thanks for the fix, Alexei. I think this is a good start for updating the 
> README. 
> I've looked at the current version, and many other things are out-of-date 
> (such as ij as the name of our executable). Some things are also duplicated - 
> we now have the nice Quick Help pages for users [1] and developers [2]. As I 
> see it, the Quick Start you've been referring to roughly matches [1], whereas 
> [2] is for those who have to 'read this README and follow building 
> instructions to the point.' :) 
> 
> I suggest that we edit the README file more to improve it. What do you think? 
> Do you think we can use JIRA 1730 for these changes? 
> 
> [1] http://incubator.apache.org/harmony/quickhelp_users.html 
> [2] http://incubator.apache.org/harmony/quickhelp_contributors.html 
> 
> Best regards, 
> Nadya Morozova
>  
> -Original Message-----
> From: Fedotov, Alexei A 
> Sent: Friday, October 06, 2006 12:23 AM
> To: Morozova, Nadezhda
> Cc: harmony-dev@incubator.apache.org
> Subject: README.txt patch Was: [drlvm] NPE is thrown when the kernel tests 
> are run on Windows at revision 448448
> 
> BTW,
> I really enjoyed the last item of the "Quick Start" section:
> 
>> 7. If building the DRLVM fails, read this README and follow building 
>> instructions to the point.
> 
> A hardcore programmer can loop infinitely here. :-)
> 
> With best regards,
> Alexei Fedotov,
> Intel Middleware Products Division
> 
>> -Original Message-
>> From: Fedotov, Alexei A
>> Sent: Friday, October 06, 2006 12:20 AM
>> To: =SMTP:[EMAIL PROTECTED]
>> Cc: harmony-dev@incubator.apache.org
>> Subject: RE: [drlvm] NPE is thrown when the kernel tests are run on Windows
>> at revision 448448
>>
>> Hi, Nadya,
>>
>> I tried to build DRLVM, faced the issue from the thread below, and filed a
>> JIRA issue: https://issues.apache.org/jira/browse/HARMONY-1730. Does the
>> patch worth to be applied to the README.txt?
>>
>> With best regards,
>> Alexei Fedotov,
>> Intel Middleware Products Division
>>
>>> -Original Message-
>>> From: Spark Shen [mailto:[EMAIL PROTECTED]
>>> Sent: Friday, September 22, 2006 9:56 AM
>>> To: harmony-dev@incubator.apache.org
>>> Subject: Re: [drlvm] NPE is thrown when the kernel tests are run on
>> Windows
>>> at revision 448448
>>>
>>> Thank you, I am trying :-).
>>>
>>> 2006/9/22, Vladimir Gorr <[EMAIL PROTECTED]>:
>>>> On 9/22/06, Spark Shen <[EMAIL PROTECTED]> wrote:
>>>>> Vladimir Gorr 写道:
>>>>>> When I roll away the latest changes for Character.java (H-1500
>>>> *Refactor
>>>>>> some methods in java.lang.Character*)
>>>>>> this issue disappears. It means a clue is here.
>>>>> Sorry for the late reply. JIRA 1500 is due to discussion [1] on the
>> dev
>>>>> mailing list.
>>>>>
>>>>> I can not build DRLVM on my desktop. (Windows XP, RI JDK1.5.0, ant
>>>>> 1.6.5). So I could not reproduce the bug
>>>>> The prompted error message is:
>>>>> C:\spark\drlvm\trunk\build\make\build.xml:238: The following error
>>>>> occurred while executing this line:
>>>>> C:\spark\drlvm\trunk\build\make\setup.xml:289: The following error
>>>>> occurred while executing this line:
>>>>> C:\spark\drlvm\trunk\build\make\setup.xml:291: The following error
>>>>> occurred while executing this line:
>>>>> C:\spark\drlvm\trunk\build\make\setup.xml:462: Warning: Could not find
>>>>> file
>>>>> C:\spark\drlvm\trunk\build\make\no_settings_in_config_or_environment
>> to
>>>>> copy.
>>>>>
>>>>> This is the first time I build DRLVM, would you give me some hint
>> about
>>>>> this error message.
>>>>
>>>>

RE: README.txt patch Was: [drlvm] NPE is thrown when the kernel tests are run on Windows at revision 448448

[Morozova, Nadezhda]

Thanks for the fix, Alexei. I think this is a good start for updating the 
README. 
I've looked at the current version, and many other things are out-of-date (such 
as ij as the name of our executable). Some things are also duplicated - we now 
have the nice Quick Help pages for users [1] and developers [2]. As I see it, 
the Quick Start you've been referring to roughly matches [1], whereas [2] is 
for those who have to 'read this README and follow building instructions to the 
point.' :) 

I suggest that we edit the README file more to improve it. What do you think? 
Do you think we can use JIRA 1730 for these changes? 

[1] http://incubator.apache.org/harmony/quickhelp_users.html 
[2] http://incubator.apache.org/harmony/quickhelp_contributors.html 

Best regards, 
Nadya Morozova
 
-Original Message-
From: Fedotov, Alexei A 
Sent: Friday, October 06, 2006 12:23 AM
To: Morozova, Nadezhda
Cc: harmony-dev@incubator.apache.org
Subject: README.txt patch Was: [drlvm] NPE is thrown when the kernel tests are 
run on Windows at revision 448448

BTW,
I really enjoyed the last item of the "Quick Start" section:

> 7. If building the DRLVM fails, read this README and follow building 
> instructions to the point.

A hardcore programmer can loop infinitely here. :-)

With best regards,
Alexei Fedotov,
Intel Middleware Products Division

>-Original Message-
>From: Fedotov, Alexei A
>Sent: Friday, October 06, 2006 12:20 AM
>To: =SMTP:[EMAIL PROTECTED]
>Cc: harmony-dev@incubator.apache.org
>Subject: RE: [drlvm] NPE is thrown when the kernel tests are run on Windows
>at revision 448448
>
>Hi, Nadya,
>
>I tried to build DRLVM, faced the issue from the thread below, and filed a
>JIRA issue: https://issues.apache.org/jira/browse/HARMONY-1730. Does the
>patch worth to be applied to the README.txt?
>
>With best regards,
>Alexei Fedotov,
>Intel Middleware Products Division
>
>>-Original Message-
>>From: Spark Shen [mailto:[EMAIL PROTECTED]
>>Sent: Friday, September 22, 2006 9:56 AM
>>To: harmony-dev@incubator.apache.org
>>Subject: Re: [drlvm] NPE is thrown when the kernel tests are run on
>Windows
>>at revision 448448
>>
>>Thank you, I am trying :-).
>>
>>2006/9/22, Vladimir Gorr <[EMAIL PROTECTED]>:
>>>
>>> On 9/22/06, Spark Shen <[EMAIL PROTECTED]> wrote:
>>> >
>>> > Vladimir Gorr 写道:
>>> > > When I roll away the latest changes for Character.java (H-1500
>>> *Refactor
>>> > > some methods in java.lang.Character*)
>>> > > this issue disappears. It means a clue is here.
>>> > Sorry for the late reply. JIRA 1500 is due to discussion [1] on the
>dev
>>> > mailing list.
>>> >
>>> > I can not build DRLVM on my desktop. (Windows XP, RI JDK1.5.0, ant
>>> > 1.6.5). So I could not reproduce the bug
>>> > The prompted error message is:
>>> > C:\spark\drlvm\trunk\build\make\build.xml:238: The following error
>>> > occurred while executing this line:
>>> > C:\spark\drlvm\trunk\build\make\setup.xml:289: The following error
>>> > occurred while executing this line:
>>> > C:\spark\drlvm\trunk\build\make\setup.xml:291: The following error
>>> > occurred while executing this line:
>>> > C:\spark\drlvm\trunk\build\make\setup.xml:462: Warning: Could not find
>>> > file
>>> > C:\spark\drlvm\trunk\build\make\no_settings_in_config_or_environment
>to
>>> > copy.
>>> >
>>> > This is the first time I build DRLVM, would you give me some hint
>about
>>> > this error message.
>>>
>>>
>>> It seems you didn't run the *build.bat update* before starting the
>build.
>>>
>>> We need to run the following steps (sorry if you're aware about this):
>>>
>>> - svn checkout classlib
>>> - svn checkout drlvm
>>> - build classlib (cd classlib/trunk; ant fetch-depend; ant)
>>> - cd drlvm/trunk/build
>>> - build.bat update (you need to slightly some time here :-) )
>>> - build.bat
>>>
>>> Thanks,
>>> Vladimir.
>>>
>>>
>>> [1]
>>> >
>>> >
>>> http://mail-archives.apache.org/mod_mbox/incubator-harmony-
>>dev/200609.mbox/[EMAIL PROTECTED]
>.
>>com%3e
>>> > Best regards
>>> >
>>> > >
>>> > > Gang, it'd be not bad to run DRLVM testing for any commits to SVN
>>> > > repository.
>>> > > Otherwise we will be very hard to catch any errors like this. Any
&

RE: [doc] new "Getting Started" guides

[Morozova, Nadezhda]

... My two cents: 

> The path to a component
> should end with component's status info - ideally it should give the
newbie
> enough info not to search though harmony-dev mail archive or JIRA at
all. 
Good point, but am not sure we're ready for it just now. I haven't found
nice wiki pages for each modules/components. Things are sometimes quite
chaotic ;(
> Yes, wiki pages are good but I think we need more. What the
component's 
> home page should contain? From my point of view it should contain the 
> following:
> 1) Doc: just brief overview and pointers to spec., docs, user's guides
Again, nice idea, but not sure this is workable at the moment. We only
have >5 docs for API modules + ~3 DRLVM components + a couple more misc
docs.  
Do you think we can have sort of table in Classlib and VM component
pages: a list of modules with pointers to specs + Harmony-specific docs
+ status (done/missing/in progress/see JIRA/). This can give a pretty
clear picture of where we are :) 

> 2) Work with the component: how to build, deploy with Harmony JRE (or
> another JRE if possible) and run with apps.
Would that not be very similar (except for paths and similar) for the
majority of components? Don't think we need how-to build for each. 

> 3) Status: in progress, no activity or done (that I mean by saying
> "released", sorry for confusion)
Very important info. We have
http://incubator.apache.org/harmony/roadmap.html where major issues can
be listed, but probably component-wise info can also help. However, I am
not sure this is appropriate for newbies. Before deciding how they can
contribute, they'd rather have the code and run it. Also, this info can
be on Wiki page, where actual discussions/decisions run.

> 4) Open issues: info from JIRA (we can fetch issues related only to
the
> component from JIRA)
Can this be automated, at least to an extent? JIRAs seem to be a very
dynamic system. Otherwise, to keep the component page up-to-date and
with JIRA numbers would require frequent changes to the website. 

> 5) Mailing list: I think we should let the newbie to be aware only
about
> exact part of the project.
Specifying keywords by which to search on the mailing list? 


Best regards, 
Nadya Morozova
 

-Original Message-
From: Stepan Mishura [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 29, 2006 1:01 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] new "Getting Started" guides

On 9/28/06, Geir Magnusson Jr. wrote:
>
> 
> >
> > For example, what the problem with releasing  'keytool' or 'beans
> > framework'?
> > Why these parts should wait until we complete full toolset of
> > classlib?
>
> Maybe the problem is a simple confusion over the word "release". What
> do you mean here?  We'd have a download called "harmony-ketool-
> v1.0.tar.gz"?  I'm guessing that this isn't what you mean.  Sorry for
> me being dense :)


Yes, you are right about confusing "release" word. Let's forget about it
and
start from the beginning. My point is that we should give clear message
to a
newbie that the project consists of independent parts and we should
provide
the newbie with a shortest path to a part where the newbie want to
contribute.

For example, 3 steps:
Apache Harmony Home page
->Getting Started For Contributors page
-> Component's homepage

The path shouldn't lead to nowhere, like saying: go to the dev-mail
archive
or JIRA and search for [classlib][]. The path to a
component
should end with component's status info - ideally it should give the
newbie
enough info not to search though harmony-dev mail archive or JIRA at
all. At
minimum the path should lead the newbie to the component's wiki page.
Yes,
wiki pages are good but I think we need more. What the component's home
page
should contain? From my point of view it should contain the following:
1) Doc: just brief overview and pointers to spec., docs, user's guides
2) Work with the component: how to build, deploy with Harmony JRE (or
another JRE if possible) and run with apps.
3) Status: in progress, no activity or done (that I mean by saying
"released", sorry for confusion)
4) Open issues: info from JIRA (we can fetch issues related only to the
component from JIRA)
5) Mailing list: I think we should let the newbie to be aware only about
exact part of the project.
6) Wiki page

For example, the newbie may be interesting in contributing to BEANS and
don't want to receive tons of messages about VM. We may let message pass
from component's mailing list to common mailing list. (Even more we may
add
required prefix to subject automatically, for example, "problems with
Introspector" => "[classlib][beans] problems with Introspector")

Does this make sense?

>
> >
> >
> >> I think we need to continue to focus on our primary goal, java SE.
> >> I've also been concerned about having "subprojects" that are too
> >> independent, creating sub-communities.  I think that should be
> >> avoided at all cost.  Sure, we each have our focus and
> >> specialization, but 

[website][doc] please fix wrong link to the developer's guide

[Morozova, Nadezhda]

Hi,

 

There's a little glitch in website: DRLVM page links into SVN for the
developer's guide though the site directory has the correct file.

Could somebody please apply the fix attached to JIRA 1631
https://issues.apache.org/jira/browse/HARMONY-1631?

 

Nadya Morozova

RE: [classlib][doc]Recommend to remove trunk\doc\kernel_doc and trunk\doc\vm_doc from svn repository.

[Morozova, Nadezhda]

Do you think we can have the docs built on a regular basis (like, a
script that triggers Doxygen build say 2 times a week + on demand to
push updates if needed) and resulting docs stored on the website?
This way, you don't have SVN versioning for auto-generated content and
keep info available for all.

Best regards, 
Nadya Morozova
 

-Original Message-
From: Mark Hindess [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 28, 2006 1:08 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib][doc]Recommend to remove trunk\doc\kernel_doc and
trunk\doc\vm_doc from svn repository. 


This has been a problem for some time - I recall commenting out the call
to an ant target that cleaned that svn-checked out documentation.

If we are going to remove them, then I think we need to add them to the
website and ensure we update them regularly.  (So that they exist in a
form we can link to - I recall seeing links to the versions in svn in
the past.)

Regards,
 Mark.

On 28 September 2006 at 16:30, Paulex Yang <[EMAIL PROTECTED]>
wrote:
> Leo Li wrote:
> > Hi, all:
> > I have fixed the script to generate vm_doc but there is a
problem: 
> > the
> > newly generated vm_doc will override the original one which is under

> > control
> > of svn. Thus it will lead to build failure since vm_doc lacks from
the
> > perspective of svn. 
> LOL, is it a problem of build script?
> > Since the content under the directories
> > of  trunk\doc\kernel_doc and trunk\doc\vm_doc can be generated 
> > accordingly,
> > I recommend to remove them from svn control as the doc of classlib
does.
> >
> Hmm...just had a look at the classlib/trunk/doc directory, I agree
that 
> current structure is interesting, there are three config files for 
> Doxygen: kernel/kernel.cfg, classlib/classlib.cfg and 
> vminterface/natives.cfg(I guess, for kernel class, classlib and native

> vmi respectively), while only two directories with Doxygen genereated 
> documents: kernel_doc and vm_doc. IMHO, there is no reason to put the 
> Doxygen generated files into SVN, which just like .class compiled by 
> javac. I vote to remove the two directories, and keep the config files

> only. And, maybe we can add a "build-doc" target in the 
> classlib/trunk/build.xml to make document creation more handy.
> 
> -- 
> Paulex Yang
> China Software Development Lab
> IBM
> 
> 
> 
> -
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [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]

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

RE: [classlib][drlvm][doc]Recommend to remove trunk\doc\kernel_doc and trunk\doc\vm_doc from svn repository.

[Morozova, Nadezhda]

Paulex, 
I agree to your suggestions on keeping the config files for generated
docs only. As for 
>And, maybe we can add a "build-doc" target in the 
> classlib/trunk/build.xml to make document creation more handy.

I fully side with that. Moreover, I'd suggest that we add such a target
for DRLVM sources as well. JIRAs start to appear with comments brushup
for Doxygen needs (eg. JIRA 1544), so why not do it. 

Best regards, 
Nadya Morozova
 

-Original Message-
From: Paulex Yang [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 28, 2006 12:31 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib][doc]Recommend to remove trunk\doc\kernel_doc and
trunk\doc\vm_doc from svn repository.

Leo Li wrote:
> Hi, all:
> I have fixed the script to generate vm_doc but there is a problem:

> the
> newly generated vm_doc will override the original one which is under 
> control
> of svn. Thus it will lead to build failure since vm_doc lacks from the
> perspective of svn. 
LOL, is it a problem of build script?
> Since the content under the directories
> of  trunk\doc\kernel_doc and trunk\doc\vm_doc can be generated 
> accordingly,
> I recommend to remove them from svn control as the doc of classlib
does.
>
Hmm...just had a look at the classlib/trunk/doc directory, I agree that 
current structure is interesting, there are three config files for 
Doxygen: kernel/kernel.cfg, classlib/classlib.cfg and 
vminterface/natives.cfg(I guess, for kernel class, classlib and native 
vmi respectively), while only two directories with Doxygen genereated 
documents: kernel_doc and vm_doc. IMHO, there is no reason to put the 
Doxygen generated files into SVN, which just like .class compiled by 
javac. I vote to remove the two directories, and keep the config files 
only. And, maybe we can add a "build-doc" target in the 
classlib/trunk/build.xml to make document creation more handy.

-- 
Paulex Yang
China Software Development Lab
IBM



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

RE: [jira] Good issue resolution guideline (was: [classlib]volunteer to supply patches for old JIRAs)

[Morozova, Nadezhda]

+1 for Wiki. This is a more edit-friendly solution. 
I can also add a link to your Wiki page from the website - for people to
know where to look for guidelines ;) 

Best regards, 
Nadya Morozova
 

-Original Message-
From: Alexey Petrenko [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 28, 2006 11:21 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Good issue resolution guideline (was:
[classlib]volunteer to supply patches for old JIRAs)

Guys,

Since there is no additional comments on this guideline...

Let's put it somewhere.
We got two options: Harmony site and wiki.
I prefer wiki because it will be easy to edit it and I can put it
there myself :)

Thoughts?

SY, Alexey

2006/9/26, Alexey Petrenko <[EMAIL PROTECTED]>:
> I've combined all the comments again.
>
> And here is the last version. I hope... :)
>
> === cut ===
> Preface
> This guideline covers a wide range of issues but not all of them.
> If you cannot do one of the steps, then write a comment to the issue.
> Use your common sense!
>
> Issue reporter:
> 1. Explicitly state the expected behavior and the
> actual behavior of Harmony code. Use links to specs, rfcs, etc.
> 2. Try to create as small a test case as possible. A patch
> to test will be highly appreciated.
> 3. Provide max. information about steps necessary to recreate the bug.
> If a patch for the test has not been supplied, provide as much
> diagnostic information about the failure as possible (stack trace,
> failure output, expected output etc).
> 4. Remember to use issue links if applicable.
> 5. Check the issue resolution when it is committed. Add a comment.
>
> Resolution provider :) :
> Depending on the type of issue, do the following:
>
> 1. Issue is probably a non-bug difference, not a bug or invalid:
>   1.1. Discuss on the dev list.
>   1.2. Add a link to the discussion thread as a comment to issue.
> 2. Issue is a bug:
>   2.1. Notify the community that you started investigation by adding
> a comment to the issue and send a message to dev list. If you cannot
> produce a patch, add another comment with the results of your
investigation.
>   2.2. If reporter did not provide a patch to test:
>   2.2.1. Try to create a patch to test.
>   2.2.2. If you cannot produce a patch, write a comment about it.
>   2.3. Create a patch to fix the issue
>   2.3.1. Any concerns? Discuss on the dev list. Add a link to
> discussion as a comment.
>   2.4. All the pacthes (test and fix) should be relative to the
> directory where the main build.xml is:
>
https://svn.apache.org/repos/asf/incubator/harmony/enhanced/classlib/tru
nk.
> Or to the module root directory.
>   2.5. Test and fix patches should be in different files.
>   2.6. If the patch requires to add, remove or move some files in the
> repository, add the appropriate script.
>   2.6. Check that all unit tests pass.
>   2.8. If it is an application-oriented issue, check the application.
>   2.9. Remember to use issue links if applicable.
>
> Committer:
> Depending on the issue type, do:
> 1. Issue is a non-bug difference, not a bug or invalid:
> Close the issue.
> 2. Issue is a bug:
>   2.1. If a patch to test is available, apply it.
>   2.2. Check that the test fails.
>   2.3. Apply the fix for the issue.
>   2.4. Check that test succeeds now.
>   2.5. Make sure that all unit tests pass.
>   2.6. For application-oriented issues, check the application.
>   2.7. If there are problems on previous steps, post a comment to
> JIRA and let "resolution provider" to resolve.
>   2.8. Make sure that the issue reporter is happy with the resolution.
>   2.9. Add revision info into JIRA issue
> === cut ===
>


-- 
Alexey A. Petrenko
Intel Middleware Products Division

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

RE: [doc] new "Getting Started" guides

[Morozova, Nadezhda]

Yop. I meant that page. Sorry, seems my fault. 
Had to clean up cache and restart PC to see the new nice version. Issue
closed, sorry for confusion :(

Best regards, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 26, 2006 6:47 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] new "Getting Started" guides

Do you mean :

http://incubator.apache.org/harmony/documentation/documentation.html

looks ok to me... will look closely at source later

geir

On Sep 26, 2006, at 10:27 AM, Morozova, Nadezhda wrote:

> Geir,
>
> I double-checked the documentation.html page - it still has no  
> site.css
> attached and does not display nicely. :(
>
> Best regards,
> Nadya Morozova
>
>
> -Original Message-
> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 26, 2006 4:28 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [doc] new "Getting Started" guides
>
> Thanks.  Fixed.
>
> On Sep 26, 2006, at 1:54 AM, Jordan Justen wrote:
>
>> Geir,
>>
>> At http://incubator.apache.org/harmony/quickhelp_users.html,
>>
>> There is a "download page" link to,
>>  http://incubator.apache.org/harmony/download.html
>> which should be,
>>  http://incubator.apache.org/harmony/downloads.html
>>
>> -Jordan
>>
>> On 9/21/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
>>>
>>> As discussed earlier today, there are now two new "Getting Started"
>>> guides on the website, accessible from the homepage.
>>>
>>>http://incubator.apache.org/harmony/quickhelp_users.html
>>>
>>>http://incubator.apache.org/harmony/quickhelp_contributors.html
>>>
>>> There is still more work to do - for example, we need to fill in the
>>> lists of tools needed and dependencies.  (I'll add a fresh Ubuntu VM
>>> in Parallels tomorrow and work though all the deps that need to be
>>> added)
>>>
>>> Give a read, test it out, and comment...
>>>
>>> geir
>>>
>>>
>>> 

>>> -
>>> 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]
>
> -
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [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]

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

RE: [doc] new "Getting Started" guides

[Morozova, Nadezhda]

Geir, 

I double-checked the documentation.html page - it still has no site.css
attached and does not display nicely. :( 

Best regards, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 26, 2006 4:28 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] new "Getting Started" guides

Thanks.  Fixed.

On Sep 26, 2006, at 1:54 AM, Jordan Justen wrote:

> Geir,
>
> At http://incubator.apache.org/harmony/quickhelp_users.html,
>
> There is a "download page" link to,
>  http://incubator.apache.org/harmony/download.html
> which should be,
>  http://incubator.apache.org/harmony/downloads.html
>
> -Jordan
>
> On 9/21/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
>>
>> As discussed earlier today, there are now two new "Getting Started"
>> guides on the website, accessible from the homepage.
>>
>>http://incubator.apache.org/harmony/quickhelp_users.html
>>
>>http://incubator.apache.org/harmony/quickhelp_contributors.html
>>
>> There is still more work to do - for example, we need to fill in the
>> lists of tools needed and dependencies.  (I'll add a fresh Ubuntu VM
>> in Parallels tomorrow and work though all the deps that need to be
>> added)
>>
>> Give a read, test it out, and comment...
>>
>> geir
>>
>>
>> -
>> 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]

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

RE: [doc] new "Getting Started" guides

[Morozova, Nadezhda]

Folks, am I the only one seeing this? 

http://incubator.apache.org/harmony/quickhelp_contributors.html 
The page starts with the middle of the description to say "This will
checkout a directory structure that ..." with all text set to
align:center, including code snippets. Then, approximately 2 screens
below, we get the webpage heading and the real start of the web page
text, with normal alignment. 

.. this must be the Friday evening effect. 

Best regards, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 22, 2006 4:42 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] new "Getting Started" guides


On Sep 22, 2006, at 8:28 AM, Morozova, Nadezhda wrote:

> Geir,
>
> Do you think it might be easier to use Wiki as storage for all FAQs  
> like
> that for now? I mean, not all of those who help find FAQ entries have
> ever checked out the website and would be willing to make patches to a
> FAQ.xml page. Wiki is easier to use when we're accumulating info. We
> could then select the most typical and/or persistent issues and make
> them appear on the website.
> (I remember your proposal on having 2 FAQs: Wiki + website page).

Right - that's what I suggested.  We have the faq start on the  
website, and then at the bottome, like to the wikiFaq, so that people  
can just add there w/o having to do a patch.  Then harvest the good  
stuff that comes to the wikiFaq back into the website

Does that make sense?

geir

>
> Best regards,
> Nadya Morozova
>
>
> -Original Message-
> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 22, 2006 4:23 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [doc] new "Getting Started" guides
>
> btw, this isn't a bad element for the FAQ :)
>
> On Sep 22, 2006, at 3:31 AM, Mikhail Fursov wrote:
>
>> Geir,
>> Why do we need an example with "ant populate_source"  and
>> "working_*" dirs ?
>> Why just not to tell something like: the advise is to copy the
>> clean harmony
>> directories into a separate folder(e.g. harmony_mypatch)  and  
>> build it
>> there. Doing this you can avoid to do complete checkout again when
>> you need
>> to prototype a new feature.
>> ?
>>
>>
>> On 9/22/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
>>>
>>> As discussed earlier today, there are now two new "Getting Started"
>>> guides on the website, accessible from the homepage.
>>>
>>>http://incubator.apache.org/harmony/quickhelp_users.html
>>>
>>>http://incubator.apache.org/harmony/quickhelp_contributors.html
>>>
>>> There is still more work to do - for example, we need to fill in the
>>> lists of tools needed and dependencies.  (I'll add a fresh Ubuntu VM
>>> in Parallels tomorrow and work though all the deps that need to be
>>> added)
>>>
>>> Give a read, test it out, and comment...
>>>
>>> geir
>>>
>>>
>>> 

>>> -
>>> 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]
>>>
>>>
>>
>>
>> -- 
>> Mikhail Fursov
>
>
> -
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [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]
>


-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

Re: [doc] problem w/ css locally?

[Morozova, Nadezhda]

Geir, 

 

In the website, the folder docs/documentation does not seem to have a
copy of the site.css file for some reason. This way, pages
documentation.html, build_website.html and a couple of others look real
ugly. Could you please fix? 

I've verified all other pages on the website, they look just fine. 

 

thanks

Nadya Morozova,

RE: [doc] Why do we have boxes drawn around source now?

[Morozova, Nadezhda]

Looks ok. I don't think I need to verify - you're more experienced with
vsl anyway :) I'll let you know if I find an occurrence where it does
not behave as we expect it.

Best regards, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 22, 2006 4:47 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] Why do we have boxes drawn around source now? 

I think it looks good.  I just took out all the table junk so we have

#macro ( source $value)
 
$escape.getText($value.getText())
 
#end


Do you want to verify before I check it in?

geir



On Sep 22, 2006, at 8:43 AM, Geir Magnusson Jr. wrote:

>
> On Sep 22, 2006, at 8:34 AM, Morozova, Nadezhda wrote:
>
>> Geir,
>>
>> I know where the outer box comes from - site.vsl, special handling of
>>  snippets. Can send you a quick patch to remove the outer  
>> box.
>
> I'm looking at that now and have removed it.  'm just scanning the  
> site now to see what breaks when we do that...
>
> geir
>
>>
>> Best regards,
>> Nadya Morozova
>>
>>
>> -Original Message-
>> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
>> Sent: Friday, September 22, 2006 4:25 PM
>> To: harmony-dev@incubator.apache.org
>> Subject: Re: [doc] Why do we have boxes drawn around source now?
>>
>>
>> On Sep 22, 2006, at 4:04 AM, Mark Hindess wrote:
>>
>>>
>>> On 21 September 2006 at 23:15, "Geir Magnusson Jr."
>>> <[EMAIL PROTECTED]> wrote:
>>>>
>>>> On Sep 21, 2006, at 10:06 PM, Richard Liang wrote:
>>>>
>>>>> On 9/22/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
>>>>>> Is this new?  We now have boxes drawn around the shaded box on a
>>>>>>  document snippet...
>>>>>>
>>>>>
>>>>> Maybe because we now have unified site.css (HARMONY-1384[1]) to  
>>>>> make
>>>>> our pages more beautiful ;-)
>>>>
>>>> I know how they are getting there.  I don't know why...  they gotta
>>>> go...
>>>
>>> Why?  Because I guess Nadya thought they helped improve the  
>>> clarity of
>>> some pages.  (I did too so was happy to commit that change.)
>>>
>>> I didn't check every page so perhaps on some it looks bad?
>>
>> Well, there are two boxes.  There is a nice pink box that contains
>> the code, and then there is a box drawn around that on the outside...
>>
>> I like the inner box.  Looks nice and neat.  Outer box?  Not so  
>> much :)
>>
>> geir
>>
>>>
>>> -Mark.
>>>
>>>> geir
>>>>
>>>>> [1] http://issues.apache.org/jira/browse/HARMONY-1384
>>>>>
>>>>> Best regards,
>>>>> Richard
>>>>>
>>>>>> 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]
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> Richard Liang
>>>>> China Development Lab, IBM
>>>>>
>>>>> --

>>>>> --
>>
>>>>> -
>>>>> 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: harmony-dev- 
>>>> [EMAIL PROTECTED]
>>>> For additional commands, e-mail: harmony-dev-
>>>> [EMAIL PROTECTED]
>>>>
>>>
>>>
>>>
>>> 

>>> -
>>> Terms of use : http://incubator.apache.org/har

RE: [doc] new "Getting Started" guides

[Morozova, Nadezhda]

Yop, that does. I can create placeholders for both pages.

Best regards, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 22, 2006 4:42 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] new "Getting Started" guides


On Sep 22, 2006, at 8:28 AM, Morozova, Nadezhda wrote:

> Geir,
>
> Do you think it might be easier to use Wiki as storage for all FAQs  
> like
> that for now? I mean, not all of those who help find FAQ entries have
> ever checked out the website and would be willing to make patches to a
> FAQ.xml page. Wiki is easier to use when we're accumulating info. We
> could then select the most typical and/or persistent issues and make
> them appear on the website.
> (I remember your proposal on having 2 FAQs: Wiki + website page).

Right - that's what I suggested.  We have the faq start on the  
website, and then at the bottome, like to the wikiFaq, so that people  
can just add there w/o having to do a patch.  Then harvest the good  
stuff that comes to the wikiFaq back into the website

Does that make sense?

geir

>
> Best regards,
> Nadya Morozova
>
>
> -Original Message-
> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 22, 2006 4:23 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [doc] new "Getting Started" guides
>
> btw, this isn't a bad element for the FAQ :)
>
> On Sep 22, 2006, at 3:31 AM, Mikhail Fursov wrote:
>
>> Geir,
>> Why do we need an example with "ant populate_source"  and
>> "working_*" dirs ?
>> Why just not to tell something like: the advise is to copy the
>> clean harmony
>> directories into a separate folder(e.g. harmony_mypatch)  and  
>> build it
>> there. Doing this you can avoid to do complete checkout again when
>> you need
>> to prototype a new feature.
>> ?
>>
>>
>> On 9/22/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
>>>
>>> As discussed earlier today, there are now two new "Getting Started"
>>> guides on the website, accessible from the homepage.
>>>
>>>http://incubator.apache.org/harmony/quickhelp_users.html
>>>
>>>http://incubator.apache.org/harmony/quickhelp_contributors.html
>>>
>>> There is still more work to do - for example, we need to fill in the
>>> lists of tools needed and dependencies.  (I'll add a fresh Ubuntu VM
>>> in Parallels tomorrow and work though all the deps that need to be
>>> added)
>>>
>>> Give a read, test it out, and comment...
>>>
>>> geir
>>>
>>>
>>> 

>>> -
>>> 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]
>>>
>>>
>>
>>
>> -- 
>> Mikhail Fursov
>
>
> -
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [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]
>


-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

RE: [doc] problem w/ css locally?

[Morozova, Nadezhda]

Geir, 

One question: if I (or somebody else for that matter) decide to change
the site.css file, which copy in the checked-out version do I modify? 
Sorry if this sounds stupid... 

Best regards, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 22, 2006 4:39 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] problem w/ css locally?


On Sep 22, 2006, at 8:04 AM, Stefano Mazzocchi wrote:

> Geir Magnusson Jr. wrote:
>> I see Tim and Nadya  discussed this already.
>>
>> I think we want to keep it as error-free as possible...  I'm going to
>> try to just copy site.css on deployment - it means we still only
>> maintain one copy, but then offline and online is the same  
>> experience.
>
> I tend to hook the css file to an absolute http URL or use ../../
> relative locations.
>
> having a working copy that needs to be updated before every commit is
> asking for trouble.

Right - so I switched the  to be simply local, and modified  
build.xml to copy it where it's needed.  So we have extra copies in  
the doc tree, but what you see locally is what you see when deployed,  
and nothing has to be touched to go between.

geir

>
> -- 
> Stefano.
>
>
> -
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [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]

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

RE: [doc] Why do we have boxes drawn around source now?

[Morozova, Nadezhda]

Geir, 

I know where the outer box comes from - site.vsl, special handling of
 snippets. Can send you a quick patch to remove the outer box. 

Best regards, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 22, 2006 4:25 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] Why do we have boxes drawn around source now? 


On Sep 22, 2006, at 4:04 AM, Mark Hindess wrote:

>
> On 21 September 2006 at 23:15, "Geir Magnusson Jr."  
> <[EMAIL PROTECTED]> wrote:
>>
>> On Sep 21, 2006, at 10:06 PM, Richard Liang wrote:
>>
>>> On 9/22/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
 Is this new?  We now have boxes drawn around the shaded box on a
  document snippet...

>>>
>>> Maybe because we now have unified site.css (HARMONY-1384[1]) to make
>>> our pages more beautiful ;-)
>>
>> I know how they are getting there.  I don't know why...  they gotta
>> go...
>
> Why?  Because I guess Nadya thought they helped improve the clarity of
> some pages.  (I did too so was happy to commit that change.)
>
> I didn't check every page so perhaps on some it looks bad?

Well, there are two boxes.  There is a nice pink box that contains  
the code, and then there is a box drawn around that on the outside...

I like the inner box.  Looks nice and neat.  Outer box?  Not so much :)

geir

>
> -Mark.
>
>> geir
>>
>>> [1] http://issues.apache.org/jira/browse/HARMONY-1384
>>>
>>> Best regards,
>>> Richard
>>>
 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]


>>>
>>>
>>> -- 
>>> Richard Liang
>>> China Development Lab, IBM
>>>
>>> 

>>> -
>>> 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: 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]
>


-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

RE: [doc] new "Getting Started" guides

[Morozova, Nadezhda]

Geir, 

Do you think it might be easier to use Wiki as storage for all FAQs like
that for now? I mean, not all of those who help find FAQ entries have
ever checked out the website and would be willing to make patches to a
FAQ.xml page. Wiki is easier to use when we're accumulating info. We
could then select the most typical and/or persistent issues and make
them appear on the website. 
(I remember your proposal on having 2 FAQs: Wiki + website page). 

Best regards, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 22, 2006 4:23 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] new "Getting Started" guides

btw, this isn't a bad element for the FAQ :)

On Sep 22, 2006, at 3:31 AM, Mikhail Fursov wrote:

> Geir,
> Why do we need an example with "ant populate_source"  and  
> "working_*" dirs ?
> Why just not to tell something like: the advise is to copy the  
> clean harmony
> directories into a separate folder(e.g. harmony_mypatch)  and build it
> there. Doing this you can avoid to do complete checkout again when  
> you need
> to prototype a new feature.
> ?
>
>
> On 9/22/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
>>
>> As discussed earlier today, there are now two new "Getting Started"
>> guides on the website, accessible from the homepage.
>>
>>http://incubator.apache.org/harmony/quickhelp_users.html
>>
>>http://incubator.apache.org/harmony/quickhelp_contributors.html
>>
>> There is still more work to do - for example, we need to fill in the
>> lists of tools needed and dependencies.  (I'll add a fresh Ubuntu VM
>> in Parallels tomorrow and work though all the deps that need to be
>> added)
>>
>> Give a read, test it out, and comment...
>>
>> geir
>>
>>
>> -
>> 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]
>>
>>
>
>
> -- 
> Mikhail Fursov


-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

RE: [doc] Why do we have boxes drawn around source now?

[Morozova, Nadezhda]

Geir, 

That's right, we have  tag set to have a border around code
snippets. You can change it if you like. The initial border setting has
come with the drl-style presentation. 

Note: some (but not all) code snippets, like the apache license quote
presented as a text, have a border, but it is drawn using images: nice
dots in corners, grey lines at each side. Do we need these? I personally
think having a border setting is simpler, but do not insist. Anyway,
having both is not acceptable. 

Best regards, 
Nadya Morozova
 

-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 22, 2006 7:16 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [doc] Why do we have boxes drawn around source now?


On Sep 21, 2006, at 10:06 PM, Richard Liang wrote:

> On 9/22/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
>> Is this new?  We now have boxes drawn around the shaded box on a
>>  document snippet...
>>
>
> Maybe because we now have unified site.css (HARMONY-1384[1]) to make
> our pages more beautiful ;-)
>

I know how they are getting there.  I don't know why...  they gotta  
go...

geir

> [1] http://issues.apache.org/jira/browse/HARMONY-1384
>
> Best regards,
> Richard
>
>> geir
>>
>> -
>> 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]
>>
>>
>
>
> -- 
> Richard Liang
> China Development Lab, IBM
>
> -
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [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]

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