It was a documentation bug.  (And it has been fixed!)

The `Deprecated` annotation is not really deprecated.

Apparently what happened is that the source code for `Deprecated` contained this in its javadoc comments:

     * @apiNote
     * It is strongly recommended that the reason for deprecating a program element
     * be explained in the documentation, using the {@code @deprecated}
     * javadoc tag. 

Apparently, the `{@code @deprecated}` was interpreted as an `@deprecated` javadoc tag by the [`metalava`][1] tool.  This caused `metalava` to inject the &quot;missing&quot; `@Deprecated` annotations into the &quot;.class&quot; files in the Android JAR file.  Presumably, the injected annotation was then incorporated into the generated javadocs on the website.

Kudos to [Manohar Reddy][2] for finding the [bug][3] in the issue tracker.

You can find the fix that they made [here][4].


------------------------------------

For what it is worth, `java.lang.Deprecated` is a class that originates in the Oracle / OpenJDK Java (i.e. standard Java) class libraries.  Android *wouldn&#39;t / shouldn&#39;t* deliberately deprecate it without a very good reason.  It would create another hurdle to Java &lt;-&gt; Android portability.

  [1]: https://android.googlesource.com/platform/tools/metalava/
  [2]: https://stackoverflow.com/users/6478047/manohar-reddy
  [3]: https://issuetracker.google.com/issues/180705308
  [4]: https://android-review.googlesource.com/c/platform/libcore/+/1601554/1/ojluni/src/main/java/java/lang/Deprecated.java#b59

I have a simple class like this.

    public class Greeting
    {
        public string From { get; set; }
        public string To { get; set; } 
        public string Message { get; set; }
    }

Strangely I get the following warning. 

    Severity	Code	Description	Project	File	Line	Suppression State
    Warning	CS8618	Non-nullable property &#39;From&#39; must contain a non-null value when exiting constructor. 
    Consider declaring the property as nullable.	MxWork.Elsa2Wf.Tuts.BasicActivities	 
    D:\work\MxWork\Elsa2.0WfLearning\MxWork.Elsa2.0Wf.Tuts\src 
    \MxWork.Elsa2Wf.Tuts.BasicActivities\Messages\Greeting.cs	5	Active

I am baffled. These new kind of messages that it throws pulls down my confidence. 
I got them from all the three properties.
And this has suddenly appeared.

Can some one please suggest how this can be mitigated. 


[![visual studio warning message][1]][1]


## Update

These days I have seen using **default!** like so, and its working.

    public class Greeting
    {
        public string From { get; set; } = default!;
        public string To { get; set; } = default!;
        public string Message { get; set; } = default!;
    }

Also you may put a question mark symbol(?) to indicate that the type is nullable, if you feel appropriate as follows.

```cs
public class Greeting
{
    public string? From { get; set; };
    public string? To { get; set; };
    public string? Message { get; set; };
}
```



  [1]: https://i.stack.imgur.com/0GjVJ.png

Non-nullable property must contain a non-null value when exiting constructor. Consider declaring the property as nullable

When you run a `.exe` console application in Windows (such as one written in C++), Windows creates a console window for you.

So in essence, the program doesn&#39;t run on top of anything other than Windows itself.

When you invoke `java Main.class` *inside* the cmd.exe console, is it really its own standalone program? It feels more like `java` is the program running and `Main.class` is just an argument given.
 
All of this is to ask, are all Java programs simply console `java [argument]` programs? Another way to ask, are all Java programs just JRE programs/instances that are reading a particular class file?

Are Java programs just instances of the JRE?

[![Deprecaated][1]][1]
According to [Official Android Documentation][2] Deprecated itself is deprecated in API level S. So what&#39;s the replacement for Deprecated which itself is deprecated?

Edit: Added web archive [link][3] for historical reference. 


  [1]: https://i.stack.imgur.com/U2JFj.png
  [2]: https://developer.android.com/reference/java/lang/Deprecated
  [3]: https://web.archive.org/web/20210218192448/https://developer.android.com/reference/java/lang/Deprecated

Android Deprecated Annotation is deprecated, what&#39;s the replacement?

