You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by or...@io7m.com on 2013/01/08 15:05:44 UTC

Javadoc aggregation doesn't use snapshots?

Hello.

I have a multimodule project at
http://fossil.io7m.com/repo.cgi/io7m-jcanephora

The root module is responsible for aggregating javadoc from all of the
submodules. I recently switched to using SNAPSHOT dependencies, rather
than having to constantly produce new releases for minor changes.
Unfortunately, now the project refuses to build. I get the following
error:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:2.8.1:aggregate
(aggregate) on project io7m-jcanephora: An error has occurred in
JavaDocs report generation:  Unable to find a version in [2.0.0, 2.1.0,
2.1.1, 2.1.2, 2.2.0, 2.3.0] to match the range
[2.4.0-SNAPSHOT,2.4.0-SNAPSHOT],[2.4.0,3.0.0) [ERROR]
com.io7m.jaux:io7m-jaux:jar:null

Note that the "[2.0.0, 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.3.0]" corresponds
exactly to the available *release* versions of io7m-jaux on the central
repository. I'm hosting snapshots at http://repo.io7m.com/snapshots and
the project seems to have no problem using those. It just seems as
though the javadoc aggregator refuses to use snapshots.

Is this a known problem (perhaps deliberate, for some reason)?

If anyone would like to try building the above project, the following
settings.xml definitions are necessary:

    <profile>
      <id>io7m-repos</id>
      <repositories>
        <repository>
          <id>io7m-snapshots</id>
          <name>io7m snapshots</name>
          <url>http://repo.io7m.com/snapshots/</url>
          <snapshots><enabled>true</enabled></snapshots>
          <releases><enabled>false</enabled></releases>
          <layout>default</layout>
        </repository>
      </repositories>
    </profile>

    <profile>
      <id>jogamp</id>
      <repositories>
        <repository>
          <id>jogamp-remote</id>
          <name>jogamp test mirror</name>
          <url>http://www.jogamp.org/deployment/maven/</url>
          <layout>default</layout>
        </repository>
      </repositories>
    </profile>

The source code can either be cloned with the fossil SCM
(http://fossil-scm.org) or downloaded as a tarball snapshot
by visiting http://fossil.io7m.com/repo.cgi/io7m-jcanephora/info/tip
after logging in anonymously (anonymous logins are required to stop
web spiders from accidentally causing havoc).

I recommend using -Dmaven.test.skip=true, as the test suite requires
a working OpenGL setup and takes a few minutes to execute.

Any help would be appreciated here, I'm at a loss as to why javadoc
aggregation has stopped working!

M

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


Re: Javadoc aggregation doesn't use snapshots?

Posted by or...@io7m.com.
> Opened:
> 
> https://jira.codehaus.org/browse/MJAVADOC-360
> 

For anyone not following this bug, I've put together a vastly simpler
case that demonstrates the problem:
 
https://github.com/io7m/io7m-jcanephora/tree/reduction
 
The problem's reproduced with a single module and a couple of
snapshots. As I said, this is currently a blocking issue for me, so if
anyone more knowledgeable about Maven's internals could take a look at
what's going on, I'd really appreciate it.
 
M

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


Re: Javadoc aggregation doesn't use snapshots?

Posted by or...@io7m.com.
*Ahem*

Please excuse that duplicate. I'd sent it from the wrong address
originally (I use bespoke addresses for easier filtering and to track
"leaks" when receiving spam) and had assumed it'd been silently
dropped...

M

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


Re: Javadoc aggregation doesn't use snapshots?

Posted by or...@io7m.com.
On Thu, 10 Jan 2013 01:39:17 +0000
<or...@io7m.com> wrote:
> 
> Opened:
> 
> https://jira.codehaus.org/browse/MJAVADOC-360

For anyone not following this bug, I've put together a vastly simpler
case that demonstrates the problem:

https://github.com/io7m/io7m-jcanephora/tree/reduction

The problem's reproduced with a single module and a couple of
snapshots. As I said, this is currently a blocking issue for me, so if
anyone more knowledgeable about Maven's internals could take a look at
what's going on, I'd really appreciate it.

M

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


Re: Javadoc aggregation doesn't use snapshots?

Posted by or...@io7m.com.
On Wed, 9 Jan 2013 14:30:47 -0500
Benson Margulies <bi...@gmail.com> wrote:

> A JIRA might get more useful attention, pointing to github or
> whatever.

Opened:

https://jira.codehaus.org/browse/MJAVADOC-360

Regards,
M

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


Re: Javadoc aggregation doesn't use snapshots?

Posted by Benson Margulies <bi...@gmail.com>.
A JIRA might get more useful attention, pointing to github or whatever.

On Wed, Jan 9, 2013 at 11:00 AM,  <or...@io7m.com> wrote:
> Anyone?
>
> This has become a blocking issue for me, and am quite surprised that it
> exists at all given that the project really isn't complicated.
>
> Would it help if I put the code on github so that people could look at
> it more easily?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

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


Re: Javadoc aggregation doesn't use snapshots?

Posted by or...@io7m.com.
Anyone?

This has become a blocking issue for me, and am quite surprised that it
exists at all given that the project really isn't complicated.

Would it help if I put the code on github so that people could look at
it more easily?

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


Re: Javadoc aggregation doesn't use snapshots?

Posted by or...@io7m.com.
On Tue, 8 Jan 2013 14:19:14 +0000
Stephen Connolly <st...@gmail.com> wrote:

> I haven't looked at your project but I have a suspicion as to what is
> going on.
> 
> By default the javadoc.jar is not generated by a default build, so as
> a result there is no javadoc.jar in the reactor and hence there is a
> search of the local and remote repositories... but since these do not
> have the javadoc.jar attached either, you get the complaint.
> 
> When you run a release using the release plugin, the standard release
> profile adds in executions for source:jar and javadoc:jar which will
> result in the artifacts being available in the reactor and hence both
> deployed to the remote repository and available for aggregation.
> 
> Please try adding the following to your maven command
> 
> -P+release
> 
> if the build works with that added to the command line, then my
> theory is correct

Hi, thanks for the quick reply.

Unfortunately, adding the flag didn't make any difference. I should
mention that I'm not actually using the release plugin (due to having
an unsupported SCM). It does cause a warning before the existing javadoc
error:

