KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
Some of my colleagues are convinced that committing build artefacts to the subversion repository is a good idea. The argument is that this way, installation and update on the test machines is easy - just "svn up"! I'm sure there are weighty arguments against this bad practice, but all I can think of are lame ones like "it takes up more room". What are the best, killer reasons to not do this? And what other approaches should we do instead? This is for Java code if that makes a difference. Everything is compiled from Eclipse (with no automated PDE builds). When I say add the build artifacts, I mean a commit would look like this: "Added the new Whizbang feature" M src/foo/bar/Foo.java M bin/Foo.jar Each code change has the corresponding generated jar file.
Tags (comma-separated)
Save Edits
Cancel