Basically I understand what you mean, but the question is: do we identify us (as ops4j community) via the location of our code and artifacts?
btw, @nexus: as said we can still install nexus at our repos but deploy the artifacts to o.s.o... This would free us at least from the burden to store all the CI artifacts locally kind regards, andreas On Wed, Jan 26, 2011 at 08:02:47PM +0100, Toni Menzel wrote: > @Peter: Thanks for heads-up. Just wondered if things are in place > already because i found a Hudson (or should we say Jenkins already?) on > [1]ci.ops4j.org. > > @All: > > Nexus.. well i was also thinking about this. Releases go to o.s.o of > cause. CI builds could either go to the ops4j-snapshots on o.s.o. Or we > host our own. For simplicity and less maintenance (better use that for > coding) i tend to favor o.s.o. > > But on the other hand not sure if its good to hand out that one too. > > The downside would be that we cannot rely on non o.s.o dependencies > during development.. i particularly would point to Felix snapshots for > example - or just in-development versions of non ops4j projects in > general. > > If its not possible to put them under one repository - hint: just ONE > nexus to point to, not two, not many. That is (of cause) just a virtual > view not about physical repos. - then we NEED to have our own nexus > instance. > > Rephrasing the Infrastructure locations: > > === > > Hosted by OPS4J > > - CI (Hudson) > > - Issue Tracking (Jira) > > - Wiki (Confluence) > > -- > > Outsourced: > > - SCM (Github) > > - Maven Repo (o.s.o) + Maven Central > > So be clear: ALL code related things are outsourced. You can develop > without OPS4J infra. But not the other way around. Just wanted to make > that clear - also question this as it sounds a bit weird. > > If we would compare that to other communities - not saying we compare > in terms of size or anything - like Apache & Eclipse.. this is very > different. Even without having looked at the Open Participation > Principle at all. > > /Toni > > On Tue, Jan 25, 2011 at 8:06 AM, Andreas Pieber <[2]anpie...@gmail.com> > wrote: > > btw, what is with our plans to use one central points to retrieve > the artifacts > via nexus? IMHO we could make them accessible via > [3]repositories.ops4j.org but > deploy the artifacts via [4]oss.sonatype.org > wdyt? > > On Tue, Jan 25, 2011 at 07:51:45AM +0100, Peter Neubauer wrote: > > Toni, Achim, > > I am still waiting for the new build server to be deployed, guess I > > will have to check status again ... > > > > /peter > > > > On Mon, Jan 24, 2011 at 4:56 PM, Achim Nierbeck > <[5]bcanh...@googlemail.com> wrote: > > > Hi Toni, > > > > > > since there wasn't any CI available, I had to upload the pax-web > > > artefacts by myself. I think I asked about this last year on the > list > > > how to do this. If I did something wrong, my apologies, but there > > > wasn't much of advice on how I could provide latest snapshots. We > did > > > need these for testing with Apache-Karaf. > > > > > > Regarding the infrastructure, I would recommend dropping the > > > repository in favor of the oss.sonatype.repository :) > > > > > > +1 for the Hudson stuff. > > > > > > Regards, Achim > > > > > > 2011/1/24 Toni Menzel <[6]t...@okidokiteam.com>: > > >> Hi Guys, > > >> just wonder what the current status is about the new > infrastructure and what > > >> the (planned?) steps are. > > >> I see [7]ci.ops4j.org is available - but we should have a solution > for the > > >> maven related world - i see that on [8]oss.sonatype.org we own a > > >> ops4j-snapshots repo which also contains pretty new Pax Web > snapshots > > >> (1.0.0-SNAPSHOT) > > >> Question, was that a manual deploy ? Because [9]ci.ops4j.org does > not contain > > >> anything. > > >> Is it given that we do not a nexus ourselves, correct ? > > >> Any evidence that we should drop some of the (legacy?) > repositories > > >> on [10]http://repository.ops4j.org > > >> I would like to bring some of the Pax Projects, along with some > new ones, to > > >> the new infrastructure (meaning Hudson and Snapshot Deployments > working > > >> properly). - where to start and is there anything written about > the new > > >> infrastructure somewhere yet ? > > >> -- > > >> Toni Menzel - [11]http://www.okidokiteam.com > > >> > > >> _______________________________________________ > > >> general mailing list > > >> [12]general@lists.ops4j.org > > >> [13]http://lists.ops4j.org/mailman/listinfo/general > > >> > > >> > > > > > > _______________________________________________ > > > general mailing list > > > [14]general@lists.ops4j.org > > > [15]http://lists.ops4j.org/mailman/listinfo/general > > > > > > > _______________________________________________ > > general mailing list > > [16]general@lists.ops4j.org > > [17]http://lists.ops4j.org/mailman/listinfo/general > > _______________________________________________ > general mailing list > [18]general@lists.ops4j.org > [19]http://lists.ops4j.org/mailman/listinfo/general > > -- > Toni Menzel - [20]http://www.okidokiteam.com > > References > > 1. http://ci.ops4j.org/ > 2. mailto:anpie...@gmail.com > 3. http://repositories.ops4j.org/ > 4. http://oss.sonatype.org/ > 5. mailto:bcanh...@googlemail.com > 6. mailto:t...@okidokiteam.com > 7. http://ci.ops4j.org/ > 8. http://oss.sonatype.org/ > 9. http://ci.ops4j.org/ > 10. http://repository.ops4j.org/ > 11. http://www.okidokiteam.com/ > 12. mailto:general@lists.ops4j.org > 13. http://lists.ops4j.org/mailman/listinfo/general > 14. mailto:general@lists.ops4j.org > 15. http://lists.ops4j.org/mailman/listinfo/general > 16. mailto:general@lists.ops4j.org > 17. http://lists.ops4j.org/mailman/listinfo/general > 18. mailto:general@lists.ops4j.org > 19. http://lists.ops4j.org/mailman/listinfo/general > 20. http://www.okidokiteam.com/ > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general
pgpyovZeV4xG0.pgp
Description: PGP signature
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
