[PATHC] javadoc artifact is installed/deployed with a weird extension

Patch that fix the problem (without the java files - I will provide it in another attachment)

Missing java files (as I could not cvs add it)

New patch (previous one didn't have maven.jar on dependencies - my bad)

Ultimate patch, with test cases and added files (thanks Carlos for the Eclipse tip

PS: final patch is MPJAVADOC-38-full.patch

Hello Felipe,

Thx for your work. I will look at it during my holidays (second half of august).
I agree with you that it is annoying to generate .javadoc files.
The only problem that I can see is if a user want to create a dependency to the javadoc (don't know why, but ...) it will not work because maven will continue to try to download a javadocs/XXX.javadoc file.
Another solution might be to not use a javadoc type fot the artifact but a zip type.

Arnauld,

I haven't though about the automatic download issue, as I was thinking in the problem from a human being point of view . In our case, for instance, we have trouble distributing our javadocs, as people would try to double click these files.

Anyway, I would vote for the zip type solution - it would be just a matter of changing one line of code at SQLDistTypeHandler.java

Feliep

The type for the javadoc is "javadoc.jar" when it is deployed on a repository.

There's one usecase for specifying the javadoc as dependency in your pom. When using IDEs you want the javadocs for your libraries to be available for the IDE as well, not only the jars.