I agree, that this should not block us from releasing the bits.
-Matthias
On Mon, Aug 23, 2010 at 11:53 PM, Leonardo Uribe lu4...@gmail.com wrote:
Hi
Ok. The idea in the future is integrate that work, but for now that is not a
stopper for a release.
The plan from my side for the next
Hi
It could be good to do a release of myfaces test project after the release
of myfaces site skin.
Personally, I think the code is good for a release, but if someone has any
objection about it, this is a good moment to say it.
regards,
Leonardo
Hi Leo,
I would like to discuss the internal structure of the myfaces test project
before we do a release of it, because I want to integrate the GSoC
webapp-tests into our codebase. However this code is not ready for a release
and should be an own module, independent from the current MyFaces test
Hi
Ok. The idea in the future is integrate that work, but for now that is not a
stopper for a release.
The plan from my side for the next weeks is do the following releases:
- Myfaces Site Skin 1
- Myfaces Test 1.0.0
- Myfaces Core 2.0.2
- Tomahawk 1.1.10
regards,
Leonardo Uribe
2010/8/23
Hi,
OK, I just wanted to let you know!
Great!
I finally want to do the myfaces archetypes release, but I also want to wait
for the next OpenWebBeans-release before releasing them.
Regards,
Jakob
2010/8/23 Leonardo Uribe lu4...@gmail.com
Hi
Ok. The idea in the future is integrate that
+1 for releasing myfaces-test. We've been using it internally and it works
relatively well (although there are a couple of issues). We have also
extended it with Spring integration, which is quite handy.
---
Kito D. Mann | twitter: kito99 | Author, JSF in Action
Virtua, Inc. |
