I'm wondering how best to manage releases/versions. Ideally Google would publish all jars to public maven repos this would be a non issue but since there not in maven and there are so many jars I'm trying to make sense of how to manage this.
When a new version is released, i.e. 1.40 (since the jars are not in maven) I'd like to just create one uber-jar that contains everything for that version. I understand probably only small parts (jars) changed but I don't see a way to know what jar(s) changed. Furthermore the version on the jar names isn't right as that's just the spec version not the impl version so that can't be used to know what changed. What are all the x-meta jars for? I tried just un-jaring all jars and creating one uber jar but that didn't work...I suspect because of the x-meta jars. Can someone that uses this in maven shed some light on how best to manage this? If I build from source, can I make one uber jar? -- You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi?hl=en.
