Home » Newcomers » Newcomers » Project directory structure
| Project directory structure [message #265537] |
Tue, 14 October 2008 14:39  |
Eclipse User |
|
|
|
Originally posted by: mclaassen.ocie.net
I am a long time Netbeans user, but am evalutating Eclipse. I am trying to
convert my Netbeans project over, and it is not going to well. I could not
find a tutorial to help me with this.
What I have is:
[root] (cvs checkout point)
libs
projects
project a
project b
build
dist
test
....
The libs directory have 3rd party jar files that are shared between the
projects. The projects each have run settings. (Where does eclipse store
the run settings.)
What I need to do in eclipse is be able to check-in whatever I need to so
that other developers can check out our codebase from CVS and have the
projects ready to go (with the run settings).
Thanks,
Mark
|
|
|
| Re: Project directory structure [message #265543 is a reply to message #265537] |
Tue, 14 October 2008 16:45  |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Mark Claassen wrote:
> I am a long time Netbeans user, but am evalutating Eclipse. I am trying
> to convert my Netbeans project over, and it is not going to well. I
> could not find a tutorial to help me with this.
>
> What I have is:
>
> [root] (cvs checkout point)
> libs
> projects
> project a
> project b
> build
> dist
> test
> ...
> The libs directory have 3rd party jar files that are shared between the
> projects. The projects each have run settings. (Where does eclipse
> store the run settings.)
>
> What I need to do in eclipse is be able to check-in whatever I need to
> so that other developers can check out our codebase from CVS and have
> the projects ready to go (with the run settings).
First, I want to point you to the Project Configuration Tutorial. Here
is the online link, but it is also available in your local Eclipse Help
(Help > Contents from the Eclipse menubar):
< http://help.eclipse.org/ganymede/topic/org.eclipse.jdt.doc.u ser/gettingStarted/qs-ProjectConfiguration.htm>
That tutorial has several examples of typical codebase layouts and how
to configure them in Eclipse projects.
For your particular case, decisions depend somewhat on a couple of
questions:
a) do you intend to manage CVS interactions from within Eclipse? The
typical usage pattern is to do so; Eclipse's CVS client is the best I've
ever used by far. I'll assume the answer is yes.
b) Do other developers on your team intend to use Eclipse, too?
Anyway, to get you started, I would recommend creating your projects
like one of the tutorial examples above; you'll have a ProjectA and a
ProjectB, rooted at the "project a" and "project b" folders in your
structure above. Since you have one shared libs directory, I'd also
recommend a third project called something like "Shared" or "Libs",
rooted in your "libs" directory. That project will only have JARs, no
source of its own. ProjectA and ProjectB will include it on their Java
Build Path > Projects section so that they both inherit its JARs.
Start with that and if you have further questions, post them.
As for run settings, they are stored in what are called Launch
Configurations. The Help has lots of material on that subject, too,
including how to store them inside the project itself so they can be
checked in.
Hope this helps,
Eric
|
|
|
| Re: Project directory structure [message #265547 is a reply to message #265543] |
Tue, 14 October 2008 17:03 |
| Eclipse User |
|
|
|
Originally posted by: mclaassen.ocie.net
> do you intend to manage CVS interactions from within Eclipse?
Yes
>Do other developers on your team intend to use Eclipse, too?
Yes
Thanks a lot. I looked for stuff and I could not find anything that looked
applicable. Just knowing what things are called (like "Launch
Configurations" helps tremendiously as well.
I will look at I will look at the tutuorial ASAP
"Eric Rizzo" <eclipse-news@rizzoweb.com> wrote in message
news:gd30bk$jpp$1@build.eclipse.org...
> Mark Claassen wrote:
>> I am a long time Netbeans user, but am evalutating Eclipse. I am trying
>> to convert my Netbeans project over, and it is not going to well. I
>> could not find a tutorial to help me with this.
>>
>> What I have is:
>>
>> [root] (cvs checkout point)
>> libs
>> projects
>> project a
>> project b
>> build
>> dist
>> test
>> ...
>> The libs directory have 3rd party jar files that are shared between the
>> projects. The projects each have run settings. (Where does eclipse
>> store the run settings.)
>>
>> What I need to do in eclipse is be able to check-in whatever I need to so
>> that other developers can check out our codebase from CVS and have the
>> projects ready to go (with the run settings).
>
> First, I want to point you to the Project Configuration Tutorial. Here is
> the online link, but it is also available in your local Eclipse Help (Help
> > Contents from the Eclipse menubar):
> < http://help.eclipse.org/ganymede/topic/org.eclipse.jdt.doc.u ser/gettingStarted/qs-ProjectConfiguration.htm>
>
> That tutorial has several examples of typical codebase layouts and how to
> configure them in Eclipse projects.
>
> For your particular case, decisions depend somewhat on a couple of
> questions:
> a) do you intend to manage CVS interactions from within Eclipse? The
> typical usage pattern is to do so; Eclipse's CVS client is the best I've
> ever used by far. I'll assume the answer is yes.
>
> b) Do other developers on your team intend to use Eclipse, too?
>
> Anyway, to get you started, I would recommend creating your projects like
> one of the tutorial examples above; you'll have a ProjectA and a ProjectB,
> rooted at the "project a" and "project b" folders in your structure above.
> Since you have one shared libs directory, I'd also recommend a third
> project called something like "Shared" or "Libs", rooted in your "libs"
> directory. That project will only have JARs, no source of its own.
> ProjectA and ProjectB will include it on their Java Build Path > Projects
> section so that they both inherit its JARs.
>
> Start with that and if you have further questions, post them.
>
> As for run settings, they are stored in what are called Launch
> Configurations. The Help has lots of material on that subject, too,
> including how to store them inside the project itself so they can be
> checked in.
>
> Hope this helps,
> Eric
|
|
|
| Re: Project directory structure [message #265562 is a reply to message #265547] |
Wed, 15 October 2008 09:47 |
| Eclipse User |
|
|
|
Originally posted by: mclaassen.ocie.net
That helped a lot.
However, I am still working on the launch configurations. I can see how to
"share" it, and that seems to works. However, I would think that if I would
copy the launch file and rename it (in the same directory), eclipse would
automatically pick it up. This seems not to be the case. How does eclipse
know how to find the launch files? I thought maybe it would do a save for
..launch files or something, but it appears to keep this information
somewhere else. Any ideas?
Netbeans projects are quite self-contained. I can check it all in and then
someone else can check it out and it is ready to go. If a new testing
configuration is needed, I can add it, commit it to CVS, and then the next
time other people do an update, they can use the new configuration. Can I
achieve this with eclipse?
"Mark Claassen" <mclaassen@ocie.net> wrote in message
news:gd31fv$vde$1@build.eclipse.org...
>> do you intend to manage CVS interactions from within Eclipse?
> Yes
>
>>Do other developers on your team intend to use Eclipse, too?
> Yes
>
> Thanks a lot. I looked for stuff and I could not find anything that
> looked applicable. Just knowing what things are called (like "Launch
> Configurations" helps tremendiously as well.
>
> I will look at I will look at the tutuorial ASAP
>
>
> "Eric Rizzo" <eclipse-news@rizzoweb.com> wrote in message
> news:gd30bk$jpp$1@build.eclipse.org...
>> Mark Claassen wrote:
>>> I am a long time Netbeans user, but am evalutating Eclipse. I am trying
>>> to convert my Netbeans project over, and it is not going to well. I
>>> could not find a tutorial to help me with this.
>>>
>>> What I have is:
>>>
>>> [root] (cvs checkout point)
>>> libs
>>> projects
>>> project a
>>> project b
>>> build
>>> dist
>>> test
>>> ...
>>> The libs directory have 3rd party jar files that are shared between the
>>> projects. The projects each have run settings. (Where does eclipse
>>> store the run settings.)
>>>
>>> What I need to do in eclipse is be able to check-in whatever I need to
>>> so that other developers can check out our codebase from CVS and have
>>> the projects ready to go (with the run settings).
>>
>> First, I want to point you to the Project Configuration Tutorial. Here is
>> the online link, but it is also available in your local Eclipse Help
>> (Help > Contents from the Eclipse menubar):
>> < http://help.eclipse.org/ganymede/topic/org.eclipse.jdt.doc.u ser/gettingStarted/qs-ProjectConfiguration.htm>
>>
>> That tutorial has several examples of typical codebase layouts and how to
>> configure them in Eclipse projects.
>>
>> For your particular case, decisions depend somewhat on a couple of
>> questions:
>> a) do you intend to manage CVS interactions from within Eclipse? The
>> typical usage pattern is to do so; Eclipse's CVS client is the best I've
>> ever used by far. I'll assume the answer is yes.
>>
>> b) Do other developers on your team intend to use Eclipse, too?
>>
>> Anyway, to get you started, I would recommend creating your projects like
>> one of the tutorial examples above; you'll have a ProjectA and a
>> ProjectB, rooted at the "project a" and "project b" folders in your
>> structure above. Since you have one shared libs directory, I'd also
>> recommend a third project called something like "Shared" or "Libs",
>> rooted in your "libs" directory. That project will only have JARs, no
>> source of its own. ProjectA and ProjectB will include it on their Java
>> Build Path > Projects section so that they both inherit its JARs.
>>
>> Start with that and if you have further questions, post them.
>>
>> As for run settings, they are stored in what are called Launch
>> Configurations. The Help has lots of material on that subject, too,
>> including how to store them inside the project itself so they can be
>> checked in.
>>
>> Hope this helps,
>> Eric
>
|
|
|
| Re: Project directory structure [message #265588 is a reply to message #265562] |
Thu, 16 October 2008 09:25 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Mark Claassen wrote:
> That helped a lot.
>
> However, I am still working on the launch configurations. I can see how
> to "share" it, and that seems to works. However, I would think that if
> I would copy the launch file and rename it (in the same directory),
> eclipse would automatically pick it up. This seems not to be the case.
> How does eclipse know how to find the launch files? I thought maybe it
> would do a save for .launch files or something, but it appears to keep
> this information somewhere else. Any ideas?
I don't know, maybe the list of launches is cached or maybe there is
something in the file that must be unique (besides the name). You could
try restarting Eclipse to see if it picks up the copied launch.
In any case, it is easier to duplicate an existing launch config using
the UI; in the Debug Configurations or Run Configurations dialog, select
the one you want to copy, right-click, and choose Duplicate.
> Netbeans projects are quite self-contained. I can check it all in and
> then someone else can check it out and it is ready to go. If a new
> testing configuration is needed, I can add it, commit it to CVS, and
> then the next time other people do an update, they can use the new
> configuration. Can I achieve this with eclipse?
Check in everything under the project, including the .project and
..classpath files, the .settings directory (if you have one), and the
..launch files.
When someone checks that out from CVS using Eclipse, it will
automatically detect those project files and set up the project
appropriately. It will even detect the .launch files and add them to the
user's Debug and Run "favorites" toolbar buttons (if you configured the
launch to do that on the Common tab).
Hope this helps,
Eric
>
>
> "Mark Claassen" <mclaassen@ocie.net> wrote in message
> news:gd31fv$vde$1@build.eclipse.org...
>>> do you intend to manage CVS interactions from within Eclipse?
>> Yes
>>
>>> Do other developers on your team intend to use Eclipse, too?
>> Yes
>>
>> Thanks a lot. I looked for stuff and I could not find anything that
>> looked applicable. Just knowing what things are called (like "Launch
>> Configurations" helps tremendiously as well.
>>
>> I will look at I will look at the tutuorial ASAP
>>
>>
>> "Eric Rizzo" <eclipse-news@rizzoweb.com> wrote in message
>> news:gd30bk$jpp$1@build.eclipse.org...
>>> Mark Claassen wrote:
>>>> I am a long time Netbeans user, but am evalutating Eclipse. I am
>>>> trying to convert my Netbeans project over, and it is not going to
>>>> well. I could not find a tutorial to help me with this.
>>>>
>>>> What I have is:
>>>>
>>>> [root] (cvs checkout point)
>>>> libs
>>>> projects
>>>> project a
>>>> project b
>>>> build
>>>> dist
>>>> test
>>>> ...
>>>> The libs directory have 3rd party jar files that are shared between
>>>> the projects. The projects each have run settings. (Where does
>>>> eclipse store the run settings.)
>>>>
>>>> What I need to do in eclipse is be able to check-in whatever I need
>>>> to so that other developers can check out our codebase from CVS and
>>>> have the projects ready to go (with the run settings).
>>>
>>> First, I want to point you to the Project Configuration Tutorial.
>>> Here is the online link, but it is also available in your local
>>> Eclipse Help (Help > Contents from the Eclipse menubar):
>>> < http://help.eclipse.org/ganymede/topic/org.eclipse.jdt.doc.u ser/gettingStarted/qs-ProjectConfiguration.htm>
>>>
>>>
>>> That tutorial has several examples of typical codebase layouts and
>>> how to configure them in Eclipse projects.
>>>
>>> For your particular case, decisions depend somewhat on a couple of
>>> questions:
>>> a) do you intend to manage CVS interactions from within Eclipse? The
>>> typical usage pattern is to do so; Eclipse's CVS client is the best
>>> I've ever used by far. I'll assume the answer is yes.
>>>
>>> b) Do other developers on your team intend to use Eclipse, too?
>>>
>>> Anyway, to get you started, I would recommend creating your projects
>>> like one of the tutorial examples above; you'll have a ProjectA and a
>>> ProjectB, rooted at the "project a" and "project b" folders in your
>>> structure above. Since you have one shared libs directory, I'd also
>>> recommend a third project called something like "Shared" or "Libs",
>>> rooted in your "libs" directory. That project will only have JARs, no
>>> source of its own. ProjectA and ProjectB will include it on their
>>> Java Build Path > Projects section so that they both inherit its JARs.
>>>
>>> Start with that and if you have further questions, post them.
>>>
>>> As for run settings, they are stored in what are called Launch
>>> Configurations. The Help has lots of material on that subject, too,
>>> including how to store them inside the project itself so they can be
>>> checked in.
>>>
>>> Hope this helps,
>>> Eric
>>
>
|
|
|
Goto Forum:
Current Time: Sat Jul 19 11:50:30 EDT 2025
Powered by FUDForum. Page generated in 0.08585 seconds |
Home