[news.eclipse.technology.equinox] Re: Meeting minutes - April 8th

["Kevin" <supreme_java_guru_1@xxxxxxxxx>]

Great. Now, without trying to take up too much space in this forum, can you
point me to how to test my workings? I am a bit new at this and while I
believe the internal compiling that occurs every time I save it seems to
show no bugs, I have no idea how to launch a new Eclipse with my parsing in
place and test it out. As I said in another thread I am used to the old
System.out.println mechanism of seeing output, so if its possible to launch
a second instance of Eclipse (or equinox which I assume is mostly eclipse at
this point?), and watch console output as I launch it to verify that at
least any one of my methods are being called, this would be great! Please
either explain to me in some more detail (offline via email if you'd prefer,
my email is listed in the cc on the enhancement you sumbitted for this
issue), or point me to some locations I can read on how to work within
equinox and test my work.

Thanks.


"Jeff McAffer" <jeff_mcaffer_REMOVE@xxxxxxxxxx> wrote in message
news:b72iia$s2d$1@xxxxxxxxxxxxxxxx
> Kevin,
>
> Yes, it matters.  This would be great.  We look forward to your input.
>
> Jeff
>
> "Kevin" <kduffey@xxxxxxxxxxxxx> wrote in message
> news:b722cq$hor$1@xxxxxxxxxxxxxxxx
> > I don't know if it matters much, but I am interested in replacing the
SAX
> > parsing of plugin.xml and fragment.xml with xml pull parsing to
hopefully
> > see an improvement in parsing speed and possibly less resource usage. I
am
> > working on that now.
> >
> > "Pascal Rapicault" <pascal_rapicault@xxxxxxxxxx> wrote in message
> > news:b71n9e$7ll$1@xxxxxxxxxxxxxxxx
> > > 11:00 AM EDT - 4/8/2003
> > >
> > > Participants:
> > >
> > > Olivier Gruber (IBM, Watson Research - NY)
> > > Woody Huang (IBM, Watson Research - NY)
> > > Keith Kimball (Lotus - Boston)
> > > Mel Martinez (Lotus - from his car ;-))
> > > Jeff McAffer (IBM, OTI Labs - Ottawa)
> > > Pascal Rapicault (IBM, OTI Labs - Ottawa)
> > > Martin (sorry did not get the spelling right) (NY)
> > >
> > > It's hard to summarize the meeting in that it has mainly been an
> > > introductory meeting to state the equinox context, present the main
work
> > > areas, and give everybody an understanding of where we are going and
in
> > > which conditions.
> > >
> > > The main talk was to state terminology and clearly separate the issues
> > that
> > > equinox addresses (see presentation for more details), and also
> understand
> > > what the interests of the different parties are.
> > >
> > > At the end of the presentation, everybody was asked to think about the
> > items
> > > they want to commit to, and give them back to the community.
> > >
> > > We already know that:
> > >
> > > - Keith is interested in plug-in "enablement"
> > > - Olivier is interested in OSGi, and API
> > > - Woody is interested in understanding the consequences
> > >   of the UI plug-in deactivation
> > > - Martin is interested in filling the alternate runtime
> > >   page with JMX info and gives us more details about his use case.
> > > - Mel is interested in API, deactivation mechanism, security, and
> > > implication of enablement/disablement on PlatformConfiguration
> > > - Pascal is interested in API, deactivation mechanism, top-level
plug-in
> > > deactivation,
> > > - Jeff is interested all aspects
> > >
> > >
> > >
> > > Action to be taken from the interested parties:
> > > ===============================================
> > > Confirm through the newsgroup or the mailing list your interest in
> > specific
> > > work items indicated on the web
> > > (see the various work areas on http://www.eclipse.org/equinox/ for
more
> > > details).
> > >
> > >
> >
> >
>
>