[WARNING] The requested profile "release" could not be activated
because it does not exist.

M

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


Re: Javadoc aggregation doesn't use snapshots?

Posted by Stephen Connolly <st...@gmail.com>.
I haven't looked at your project but I have a suspicion as to what is going
on.

By default the javadoc.jar is not generated by a default build, so as a
result there is no javadoc.jar in the reactor and hence there is a search
of the local and remote repositories... but since these do not have the
javadoc.jar attached either, you get the complaint.

When you run a release using the release plugin, the standard release
profile adds in executions for source:jar and javadoc:jar which will result
in the artifacts being available in the reactor and hence both deployed to
the remote repository and available for aggregation.

Please try adding the following to your maven command

-P+release

if the build works with that added to the command line, then my theory is
correct


On 8 January 2013 14:05, <or...@io7m.com> wrote:

> Hello.
>
> I have a multimodule project at
> http://fossil.io7m.com/repo.cgi/io7m-jcanephora
>
> The root module is responsible for aggregating javadoc from all of the
> submodules. I recently switched to using SNAPSHOT dependencies, rather
> than having to constantly produce new releases for minor changes.
> Unfortunately, now the project refuses to build. I get the following
> error:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.8.1:aggregate
> (aggregate) on project io7m-jcanephora: An error has occurred in
> JavaDocs report generation:  Unable to find a version in [2.0.0, 2.1.0,
> 2.1.1, 2.1.2, 2.2.0, 2.3.0] to match the range
> [2.4.0-SNAPSHOT,2.4.0-SNAPSHOT],[2.4.0,3.0.0) [ERROR]
> com.io7m.jaux:io7m-jaux:jar:null
>
> Note that the "[2.0.0, 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.3.0]" corresponds
> exactly to the available *release* versions of io7m-jaux on the central
> repository. I'm hosting snapshots at http://repo.io7m.com/snapshots and
> the project seems to have no problem using those. It just seems as
> though the javadoc aggregator refuses to use snapshots.
>
> Is this a known problem (perhaps deliberate, for some reason)?
>
> If anyone would like to try building the above project, the following
> settings.xml definitions are necessary:
>
>     <profile>
>       <id>io7m-repos</id>
>       <repositories>
>         <repository>
>           <id>io7m-snapshots</id>
>           <name>io7m snapshots</name>
>           <url>http://repo.io7m.com/snapshots/</url>
>           <snapshots><enabled>true</enabled></snapshots>
>           <releases><enabled>false</enabled></releases>
>           <layout>default</layout>
>         </repository>
>       </repositories>
>     </profile>
>
>     <profile>
>       <id>jogamp</id>
>       <repositories>
>         <repository>
>           <id>jogamp-remote</id>
>           <name>jogamp test mirror</name>
>           <url>http://www.jogamp.org/deployment/maven/</url>
>           <layout>default</layout>
>         </repository>
>       </repositories>
>     </profile>
>
> The source code can either be cloned with the fossil SCM
> (http://fossil-scm.org) or downloaded as a tarball snapshot
> by visiting http://fossil.io7m.com/repo.cgi/io7m-jcanephora/info/tip
> after logging in anonymously (anonymous logins are required to stop
> web spiders from accidentally causing havoc).
>
> I recommend using -Dmaven.test.skip=true, as the test suite requires
> a working OpenGL setup and takes a few minutes to execute.
>
> Any help would be appreciated here, I'm at a loss as to why javadoc
> aggregation has stopped working!
>
> M
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>