-
1. Re: Can't build Ajax4JSF
sergeysmirnov Aug 24, 2007 12:51 PM (in response to chawax)Ajax4jsf project is retired. We are not going to support this repo anymore.
If you have a problem with Richfaces 3.1.0 build, launch maven with
mvn clean install -X
and send the log to asmirnov _at_ exadel.com
P.S. We create the build several times a day on different computers know. No problems yet found. -
2. Re: Can't build Ajax4JSF
chawax Aug 27, 2007 4:47 AM (in response to chawax)OK. It would be a good idea to announce it on Ajax4JSF project mainpage, because I could'n read this information anywhere ;)
Does it mean that Richfaces will include Ajax4JSF components from version 3.1 ? -
3. Re: Can't build Ajax4JSF
chawax Aug 27, 2007 11:22 AM (in response to chawax)I could build from Richfaces 3.1.0 nighlty sources. But no way to build with Richefaces 3.1-RC3 of Richfaces 3.0.1. It looked like problems with dependencies (qdox 1.6).
-
4. Re: Can't build Ajax4JSF
sergeysmirnov Aug 27, 2007 2:39 PM (in response to chawax)"chawax" wrote:
OK. It would be a good idea to announce it on Ajax4JSF project mainpage, because I could'n read this information anywhere ;)
3.1 ?
I guess, you are the person who never reads the announcements and sticky posts on the public forums.
http://www.jboss.com/index.html?module=bb&op=viewforum&f=259
http://www.jboss.com/index.html?module=bb&op=viewforum&f=261"chawax" wrote:
Does it mean that Richfaces will include Ajax4JSF components from version 3.1 ?
Yes, Ajax4jsf components + RichFaces components + brand new components. 64 in total will be on board of 3.1.0 -
5. Re: Can't build Ajax4JSF
chawax Aug 28, 2007 3:49 AM (in response to chawax)Well, I don't think the first thing people discovering Ajax4JSF do is going on the forum to read announcements ;) I went on this forum only when I had problems building Ajax4JSF, not before.
So I still think that just a few words to announce that Ajax4JSF will be folded with Richfaces from version 3.1 would be welcome on this page : http://labs.jboss.com/jbossajax4jsf/
Thanks for your response anyway ;)