| Re: [higgins-dev] Can we cvsignore lib? |
as a stop-gap, I built a linux shell script that does this:
for each jar file found in a specified "shared lib" folder:
locate all projects that depend on that jar, and for each of those projects:
create a symlink from that project's lib folder back to the jar file in the "shared folder"
Note that the first thing it does is removes all the existing jars in all the existing lib folders, so comment that line out if you don't want that behavior.
Also note that this is the first time I ever wrote a shell script or used awk, and my use of grep needs work. The thing is probably a sublime example of how not to do what I wanted. It should embarrass me to send it, but I really don't care. Oh, it also leaves some temp files in the directory that you run it from.
You have to run this from your workspace root (the directory which holds the roots of all your higgins projects), and you have to pass it one argument which is the path to your shared lib folder, like this:
sh symlinklibs.sh /home/jimse/dev/higgins/commonlibs
>>> Valery Kokhan <vkokhan@xxxxxxxxxxxxxx> 09/06/07 4:02 AM >>>
Jim,
The other minus is that a lot of our projects already have all (or
most) dependencies in lib folder and if we remove then it will be even
worse.
The alternative proposal would be to put all our dependency jars which
was already approved in new project in CVS (just with lib folders to
contains them) and make all our projects to use jars from that project.
Valery
Wednesday, September 5, 2007, 7:54:29 PM, you wrote:
> It seems like we're a long way from storing all dependency jar
> files in CVS. Until that day comes, does anyone object to adding
> "lib" to the .cvsignore at each project root?
> On the plus side, this would allow anyone using a link- capable OS
> (*nix) to create a "lib" link to a common lib directory. This would
> save lots of frustration in copying jar files around as dependencies change over time.
> On the minus side, people would have to create a lib directory (or link in the case above).
> I don't think creating a lib directory is all that bad since we
> already require people to populate it today (which is much more work than making the directory).
> If no one objects, I'd like to do this within the next day or two.
> Jim
> _______________________________________________
> higgins- dev mailing list
> higgins- dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/higgins- dev
Attachment:
symlinklibs.sh
Description: Bourne shell script