Ok, you're right about the compile phase. I'm sorry I jumped to conclusion, but most posts about these things are caused by running a specific goal instead of the lifecycle.
What happens if you execute mvn compile Does it work? What version of maven are you using? Have you tried with 3.0-alpha? Maybe the gwt-maven-plugin User mailing list can provide better support. Or maybe someone else has more indepth knowledge of plugins and knows exactly how it works. Your idea sounds as it could be the problem here. /Anders On Thu, Jan 21, 2010 at 02:54, Ryan Stewart <[email protected]> wrote: > > > Anders Hammar wrote: > > > > When you execute > > mvn gwt:run > > you're not executing the maven lifecycle - just that goal of the gwt > > plugin. > > Thus, the plugin bindings you've specified are not executed. Try > > mvn install > > instead. > > > > No, as I mentioned in my original post, the gwt:run goal causes the compile > phase to execute, meaning that the properties plugin does execute. You can > see it in the output I included. I'm thinking that maybe running it in this > way, the gwt plugin is executed somehow "outside" of the lifecycle that the > compile phase is executed in. > -- > View this message in context: > http://old.nabble.com/Property-loaded-by-plugin-not-available-to-gwt%3Arun-tp27227122p27251689.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
