maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Closed] (MRELEASE-306) Allow for controlling plugin updates
Date Sun, 06 Sep 2015 20:45:48 GMT


Michael Osipov closed MRELEASE-306.
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If
you think this issue still applies, retest your problem with the most recent version of Maven
and the affected component, reopen and post your results.

> Allow for controlling plugin updates
> ------------------------------------
>                 Key: MRELEASE-306
>                 URL:
>             Project: Maven Release Plugin
>          Issue Type: New Feature
>          Components: prepare
>    Affects Versions: 2.0-beta-7
>            Reporter: Aleksei Valikov
> Hi folks,
> I am the author of Maven2 JAXB2 plugin. The project can be found here:
> This is the direct link to SVN:
> I have recently tried to start using Maven Release Plugin for releases. Unfortunatelly
I failed.
> My problem is as follows. In this project I have a plugin module maven-jaxb2-plugin with
packaging maven-plugin. There is also a further module maven-jaxb2-plugin-testing (jar packaging)
which depends on maven-jaxb2-plugin. 
> When I try releasing the project, I get the following failure report in the maven-jaxb2-plugin-testing
(assume 0.5-SNAPSHOT -> 0.5 release):
> {code}
>         [INFO] ------------------------------------------------------------------------
>         [INFO] Failed to resolve artifact.
>     Missing:
>         ----------
>         1) org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:jar:0.5
>           Try downloading the file manually from the project website.
>           Then, install it using the command: 
>               mvn install:install-file -DgroupId=org.jvnet.jaxb2.maven2 -DartifactId=maven-jaxb2-plugin
-Dversion=0.5 -Dpackaging=jar -Dfile=/path/to/file
>           Alternatively, if you host your own repository you can deploy the file there:

>               mvn deploy:deploy-file -DgroupId=org.jvnet.jaxb2.maven2 -DartifactId=maven-jaxb2-plugin
-Dversion=0.5 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>           Path to dependency: 
>           	1) org.jvnet.jaxb2.maven2:maven-jaxb2-plugin-testing:jar:0.5
>           	2) org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:jar:0.5
>         ----------
>         1 required artifact is missing.
>     for artifact: 
>           org.jvnet.jaxb2.maven2:maven-jaxb2-plugin-testing:jar:0.5
>         from the specified remote repositories:
>           jfrog-plugins (,
>  (,
>  (,
>           central (
> {code}
> At the same time when I simply build the project with 
> {code}mvn -DperformRelease=true clean install{code}
> everything works fine.
> I suppose the problem is in the way the Maven is executed:
> {code}mvn clean verify --no-plugin-updates --batch-mode -P samples,{code}
> I guess --no-plugin-updates is to blame.
> Therefore I am looking for a way to disable --no-plugin-updates. I'm surely allright
if the default behaviour is to have it present by default, but there must be a way to configure
its absence.
> Please let me know if you acknowledge the issue or maybe I'm mistaken somewhere.
> If what I'm saying makes sense for you, I could try making a fix.

This message was sent by Atlassian JIRA

View raw message