Re: AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-18 Thread Carsten Ziegeler
Mike Müller wrote: > IMHO that's exactly the problem (or the point of view) which I > encoutered also: If you make changes to the actual trunk or if > you like to test the latest committed patch in whatever bundle, > where not the most recent bundle is refered in the pom of > launchpad/bundles, you

Re: AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-18 Thread Andreas Kollegger
You could just not use launchpad. I've created an OSGi project using pax-construct. The project provisions all the required Sling Bundles, which first must be built and installed in my local repository. In my OSGi project provisioning, I just reference all the SNAPSHOT versions if I want to

AW: AW: AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-18 Thread Mike Müller
Hi Felix >>> snip snap > > There are two things which make me wonder: > > > > 1) Why should the launchpad/bundle be something more stable > than the other > > stuff in the SVN? There's a (stable) release which ca be > used by users if > > they do not wish to have the newest stuff which maybe is un

AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-18 Thread Mike Müller
Hi > Replying to the head with some observations with a "user of sling > trunk" hat on rather than a core sling developer. > > If I make changes to sling trunk (eg usermanager servlets) > and use the > launchpad. nothing happens. > because launchpad depends on released versions and has nothing

Re: AW: AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-18 Thread Felix Meschberger
Hi, Mike Müller schrieb: > Hi > > From the discussion I've got, that launchpad/bundles should point only to > (stable) bundles which are already released or would be released soon in the > next release. There is a subtle notion: The launchpad/bundles module should contain stuff, we deem required

AW: AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-18 Thread Mike Müller
Hi From the discussion I've got, that launchpad/bundles should point only to (stable) bundles which are already released or would be released soon in the next release. There are two things which make me wonder: 1) Why should the launchpad/bundle be something more stable than the other stuff in t

Re: AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-18 Thread Felix Meschberger
Hi, Lets step back for a moment and look at what we got and we need: 1. the bundles module refers to what gets released 2. we should test what we release If we agree on this I think it is clear that the testing module should really refer to the same set of bundles as what gets released (or bet

Re: AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-18 Thread Carsten Ziegeler
Bertrand Delacretaz wrote: > On Mon, May 18, 2009 at 10:57 AM, Carsten Ziegeler > wrote: >> Bertrand Delacretaz wrote: >>> ...so we might want to go back and have >>> launchpad/testing use its own set of bundles version numbers. >>> >>> WDYT? > >> Ok, we can do this - so this is kind of doing li

Re: AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-18 Thread Bertrand Delacretaz
On Mon, May 18, 2009 at 10:57 AM, Carsten Ziegeler wrote: > Bertrand Delacretaz wrote: >> ...so we might want to go back and have >> launchpad/testing use its own set of bundles version numbers. >> >> WDYT? > Ok, we can do this - so this is kind of doing like gump is doing its stuff. > But I see

Re: AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-18 Thread Carsten Ziegeler
Bertrand Delacretaz wrote: > On Mon, May 18, 2009 at 10:11 AM, Carsten Ziegeler > wrote: >> ...I think all automatisms fail here; whenever >> someone thinks that a new bundle is ready for release/inclusing in the >> release, update the dependency in the launchpad/bundles > > Why not, but I'd

Re: AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-18 Thread Bertrand Delacretaz
On Mon, May 18, 2009 at 10:11 AM, Carsten Ziegeler wrote: > ...I think all automatisms fail here; whenever > someone thinks that a new bundle is ready for release/inclusing in the > release, update the dependency in the launchpad/bundles Why not, but I'd like the launchpad/testing module to a

Re: AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-18 Thread Carsten Ziegeler
Felix Meschberger wrote: > Hi, > > How about this: I created SLING-972 [1] as a standing task issue for the > next collection release. Whenever a bundle is modified, the > launchpad/bundles module should be checked whether the reference to the > latest snapshot is already contained and under the l

Re: AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-15 Thread Felix Meschberger
Hi, How about this: I created SLING-972 [1] as a standing task issue for the next collection release. Whenever a bundle is modified, the launchpad/bundles module should be checked whether the reference to the latest snapshot is already contained and under the label of SLING-972 update the referenc

AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-15 Thread Mike Müller
Hi Bertrand > > ...Have you in mind to give users something more stable > than the real > > snapshot if the build the standalone app or the web app? > > At the moment I use the launchpad app as the base for my tests. > > But I would like to do the tests with the latest sling source. > > So if my a

AW: update launchpad/bundles/pom.xml to SNAPSHOT versions?

2009-05-15 Thread Mike Müller
Hi Felix Have you in mind to give users something more stable than the real snapshot if the build the standalone app or the web app? At the moment I use the launchpad app as the base for my tests. But I would like to do the tests with the latest sling source. So if my assumption about your doubt i