Re: Fixed Locations for Build Artifacts?
I don't see this code as being worth maintaining, since Google often changes build tools versions and we barely have the resources now to play catch up. On Mar. 11, 2018 8:05 p.m., "Terence M. Bandoian" wrote: > Would it make sense to copy build artifacts to fixed locations, with fixed > names, and to publicize those locations and names for the use of downstream > tools? This would help avoid unnecessary breakages when the build tools > used or the project structures generated by Cordova are modified. > > -Terence Bandoian > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Fixed Locations for Build Artifacts?
Would it make sense to copy build artifacts to fixed locations, with fixed names, and to publicize those locations and names for the use of downstream tools? This would help avoid unnecessary breakages when the build tools used or the project structures generated by Cordova are modified. -Terence Bandoian - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Nightly build #657 for cordova has failed
Nightly build #657 for cordova has failed. Please check failure details on build details page at https://builds.apache.org/job/cordova-nightly/657/ You can also take a look at build console: https://builds.apache.org/job/cordova-nightly/657/consoleFull - Jenkins for Apache Cordova - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
