On Thu, Jan 27, 2011 at 11:27:58AM +0100, Toni Menzel wrote: > On Thu, Jan 27, 2011 at 11:13 AM, Andreas Pieber > <[1]anpie...@gmail.com> wrote: > > 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? > > Yea, i think its location independent. Just wanted to clarify this > interesting fact. > > 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 > > But what exactly do we use "our nexus" for ? > Maybe it makes things easier: I use a local nexus instance as a proxy. > Thats the gate everything works for me. > I can add several repos pretty much independently. > But, what do we advice users/committers to build the software ? We > don't require a nexus. I would like to give one nexus repo URL that > works and lets you build the entire Trunk of all OPS4J projects. Thats > also what the CI Server will use for artifact resolution. Deployment > Target can be the o.s.o one. > So bottomline: Have a OPS4J Nexus as a proxy only then ? Never deploy > artifacts there as a rule of thumb ?
I like this idea; if you want to use snapshots of ops4j and all ops4j artifacts require only one external repo (repository.ops4j.org/nexus/) and the artifacts are gathered from o.s.o, jboss, ... +1 from my side kind regards, andreas > > 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][2]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][3]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][4]repositories.ops4j.org but > > deploy the artifacts via [4][5]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][6]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][7]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][8]ci.ops4j.org is available - but we should have > a solution > > for the > > > >> maven related world - i see that on [8][9]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][10]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][11]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][12]http://www.okidokiteam.com > > > >> > > > >> _______________________________________________ > > > >> general mailing list > > > >> [12][13]general@lists.ops4j.org > > > >> [13][14]http://lists.ops4j.org/mailman/listinfo/general > > > >> > > > >> > > > > > > > > _______________________________________________ > > > > general mailing list > > > > [14][15]general@lists.ops4j.org > > > > [15][16]http://lists.ops4j.org/mailman/listinfo/general > > > > > > > > > > _______________________________________________ > > > general mailing list > > > [16][17]general@lists.ops4j.org > > > [17][18]http://lists.ops4j.org/mailman/listinfo/general > > > > _______________________________________________ > > general mailing list > > [18][19]general@lists.ops4j.org > > [19][20]http://lists.ops4j.org/mailman/listinfo/general > > > > -- > > Toni Menzel - [20][21]http://www.okidokiteam.com > > > > References > > > > 1. [22]http://ci.ops4j.org/ > > 2. mailto:[23]anpie...@gmail.com > > 3. [24]http://repositories.ops4j.org/ > > 4. [25]http://oss.sonatype.org/ > > 5. mailto:[26]bcanh...@googlemail.com > > 6. mailto:[27]t...@okidokiteam.com > > 7. [28]http://ci.ops4j.org/ > > 8. [29]http://oss.sonatype.org/ > > 9. [30]http://ci.ops4j.org/ > > 10. [31]http://repository.ops4j.org/ > > 11. [32]http://www.okidokiteam.com/ > > 12. mailto:[33]general@lists.ops4j.org > > 13. [34]http://lists.ops4j.org/mailman/listinfo/general > > 14. mailto:[35]general@lists.ops4j.org > > 15. [36]http://lists.ops4j.org/mailman/listinfo/general > > 16. mailto:[37]general@lists.ops4j.org > > 17. [38]http://lists.ops4j.org/mailman/listinfo/general > > 18. mailto:[39]general@lists.ops4j.org > > 19. [40]http://lists.ops4j.org/mailman/listinfo/general > > 20. [41]http://www.okidokiteam.com/ > > > _______________________________________________ > > general mailing list > > [42]general@lists.ops4j.org > > [43]http://lists.ops4j.org/mailman/listinfo/general > > _______________________________________________ > general mailing list > [44]general@lists.ops4j.org > [45]http://lists.ops4j.org/mailman/listinfo/general > > -- > Toni Menzel - [46]http://www.okidokiteam.com > > References > > 1. mailto:anpie...@gmail.com > 2. http://ci.ops4j.org/ > 3. mailto:anpie...@gmail.com > 4. http://repositories.ops4j.org/ > 5. http://oss.sonatype.org/ > 6. mailto:bcanh...@googlemail.com > 7. mailto:t...@okidokiteam.com > 8. http://ci.ops4j.org/ > 9. http://oss.sonatype.org/ > 10. http://ci.ops4j.org/ > 11. http://repository.ops4j.org/ > 12. http://www.okidokiteam.com/ > 13. mailto:general@lists.ops4j.org > 14. http://lists.ops4j.org/mailman/listinfo/general > 15. mailto:general@lists.ops4j.org > 16. http://lists.ops4j.org/mailman/listinfo/general > 17. mailto:general@lists.ops4j.org > 18. http://lists.ops4j.org/mailman/listinfo/general > 19. mailto:general@lists.ops4j.org > 20. http://lists.ops4j.org/mailman/listinfo/general > 21. http://www.okidokiteam.com/ > 22. http://ci.ops4j.org/ > 23. mailto:anpie...@gmail.com > 24. http://repositories.ops4j.org/ > 25. http://oss.sonatype.org/ > 26. mailto:bcanh...@googlemail.com > 27. mailto:t...@okidokiteam.com > 28. http://ci.ops4j.org/ > 29. http://oss.sonatype.org/ > 30. http://ci.ops4j.org/ > 31. http://repository.ops4j.org/ > 32. http://www.okidokiteam.com/ > 33. mailto:general@lists.ops4j.org > 34. http://lists.ops4j.org/mailman/listinfo/general > 35. mailto:general@lists.ops4j.org > 36. http://lists.ops4j.org/mailman/listinfo/general > 37. mailto:general@lists.ops4j.org > 38. http://lists.ops4j.org/mailman/listinfo/general > 39. mailto:general@lists.ops4j.org > 40. http://lists.ops4j.org/mailman/listinfo/general > 41. http://www.okidokiteam.com/ > 42. mailto:general@lists.ops4j.org > 43. http://lists.ops4j.org/mailman/listinfo/general > 44. mailto:general@lists.ops4j.org > 45. http://lists.ops4j.org/mailman/listinfo/general > 46. http://www.okidokiteam.com/ > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general
pgpLinAp3KXaG.pgp
Description: PGP signature
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
