Ajax4JSF SVN: maven only?

[robjellinghaus]

I just checked out https://svn.jboss.org/repos/ajax4jsf/trunk/gwtjsf/ in order to land my changes. It looks like there is no more build.xml file at all. Is it the case that I need to install Maven in order to build gwtjsf now?

If so, it's kind of a problem, because my changes rely on an unreleased preview version of GWT (available http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/711dc76b5aefe902/#). How can I build my new gwtjsf changes with Maven, when I can't update the trunk/gwtjsf/pom.xml file (because there is no new 1.4.0 released version of GWT yet)?

Sergey, Alexandr, Igor, please advise?

I will prepare to land an ant build file just so it is possible to build gwtjsf against the 1.4 GWT preview (which is what people in the users forum are asking for). But if you guys don't let me know what you'd like me to do, I will just zip all the source up and put it on my website, and I will have to hold off on officially landing until GWT 1.4.0 releases for real and I can hook it into Maven.

Cheers,
Rob

[robjellinghaus]

In fact, it seems a little worse than this. As far as I can tell (and I admit to having only just tried Maven for the first time tonight), the gwtjsf subtree is not compiled at all by Maven.

I ran "mvn clean install" in ajax4jsf/trunk, and it did a whole lot of downloading and then did what was apparently a successful build, generating an ajax4jsf/trunk/framework/target/ajax4jsf-1.1.1-SNAPSHOT.jar file. But that jar file contains no gwtjsf classes (no org.ajax4jsf.gwt classes) at all. Neither do any of the other .jar files in any of the other target/ subdirectories.

What am I missing? Is the gwtjsf subtree being compiled to somewhere else? If so, where? Or is that subtree just not really integrated into the Maven build yet? Please don't tell me that part is up to me, as otherwise you run a dire risk of my screwing up the Maven build... it would be better for someone who knows Maven to do that part.

Cheers,
Rob

[sergeysmirnov]

I think we have to switch to Maven the g4jsf also.

[robjellinghaus]

I think I agree.

Is that something you guys plan to do? If so, when?

If I can help, please let me know how. (If I do not hear from you, I will leave it up to you.)

Thanks.

[sergeysmirnov]

Actually, the development process with g4jsf should be migrated to Maven as well as building of g4jsf package along with other ajax4jsf stuff (with the same mvn install). We are not going to start this job before the portal support will be finalized. So, if you are interested do not postpone this migration, you contribution in this process might be very beneficial.

[robjellinghaus]

OK. I will look into it. Thanks for clarifying your intention here.

Cheers!
Rob

[robjellinghaus]

I am going to wait on this until the final GWT 1.4 release, so that I can add the GWT 1.4 libraries as a Maven dependency, rather than having to sort out how to include them as local libraries (and then undo that work once the actual release ships).

Meanwhile, I will go back to working on my Seam/G4JSF blogging example.

Cheers,
Rob