Yes you are absolutely right. Yes currently it's hard for debugging as we don't know which version of JAR is breaking the Environment.
that's the reason we want to move with Maven we can know our artifact build version and believe me it's very hard to change these things when you have more then 100 products live :-) That's why we come up with a solution at this moment to create some mock-up URL, Which Maven is looking for and once things are good and everybody is happy :-) i mean each team :-) then we can get approval to move with MAVEN. Thanks a lot for all your help again. -daivish. On Mon, Jul 25, 2011 at 1:01 PM, Ron Wheeler <rwhee...@artifact-software.com > wrote: > > On 25/07/2011 3:47 PM, Wayne Fay wrote: > >> Yes I agree with Nexus, But the only concern in choosing Nexus is we have >>> to >>> daily copy our latest JAR files from Existing location to New location >>> for >>> Even 1 Project. As so many dependency on those Jar files and which are >>> daily >>> updating. So we have to daily Update the new Nexus location too. >>> >> Arguably, this can be easily handled with a simply cron job which >> calls mvn deploy:deploy-file across files in various directories where >> your artifacts currently live. >> >> Wayne >> > Good solution. > You also should only be copying the released versions of libraries rather > that the daily snapshots. > You need some stability in the dependencies of your projects otherwise you > have a heck of a time debugging the project. > > It sounds like your current system makes it very hard to know the pedigree > of any artifact that you build. > Maven and Nexus should move you towards a way of life that is more aware of > releases, SNAPSHOTS and stuff that somebody is working on. (I don't want to > use any of the last type and usually prefer an older version of the first > type to a current SNAPSHOT unless I absolutely need the latest thing that > only the SNAPSHOT includes.) > > Ron > > > ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> users-unsubscribe@maven.**apache.org<users-unsubscr...@maven.apache.org> >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >> > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@maven.**apache.org<users-unsubscr...@maven.apache.org> > For additional commands, e-mail: users-h...@maven.apache.org > >
