NetBeans and CVS
We have different projects all being hosted in the same CVS respository.
Say, for example, the repository root is "/cvs". One project is named
"commons" and another is named "vgm". Both use the same top-level package
structure. So out on the CVS server, I have:
+ /cvs
|+ COMMONS
|| + com
||+ ...
|+ VGM
|| + com
||+ ...
..
When I check out into NetBeans, I check out modules COMMONS and VGM (I would
like to maintain these in the same mounted filesystem). But the problem is
the classpath is "screwed-up". Because these are both checked out in the
same filesystem, I cannot simply use the relative mount point to adjust the
directories.
I had thought that adding the "com" level directories to the project (i.e.,
Tools | Add to Project) would correct the problem, but apparently the
project-tab is not taken into account for classpath building.
Another problem I see coming up is dealing with libraries. We have a whole
seperate dir for placing jars out on CVS (under /cvs/LIB). Ideally, when
checking out a module (say the VGM module in the example above), I would
like the CVS module def to include the dependent libraries. This is easy
enough from a CVS perspective, but again the problem arises once the files
are in NetBeans of how to get them into the classpath.
Thanks for any insight.
# 1
Hi Steve,
Here is the way we do it, also having multiple modules in CVS.
We use the treefs (in the update center beta, install "View over a
Filesystem"), which enables you to mount any node in the explorer as a
filesystem, which will then be used for the classpath. It works very
well, you can then mount these virtual filesystems as nodes in the
project tab.
It has a few drawbacks, listed here:
- you will have multiple tree roots named "com" (but you have this already)
- if you use the "explore from here", and mount it as a tab somewhere in
the IDE, next time you restart NetBeans, you'll have to re-explore from
here and re-place the tab where you want it. Because of treefs, the tabs
existence and location are not saved. If your package tree is deep and
thin, and you restart your IDE everyday, it might bother you.
But I like this separation. You are in the filesystem tab to setup the
CVS modules (creation, removal, etc.). Then in the project tab, you do
editing, and the day-to-day CVS operations (update, refresh, commit,
add/remove, etc).
--Pascal
SteveEbersole wrote:
>We have different projects all being hosted in the same CVS respository.
>Say, for example, the repository root is "/cvs". One project is named
>"commons" and another is named "vgm". Both use the same top-level package
>structure. So out on the CVS server, I have:
>
>+ /cvs
> |+ COMMONS
> || + com
> ||+ ...
> |+ VGM
> || + com
> ||+ ...
>...
>
>When I check out into NetBeans, I check out modules COMMONS and VGM (I would
>like to maintain these in the same mounted filesystem). But the problem is
>the classpath is "screwed-up". Because these are both checked out in the
>same filesystem, I cannot simply use the relative mount point to adjust the
>directories.
>
>I had thought that adding the "com" level directories to the project (i.e.,
>Tools | Add to Project) would correct the problem, but apparently the
>project-tab is not taken into account for classpath building.
>
>
>Another problem I see coming up is dealing with libraries. We have a whole
>seperate dir for placing jars out on CVS (under /cvs/LIB). Ideally, when
>checking out a module (say the VGM module in the example above), I would
>like the CVS module def to include the dependent libraries. This is easy
>enough from a CVS perspective, but again the problem arises once the files
>are in NetBeans of how to get them into the classpath.
>
>Thanks for any insight.
>
>
>
# 2
Hi Steve,
I'm new to NetBeans, so I can't offer any advice on how to get this to work
using the native build system, but you could always create an Ant build file
which explicitly sets the classpath and launch this from within the IDE.
Cheers,
Robert
--Original Message--
From: SteveEbersole [mailto:steberso@vignette.com]
Sent: 26 July 2002 20:03
To: nbusers@netbeans.org
Subject: NetBeans and CVS
We have different projects all being hosted in the same CVS respository.
Say, for example, the repository root is "/cvs". One project is named
"commons" and another is named "vgm". Both use the same top-level package
structure. So out on the CVS server, I have:
+ /cvs
|+ COMMONS
|| + com
||+ ...
|+ VGM
|| + com
||+ ...
..
When I check out into NetBeans, I check out modules COMMONS and VGM (I would
like to maintain these in the same mounted filesystem). But the problem is
the classpath is "screwed-up". Because these are both checked out in the
same filesystem, I cannot simply use the relative mount point to adjust the
directories.
I had thought that adding the "com" level directories to the project (i.e.,
Tools | Add to Project) would correct the problem, but apparently the
project-tab is not taken into account for classpath building.
Another problem I see coming up is dealing with libraries. We have a whole
seperate dir for placing jars out on CVS (under /cvs/LIB). Ideally, when
checking out a module (say the VGM module in the example above), I would
like the CVS module def to include the dependent libraries. This is easy
enough from a CVS perspective, but again the problem arises once the files
are in NetBeans of how to get them into the classpath.
Thanks for any insight.
# 3
P. Fleury wrote:
> - if you use the "explore from here", and mount it as a tab somewhere in
> the IDE, next time you restart NetBeans, you'll have to re-explore from
> here and re-place the tab where you want it. Because of treefs, the tabs
> existence and location are not saved. If your package tree is deep and
> thin, and you restart your IDE everyday, it might bother you.
Huh? Works fine for me, I just tried it with NB 3.4 RC1.
-Jesse
--
Jesse Glick <mailto:jesse.glick@sun.com> x22801
NetBeans, Open APIs <http://www.netbeans.org/>
# 4
Jesse Glick wrote:
> P. Fleury wrote:
>
>> - if you use the "explore from here", and mount it as a tab somewhere
>> in the IDE, next time you restart NetBeans, you'll have to re-explore
>> from here and re-place the tab where you want it. Because of treefs,
>> the tabs existence and location are not saved. If your package tree
>> is deep and thin, and you restart your IDE everyday, it might bother
>> you.
>
>
> Huh? Works fine for me, I just tried it with NB 3.4 RC1.
Yes, it does for me too now :-) So there are only benefits left then ! :-)
Cheers,
--Pascal
>
>
> -Jesse
>
