gwt:debug

John Mazzitelli mazz at redhat.com
Thu Oct 7 12:40:15 UTC 2010


[sending to rhq-devel mailing list so community knows about this]

Even though Lukas fixed this so it can still work on mvn 2.1 (see below 
for more info), we should require maven 2.2 to build anyway - any 
objections to bump up the required maven version to build RHQ?

This is where we talk about the required mvn version:

http://rhq-project.org/display/RHQ/Building+RHQ#BuildingRHQ-InstallMaven


On 10/07/2010 06:03 AM, Lukas Krejci wrote:
> Mazz pointed out to me yesterday that I broke mvn gwt:debug with my changes
> that got the core/domain rid of gwt dependencies.
>
> It wasn't broken per se but because coregui now contains 2 GWT modules, the
> gwt:debug goal needed to be told which of those modules to start debugging.
>
> The only way I could find that would fix that inconvenience unfortunately only
> works with maven 2.2.0 and later.
>
> So if you have maven 2.2.0 and up, you can yet again just issue
>
> mvn gwt:debug
>
> and it should start debugging CoreGUI but if you're stuck with older versions
> of gwt, you'll need to do:
>
> mvn gwt:debug -Dgwt.module=org.rhq.enterprise.gui.coregui.CoreGUI
>
> I didn't change the minimum version of maven we need in the root pom


More information about the rhq-devel mailing list