Hi Alex and Carsten, > -----Original Message----- > From: Alexander Klimetschek [mailto:[EMAIL PROTECTED] > Sent: Friday, July 18, 2008 6:23 AM > To: [email protected] > Subject: Re: Sling inter-dependencies > > On Fri, Jul 18, 2008 at 11:45 AM, Carsten Ziegeler > <[EMAIL PROTECTED]> wrote: > > this is actually a hot topic where people have different > opinions. For > > now we think that we should change dependencies between modules if > > there is no reason for it. > > You probably mean > > "For now we think that we should *not* change dependencies > between modules if there is no reason for it." > > > If we would have changed the dependency to 2.0.3-incubator-SNAPSHOT > > for the json module, you would first need to build the > snapshot of the > > json module, deploy that before you can deploy your servlets get > > module. And in the end this wouldn't be required, but you > can't tell this from looking at the pom. > > That's actually a good argument I have never thought of so far! > > @Craig: You may take a look at > http://cwiki.apache.org/SLING/thoughts-on-release-management.html, > which describes the "official" versioning and release process > for Sling. >
Yeah, ok, thanks for the explanation, after submitting this and thinking about it more, I figured you'd have a good reason ;-) So, if I submit a patch, should I change the version for the "org.apache.sling.commons.json" dependency in the "org.apache.sling.servlets.get" pom? Would that be ok? > Regards, > Alex > > -- > Alexander Klimetschek > [EMAIL PROTECTED] > Cheers, Craig
