Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse-dev] Re: eclipse-dev digest, Vol 1 #712 - 9 msgs (Out of the Office)

I will be off site today.  If immediate assistance is needed, please
contact Emy Lopez at 545-2263.  Thank you.

>>> eclipse-dev 08/07/03 12:00 >>>

Send eclipse-dev mailing list submissions to
	eclipse-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
	http://dev.eclipse.org/mailman/listinfo/eclipse-dev
or, via email, send a message with subject or body 'help' to
	eclipse-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
	eclipse-dev-admin@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of eclipse-dev digest..."


Today's Topics:

   1. Multiple version support usage (Pascal Rapicault)
   2. [eclipse-build]Build N20030807 (Timestamp:  200308070010):Compile
errors in build (sonia_dimitrov@xxxxxxxxxx)
   3. WOLips & Eclipse on a PC (Goodbye Bill)
   4. Refactoring (Andy Choi)
   5. [eclipse-build]Build N20030807 (Timestamp: 
200308070010):Automated JUnit Testing complete.  Test failures/errors
occurred. (sonia_dimitrov@xxxxxxxxxx)
   6. Re: [jdt-dev] Refactoring (Dirk Baeumer)
   7. Re: [eclipse-build]Build N20030807 (Timestamp: 
200308070010):Compile
       errors in build (Tod Creasey)
   8. Planning Meeting Notes - August 6, 2003 (Mike Wilson)

--__--__--

Message: 1
To: eclipse-dev@xxxxxxxxxxx, equinox-dev@xxxxxxxxxxx,
	platform-core-dev@xxxxxxxxxxx
From: "Pascal Rapicault" <Pascal_Rapicault@xxxxxxxxxx>
Date: Wed, 6 Aug 2003 15:29:15 -0400
Subject: [eclipse-dev] Multiple version support usage
Reply-To: eclipse-dev@xxxxxxxxxxx

This is a multipart message in MIME format.
--=_alternative 006B0CE385256D7A_=
Content-Type: text/plain; charset="us-ascii"

As we are revamping the runtime, we were wondering about the necessity
of 
the multiple version support.
We are trying to understand the use case of the multiple version and
their 
importance.  Typical scenarios involve multiple "products" installed in 
the same Eclipse where each product supplies/requires particular
versions 
of prerequisite plugins.  For example, two products which use EMF, GEF, 
... where one requires version 1.0 and the other 2.0.  In this case the 
version requirements are incompatible and either the runtime would load 
both versions or, if multiple version support is not available, one 
version would be chosen and, as a result, one of the products would be 
disabled.

In allowing for multiple versions plugin developers must be senstive to 
the distribution and use of objects/classes from different versions of
the 
same plugin.  Typical symptoms include ClassCastExceptions where, for 
example, an instance of class Foo from one version of plugin P is passed

to someone expecting an instance of class Foo from another version of P.

To analyze your distribution of such plugins, ask yourself 
- Does your public API expose a plugin which may reasonably have multple

versions in the system? 
- Do you simply use such a plugin internally (amongst your own plugins) 
and do not expose these classes in your API? 
- Do any of my plugins require and then re-export plugins acquired from
a 
third party?

Understanding your requirements for multiple version support and
tolerance 
of the side effects will guide the support included in the Eclipse 
runtime.

Please enter any comments in the following bug report: 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=41218

        PaScaL
--=_alternative 006B0CE385256D7A_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">As we are revamping the runtime, we
were wondering about the necessity of the multiple version
support.</font>
<br><font size=2 face="sans-serif">We are trying to understand the use
case of the multiple version and their importance. &nbsp;Typical
scenarios involve multiple &quot;products&quot; installed in the same
Eclipse where each product supplies/requires particular versions of
prerequisite plugins. &nbsp;For example, two products which use EMF,
GEF, ... where one requires version 1.0 and the other 2.0. &nbsp;In this
case the version requirements are incompatible and either the runtime
would load both versions or, if multiple version support is not
available, one version would be chosen and, as a result, one of the
products would be disabled.</font>
<br>
<br><font size=2 face="sans-serif">In allowing for multiple versions
plugin developers must be senstive to the distribution and use of
objects/classes from different versions of the same plugin.
&nbsp;Typical symptoms include ClassCastExceptions where, for example,
an instance of class Foo from one version of plugin P is passed to
someone expecting an instance of class Foo from another version of
P.</font>
<br>
<br><font size=2 face="sans-serif">To analyze your distribution of such
plugins, ask yourself </font>
<br><font size=2 face="sans-serif">- Does your public API expose a
plugin which may reasonably have multple versions in the system?
&nbsp;</font>
<br><font size=2 face="sans-serif">- Do you simply use such a plugin
internally (amongst your own plugins) and do not expose these classes in
your API? </font>
<br><font size=2 face="sans-serif">- Do any of my plugins require and
then re-export plugins acquired from a third party?</font>
<br>
<br><font size=2 face="sans-serif">Understanding your requirements for
multiple version support and tolerance of the side effects will guide
the support included in the Eclipse runtime.</font>
<br>
<br><font size=2 face="sans-serif">Please enter any comments in the
following bug report: &nbsp; &nbsp; &nbsp;
&nbsp;https://bugs.eclipse.org/bugs/show_bug.cgi?id=41218</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp;
PaScaL</font>
--=_alternative 006B0CE385256D7A_=--

