Yep. Absolutely critical items. Thanks for that Guillaume :)
On 9/6/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
Before being able to release, we have to ensure that the following points
are handled:
* the main pom should inherit org.apache:apache:3 (optional, but...)
* the groupId should be set to org.apache.ode (rather than ode)
* the version should be set to 2.0-incubating-SNAPSHOT
* each incubating binary artifact (jar, war, jbi component, etc..)
deployed
on an m2 repo should include the following stuff
META-INF/DISCLAIMER (the incubator disclaimer)
META-INF/LICENSE (the ASL)
META-INF/NOTICE (an up-to-date notice)
* each distribution (binary / source) should include these files at the
top level
Note that while the DISCLAIMER / LICENSE are easy to handle, the NOTICE
file may require some (hard) work.
In addition, we need to remove the hibernate dependencies from the trunk
before being able to release.
Sorry, but else, you're 99% sure that the incubator PMC will -1 the
release...
so it's best to do it before than after.
On 9/6/06, Matthieu Riou <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I think it would be a good idea to make a first release of Ode soon. The
> code is getting stable again after all the IAPI and deployment
> refactorings
> and we have something that would be pretty useable. If we want people to
> start using Ode, binaries are also much better than the "build yourself"
> approach. I think we'd distribute two different distributions, one
> packaged
> with Axis2 to deploy in a servlet engine and another one to deploy in a
> JBI
> container (ServiceMix).
>
> What do you think?
>
> Matthieu
>
>
--
Cheers,
Guillaume Nodet
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
