Yeah,
https://repository.apache.org/content/repositories/orgapachefury-1053/org/apache/fury/fury-parent/
has pom.xml file included only, so I released it to Maven Central.
On Mon, Oct 7, 2024 at 6:12 PM PJ Fanning wrote:
>
> This looks like it was released to Maven Central.
>
> https://repo1.m
This looks like it was released to Maven Central.
https://repo1.maven.org/maven2/org/apache/fury/fury-parent/0.8.0/
On Mon, 7 Oct 2024 at 21:37, Shawn Yang wrote:
>
> Turns out it's uploaded by maven assembly plugin, I skipped it by
> ` -Dassembly.skipAssembly=true` and made a new maven staging
Turns out it's uploaded by maven assembly plugin, I skipped it by
` -Dassembly.skipAssembly=true` and made a new maven staging artifact:
https://repository.apache.org/content/repositories/orgapachefury-1053/org/apache/fury/fury-parent/
On Mon, Oct 7, 2024 at 10:57 AM Shawn Yang wrote:
> It's upl
It's uploaded to maven repository automatically. I just want to release
pom.xml. I will see whether I can just publish pom.xml only.
PJ Fanning 于2024年10月7日 周一10:35写道：
> Why do you have a source release zip in Maven Central? Shouldn't we
> only have the official releases that are released to svn t
Why do you have a source release zip in Maven Central? Shouldn't we
only have the official releases that are released to svn to
dist.apache.org?
I would like to raise a vote about this part of the process. I guess
it's sort of up to the PPMC but this seems odd to me.
https://repository.apache.org
Yean, I uploaded to staging repository using the same commiidas rest of
fury 0.8.0
PJ Fanning 于2024年10月7日 周一10:17写道：
> The new fury-parent release should be done using the exact same git
> commit as the rest of the 0.8.0 release.
>
> On Mon, 7 Oct 2024 at 17:16, PJ Fanning wrote:
> >
> > A quali
The new fury-parent release should be done using the exact same git
commit as the rest of the 0.8.0 release.
On Mon, 7 Oct 2024 at 17:16, PJ Fanning wrote:
>
> A qualified yes. You can publish the missing fury-parent.
>
> Could you get someone to validate it though before releasing it? So
> publi
A qualified yes. You can publish the missing fury-parent.
Could you get someone to validate it though before releasing it? So
publish to staging area in Nexus (Nexus 'close') and then when
validated, release it.
On Mon, 7 Oct 2024 at 16:01, Shawn Yang wrote:
>
> In vote thread:
> https://lists.a
In vote thread:
https://lists.apache.org/thread/1l37kv1xtgrjh60psfjcyngfd4jctbrg we missed
fury-parent pom.xml, this made fury 0.8.0 unusable. it has been issued by
users in https://github.com/apache/fury/issues/1872.
Since fury-parent pom.xml is just a convenience release, the source release
is u
