Can the person responsible for the custom shindig module (1.0-r790473-Patch06) please update it to not rely on gatein-dep 1.1.0-Beta02, that version doesn't exist in the repos and is causing the build to fail. Good old maven bringing in multiple dependencies of everything :( On Thu, 2011-04-28 at 12:34 +0200, Julien Viet wrote: > I would like to clarify how now 3rd party should be managed in GateIn trunk, because it has changed implicitly since yesterday (see the another thread of this list). > > Now we are trying to handle all 3rd party dependencies in a separate "dependency" oriented pom known as gatein-dep that specifies the version of the library we use in GateIn and its components (although it is less strict for component). This has been existing until now but was not really used, so it's not really something new, what is new is that now we want to use it for real. > > This pom is not in the project itself which means that it has a separate lifecycle and any update to the thirdparty should be done here. It may seem a bit heavy but in fact this serve the purpose that updating a lib has often consequences at the integration level of the whole server. So indeed if one version must be changed or added, this should be done in this gatein-dep pom. Actually this helped me to find out dated libraries in gatein that were expected by Shindig at runtime but were not satisfied (now the Shindig fork uses the gatein-dep as it has many dependencies). > > The gatein-dep pom can be found here http://anonsvn.jboss.org/repos/gatein/maven/dep/trunk/ > > It is integrated in gatein by a declaration in the parent pom: > > <dependency> > <groupId>org.gatein</groupId> > <artifactId>gatein-dep</artifactId> > <version>1.1.0-Beta03</version> > <type>pom</type> > <scope>import</scope> > </dependency> > > Of course it does not mean you cannot override a version in your own pom when you need to test something like adding a new library or changing a version to test something. Actually this can be done by changing the parent pom in your local copy. When you think something should be changed or added, then you should raise the concern to get this change in the gatein-dep pom. > > cheers > > Julien > _______________________________________________ > gatein-dev mailing list > gatein-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/gatein-dev

actually https://repository.jboss.org/nexus/content/groups/public/org/gatein/gatei... On Apr 28, 2011, at 8:00 PM, Julien Viet wrote: > I deployed this pom 1.1.0-Beta02 : https://repository.jboss.org/nexus/content/groups/public/org/gatein/gatei... > > why don't you see it ? > > why is now everyone wanting to compile Shindig now :-) ?

> On Apr 28, 2011, at 7:43 PM, Matt Wringe wrote: > >> Can the person responsible for the custom shindig module >> (1.0-r790473-Patch06) please update it to not rely on gatein-dep >> 1.1.0-Beta02, that version doesn't exist in the repos and is causing the >> build to fail. >> >> Good old maven bringing in multiple dependencies of everything :( >> >> On Thu, 2011-04-28 at 12:34 +0200, Julien Viet wrote: >>> I would like to clarify how now 3rd party should be managed in GateIn trunk, because it has changed implicitly since yesterday (see the another thread of this list). >>> >>> Now we are trying to handle all 3rd party dependencies in a separate "dependency" oriented pom known as gatein-dep that specifies the version of the library we use in GateIn and its components (although it is less strict for component). This has been existing until now but was not really used, so it's not really something new, what is new is that now we want to use it for real. >>> >>> This pom is not in the project itself which means that it has a separate lifecycle and any update to the thirdparty should be done here. It may seem a bit heavy but in fact this serve the purpose that updating a lib has often consequences at the integration level of the whole server. So indeed if one version must be changed or added, this should be done in this gatein-dep pom. Actually this helped me to find out dated libraries in gatein that were expected by Shindig at runtime but were not satisfied (now the Shindig fork uses the gatein-dep as it has many dependencies). >>> >>> The gatein-dep pom can be found here http://anonsvn.jboss.org/repos/gatein/maven/dep/trunk/ >>> >>> It is integrated in gatein by a declaration in the parent pom: >>> >>> <dependency> >>> <groupId>org.gatein</groupId> >>> <artifactId>gatein-dep</artifactId> >>> <version>1.1.0-Beta03</version> >>> <type>pom</type> >>> <scope>import</scope> >>> </dependency> >>> >>> Of course it does not mean you cannot override a version in your own pom when you need to test something like adding a new library or changing a version to test something. Actually this can be done by changing the parent pom in your local copy. When you think something should be changed or added, then you should raise the concern to get this change in the gatein-dep pom. >>> >>> cheers >>> >>> Julien >>> _______________________________________________ >>> gatein-dev mailing list >>> gatein-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/gatein-dev >> >> >

