[
http://jira.codehaus.org/browse/MRELEASE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116918
]
Aleksei Valikov commented on MRELEASE-306:
------------------------------------------
Hm, it seems that --no-plugin-updates have nothing to do with it.
> Allow for controlling plugin updates
> ------------------------------------
>
> Key: MRELEASE-306
> URL: http://jira.codehaus.org/browse/MRELEASE-306
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> 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:
> https://maven-jaxb2-plugin.dev.java.net
> This is the direct link to SVN:
> https://maven-jaxb2-plugin.dev.java.net/svn/maven-jaxb2-plugin/trunk
> 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}
> [ERROR] BUILD ERROR
> [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 (http://www.jfrog.org/artifactory/[EMAIL PROTECTED]),
> maven-repository.dev.java.net (http://download.java.net/maven/1),
> maven2-repository.dev.java.net (http://download.java.net/maven/2),
> central (http://repo1.maven.org/maven2)
> {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,dev.java.net{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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
