Thanks, Martin. I am very pleased that you know about the problem and plan to fix it.
Again, thanks. Leif On 11/23/05, Martin Schnabel <[EMAIL PROTECTED]> wrote: > Leif Wells wrote: > > >This isn't the first time this has happened to me, so I guess I should > >have learned. > > > >I am using ASDT 0.0.8build5 (yes, I know that there are later builds > >in subversion, but I wouldn't know where to begin to compile a Eclipse > >plug-in). > > > > > it is not fixed on cvs ... i check it just now. > i add it to my list should be fixed by friday > and compiling an eclipse plugin is a piece of cake. > just open the plugin.xml file of the editor module > (make sure u have loaded all needed projects from cvs > compiler,core,editor,help,launcher,logger,viewer,wizards and feature) > and a nice interface will open. u can export it on the overview page. > > >I was creating a project that already had code in it, code that I had > >spent all day working with to be clean enough to use inside ASDT. The > >result of creating the new project was that I had no code. > > > >I have not been able to pin down the specific conditions to recreate > >this problem, so I have not reported the bug. I thought that I'd > >mention it here (again, if someone already has) that you need to watch > >out when creating a project in a folder where you already have code. > > > >So, safety tip from Leif: make a back up. > > > >(Yes, we use subversion here. But the next step *after* creating the > >project inside Eclipse was to create a subversion repository.) > > > >Leif > > > and for that use right-click on project and select Team->Share Project. > this solution is much cleaner > > best regards > Martin Schnabel > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
