You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Terence M. Bandoian" <te...@tmbsw.com> on 2018/03/12 03:04:01 UTC
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-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Fixed Locations for Build Artifacts?
Posted by "Terence M. Bandoian" <te...@tmbsw.com>.
Ohhh. I think I get it now. My understanding is that the directory
structure expected by Android Studio changes regularly and Cordova has
no choice but to change along with it. However, Visual Studio expects
Android debug APKs to be specifically named and located in order to
start Android debug sessions. This is convenient if you're developing
for Windows and Android because a single IDE can be used for both
platforms and the Cordova project source files are directly accessible
in the IDE.
The after-build script I posted in issue CB-13932
(https://issues.apache.org/jira/browse/CB-13932) resolves the Android
debug APK naming/location problem in Visual Studio but I'm wondering if
there are any other tools with similar build artifact name/location
expectations. If so, Cordova could potentially insulate those tools
from breakages by incorporating something as simple as the above
after-build script into the build processes.
-Terence
On 3/11/2018 11:16 PM, Joe Bowser wrote:
> 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" <te...@tmbsw.com> 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-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Fixed Locations for Build Artifacts?
Posted by "Terence M. Bandoian" <te...@tmbsw.com>.
Ohhh. I think I get it now. My understanding is that the directory
structure expected by Android Studio changes regularly and Cordova has
no choice but to change along with it. However, Visual Studio expects
Android debug APKs to be specifically named and located in order to
start Android debug sessions. This is convenient if you're developing
for Windows and Android because a single IDE can be used for both
platforms and the Cordova project source files are directly accessible
in the IDE.
The after-build script I posted in issue CB-13932
(https://issues.apache.org/jira/browse/CB-13932) resolves the Android
debug APK naming/location problem in Visual Studio but I'm wondering if
there are any other tools with similar build artifact name/location
expectations. If so, Cordova could potentially insulate those tools
from breakages by incorporating something as simple as the above
after-build script into the build processes.
-Terence
On 3/11/2018 11:16 PM, Joe Bowser wrote:
> 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" <te...@tmbsw.com> 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-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Fixed Locations for Build Artifacts?
Posted by Joe Bowser <bo...@gmail.com>.
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" <te...@tmbsw.com> 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-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>