Same here, most of the times create a custom run configuration which uses the CVD for that. Tommaso
2011/3/22 Thilo Götz <[email protected]> > I'm all for it. This has been long missing in our > tools chain. I can't begin to count how many times > I've written/partially copied the helper class you > describe below. > > --Thilo > > On 3/22/2011 18:01, Jörn Kottmann wrote: > > Any opinions/comments on this? Otherwise I will start working on it. > > > > Jörn > > > > On 3/21/11 12:54 PM, Jörn Kottmann wrote: > >> Hi all, > >> > >> developing/testing AEs inside eclipse is cumbersome because we do not > >> have launch support for AEs. To run an AE inside eclipse a small helper > >> class must be created which can instantiate the AE, supply it with CASes > >> and maybe serialize the processed CASes again. > >> > >> To ease up this process we should have launch support which is capable > of > >> instantiating an AE (or AAE), supply it with CASes and then serialize > the CASes > >> again. The launch support should also be able to run PEARS. > >> > >> A first simple version of such a wizard could read all xmi files from > one > >> folder and write the results to another folder. > >> > >> Combined with the Cas Editor we would then have complete eclipse tooling > for > >> developing AEs, e.g. for making a simple hello world AE a user might > >> want to perform the following steps: > >> > >> 1. Write the AE, create the descriptor and type system > >> 2. Import sample texts > >> 3. View the imported texts > >> 4. Run the AE over the imported texts > >> 5. View added annotations > >> > >> Jörn > > >
