You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by HHB <hu...@yahoo.ca> on 2009/03/29 16:08:40 UTC

Sharing Maven-based project

Hey,
I use Maven as the build tool for our project.
Now my team mates want to checkout the project from the SVN and I want to
add the project to out continuous integration server (Hudson).
I'm not sure but should I create a central repository in our unit? or let
each mate (and CI server) download the dependency himself?
What repository manager do you suggest? 
Thanks.
-- 
View this message in context: http://www.nabble.com/Sharing-Maven-based-project-tp22767986p22767986.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Sharing Maven-based project

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
We have some tools to help convert a local repo into a remote repo
format: https://docs.sonatype.com/display/NX/Nexus+Command+Line+Tools

-----Original Message-----
From: HHB [mailto:hubaghdadi@yahoo.ca] 
Sent: Tuesday, March 31, 2009 10:57 AM
To: users@maven.apache.org
Subject: Re: Sharing Maven-based project


Please correct me if I'm wrong:
1. I have to install Nexus (my choice) on the dev machine (shared
server).
2. I will use Nexus to copy my local MVN repository to the dev machine.
Thanks for help , I'm so newbie with Maven.


Cedros GmbH wrote:
> 
> Yes, create a repository for your unit/company.
> You don't want to let your colleagues download artifacs manually from

> eg. SVN.
> 
> We use Artifactoy as a repository and central mirror for every maven  
> installation in the company.
> Its running on Tomcat, easy to install and integrated with the company

> LDAP.
> 
> Regards
> 
> Am 29.03.2009 um 16:08 schrieb HHB:
> 
>>
>> Hey,
>> I use Maven as the build tool for our project.
>> Now my team mates want to checkout the project from the SVN and I  
>> want to
>> add the project to out continuous integration server (Hudson).
>> I'm not sure but should I create a central repository in our unit?  
>> or let
>> each mate (and CI server) download the dependency himself?
>> What repository manager do you suggest?
>> Thanks.
>> -- 
>> View this message in context:
>>
http://www.nabble.com/Sharing-Maven-based-project-tp22767986p22767986.ht
ml
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 

-- 
View this message in context:
http://www.nabble.com/Sharing-Maven-based-project-tp22767986p22804979.ht
ml
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Sharing Maven-based project

Posted by Oliver Klein <ok...@cedros.com>.
1. Yes.
2. I'am not familiar with NEXUS ('cause we use Artifactory) and I  
don't know about your local repository.
But the common steps would include to configure NEXUS as a mirror in  
your $HOME/.m2/settings.xml (or pom.xml) and then deploy artifacts to  
it.
The following XML is the mirror configuration for our Artifactory,  
NEXUS should be something equal - have a look in the docs.

     <!-- development gobal mirror -->
     <mirrors>
         <mirror>
             <id>YOURSERVERNAME</id>
             <mirrorOf>*</mirrorOf>
             <url>http://YOURSERVERNAME/artifactory/repo</url>
             <name>Artifactory</name>
         </mirror>
     </mirrors>

So if you request an artifact, e.g. 'junit-3.5.8' it is loaded from  
the NEXUS repository.
If it isn't in the NEXUS repository, it gets loaded from the central  
to NEXUS and then to your client.

Deploying artifacts: http://maven.apache.org/plugins/maven-deploy-plugin/


Am 31.03.2009 um 16:56 schrieb HHB:

>
> Please correct me if I'm wrong:
> 1. I have to install Nexus (my choice) on the dev machine (shared  
> server).
> 2. I will use Nexus to copy my local MVN repository to the dev  
> machine.
> Thanks for help , I'm so newbie with Maven.
>
>
> Cedros GmbH wrote:
>>
>> Yes, create a repository for your unit/company.
>> You don't want to let your colleagues download artifacs manually from
>> eg. SVN.
>>
>> We use Artifactoy as a repository and central mirror for every maven
>> installation in the company.
>> Its running on Tomcat, easy to install and integrated with the  
>> company
>> LDAP.
>>
>> Regards
>>
>> Am 29.03.2009 um 16:08 schrieb HHB:
>>
>>>
>>> Hey,
>>> I use Maven as the build tool for our project.
>>> Now my team mates want to checkout the project from the SVN and I
>>> want to
>>> add the project to out continuous integration server (Hudson).
>>> I'm not sure but should I create a central repository in our unit?
>>> or let
>>> each mate (and CI server) download the dependency himself?
>>> What repository manager do you suggest?
>>> Thanks.
>>> -- 
>>> View this message in context:
>>> http://www.nabble.com/Sharing-Maven-based-project-tp22767986p22767986.html
>>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> -- 
> View this message in context: http://www.nabble.com/Sharing-Maven-based-project-tp22767986p22804979.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Sharing Maven-based project

Posted by Geoffrey Wiseman <ge...@gmail.com>.
On Tue, Mar 31, 2009 at 2:07 PM, Brian E. Fox <br...@reply.infinity.nu>wrote:

