Forwarding this as FYI. Tuscany is doing this so it sounds like we'll need to change that soon if we're to keep putting the Tuscany artifacts in the central Maven repository.
...ant ---------- Forwarded message ---------- From: Brian Fox <[email protected]> Date: Sat, Mar 20, 2010 at 8:45 PM Subject: Re: Third party Maven Repository Usage To: general <[email protected]> At the Central repository we are restricting the inclusion of external repositories because this generally creates a mess. This is being enforced on new artifacts coming in so I would recommend you do not add them or your artifacts themselves will end up blocked. A better choice is to encourage the missing dependency projects to get their stuff into Central, or find some compatible libraries that are. On Mon, Mar 8, 2010 at 11:50 AM, Gurkan Erdogdu <[email protected]> wrote: > Hi; > > Is there any rule/policy for using third-party maven repositories in our > project poms? Recently, we have required to list some repositories in > settings.xml (for example: jboss) to our codebase built correctly. But when > Apache-Hudson runs to built daily, it throws errors because of not finding > required repositories. Is it OK to list those repositories in our poms? > > I have just found > http://maven.apache.org/guides/mini/guide-central-repository-upload.htmldocumentation > FAQ and common mistakes section. > > Thanks; > > --Gurkan > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
