i agree with that but i'm doing what i can. etch-29 is a new issue, btw.
not even sure that issues
that don't change api or functional contracts need to be voted at all.
do we have to vote build
changes? what about small improvement to javadoc or unit tests? but
since i don't have working
approval for 1.0.2 yet...
scott out
James Dixson wrote:
Is it really necessary to vote on each and every thing going into 1.0.2. Why
don't we instead vote on the list of Jira issues to include in the release
in one vote?
If there is contention as to something to include/not include, then we can
modify the list before finalizing?
Thoughts?
BTW +1 on including ETCH-29
On 1/22/09 3:40 PM, "Scott Comer (sccomer)" <[email protected]> wrote:
rick has extended the existing maven install script to include the
other artifacts which are useful, and to also include the bundled
source. there is no risk to core etch functionality to do this.
i've tested his changes and they work.
Installing all Maven artifacts along with their sources.
--------------------------------------------------------
Key: ETCH-29
URL: https://issues.apache.org/jira/browse/ETCH-29
Project: Etch
Issue Type: Improvement
Components: build
Reporter: Richard Bolkey
It's handy to have the other packages Etch produces installed as
artifacts in the local Maven repository (in case your doing plugin
development or something). Also, installing the source package is VERY
handy when debugging.
