Hi,

I've used other build tools (mostly make and ant, with a smattering of autoconf and imake), but I'd like to move to Maven. However, I'm having a lot of trouble getting started.

I'm starting a new project that depends on another local project (of which I'm also a developer), and I want my new project to depend on the old one's jar file (let's call it old-1.0.jar). I figured out how to put old-1.0.jar in a local repository so Maven could find it.

The problem is that I'm using Eclipse with the Maven plugin, and I'd like Eclipse to know about the source, or at least the javadocs, for the old project. But I can't figure out how to attach source or javadocs to old-1.0.jar. I know how to do it with the normal Eclipse UI, but when I try that it immediately disappears (I guess the Maven plugin overwrites it).

So I thought there must be a way to put the source or at least javadocs in the local Maven repository and associate them with old-1.0.jar. But I can't figure out how. All the docs about repositories that I can find talk about the code jar file or say (in essence) "use Maven for your project and it will manage the repository automagically for you." This would be great, except that the old project is built with a complicated ant script, not with Maven, and I don't want to convert the old project to Maven just so my new project can use Maven.

I apologize if this is not the right forum for this type of question. I've searched the FAQs, the website, the mailing list, the web at large, all to no avail.

Thanks!

- Chris

<editorial frustration-level="high">
What I'd *really* like is to be able to tell Maven, "This new project depends on the jar file old.jar, which is in this location (which happens to be in the new project). And the old project's source files are over there and its javadocs are there." I've read the reasons why the Maven folks think storing jars in CVS is a bad idea, and I think they have a lot of good points. But I don't want to set up a repository and go through all this hassle just to try out Maven with my new project. If and when I'm convinced that Maven is really all that, then I'll be willing to jump through the hoops to do everything the Maven Way. As of now, although it seems like Maven will have advantages in the future, it's not at all clear to me that they outweigh the annoyances.
</editorial>

--
----------------------------------------------------------------------
A. Chris Long           [EMAIL PROTECTED]
Principal Scientist     703-652-1600 x207
Global InfoTek, Inc.    www.globalinfotek.com
----------------------------------------------------------------------


Reply via email to