Dennis Sosnoski wrote: > All the dependency jars need to be included in the distribution > download, but I'd like to move away from having them in CVS (or SVN, in > the future). Nigel has got me using Ivy for dependency management in > JiBX/WS, so I wonder if we can usefully do the same thing for the main > project? Ivy would allow us to add dependency management features to the existing Ant build. One issue that we need to address is how to use the Ivy dependencies to create a Maven pom file, and how to publish to the Maven repositories. I'll look into this for JiBX/WS. Ivy does have a makepom task to create a Maven pom from the Ivy dependency file. We could then use either Jerome's shell scripts or the Maven Ant tasks to publish to the Maven repositories.
> I suppose one issue would be the Eclipse jars - from a quick look I don't see > a Maven repository for these jars. Thoughts? > Are these jars available from a location with a structured URL? If so, we should be able to create an Ivy settings file to resolve the Eclipse jars using the URL. Jerome - any thoughts on how we can handle these "missing" jars for Maven users using the JiBX 1.2 release? Nigel. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ jibx-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jibx-devs
