anywhere a "copy" function. Is there a way to
> export/import
> or something like that to replicate data from production to my test
> environment.
>
> Thanks
> Jirong
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/How-to-replicate
:
http://maven.40175.n5.nabble.com/How-to-replicate-company-internal-repository-tp5663623p5669083.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
.n5.nabble.com/How-to-make-a-company-internal-repository-td5652959.html
>
> As it seems quite different than the question you are asking
> here.it is about copying stuff from Central, something that defies
> the purpose of proxy at start.
>
>
> Thanks,
> ~t~
>
> On
You refer to this mail?
http://maven.40175.n5.nabble.com/How-to-make-a-company-internal-repository-td5652959.html
As it seems quite different than the question you are asking
here.it is about copying stuff from Central, something that defies
the purpose of proxy at start.
Thanks,
~t~
On
> I tried this list, it's not active.
>
> http://maven.40175.n5.nabble.com/Nexus-Maven-Repository-Manager-Users-List-f127899.html
It is active, just not as active as you might like, or perhaps you
didn't get a reply to your question yet for some reason. That in't
sufficient justification to ask yo
nexus professional allows you to replicate across nodes.
Or you can do rsync between nodes.
-D
On Wed, Apr 25, 2012 at 10:28 PM, Manfred Moser wrote:
> On Wed, April 25, 2012 7:23 pm, hujirong wrote:
>> I tried this list, it's not active.
>>
>> http://maven.40175.n5.nabble.com/Nexus-Maven-Repos
On Wed, April 25, 2012 7:23 pm, hujirong wrote:
> I tried this list, it's not active.
>
> http://maven.40175.n5.nabble.com/Nexus-Maven-Repository-Manager-Users-List-f127899.html
Not true. It is just fine. In terms of replicating your nexus..
You could just copy the sonatype work nexus folder to t
The current company one is created by another group. It's production one. Our
group wants to use the same approach but need some time to try out.
Jirong
--
View this message in context:
http://maven.40175.n5.nabble.com/How-to-replicate-company-internal-repository-tp5663623p5666517.html
I tried this list, it's not active.
http://maven.40175.n5.nabble.com/Nexus-Maven-Repository-Manager-Users-List-f127899.html
--
View this message in context:
http://maven.40175.n5.nabble.com/How-to-replicate-company-internal-repository-tp5663623p5666516.html
Sent from the Maven - Users ma
> We use a internal Nexus repository. Now I want to set up an isolated test
> environment. What's the best way to replicate the whole internal repository
> into my Nexus?
I read this as "...Nexus... Nexus... Nexus..."
Why are you asking this here? Please use the Nexus Use
On 24/04/2012 8:59 PM, hujirong wrote:
Hi
We use a internal Nexus repository. Now I want to set up an isolated test
environment. What's the best way to replicate the whole internal repository
into my Nexus?
Why?
What are you trying to do with a separate repo?
Ron
Thanks
Jirong
--
View
Hi
We use a internal Nexus repository. Now I want to set up an isolated test
environment. What's the best way to replicate the whole internal repository
into my Nexus?
Thanks
Jirong
--
View this message in context:
http://maven.40175.n5.nabble.com/How-to-replicate-company-internal-repos
>
> myISR
> file:///export/home/buildmaster/.m2/repository/
As I suspected, this is all horribly wrong. The ~/.m2 directory is
merely a repo CACHE. It DOES NOT function as a repository. Stop trying
to make this work. It does not and should not (metadata is different
among other things as you have
I tried declaring the local repository in the settings.xml file but that
resulted in the same error so I tried explicitly listing the repository
in the pom.xml 'repositories' section. Here is a cut/paste from my
pom.xml.I'm running the mvn install command from the same machine as
the r
> Thanks for the response. The parent .pom file is in the following
> directory - does the repository declaration need to be explicit to the
> module folder level? If so, how does it find different files within the
> repository?
I don't understand your questions. I don't have a "repository
d
Hi Wayne,
Thanks for the response.The parent .pom file is in the following
directory - does the repository declaration need to be explicit to the
module folder level?If so, how does it find different files within
the repository?
/export/home/buildmaster/.m2/repository/com/storagetek/V
This is your problem:
> Could not find artifact
> com.storagetek:VOP_MAVEN-parent:pom:1.0 in myISR
> (file:///export/home/buildmaster/.m2/repository/)
This means there is no pom file corresponding to this artifact in your
repository. Whatever process you used to put those files into your
repo has
Hi All,
Complete newbie to Maven and newbie to build environments in
general. Using maven to build an internal project with the idea of
automating builds once I get things going. I originally started with
building the project using Maven inside of Netbeans which I was
eventually succe
I am a big fan of Nexus.
It makes Maven actually fun to use.
We used it with a very small team of 4 people.
My only regret is that we did not install it as soon as we started with
Maven. It would have saved a lot of grief.
The free version works very well. We have had absolutely no problems
with
Here, we often install nexus under a standard tomcat install, and it just
works, sometimes sharing with Jenkins.
Seems not to be a problem, compared to other heavy-weights like the ones
from a major Java Tools supplier I wouldn't dare to name here, which end up
needing to use a full, stand-alone i
Barrie,
Thanks for the quick reply.
When I said "shared server", I meant that we want to have multiple
applications on the same server - repository application will be one of
them. I don't know what we will be putting on this server, yet, but one
thing is for sure, it has to multi task. Based on
On Thu, Jul 7, 2011 at 12:59 PM, Niranjan Rao wrote:
> Hi folks,
>
> I have been researching options for setting up internal maven repository
> - free software. Based on my research it seems like nexus is most
> recommended choice.
>
> Wondering if people here have any opinions/suggestions.
Nexus
Hi folks,
I have been researching options for setting up internal maven repository
- free software. Based on my research it seems like nexus is most
recommended choice.
Wondering if people here have any opinions/suggestions.
Ours is a small setup with less than 20 developers. Ideally we would
l
>> On Mon, Jan 24, 2011 at 5:41 AM, Anders Hammar wrote:
> We do this by building jars that aggregate our 3rd party dependencies once
> per release so we know exactly what transitive dependencies are going to be
> used by the developers.
If you are running maven for some time, I won't surprised if
On 24/01/2011 6:28 PM, Guo Du wrote:
On Mon, Jan 24, 2011 at 5:41 AM, Anders Hammar wrote:
You could be somewhat aided by the procurement feature of Nexus Pro (the
commercial edition of the Nexus repo manager):
http://www.sonatype.com/books/nexus-book/reference/procure.html
Looked at the link,
On Mon, Jan 24, 2011 at 5:41 AM, Anders Hammar wrote:
> You could be somewhat aided by the procurement feature of Nexus Pro (the
> commercial edition of the Nexus repo manager):
> http://www.sonatype.com/books/nexus-book/reference/procure.html
Looked at the link, Procured Development Repository[1]
On Mon, Jan 24, 2011 at 2:31 AM, Ron Wheeler
wrote:
> 1. Developer enables the access to internal repository(Nexus or other).
Internal repository is isolated from external even with nexus. This is
the main point of this work flow. Imaging with transparent proxy to
maven central, developer co
gt; checksum/javadoc/sources/license/lawyer, once passed those check, then
> deployed to internal maven repository to build into product. Internal
> repository is isolated from external repository for various reason.
>
> A typical work flow will be:
> 1. Developer enable the
1. Developer enables the access to internal repository(Nexus or other).
2. Developer add new dependencies as artifacts/plugins which available
from external repository.
3. Developer test the new pom setup and it works on local machine
4. Maven and Nexus will automatically load new dependencies
check, then
deployed to internal maven repository to build into product. Internal
repository is isolated from external repository for various reason.
A typical work flow will be:
1. Developer enable the access to external repository.
2. Developer add new dependencies as artifacts/plugins which
The link earlier in this thread.
/Anders (mobile)
Den 2010 8 20 09:50 skrev "Naresh" :
>
> Which instructions Sir ?
>
> I am confused here ?
>
> --
> View this message in context:
http://maven.40175.n5.nabble.com/How-to-force-Maven-to-use-the-internal-repositor
Which instructions Sir ?
I am confused here ?
--
View this message in context:
http://maven.40175.n5.nabble.com/How-to-force-Maven-to-use-the-internal-repository-tp2641805p2641858.html
Sent from the Maven - Users mailing list archive at Nabble.com
-------
>
> **
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/How-to-force-Maven-to-use-the-internal-repository-tp2641805p2641846.h
//maven.40175.n5.nabble.com/How-to-force-Maven-to-use-the-internal-repository-tp2641805p2641846.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
s
On Fri, Aug 20, 2010 at 07:22, Naresh wrote:
>
> Hi Experts,
>
> I have configured parent pom.xml to use the internal repository which i
> have
> created it with apache Archiva. My Pom looks like
>
> < distributionManagement>
>
> < repository>
>
>
Hi Experts,
I have configured parent pom.xml to use the internal repository which i have
created it with apache Archiva. My Pom looks like
< distributionManagement>
< repository>
< id>internal< /id>
< url>dav:http://x.x.x.x:9090/archiva/repository/
would recommend to follow the recomandations of the other post.
Kind regards
Karl Heinz Marbaise
--
View this message in context:
http://old.nabble.com/-internal-repository--How-to-use-relative-path-in-the-declaration-of-repository-tp28751349p28752713.html
Sent from the Maven - Users maili
hat on the Internet).
4. Remove the repositories section which points at your local file syste,
5. You should be all set to use Maven the way it is meant to be used.
/Anders
On Wed, Jun 2, 2010 at 10:03, NGUYEN Cong Kinh <
cong_kinh.ngu...@it-sudparis.eu> wrote:
> Hi everybody,
>
Hi everybody,
I have a problem with deploying an internal repository. In fact, I have
some modules as the following:
- module A
+ module A1
+ module A11
+ pom.xml
+ src
+ libs
+ module A12
+ module A2
In the module A11, I
] On Behalf Of Ron Wheeler
Sent: Tuesday, June 01, 2010 10:38 AM
To: users@maven.apache.org
Subject: Re: Internal Repository Advice
I got the Nexus free version.
It is the only way to use maven effectively.
We used maven for 2 years without a repository and in retrospect it was
the one of the worst
kins wrote:
I'm moving my companies projects to Maven and need an internal repository.
I hesitated to use something like Artifactory because I thought a
simple directory structure, under Apache, would be sufficient (did it
that way back in the Maven1 days).
However, I'm having troubl
> I'm moving my companies projects to Maven and need an internal repository.
>
> I hesitated to use something like Artifactory because I thought a
> simple directory structure, under Apache, would be sufficient (did it
> that way back in the Maven1 days).
>
> However, I&
Today, I think the ones to choose from are nexus and artifactory. They are
easy to use, still they have the most features. I believe that the
development on archiva is slow (although it does what it is supposed to).
/Anders
Den 1 jun 2010 16.23, "Shan Syed" skrev:
Artifactory, Nexus, and Archiv
jects to Maven and need an internal repository.
>
> I hesitated to use something like Artifactory because I thought a
> simple directory structure, under Apache, would be sufficient (did it
> that way back in the Maven1 days).
>
> However, I'm having trouble deploying projects (po
I'm moving my companies projects to Maven and need an internal repository.
I hesitated to use something like Artifactory because I thought a
simple directory structure, under Apache, would be sufficient (did it
that way back in the Maven1 days).
However, I'm having trouble deployin
To: Maven Users List
Subject: RE: Using archetype:generate with internal repository
Hello Sagara,
That really helped, thank you. I had to do a bit of digging but I
finally got it.
One question though. If I do mvn archetype:generate
-DarchetypeCatalog=http://url it works fine, but if I do the
am I doing wrong?
Shahzad Qureshi
Systems Analyst/Programmer
Applications Directorate, CIOB
Environment Canada
shahzad.qure...@ec.gc.ca
-Original Message-
From: Sagara Gunathunga [mailto:sagar...@gmail.com]
Sent: Tuesday, March 17, 2009 1:05 AM
To: Maven Users List
Subject: Re: Using a
Hi Shahzad,
Do you have archetype-catalog.xml file on your internal repository ?
,it is required to have a archetype-catalog.xml file to get Archetype
information for Maven Archetype Plug-in. please see the [1]
[1] -
http://maven.apache.org/plugins/maven-archetype-plugin/specification
Hi all,
I am having difficulty using archetype:generate plugin where I want it
to use an archetype stored in our internal repository. I was able to do
so using archetype:create plugin. I've a settings.xml in .m2 directory
and that's where archetype:create reads the internal repository
i
Hi,
Looks like you are failing on the different repo id/same repo url issue
(see:
http://wiki.jfrog.org/confluence/display/RTF/Configuring+Artifacts+Resolution,
bottom of the page). The corresponding server output would provide more
info.
Anyway, it's better to ask artifactory-specific questions o
Hi,
can you help me what's wrong with my configuration for deploying app to
JFrog artifactory?
On jfrog artifactory I have repository myAppsRepository.
I use eclipse 3.4 (but on the command line it's the same problem), maven
2.0.9
settings.xml
myRemoteRepository
user
p
e talking out a hole but check this out...>>The release version along
>with version range information comes from metadata... if you created>your
>internal repository in a way other than using the deploy plugin then you won't
>have metadata.>If you are copying your
I may be talking out a hole but check this out...
The release version along with version range information comes from metadata...
if you created your internal repository in a way other than using the deploy
plugin then you won't have metadata. If you are copying your local repository
ak
Hello,
I'm having difficulties getting the maven-archetype-plug-in to work with an
internal repository. The problem seems to be that it cannot locate the RELEASE
version of this plugin when given an internal repository. I've copied the error
I get to the end of this email togeth
Hi Rick,
If you're using an internal repository, you should not define other
repositories inside your settings.xml. You really better want to do this
configuration inside your internal maven repository manager. This might be
one of the causes of your problems.
But also note that you
Use the offline flag
On Tue, Dec 30, 2008 at 1:31 PM, Rick wrote:
> I've googled this and tried to search the archives but it's hard to
> get a direct hit.
>
> We are using an internal repository but if for some reason that
> repository goes down, isn't there a
I've googled this and tried to search the archives but it's hard to
get a direct hit.
We are using an internal repository but if for some reason that
repository goes down, isn't there a way the maven build can still
proceed using the files in the user's local repository (as
You may need to elaborate on your set up, as you can see here it is
possible to deploy them together for build #2:
http://snapshots.repository.codehaus.org/org/codehaus/redback/redback-users-api/1.1-SNAPSHOT/
That was built using the release profile in this pom:
http://svn.codehaus.org/redback/red
So I've just noticed that while we're installing snapshots, if you don't
explicitly tell maven to NOT use a unique snapshot number AND you have
say 4 generated artifacts you're installing, the metadata reflects the
last one installed.
For example, if you have a project that generates:
1 - a
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 23, 2008 3:46 PM
To: Maven Users List
Subject: Re: Internal repository question - stopping repo1
You need a to set up a mirror pointing to your local repo as a
* in your settings.xml file, and Maven will only go
to that server for all of its files
lease notify me immediately by replying to the
message and deleting it from your computer. Thank you.
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 23, 2008 7:19 PM
To: Maven Users List
Subject: Re: Internal repository question - stopping repo1
In
unication is strictly prohibited. If you have received this
> communication in error, please notify me immediately by replying to the
> message and deleting it from your computer. Thank you.
>
> -Original Message-
> From: Wayne Fay [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April
To: Maven Users List
Subject: Re: Internal repository question - stopping repo1
You need a to set up a mirror pointing to your local repo as a
* in your settings.xml file, and Maven will only
go to that server for all of its files.
Wayne
On 4/23/08, Daniel King <[EMAIL PROTECTED]> wrote:
>
plugins being downloaded from repo1. I thought that those plugins would
> be downloaded to my internal repository. Then when I clear out the
> local repository and do a build again it would only get those from my
> internal repository. However it is still going out to repo1 for
&g
sitory and do a build, I see
plugins being downloaded from repo1. I thought that those plugins would
be downloaded to my internal repository. Then when I clear out the
local repository and do a build again it would only get those from my
internal repository. However it is still going out to
lto:[EMAIL PROTECTED]
Sent: Thursday, April 10, 2008 4:42 PM
To: users@maven.apache.org
Subject: Looking to make internal repository externally access
Hello,
My company has an internal maven repo that I would like to have accessible from
the outside. The problem is that it's a private repo
Hi,
for basic auth just put a element [1] with the same id as your
repository definition in your settings.xml. If you want more security
than just basic auth, there is a guide [2] describing authentication
with client certificates over https on the maven homepage.
-Tim
[1] http://maven.apache.
Hello,
My company has an internal maven repo that I would like to have accessible from
the outside. The problem is that it's a private repo - so we want to at least
have basic auth on it when it is externally accessible. Up until now we've been
just using vpn - but we we've been having issues w
erably with patches) welcome! :)
>
> --
> Wendy
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.
On Mon, Mar 24, 2008 at 1:40 PM, buzzterrier <[EMAIL PROTECTED]> wrote:
> mvn deploy:deploy-file -DgroupId=com.foo -DartifactId=common-dependencies
> -Dversion=1.0 -Dpackaging=pom -Dfile=c:/poms/common-dependencies.xml
> -Durl=http://ourinternalrepos:8080/archiva/repository/internal
> -Dreposi
Hi Wendy,
On Mon, 2008-03-24 at 13:19 -0700, Wendy Smoak wrote:
> On Mon, Mar 24, 2008 at 1:16 PM, buzzterrier <[EMAIL PROTECTED]> wrote:
>
> > Thx for the reply. I did define a custom pom, that declared the
> > dependencies, e.g.
> ...
> > but when
install plugin states that it:
"Installs a file in local repository."
I want to install to an Internal repository which is why the deploy plugin
seemed appropriate.
Wendy Smoak-3 wrote:
>
> On Mon, Mar 24, 2008 at 1:16 PM, buzzterrier <[EMAIL PROTECTED]>
> wrote:
>
> log4j
> log4j
> 1.2.12
>
>
> axis
> axis
> 1.3
> compile
>
> ...
&
On Mon, Mar 24, 2008 at 1:16 PM, buzzterrier <[EMAIL PROTECTED]> wrote:
> Thx for the reply. I did define a custom pom, that declared the
> dependencies, e.g.
...
> but when I deploy this pom to the internal repository the dependencies are
> stripped out and I am left with:
axis
axis
1.3
compile
...
but when I deploy this pom to the internal repository the dependencies are
stripped out and I am left with:
4.0.0
com.foo
common-dependencies
pom
1.0
If I
t as pom. This works when I
> install it to my local repository. However, when I try to deploy it to our
> Internal repository, only the project description gets uploaded, without the
> dependencies.
>
> for example, here is a snippet of what gets installed locally:
>
our
Internal repository, only the project description gets uploaded, without the
dependencies.
for example, here is a snippet of what gets installed locally:
...
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schem
t I thought of
deleting it from the internal repository, but now I've noticed it's enogh
just to delete it from the local one) at the beginning of the build and then
the newest version of the snapshot will be downloaded from the internal
repository.
It's a brutal workaround, but sin
On 3/6/08, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> Maven Dependency Plugin -> purge-local-repository maybe?
>
> http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html
That's it! Thanks Wendy. ;-)
Wayne
---
On Thu, Mar 6, 2008 at 9:08 AM, Wayne Fay <[EMAIL PROTECTED]> wrote:
> I know I've seen someone mention a plugin here that can either wipe
> out your entire repo or selected parts of it. But I can't recall what
> its called right now, and a quick Google search didn't reveal anything
> (but I did
'll
post a follow-up.
Wayne
On 3/6/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Papapara Tudu schrieb:
> > Hello,
> >
> > I would like to delete the whole folder that contains a certain dependency
> > from my internal repository by running a Maven
Papapara Tudu schrieb:
> Hello,
>
> I would like to delete the whole folder that contains a certain dependency
> from my internal repository by running a Maven command from a dev machine.
> Is it possible to do that?
>
Do you mean deleting stuff from the ~/.m2/repository
Hello,
I would like to delete the whole folder that contains a certain dependency
from my internal repository by running a Maven command from a dev machine.
Is it possible to do that?
Thanks,
Papapara Tudu
--
View this message in context:
http://www.nabble.com/Wiping-out-a-dependency-from-an
I
guess it worked before because I had some old versions of Eclipse plugins on
the machines where I have my local and internal repository which were
created earlier, before the project was set up with the internal repo.
Thanks,
Papapara Tudu
--
View this message in context:
http://www.nabble.co
On Feb 18, 2008 10:31 AM, Papapara Tudu <[EMAIL PROTECTED]> wrote:
> I'm using Archiva 1.0.1 and Maven 2.0.8.
> My Maven settings.xml are the default ones, no changes (on both machines).
> My pom.xml has the following entry:
...
>
...
No ? You'll need to repeat the repository as a
plug
Wayne Fay wrote:
>
> What software are you using to run your internal repository? And how
> did you get the plugin there (mvn deploy; manual copy of files;
> something else)? Make sure the metadata is present for the Eclipse
> plugin in your repo.
>
I'm using Archiva 1.
What software are you using to run your internal repository? And how
did you get the plugin there (mvn deploy; manual copy of files;
something else)? Make sure the metadata is present for the Eclipse
plugin in your repo.
Wayne
On 2/15/08, Papapara Tudu <[EMAIL PROTECTED]> wrote:
>
>
Hello,
my project is using an internal repository for all dependencies.
For some reason I cannot run any of the Eclipse Maven plugins, however all
other dependencies get downloaded correctly from the internal repository.
For example, when I run
mvn eclipse:eclipse, I get the following error
I was able to reproduce it. The problem is that this looks like a
maven1 plugin, coming from a maven1 repository, so it translates to
/plugins/ which doesn't exist.
Manually installing is a reasonable workaround. You can file an issue
if you like - though the only way I could think to fix it is fo
Hello,
Archiva Beta 3, plexus standalone, Fedora Core 5, jdk1.5.0_09
A user asked me to cache http://download.java.net/maven/1, a Maven 1
repo. I configured a proxy connector to cache it into the Archiva
'internal' maven 2 repository.
The user has the following in his settings.xml;
;
> Upload them to a bog-standard maven repository using, for example,
> scp or webdav. Maven repos are just directory trees of a known
> structure.
>
>> Is there an easier way to create an internal repository (forget
>> proximity),
>> so that you can use the
wagon
wagon-webdav
1.0-beta-2
Thanks,
Owen.
--
View this message in context:
http://www.nabble.com/uploading-jars-to-a-internal-repository-using-%22mvn-deploy%22-tf4533027s177.html#a12992552
Sent from the Maven - Users
Hello,
you could try to use WebDAV (confgure it as build extension in mvn
2.0.7) and point the repo URL to address:
http://devserver1:/px-webapp/dav/inhouse
Hope helps,
~t~
On 9/28/07, owen_moony <[EMAIL PROTECTED]> wrote:
>
>
> inhouse
>
upload my own jars created by me?
Upload them to a bog-standard maven repository using, for example,
scp or webdav. Maven repos are just directory trees of a known
structure.
Is there an easier way to create an internal repository (forget
proximity),
so that you can use the "mvn d
' not supported
So, I dont know what the deal is. The proximity website that you deploy has
no way of allowing you to upload and the file structure of the repository is
a mystery. How do you upload your home grown jars?!
Is there an easier way to create an internal repository (forget proximi
On 8/23/07, Chris Helck <[EMAIL PROTECTED]> wrote:
> I need to populate an inhouse repository so it can act as a stand alone
> repository. It needs to include the standard maven plugins. I don't want
> to rsync Ibiblio.
>
> I've tried using the assembly plugin to create a repository but it does
> n
On 23/08/07, Chris Helck <[EMAIL PROTECTED]> wrote:
>
> I need to populate an inhouse repository so it can act as a stand alone
> repository. It needs to include the standard maven plugins. I don't want
> to rsync Ibiblio.
>
> I've tried using the assembly plugin to create a repository but it does
I need to populate an inhouse repository so it can act as a stand alone
repository. It needs to include the standard maven plugins. I don't want
to rsync Ibiblio.
I've tried using the assembly plugin to create a repository but it does
not include the plugins.
What should I do?
Thanks,
C. Helck
You want to use the maven deploy plugin - details on usage here:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Martin A.Villalobos
Sent: Thursday, June 21, 2007 1:40 PM
To: users@maven.apache.org
Subject: Uploading the .jar to my internal repository
On 6/21/07, Martin A.Villalobos <[EMAIL PROTECTED]> wrote:
I'm trying to upload a .jar to my internal repository.
Somebody can helpme with a detailed howto about this task?
Try this, and then ask if you have a specific question:
http://maven.apache.org/plugins/maven-deploy-plugin
1 - 100 of 348 matches
Mail list logo
