[m2] problem getting latest plugin version to local maven repository
We've got an inhouse mirror of the central repository (MyCompanyCentral). We also publish a company-specific maven-plugin to that same repository. We face the problem that the latest version of our plugin is not downloaded to the local maven repository, if there is already an old version, even not after several days. We also tried with updatePolicyinterval:30/updatePolicy and updatePolicyalways/updatePolicy but no success. It only worked when we deleted the old local versions, or when we run maven with the -U parameter. Should this basically work? Any idea what we might do wrong? We use this settings.xml: settings localRepositoryD:/mavenrepo/localRepository mirrors mirror idMyCompanyCentral/id nameMyCompany Central Repository/name urlhttp://build.mycompany.com/m2/repository/url mirrorOfcentral/mirrorOf /mirror /mirrors profiles profile idMyCompanyDefaultProfile/id repositories repository idMyCompanyCentral/id nameMyCompany Central Repository/name urlhttp://build.mycompany.com/m2/repository/url layoutdefault/layout /repository repository idMyCompanySnapshot/id nameMyCompany Snapshot Repository/name urlhttp://build.mycompany.com/snapshot/url /repository /repositories /profile /profiles activeProfiles activeProfileMyCompanyDefaultProfile/activeProfile /activeProfiles /settings Thanks, Tom __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] problem getting latest plugin version to local maven repository
Just as an idea, try going to the user account that you build under's .m2
directory (${user.dir}/.m2) and delete the plugin-registry.xml file, and
re-run. It might be causing you some problems.
Eric
On 11/20/06, Thomas Will [EMAIL PROTECTED] wrote:
We've got an inhouse mirror of the central repository
(MyCompanyCentral). We also publish a company-specific
maven-plugin to that same repository.
We face the problem that the latest version of our
plugin is not downloaded to the local maven
repository, if there is already an old version, even
not after several days.
We also tried with
updatePolicyinterval:30/updatePolicy
and updatePolicyalways/updatePolicy
but no success.
It only worked when we deleted the old local versions,
or when we run maven with the -U parameter.
Should this basically work?
Any idea what we might do wrong?
We use this settings.xml:
settings
localRepositoryD:/mavenrepo/localRepository
mirrors
mirror
idMyCompanyCentral/id
nameMyCompany Central Repository/name
urlhttp://build.mycompany.com/m2/repository/url
mirrorOfcentral/mirrorOf
/mirror
/mirrors
profiles
profile
idMyCompanyDefaultProfile/id
repositories
repository
idMyCompanyCentral/id
nameMyCompany Central Repository/name
urlhttp://build.mycompany.com/m2/repository/url
layoutdefault/layout
/repository
repository
idMyCompanySnapshot/id
nameMyCompany Snapshot Repository/name
urlhttp://build.mycompany.com/snapshot/url
/repository
/repositories
/profile
/profiles
activeProfiles
activeProfileMyCompanyDefaultProfile/activeProfile
/activeProfiles
/settings
Thanks, Tom
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Eric Redmond
http://codehaus.org/~eredmond
Re: [m2] problem getting latest plugin version to local maven repository
How did you deploy your plugin ? Did you use the release plugin ? If you just do a deploy, add -DupdateReleaseInfo=true Tom On 11/21/06, Tom Will [EMAIL PROTECTED] wrote: We've got an inhouse mirror of the central repository. We also deploy a company-specific maven-plugin to that inhouse mirror. We face the problem that the latest version of our plugin is not downloaded to the local maven repository, if there is already an old local version, even not after several days. We also tried with updatePolicyinterval:30/updatePolicy and updatePolicyalways/updatePolicy but no success. It only worked when we deleted the old local versions, or when we run maven with the -U parameter. Should this basically work? Any idea what we might do wrong? We use this settings.xml: settings localRepositoryD:/mavenrepo/localRepository mirrors mirror idMyCompanyCentral/id nameMyCompany Central Repository/name urlhttp://build.mycompany.com/repository/url mirrorOfcentral/mirrorOf /mirror /mirrors profiles profile idMyCompanyDefaultProfile/id repositories repository idMyCompanyCentral/id nameMyCompany Central Repository/name urlhttp://build.mycompany.com/repository/url layoutdefault/layout /repository repository idMyCompanySnapshot/id nameMyCompany Snapshot Repository/name urlhttp://build.mycompany.com/snapshot/url /repository /repositories /profile /profiles activeProfiles activeProfileMyCompanyDefaultProfile/activeProfile /activeProfiles /settings Thanks, Tom -- View this message in context: http://www.nabble.com/-m2--problem-getting-latest-plugin-version-to-local-maven-repository-tf2677604s177.html#a7467807 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
