I think this is about right given how things are setup. Step one
makes my brain hurt though...
* * *
Since we really treat each spec as its own project, we should drop
the uber "specs" project and promote each spec to a top-level
project. Then everyone will know how to update them, as it will be
like every other project... no magical mystical svn mv back and forth.
--jason
On Jan 7, 2007, at 8:54 PM, Tim McConnell wrote:
Hi, I need to change one of the spec files for JSR-88 and am a
little unclear about the process. So, here's what I've done thus
far (on my local filesystem only) and was wondering if it seems
correct ??
1) Copied the \specs\tags\1_1_1\geronimo-spec-j2ee-deployment
directory to \specs\trunk\geronimo-spec-j2ee-deployment
2) To follow the convention I inferred under specs\trunk I then
renamed that directory to \specs\trunk\geronimo-j2ee-
deployment_1.2_spec
3) Edited files that I needed to updated...
(e.g., \specs\trunk\geronimo-j2ee-deployment_1.2_spec\src\main\java
\javax\enterprise\deploy\spi.DeploymentManager.java)
4) Changed pom.xml under \specs\trunk\geronimo-spec-j2ee-deployment
5) Changed pom.xml under \trunk
Finally, do we want to rename specs which include "J2EE" to
something that includes "JEE5". e.g., \specs\trunk\geronimo-jee5-
deployment_1.2_spec
--
Thanks,
Tim McConnell
