Hi to all, sometimes i write on maven, but my are ideas, just to discuss with other Pivot developers and for mid-long term plans, don't worry ...
> 1) Distribute Pivot artifacts via Maven for consumption by other projects Yes, i think this would help Pivot users to integrate in their projects, some months ago i tried to convert the Started example to maven and after this the full projects shrink down to few KB of zip (stripped out all jars), for example. But i had to install all pivot jars manually in my repository, and wasn't the best ... One time we'll have a release i think there is a system to put release jars in the maven repository, in the right way (asking to someone i suppose) ... For this, i could send my samples pom files, if/when needed as a starting point. > 2) Use Maven to build Pivot itself I agree with all, until major benefits will come (and someone of us will become a maven expert i didn't suggest to migrate). One powerful thing I've seen is the ability to remove all required jars, and let maven handle all of them, for example i had a server-side resource to call with a unit test, so i put Jetty as a requirements (and in the future I'd like to move to Grizzly or other ...), and handle start/stop of all during that unit test, including the test pivot application. Another test was to modularize a Pivot Application into modules, thinking at a mid size application (1 common + 0 .. n modules), and handling builds, etc., and putting it inside a full JavaEE Application, to try to identify problems, but was only an experiment (working but) at beginning ... But things like this maybe could help in projects other than Pivot base ... maybe a variant of the Starter (dedicated to maven) could be a simple test. And this is a sample usage of point 1. What do you think ? Best regards, Sandro
