Re: Moving Spindle IDE agnostic code into Maven projects
Hugo Palma <[email protected]> Thu, 26 Jan 2006 11:23:33 +0000
| Newsgroups | gmane.comp.ide.eclipse.spindle.devel |
|---|---|
| Message-ID | <[email protected]> |
All great news. I feel that everything is falling into place. About embeding the jars in the project. With Maven 2 transitive dependencies if you include those jar as dependencies of you Maven project they will be made dependencies of whoever uses the project itself. Not sure how this behaviour will fit in the eclipse/maven2eclipse project though. If transitive dependencies don't solve the problem i can see two other solutions: - Use the ant-run plugin to unjar the jars into your output dir just before the packaging phase. This way the contents of the jars will be included in the project artifact. - Use profiles to copy the jars to your IDE project lib folder when you install the project. Cheers Hugo On 26/01/06, Geoff Longman <[email protected]> wrote: > > Didn't make sense to have that stuff in the Eclipse plug-in anymore. > > And while I was at it I made a package naming change that is looong > overdue. > > com.iw.plugins.* > > becomes > > net.sf.spindle.* > > 'com.iw' was chosen as the company I owned at the time was Intelligent > Works (iw get it?) > IW is long dead (although the corpse jumps up now again to bite me in the > ass). > > There is a new module in the sf repo called 'spindle-libraries', in > there are two Maven projects inside: > > spindle-core; and > spindle-parser > > I'm a Maven newbie so it took so long to get it going that the > 'spindle-parser' project is actually empty right now. Will fill it up > tomorrow. BTW I have two jars that should just be in there. There's no > source available and thus nothing to build. Any tips on how to embed > these into the project. Maybe unjar them somewhere in the project? > > If your IDE of choice is Eclipse, the projects are configured to work > best in an environment that includes the Maven 2 plugin (Eclipse > plugin that is) update url is http://m2eclipse.codehaus.org/ > > One could check out spindle-libraries outside of the workbench and > then import the sub-projects into Eclipse, or one could just import > the subprojects directly. I think either will work fine. > > The tests were light to start with but it seems most had Eclipse > dependencies and thus are not destined to sit in spindle-core. Guess > I'll have to write more tests! > > Geoff > > > -- > The Spindle guy. http://spindle.sf.net > Get help with Spindle: > http://lists.sourceforge.net/mailman/listinfo/spindle-user > Blog: http://jroller.com/page/glongman > Feature Updates: http://spindle.sf.net/updates >