Re: [Webmacro-devel] License, Maven

[Tim P. <ti...@pa...>]

On Saturday 22 April 2006 15:57, Lane Sharman wrote:
> I have signed the new license and like it a lot.
>
> re maven: I would like to see a transform operation on the existing
> ditribution so that the existing distribution can be preserved. the
> transform operation would make a copy (much as a copy is made prior to
> compilation). The copy would create maven1/ and maven2/ which would
> allow you to work in a maven1/ and maven2/ build environment if that was
> your gig.
>
> in other words, I do not want to see an either/or. Rather, maven1/ and
> maven2/ depend on using the existing distribution model which works for
> a lot of people. I have to do the distribution to sf so I do not want to
> have to learn a whole new deal to do the distros. There could be 2 tasks
> in build.xml: "copyMaven1" and "copyMaven2" which would set up the new
> structure.
>
> I like the idea of maven as that if you start to manage a lot of
> projects, it does make sense to have  a common distribution model. From
> an SCM standpoint, absolutely concur with the objective of Maven. But as
> a development team, we are pretty comfy with using the current model.
>
> What do you think?

Spot on.
We add the maven files (project.xml and project.properties for maven1 and 
pom.xml for maven2)  and also the checkstyle config files and the job is done.

I have pretty much finished project.xml, I can point to the correct location 
of the new license (I prefer to see these files in the root but can work with 
current location).

I have done an initial checkstyle configuration.

The POM may be a bit more difficult to shoehorn our current structure into, 
but probably not. 

I was wondering if it would be good to publish the jars as 
WebMacro-version-m1.jar and WebMacro-version-m2.jar, not quite sure if this 
would buy us anything. 

There is a Maven Sourceforge plugin, which deals with SF, but I have yet to 
investigate it. 

The above setup would enable the current procedure to remain completely 
unchanged and enable us to publish in Maven form simply by 
maven deploy (for m1) and 
mvn deploy for m2. 

I would like to commit what I have done and play with deploying to 
http://melati.org/maven
I have yet to setup a m2 repository, but when I have done that and 
ironed out the wrinkles we should be fit to go. 

I would also like to version the jars in lib in accordance with 
http://www.paneris.org/~timp/webmacro/dependencies.html

cheers
TimP