Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » Launch configurations should be stored in projects
Launch configurations should be stored in projects [message #155907] Mon, 26 April 2004 07:44 Go to next message
Eclipse UserFriend
Originally posted by: weberjn.yahoo.com

It seems that launch configurations are stored in
eclipse\workspace\.metadata\.plugins\org.eclipse.debug.core\ .launches

I think launch configurations should be part of the project, i.e. be in
the project tree.
If launch configurations contain long command line arguments, it is
cumbersome to enter them by hand. If they were part of the project, they
would be automatically imported on importing a project. Already now a
launch configuration is attached to a project, so why should it not be
part of the project?

What do you think, should I enter a bug?

Juergen
Re: Launch configurations should be stored in projects [message #155925 is a reply to message #155907] Mon, 26 April 2004 08:14 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: pascal.ibm.canada

Launch configuration can be saved and then stored in the project.
Look around in the launch configuration menu.

PaScaL

Juergen Weber wrote:
> It seems that launch configurations are stored in
> eclipse\workspace\.metadata\.plugins\org.eclipse.debug.core\ .launches
>
> I think launch configurations should be part of the project, i.e. be in
> the project tree.
> If launch configurations contain long command line arguments, it is
> cumbersome to enter them by hand. If they were part of the project, they
> would be automatically imported on importing a project. Already now a
> launch configuration is attached to a project, so why should it not be
> part of the project?
>
> What do you think, should I enter a bug?
>
> Juergen
>
>
Re: Launch configurations should be stored in projects [message #155972 is a reply to message #155925] Mon, 26 April 2004 10:44 Go to previous messageGo to next message
Eclipse UserFriend
As Pascal indicated, if you designate a launch configuration to be shared,
you can specify the location.
See the Common tab for any launch configuration.

HTH
Darins

"Pascal Rapicault" <pascal@ibm.canada> wrote in message
news:c6iu2q$qma$1@eclipse.org...
> Launch configuration can be saved and then stored in the project.
> Look around in the launch configuration menu.
>
> PaScaL
>
> Juergen Weber wrote:
> > It seems that launch configurations are stored in
> > eclipse\workspace\.metadata\.plugins\org.eclipse.debug.core\ .launches
> >
> > I think launch configurations should be part of the project, i.e. be in
> > the project tree.
> > If launch configurations contain long command line arguments, it is
> > cumbersome to enter them by hand. If they were part of the project, they
> > would be automatically imported on importing a project. Already now a
> > launch configuration is attached to a project, so why should it not be
> > part of the project?
> >
> > What do you think, should I enter a bug?
> >
> > Juergen
> >
> >
Re: Launch configurations should be stored in projects [message #156385 is a reply to message #155972] Wed, 28 April 2004 17:54 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: neil.neil.swingler.name

But even if the .launch file is stored in the project, it belongs to the
workspace which is rather unintuitive.

- Neil Swingler

"Darin Swanson" <Darin_Swanson@us.ibm.com> wrote in message
news:c6j6s6$8es$1@eclipse.org...
> As Pascal indicated, if you designate a launch configuration to be shared,
> you can specify the location.
> See the Common tab for any launch configuration.
>
> HTH
> Darins
>
> "Pascal Rapicault" <pascal@ibm.canada> wrote in message
> news:c6iu2q$qma$1@eclipse.org...
> > Launch configuration can be saved and then stored in the project.
> > Look around in the launch configuration menu.
> >
> > PaScaL
> >
> > Juergen Weber wrote:
> > > It seems that launch configurations are stored in
> > > eclipse\workspace\.metadata\.plugins\org.eclipse.debug.core\ .launches
> > >
> > > I think launch configurations should be part of the project, i.e. be
in
> > > the project tree.
> > > If launch configurations contain long command line arguments, it is
> > > cumbersome to enter them by hand. If they were part of the project,
they
> > > would be automatically imported on importing a project. Already now a
> > > launch configuration is attached to a project, so why should it not be
> > > part of the project?
> > >
> > > What do you think, should I enter a bug?
> > >
> > > Juergen
> > >
> > >
>
>
Re: Launch configurations should be stored in projects [message #156390 is a reply to message #156385] Wed, 28 April 2004 18:58 Go to previous message
Eclipse UserFriend
Sorry, I don't understand your comment?

Darins

"Neil Swingler" <neil@neil.swingler.name> wrote in message
news:c6p8qf$a4e$1@eclipse.org...
> But even if the .launch file is stored in the project, it belongs to the
> workspace which is rather unintuitive.
>
> - Neil Swingler
>
> "Darin Swanson" <Darin_Swanson@us.ibm.com> wrote in message
> news:c6j6s6$8es$1@eclipse.org...
> > As Pascal indicated, if you designate a launch configuration to be
shared,
> > you can specify the location.
> > See the Common tab for any launch configuration.
> >
> > HTH
> > Darins
> >
> > "Pascal Rapicault" <pascal@ibm.canada> wrote in message
> > news:c6iu2q$qma$1@eclipse.org...
> > > Launch configuration can be saved and then stored in the project.
> > > Look around in the launch configuration menu.
> > >
> > > PaScaL
> > >
> > > Juergen Weber wrote:
> > > > It seems that launch configurations are stored in
> > > >
eclipse\workspace\.metadata\.plugins\org.eclipse.debug.core\ .launches
> > > >
> > > > I think launch configurations should be part of the project, i.e. be
> in
> > > > the project tree.
> > > > If launch configurations contain long command line arguments, it is
> > > > cumbersome to enter them by hand. If they were part of the project,
> they
> > > > would be automatically imported on importing a project. Already now
a
> > > > launch configuration is attached to a project, so why should it not
be
> > > > part of the project?
> > > >
> > > > What do you think, should I enter a bug?
> > > >
> > > > Juergen
> > > >
> > > >
> >
> >
>
>
Previous Topic:Does the Eclipse debugger have a way to display a method's return value?
Next Topic:Plugin classpath problems, need connection to JBoss server
Goto Forum:
  


Current Time: Tue Jul 22 04:51:25 EDT 2025

Powered by FUDForum. Page generated in 0.43802 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top