tags:

views:

36

answers:

3

The environment: SVN, Netbeans, Hudson

SVN Project A: Builds a library file (foo.jar). The build file is under /dist, which is ignored for svn, the sourcecode is under svn control.

SVN Project B: holds all library files. (other SVN projects get all their libraries from here via external svn)

Question: I want to commit foo.jar from A into B. How to do that ? foo.jar cannot be added or committed because it is not under SVN control.

Thanks for any hints ! (The question is independent from the IDE and CI Server)

A: 

Why don't you change your build in that it automatically copies your jar to project B and when you commit project B it automatically commits your jar ? Is this an acceptable approach ?

thelost
+1  A: 

There may be a more clever way to do it, but what if your final step in the build process was to copy the output file (foo.jar) from projA/dist into projB/lib, and then check in projB?

This would assume that the two working copies are checked out in a specific place on the machine(s) used to perform builds, which may not be ideal from an academic standpoint of allowing the projects to be checked out anywhere, and have no interdependencies, but it should meet your needs to get the job done and move to the next problem!

pkaeding
A: 

When we need to do something like this we usually copy the file from A to B automatically at the end of the build. You could probably change the build process to commit it automatically if everything was fine (though that's not always a good idea).

rslite