Re: [mdt-ocl.dev] On committing Impact Analyzer to examples

[Adolfo Sánchez-Barbudo Herrera <adolfosbh@xxxxxxxxxxxxxxxx>]

Axel,

All Right. Go ahead !!

Cheers,
Adolfo.

El 13/01/2011 21:04, Axel Uhl escribió:
> Are you suggesting I may as a first example towards the full Impact 
> Analyzer commit add the org.eclipse.ocl.examples.eventmanager bundle 
> to the examples feature?
>
> Best,
> -- Axel
>
> On 1/10/2011 1:42 PM, Adolfo Sánchez-Barbudo Herrera wrote:
> > Axel,
> >
> > Regarding your build concern as soon as your plugins are included in the
> > org.eclipse.ocl.examples feature, the code will properly be built and
> > available in our produced artifacts (p2 repo, zips, etc )
> >
> > Cheers,
> > Adolfo
> > El 06/01/2011 7:16, Ed Willink escribió:
> > > Hi Axel
> > >
> > > [Please keep discussions public, whenever politic.]
> > >
> > > You may find that there aspects of the wiki that need debugging.
> > >
> > > The intent of the PSF structure is to have a small PSF advertised on
> > > the project page that gives basic projects and access to all the other
> > > PSFs. In principle you are adding plugins to examples and tests.
> > > Examples has got quite big; there might be a case for partitioning it.
> > >
> > > The examples feature too has got quite big. It could be sensible to
> > > have sub-features for IA and pivot/editors.
> > >
> > > build.xml only needs changing if the builds have irregular aspects
> > > (e.g auto-generation of the test models).
> > >
> > > ocl.map and build.properties control the old Dash Athena build and
> > > were the only files that needed changing.
> > >
> > > I have not looked at how the replacement Buckminster build works. 
> > > Adolfo?
> > >
> > > A reminder: Modeling projects are migrating to Buckminster and Git. We
> > > decided to allow EGit to mature a little, so that we will switch
> > > immediately after the Indigo release.
> > >
> > > Regards
> > >
> > > Ed
> > >
> > > On 05/01/2011 22:34, Axel Uhl wrote:
> > > > Hi Ed,
> > > >
> > > > it seems I'm close to be able to commit the IA now technically. This
> > > > now brings me to the more logical aspects of such a large commit.
> > > >
> > > > What do I have to observe about the releng / build / test
> > > > infrastructure? I think I've read the existing docs in the Wiki but
> > > > may have missed the part about central test / build. For example,
> > > > would I add something to releng/maps/ocl.map for bundles added in the
> > > > examples/ area? Any .psf files to update? Any build.xml magic? Any
> > > > feature.xml, e.g., the one under org.eclipse.ocl.examples.feature?
> > > >
> > > > I started tonight by committing the event manager functionality which
> > > > is the basis for anything Impact Analyzer-related. It would be a nice
> > > > exercise for me as new committer to get these things included in the
> > > > central build etc.
> > > >
> > > > Thanks and best,
> > > > -- Axel
> > > >
> > > >
> > > > -----
> > > > No virus found in this message.
> > > > Checked by AVG - www.avg.com
> > > > Version: 10.0.1191 / Virus Database: 1435/3361 - Release Date: 
> > > > 01/05/11
> > > _______________________________________________
> > > 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