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 (http://www.sparrowmailapp.com/?sig) On Tuesday 27 March 2012 at 09:37, Thorbjørn Ravn Andersen wrote: > > Hi. > > > > > > 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. > > > > > > /Thorbjørn > > > > > > > > > > > > _______________________________________________ > m2e-users mailing list > [email protected] (mailto:[email protected]) > https://dev.eclipse.org/mailman/listinfo/m2e-users > >
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
