Nexus has to connect for the first download of a specific artifact. But it's going to be much faster for the second access (for that artifact). A Maven repo manager is a normal part of a maven infrastructure nowadays. Or at least should be.
/Anders On Fri, Jan 29, 2010 at 13:27, maven apache <[email protected]> wrote: > 2010/1/29 Anders Hammar <[email protected]> > > > The Nexus book talks about all these questions: > > http://www.sonatype.com/books/nexus-book/reference/ > > > > Thanks, I have tried the nexus, in fact I have heard it before, and I use > it this afternoon. > You said it can solve the speed problem in the IDE for updating > dependency,however I found the nexus just acted as a bridge between the > proxy repo and the remote repo, when updating dependency, it also connect > to > the remote repo which is a time-cousuming work. > So,it is my configration or something else? > > > /Anders > > > > On Fri, Jan 29, 2010 at 09:17, maven apache <[email protected]> > > wrote: > > > > > 2010/1/29 Anders Hammar <[email protected]> > > > > > > > Well, this is the good thing about m2eclipse. It uses the pom as > > master. > > > > A repo manager (Nexus for example) will solve your network problems. > > > > > > > Nexus is to be used for building private maven repository, and I just > > make > > > some mirrors (for example ,create a proxy repo for the central) in the > > > setting.xml. > > > So I wonder if I have to create proxy repo for each repo defined in the > > > project using nexus? And then config the releated mirror in the > > > setting.xml? > > > > > > > > > However in a maven project, there always too many repo defined, is it > > > necessary ? > > > > > > > > > > > /Anders > > > > > > > > On Fri, Jan 29, 2010 at 02:28, maven apache <[email protected]> > > > > wrote: > > > > > > > > > 2010/1/28 Anders Hammar <[email protected]> > > > > > > > > > > > You should use m2eclipse. You want to have one dev environment > > setup, > > > > not > > > > > > having to manage two separate ones - the POM should be the > master. > > > And > > > > > you > > > > > > would get many nice features like dep graphs and easier > management > > of > > > > > your > > > > > > deps. > > > > > > > > > > Yes, it is true,I can check the dependency more clearly, However > > there > > > is > > > > a > > > > > rather unbearable problem, m2eclipse will update the maven > dependency > > > as > > > > > soon as I modify the pom(most time I just config some plugins > rather > > > add > > > > or > > > > > remove the dependency),and if the web connecttion is bad or some > > > artifact > > > > > is > > > > > not available, it will take too long. > > > > > > > > > > > And eventuelly you'll also get much fast builds (incremental > > builds, > > > > > > already partly in place in 0.9.9-dev). And, maybe most > importantly, > > > the > > > > > > maven configuration and eclipse configuration will be synced. > We're > > > not > > > > > > there yet though, but I believe we will be for the major plugins > in > > > > v1.0 > > > > > of > > > > > > m2e. > > > > > > > > > > > > But make sure you use the latest 0.9.9-dev build, not v0.9.8 of > > m2e. > > > > > > > > > > > > /Anders > > > > > > > > > > > > On Thu, Jan 28, 2010 at 10:22, maven apache < > > [email protected]> > > > > > > wrote: > > > > > > > > > > > > > BTW, do you think it is a good idea to use m2eclipse? or other > > IDE > > > > > > > integrate > > > > > > > with maven? > > > > > > > > > > > > > > Beacuse I found if I work without m2eclipse, each I edit the > pom, > > I > > > > > > should > > > > > > > use mvn eclipse:eclipse to update the .classpath ,however the > > > > m2eclipse > > > > > > > work > > > > > > > rather slowly.... :(. > > > > > > > How about your? > > > > > > > > > > > > > > 2010/1/28 Anders Hammar <[email protected]> > > > > > > > > > > > > > > > I also see that they add other repositories in their pom. A > > total > > > > > > mess... > > > > > > > > > > > > > > > > /A > > > > > > > > > > > > > > > > On Thu, Jan 28, 2010 at 10:05, Stephen Connolly < > > > > > > > > [email protected]> wrote: > > > > > > > > > > > > > > > > > Correct, based on their pom.... this is one of those > examples > > > of > > > > > why > > > > > > it > > > > > > > > is > > > > > > > > > a > > > > > > > > > bad plan to add dependencies in a profile that is activated > > > based > > > > > on > > > > > > > the > > > > > > > > > build JDK and/or OS > > > > > > > > > > > > > > > > > > 2010/1/28 maven apache <[email protected]> > > > > > > > > > > > > > > > > > > > 2010/1/28 Anders Hammar <[email protected]> > > > > > > > > > > > > > > > > > > > > > Here you go: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://repo1.maven.org/maven2/org/apache/rampart/rampart-project/1.4/rampart-project-1.4.pom > > > > > > > > > > > > > > > > > > > > > > I didn't look closely enough. The JDK1.4 profile is > > active > > > by > > > > > > > > default, > > > > > > > > > do > > > > > > > > > > > as > > > > > > > > > > > you're NOT using JDK 1.5 that profile is not going to > > kick > > > > in. > > > > > > > > > > > > > > > > > > > > > Oh, my fault, I did not check it clearly enouth. > > > > > > > > > > You mean not matter which jdk I use( configed in the > > compile > > > > > > > version?), > > > > > > > > > as > > > > > > > > > > long as the version is not 1.5(for my case , it is 1.6), > > the > > > > > jdk14 > > > > > > > > > profile > > > > > > > > > > will be actived? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > /Anders > > > > > > > > > > > > > > > > > > > > > > On Thu, Jan 28, 2010 at 09:30, maven apache < > > > > > > > [email protected]> > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > 2010/1/28 Anders Hammar <[email protected]> > > > > > > > > > > > > > > > > > > > > > > > > > You're building with JDK 1.4, not JDK 1.5. > > > > > > > > > > > > > > > > > > > > > > > > How? I did not sepcify 1.4 or .1.5. > > > > > > > > > > > > In the parent pom of my project I config the compile > > > > version > > > > > to > > > > > > > > 1.6, > > > > > > > > > > and > > > > > > > > > > > my > > > > > > > > > > > > eclipse are using jdk1.6_18 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > There are profiles in the pom of > > > > > > > > > > > > > > > > > > > > > > > > > > org.apache.rampart:rampart-policy:jar:1.4 > > > > > > > > > > > > > > > > > > > > > > > > > > (Actually, the profiles are in the parent of that > > > > project). > > > > > > > > > > > > > > > > > > > > > > > > > Yes, I know this, I have check the pom. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > The homepage which you refer to isn't telling the > > > > complete > > > > > > > > truth... > > > > > > > > > > > > > > > > > > > > > > > > > > /Anders > > > > > > > > > > > > > On Thu, Jan 28, 2010 at 09:15, maven apache < > > > > > > > > > [email protected]> > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi: > > > > > > > > > > > > > > I found a strange problem, it seems that maven > may > > > > > download > > > > > > a > > > > > > > > > wrong > > > > > > > > > > > > > version > > > > > > > > > > > > > > for a transitive dependency. > > > > > > > > > > > > > > Details can be found here : > > > > > > > > > > > > > > http://dpaste.com/151511/ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
