I have a subproject in a large multi-module project with the following
dependency:
--------------
<dependency>
<groupId>org.apache.httpcomponents</groupId>
<artifactId>httpclient-osgi</artifactId>
<version>4.5.2</version>
<type>bundle</type>
</dependency>
--------------
The project builds without error.
I was working on implementing Javadoc generation in this tree. When I ran the
"aggregate-jar" goal from the toplevel, it gave me an error saying it couldn't
find this artifact. This was initially mystifying (and still is somewhat).
We use an intranet Maven repo, so it's pulling from that instead of
mavencentral. When I looked in the repo itself, I noticed that it had that
artifact, but not the "bundle" type. It just had the plain jar (I assume I
would see something in the directory saying it was a bundle).
When I looked in my local repo, it also only had the plain jar (I even cleared
out the local repo and reran the build to regenerate it).
I then tried commenting out the "type" property and also cleared out that
section of the local repo. As before, the subproject built without error. In
addition, the toplevel Javadoc generation did not fail.
It seems like the regular Maven dependency mechanism was happy with getting
just the "jar" artifact, even though the dependency specified the "bundle"
type, but the Javadoc generation would only work with the exact type as
specified.
I don't know if there's a bug here, but there's certainly something odd going
on here.
Can anyone explain what happened here?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
