Why should a developer be forced to set a remote repo up to placate Maven? The company I work for manages remote dependencies via an Anthill build server, whose format does not match up with Maven's strict repo format. So I had to duplicate and manually synch a local Maven repo with the build server. Maven is quite a bit more than a build program; it is truly a build infrastructure. Honestly, this works well when everyone in your development team is on board with it and understands. However, enforcing this infrastructure to simply build an application is too much to shackle a developer with.
-Scott > -----Original Message----- > From: Ralph Goers [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 23, 2006 10:02 AM > To: Jetspeed Users List > Subject: Re: RFC: J2 Build System > > > > Church Michael R wrote: > > > > Maven requires a network connection the first time you build, whether or > not > > you are building from source. Try building and deploying the "simplest > > portlet" example after initial binary installation, when you have no > > internet connection, and see what happens.... > > > > Mike Church > > Software Engineering > > > > > This is completely untrue. It is not maven that is requiring this. It > is your configuration. > > Create a build.properties file in your home directory and then put a > definition for "maven.repo.remote" in it that points to a local maven > repository somewhere on your internal network or on your local machine. > > Ralph > > --------------------------------------------------------------------- > 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]
