Hi Radu, I agree. But this is an orthogonal problem to the question of what SCM system we use.
I actually thought that we did deploy snapshots via CI. I see some artifacts under https://repository.apache.org/content/repositories/snapshots/org/apache/sling/ but it is inconsistent. Anyone know what is going on with the snapshot deployment? And what we can do to re-enable it? FWIW, I don't think we should (or really could) following a launchpad-only-contains-releases rule. But I'm willing to be convinced otherwise if the snapshot thing is really impossible. Justin On Thu, Oct 2, 2014 at 3:46 PM, Radu Cotescu <[email protected]> wrote: > Hi, > I know that I'm just an occasional contributor to Sling and I noticed that > this talk is mostly between PMC members. However, here's my big +1 for what > Robert proposed. > > Currently if somebody wants to contribute a new module to Sling they have > to build the full project to get a running launchpad, which (assuming that > they didn't use -DskipTests) takes a while. > > Just my €0.02. > > Cheers, > Radu > > On Thu, Oct 2, 2014 at 4:14 PM, Robert Munteanu <[email protected]> wrote: > >> Or do we we guarantee that the >> Launchpad is always buildable outside the reactor by banning SNAPSHOT >> dependencies >>