<p><a href="https://i.stack.imgur.com/U2JFj.png" target="_blank" rel="noopener noreferrer"><img src="https://i.stack.imgur.com/U2JFj.png" alt="Deprecaated"></a>
According to <a href="https://developer.android.com/reference/java/lang/Deprecated" target="_blank" rel="noopener noreferrer">Official Android Documentation</a> Deprecated itself is deprecated in API level S. So what's the replacement for Deprecated which itself is deprecated?</p>
<p>Edit: Added web archive <a href="https://web.archive.org/web/20210218192448/https://developer.android.com/reference/java/lang/Deprecated" target="_blank" rel="noopener noreferrer">link</a> for historical reference.</p>


I see that the explicit cast syntax for boolean `(boolean)` is syntactically legal, but I can&#39;t think of a use for it.  The corresponding Boolean object -- or rather casting back and forth between boolean and Boolean -- is handled by autoboxing.  So it seems like a useless language artifact of the compiler.  Is there a functional scenario I am missing? 


In Java is boolean cast useless?

I tried to implement request permissions for writing and reading from storage. Everything worked good but today Android showed me that the method onRequestPermissionsResult(...) is deprecated. There are so many questions about this topic in StackOverflow, but unfortunately, they are outdated. 

I called the methods below in a fragment. 

It was suggested simply to call:

    requestPermissions(new String[] {Manifest.permission.WRITE_EXTERNAL_STORAGE},
    StorageKeys.STORAGE_PERMISSION_CODE)

instead of my approach:

    ActivityCompat.requestPermissions(getActivity(),
    new String[] {Manifest.permission.WRITE_EXTERNAL_STORAGE},
    StorageKeys.STORAGE_PERMISSION_CODE))

But both of them show that onRequestPermissionsResult(...) is deprecated.

Here is my onRequestPermissionsResult(...)-method:

      @Override
      public void onRequestPermissionsResult(int requestCode, @NonNull String[] permissions,
                                             @NonNull int[] grantResults) {
    
        if (requestCode == StorageKeys.STORAGE_PERMISSION_CODE) {
    
          if (grantResults.length &gt; 0
              &amp;&amp; grantResults[0] == PackageManager.PERMISSION_GRANTED) {
    
            exportBibTex.createBibFile();
            exportBibTex.writeBibFile(exportBibTex
                .getBibDataLibrary(libraryModel, bookDao, noteDao));
    
            Toast.makeText(getContext(),
                getString(R.string.exported_file_stored_in) + &#39;\n&#39;
                    + File.separator + StorageKeys.DOWNLOAD_FOLDER + File.separator + fileName
                    + StorageKeys.BIB_FILE_TYPE, Toast.LENGTH_LONG).show();
    
          } else {
            Toast.makeText(getContext(), R.string.storage_permission_denied,
                Toast.LENGTH_SHORT).show();
          }
        }
      }

Here is a simple alert dialog, in which I call the onRequestPermissionsResult(...):

      private void showRequestPermissionDialog() {
        AlertDialog.Builder reqAlertDialog = new AlertDialog.Builder(getContext());
        reqAlertDialog.setTitle(R.string.storage_permission_needed);
        reqAlertDialog.setMessage(R.string.storage_permission_alert_msg);
    
        reqAlertDialog.setPositiveButton(R.string.ok,
            (dialog, which) -&gt; ActivityCompat.requestPermissions(getActivity(),
                new String[] {Manifest.permission.WRITE_EXTERNAL_STORAGE},
                StorageKeys.STORAGE_PERMISSION_CODE));
        reqAlertDialog.setNegativeButton(R.string.cancel,
            (dialog, which) -&gt; dialog.dismiss());
    
        reqAlertDialog.create().show();
      }

Is there any alternative for onRequestPermissionsResult(...), that I can use?

Android - onRequestPermissionsResult() is deprecated. Are there any alternatives?

Should I be worried about *JCenter* being deprecated?

Why should I migrate my libraries from *JCenter* to other Maven repositories?

Can I continue to use `jcenter()` in my Gradle build script?




JCenter deprecation; impact on Gradle and Android

I am somewhat new to coding and am trying to use the Lombok plugin to automatically create Getters/Setters e.t.c. for my fields of a specific class. In doing so I get greeted with the following error:

The error:

&gt; java: java.lang.IllegalAccessError: class lombok.javac.apt.LombokProcessor (in unnamed module @0x3b67ef9b) cannot access class com.sun.tools.javac.processing.JavacProcessingEnvironment (in module jdk.compiler) because module jdk.compiler does not export com.sun.tools.javac.processing to unnamed module @0x3b67ef9b

