[forge-dev] How should plugins keep up with api updates

[Lincoln Baxter, III]

Yep, I know. I was simply saying that I was confused because it does not at
the moment.

On Thu, May 31, 2012 at 5:26 PM, Max Rydahl Andersen <
max.andersen at redhat.com> wrote:

> yes, this is not unique to eclipse (and even though eclipse have full osgi
> model under it is still a nightmare)  - and I would be really interested in
> how you would avoid plugin interdependencies at Forge going forward ?
>
> Don't you expect others to depend on each other and build on top ?
>
> /max
>
> On May 31, 2012, at 9:56 , Koen Aers wrote:
>
> > Hi Lincoln,
> >
> > Plugin dependencies could become a reality very soon. Imagine a plugin
> that adds a facet to a project that is being used by yet another plugin…
> >
> > Cheers,
> > Koen
> >
> > Op 31-mei-2012, om 08:30 heeft Lincoln Baxter, III het volgende
> geschreven:
> >
> >> Ah, you were talking about eclipse. Yes, this makes sense. It's
> painful. I was confused because Forge currently doesn't have any plugin
> dependencies.
> >>
> >> On Thu, May 31, 2012 at 2:22 AM, Thomas Frühbeck <fruehbeck at aon.at>
> wrote:
> >> Lincoln,
> >> are you one of those lucky guys who don't have to hassle regularly with
> incompatible plugins in Eclipse?
> >> Just a hint:
> >>     - I tried to install JBoss Tools 32bit into classic Eclipse 32bit
> on Win7 - it failed in the middle of installing ???
> >>     - SVN: there are two prominent plugins, incompatible, one looking
> half way like the other but handling is very different in the hard cases,
> PITA from start to end, I see myself reverting regularly to the command line
> >>     - for some time recently I couldn't update my m2e plugin because it
> carried a dependency to a something in version 1.1 which was not released
> yet ???
> >>
> >> Have a look at the different flavors Eclipse IDE bundles - to me the
> main reason for those is: plug-in (inter-) dependencies and plug-in
> management.
> >> I don't want to complain, but to me these are the everyday problems I
> face _after_ I told my boss that the fix xxx will only take an hour :-/
> (The fix itself may take 5 minutes, the rest of the day it will take to get
> the infrastructure of the project up and running again.)
> >>
> >> And then we are programmers open for the newest, latest, greatest. And
> of course any author of a plugin would want his customers to pick up the
> new functionality ASAP.
> >> So I think one core features is a stable, manageable plugin life cycle.
> >>
> >> Thomas
> >>
> >> Am 31.05.2012 07:40, schrieb Lincoln Baxter, III:
> >>> On Wed, May 30, 2012 at 6:18 PM, Burr Sutter <bsutter at redhat.com>
> wrote:
> >>> Well said Thomas - I am a great "dumb user" and plug-in dependencies
> drive me nuts.
> >>>
> >>> What do you mean by plug-in dependencies? What drives you nuts?
> >>>
> >>>
> >>
> >>
> >> _______________________________________________
> >> forge-dev mailing list
> >> forge-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/forge-dev
> >>
> >>
> >>
> >>
> >> --
> >> Lincoln Baxter, III
> >> http://ocpsoft.org
> >> "Simpler is better."
> >> _______________________________________________
> >> forge-dev mailing list
> >> forge-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/forge-dev
> >
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>



-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20120531/c7209482/attachment.html