>
> "Publish" does not mean to the whole world.
>

Well, it *can*, if that's what you want... ;-)

-Curtis


On Tue, Feb 21, 2012 at 4:25 PM, Ron Wheeler <[email protected]
> wrote:

> On 21/02/2012 3:09 PM, Daivish Shah wrote:
>
>> Hi,
>>
>> I have a project with following structure.
>>
>> maven-main-project
>>            maven-ear
>>            maven-ejb
>>            maven-schema
>>            maven-pojo
>>            maven-java
>>
>> This is my project structure for multi-module project. And now if i don't
>> want to publish any artifacts outside of this project. I mean to say i
>> don't want to publish any artifactory/nexus/archiva repository copy for
>> other people to use it.
>>
> Other people being your coworkers and co-developers?
> A Maven repo is a private place.
> You control who has access.
> It is normally only for your team (even if you are the whole team).
>
> If you are using Maven you need a repo. We went for 2 years without one
> and it was a really stupid oversight on our part.
> It greatly simplifies your life and makes Maven much easier to understand
> and makes it much easier to do the right things.
> "Publish" does not mean to the whole world.
>
> Ron
>
>
>  *Use Case :*
>>
>> Here my maven-ear is part of the maven-main-project and that's the only
>> module which use the maven-pojo and maven-java generated artifacts and
>> which i don't want to publish it on repository but just want to use it for
>> building the EAR.
>>
>> How can i disable those 2 (maven-pojo and maven-java) projects not to
>> publish artifacts at repository level.
>>
>> Looking for some solution on this, As don't want to create unncessary
>> artifacts on repository as nobody is going to use it other then my own
>> Main
>> project EAR project.
>>
>> Thanks.
>>
>>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: [email protected]
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

Reply via email to