On 1/7/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Can you give me an example of an OSS project submitting something to the central repository that doesn't have a public repository? How can you operate as an OSS project without a public repository?
well, these are a couple of small projects I created upload bundles for in the past that don't have a repository at all: http://www.lamatek.com/GoogleMaps/ http://schmidt.devlib.org/image-info/ ... and other projects may have a repository accessible only from an intranet (what sense does it make forcing users to put an intranet server in there?). This limitation was already reported in jira http://jira.codehaus.org/browse/MREPOSITORY-2
> It doesn't make sense that repository:bundle-create require it to > work, also because it's not really useful for users It's definitely useful for users to have the location of the source repository. Especially from IDEs if you grab a remote POM and want to create a project.
right, I agree with that. But we are simply saying that a scm url is not mandatory, not that we don't want it at all.. I think that all the elements that really impact most users like the basic project info (name, ids, description) license and dependencies (that we can't check automatically) should be made mandatory, but enforcing the availability of an scm url is probably too much.
> (on the other hand > license info was not mandatory, and that's something that can always > be filled and that is definitively useful). The license file was, but the element being specified is better. Some form of license information was mandatory.
yes, we are forcing users to add a license file but actually such file is simply discarded when uploading to a maven 2 repo :( fabrizio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
