[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Needing to hint Javadoc to m2e

Maybe the solution is to get javadoc jars onto Maven central, thereby solving it for everyone...

On 03/28/2012 01:29 AM, Thorbjørn Ravn Andersen wrote:

We do have a Artifactory repository, but we primarily use it as a cache.  I would like a solution that only depends on our own code and Maven Central, to keep it as simple as possible.


I’ve noticed that we can configure m2e to be quiet about error situations, so it would be nice if this could be done too.





From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx] On Behalf Of Asaf Mesika
Sent: 27. marts 2012 21:37
To: Maven Integration for Eclipse users mailing list
Subject: Re: [m2e-users] Needing to hint Javadoc to m2e


Do you have a Nexus / Artifactory in your organization? I mean, you can easily place the source and java doc there. If it's something that keeps getting refreshed, you can setup a build process job in Jenkins or a similar CI tool to push the changes and deploy it to Nexus / Artifactory


Asaf Mesika
Sent with Sparrow


On Tuesday 27 March 2012 at 09:37, Thorbjørn Ravn Andersen wrote:



I have a problem with some legacy artifacts which do not have source or javadoc artifacts placed in Maven Central, but where the Javadoc has been published on a webserver, and where I have a source jar present in my workspace.


I would like to be able to hint to m2e that for a given artifact in the pom.xml, I would like to have my source jar “attached” to it as the source and the URL “attached” to it as the Javadoc location.    I would not like to modify the existing artifact or put dummy artifacts in my local repository as I would like a robust solution.


Any suggestions


(for StackOverflow participants there is 250 easy points for this on http://stackoverflow.com/q/9699631/53897)


Thanks for any suggestions.






m2e-users mailing list


m2e-users mailing list

CONFIDENTIALITY NOTICE: This message is intended only for the use and review of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message solely to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify sender immediately by telephone or return email. Thank you.