I would like my build script to act properly for release and development environments.

For this I would like to define a property in ant, call it (e.g.) `fileTargetName`

`fileTargetName` will get it&#39;s value from the environment variable `RELEASE_VER` if it&#39;s available, if it is not available it will get the default value of **dev**

Help with ant `&lt;condition&gt;&lt;value&gt;&lt;/condition&gt;` &amp; `&lt;property&gt;` to get it working is appreciated.

define ant property from environment with default value

Shutting off *my own* app&#39;s LogCat output before releasing an app to the market is straightforward. I also know how to selectively filter LogCat message by tag and/or id for my own debug convenience.

But now I am interested in something that may be much more difficult (perhaps impossible?): Disable all LogCat output, including &amp; especially those coming from 3rd-party services like TtsService, GoogleLoginService, etc.

Is this possible?

To further clarify: I am *not* interested in filtering out messages for myself. I am rather interested in disabling 3rd-party messages for whoever downloads my app from the Android Market. Is this possible?


Disable LogCat Output COMPLETELY in release Android app?

I have an update to my app that has been reviewed and is **Pending Developer Release**.

I have found a bug in this version and would actually like to reject this binary and keep my existing binary.

Once I fix the bug, I would like to re-upload a new binary. Is this possible?

Rejecting an app that is Pending Developer Release

When I use Application Loader, I get to the point where it asks me to &quot;Choose...&quot; the file to be uploaded.

