I think we should try not to create a repository per bundle, if we can
avoid it. Particularly if each such repository would only contain a
pom.xml, an osgi.bnd and some license files...
I hope we can find a way of configuring the Maven Release plugin to work
on a submodule of a multi-module project. That's a thing to be tried out
in a local sandbox.
Anyway, thanks for raising the point. It's a good question and not a
trivial one.
I don't see a problem with (too) many tags on a repo. And even if we had
100 bundles with 10 versions each, it maybe wouldn't look nice on the
GitHub UI, but Git itself should be able to handle that.
Should we ever run into scalability problems, we could still think about
splitting the repository into groups, but I don't think we need to do it
up front.
Don't know who said it: "Premature optimization is the root of all
evil." :-)
Best regards,
Harald
Am 01.02.2012 17:19, schrieb Andreas Pieber:
Well, I've never tried, but in theory it should also be able to use the
plugin only for subprojects. But I think it would be extremely confusing
to have many tags on one repository. The question is: would it be
feasible to create a new repository for each project? The advantage
would be definitely to be able to use default git/maven methods; the BIG
disadvantage would be that you need administration rights to start such
a new project.
Kind regards,
Andreas
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
