+1
Cheers,
Jamie
On Wed, Jan 18, 2023 at 4:10 PM Raymond Augé
wrote:
>
> +1
>
> On Wed, Jan 18, 2023 at 2:16 PM wrote:
>
> > +1
> >
> > David
> >
> > On Wednesday, 18 January 2023, Thomas Watson wrote:
> >
> > > Hi,
> > >
> > > We solved 1 issue in this release:
> > > https://issues.apache.org
+1
On Wed, Jan 18, 2023 at 2:16 PM wrote:
> +1
>
> David
>
> On Wednesday, 18 January 2023, Thomas Watson wrote:
>
> > Hi,
> >
> > We solved 1 issue in this release:
> > https://issues.apache.org/jira/browse/FELIX-6581
> >
> > Staging repository:
> > https://repository.apache.org/content/reposi
+1
David
On Wednesday, 18 January 2023, Thomas Watson wrote:
> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/browse/FELIX-6581
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachefelix-1452/
>
> You can use this UNIX script to down
Hi,
We solved 1 issue in this release:
https://issues.apache.org/jira/browse/FELIX-6581
Staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-1452/
You can use this UNIX script to download the release and verify the
signatures:
https://github.com/apache/felix-dev/
I am preparing an SCR 2.2.6 release for vote and I ran into an issue with
mvn release:prepare because of the use of
https://github.com/apache/felix-dev.git has the scm connection. The issue
was trying to push up the commit and tag associated with the prepared
release. Github responded saying that
[
https://issues.apache.org/jira/browse/FELIX-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678242#comment-17678242
]
Tom Watson commented on FELIX-6581:
---
This was fixed in commit
https://github.com/apach
