Great news Donald!

I guess the idea to make this new repository branch to act as a geronimo specific maven repository that can be relied on and pointed to in geronimo project pom:s !?! This would (among other things) cut down the steps (and build instructions) needed for building special purpose assembles and plugins as you would no longer need to check out the vXXX gernonimo artifact subdir and manually do a mvn install into your local repos before you can scratch build your project.

Simplicity is  king!

thanks
  peter petersson

Donald Woods wrote:
We have danced around the problem of not being able to build Samples, Plugins or GEP from a clean m2 repo without building the Server's repository subdir for long enough. I believe it is time to create the following location in SVN -
    geronimo/repo
Which would hold our private patched artifacts of other projects (like Tomcat, Pluto, ...), just like the OpenEJB team has done for some of their private depends. I don't see this as a major hit to the svn infrastructure, given the jars (10 for 2.2.) will only be downloaded when starting with a clean m2 repo or when we publish any updated depends.

Unless someone comes up with a better solution by Friday morning, I'll create the new repo branch and populate it with the latest 2.1.2 and 2.2 patched artifacts tomorrow.


-Donald

Reply via email to