maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anthony Whitford <anth...@whitford.com>
Subject Re: Chicken-Egg problem with JXR & release:perform
Date Thu, 14 Feb 2019 19:46:54 GMT
mvn site works fine.  It only fails when I do release:perform.

My workaround is to checkout the release tag, run `mvn clean install` to install the release
version locally, then checkout master, and then run `mvn release:perform` again.  I’ve been
doing this the last few releases, but this is ridiculous.  I release this project so infrequently,
I don’t recall what precisely changed.  I mostly just upgrade plugins as the code is fairly
stable, but I also upgrade Maven (3.6.0) and Java (11.0.1).

I even tried skipping JXR, like:  `mvn -Dmaven.jxr.skip=true release:perform` — but that
didn’t work either.  (It appears that the dependency resolution is still performed despite
skipping the plugin logic.)

Note that the top-level parent project is failing — the module (which is what it really
is complaining about is missing) hasn’t had a chance to deploy yet.  Is the jxr:aggregate
report goal running too early — doesn’t it need to wait until after each module runs?
 How would release:perform differ from normal site?



> On Feb 14, 2019, at 10:59 AM, Robert Scholte <rfscholte@apache.org> wrote:
> 
> running 'mvn site' would already show the problem.
> 
> One of the things you should do is mention the reports you want to generate, now all
available jxr-reports are generated, that's probably more than you want.
> 
> not sure what the difference is with the integration test[1] which shows the aggregate
report should work.
> 
> thanks,
> Robert
> 
> [1] https://github.com/apache/maven-jxr/tree/master/maven-jxr-plugin/src/it/aggregate
> 
> 
> On Thu, 14 Feb 2019 07:25:20 +0100, Anthony Whitford <anthony@whitford.com> wrote:
> 
>> I have an open source project:  https://github.com/awhitford/lombok.maven <https://github.com/awhitford/lombok.maven>
>> Lately (and this started happening months ago), I am unable to do a clean:  mvn release:prepare,
then mvn release:perform
>> The mvn release:perform fails like this:
>> 
>> [INFO] [INFO] configuring report plugin org.apache.maven.plugins:maven-jxr-plugin:3.0.0
>> [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/projectlombok/lombok-maven-plugin/1.18.6.0/lombok-maven-plugin-1.18.6.0.jar
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [INFO] Reactor Summary for Maven Plugin for Project Lombok 1.18.6.0:
>> [INFO] [INFO]
>> [INFO] [INFO] Maven Plugin for Project Lombok .................... FAILURE [ 47.240
s]
>> [INFO] [INFO] Lombok Maven Plugin ................................ SKIPPED
>> [INFO] [INFO] Sample Lombok Maven Project ........................ SKIPPED
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [INFO] BUILD FAILURE
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [INFO] Total time:  47.412 s
>> [INFO] [INFO] Finished at: 2019-02-13T22:17:02-08:00
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.7.1:site
(default-site) on project lombok-maven: failed to get report for org.apache.maven.plugins:maven-jxr-plugin:
Plugin org.projectlombok:lombok-maven-plugin:1.18.6.0 or one of its dependencies could not
be resolved: Could not find artifact org.projectlombok:lombok-maven-plugin:jar:1.18.6.0 in
central (https://repo.maven.apache.org/maven2) -> [Help 1]
>> [INFO] [ERROR]
>> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
>> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [INFO] [ERROR]
>> [INFO] [ERROR] For more information about the errors and possible solutions, please
read the following articles:
>> [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Reactor Summary for Maven Plugin for Project Lombok 1.18.6.1-SNAPSHOT:
>> [INFO]
>> [INFO] Maven Plugin for Project Lombok .................... FAILURE [ 54.864 s]
>> [INFO] Lombok Maven Plugin ................................ SKIPPED
>> [INFO] Sample Lombok Maven Project ........................ SKIPPED
>> [INFO] ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Total time:  55.474 s
>> [INFO] Finished at: 2019-02-13T22:17:02-08:00
>> [INFO] ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:perform
(default-cli) on project lombok-maven: Maven execution failed, exit code: '1' -> [Help
1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions, please read
the following articles:
>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>> 
>> In other words, it appears that the JXR plugin is complaining that it cannot download
the Lombok-maven-plugin-1.18.6.0.jar from Central.  Well, duh! — I’m in the middle of
its release…
>> 
>> How are others getting around this problem?  What am I doing wrong?
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message