Hi Konrad,
The plugin documentation should be updated now. Fixed at: 2e3bb65
<https://github.com/apache/sling-site/commit/2e3bb65ae472c79eb6a55965f4496bc5bbd3fc88>
I got distracted by the error below from the starter ci build after
updating to the released versions. I retried the ci starter build today
and the conflict seems to have resolved itself and the build worked. Maybe
something could be done to ensure that the docker container name is more
unique for each test run?
Caused by: io.fabric8.maven.docker.access.hc.http.HttpRequestException:
{"message":"Conflict. The container name \"/sling-1\" is already in
use by container
\"561df86f937afdecddc271bf24a537c182c98bc266337e5eee0b679423710689\".
You have to remove (or rename) that container to be able to reuse that
name."} (Conflict: 409)
Regards,
Eric
On Wed, Nov 23, 2022 at 1:08 AM Konrad Windszus <[email protected]> wrote:
> Thanks for the release, can you also publish the Maven site according to
> https://sling.apache.org/documentation/development/release-management.html#appendix-b-deploy-maven-plugin-documentation-if-applicable
> <
> https://sling.apache.org/documentation/development/release-management.html#appendix-b-deploy-maven-plugin-documentation-if-applicable>
> ?
>
> I still see the old SNAPSHOT version at
> https://sling.apache.org/components/sling-feature-launcher-maven-plugin/ <
> https://sling.apache.org/components/sling-feature-launcher-maven-plugin/>.
>
> Konrad
>
> > On 23. Nov 2022, at 04:18, Eric Norman <[email protected]> wrote:
> >
> > Hi,
> >
> > The vote has passed with the following result :
> >
> > +1 (binding): Daniel Klco, Robert Munteanu, Eric Norman
> > +1 (non binding): none
> >
> > I will copy this release to the Sling dist directory and promote the
> > artifacts to the central Maven repository.
>
>
