1) The url has to contain the major version number (ex: ../v1/.., ../v2/.., ../v3/..). This allows for different client versions to work against their supported data. Not sure if maven supports this OOTB or if we just release our own major version LATEST.
Without changing the POM if you wanted Maven to switch between /v1, /v2 or /v3 that would require either user specific properties overriding the project specific one or one could call different profiles. On Fri, Jul 18, 2014 at 4:07 PM, Reza <[email protected]> wrote: > Is that URL HTTP? > > Currently there are 2 requirements for downloading devicemap resources > over the internet: > > 1) The url has to contain the major version number (ex: ../v1/.., > ../v2/.., ../v3/..). This allows for different client versions to work > against their supported data. Not sure if maven supports this OOTB or if we > just release our own major version LATEST. > > 2) The download has to be fast. Don't want initialization taking more than > 1 to 2 seconds. Putting a CDN infront of the URL will solve this. > > Am I missing anything else...? > > > ________________________________ > From: Bertrand Delacretaz <[email protected]> > To: "[email protected]" < > [email protected]>; Reza <[email protected]> > Sent: Friday, July 18, 2014 9:38 AM > Subject: Re: URLResource reading from svn.apache.org by default? > > > Hi, > > On Fri, Jul 18, 2014 at 3:06 PM, Reza <[email protected]> > wrote: > > ...a common complaint about using device classification is that you have > to > > constantly track and maintain new devices... > > You might also use the Maven distribution mechanism for these data > files - in another project I'm using pax URL to resolve URLs like > > mvn:org.apache.sling/org.apache.sling.commons.log/LATEST > > to get the corresponding artifact from a Maven repository. > > The nice thing with that is that you don't have to worry about > infrastructure. > > > > > -Bertrand >
