Re: Best practices for inlining build (revision) number into GWT App?

Hi Honza,

your implementation sounds intresting.
Can you provide more informations about your solution?

Thanks Frank

 
Am Mittwoch, 12. Juni 2013 09:50:41 UTC+2 schrieb Honza Rames:

I have a XML file that stores various information about my build and is updated by a Linker which increments build number each build I make. And I have a generator that returns an interface that I can use in GWT app which includes the build number, revision, build date etc.

Regards

Honza

On Tuesday, June 11, 2013 7:17:42 PM UTC+2, Joseph Lust wrote:

For various reasons you need to know the revision of the GWT app code. For example to verify that the server API is not newer than the JS code (i.e. if you deploy GWT JS to a CDN).

Some common approaches which I find to be rather hackish:

• Use Maven replacer to replace a sequence in a source file at the validation stage and have that inlined into your GWT file at compile (hackish)
• Use Maven replacer or Maven war plugin filters to add the build number to the index.html page, or a backend service (JS code still not independently versioned, more API calls)
• Hardcode it (don't hardcode things)

After two years, the best method I've see is to create a code generator to allow deferred binding of the build number. This however has always stuck me as massively overkill to add a number to a build artifact.

So, I was curious how others here have dealt with this common issue. Hopefully there is a simpler way.

Sincerely,

Joseph

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.