After doing some searching online, I found out that this error is related to an issue in OpenJDK 15 but I am currently using OpenJDK 16, hence why I am confused that I am still getting this error.

This thread claims to have a solution: https://github.com/rzwitserloot/lombok/issues/2681#issuecomment-748616687 but after implementing the plugin, it does not seem to make any difference and I still receive the error.

I have most likely made a trivial mistake since I am a beginner but if someone knows what I am missing please let me know.


&lt;h3&gt;Class Using @Data (Lombok):&lt;/h3&gt;

```package sia.tacocloud;
import lombok.Data;

@Data
public class Ingredient {

    private final String id;
    private final String name;
    private final Type type;

    public enum Type {
        WRAP, PROTEIN, VEGGIES, CHEESE, SAUCE
    }

}

```

&lt;h3&gt;My Pom File:&lt;/h3&gt;

```&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
	xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
	&lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
	&lt;parent&gt;
		&lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
		&lt;artifactId&gt;spring-boot-starter-parent&lt;/artifactId&gt;
		&lt;version&gt;2.4.4&lt;/version&gt;
		&lt;relativePath/&gt; &lt;!-- lookup parent from repository --&gt;
	&lt;/parent&gt;
	&lt;groupId&gt;sia&lt;/groupId&gt;
	&lt;artifactId&gt;taco-cloud&lt;/artifactId&gt;
	&lt;version&gt;0.0.1-SNAPSHOT&lt;/version&gt;
	&lt;name&gt;taco-cloud&lt;/name&gt;
	&lt;description&gt;Taco Cloud Project&lt;/description&gt;
	&lt;properties&gt;
		&lt;java.version&gt;16&lt;/java.version&gt;
	&lt;/properties&gt;
	&lt;dependencies&gt;
		&lt;dependency&gt;
			&lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
			&lt;artifactId&gt;spring-boot-starter-thymeleaf&lt;/artifactId&gt;
		&lt;/dependency&gt;
		&lt;dependency&gt;
			&lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
			&lt;artifactId&gt;spring-boot-starter-web&lt;/artifactId&gt;
		&lt;/dependency&gt;

		&lt;dependency&gt;
			&lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
			&lt;artifactId&gt;spring-boot-devtools&lt;/artifactId&gt;
			&lt;scope&gt;runtime&lt;/scope&gt;
			&lt;optional&gt;true&lt;/optional&gt;
		&lt;/dependency&gt;
		&lt;dependency&gt;
			&lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
			&lt;artifactId&gt;spring-boot-starter-test&lt;/artifactId&gt;
			&lt;scope&gt;test&lt;/scope&gt;
		&lt;/dependency&gt;
		&lt;dependency&gt;
			&lt;groupId&gt;org.projectlombok&lt;/groupId&gt;
			&lt;artifactId&gt;lombok&lt;/artifactId&gt;
		&lt;/dependency&gt;
	&lt;/dependencies&gt;

	&lt;build&gt;
		&lt;plugins&gt;
			&lt;plugin&gt;
				&lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
				&lt;artifactId&gt;spring-boot-maven-plugin&lt;/artifactId&gt;
			&lt;/plugin&gt;
		&lt;/plugins&gt;
	&lt;/build&gt;

&lt;/project&gt;
```


java.lang.IllegalAccessError: class lombok.javac.apt.LombokProcessor cannot access class com.sun.tools.javac.processing.JavacProcessingEnvironment

I have a [Gradle][1] project in Ubuntu.  It&#39;s written in Java 14.  I have the Java 14 JDK installed.  When I build it from the command line, everything works, but no one wants to use a command line!  When I open it in IntelliJ IDEA, it throws an error:

```lang-none
* Where:
Initialization script &#39;/tmp/ijmapper.gradle`

