Re: [mdt-ocl.dev] Fwd: Build failed in Hudson: buckminster-mdt-ocl-core-

[Axel Uhl <eclipse@xxxxxxxxxxxxxxxxxx>]

Can't seem to find anything on psf dependency declarations. It also 
seems to be specific to the team provider (CVS in our case). eGit, for 
example, so far has no support for .psf files and are only now about to 
start building such support. Something to consider during git migration...

I suggest, with a git migration pending for Indigo+1, we leave the .psf 
files as they are right now. Working, like they did before, and a few 
implicit dependencies that may need documentation in a readme.

Best,
-- Axel

On 2/12/2011 6:44 AM, Ed Willink wrote:
> Hi Axel
>
> Thanks for the examples.psf commit.
>
> The intent is that after importing all relevant PSFs, a workspace just
> works, for either another team member, or an inquisitive Eclipse user.
>
> The current structure was plausible while the number of examples was
> small and LPG was the primary tooling.
>
> The advent of Xtext may mean that we want to revise to support
> sub-workspaces effectively. Perhaps an impact.psf and an editors.psf,
> but I've not discovered how to express PSF import/dependency; indeed I
> only discovered about Working Sets from someone else's PSF. Perhaps you
> can find the PSF XML content definition and do something better;
> Googling doesn't find it for me so it may be a matter of finding the
> platform Java code.
>
> Regards
>
> Ed
>
> On 11/02/2011 23:29, Axel Uhl wrote:
> > Ed,
> >
> > I've included the Impact Analyzer + Event Manager bundles in
> > examples.psf and committed the change.
> >
> > Would you want me to extend the tests.psf as well, including the
> > impact analyzer-related test bundles?
> >
> > Best,
> > -- Axel
> >
> > On 2/11/2011 10:55 PM, Ed Willink wrote:
> > > Hi
> > >
> > > We haven't had a successful build for some time now
> > >
> > > The problem seems to be
> > >
> > > Required plug-in 'org.eclipse.jdt.junit4.runtime' could not be found.
> > >
> > > I recall that JUnit 3 and JUnit 4 coexistence required JUnit 4 bounds to
> > > be specified
> > > explicitly, two of Axel's test plugins have no version bounds. (Might
> > > have been
> > > cross-project-dev about a year ago,) I suggest adding
> > > the bounds/removing Axel's tests to get a decent build again.
> > >
> > > Axel: examples.psf does not import your plugins.
> > >
> > > My CVS changes still do not show up although Axel's do. I wonder if this
> > > is another
> > > stupid identity problem like that which prevented me hitting Build Now
> > > till my
> > > identity was recreated.
> > >
> > > Regards
> > >
> > > Ed
> > > _______________________________________________
> > > mdt-ocl.dev mailing list
> > > mdt-ocl.dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
> > _______________________________________________
> > mdt-ocl.dev mailing list
> > mdt-ocl.dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
> >
> >
> > -----
> > No virus found in this message.
> > Checked by AVG - www.avg.com
> > Version: 10.0.1204 / Virus Database: 1435/3436 - Release Date: 02/11/11
>
> _______________________________________________
> mdt-ocl.dev mailing list
> mdt-ocl.dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev