> I'm not really sure what the benefit is of being able > to build offline the first time? Once the user builds > the samples once..they can then build offline if > they'd like. > > The way I see it, is that we include in the dist any > AndroMDA modules that we are releasing as well as the > core libs required by these core modules. When the > user builds the samples, the extra libs required by > the samples would just be downloaded by maven like > normal. What do you guys think? Maybe I'm missing > something, but to me it doesn't make sense to bundle > all the libs used by our samples. >
Although I understand Matthias' request, I have to say I agree with Chad. It will introduce only more complexity to be able to build offline the first time. Anyway, someone who is ready to build AndroMDA from the sources will surely be happy to download the dependencies separately into his local Maven repository during the first build. I see this feature as an advantage (small src bundle footprint, easy when you are already using maven: maybe you'll already have some of the dependendies, ...). Why don't we meet in the middle ? We could make a bundle available which basically is a zip file containing the library dependencies. This one would be quite big, but users who want to build offline for some reason, would simply download a copy of this lib too. So it would be what Matthias wants, only in a separate bundle. What do you think ? Wouter. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Andromda-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
