You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Barrie Treloar <ba...@gmail.com> on 2006/08/11 04:57:13 UTC

[m2] How to install local patches of plugins and stop snapshots from maven site being installed

I have patched the maven-assembly-plugin (and submitted to JIRA) and
then deployed my local patched version into our internal repository.

Now someone has deployed a new snapshot version into the maven
snapshot site and my local changes have been overridden.

This may be because of a number of factors
- I am using maven-proxy which may be aggregating the repositories (I
am behind an NTLM firewall)
- I have previously installed some snapshot plugins so that the meta
information is still available and is being checked (because the
plugin is a snapshot plugin it probably depends on snapshots of other
plugins)

Does anyone have a recommendation for how I can use my patched version only?
Should I change the version details to include a suffix like -COMPANY
and to create a release to our internal repository instead of using a
snapshot version?

Cheers

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


Re: [m2] How to install local patches of plugins and stop snapshots from maven site being installed

Posted by Kenney Westerhof <fo...@gods.nl>.
Was't this problem related to the fact that if you do an 'mvn install'
to your local repo, resulting in -SNAPSHOT.jar, and then later on
maven finds a new timestamped snapshot, that one is used instead?

I don't think the jar in your company repository has a timestamp in it,
just -SNAPSHOT. If so, then it's the above 'bug' kicking in.

What you could/should do is deploy with a timestamp, and then fix the 
version in the pom to that timestamp (i.e. 
<version>yyyymmddhhss-a</version> instead of SNAPSHOT).

On the other hand, on normal installations no snapshot plugins are used, 
because the snapshot plugin repo wasn't listed anywhere, so any snapshot 
versions of plugins you want to use you have to install yourself - 
that'll pin those down too.

HTH,

-- Kenney

Brett Porter wrote:
> changing the version or blocking the download the main alternatives. you 
> can locally block the download for all snapshots by setting the policy 
> to either disabled (don't use any external snapshots), or update 
> interval to "never" (get external snapshots, but never update them, 
> meaning locally installed ones stay).
> 
> Or, you could deploy your snapshot to your proxy repository and as long 
> as it never updates that one you'll be ok - not sure how to configure 
> that in maven-proxy though.
> 
> - Brett
> 
> On 11/08/2006 12:57 PM, Barrie Treloar wrote:
>> I have patched the maven-assembly-plugin (and submitted to JIRA) and
>> then deployed my local patched version into our internal repository.
>>
>> Now someone has deployed a new snapshot version into the maven
>> snapshot site and my local changes have been overridden.
>>
>> This may be because of a number of factors
>> - I am using maven-proxy which may be aggregating the repositories (I
>> am behind an NTLM firewall)
>> - I have previously installed some snapshot plugins so that the meta
>> information is still available and is being checked (because the
>> plugin is a snapshot plugin it probably depends on snapshots of other
>> plugins)
>>
>> Does anyone have a recommendation for how I can use my patched version 
>> only?
>> Should I change the version details to include a suffix like -COMPANY
>> and to create a release to our internal repository instead of using a
>> snapshot version?
>>
>> Cheers
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
> 
> 

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


Re: [m2] How to install local patches of plugins and stop snapshots from maven site being installed

Posted by Brett Porter <br...@apache.org>.
changing the version or blocking the download the main alternatives. you 
can locally block the download for all snapshots by setting the policy 
to either disabled (don't use any external snapshots), or update 
interval to "never" (get external snapshots, but never update them, 
meaning locally installed ones stay).

Or, you could deploy your snapshot to your proxy repository and as long 
as it never updates that one you'll be ok - not sure how to configure 
that in maven-proxy though.

- Brett

On 11/08/2006 12:57 PM, Barrie Treloar wrote:
> I have patched the maven-assembly-plugin (and submitted to JIRA) and
> then deployed my local patched version into our internal repository.
> 
> Now someone has deployed a new snapshot version into the maven
> snapshot site and my local changes have been overridden.
> 
> This may be because of a number of factors
> - I am using maven-proxy which may be aggregating the repositories (I
> am behind an NTLM firewall)
> - I have previously installed some snapshot plugins so that the meta
> information is still available and is being checked (because the
> plugin is a snapshot plugin it probably depends on snapshots of other
> plugins)
> 
> Does anyone have a recommendation for how I can use my patched version 
> only?
> Should I change the version details to include a suffix like -COMPANY
> and to create a release to our internal repository instead of using a
> snapshot version?
> 
> Cheers
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 


-- 
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

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