Thanks, everyone, for your suggestions, but I haven't got the answer that I'm 
looking for...

At 3:40 PM -0500 11/22/04, Thompson, Bryan B. wrote:
>I generally describe non-maven jars in a <dependency>, specify the full
>jar name in <jar>, and then just drop them into the appropriate subdir
>on my local repository.


I want to put the files in our private "central" repository so other people on 
the team can get them.  I'm


At 9:48 PM +0100 11/22/04, Mark Lowe wrote:
>i just build on the remote
>server and it builds the respoitory for me (i set the directory to
>/www/maven (or the equivalent). The local repository on the staging
>server is the same as when it acts as our remote repository.

We can't build on the repository machine.  I want to build on a designated  
build machine  and then deploy to our internal, remote maven repository.

At 3:52 PM -0500 11/22/04, Eric Giguere wrote:
>2- for those of unknown source and/or version, deploy them on your internal 
>repository and give them whatever version number you feel giving it.

What did you use to upload to the local remote repository?

Basically, what I'm looking for is a way to read a list of jars from an XML (or 
text) file and upload them to our remote maven repository.  The artifact:deploy 
tag is problematic because it requires a POM, which requires that we create a 
project.xml for each jar, which IMHO is overkill.

Perhaps I could use the repository:copy-jar goal inside a forEach loop to copy 
each one up:

FOREACH blah, blah
<j:set var="artifact" value="${maven.build.dir}/downloads/flux-2.2.jar" />
<j:set var="groupId" value="flux" />
<attainGoal name="repository:copy-jar"/>
END-FOREACH

Does this make sense?

Thanks,

Sean


-- 
---------------------------------------------------------------------------
M. Sean Gilligan                    : 831-466-9788 x11
vBlog Central                       : http://www.vblogcentral.com
---------------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to