> Don't forget about the improved build performance that will come with
> the proxies you get with a repo manager. I wouldn't say that you don't
> need one until you actually need to share artifacts (which would happen
> as soon as you actually start building and releasing anyway). I would
> say that as soon as you have more than one developer in a given
> location, you should consider a repo manager if only to proxy builds and
> protect yourself from transient network outages.
>

I'd agree that if you're comfortable with Maven, that's a good strategy.  If
you're not, then I'd probably rather get the team accustomed to Maven before
they get into repo managers.  It's just one more moving piece.  YMMV, of
course.

  - Geoffrey
-- 
Geoffrey Wiseman
http://www.geoffreywiseman.ca/

RE: Sharing Maven-based project

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
>Yes, although if all your project dependencies are in the Maven central
>repository, there may be some value in waiting on Nexus (or one of the
other
>repo managers, although I like Nexus) 'til you're "ready".  If you've
>already got several dependencies in your local repo that can't be found
on
>central, then it's probably simpler to set up Nexus than it is to move
>dependencies around between developers, yes.

Don't forget about the improved build performance that will come with
the proxies you get with a repo manager. I wouldn't say that you don't
need one until you actually need to share artifacts (which would happen
as soon as you actually start building and releasing anyway). I would
say that as soon as you have more than one developer in a given
location, you should consider a repo manager if only to proxy builds and
protect yourself from transient network outages.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Sharing Maven-based project

Posted by Geoffrey Wiseman <ge...@gmail.com>.
On Tue, Mar 31, 2009 at 10:56 AM, HHB <hu...@yahoo.ca> wrote:

>
> Please correct me if I'm wrong:
> 1. I have to install Nexus (my choice) on the dev machine (shared server).
> 2. I will use Nexus to copy my local MVN repository to the dev machine.
> Thanks for help , I'm so newbie with Maven.
>
>
Yes, although if all your project dependencies are in the Maven central
repository, there may be some value in waiting on Nexus (or one of the other
repo managers, although I like Nexus) 'til you're "ready".  If you've
already got several dependencies in your local repo that can't be found on
central, then it's probably simpler to set up Nexus than it is to move
dependencies around between developers, yes.

  - Geoffrey
-- 
Geoffrey Wiseman
http://www.geoffreywiseman.ca/

Re: Sharing Maven-based project

Posted by HHB <hu...@yahoo.ca>.
Please correct me if I'm wrong:
1. I have to install Nexus (my choice) on the dev machine (shared server).
2. I will use Nexus to copy my local MVN repository to the dev machine.
Thanks for help , I'm so newbie with Maven.


Cedros GmbH wrote:
> 
> Yes, create a repository for your unit/company.
> You don't want to let your colleagues download artifacs manually from  
> eg. SVN.
> 
> We use Artifactoy as a repository and central mirror for every maven  
> installation in the company.
> Its running on Tomcat, easy to install and integrated with the company  
> LDAP.
> 
> Regards
> 
> Am 29.03.2009 um 16:08 schrieb HHB:
> 
>>
>> Hey,
>> I use Maven as the build tool for our project.
>> Now my team mates want to checkout the project from the SVN and I  
>> want to
>> add the project to out continuous integration server (Hudson).
>> I'm not sure but should I create a central repository in our unit?  
>> or let
>> each mate (and CI server) download the dependency himself?
>> What repository manager do you suggest?
>> Thanks.
>> -- 
>> View this message in context:
>> http://www.nabble.com/Sharing-Maven-based-project-tp22767986p22767986.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Sharing-Maven-based-project-tp22767986p22804979.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Sharing Maven-based project

Posted by Cedros GmbH <ok...@cedros.com>.
Yes, create a repository for your unit/company.
You don't want to let your colleagues download artifacs manually from  
eg. SVN.

We use Artifactoy as a repository and central mirror for every maven  
installation in the company.
Its running on Tomcat, easy to install and integrated with the company  
LDAP.

Regards

Am 29.03.2009 um 16:08 schrieb HHB:

>
> Hey,
> I use Maven as the build tool for our project.
> Now my team mates want to checkout the project from the SVN and I  
> want to
> add the project to out continuous integration server (Hudson).
> I'm not sure but should I create a central repository in our unit?  
> or let
> each mate (and CI server) download the dependency himself?
> What repository manager do you suggest?
> Thanks.
> -- 
> View this message in context: http://www.nabble.com/Sharing-Maven-based-project-tp22767986p22767986.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Sharing Maven-based project

Posted by B Smith-Mannschott <bs...@gmail.com>.
On Sun, Mar 29, 2009 at 16:08, HHB <hu...@yahoo.ca> wrote:
>
> Hey,
> I use Maven as the build tool for our project.
> Now my team mates want to checkout the project from the SVN and I want to
> add the project to out continuous integration server (Hudson).
> I'm not sure but should I create a central repository in our unit? or let
> each mate (and CI server) download the dependency himself?
> What repository manager do you suggest?
> Thanks.

I use a combination of Nexus[1] for my maven artifacts and Hudson[2]
for continuous build. Both were very easy to set up and maintain.

[1] http://nexus.sonatype.org/
[2] https://hudson.dev.java.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org