How to clean the top level project?

[sc1478 (Steve Cohen)]

@David_Karr

Irrespective of any particular solution to this, I think it’s generally better to structure builds so that you don’t need to do this. If another project needs the artifacts from another project, that project should reference that as a dependency. It might be best to fully describe what you generally need to do, so someone could advise on how and whether to transform the build to not require copying artifacts this way.

What I’m trying to do here, David, is emulate an existing process, in which the build for a particular project builds a bunch of RPMs, bundles them into a tar file for convenience and also puts the rpms AND the tar file, for some historical reason unknown to me, in the top level directory. Our current automated build does this and it’s a convention for our team. I suppose it’s easier for people to find them this way. There might be other suggestions that are as good, but right now, we haven’t done anything on automated gradle building.