Home » Archived » Test and Performance Tools Platform (TPTP) » TPTP project structure
| TPTP project structure [message #69537] |
Fri, 05 May 2006 18:09  |
Eclipse User |
|
|
|
Originally posted by: user.domain.invalid
I checked out the code for TPTP and am confused about what I got,
structure-wise. I'm confused because the TPTP platform checkout got me
a folder of that name (platform), but it doesn't contain an Eclipse
project. Instead it is a folder of sub-projects, each of which would
have to be individually imported into Eclipse (I think) before I can
start building the test widgets I want.
But I see a problem with this approach because there is a folder called
features and if I open the source for TPTP monitoring, there is also a
folder called features inside there. So if I try to set up these
sub-folders as Eclipse projects, I immediately run into a name space
collision between these features folders, I can't have 2 projects both
called "features".
So how's everyone else setting these things up? I sure don't want to
have to import about 50 or more Eclipse projects, one for each
sub-folder I see, and have to rename those that have naming collisions.
The solution is obvious right? And I'm just missing it?
Rick
|
|
|
| Re: TPTP project structure [message #69557 is a reply to message #69537] |
Fri, 05 May 2006 20:29  |
 Victor Legros
Messages: 1
Registered: July 2009 |
Junior Member |
|
|
I'm sure the more experienced people might have something to add/coprrect,
but I thought I'd just send off a quick reply, since I have some time.
You are correct in that the "platform" or "monitoring" folders in
CVS=>HEAD are not projects, and that the subfolders are the projects.
Also, I believe those "features" folders you mentioned are also just
containers for projects inside them, not importable as projects for the
same reason platform and monitor are not.
I believe that you would need to import these individually (but likely
would not need all, depending on what you're building). For example, on
my present workbench, I have org.eclipse.hyades.use.cases and
org.eclipse.tptp.testautomation, and both have "bin" directories, but
there is no conflict. I don't think you can duplicate "actual" projects
though.
Hope that helps,
Victor
|
|
|
| Re: TPTP project structure [message #69720 is a reply to message #69537] |
Mon, 08 May 2006 12:27 |
Paul Slauenwhite
Messages: 975
Registered: July 2009 |
Senior Member |
|
|
Hi Rick,
The easiest way to extract TPTP plugins from CVS is to import (File >>
Import >> Team Project Set) using one of the TPTP project sets:
From http://www.eclipse.org/tptp/ >> Documentation
a.. TPTP Project File Set (Developers)
a.. TPTP Project File Set (Users)
In short, you need to select just the plugins (not features, since they
are use for packaging TPTP) you want to extract, build and run locally under
one or more of the four subproject (project, test, trace and monitor)
folders in CVS.
Paul
"rkm" <user@domain.invalid> wrote in message
news:e3g4cs$1e8$1@utils.eclipse.org...
> I checked out the code for TPTP and am confused about what I got,
> structure-wise. I'm confused because the TPTP platform checkout got me
> a folder of that name (platform), but it doesn't contain an Eclipse
> project. Instead it is a folder of sub-projects, each of which would
> have to be individually imported into Eclipse (I think) before I can
> start building the test widgets I want.
>
> But I see a problem with this approach because there is a folder called
> features and if I open the source for TPTP monitoring, there is also a
> folder called features inside there. So if I try to set up these
> sub-folders as Eclipse projects, I immediately run into a name space
> collision between these features folders, I can't have 2 projects both
> called "features".
>
> So how's everyone else setting these things up? I sure don't want to
> have to import about 50 or more Eclipse projects, one for each
> sub-folder I see, and have to rename those that have naming collisions.
> The solution is obvious right? And I'm just missing it?
>
> Rick
|
|
|
| Re: TPTP project structure [message #69814 is a reply to message #69720] |
Mon, 08 May 2006 15:25 |
| Eclipse User |
|
|
|
Originally posted by: user.domain.invalid
Paul Slauenwhite wrote:
thanks Paul. I'm not sure what the exact process is so I opened the
developers file set using Firefox, and I see all the html for the set.
So I copied that into a local file on my mac and tried the import as you
described. It starts to work and prompts me for a cvs
username/password. As soon as I type the first letter of anonymous,
Eclipse crashes. Tried it again, crashed it again. sigh
Probably works on a PC, right? Too bad I already bit the bullet and
individually imported over 100 separate projects on my PC before I saw
your note. I had no idea how I expected to keep those up to date as new
releases were made... I was just desperate to get anything going.
Guess I'll try the psf file on the PC and see what happens.
thanks again.
> Hi Rick,
> The easiest way to extract TPTP plugins from CVS is to import (File >>
> Import >> Team Project Set) using one of the TPTP project sets:
>
> From http://www.eclipse.org/tptp/ >> Documentation
>
> a.. TPTP Project File Set (Developers)
> a.. TPTP Project File Set (Users)
>
> In short, you need to select just the plugins (not features, since they
> are use for packaging TPTP) you want to extract, build and run locally under
> one or more of the four subproject (project, test, trace and monitor)
> folders in CVS.
>
|
|
|
| Re: TPTP project structure [message #70040 is a reply to message #69814] |
Tue, 09 May 2006 12:18 |
| Eclipse User |
|
|
|
Originally posted by: user.domain.invalid
rkm wrote:
> thanks Paul. I'm not sure what the exact process is so I opened the
> developers file set using Firefox, and I see all the html for the set.
> So I copied that into a local file on my mac and tried the import as you
> described. It starts to work and prompts me for a cvs
> username/password. As soon as I type the first letter of anonymous,
> Eclipse crashes. Tried it again, crashed it again. sigh
changed the .psf file to use pserver instead of extssh, then it worked
on the mac. I should open a bug on the crash, will do that asap.
>
> Guess I'll try the psf file on the PC and see what happens.
Would have worked it looks like, except that I didn't know a password
for the extssh connection, that's what clued me in on how to fix it on
the mac.
That sure was easier than unpacking all those projects by hand like I
did on my PC... it's good to get a little help now and then. Thanks.
|
|
|
| Re: TPTP project structure [message #70059 is a reply to message #69814] |
Tue, 09 May 2006 12:18 |
Paul Slauenwhite
Messages: 975
Registered: July 2009 |
Senior Member |
|
|
Hi Rick,
Sounds like you are following the correct process. I would suggest
opening a defect against the Team support in Eclipse, specific for the Mac.
This project set works on the PC.
Paul
"rkm" <user@domain.invalid> wrote in message
news:e3nntq$q0k$1@utils.eclipse.org...
> Paul Slauenwhite wrote:
>
> thanks Paul. I'm not sure what the exact process is so I opened the
> developers file set using Firefox, and I see all the html for the set.
> So I copied that into a local file on my mac and tried the import as you
> described. It starts to work and prompts me for a cvs
> username/password. As soon as I type the first letter of anonymous,
> Eclipse crashes. Tried it again, crashed it again. sigh
>
> Probably works on a PC, right? Too bad I already bit the bullet and
> individually imported over 100 separate projects on my PC before I saw
> your note. I had no idea how I expected to keep those up to date as new
> releases were made... I was just desperate to get anything going.
>
> Guess I'll try the psf file on the PC and see what happens.
>
> thanks again.
>
> > Hi Rick,
> > The easiest way to extract TPTP plugins from CVS is to import (File
>>
> > Import >> Team Project Set) using one of the TPTP project sets:
> >
> > From http://www.eclipse.org/tptp/ >> Documentation
> >
> > a.. TPTP Project File Set (Developers)
> > a.. TPTP Project File Set (Users)
> >
> > In short, you need to select just the plugins (not features, since
they
> > are use for packaging TPTP) you want to extract, build and run locally
under
> > one or more of the four subproject (project, test, trace and monitor)
> > folders in CVS.
> >
|
|
|
| Re: TPTP project structure [message #70098 is a reply to message #70059] |
Tue, 09 May 2006 13:50 |
| Eclipse User |
|
|
|
Originally posted by: user.domain.invalid
Paul Slauenwhite wrote:
> Sounds like you are following the correct process. I would suggest
> opening a defect against the Team support in Eclipse, specific for the Mac.
> This project set works on the PC.
Defect 140788.
|
|
|
| Re: TPTP project structure [message #70342 is a reply to message #69720] |
Wed, 10 May 2006 15:34 |
| Eclipse User |
|
|
|
Originally posted by: axel.stollfuss.avono.de
Hi Paul,
one short question concerning the Project File Sets. Are the Project
File Sets for TPTP 4.2 already available for download ?
Regards,
Axel
Paul Slauenwhite wrote:
> Hi Rick,
> The easiest way to extract TPTP plugins from CVS is to import (File >>
> Import >> Team Project Set) using one of the TPTP project sets:
>
> From http://www.eclipse.org/tptp/ >> Documentation
>
> a.. TPTP Project File Set (Developers)
> a.. TPTP Project File Set (Users)
>
> In short, you need to select just the plugins (not features, since they
> are use for packaging TPTP) you want to extract, build and run locally under
> one or more of the four subproject (project, test, trace and monitor)
> folders in CVS.
>
> Paul
> "rkm" <user@domain.invalid> wrote in message
> news:e3g4cs$1e8$1@utils.eclipse.org...
>> I checked out the code for TPTP and am confused about what I got,
>> structure-wise. I'm confused because the TPTP platform checkout got me
>> a folder of that name (platform), but it doesn't contain an Eclipse
>> project. Instead it is a folder of sub-projects, each of which would
>> have to be individually imported into Eclipse (I think) before I can
>> start building the test widgets I want.
>>
>> But I see a problem with this approach because there is a folder called
>> features and if I open the source for TPTP monitoring, there is also a
>> folder called features inside there. So if I try to set up these
>> sub-folders as Eclipse projects, I immediately run into a name space
>> collision between these features folders, I can't have 2 projects both
>> called "features".
>>
>> So how's everyone else setting these things up? I sure don't want to
>> have to import about 50 or more Eclipse projects, one for each
>> sub-folder I see, and have to rename those that have naming collisions.
>> The solution is obvious right? And I'm just missing it?
>>
>> Rick
>
>
|
|
|
| Re: TPTP project structure [message #70518 is a reply to message #70342] |
Thu, 11 May 2006 13:04 |
Paul Slauenwhite
Messages: 975
Registered: July 2009 |
Senior Member |
|
|
Hi Axel,
Unfortunately these project sets were last updated for the plugins
shipped with TPTP V4.1.x. However, there should be no new plugins in TPTP
V4.2.0.
Paul
"Axel Stollfuss" <axel.stollfuss@avono.de> wrote in message
news:e3t16u$ve2$1@utils.eclipse.org...
> Hi Paul,
>
> one short question concerning the Project File Sets. Are the Project
> File Sets for TPTP 4.2 already available for download ?
>
> Regards,
> Axel
>
> Paul Slauenwhite wrote:
> > Hi Rick,
> > The easiest way to extract TPTP plugins from CVS is to import (File
>>
> > Import >> Team Project Set) using one of the TPTP project sets:
> >
> > From http://www.eclipse.org/tptp/ >> Documentation
> >
> > a.. TPTP Project File Set (Developers)
> > a.. TPTP Project File Set (Users)
> >
> > In short, you need to select just the plugins (not features, since
they
> > are use for packaging TPTP) you want to extract, build and run locally
under
> > one or more of the four subproject (project, test, trace and monitor)
> > folders in CVS.
> >
> > Paul
> > "rkm" <user@domain.invalid> wrote in message
> > news:e3g4cs$1e8$1@utils.eclipse.org...
> >> I checked out the code for TPTP and am confused about what I got,
> >> structure-wise. I'm confused because the TPTP platform checkout got me
> >> a folder of that name (platform), but it doesn't contain an Eclipse
> >> project. Instead it is a folder of sub-projects, each of which would
> >> have to be individually imported into Eclipse (I think) before I can
> >> start building the test widgets I want.
> >>
> >> But I see a problem with this approach because there is a folder called
> >> features and if I open the source for TPTP monitoring, there is also a
> >> folder called features inside there. So if I try to set up these
> >> sub-folders as Eclipse projects, I immediately run into a name space
> >> collision between these features folders, I can't have 2 projects both
> >> called "features".
> >>
> >> So how's everyone else setting these things up? I sure don't want to
> >> have to import about 50 or more Eclipse projects, one for each
> >> sub-folder I see, and have to rename those that have naming collisions.
> >> The solution is obvious right? And I'm just missing it?
> >>
> >> Rick
> >
> >
|
|
|
Goto Forum:
Current Time: Sat Nov 09 01:07:46 GMT 2024
Powered by FUDForum. Page generated in 0.04584 seconds |
] 
Search
Help
Register
Login
Home
