As suggested, I'm putting this up here again because it went unanswered.
Frankly, I have no idea what maven is and how it could be useful for us (and http://maven.apache.org/about/whatismaven.html does not really given me more of a clue, and I am too lazy to check out your project to find out how you use it ;) ).
Hence, I do not know how much the following relates to this: I am currently working on ideas to improve the Java UNO runtime in such a way that one can get rid of CLASSPATH and still have Java UNO components that bring with them their own (Java classes representing) UNO types. This probably means that there will be one small additional JAR through which all all of Java UNO (including components) is loaded. At runtime, an application will thus only have to access this one JAR. (However, at compile time, all the current JARs have to be available, and it looks to me that what you are doing with maven is directed to compile time, right?)
In case you feel the need to set something up for maven and just want to go ahead: I would like to strongly discourage you from taking any deliverables from OOo (i.e., some JARs) and making them available somewhere else---those deliverables will be outdated quickly, and it can become a nightmare if people use that external, outdated stuff, have problems with it, and come here at OOo to complain about it...
-Stephan
Thanks, Mike
--- Mike Traum <[EMAIL PROTECTED]> wrote:
I was wondering if it would be possible for you to start making the api jars available through a maven repository, either your own, or ibiblio. This would make it MUCH easier to develop a java client app, as a plugin could easily be developed to create the jar (and I would probably do this right after they arrive in a repo, as I basically already have the code for this in my project).
The maven repo could also get used by developers who use ant, where it is becoming increasingly more common to use the ant:get task to retrieve build dependencies.
The only change, as I can see, would be that you would want the Bootstrap in a jar as well.
If you're interested in what this looks like using maven, see the CVS for my http://oogalleryimport.sourceforge.net project. It would be much simpler, though, if we could get a repo going because I would then rip out all of that code in maven.xml which help's add the Bootstrap to my app and create a plugin.
Thanks, mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
