| If you don't want your artifacts uploaded to some place (like your SCM) then don't do it. But let me explain how useful this actually is. When working on a Java project with a team of people, we usually use Maven and some CI tool like Jenkins or Bamboo. People commit code, Jenkins run a Maven build and then either Jenkins or Maven uploads build artifacts to a central repository. Artifacts usually are: the jar/war/ear file, the -src.jar and the -javadoc.jar. If code is finished then it will be a x.y release, otherwise it will be uploaded as something like 1.0-SNAPSHOT. Snapshots are usually timestamped. Now I have a standard place where other projects can find dependencies, where the ops team can grab releases, where developers can find dependencies, code and documentation. Three extra lines in a pom.xml and you get all that. Your IDE now picks it up and keeps it up to date. You can click/hotkey on anything and it will show source or documentation. You call it pollution, I call it a great and pretty much completely automatic infrastructure that makes development so much easier. |