I just offered an advice based on my own experience nothing more :) Cheers Daniel
On Mon, Jan 10, 2011 at 3:48 AM, Benson Margulies <bimargul...@gmail.com> wrote: > Gang, > > Please be clear about when you are offering advice to podlings and > when you are conveying policy. The people in the podlings get > justifiably rattled when they get email that seems to suggest that > they are somehow not following some rule that isn't, apparently, > written down anywhere. > > --benson > > > On Sun, Jan 9, 2011 at 8:05 PM, Michael MacFadden > <michael.macfad...@gmail.com> wrote: >> There are additional benefits to dependency management systems like Maven or >> Ivy as well. Beyond avoiding checking in jar files, you can reference a >> dependency once and not have to proliferate references if you have multi >> module builds (with multiple build files). Also, if your project gets >> separated into multiple modules, then the build system can actually mange >> internal dependancies. >> >> Of course checking Jars in to SVN is usually simpler in the short term. >> >> ~Michael >> >> On Jan 9, 2011, at 4:55 PM, dsh wrote: >> >>> s/way/idea/ >>> >>> On Mon, Jan 10, 2011 at 1:54 AM, dsh <daniel.hais...@googlemail.com> wrote: >>>> Hi, >>>> >>>> I'd suggest to consider dependency management systems such as Apache >>>> Maven or Apache Ivy as an advantage in the long run. They allow to >>>> precisely document your dependencies and both support an offline mode. >>>> Additionally both of course provide a very reliable way to define >>>> exactly what version of what jars are required and ensure everyone has >>>> the same ones. >>>> >>>> So don't put the way aside to migrate to a dependency management >>>> system as soon as possible. >>>> >>>> Cheers >>>> Daniel >>>> >>>> On Mon, Jan 10, 2011 at 1:46 AM, Alex North <ano...@google.com> wrote: >>>>> The Wave project also has jars in its repository (on its way to Apache >>>>> SVN). >>>>> That seems to be the most reliable way to define exactly what version of >>>>> what jars are required and ensure everyone has the same ones. >>>>> >>>>> On 10 January 2011 11:16, Grant Ingersoll <gsing...@apache.org> wrote: >>>>> >>>>>> This seems a bit over the top. I prefer them in SVN so I can get them >>>>>> all >>>>>> at once, which is especially nice when one is working offline. >>>>>> >>>>>> On Jan 9, 2011, at 5:53 PM, sebb wrote: >>>>>> >>>>>>> I've just noticed that there are lots of jars stored in SVN under >>>>>>> >>>>>>> >>>>>> http://svn.apache.org/repos/asf/incubator/lcf/branches/release-0.1-branch >>>>>>> >>>>>>> AIUI, SVN should not be used for storing library jars. >>>>>>> >>>>>>> == >>>>>>> >>>>>>> The way other projects manage this is to define the jar dependencies >>>>>>> in a build file, and get the build process to download the jars. >>>>>>> >>>>>>> If using Maven, this is trivial, as declared dependencies are >>>>>>> automatically downloaded. >>>>>>> >>>>>>> It's not that difficult when using Ant either - see for example the >>>>>>> Tomcat or JMeter projects. >>>>>>> >>>>>>> There is also an Ant Maven task: >>>>>>> http://maven.apache.org/ant-tasks/examples/dependencies.html >>>>>>> >>>>>>> and Apache Ivy >>>>>>> http://ant.apache.org/ivy/ >>>>>>> >>>>>>> though I've not used either of those. >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>>>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>>>> >>>>>> >>>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
