| RE: [higgins-dev] build output directories |
|
Does anyone know how to remove a directory from CVS?
I've been playing with making these changes in the sts projects and have this problem:
- Can't delete ./build from CVS
- Can add .cvsignore (containing *) to ./build -- this works great until:
- Eclipse deletes everything under ./build when you do a clean, including .cvsignore -- thus
- Eclipse CVS wants to commit everything under ./build
In the IdAS project, I never added the build directory (called ./bin, but I an change that) to CVS, thus none of these problems are an issue.
So, if we could just remove the ./build directories from all the sts projects, we could put "build" in the .cvsignore at the project root and all would be well.
Jim
>>> "Paul Trevithick" <paul@xxxxxxxxxxxxxxxxx> 2/3/07 9:29 AM >>> +1 From: higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Sermersheim Actually, I'm torn on the doc output directory. IdAS and STS currently output these to ../www.org.eclipse.higgins.docs/<project>. This is good for people like me who have commit rights to the www cvs repository, but not so good for anyone else. Maybe we should output into ./build/doc, and if someone like me wants to occasionally copy that output into another project, then we can. Jim We were talking on IM today about making consistent the build output directories for our projects. We ended up wanting to do this: ./build/classes (holds .class files) ./build/lib (holds .jar and .war) Looking closer, I think we probably also want: ./build/doc (generated doc output) But back on ./build/classes. I think we want to have the eclipse output dir just be ./build. This is because the "Clean" target deletes stuff in the eclipse output directory. So for example, in the current sts projects, this will only clean stuff under ./build/classes. We need Clean to clean all output. The only potential problem I see is if we ever wanted to have a package name that starts with "lib" or "doc". Jim |