search

Esri / vehicle-commander-java

The Vehicle Commander template demonstrates best practices for building in-vehicle military applications with ArcGIS Runtime. The Vehicle Commander template contains source code for an in-vehicle application.
Apache License 2.0
16 stars 13 forks source link

Update Jenkins buildfile to reflect the latest version of Runtime #34

Closed ACueva closed 9 years ago

ACueva commented 10 years ago

There will not be a 10.2.3 version of Runtime and we'll be moving directly to 10.2.4. Current buildfile references 10.2.3.

Buildfile: C:\Program Files (x86)\Jenkins\workspace\Daily Build - Vehicle Commander\source\VehicleCommander\build.xml [echo] ARCGISRUNTIMESDKJAVA_10_2_3 = C:\Program Files (x86)\ArcGIS SDKs\java10.2.3 [echo] ARCGISRUNTIMESDKJAVA_10_2 = ${env.ARCGISRUNTIMESDKJAVA_10_2}

ACueva commented 10 years ago

@garys-esri has an open issue to migrate Vehicle Commander to 10.2.3.

garysheppardjr commented 10 years ago

There is an ArcGIS Runtime 10.2.3. We could certainly recompile the app with 10.2.3 and release it, but there are no new features in Vehicle Commander as far as I know. Is it worth doing, or should we wait for 10.2.4?

ACueva commented 10 years ago

Good question Gary. Ben? @conklinbd

conklinbd commented 10 years ago

Ok. My mistake I thought they skipped 10.2.3. I think we could wait for 10.2.4 since it will be close and will have new features.

csmoore commented 9 years ago

Looks like this was done using 10.2.3 (in latest updated/PR) so @ACueva just making sure it is OK to close this one?

Going forward, I think @ACueva is just going to create a "v.next" branch whenever he needed to update a build file for the next version for Jenkins. "v.next" is a good generic branch name since we can just keep reusing it as needed.

conklinbd commented 9 years ago

@ACueva is this completed?

ACueva commented 9 years ago

@conklinbd, sorry, yes, it appears @garys-esri has created a 10.4 tag.

@csmoore is simply tagging changes sufficient or should we go with a 10.4 branch?

csmoore commented 9 years ago

If we need to have Jenkins always build with the v.next (not sure if this is 10.2.5 or 10.3 or 10.4 in this case) then we should probably create a "v.next" branch - I'll show you how this works in practice & it will make a bit more sense.

But this is how the SDK sample repos work (ex. goto: https://github.com/Esri/arcgis-runtime-samples-dotnet and switch branch to "v.next") and this seems to work well for them (and their repos are typically more volatile than ours)

ACueva commented 9 years ago

Created v.next branch, tested in Jenkins. All is well.