On 4/24/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > On 4/24/06, Brandon Goodin <[EMAIL PROTECTED]> wrote: > > "tons of advantages" - please quantify this. > > Well distributing internal corporation dependencies and managing the > version, especially nightly build is way easier using Maven repository > capabilities. Managing your project dependencies version is also > really easier (especially conflicts and snapshots). > > All the Maven generated reports also work better with regular > dependencies because they can find some metadatas to work with. > > > > > Personally, I find the repository to be a "nice" piece of Maven. But, > > I don't see it as a cardinal sin to actually distribute libraries in > > your project. If you follow the libary naming convention then who > > cares? > > > > Personally, what i find annoying are the copious additional, needless, > > and redundant dependencies that i have to download because of the > > dependencies defined in the pom of a jar that i need to download. > > Nothing the exclude tag can't fix. > > > I also find it annoying to have to manually install several small > > libraries to my local repo cuz i can't distribute them as a result of > > licensing. It is additionally annoying to have to setup a jar > > repository that will be used for jars that will be needed that can > > only be distributed privately. All of this... vs. me just referencing > > them in my source tree? > > > > You are making this sound like it is a lot of work. Manually > installing files on a corporate repository using install:install-file
wanted to say deploy:deploy-file > usually doesn't take more time then checking them inside SVN. A maven > repository is basically a Jar versionning systems. > > > I like Maven a lot and really enjoy the standard project layout > > features and plugins that are provided. But, the jar repository has > > caused me more time and less efficiency. However, i do like ibiblio > > for a single one stop shop for grabbing jars i need... to drop in my > > source tree ;-) > > > > I like it when people can check out my source from SVN and simply > > build. This is possible when i place them in SVN. Heck, I can even > > check Sun Jars into my SVN repo! ;) > > If you have a remote Maven repository on the same server as your SVN > repo, I really don't see the difference. > > > > > Thanks to everyone for pointing me in the direction of the system. > > I'll be using it. I'm always open to a compelling argument and a tap > > on the forehead that helps me to see the light. > > > > Many Thanks, > > Brandon > > > > On 4/24/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > > > Well you can use *system* dependencies but you loose tons of > > > advantages. Instead, maybe you should just populate your local > > > repository using the install plugin and -o to run mvn offline. > > > > > > On 4/24/06, Brandon Goodin <[EMAIL PROTECTED]> wrote: > > > > Is it a requirement that i use the remote repository for jars? Is > > > > there a way to reference jars that are distributed with the code when > > > > checked out from the code repository? > > > > > > > > Brandon > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
