Jason, > So why can't it all be in one repository? You have people who buy > your products with a non-source license and you give them access to > binaries from a Maven repository instead of an installer? Or you have > updaters that use a Maven repository so you only need the binaries > for this? This last case I could understand. >
We cannot have just one repository and give access to paying customers because we also have a community of plugin developers which rely on various artifacts that are part of our products. This would mean for every developer that would like to write a plugin we would have to give them access to the repository - this would include our private sources. > For your own artifacts that you are producing why do they need to be > public at all? I ask because I do something similar and I don't > understand what it is you're actually trying to accomplish. This > aside it still doesn't change the fact Maven wasn't designed to have > the primary artifact separated from the secondaries and simply causes > a discontinuity in tooling. This is currently how it works. For > anyone trying to debug their copy of an Atlassian product the Maven > IDE integration wouldn't work. The jars that are released to public without their sources and javadocs are not something the developers building and modifying the products would be wanting source and javadocs for anyway. They are there simply deployed so that they can build the source code that they are licensed to modify. Internally, our developers would be able to access the primary artifacts, sources, javadocs and assemblies. > In your case would it not be easier to give people read-only access > to the SCM, they build it as you build it and have access to a > password protected repository that contains everything required for > building. I don't understand your need to separate it the binaries > from javadoc and sources. Customers currently download the sources from the website, not checking them out from the repository. Having a password protected repository would mean we would have to add more admin overhead to the Developer Network team. I believe a user should be able to configure their maven builds to allow the deployment of attached artifacts to a specified repository. Users who would use this feature would have to be aware of the consequences of splitting these artifacts away from their primary artifacts. James --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
