> Sorry if I'm missing something but why they can't just publish everything to > their private repo and just mirror things > they want share to the public repository afterwards?
Sure, that could be done, however, this is yet more infrastructure that needs to be written and maintained in the build environment. > As being Maven user (I'm from Apache Cocoon) I support Jason's opinion here. > If you have very specific requirements that > could be fulfilled by existing tools (few lines of script) just use them and > don't pollute other tools with your > specific needs. Why use yet another external tool? >From the maven website itself: "Maven can manage a project's build, reporting and documentation from a central piece of information." So, is the information for the control of artifact deployment not within the scope of the projects mission? Isn't maven supposed to manage my projects build? As you know, Maven already does this in a limited sense - you can deploy whole projects to one repository or another via specifying a distribution management information in your pom. The real use case here is giving developers the flexibility to control what kinds of artifacts go where and subsequently who has access to specific artifact types. For example, at Atlassian, we have a model where customers pay for a license and receive our source code. Customers can then use Maven to resolve dependant artifacts from our public maven repository and build the entire product. For IP reasons, we cannot publish the source and javadoc artifacts publicly along with the jar artifact of which our internal development staff and contractors need to use. I think this would be a fairly common use case among other companies with similar models and if maven is a build management tool - why can't it manage the needs of commercial products too? Thanks -- James William Dumay <[EMAIL PROTECTED]> Atlassian Software Systems --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
