package android.support.annotation does not exist

在把百度地图的安卓源码放到自己的源码中发生了报错。
程序报错package android.support.annotation does not exist,
在网上找了很多,
要不就是进android studio 把support仓库卸载之后重装,结果卸载之后,那个就找不到了,又手动跑外网下载安装support,

要不就是更新SDK,换V4包,

最后我把那些
import android.support.annotation
改成了
import androidx.annotation

然后各种修修补补,才能勉强可以用。

参考链接:1、https://blog.csdn.net/BigMoster/article/details/77676711
2、https://blog.csdn.net/Mr_Tony/article/details/49363997
3、https://blog.csdn.net/kankanlj/article/details/83899503
4、https://blog.csdn.net/hhdhz/article/details/87395833
5、https://blog.csdn.net/u012149181/article/details/78690296

如果要开发百度地图的话,这个文章还是很有用的,https://blog.csdn.net/qq_34115899/article/details/80541545

### Spring Boot `@ConfigurationProperties` Prefix Usage and Requirements In Spring Boot applications, the `@ConfigurationProperties` annotation allows binding externalized properties (from sources like `.properties`, `.yml`, or environment variables) into strongly-typed Java objects. The prefix attribute of this annotation is crucial as it specifies which set of properties should be bound to the annotated class. The syntax for using `@ConfigurationProperties` with a specific prefix looks like: ```java @ConfigurationProperties(prefix = "my.custom.prefix") public class CustomProperties { private String property; // getters and setters... } ``` For proper functioning, ensure that the component scanning can find your configuration classes by either adding them within an auto-detected package or explicitly registering them through `@Import` annotations or bean definitions[^1]. Additionally, when configuring such beans, one must enable support for processing these configurations typically done via `@EnableConfigurationProperties`. This ensures that any beans marked with `@ConfigurationProperties` are processed correctly during application startup. An example setup might look like so: ```java import org.springframework.boot.context.properties.ConfigurationProperties; import org.springframework.context.annotation.Bean; import org.springframework.context.annotation.Configuration; @Configuration @EnableConfigurationProperties(CustomProperties.class) public class AppConfig { } // Define where to bind properties from. @ConfigurationProperties(prefix = "app.datasource") public class DataSourceProperties { private String url; private String username; private String password; // standard getter/setter methods... } ``` When setting up logging levels dynamically at runtime using HTTP endpoints provided by Actuator, while not directly related to `@ConfigurationProperties`, demonstrates how flexible property management in Spring Boot can be extended beyond just static files[^3]. However, for managing complex settings effectively, leveraging `@ConfigurationProperties` remains essential due to its type-safe nature over traditional `Environment` abstraction alone. #### Validation Support Validation groups may also apply constraints on fields inside `@ConfigurationProperties`-annotated POJOs ensuring only valid data gets injected into components relying upon those values. To achieve validation automatically without manual calls to validators, include `spring-boot-starter-validation`. --related questions-- 1. How does one validate properties loaded via `@ConfigurationProperties`? 2. What mechanisms exist for refreshing `@ConfigurationProperties` after changes occur outside the JVM process? 3. Can you provide examples demonstrating secure handling of sensitive information stored under certain prefixes used alongside `@ConfigurationProperties`? 4. In what ways do custom editors play a role in converting string representations found in configuration files back into more complex types expected by target object attributes? 5. Is there any difference between using YAML versus Properties format specifically concerning multi-level nested keys accessed through dot notation within `@ConfigurationProperties` bindings?
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值