[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [virgo-dev] [libra-dev] Virgo IDE Refactoring


Naci,

Thanks for putting so much energy into this. For some clarification of how I've been looking at that particular bug, place see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=329198#c20. I think perhaps the overall scope had become too broad for that one single bug, and I also don't want to predispose where we should be putting our energies. It may be that the most low-hanging fruit or most community interest is in supporting stuff in the context of WTP deployments, in which case that should drive our efforts. I really appreciate how much Libra has been willing to extend itself in terms of taking on some of this stuff; I think for sure broadening the availability of these tools to the largest possible set of consumers is the way to go.

It occurs to be that perhaps we should have some kind of conf call -- or given our various geographic locations maybe at least a bug or Wiki to see where we see things getting distributed and divide effort and codebase accordingly. Leo and I are going to have a follow-up email about some other pieces that overlap current Virgo / Libra boundary, and now might be a good time to go through this stuff systematically.

cheers!

Miles

On 2012-03-15, at 9:52 AM, Naci Dai wrote:

Hi Libras,

I just want to add to the discussion that Miles has started earlier on
what we can generalize from Virgo Tools/IDE.  We are willing to put
some effort into this.

1) I have been mulling over how to generalize the PDE bundle
resolution mecahnsim so that it is sensitive to targeted frameworks
and that we ca have more than one targeted framework in a workspace.
I am pretty much convinced that trying change PDE Target Platform
Definitions is not the way to go.  PDE is not a BDE and should not try
to be one.

Virgo Tools adopts WTP target runtimes classpath containers, the
"Bundle Dependency" resolution mechanism.  I believe this can be moved
into Libra without much trouble.  This can be made extensible for
Framework types to provide the different methods for resolving
behavior.

2) Of course number (1)  comes with a natural prereq:  A first class
framework neutral bundle project type that understands the basics of
osgi bundles.  Too many "Bundle Project" types are not productive.
Rational Tools for Aries have one, Virgo Tools have another, of course
there is PDE Plugin Projects etc.   I suggest that we adopt a baseline
Bundle Project with "Bundle Dependency" classpath containers, and
Libra OSGi Bundle Facet.  Specific behavior should be added with
Facets (i.e. Virgo or Aries specific behavior).  Those facets can live
elsewhere.

3) To complete the pack, we can discuss adopting the Bundle Manifest
Editor from Virgo Tools.


Any thoughts?

--
Naci Dai - naci.dai@xxxxxxxxxxxxx
eteration a.s.  itu ari-1 25 maslak istanbul tr
ph: +90 212 328 0825 - fax: +90 212 328 0521
_______________________________________________
libra-dev mailing list
libra-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/libra-dev

______________________________
Miles T. Parker
Senior Engineer and Product Manager, Tasktop
Committer, Eclipse Mylyn and Virgo
Project Lead, Model Focussing Tools and AMP
skype: milestravisparker