Re: [iam-dev] Preventing classpath updates when dependent project is on

[Abel Muiño Vizcaino <amuino@xxxxxxxxx>]

You're right, during the import it is possible that several classpath  
updates might be triggered.

El 12/02/2009, a las 22:37, Carlos Sanchez escribió:

> if you import a bunch of projects you have a classpath update in all
> of them, even if the dependent ones are in error.
>
> When you fix the error, all the dependents will be refreshed, and will
> happen again if you have to fix other project
>
> unless I'm missing something
>
>
> On Thu, Feb 12, 2009 at 1:12 PM, Abel Muiño Vizcaino  
> <amuino@xxxxxxxxx> wrote:
> > What do you mean by "countless classpath updates"?
> >
> > We shouldn't be doing so many classpath updates (except when the
> > dependencies -direct or transitive- change).
> >
> > Maybe I am missing something?
> >
> > In any case, removing superfluous work gets always my +1 :D
> >
> > El 12/02/2009, a las 21:33, Carlos Sanchez escribió:
> >
> > > I was thinking that to prevent countless classpath updates we could
> > > check if any of the dependent projects are on error, and if so, just
> > > add a marker "The project x that is required by this one is in  
> > > error.
> > > Fix it first" and not trigger the classpath updates. It's what jdt
> > > does when there are build source problems.
> > >
> > > It could be configurable in the preferences.
> > >
> > > WDYT?
> > > _______________________________________________
> > > iam-dev mailing list
> > > iam-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/iam-dev
> >
> > _______________________________________________
> > iam-dev mailing list
> > iam-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/iam-dev
> _______________________________________________
> iam-dev mailing list
> iam-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/iam-dev