Overriding parent's distribution management

["Krishnamurthi, Venkat " <ve...@citi.com>]

Hi,

I'm trying to override a parent pom's distribution management through
the child's pom. (Deploy the artifacts in different directories). When I
tried adding a <distributionManagement> element in the child pom, it is
still picking up the details from the parent's pom. Please help me
resolve this issue.

Thanks and Regards,
Venkat

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

Re: Overriding parent's distribution management

[Manuel EVENO <ma...@gmail.com>]

I'm facing the same problem here at my client's.

We have a team internal repository use and visible only to our team.
We have a company-wide repository where we only put some of the
internaly-released artefacts. This way we can filter which version is
visible, usable, used by the other teams.
Then we have a third repository when we need to share artefacts with a
external company. This third repository exists because my client don't want
this external company to see (and possibly steal) any artefact (with
sources) produced internally. We have also have specific contractual rules
for this third repository.

What is maven best-practices for this ?
 - We want the first repo accessible with the default 'mvn deploy' command
 - The second repo accessible with profile activation : mvn -P
deploy-internal deploy
 - The third repo accessible with profile activation : mvn -P deploy-public
deploy

The real problem is to have a default behavior on 'mvn deploy' command ...

I've already look at the stage plugin but it does not fit our needs (and by
the way don't work at all).

Thanks !
Manuel

-- 
http://blog.xebia.fr
http://blog.xebia.com

On Fri, May 16, 2008 at 6:36 PM, Clifton <cl...@gmail.com> wrote:

>
> Thank you for asking this question. I had the very same problem and I'd
> love
> to hear a best practices approach. My workaround, not the best, is to
> define
> them separately in profiles. Then you can use cmd line properties to
> activate one or the other in the activation section of the profile. It may
> not work in your case if you actually want certain pieces to deploy with
> different dist mgmt settings than others in a single build command.
>
>
> Krishnamurthi, Venkat wrote:
> >
> > Hi,
> >
> > I'm trying to override a parent pom's distribution management through
> > the child's pom. (Deploy the artifacts in different directories). When I
> > tried adding a <distributionManagement> element in the child pom, it is
> > still picking up the details from the parent's pom. Please help me
> > resolve this issue.
> >
> > Thanks and Regards,
> > Venkat
> >
> > ---------------------------------------------------------------------
> > 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/running-mvn-idea%3Aidea-tp17232616p17279055.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: Overriding parent's distribution management

[Clifton <cl...@gmail.com>]

Thank you for asking this question. I had the very same problem and I'd love
to hear a best practices approach. My workaround, not the best, is to define
them separately in profiles. Then you can use cmd line properties to
activate one or the other in the activation section of the profile. It may
not work in your case if you actually want certain pieces to deploy with
different dist mgmt settings than others in a single build command.


Krishnamurthi, Venkat wrote:
> 
> Hi,
> 
> I'm trying to override a parent pom's distribution management through
> the child's pom. (Deploy the artifacts in different directories). When I
> tried adding a <distributionManagement> element in the child pom, it is
> still picking up the details from the parent's pom. Please help me
> resolve this issue.
> 
> Thanks and Regards,
> Venkat
> 
> ---------------------------------------------------------------------
> 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/running-mvn-idea%3Aidea-tp17232616p17279055.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