If I understand correctly, it supposes to be the appName.app file I see under &quot;Products&quot; on my app bundle (I right click it and select &quot;Show in Finder&quot; to get to the specific file in library; then I&#39;m supposed to ZIP it and the ZIP file is what I will choose in Application Loader). First, am I correct with this assumption?

if yes...

What should I define different in XCode than the way I used to build the application for testing (on simulator and on my personal iPhone)?

Should I change the **Info---&gt;Command-line build use** from **Debug** to **Release**?

How should I define the **Build Settings---&gt;Code Signing** section (in which field should I select the &quot;**iPhone Developer**&quot; option and in which should it be &quot;**iPhone Distribution**&quot;)?

Are there any other important Info/Build Settings/p.list/etc... fields I should relate to?

any help will be appreciated...

How to Create the Upload File for Application Loader?

 - What is it exactly?
 - For what is it used?  
 - How widespread is the usage?  
 - How is it usually used?  



What exactly is a Release in GitHub?

I&#39;m trying to upload a release to Fabric &amp; I&#39;m getting errors as follows. I&#39;m using the Xcode 6.3 (recently updated).

 - Xcode: 6.3 
 - Fabric: 1.1.3 
 - OSX: 10.10.3

![An Error from Fabric tool][1]

1. What should I do to resolve above error &amp; continue uploading the release via fabric desktop tool?

2. Is there any other way to upload binary to fabric?

  [1]: https://i.stack.imgur.com/orouk.png

Fabric release Xcode 6.3 codesign xcode-select

How do I get my SHA1 Keys for debug and release using android studio on a mac?
(These are required for Google API Keys)

SHA1 Key for DEBUG &amp; RELEASE ANDROID STUDIO MAC , How to generate SHA1 Release Keys in Mac?

I got this warning message:

&gt; This App Bundle contains Java/Kotlin code, which might be obfuscated. We recommend you upload a deobfuscation file to make your crashes and ANRs easier to analyze and debug

what does it mean? what is the shortest solution for this?

Android version release warning message: This App Bundle contains Java/Kotlin code, which might be obfuscated

I am making an app that processes sensitive credit card data.

If my code is running in debug mode I want to log this data to the console and make some file dumps.   

However on the final appstore version (ie when it is running in release mode) it is essential all of this is disabled (security hazard)!

I will try to answer my question as best I can;  so the question becomes *&#39;Is this solution path the right or best way to do it?&#39;*
  
    // add `IS_DEBUG=1` to your debug build preprocessor settings  
  
    #if( IS_DEBUG )  
    #define MYLog(args...) NSLog(args)  
    #else  
    #define MYLog(args...)  
    #endif  



How to determine whether code is running in DEBUG / RELEASE build?

I have published an application on the play store with flutter, now I want to upload a new version of the application. I am trying to change the version code with: 

&gt; flutter build apk --build-name=1.0.2 --build-number=3 

or changing the local.properties like this

     flutter.versionName=2.0.0
     flutter.versionCode=2
     flutter.buildMode=release

but every time I get an error on the play store

&gt; You must use a different version code for your APK or your Android App Bundle because code 1 is already assigned to another APK or Android App Bundle.

 

Flutter: upgrade the version code for play store

Using [GitHub&#39;s Release feature](https://github.com/blog/1547-release-your-software), it is possible to provide a link to download a specific version of the published software. However, every time a release is made, the gh-page also needs to be updated.

Is there a way to get a link to a specific file of whatever the latest version of a software is?

e.g., this would be a static link:

`https://github.com/USER/PROJECT/releases/download/v0.0.0/package.zip`

What I&#39;d like is something like:

`https://github.com/USER/PROJECT/releases/download/latest/package.zip`

&gt; NOTE: The difference between this question and
&gt; https://stackoverflow.com/questions/21439239/github-latest-release is
&gt; that this question specifically asks for getting access to the file,
&gt; not the GitHub latest release page

Is there a link to GitHub for downloading a file in the latest release of a repository?

Android gradle produces apk in two binaries: unaligned and aligned.

The [document][1] said...

&gt; Once you have signed the APK with your private key, run zipalign on the file. This tool ensures that all uncompressed data starts with a particular byte alignment, relative to the start of the file. Ensuring alignment at 4-byte boundaries provides a performance optimization when installed on a device. When aligned, the Android system is able to read files with mmap(), even if they contain binary data with alignment restrictions, rather than copying all of the data from the package. The benefit is a reduction in the amount of RAM consumed by the running application.

Seems like aligned apk is strongly recommended to distribute. For me, I only use *aligned* apk as a result product and ignore *unaligned* apk. 
  
Does unaligned apk have any special usage during development?

  [1]: http://developer.android.com/tools/publishing/app-signing.html

why unaligned apk is needed?

I&#39;ve encountered the following paragraph:

&gt; “Debug vs. Release setting in the IDE when you compile your code in Visual Studio makes almost no difference to performance… the generated code is almost the same. The C# compiler doesn’t really do any optimization. The C# compiler just spits out IL… and at the runtime it’s the JITer that does all the optimization. The JITer does have a Debug/Release mode and that makes a huge difference to performance. But that doesn’t key off whether you run the Debug or Release configuration of your project, that keys off whether a debugger is attached.”

The source is [here][1] and the podcast is [here][2].

Can someone direct me to a Microsoft article that can actually prove this?

Googling &quot;*C# debug vs release performance*&quot; mostly returns results saying &quot;*Debug has a lot of performance hit*&quot;, &quot;*release is optimized*&quot;, and &quot;*don&#39;t deploy debug to production*&quot;.

  [1]: http://andrewmyhre.wordpress.com/2008/05/13/c-debugrelease-and-performance/
  [2]: http://go2.wordpress.com/?id=725X1342&amp;site=andrewmyhre.wordpress.com&amp;url=http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyId%3DB11AD912-4158-44CC-A771-A5E044F7E3BB%26displaylang%3Den

Debug vs. Release performance

Recently I started to get this message randomly:

&gt; Metadata file &#39;...\Release\project.dll&#39; could not be found in Visual Studio

I have a solution with several projects in it. The current build mode is Debug and all projects&#39; configurations are set to Debug. But when I try to run the main project - sometimes it gives me a few errors, all of which are &quot;Metadata file &#39;...\Release\projectX.dll&#39; could not be found&quot; - and, look, it says about RELEASE folder, though current mode is Debug. Why? I tried to search for reference to &quot;Release\projectX.dll&quot; inside all solution files, and I found one in ResolveAssemblyReference.cache file.

I made a good search over the Internet and found a few people with a similar problem, but there was no solution, or at least no working solution.

I tried to delete references to those projects and read them, but in some time I start getting these errors again.

It seems like a bug. Why does it search for referenced projects in Release folders when I always use Debug mode?

**PS.** For those who met this problem: I couldn&#39;t solve it in an easy way. It disappeared only after I reinstalled Windows :(


Error &quot;Metadata file &#39;...\Release\project.dll&#39; could not be found in Visual Studio&quot;

I want the commandline for building a particular project of a solution using msbuild like we do with devenv.com.In devenv.com we can specify a project of a solution using following commandline 

    devenv.com /Build Release|x86 test.sln /project &quot;testproject&quot;

Using the above commandline i can build the testproject in the test.sln using devenv.com.What is the commandline for msbuild for the same solution.

Thanks

specify project file of a solution using msbuild

I am able to build a solution using MSBuild.exe, but my issue is I can only manage to get it to build in DEBUG mode. I need to build my solution in Release mode using MSBUILD.

Here is what I&#39;ve tried

    Process msbuild = Process.Start(&quot;C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\MsBuild.exe&quot;, solutionfilepath + &quot; /P:Config=Release&quot;);

and

    Process msbuild = Process.Start(&quot;C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\MsBuild.exe&quot;, solutionfilepath + &quot; /P:Configuration=Release&quot;);

Building C# Solution in Release mode using MSBuild.exe

I&#39;d like to publicate my app to GooglePlay but first i would like to do a last testing with the signed apk to ensure that all of the used API keys are working correctly with the release version (GMaps, Facebook, etc)

So i just **made a signed version of my app with our release key** and when i try to install the app to the device **i got an error:**

 [![enter image description here][1]][1]


I have tried to copy the apk to the device and **install it with an apk installer app.**

Strange thing is when i do the same process **with debug signing key, all is well, I can install and run the app.**

Here are the **steps of the procedure:**

I select the **release key**, type password.

[![Here are the steps of the procedure:][2]][2]

I do **select release build type** instead of debugging

[![I do select release build type instead of debugging][3]][3]


Just in case **i also defined in the gradle file the signing keys** but I must admit i dont know is it necessary.

[![Just in case i also defined in the gradle file the signing keys but I must admit i dont know is it necessary.][4]][4]


I tried like 7 seven times now so i assume this problem is **not just a 
mistyped password**, also **I can make this work with the standard debug android signing key.**


Please help if you can.




  [1]: http://i.stack.imgur.com/ck3uM.png
  [2]: http://i.stack.imgur.com/bWk81.png
  [3]: http://i.stack.imgur.com/joqXA.png
  [4]: http://i.stack.imgur.com/DZ6uM.png

Cannot install signed apk to device manually, got error &quot;App not installed&quot;

I would like to have my Gradle build to create a release signed apk file using Gradle.

I&#39;m not sure if the code is correct or if I&#39;m missing a parameter when doing `gradle build`?

This is some of the code in my gradle file:

```groovy
android {
    ...
    signingConfigs {
        release {
            storeFile file(&quot;release.keystore&quot;)
            storePassword &quot;******&quot;
            keyAlias &quot;******&quot;
            keyPassword &quot;******&quot;
        }
    }
}
```

The Gradle build finishes *SUCCESSFUL*, and in my `build/apk` folder I only see the `...-release-unsigned.apk` and `...-debug-unaligned.apk` files. 

Any suggestions on how to solve this?


How to create a release signed apk file using Gradle?

What is the difference between a **Snapshot** Repository and **Release** Repository?

This is with reference to setting up Repositories (like Artifactory, Nexus etc)

Maven Snapshot Repository vs Release Repository

I&#39;m using SVN, Maven 3.0.3 on the latest version of Jenkins and the Maven Release plugin.  I&#39;m trying to use the Maven release plugin (through Jenkins) do a dry run and so am executing the options …

	Executing Maven:  -B -f /scratch/jenkins/workspace/myproject/myproject/pom.xml -DdevelopmentVersion=53.0.0-SNAPSHOT -DreleaseVersion=52.0.0 -Dusername=***** -Dpassword=********* -DskipTests -P prod -Dresume=false -DdryRun=true release:prepare

But the dry run is dying with the error below …

	[JENKINS] Archiving /scratch/jenkins/workspace/myproject/myproject/pom.xml to /home/evotext/hudson_home/jobs/myproject/modules/org.mainco.subco$myproject/builds/2013-11-18_16-09-14/archive/org.mainco.subco/myproject/52.0.0/myproject-52.0.0.pom
	Waiting for Jenkins to finish collecting data
	mavenExecutionResult exceptions not empty
	message : Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on project myproject: You don&#39;t have a SNAPSHOT project in the reactor projects list.
	cause : You don&#39;t have a SNAPSHOT project in the reactor projects list.
		Stack trace : 
	org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 	org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on project myproject: You don&#39;t have a SNAPSHOT project in the reactor projects list.
		at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
		at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
		at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
		at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
		at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
		at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
		at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
		at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
		at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
		at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:117)
		at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
		at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
		at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
		at java.lang.reflect.Method.invoke(Method.java:606)
		at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
		at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
		at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:178)
		at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
		at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
		at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
		at java.lang.reflect.Method.invoke(Method.java:606)
		at hudson.maven.Maven3Builder.call(Maven3Builder.java:129)
		at hudson.maven.Maven3Builder.call(Maven3Builder.java:67)
		at hudson.remoting.UserRequest.perform(UserRequest.java:118)
		at hudson.remoting.UserRequest.perform(UserRequest.java:48)
		at hudson.remoting.Request$2.run(Request.java:326)
		at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
		at java.util.concurrent.FutureTask.run(FutureTask.java:262)
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
		at java.lang.Thread.run(Thread.java:744)
	Caused by: org.apache.maven.plugin.MojoFailureException: You don&#39;t have a SNAPSHOT project in the reactor projects list.
		at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:219)
		at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181)
		at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
		at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
		... 30 more
	Caused by: org.apache.maven.shared.release.ReleaseFailureException: You don&#39;t have a SNAPSHOT project in the reactor projects list.
		at org.apache.maven.shared.release.phase.CheckPomPhase.execute(CheckPomPhase.java:111)
		at org.apache.maven.shared.release.phase.CheckPomPhase.simulate(CheckPomPhase.java:123)
		at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:199)
		at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140)
		at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103)
		at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211)
		... 33 more


