You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Godschall, John" <JG...@firstmarblehead.com> on 2011/03/29 19:06:39 UTC
Procedure for updating Internal Repo with 3rd party
Hi
What's the best procedure for uploading 3rd party artifacts to an internal repository.
This doc explains how to update the local cached repository but not a central internal repository.
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html
I have used the depoy:deploy-file plugin but this does not seem to include the pom, the md5 and sha1 files.
In addition, some projects have a parent pom structure as well.
I currently do not use a Repository Manager and am looking for a generic way to perform this task.
Here is an example of what I would like to upload to my central repostory
Directory of c:\internal_repo1\javax\mail\mail\1.4.2
mail-1.4.2-sources.jar
mail-1.4.2-sources.jar.md5
mail-1.4.2-sources.jar.sha1
mail-1.4.2.jar
mail-1.4.2.jar.md5
mail-1.4.2.jar.sha1
mail-1.4.2.pom
mail-1.4.2.pom.md5
mail-1.4.2.pom.sha1
maven-metadata.xml
maven-metadata.xml.md5
maven-metadata.xml.sha1
Please note that this repository already have previous versions so and I would like to make sure it's metadata files are updated correctly in the parent directory.
Ie:
Directory of c:\internal_repo1\javax\mail\mail
<DIR> 1.3.1
<DIR> 1.3.2
<DIR> 1.3.3
<DIR> 1.3.3_01
<DIR> 1.4
maven-metadata-local.xml
maven-metadata.xml
maven-metadata.xml.md5
maven-metadata.xml.sha1
thanks
*This e-mail and any attachments may contain content protected
under federal law and is also confidential and proprietary in nature.
If you received this message in error, please notify the sender
immediately and delete the original and destroy all copies of the
message and any attachments. Any other use of this e-mail by you
including retaining, using, copying, distributing, or otherwise
disclosing this information in any manner is prohibited.
Re: Procedure for updating Internal Repo with 3rd party
Posted by Ron Wheeler <rw...@artifact-software.com>.
Get your Nexus up and running (local or on a shared server) and then
read the Nexus docs.
Loading 3rd party lists is easy to do and everyone has to do it because
of the ORACLE/Sun licensing policies so you will have lots of friends
and lots of docs on the repo side.
It is not really a Maven problem. The Nexus forum is the best place for
these questions.
Nexus is free and makes Maven actually productive and the whole process
a lot more transparent.
Ron
PS: The other repo systems may be just as good but I can vouch for Nexus.
On 29/03/2011 3:28 PM, Wendy Smoak wrote:
> On Tue, Mar 29, 2011 at 1:06 PM, Godschall, John
> <JG...@firstmarblehead.com> wrote:
>
>> I have used the depoy:deploy-file plugin but this does not seem to include the pom, the md5 and sha1 files.
>> In addition, some projects have a parent pom structure as well.
> Can you paste the command you used, and what happened? There is an
> option to generate the pom, or to provide it if you have one for the
> artifact already.
>
> http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
>
>> I currently do not use a Repository Manager
> Well, there's the real solution. ;) Why not? You can run it locally
> and point to http://localhost instead of (I assume)
> file:///internal_repo1 .
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Procedure for updating Internal Repo with 3rd party
Posted by Wendy Smoak <ws...@gmail.com>.
On Tue, Mar 29, 2011 at 1:06 PM, Godschall, John
<JG...@firstmarblehead.com> wrote:
> I have used the depoy:deploy-file plugin but this does not seem to include the pom, the md5 and sha1 files.
> In addition, some projects have a parent pom structure as well.
Can you paste the command you used, and what happened? There is an
option to generate the pom, or to provide it if you have one for the
artifact already.
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
> I currently do not use a Repository Manager
Well, there's the real solution. ;) Why not? You can run it locally
and point to http://localhost instead of (I assume)
file:///internal_repo1 .
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org