Yes, you are right. I don't think the deploying has much to do with Proximity because Proximity doesn't yet support uploading. We are using IIS ftp server to handle deploying to Proximity's repos.
My question was a general one...of how to do a private build/release of public artifacts that you wish were already public but aren't so you have to make it public for our company's developers. -dh -----Original Message----- From: Tamás Cservenák [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 8:11 AM To: Maven Users List Subject: Re: How to deploy artifacts and its dependencies into a local proxy/repo? Hi Dave, it seems to me that you have no problem with _DEPLOYING_ to Proximity in general, right? Correct me if i'm wrong. (sigh) I have no experience with IDEA and building it's plugin..... I assume this question regards building IDEA plugin in general? ~t~ On 8/30/06, Dave Hoffer <[EMAIL PROTECTED]> wrote: > > Often, it seems, we have a need to use custom built public maven2 > plug-ins with our current maven2 projects. An example of this is the > IDEA plugin. We need to use 2.1-SNAPSHOT because the latest released > version 2.0 has several limitations that make it unusable. These > limitations have been fixed a long time ago in the IDEA plug-in trunk so > this is what we need to use. > > > > Now what would be ideal; is for this to be released. Second best would > be for the IDEA developers to make publicly available snapshot releases. > But this is a different story...assuming these can't be done I need to > build the source and put it in our proxy (Proximity) server so it is > available to all developers. > > > > If I get the source and run the maven install goal on each developer > system, all is fine. The install puts it in the user's local repo and > they can use it just fine. However, I want to deploy it so all don't > need to do this. > > > > If I run the deploy goal on the single IDEA artifact it doesn't work. I > think this is because the IDEA plug-in has lots of dependencies that the > deploy command line goal doesn't know about...it just deploys one > artifact. > > > > If I try to modify the IDEA source project pom files to point to my > distributionManagement repositories, that doesn't work either. I get > some build error when I run the deploy goal on the IDEA pom. I don't > know what the issue here is but there are lots of parent poms and it is > likely I missed something. In any case, this doesn't 'seem' like the > right way to do this. > > > > What is the right way to deploy the IDEA plug-in locally into my shared > corporate repo? > > > > -dh > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