* What went wrong:
Could not compile initialization script &#39;/tmp/ijmapper.gradle`.
&gt; Startup failed:
General error during semantic analysis: Unsupported class file major version 60.
```

followed by a long, unhelpful stack trace that says a lot about Groovy.  (The project is not a Groovy project; it&#39;s a Java project.)

[Major version 60 refers to Java 16,][2] which this project is not using.  I&#39;ve already gone into *Project Structure* and made sure that it&#39;s set to use JDK version 14.  But the name &quot;ijmapper&quot; suggests that this has something to do with IntelliJ specifically, and this is likely an IDE problem rather than a project problem.

The mapper file simply says:

`if(!ext.has(&#39;mapPath&#39;)) ext.mapPath = { path -&gt; path}`

A simple polyfill, in other words.

What&#39;s going on here and how can I fix it?

  [1]: https://en.wikipedia.org/wiki/Gradle
  [2]: https://stackoverflow.com/questions/9170832/list-of-java-class-file-format-major-version-numbers




How can I fix &quot;unsupported class file major version 60&quot; in IntelliJ IDEA?

Android Studio Arctic Fox Canary 8 started to warn that `JCenter is at end of life`

[![enter image description here][1]][1]

But I cannot just delete `jcenter()` declarations since it hosts a lot of android artifacts, it would lead to `Could not resolve all artifacts` error. What is the right way to solve this warning?


  [1]: https://i.stack.imgur.com/qQiwt.png

&quot;JCenter is at end of life&quot; android lint warning, what is the replacement?

Stetho and Google Chrome DevTools have become unusable after a macOS update (I doubt that macOS update is the origin of this bug, but I prefer to mention it).

Here is the appearance of DevTools after the open of &quot;inspect mode&quot; on a device (provided by Facebook Stetho library for Android &amp; OKHttp).

![DevTools window](https://i.stack.imgur.com/8AK7W.png)


There are no longer &quot;CSS&quot; stylesheets on the page and fonts have changed.
Many tab pages aren&#39;t displayed (i.e. Network Requests), I only have access to some error messages :

```
There were 84 bytes that were not consumed while processing request 4
There were 84 bytes that were not consumed while processing request 5
There were 84 bytes that were not consumed while processing request 6
Failed to clear temp storage: undefined
```

I followed instructions on this issue : https://stackoverflow.com/questions/31358446/failed-to-clear-temp-storage/35172470 and this one : https://stackoverflow.com/questions/36850053/failed-to-clear-temp-storage-securityerror-in-chrome?noredirect=1&amp;lq=1 but I haven&#39;t been able to fix the problem. 

Here is what I tried :
 - Uninstall and reinstall Chrome with AppCleaner
 - Remove chrome cache from disk
 - Remove chrome profiles from `~/Library/Application\ Support/Google/Chrome`
 - Create and use a new Chrome profile
 - Try to connect on Firefox distant debug (unfonctionnal)
 - Restart system

Have any of you ever encountered this problem ?
Thanks !



Chrome DevTools broken - Stetho unusable

When creating a new project in Android Studio Arctic Fox Canary 8, this is the app level build.gradle

```
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
    repositories {
        google()
        mavenCentral()
    }
    dependencies {
        classpath &quot;com.android.tools.build:gradle:7.0.0-alpha08&quot;
        classpath &quot;org.jetbrains.kotlin:kotlin-gradle-plugin:1.4.30&quot;

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

```

When creating the same new project in the Android Studio 4.1.2, the app-level build.gradle file is this:

```
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
    ext.kotlin_version = &quot;1.3.72&quot;
    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath &quot;com.android.tools.build:gradle:4.1.2&quot;
        classpath &quot;org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version&quot;

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        google()
        jcenter()
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

```

One of the libraries I am using requires the `allprojects`

I manually tried to add the `allprojects` section in Canary 8, received this error:

```
 problem occurred evaluating root project &#39;My Application&#39;.
&gt; Build was configured to prefer settings repositories over project repositories but repository &#39;Google&#39; was added by build file &#39;build.gradle&#39;
```

Why was the `allprojects` in Android Studio Canary 8 was removed and how can I add it back so that I can use the libraries?

In Android Studio Arctic Fox Canary 8, the app level build.gradle does not generate `allprojects` section and causes error when manually added

While trying to Generate a singed apk I&#39;m getting this error

    Entry name &#39;classes.dex&#39; collided

Can someone tell me how to solve it? I recently changed the default package name which was com.exmaple to my app&#39;s name. It builds correctly but gives this error while trying to generate a signed APK

My android studio version is 4.1.2

Please let me know if you need more information and I will update the question accordingly

Content Type	Original Author	Original Content on Stackoverflow
Question	YaMiN	View Question on Stackoverflow
Solution 1 - Java	Stephen C	View Answer on Stackoverflow

Android Deprecated Annotation is deprecated, what's the replacement?

Java Problem Overview

Java Solutions

Solution 1 - Java

Are Java programs just instances of the JRE?

Non-nullable property must contain a non-null value when exiting constructor. Consider declaring the property as nullable

Attributions