you prefer BuildTragic ?

On Apr 28, 2011, at 8:12 PM, Matt Wringe wrote: > On Thu, 2011-04-28 at 20:01 +0200, Julien Viet wrote: >> actually https://repository.jboss.org/nexus/content/groups/public/org/gatein/gatei... >> >> >> On Apr 28, 2011, at 8:00 PM, Julien Viet wrote: >> >>> I deployed this pom 1.1.0-Beta02 : https://repository.jboss.org/nexus/content/groups/public/org/gatein/gatei... >>> >>> why don't you see it ? >>> >>> why is now everyone wanting to compile Shindig now :-) ? > > It appears to be available now, the directory was empty when I was > trying to build it a couple of minutes ago. > > I wasn't trying toi build Shindig, the app registry has it as a > dependency, and maven fails if dependencies of dependencies can't be > resolved (I sometimes really hate maven). > >>> On Apr 28, 2011, at 7:43 PM, Matt Wringe wrote: >>> >>>> Can the person responsible for the custom shindig module >>>> (1.0-r790473-Patch06) please update it to not rely on gatein-dep >>>> 1.1.0-Beta02, that version doesn't exist in the repos and is causing the >>>> build to fail. >>>> >>>> Good old maven bringing in multiple dependencies of everything :( >>>> >>>> On Thu, 2011-04-28 at 12:34 +0200, Julien Viet wrote: >>>>> I would like to clarify how now 3rd party should be managed in GateIn trunk, because it has changed implicitly since yesterday (see the another thread of this list). >>>>> >>>>> Now we are trying to handle all 3rd party dependencies in a separate "dependency" oriented pom known as gatein-dep that specifies the version of the library we use in GateIn and its components (although it is less strict for component). This has been existing until now but was not really used, so it's not really something new, what is new is that now we want to use it for real. >>>>> >>>>> This pom is not in the project itself which means that it has a separate lifecycle and any update to the thirdparty should be done here. It may seem a bit heavy but in fact this serve the purpose that updating a lib has often consequences at the integration level of the whole server. So indeed if one version must be changed or added, this should be done in this gatein-dep pom. Actually this helped me to find out dated libraries in gatein that were expected by Shindig at runtime but were not satisfied (now the Shindig fork uses the gatein-dep as it has many dependencies). >>>>> >>>>> The gatein-dep pom can be found here http://anonsvn.jboss.org/repos/gatein/maven/dep/trunk/ >>>>> >>>>> It is integrated in gatein by a declaration in the parent pom: >>>>> >>>>> <dependency> >>>>> <groupId>org.gatein</groupId> >>>>> <artifactId>gatein-dep</artifactId> >>>>> <version>1.1.0-Beta03</version> >>>>> <type>pom</type> >>>>> <scope>import</scope> >>>>> </dependency> >>>>> >>>>> Of course it does not mean you cannot override a version in your own pom when you need to test something like adding a new library or changing a version to test something. Actually this can be done by changing the parent pom in your local copy. When you think something should be changed or added, then you should raise the concern to get this change in the gatein-dep pom. >>>>> >>>>> cheers >>>>> >>>>> Julien >>>>> _______________________________________________ >>>>> gatein-dev mailing list >>>>> gatein-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/gatein-dev >>>> >>>> >>> >> > >