--__--__--

Message: 2
Date: Wed, 6 Aug 2003 22:41:52 -0600
From: sonia_dimitrov@xxxxxxxxxx
To: eclipse-dev@xxxxxxxxxxx
Subject: [eclipse-dev] [eclipse-build]Build N20030807 (Timestamp: 
200308070010):Compile errors in build
Reply-To: eclipse-dev@xxxxxxxxxxx

--1469999146.1060231312178.JavaMail.sdimitro.relengbuildserv
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Build N20030807 (Timestamp: 200308070010):  Compile errors in build. 
See attached compile logs.
--1469999146.1060231312178.JavaMail.sdimitro.relengbuildserv
Content-Type: application/octet-stream;
name="/builds/nightly/src/N-N20030807-200308070010/compilelogs/plugins/org.eclipse.ui.workbench_3.0.0/workbench.jar.bin.log"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="/builds/nightly/src/N-N20030807-200308070010/compilelogs/plugins/org.eclipse.ui.workbench_3.0.0/workbench.jar.bin.log"

----------
1. ERROR in /builds/nightly/src/plugins/org.eclipse.ui.workbench/Eclipse
UI/org/eclipse/ui/internal/decorators/DecorationScheduler.java (at line
232)
	.getDecorations(
	 ^^^^^^^^^^^^^^
The method getDecorations(Object, DecorationBuilder) in the type
LightweightDecoratorManager is not applicable for the arguments (Object,
DecorationBuilder, boolean)
----------
2. ERROR in /builds/nightly/src/plugins/org.eclipse.ui.workbench/Eclipse
UI/org/eclipse/ui/internal/decorators/DecorationScheduler.java (at line
253)
	.getDecorations(
	 ^^^^^^^^^^^^^^
The method getDecorations(Object, DecorationBuilder) in the type
LightweightDecoratorManager is not applicable for the arguments (Object,
DecorationBuilder, boolean)
----------
2 problems (2 errors)

--1469999146.1060231312178.JavaMail.sdimitro.relengbuildserv--


--__--__--

Message: 3
Date: Thu, 07 Aug 2003 02:12:44 -0400
From: Goodbye Bill <movingtomac@xxxxxxxxxxx>
To: "List: Eclipse Core" <eclipse-dev@xxxxxxxxxxx>,
	"List: WebObjects-Dev" <webobjects-dev@xxxxxxxxxxxxxxx>
Subject: [eclipse-dev] WOLips & Eclipse on a PC
Reply-To: eclipse-dev@xxxxxxxxxxx

I need to do some development on a PC and want to use Eclipse and
WOLips.  I
cannot, however, find any way to invoke the Update Manager Perspective.
I've tried going to "Help/Software Updates/Find & Install" but cannot
get
anywhere.  Even though I'm specifically browsing to WOLips, and
selecting
all of the features, nothing appears in the next window (Search
Results), so
I cannot continue.

What am I doing wrong? 


--__--__--

Message: 4
To: jdt-dev@xxxxxxxxxxx, eclipse-dev@xxxxxxxxxxx
Date: Thu, 07 Aug 2003 18:36:48 +1200 (NZST)
From: Andy Choi <sincho02@xxxxxxxxx>
Subject: [eclipse-dev] Refactoring
Reply-To: eclipse-dev@xxxxxxxxxxx

i am currently working on a project that require some refactoring to be
include with the plug-in, and the refactoring is context dependent to
the
project, and i think the refactoring component provided in eclipse can
be
use as some foundation for the project that i am working on, but i need
to
understand the refactoring currently in eclipse now, can anyone suggest
me
where about in the code is a good starting point in understanding the
how
the component works?

Thanx in advance.

Regards,

Andy.


======================================================
From Andy Choi
ID : 0102962
Alternate Email Address: andy_capcap@xxxxxxxxxxx
Mobile : 021338180
  

--__--__--

Message: 5
Date: Thu, 7 Aug 2003 00:48:17 -0600
From: sonia_dimitrov@xxxxxxxxxx
To: eclipse-dev@xxxxxxxxxxx
Subject: [eclipse-dev] [eclipse-build]Build N20030807 (Timestamp: 
200308070010):Automated JUnit Testing complete.  Test failures/errors
occurred.
Reply-To: eclipse-dev@xxxxxxxxxxx

Build N20030807 (Timestamp: 200308070010):  Automated JUnit testing is
complete.  Test failures/errors occurred in the following:  

org.eclipse.ant.tests.ui_linux.gtk
org.eclipse.ant.tests.ui_winxp
org.eclipse.jdt.debug.tests_linux.gtk
org.eclipse.jdt.debug.tests_winxp
org.eclipse.jdt.ui.tests.refactoring_linux.gtk
org.eclipse.jdt.ui.tests.refactoring_winxp
org.eclipse.jdt.ui.tests_linux.gtk
org.eclipse.jdt.ui.tests_winxp

http://download.eclipse.org/downloads/drops/N-N20030807-200308070010/testResults.php

--__--__--

Message: 6
To: jdt-dev@xxxxxxxxxxx
Cc: eclipse-dev@xxxxxxxxxxx, jdt-dev@xxxxxxxxxxx,
	jdt-dev-admin@xxxxxxxxxxx
From: Dirk Baeumer <dirk_baeumer@xxxxxxxxxx>
Date: Thu, 7 Aug 2003 11:28:25 +0200
Subject: [eclipse-dev] Re: [jdt-dev] Refactoring
Reply-To: eclipse-dev@xxxxxxxxxxx





Andy,

the refactoring API is currently internal to JDT/UI plug-in hence there
is
no documentation
available how to write your own refactoring. The only thing I can
recommend
is to look at
a specific refactoring and try to understand how it works. I would
suggest
the latest version
of self encapsulate field (it's now converted to ast rewrite). The
refactoring is located in the
package org.eclipse.jdt.internal.corext.refactoring.sef and its UI is
located in package
org.eclipse.jdt.internal.ui.refactoring.sef.

Please be aware that the refactoring framework will become API in 3.0
(see
also plan
item https://bugs.eclipse.org/bugs/show_bug.cgi?id=36943.

Dirk



                                                                        
  
             Andy Choi                                                  
  
             <sincho02@xxxxxx.                                          
  
             nz>                                                       
To 
             Sent by:                  jdt-dev@xxxxxxxxxxx,             
  
             jdt-dev-admin@ecl         eclipse-dev@xxxxxxxxxxx          
  
             ipse.org                                                  
cc 
                                                                        
  
                                                                  
Subject 
             08/07/2003 08:36          [jdt-dev] Refactoring            
  
             AM                                                         
  
                                                                        
  
                                                                        
  
             Please respond to                                          
  
             jdt-dev@eclipse.o                                          
  
                    rg                                                  
  
                                                                        
  
                                                                        
  




i am currently working on a project that require some refactoring to be
include with the plug-in, and the refactoring is context dependent to
the
project, and i think the refactoring component provided in eclipse can
be
use as some foundation for the project that i am working on, but i need
to
understand the refactoring currently in eclipse now, can anyone suggest
me
where about in the code is a good starting point in understanding the
how
the component works?

Thanx in advance.

Regards,

Andy.


======================================================
From Andy Choi
ID : 0102962
Alternate Email Address: andy_capcap@xxxxxxxxxxx
Mobile : 021338180

_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-dev



--__--__--

Message: 7
To: eclipse-dev@xxxxxxxxxxx
Subject: Re: [eclipse-dev] [eclipse-build]Build N20030807 (Timestamp: 
200308070010):Compile
 errors in build 
From: "Tod Creasey" <Tod_Creasey@xxxxxxxxxx>
Date: Thu, 7 Aug 2003 07:43:24 -0400
Reply-To: eclipse-dev@xxxxxxxxxxx

This compile error has been fixed and released to HEAD.

Tod

--__--__--

Message: 8
To: eclipse-dev@xxxxxxxxxxx
From: "Mike Wilson" <Mike_Wilson@xxxxxxxxxx>
Date: Thu, 7 Aug 2003 11:24:15 -0400
Subject: [eclipse-dev] Planning Meeting Notes - August 6, 2003
Reply-To: eclipse-dev@xxxxxxxxxxx

This is a multipart message in MIME format.
--=_alternative 005498BD85256D7B_=
Content-Type: text/plain; charset="US-ASCII"

Outreach:
- Dirk gave a talk at IBM/Austria. 
  - Title: "How to contribute to Eclipse"


----------------
Status
----------------


Core:
- RCP
  - moved to resources and runtime 3.0 codebase
  - working with running ANT in new dynamic world (and dealing with OSGi
    classloaders)
- Concurrency:
  - new code released to HEAD (not integration build yet)
  - view update problems reported last week are also found when running 
without
    the patch so they weren't introduced by the new concurrency code
- User Experience:
  - received code from update for removing the config from the workspace
  - need to code review it before release into PlatformConfiguration and

Main classes
  - looking at "default workspace location" problem....similar issues
- Misc:
  - still working on XMLPull approval for inclusion in the SDK...almost 
there

Ant:
- extension point for contributed Ant properties
- work in progress for hyperlinks & console coloring for running with 
external VM
- bug fixing

Debug:
- work in progress for external breakpoints and location verification 
using JDOM
- work in progress for generic (debug platform) watch items, with 
contributed
  delegates for value computation (per debug model)
- requested new plug-in for generic console, such that clients can use 
console
  without pre-req'ing debug plug-in
- bug fixing

Platform/JDT Text:
- bug fixing
- context views:
  - contents of Declaration and Javadoc view is computed in the
background
- added context menu showing Copy and F3 (where available)
- retarget Select All action (default: Ctrl+A)
- added preview functionality to Javadoc view
- affordance --  opportunity to press F2 is shown in Java editor hovers:
  - This is one of the first affordances shown in the UI. With more to 
come,
    this raises need for a global preference for enabling/disabling 
"learning"
    mode.
- continued work on Javadoc formatting:
  - not yet released
- continued work on share file buffers:
  - not yet released, implies the conceptual shift of allowing multiple
    partitionings on a single document with major ripple effects on
viewer
    and editor setup.

Platform Search:
  - Thomas Maeder back in ZRH, designated to assume ownership of the 
search component.


JDT UI:
- bug fixing
- worked on refactoring text edit infrastructure so that it 
  can be moved out of JDT/UI plug-in.

Help:
- proposal for partitioning help for rich platform discussed and
approved

Update:
- storing update state outside the workspace
  - patch submitted
- working on site shadowing utility that will allow administrators to 
point at
  the remote site and shadow select features on the LAN for faster
access 
(part
  of corporate control of updates item)
- bug fixes

PDE:
- JUnit integration into PDE is done and tested.
- addressed several outstanding PDE JUnit defects/enhancements.
- will be in next week's integration build.
--=_alternative 005498BD85256D7B_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Outreach:</tt></font>
<br><font size=2><tt>- Dirk gave a talk at IBM/Austria. </tt></font>
<br><font size=2><tt>&nbsp; - Title: &quot;How to contribute to
Eclipse&quot;</tt></font>
<br>
<br>
<br><font size=2><tt>----------------</tt></font>
<br><font size=2><tt>Status</tt></font>
<br><font size=2><tt>----------------</tt></font>
<br>
<br>
<br><font size=2><tt>Core:</tt></font>
<br><font size=2><tt>- RCP</tt></font>
<br><font size=2><tt>&nbsp; - moved to resources and runtime 3.0
codebase</tt></font>
<br><font size=2><tt>&nbsp; - working with running ANT in new dynamic
world
(and dealing with OSGi</tt></font>
<br><font size=2><tt>&nbsp; &nbsp; classloaders)</tt></font>
<br><font size=2><tt>- Concurrency:</tt></font>
<br><font size=2><tt>&nbsp; - new code released to HEAD (not integration
build yet)</tt></font>
<br><font size=2><tt>&nbsp; - view update problems reported last week
are
also found when running without</tt></font>
<br><font size=2><tt>&nbsp; &nbsp; the patch so they weren't introduced
by the new concurrency code</tt></font>
<br><font size=2><tt>- User Experience:</tt></font>
<br><font size=2><tt>&nbsp; - received code from update for removing the
config from the workspace</tt></font>
<br><font size=2><tt>&nbsp; - need to code review it before release into
PlatformConfiguration and Main classes</tt></font>
<br><font size=2><tt>&nbsp; - looking at &quot;default workspace
location&quot;
problem....similar issues</tt></font>
<br><font size=2><tt>- Misc:</tt></font>
<br><font size=2><tt>&nbsp; - still working on XMLPull approval for
inclusion
in the SDK...almost there</tt></font>
<br>
<br><font size=2><tt>Ant:</tt></font>
<br><font size=2><tt>- extension point for contributed Ant
properties</tt></font>
<br><font size=2><tt>- work in progress for hyperlinks &amp; console
coloring
for running with external VM</tt></font>
<br><font size=2><tt>- bug fixing</tt></font>
<br>
<br><font size=2><tt>Debug:</tt></font>
<br><font size=2><tt>- work in progress for external breakpoints and
location
verification using JDOM</tt></font>
<br><font size=2><tt>- work in progress for generic (debug platform)
watch
items, with contributed</tt></font>
<br><font size=2><tt>&nbsp; delegates for value computation (per debug
model)</tt></font>
<br><font size=2><tt>- requested new plug-in for generic console, such
that clients can use console</tt></font>
<br><font size=2><tt>&nbsp; without pre-req'ing debug
plug-in</tt></font>
<br><font size=2><tt>- bug fixing</tt></font>
<br>
<br><font size=2><tt>Platform/JDT Text:</tt></font>
<br><font size=2><tt>- bug fixing</tt></font>
<br><font size=2><tt>- context views:</tt></font>
<br><font size=2><tt>&nbsp; - contents of Declaration and Javadoc view
is computed in the background</tt></font>
<br><font size=2><tt>- added context menu showing Copy and F3 (where
available)</tt></font>
<br><font size=2><tt>- retarget Select All action (default:
Ctrl+A)</tt></font>
<br><font size=2><tt>- added preview functionality to Javadoc
view</tt></font>
<br><font size=2><tt>- affordance -- &nbsp;opportunity to press F2 is
shown
in Java editor hovers:</tt></font>
<br><font size=2><tt>&nbsp; - This is one of the first affordances shown
in the UI. With more to come,</tt></font>
<br><font size=2><tt>&nbsp; &nbsp; this raises need for a global
preference
for enabling/disabling &quot;learning&quot;</tt></font>
<br><font size=2><tt>&nbsp; &nbsp; mode.</tt></font>
<br><font size=2><tt>- continued work on Javadoc formatting:</tt></font>
<br><font size=2><tt>&nbsp; - not yet released</tt></font>
<br><font size=2><tt>- continued work on share file buffers:</tt></font>
<br><font size=2><tt>&nbsp; - not yet released, implies the conceptual
shift of allowing multiple</tt></font>
<br><font size=2><tt>&nbsp; &nbsp; partitionings on a single document
with
major ripple effects on viewer</tt></font>
<br><font size=2><tt>&nbsp; &nbsp; and editor setup.</tt></font>
<br>
<br><font size=2><tt>Platform Search:</tt></font>
<br><font size=2><tt>&nbsp; - Thomas Maeder back in ZRH, designated to
assume ownership of the search component.</tt></font>
<br>
<br>
<br><font size=2><tt>JDT UI:</tt></font>
<br><font size=2><tt>- bug fixing</tt></font>
<br><font size=2><tt>- worked on refactoring text edit infrastructure so
that it </tt></font>
<br><font size=2><tt>&nbsp; can be moved out of JDT/UI
plug-in.</tt></font>
<br>
<br><font size=2><tt>Help:</tt></font>
<br><font size=2><tt>- proposal for partitioning help for rich platform
discussed and approved</tt></font>
<br>
<br><font size=2><tt>Update:</tt></font>
<br><font size=2><tt>- storing update state outside the
workspace</tt></font>
<br><font size=2><tt>&nbsp; - patch submitted</tt></font>
<br><font size=2><tt>- working on site shadowing utility that will allow
administrators to point at</tt></font>
<br><font size=2><tt>&nbsp; the remote site and shadow select features
on the LAN for faster access (part</tt></font>
<br><font size=2><tt>&nbsp; of corporate control of updates
item)</tt></font>
<br><font size=2><tt>- bug fixes</tt></font>
<br>
<br><font size=2><tt>PDE:</tt></font>
<br><font size=2><tt>- JUnit integration into PDE is done and
tested.</tt></font>
<br><font size=2><tt>- addressed several outstanding PDE JUnit
defects/enhancements.</tt></font>
<br><font size=2><tt>- will be in next week's integration
build.</tt></font>
--=_alternative 005498BD85256D7B_=--


--__--__--

_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/eclipse-dev


End of eclipse-dev Digest


Back to the top