My SVN checkout method is set to &quot;Always checkout a fresh copy&quot; and I have a snapshot version in question in my snapshot repository, but not in my release repository.  Is there a way I can get the &quot;reactor projects list&quot; to look at my snapshot repo?

&lt;b&gt;Edit:&lt;/b&gt; I&#39;m including the snippet of my pom where the project gets its version -- it inherits it from a parent

        &lt;parent&gt;
                &lt;artifactId&gt;subco&lt;/artifactId&gt;
                &lt;groupId&gt;org.mainco.subco&lt;/groupId&gt;
                &lt;version&gt;52.0.0&lt;/version&gt;
        &lt;/parent&gt;


&quot;You don&#39;t have a SNAPSHOT project in the reactor projects list.&quot; when using Jenkins Maven release plugin

I get the following error output while running the Maven release plugin prepare step i.e. `mvn release:prepare --batch-mode -DreleaseVersion=1.1.2 -DdevelopmentVersion=1.2.0-SNAPSHOT -Dtag=v1.1.2 -X` from an Atlassian Bamboo plan. However doing the same in the command line works fine. The full error stack is below.

Any ideas how can this be solved?

	[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare (default-cli) on project hpcmom: An error is occurred in the checkin process: Exception while executing SCM command. Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref -&gt; [Help 1]
		org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare (default-cli) on project hpcmom: An error is occurred in the checkin process: Exception while executing SCM command.
		at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
		at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
		at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
		at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
		at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
		at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
		at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
		at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
		at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
		at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
		at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
		at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
		at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
		at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
		at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
		at java.lang.reflect.Method.invoke(Method.java:606)
		at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
		at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
		at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
		at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
	Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred in the checkin process: Exception while executing SCM command.
		at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:281)
		at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:232)
		at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
		at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
		... 19 more
	Caused by: org.apache.maven.shared.release.ReleaseExecutionException: An error is occurred in the checkin process: Exception while executing SCM command.
		at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:160)
		at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.performCheckins(AbstractScmCommitPhase.java:145)
		at org.apache.maven.shared.release.phase.ScmCommitPreparationPhase.runLogic(ScmCommitPreparationPhase.java:76)
		at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.execute(AbstractScmCommitPhase.java:78)
		at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:234)
		at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:169)
		at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:146)
		at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:107)
		at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:277)
		... 22 more
	Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command.
		at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63)
		at org.apache.maven.scm.provider.git.AbstractGitScmProvider.executeCommand(AbstractGitScmProvider.java:291)
		at org.apache.maven.scm.provider.git.AbstractGitScmProvider.checkin(AbstractGitScmProvider.java:217)
		at org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:410)
		at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:156)
		... 30 more
	Caused by: org.apache.maven.scm.ScmException: Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

		at org.apache.maven.scm.provider.git.gitexe.command.branch.GitBranchCommand.getCurrentBranch(GitBranchCommand.java:147)
		at org.apache.maven.scm.provider.git.gitexe.command.checkin.GitCheckInCommand.createPushCommandLine(GitCheckInCommand.java:192)
		at org.apache.maven.scm.provider.git.gitexe.command.checkin.GitCheckInCommand.executeCheckInCommand(GitCheckInCommand.java:132)
		at org.apache.maven.scm.command.checkin.AbstractCheckInCommand.executeCommand(AbstractCheckInCommand.java:54)
		at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
		... 34 more
	[ERROR] 
	[ERROR] 
	[ERROR] For more information about the errors and possible solutions, please read the following articles:
	[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
	simple	02-Dec-2013 17:18:09	Failing task since return code of [/opt/dev/apache-maven/3.0.5//bin/mvn -Djava.io.tmpdir=/opt/atlassian/bamboo/5.2.1/temp/HPCMOM-RELEASE-JOB1 release:prepare --batch-mode -DignoreSnapshots=false -DreleaseVersion=1.1.2 -DdevelopmentVersion=1.2.0-SNAPSHOT -Dtag=v1.1.2 -X] was 1 while expected 0

**UPDATE:**

Doing `git ls-remote .` on a local workspace clone produces:

    azg@olympus:~/code/hpcmom$ git ls-remote .
    7894eea08a0afecb99515d1339623be63a7539d4	HEAD
    7894eea08a0afecb99515d1339623be63a7539d4	refs/heads/master
    7894eea08a0afecb99515d1339623be63a7539d4	refs/remotes/origin/HEAD
    7894eea08a0afecb99515d1339623be63a7539d4	refs/remotes/origin/master
    6a7095b86cccdfd4b28e4dea633d0930809ae9ac	refs/tags/v1.0
    1a53462b1ecf0abfea8245016304cda9c78b420d	refs/tags/v1.0^{}
    5113a7cbcf35c47b680a9c36e15e5fa01ef1d2e6	refs/tags/v1.1
    79a3073ecabe65d3c8051520f8007d9e49a65a06	refs/tags/v1.1^{}
    a00249209597ea1214d80ee38f228c40db7022c2	refs/tags/v1.1.0
    e892bce8d25d87368ab557fee0d30810bef7e31e	refs/tags/v1.1.0^{}
    b491a312c39088533cb069e4ab1ae8a00d1f6bfe	refs/tags/v1.1.2
    a3f7618dada7ed60d8190426152ffd90e0e40a86	refs/tags/v1.1.2^{}

Doing `git ls-remote .` on the Bamboo clone produces:

    azg@olympus:/var/atlassian/application-data/bamboo/xml-data/build-dir/HPCMOM-RELEASE-JOB1$ git ls-remote .
    2422ce066ac35dae3c54f1435ef8dae5008a9a14	HEAD
    57c08d581c0fd9e788049733fbdc9c22b9a6ae00	refs/heads/master
    57c08d581c0fd9e788049733fbdc9c22b9a6ae00	refs/remotes/origin/HEAD
    57c08d581c0fd9e788049733fbdc9c22b9a6ae00	refs/remotes/origin/master
    7539f9700d78a1b766fca7ed9f409914f1ea9d08	refs/tags/vnull
    6bfa8c3fdb1f8f56a385035f01b1b77b6e88da8b	refs/tags/vnull^{}

and this is very weird why is the local development clone output so different from the Bamboo one?

&quot;Git fatal: ref HEAD is not a symbolic ref&quot; while using maven release plugin

&gt; **Possible Duplicate:**  
&gt; [How to tell if a .NET application was compiled in DEBUG or RELEASE mode?](https://stackoverflow.com/questions/194616/how-to-tell-if-a-net-application-was-compiled-in-debug-or-release-mode)  

&lt;!-- End of automatically inserted text --&gt;

I&#39;m sure this has been asked before, but google and SO search failed me.

How can I identify if a DLL is a release build or debug build?


How to identify if the DLL is Debug or Release build (in .NET)

In Solution properties, I have Configuration set to &quot;release&quot; for my one and only project. 

At the beginning of the main routine, I have this code, and it is showing &quot;Mode=Debug&quot;. 
I also have these two lines at the very top: 

    #define DEBUG 
    #define RELEASE

  
Am I testing the right variable? 

    #if (DEBUG)
                Console.WriteLine(&quot;Mode=Debug&quot;); 
    #elif (RELEASE)
                Console.WriteLine(&quot;Mode=Release&quot;); 
    #endif


My goal is to set different defaults for variables based on debug vs release mode. 

C# if/then directives for debug vs release

Currently, I package the release builds with Nuget for the official builds to nuget.org, but I package the debug builds with Nuget for the symbol source pushes to symbolsource.org.

EDIT: (Jon Skeet, with some bias from Noda Time development)

NuGet now supports pushing to both NuGet gallery *and* symbolsource.org (or similar servers), [as documented][1]. Unfortunately, there are two contradictory requirements here:

- When just *using* a library without any need for debugging, you really want a release build. That&#39;s what release builds are for, after all.
- When debugging into a library for diagnostic purposes, you really want a debug build with all the appropriate optimizations disabled. That&#39;s what debug builds are for, after all.

That would be fine, but NuGet doesn&#39;t (as far as I can tell) allow both the release and debug builds to be published in a useful way, in the same package.

So, the choices are:

- Distribute the debug builds to everyone (as shown in the example in the docs) and live with any size and performance hits. 
- Distribute the release builds to everyone and live with a slightly impaired debug experience.
- Go for a really complicated distribution policy, potentially providing separate release and debug packages.

The first two really boil down to the effect of the differences between debug and release builds... although it&#39;s worth noting that there&#39;s also a big difference between wanting to step into the code of a library because you want to check some behaviour, and wanting to debug the code of a library because you believe you&#39;ve found a bug. In the second case, it&#39;s probably better to get the code of the library *as a Visual Studio solution* and debug that way, so I&#39;m not paying too much heed to that situation.

My temptation is to just keep with the release builds, with the expectation that *relatively* few people will need to debug, and the ones who do won&#39;t be impacted *much* by the optimizations in the release build. (The JIT compiler does most of the optimizing anyway.)

So, are there other options we hadn&#39;t considered? Are there other considerations which tip the balance? Is pushing NuGet packages to SymbolSource sufficiently new that &quot;best practice&quot; really hasn&#39;t been established?

  [1]: http://docs.nuget.org/docs/creating-packages/creating-and-publishing-a-symbol-package

Best practices with Nuget: Debug or Release?

I have created android build of my Flutter application.

Then I created an internal testing release. It is showing a warning 


&gt; This App Bundle contains native code, and you&#39;ve not uploaded debug
&gt; symbols. We recommend you upload a symbol file to make your crashes
&gt; and ANRs easier to analyze and debug. 

Basically what I had to do is add following to build.gradle file according to the link they show.


    android.buildTypes.release.ndk.debugSymbolLevel = { SYMBOL_TABLE | FULL }

I assume it is android/app/build.gradle they are talking about.


Not sure exactly where in that file I have to add this line.

Can someone point out where to add this line?

How to add debug symbols to build.gradle

Why is it that when I build an application, Xcode creates a debug build? I want to create a release build. How can I do this?

How do I create a release build in Xcode?

I want to build android app and start signing it. 
For that I need to have Release version of apk. Google documentation suggests only Eclipse and ant ways to have release builds: http://developer.android.com/tools/publishing/app-signing.html#releasecompile

However I cannot find how to force gradle build release version of apk. `build.gradle` does not give any hints either. `gradlew tasks` suggests, that there is no install Release configuration, but uninstall release exists:

    Install tasks
    -------------
    installDebug - Installs the Debug build
    installTest - Installs the Test build for the Debug build
    uninstallAll - Uninstall all applications.
    uninstallDebug - Uninstalls the Debug build
    uninstallRelease - Uninstalls the Release build
    uninstallTest - Uninstalls the Test build for the Debug build

My `build.gradle`:

    buildscript {
        repositories {
            mavenCentral()
        }
        dependencies {
            classpath &#39;com.android.tools.build:gradle:0.5.+&#39;
        }
    }
    apply plugin: &#39;android&#39;
    
    repositories {
        mavenCentral()
    }
    
    dependencies {
        compile &#39;com.android.support:support-v4:13.0.+&#39;
        compile files(&#39;libs/android-support-v4.jar&#39;)
        compile project(&quot;:libraries:ActionBarSherlock&quot;)
        compile project(&quot;:libraries:CollabsibleSearchMenu&quot;)
    }
    
    android {
        compileSdkVersion 18
        buildToolsVersion &quot;18.0.1&quot;
    
        defaultConfig {
            minSdkVersion 8
            targetSdkVersion 16
        }
    }

What I am missing?

How to set up gradle and android studio to do release build?

I see how Xcode 4 splits the info on your targets nicely in one view, but how does one build and run these different builds? All I see are the options to build and to run, and these options to build for running, testing, and profiling. It&#39;s not clear to me how these map to the build configurations, though.

Running a release build with Xcode 4

I&#39;m trying to release a Jenkins plugin ([stashNotifier][1]) with Maven and face a problem with the release plugin. 

    mvn clean release:prepare

runs to completion without errors but fails to commit the changed pom.xml in my local git repository. Even though it does tag the HEAD of the branch on which I&#39;m trying to release version 1.0.2. This is what my local branch looks like before preparing the release

    * df60768 (HEAD, origin/develop, develop) upgraded parent pom to version 1.498
    * 792766a added distribution management section to pom.xml and amended readme.md 

and this is what it looks like after

    * df60768 (HEAD, tag: stashNotifier-1.0.2, origin/develop, develop) upgraded parent pom to version 1.498
    * 792766a added distribution management section to pom.xml and amended readme.md 

Unfortunately, the pom.xml already contains the next development version, which in turn causes a subsequent release:perform to release that snapshot version.

From the command output of maven, it almost looks like it&#39;s omitting the git commit command:

    [INFO] Checking in modified POMs...
    [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier &amp;&amp; git add -- pom.xml
    [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
    [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier &amp;&amp; git status
    [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
    [INFO] Tagging release with the label stashNotifier-1.0.2...
    [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier &amp;&amp; git tag -F /var/folders/dr/xxbtyycs1z9dl2_snlj87zrh0000gn/T/maven-scm-678409272.commit stashNotifier-1.0.2
    [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
    [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier &amp;&amp; git push git@github.com:jenkinsci/stashnotifier-plugin.git stashNotifier-1.0.2
    [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
    [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier &amp;&amp; git ls-files
    [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
    [INFO] Transforming &#39;Stash Notifier&#39;...
    [INFO] Not removing release POMs
    [INFO] Checking in modified POMs...
    [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier &amp;&amp; git add -- pom.xml
    [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
    [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier &amp;&amp; git status
    [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
    [INFO] Release preparation complete.

I&#39;m running maven 3.0.5 (without --dry-run or -DpushChanges=false). Here are the relevant (I think) parts of my effective pom:

    [...]

    &lt;scm&gt;
       &lt;connection&gt;scm:git:git://github.com/jenkinsci/stashnotifier-plugin.git&lt;/connection&gt;
       &lt;developerConnection&gt;scm:git:git@github.com:jenkinsci/stashnotifier-plugin.git&lt;/developerConnection&gt;
       &lt;url&gt;https://github.com/jenkinsci/stashnotifier-plugin&lt;/url&gt;
    &lt;/scm&gt;

    [...]

    &lt;distributionManagement&gt;
       &lt;repository&gt;
          &lt;id&gt;maven.jenkins-ci.org&lt;/id&gt;
          &lt;url&gt;http://maven.jenkins-ci.org:8081/content/repositories/releases/&lt;/url&gt;
       &lt;/repository&gt;
       &lt;snapshotRepository&gt;
          &lt;id&gt;maven.jenkins-ci.org&lt;/id&gt;
          &lt;url&gt;http://maven.jenkins-ci.org:8081/content/repositories/snapshots&lt;/url&gt;
       &lt;/snapshotRepository&gt;
       &lt;site&gt;
         &lt;id&gt;github-pages&lt;/id&gt;
         &lt;url&gt;gitsite:git@github.com/jenkinsci/maven-site.git:plugin-parent/stashNotifier&lt;/url&gt;
       &lt;/site&gt;
    &lt;/distributionManagement&gt;

    [...]

    &lt;properties&gt;
       [...]
       &lt;maven-release-plugin.version&gt;2.2.2&lt;/maven-release-plugin.version&gt;
       [...]
    &lt;/properties&gt;

    [...]

    &lt;build&gt;
       [...]
       &lt;pluginManagement&gt;
          &lt;plugins&gt;
             [...]
             &lt;plugin&gt;
                &lt;artifactId&gt;maven-release-plugin&lt;/artifactId&gt;
                &lt;version&gt;2.2.2&lt;/version&gt;
             &lt;/plugin&gt;
             [...]
       &lt;/pluginManagement&gt;

       [...]

       &lt;plugins&gt;
          [...]
          &lt;plugin&gt;
             &lt;artifactId&gt;maven-release-plugin&lt;/artifactId&gt;
             &lt;version&gt;2.2.2&lt;/version&gt;
             &lt;configuration&gt;
                &lt;goals&gt;deploy&lt;/goals&gt;
             &lt;/configuration&gt;
          &lt;/plugin&gt;
          [...]
       &lt;/plugins&gt;
    &lt;/build&gt;

What am I doing wrong? Thanks in advance for your insights!


  [1]: https://github.com/jenkinsci/stashnotifier-plugin

mvn release:prepare not committing changes to pom.xml

In debug mode, everything looks good. I get answers and data lists from my API. But after creating *app-release.apk* and installing it on my phone, there isn&#39;t an Internet connection any more.

Here is my code:

    ScopedModelDescendant&lt;ReportPosViewModel&gt;(
      builder: (context, child, model) {
        return FutureBuilder&lt;List&lt;Invoice&gt;&gt;(
          future: model.invoices,
          builder: (_,
            AsyncSnapshot&lt;List&lt;Invoice&gt;&gt; snapshot) {
              switch (snapshot.connectionState) {
                case ConnectionState.none:
                case ConnectionState.active:
                case ConnectionState.waiting:
                  return Center(
                    child:
                      const CircularProgressIndicator());
                case ConnectionState.done:
                  if (snapshot.hasData) {
                    // Something todo
                  }
                  else if (snapshot.hasError) {
                    return NoInternetConnection(
                      action: () async {
                        await model.setInvoice();
                        await getData();
                      },
                    );
                  }
              }
          },
        );
      },
    ),







Why can&#39;t a Flutter application connect to the Internet when installing &quot;app-release.apk&quot;? But it works normally in debug mode

### Background

I have an ASP.NET MVC application project, along with various other projects within a Visual Studio solution. The different projects use various versions of the NPoco library as follows:

* The MVC project includes a version of NPoco through NuGet.
* Some other projects include a (probably different) version of NPoco through a reference to a DLL (not the DLL provided through NuGet).
* One of the projects is the source code of a version of NPoco with some alterations made.

I&#39;m using Visual Studio 2015 Update 3 14.0.25422.01.

### Error
For some reason, when I launch this application in the debugger using the normal Start Debugging command in Visual Studio, it launches, but it also produces the following warning:

[![You are debugging a Release build of NPoco.dll. Using Just My Code with Release builds using compiler optimizations results in a degraded debugging experience (e.g. breakpoints will not be hit).][1]][1]

If I press **Continue Debugging**, everything seems to still work as usual, including breakpoints.

This problem only started happening recently.

### Question

1. Anyone know what caused the above error?
2. Do I have something misconfigured?


  [1]: http://i.stack.imgur.com/1r09x.png

Error: You are debugging a Release build of X.dll

In C, we can build a debug version or a release version of the binary files (the object files and the executable). How can we do this in Go? 

How to build a release version binary in Go?

Our company is currently using a simple trunk/release/hotfixes branching model and would like advice on what branching models work best for your company or development process.

 1. **Workflows / branching models**

 Below are the three main descriptions of this I have seen, but they are partially contradicting each other or don&#39;t go far enough to sort out the subsequent issues we&#39;ve run into (as described below). Thus our team so far defaults to not so great solutions. Are you doing something better? 
 
  - [gitworkflows(7) Manual Page][2] 
  - [(nvie) A successful Git branching model][3]
  - [(reinh) A Git Workflow for Agile Teams][4]

 1. **Merging vs rebasing (tangled vs sequential history)** 

 Should one `pull --rebase` or wait with merging back to the mainline until your task is finished? Personally I lean towards merging since this preserves a visual illustration of on which base a task was started and finished, and I even prefer `merge --no-ff` for this purpose. It has other drawbacks however. Also many haven&#39;t realized the useful property of merging - that it isn&#39;t [commutative][5] (merging a topic branch into master does not mean merging master into the topic branch).

 1. **I am looking for a natural workflow** 

 Sometimes mistakes happen because our procedures don&#39;t capture a specific situation with simple rules. For example a fix needed for earlier releases should of course be based sufficiently downstream to be possible to merge upstream into all branches necessary (is the usage of these terms clear enough?). However it happens that a fix makes it into the master before the developer realizes it should have been placed further downstream, and if that is already pushed (even worse, merged or something based on it) then the option remaining is cherry-picking, with its associated perils. What simple rules like such do you use? *Also in this is included the awkwardness of one topic branch necessarily excluding other topic branches (assuming they are branched from a common baseline). Developers don&#39;t want to finish a feature to start another one feeling like the code they just wrote is not there anymore*

 1. **How to avoid creating merge conflicts (due to cherry-pick)?** 

 What seems like a sure way to create a merge conflict is to cherry-pick between branches, they can never be merged again? Would applying the same commit in revert (how to do this?) in either branch possibly solve this situation? This is one reason I do not dare to push for a largely merge-based workflow.

 1. **How to decompose into topical branches?** 

 We realize that it would be awesome to assemble a finished integration from topic branches, but often work by our developers is not clearly defined (sometimes as simple as &quot;poking around&quot;) and if some code has already gone into a &quot;misc&quot; topic, it can not be taken out of there again, according to the question above? How do you work with defining/approving/graduating/releasing your topic branches?

 1. **Proper procedures like code review and graduating** would of course be lovely. 
 
 But we simply cannot keep things untangled enough to manage this - any suggestions?
integration branches, illustrations?

Below is a list of related questions:

 - [What are some good strategies to allow deployed applications to be hotfixable?][6]
 - [Workflow description for Git usage for in-house development][7]
 - [Git workflow for corporate Linux kernel development][8]
 - [How do you maintain development code and production code?][9] (thanks for [this][10] PDF!)
 - [git releases management][11]
 - [Git Cherry-pick vs Merge Workflow][12]
 - [How to cherry-pick multiple commits][13]
 - [How do you merge selective files with git-merge?][14]
 - [How to cherry pick a range of commits and merge into another branch][15]
 - [ReinH Git Workflow][16]
 - [git workflow for making modifications you’ll never push back to origin][17]
 - [Cherry-pick a merge][18]
 - [Proper Git workflow for combined OS and Private code?][19]
 - [Maintaining Project with Git][20]
 - [Why cant Git merge file changes with a modified parent/master.][21]
 - [Git branching / rebasing good practices][22]
 - [When will &quot;git pull --rebase&quot; get me in to trouble?][23]
 - [How are DVCS used in large teams?][29]

Also check out what Plastic SCM writes on [task driven development][26], and if Plastic is not your choice, study [nvie&#39;s branching model][27] and his [supporting scripts][28].



  [2]: http://www.kernel.org/pub/software/scm/git/docs/gitworkflows.html
  [3]: http://nvie.com/git-model
  [4]: http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html
  [5]: http://en.wikipedia.org/wiki/Commutativity
  [6]: https://stackoverflow.com/questions/143814/what-are-some-good-strategies-to-allow-deployed-applications-to-be-hotfixable
  [7]: https://stackoverflow.com/questions/1049917/workflow-description-for-git-usage-for-in-house-development/1050628
  [8]: https://stackoverflow.com/questions/1856241/git-workflow-for-corporate-linux-kernel-development
  [9]: https://stackoverflow.com/questions/216212
  [10]: https://stackoverflow.com/questions/216212/how-do-you-maintain-development-code-and-production-code/216219#216219
  [11]: https://stackoverflow.com/questions/1042400/git-releases-management
  [12]: https://stackoverflow.com/questions/1241720/git-cherry-pick-vs-merge-workflow
  [13]: https://stackoverflow.com/questions/1670970/how-to-cherry-pick-multiple-commits
  [14]: https://stackoverflow.com/questions/449541/how-do-you-merge-selective-files-with-git-merge
  [15]: https://stackoverflow.com/questions/1994463/how-to-cherry-pick-a-range-of-commits-and-merge-into-another-branch
  [16]: https://stackoverflow.com/questions/855266/reinh-git-workflow
  [17]: https://stackoverflow.com/questions/582015/git-workflow-for-making-modifications-youll-never-push-back-to-origin
  [18]:  https://stackoverflow.com/questions/232771/cherry-pick-a-merge
  [19]: https://stackoverflow.com/questions/2195826/proper-git-workflow-for-combined-os-and-private-code
  [20]: https://stackoverflow.com/questions/2587721/maintaining-project-with-git
  [21]: https://stackoverflow.com/questions/2588824/why-cant-git-merge-file-changes-with-a-modified-parent-master
  [22]: https://stackoverflow.com/questions/2601967/git-branching-rebasing-good-practices
  [23]: https://stackoverflow.com/questions/2590260/when-will-git-pull-rebase-get-me-in-to-trouble
  [24]: http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg39091.html
  [26]: http://www.plasticscm.com/features/task-driven-development.aspx
  [27]: http://nvie.com/posts/a-successful-git-branching-model/
  [28]: https://github.com/nvie/gitflow
  [29]: https://stackoverflow.com/questions/787638/how-are-dvcs-used-in-large-teams

What Git branching models work for you?

&gt; **Possible Duplicate:**  
&gt; [Why use Autorelease pool?](https://stackoverflow.com/questions/6394735/why-use-autorelease-pool)  

&lt;!-- End of automatically inserted text --&gt;

All Objective-C starting page opens with a default `@autoreleasepool{...}` statement under the main function declaration. But what is this statement actually doing? The new Objective-C releases automatically objects and deleting the line changes nothing to the program. Is this command really necessary?

What is autoreleasepool?

&gt; **Possible Duplicate:**  
&gt; [How to find out if a .NET assembly was compiled with the TRACE or DEBUG flag](https://stackoverflow.com/questions/629674)  

&lt;!-- End of automatically inserted text --&gt;

&gt; **Possible Duplicate:**  
&gt; [How to idenfiy if the DLL is Debug or Release build (in .NET)](https://stackoverflow.com/questions/798971/how-to-idenfiy-if-the-dll-is-debug-or-release-build-in-net)  

&lt;!-- End of automatically inserted text --&gt;

What&#39;s the easiest way to programmatically check if the current assembly was compiled in Debug or Release mode?


Programmatically detecting Release/Debug mode (.NET)

I&#39;m starting to get to the point where I want to consider building a
lite version of my iPhone app. I&#39;ve found a few things on the web that talk
about the process a bit, namely:

[http://developer.apple.com/tools/XCode/XCodeprojects.html][1]

[http://www.pacificspirit.com/blog/2009/01/27/building_for_multiple_iphone_targets_in_xcode][2]

What I&#39;m
specifically interested in is simplifying the process of managing
which files are included in the different versions of my app as I
continually modify and enhance my paid for version.


  [1]: http://developer.apple.com/tools/XCode/XCodeprojects.html
  [2]: http://www.pacificspirit.com/blog/2009/01/27/building_for_multiple_iphone_targets_in_xcode

How do I manage building a Lite vs Paid version of an iPhone app?

How do I switch between debug and release in Visual C# 2010 Express?

I have looked in the project properties, but it seems to be missing. What am I missing?


How to switch between debug and release in Visual C# 2010 Express?

i would like to release a snapshot project &#39;foo-1.0-SNAPSHOT&#39; using the maven release plugin. The project depends on a 3rd party module &#39;bar-1.0-SNAPSHOT&#39; which is not released yet.
I use the option &#39;allowTimestampedSnapshots&#39; in my project&#39;s pom.xml to allow timestamped snapshots but i assume that the 3rd party module (bar) is not timestamped unless i build it myself as maven still complains about unresolved SNAPSHOT dependencies.

Is there a way to release the project foo regardless of dependent SNAPSHOT projects and if not how could i add a timestamp to the 3rd party project?


 

how to release a project which depends on a 3rd party SNAPSHOT project in maven

I&#39;ve been developing my first app for work and am having trouble removing an earlier version from the Google Play Console.

My first release was version 2, which I released on the Internal Test track, as much as an experiment to understand the working of things.  I have subsequently release the app up to version 8, always targeting Alpha/Closed Track and had no problems with them.

However my first release, the one in Internal test track, simply refuses to go away.  All the others I have found I can click MANAGE then RELEASE TO BETA then DISCARD (at the bottom) and they go away, but not this one.

Can anyone help me with this please.  I have to say that the websites for releasing to both Android and to Apple do leave much to be desired - a bit of a baptism of fire to get your first app out there, even just to testers.

All Release Solutions on Gang of Coders

Total of 39 Release Solutions