| Re: Launch configurations should be stored in projects [message #156398] |
Wed, 28 April 2004 18:17  |
Eclipse User |
|
|
|
Originally posted by: neil.neil.swingler.name
We share our project using Clearcase SCM. If I share a launch config and put
the .launch file in the project under version control, the other team
members don't automatically see the launch config, they have to explicitely
import it into their workspace. Not the end of the world I admit.
- Neil
From: "Darin Swanson" <Darin_Swanson@us.ibm.com>
Subject: Re: Launch configurations should be stored in projects
Date: 29 April 2004 00:58
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
> > > >
> > > >
> >
> >
>
>
|
|
|
| Re: Launch configurations should be stored in projects [message #156524 is a reply to message #156398] |
Thu, 29 April 2004 00:16  |
| Eclipse User |
|
|
|
Originally posted by: eclipse.rizzoweb.com
Neil Swingler wrote:
> We share our project using Clearcase SCM. If I share a launch config and put
> the .launch file in the project under version control, the other team
> members don't automatically see the launch config, they have to explicitely
> import it into their workspace. Not the end of the world I admit.
Strange. I've used shared launch configs before (using CVS instead of
ClearCase, but that should be irrelevant for this) and they
automatically show up when I update from the repository - I never had to
import them (I don't even know how to go about importing launch configs).
Are you using 2.1 or the 3.0 branch of Eclipse?
Eric
--
I'm all in favor of keeping dangerous weapons out of the hands of fools.
Let's start with typewriters.
|
|
|
Powered by
FUDForum. Page generated in 0.04117 seconds
Home