Hi all!
As a test I've been trying to convert one of our projects to M2.
The project in question makes use of a custom taglet library during
creation of the project documentation.
In spirit of Maven I thought I could simply add the taglet library
to an internal repository and add a dependency to it in the project.
Here's what I did in the project POM to achieve this:
<project>
...
<dependencies>
<dependency>
<groupId>ch.ergon.libx</groupId>
<artifactId>taglet</artifactId>
<version>1.2.1</version>
<scope>compile</scope>
</dependency>
</dependencies>
...
</project>
I was a little puzzled that there is no 'report' scope but since I'm
new to M2 I thought what the heck, let's try with 'compile'...
OK, next I tried to add a configuration to the javadoc:javadoc goal
that ensures that the taglet is used:
<project>
...
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<taglet>ch.ergon.libx.taglet.ETaglets</taglet>
<tagletpath>${maven.repo.local}/ch/ergon/libx/taglet/1.2.1/taglet-1.2.1.jar</tagletpath>
</configuration>
</plugin>
</plugins>
</build>
...
</project>
Looks like a very ugly workaround that I have to include to dependency
again, but then I wanted to use the taglet from the repository and
though I'd just give it a try and clean up afterwards.
As it turns out however ${maven.repo.local} is not available at all
(i.e. the log shows a conversion to 'null') and the whole story doesn't
feel right anyway like this...
... therefore: "What is the suggested method of using taglets?"
In an ideal world the taglet would just be stored in the maven repository,
could be added as a dependency and be included automatically.
In hopes that I'm not the first trying to get taglets to work with M2, :)
// Bruno
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
