Home » Eclipse Projects » Eclipse Platform » If I ever launch a project I can't close or delete it
| If I ever launch a project I can't close or delete it [message #19829] |
Mon, 28 April 2003 11:37  |
Eclipse User |
|
|
|
Originally posted by: bob.objfac.com
Once a project has been launched, if it is closed or deleted, any subsequent
launch fails with a "project missing" error. This is even true if the
missing project is an application and I later try to launch plugins!
This behavior appeared in the late stages of 2.1 and persists in the
released version. I reported a bug that was not reproduced at the other end,
i.e., not fixed.
This is a considerable nuisance. It means to remove a project from a
workspace (and continue working), I have to build a new workspace without
it!
Do others see this? I am hoping someone else will have a simple,
reproducible test case.
Bob
|
|
|
| Re: If I ever launch a project I can't close or delete it [message #19936 is a reply to message #19829] |
Mon, 28 April 2003 11:33  |
| Eclipse User |
|
|
|
Originally posted by: jed_anderson.us.ibm.com
Bob,
I assume this bug has to do with self-hosting Eclipse, if I'm wrong,
please ignore my next comments :).
Do you have multiple projects in your workspace? I ask because when I
self-host I usually have the ~60 Eclipse SDK plugins plus some of my own
in my workspace. When I delete a project, I simply select another
plugin and launch that one instead.
jkca
Bob Foster wrote:
> Once a project has been launched, if it is closed or deleted, any subsequent
> launch fails with a "project missing" error. This is even true if the
> missing project is an application and I later try to launch plugins!
>
> This behavior appeared in the late stages of 2.1 and persists in the
> released version. I reported a bug that was not reproduced at the other end,
> i.e., not fixed.
>
> This is a considerable nuisance. It means to remove a project from a
> workspace (and continue working), I have to build a new workspace without
> it!
>
> Do others see this? I am hoping someone else will have a simple,
> reproducible test case.
>
> Bob
>
>
|
|
|
| Re: If I ever launch a project I can't close or delete it [message #20563 is a reply to message #19936] |
Mon, 28 April 2003 18:42 |
| Eclipse User |
|
|
|
Originally posted by: bob.objfac.com
Another person who can't reproduce my problem!
I have a fair number of projects; not all the Eclipse SDK plugins but all
those my plugins depend upon, plus five or six of my own plugins, plus some
stray cats and dogs, little test projects, etc.
What happens to me is that if I delete a project that has ever been launched
the next launch of anything else will complain that it can't find the
deleted project. Not just complain but launch, but kill the launch. Not just
for projects that were involved in a dependency, but for completely
independent projects that are not even plugins. As Jimmy Durante said, "It's
disgustipatin'." ;-}
Bob
"Jed Anderson" <jed_anderson@us.ibm.com> wrote in message
news:b8jhk5$21m$1@rogue.oti.com...
> Bob,
>
> I assume this bug has to do with self-hosting Eclipse, if I'm wrong,
> please ignore my next comments :).
>
> Do you have multiple projects in your workspace? I ask because when I
> self-host I usually have the ~60 Eclipse SDK plugins plus some of my own
> in my workspace. When I delete a project, I simply select another
> plugin and launch that one instead.
>
> jkca
>
>
> Bob Foster wrote:
> > Once a project has been launched, if it is closed or deleted, any
subsequent
> > launch fails with a "project missing" error. This is even true if the
> > missing project is an application and I later try to launch plugins!
> >
> > This behavior appeared in the late stages of 2.1 and persists in the
> > released version. I reported a bug that was not reproduced at the other
end,
> > i.e., not fixed.
> >
> > This is a considerable nuisance. It means to remove a project from a
> > workspace (and continue working), I have to build a new workspace
without
> > it!
> >
> > Do others see this? I am hoping someone else will have a simple,
> > reproducible test case.
> >
> > Bob
> >
> >
>
|
|
|
| Re: If I ever launch a project I can't close or delete it [message #22192 is a reply to message #20563] |
Tue, 29 April 2003 09:48 |
| Eclipse User |
|
|
|
Originally posted by: wegener.cboenospam.com
Bob Foster wrote:
> Another person who can't reproduce my problem!
> I have a fair number of projects; not all the Eclipse SDK plugins but all
> those my plugins depend upon, plus five or six of my own plugins, plus some
> stray cats and dogs, little test projects, etc.
> What happens to me is that if I delete a project that has ever been launched
> the next launch of anything else will complain that it can't find the
> deleted project. Not just complain but launch, but kill the launch. Not just
> for projects that were involved in a dependency, but for completely
> independent projects that are not even plugins. As Jimmy Durante said, "It's
> disgustipatin'." ;-}
> Bob
> "Jed Anderson" <jed_anderson@us.ibm.com> wrote in message
> news:b8jhk5$21m$1@rogue.oti.com...
> > Bob,
> >
> > I assume this bug has to do with self-hosting Eclipse, if I'm wrong,
> > please ignore my next comments :).
> >
> > Do you have multiple projects in your workspace? I ask because when I
> > self-host I usually have the ~60 Eclipse SDK plugins plus some of my own
> > in my workspace. When I delete a project, I simply select another
> > plugin and launch that one instead.
> >
> > jkca
> >
> >
> > Bob Foster wrote:
> > > Once a project has been launched, if it is closed or deleted, any
> subsequent
> > > launch fails with a "project missing" error. This is even true if the
> > > missing project is an application and I later try to launch plugins!
> > >
> > > This behavior appeared in the late stages of 2.1 and persists in the
> > > released version. I reported a bug that was not reproduced at the other
> end,
> > > i.e., not fixed.
> > >
> > > This is a considerable nuisance. It means to remove a project from a
> > > workspace (and continue working), I have to build a new workspace
> without
> > > it!
> > >
> > > Do others see this? I am hoping someone else will have a simple,
> > > reproducible test case.
> > >
> > > Bob
> > >
> > >
> >
Have you checked the Plugins and Fragments tab of your launch config and
the Target Platform page of the Plugin Development Properties to make sure
that the old project isn't still trying to be included.
|
|
| | |
| Re: If I ever launch a project I can't close or delete it [message #26005 is a reply to message #23157] |
Thu, 01 May 2003 12:48 |
| Eclipse User |
|
|
|
Originally posted by: bob.objfac.com
Here are the steps I follow prior to seeing the bug:
1. Download new version of Eclipse.
2. Re-establish previous version templates and preferences (sometimes I
forget this step).
3. Check out plugin projects from CVS in dependency order.
4. Import binary projects from Eclipse to resolve remaining dependencies.
5. At this point, all projects build.
6. Configure PDE launcher to ignore binary projects.
7. At this point, PDE launches and runs plugin projects.
8. Later, add a new project. Can be anything. Recently it was a Java
application project (some test code).
9. Run/debug new project.
10. Close project.
11. Attempt to launch with PDE. Complains that application project is
missing.
12. Re-open project. PDE now launches. There is _no_ visible dependency on
application project.
13. Close project. PDE won't launch.
14. Write bug report.
(It's even worse if I delete the project instead of close it. I have to
build a new workspace to get running again.)
I think this problem first appeared in 2.1 RC2 or RC3.
I added the above to the bug report, FWIW.
As I recall, there was an even more horrible problem involving missing
projects in RC2 that got fixed in RC3. That had to do with spurious build
errors.
Now a question: Where the heck are these dependencies stored? I don't mean
where in the UI; you can't see them in the UI. I mean, on disk.
Bob
"Jed Anderson" <jed_anderson@us.ibm.com> wrote in message
news:b8mil3$inv$1@rogue.oti.com...
> Bob,
>
> I looked at the bug
> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=35094). You never give
> an exact path to follow to reproduce the bug. It sounds like you are
> pushing the envelope here, and I think it would help us greatly if you
> could give a detailed list of steps (like the ones Dejan gave) that you
> follow to get this error.
>
> jkca
>
> Bob Foster wrote:
> > "Dave Wegener" <wegener@cboenospam.com> wrote in message
> > news:b8lvqo$1lr$1@rogue.oti.com...
> >
> >>Have you checked the Plugins and Fragments tab of your launch config and
> >
> >
> > Sure. Not there. Even if it had been, the problem of having dependencies
> > that aren't in the workspace was fixed as a bug for 2.1.
> >
> >
> >>the Target Platform page of the Plugin Development Properties to make
sure
> >>that the old project isn't still trying to be included.
> >
> >
> > Far as I can see, Target Platform just refers to other workspaces. So
no,
> > the project isn't in the list.
> >
> > Note the project most recently causing problems was not even a plugin
> > project.
> >
> > Bob
> >
> >
>
|
|
|
| Re: If I ever launch a project I can't close or delete it [message #27178 is a reply to message #26005] |
Thu, 01 May 2003 21:43 |
| Eclipse User |
|
|
|
Originally posted by: d.wegener(spamblock).attbi.com
Is it possible that your runtime workbench (workbench location used by your
PDE launch) is the same as your development workbench (workbench that you
develop code in)?
"Bob Foster" <bob@objfac.com> wrote in message
news:b8rifh$5mu$1@rogue.oti.com...
> Here are the steps I follow prior to seeing the bug:
>
> 1. Download new version of Eclipse.
> 2. Re-establish previous version templates and preferences (sometimes I
> forget this step).
> 3. Check out plugin projects from CVS in dependency order.
> 4. Import binary projects from Eclipse to resolve remaining dependencies.
> 5. At this point, all projects build.
> 6. Configure PDE launcher to ignore binary projects.
> 7. At this point, PDE launches and runs plugin projects.
> 8. Later, add a new project. Can be anything. Recently it was a Java
> application project (some test code).
> 9. Run/debug new project.
> 10. Close project.
> 11. Attempt to launch with PDE. Complains that application project is
> missing.
> 12. Re-open project. PDE now launches. There is _no_ visible dependency on
> application project.
> 13. Close project. PDE won't launch.
> 14. Write bug report.
>
> (It's even worse if I delete the project instead of close it. I have to
> build a new workspace to get running again.)
>
> I think this problem first appeared in 2.1 RC2 or RC3.
>
> I added the above to the bug report, FWIW.
>
> As I recall, there was an even more horrible problem involving missing
> projects in RC2 that got fixed in RC3. That had to do with spurious build
> errors.
>
> Now a question: Where the heck are these dependencies stored? I don't mean
> where in the UI; you can't see them in the UI. I mean, on disk.
>
> Bob
>
> "Jed Anderson" <jed_anderson@us.ibm.com> wrote in message
> news:b8mil3$inv$1@rogue.oti.com...
> > Bob,
> >
> > I looked at the bug
> > (https://bugs.eclipse.org/bugs/show_bug.cgi?id=35094). You never give
> > an exact path to follow to reproduce the bug. It sounds like you are
> > pushing the envelope here, and I think it would help us greatly if you
> > could give a detailed list of steps (like the ones Dejan gave) that you
> > follow to get this error.
> >
> > jkca
> >
> > Bob Foster wrote:
> > > "Dave Wegener" <wegener@cboenospam.com> wrote in message
> > > news:b8lvqo$1lr$1@rogue.oti.com...
> > >
> > >>Have you checked the Plugins and Fragments tab of your launch config
and
> > >
> > >
> > > Sure. Not there. Even if it had been, the problem of having
dependencies
> > > that aren't in the workspace was fixed as a bug for 2.1.
> > >
> > >
> > >>the Target Platform page of the Plugin Development Properties to make
> sure
> > >>that the old project isn't still trying to be included.
> > >
> > >
> > > Far as I can see, Target Platform just refers to other workspaces. So
> no,
> > > the project isn't in the list.
> > >
> > > Note the project most recently causing problems was not even a plugin
> > > project.
> > >
> > > Bob
> > >
> > >
> >
>
>
|
|
| |
Goto Forum:
Current Time: Fri Jun 06 11:17:42 EDT 2025
Powered by FUDForum. Page generated in 0.05396 seconds |
Home