Hi Wendy, I don't have a requirement to build from source, but in the case of the maven plugins, nowhere on the web seems to point to a place where I can download the finished product (aside from letting maven find it, and who knows what other dependencies). I am adverse to letting maven just pull things because then I have a very long list of items to check and verify arranged in a tree, and it's all too easy to miss a subtree and think I've got everything covered. Basically the problem is I make a really crappy computer when it comes to tree-traversals and not losing my place when someone comes over to chat, I go to lunch, or I have to go home at the end of the day. :-) I don't want to trust that I won't make a mistake, I'd rather take a bit more time and let the build system ensure that I didn't miss anything.
If I act as gatekeeper, I know that the project won't build properly until I've applied each dependency required to build the project. (and then same for test... etc). This shouldn't be any more burdensome than finding the transitive dependencies for a good sized ant project, which I've done many times before, except that maven plug-in folks seem to squirrel their stuff away where only maven can find it, so I'm having trouble getting maven working to start with. -Gus -----Original Message----- From: Wendy Smoak [mailto:[email protected]] Sent: Wednesday, May 18, 2011 6:35 PM To: Maven Users List Subject: Re: Bootstraping a repository manager On Wed, May 18, 2011 at 5:21 PM, Heck, Gus (Patrick) <[email protected]> wrote: > I can't seem to find a place to > download something that I can upload directly to artifactory, so I tried > to start with the first plugin that was failing, and build that and see > if mvn deploy would deploy it to artifactory. (First, question... is > that a reasonable idea?) That would be: http://repo1.maven.org/maven2 However it is not going to be fun to find each thing you need and upload it to your internal repository manager. (I work with a company that does it this way.) Especially for plugins. Is there any middle ground? Let the repository manager proxy into a segregated directory, vet everything in there and then move it to the pristine internal repo? > Unfortunately, as soon as I did > > svn checkout > http://svn.apache.org/repos/asf/maven/plugins/tags/maven-clean-plugin-2. > 4.1 maven-clean-plugin > cd maven-clean-plugin > mvn deploy Hmm... first, do you *really* have a requirement to build everything from source? -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] This e-mail and any attachments are intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified any dissemination, distribution or copying of this email, and any attachments thereto, is strictly prohibited. If you receive this email in error please immediately notify the sender and permanently delete the original copy and any copy of any e-mail, and any printout thereof. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
