<div dir="ltr">I don't think I'm the only one in the community who thinks we should reconsider our GWT usage...</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 28, 2013 at 12:55 PM, Eli Mesika <span dir="ltr"><<a href="mailto:emesika@redhat.com" target="_blank">emesika@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
----- Original Message -----<br>
> From: "Yair Zaslavsky" <<a href="mailto:yzaslavs@redhat.com">yzaslavs@redhat.com</a>><br>
> To: "Martin Perina" <<a href="mailto:mperina@redhat.com">mperina@redhat.com</a>><br>
> Cc: <a href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a><br>
> Sent: Wednesday, August 28, 2013 5:34:42 AM<br>
> Subject: Re: [Engine-devel] Java Development Lifecycle<br>
><br>
><br>
><br>
> ----- Original Message -----<br>
> > From: "Martin Perina" <<a href="mailto:mperina@redhat.com">mperina@redhat.com</a>><br>
> > To: <a href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a><br>
> > Sent: Tuesday, August 27, 2013 2:54:38 PM<br>
> > Subject: Re: [Engine-devel] Java Development Lifecycle<br>
> ><br>
> > For me the most time consuming problem is GWT compilation.<br>
<br>
When compiling GWT it build both Admin & User portals , it duplicates the compilation time , can this please be separated such that I can build admin portal without a user portal and vice verse ???<br>
<br>
It would be<br>
> > really<br>
> > nice<br>
> > if we can agree to create some clear separation between frontend and<br>
> > backend<br>
> > part, for<br>
> > example if frontend would communicate with backend only through REST API,<br>
> > GWT<br>
> > would<br>
> > have to recompile only if REST API or some frontend code has been changed.<br>
> ><br>
> > It's not something what can be done i short term, but it would be nice if<br>
> > we<br>
> > can<br>
> > find a way how to do it and create a schedule for this task.<br>
><br>
> +100<br>
><br>
> ><br>
> ><br>
> ><br>
> > ----- Original Message -----<br>
> > > From: "Mooli Tayer" <<a href="mailto:mtayer@redhat.com">mtayer@redhat.com</a>><br>
> > > To: "engine-devel" <<a href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a>><br>
> > > Sent: Tuesday, August 27, 2013 1:29:01 PM<br>
> > > Subject: [Engine-devel] Java Development Lifecycle<br>
> > ><br>
> > > Hello,<br>
> > ><br>
> > > I've been working on the engine for a few month now,<br>
> > > And I feel I have not yet been able to find a productive and fast<br>
> > > approach<br>
> > > for Java development in different engine components.<br>
> > ><br>
> > > This revolves mainly around:<br>
> > ><br>
> > > Compiling and deploying artifacts:<br>
> > > ==================================<br>
> > > If I want to check a small change in the engine,<br>
> > > Be it in an artifact that is part of engine.ear or when I am working on<br>
> > > one<br>
> > > of the side tools<br>
> > > that might run as a service (e.g ovirt-engine-notifier)<br>
> > > or just a single jar (engine-manage-domains)<br>
> > > It is essential to compile only parts of the project and not all of it.<br>
> > ><br>
> > > This can be achieved usually quite easily with mvn,<br>
> > > however afterwards I would like to be able to also deploy and run it<br>
> > > locally<br>
> > > or even take all jars comprising a project and run them exploded inside<br>
> > > my<br>
> > > IDE<br>
> > > (I use intellij idea) so I can enjoy live code editing and other benefits<br>
> > > idea<br>
> > > jboss & gwt integration offers. I have been using remote debug<br>
> > > (which is available by default in the engine and non existent in other<br>
> > > jars<br>
> > > so<br>
> > > I have to tamper manually with a python service file to add debug flags -<br>
> > > see<br>
> > > next)<br>
> > > But it's not as powerful as running inside an IDE and I feel my current<br>
> > > development lifecycle is<br>
> > > not as fast and productive as it could have been.<br>
> > > (I do understand the engine is complex regarding configuration and<br>
> > > deployment, so it's a challenge)<br>
> > ><br>
> > > Configuration:<br>
> > > ==============<br>
> > > This might be more of a todo item, I'm not sure..<br>
> > > After deployment of an artifact to run on a machine(again, engine,<br>
> > > notifier<br>
> > > or whatever)<br>
> > > if I want to change it's configuration<br>
> > > (configure it for remote debug as mentioned or change it's logging<br>
> > > behavior<br>
> > > and so on)<br>
> > > It seems I always have to do it in a different place which I always spend<br>
> > > hours finding.<br>
> > > It could be great if for all artifacts configuration could be streamlined<br>
> > > and<br>
> > > monolithic<br>
> > > across different components.<br>
> > ><br>
> > > These issues might seem obvious to some of you or unneeded to others, but<br>
> > > I've decided to shout out<br>
> > > in engine-devel because my usual way of approaching individuals has not<br>
> > > got<br>
> > > me very far,<br>
> > > and also because I'm convinced some of you have found ways to be<br>
> > > productive<br>
> > > I<br>
> > > am unaware of -<br>
> > > Please share them! Others may have their own good ideas & approaches(or<br>
> > > their<br>
> > > own needs).<br>
> > ><br>
> > > Thanks,<br>
> > > Mooli.<br>
> > > _______________________________________________<br>
> > > Engine-devel mailing list<br>
> > > <a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br>
> > > <a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/engine-devel</a><br>
> > ><br>
> > _______________________________________________<br>
> > Engine-devel mailing list<br>
> > <a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br>
> > <a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/engine-devel</a><br>
> ><br>
> _______________________________________________<br>
> Engine-devel mailing list<br>
> <a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/engine-devel</a><br>
><br>
_______________________________________________<br>
Engine-devel mailing list<br>
<a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/engine-devel</a><br>
</blockquote></div><br></div>