Fragment生命周期

  1. onAttach
    Called when a fragment is first attached to its activity
  2. onCreate
    Called to do initial creation of a fragment
    Note that this can be called while the fragment’s activity is still in the process of being created. As such, you can not rely on
    Things like the activity’s content view hierarchy being initialized
  3. onCreateView
    Called to have the fragment instantiate its user interface view
    If you return a View from here, you will later be called in onDestroyView when the view is being released.
  4. onViewCreated
    Called immediately after onCreateView has returned, but before any saved state has been restored in to the view. This gives subclasses a chance to initialize themselves once they know their view hierarchy has been completely created. The fragment’s view hierarchy is not however attached to its parent at this point.
  5. onActivityCreated
    Called when the fragment’s activity has been created and this
    fragment’s view hierarchy instantiated
    It can be used to do final initialization once these pieces are in place, such as retrieving views or restoring state.It is also useful for fragments that use setRetainInstance(boolean) to retain their instance,
    as this callback tells the fragment when it is fully associated with the new activity instance.
  6. onStart
    Called when the Fragment is visible to the user.
    This is generallytied toActivity.onStart of the containing Activity’s lifecycle.
  7. onResume
    Called when the fragment is visible to the user and actively running.
    This is generally tied to Activity.onResume of the containing Activity’s lifecycle.
  8. onPause
    Called when the Fragment is no longer resumed.
    This is generally tied to Activity.onPause of the containing Activity’s lifecycle.
  9. onStop
    Called when the Fragment is no longer started.
    This is generally tied to Activity.onStop of the containing Activity’s lifecycle.
  10. onDestroyView
    Called when the view previously created by onCreateView has been detached from the fragment. The next time the fragment needs to be displayed, a new view will be created.
  11. onDestroyView
    Called when the fragment is no longer in use.
  12. onDetach
    Called when the fragment is no longer attached to its activity
资源下载链接为: https://pan.quark.cn/s/22ca96b7bd39 在当今的软件开发领域,自动化构建与发布是提升开发效率和项目质量的关键环节。Jenkins Pipeline作为一种强大的自动化工具,能够有效助力Java项目的快速构建、测试及部署。本文将详细介绍如何利用Jenkins Pipeline实现Java项目的自动化构建与发布。 Jenkins Pipeline简介 Jenkins Pipeline是运行在Jenkins上的一套工作流框架,它将原本分散在单个或多个节点上独立运行的任务串联起来,实现复杂流程的编排与可视化。它是Jenkins 2.X的核心特性之一,推动了Jenkins从持续集成(CI)向持续交付(CD)及DevOps的转变。 创建Pipeline项目 要使用Jenkins Pipeline自动化构建发布Java项目,首先需要创建Pipeline项目。具体步骤如下: 登录Jenkins,点击“新建项”,选择“Pipeline”。 输入项目名称和描述,点击“确定”。 在Pipeline脚本中定义项目字典、发版脚本和预发布脚本。 编写Pipeline脚本 Pipeline脚本是Jenkins Pipeline的核心,用于定义自动化构建和发布的流程。以下是一个简单的Pipeline脚本示例: 在上述脚本中,定义了四个阶段:Checkout、Build、Push package和Deploy/Rollback。每个阶段都可以根据实际需求进行配置和调整。 通过Jenkins Pipeline自动化构建发布Java项目,可以显著提升开发效率和项目质量。借助Pipeline,我们能够轻松实现自动化构建、测试和部署,从而提高项目的整体质量和可靠性。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

沐怡旸--指针诗笺

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

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

余额充值