I would leave the m3 branch alone... its not worth the effort to
change things there... though you may want to merge the myfaces repo
changes (configs/jasper) from trunk, to help with SNAPSHOT resolution
when Mvn tries to perform updates.
As for the rest of these, I mentioned a way to handle this in the
short-term in a mail I sent about "Local module repos and SNAPSHOT
artifacts".
* * *
What's the motivation to do this to m3 (which is a very short-lived
branch)?
--jason
On Feb 27, 2007, at 8:38 AM, Matt Hogstrom wrote:
In doing the release I've run into a few different repos scattered
in the tree. I'd like to move those repos to a top level
repository directory for the tree. This helps out so that any
artifacts that are related to a release are put in one place.
Here is the list of repos:
.//applications/console/geronimo-console-standard/repository
.//applications/console/geronimo-console-standard/src/main/java/org/
apache/geronimo/console/repository
.//applications/console/geronimo-console-standard/src/main/webapp/
WEB-INF/view/repository
.//applications/geronimo-dojo/repository
.//applications/geronimo-uddi-server/repository
.//configs/jasper/repository
I would prefer to move these artifacts up to a top level ./
repository directory that is maintained as part of the tree and add
this repo at the root level. I'm wondering if there is a specific
reason that they are located on a per module basis?
I'm heading for a plane and will be disconnected for a while so if
someone has some spare cycles it would be most appreciated if this
could be done in the 2.0-M3 tree.
I'd like to discuss this for trunk.
