-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GH-41307: [Java] Use org.apache:apache parent pom version 31 #41772
GH-41307: [Java] Use org.apache:apache parent pom version 31 #41772
Conversation
@lidavidm re-uploading the pull request with the fix for |
@github-actions crossbow submit java test-conda-python-3.10-spark-v3.5.0 |
|
The |
@github-actions crossbow submit -g java |
Revision: a5c8d7d Submitted crossbow builds: ursacomputing/crossbow @ actions-b536a3215e |
These seems to be passing, but there are some other CIs failing. |
Yes, noticed that some flight tests seem flaky? I also found occurrence of this issue in other pull requests like this job for example: https://github.com/apache/arrow/actions/runs/9185953424/job/25260768750 |
Yes indeed. Would you mind filing an issue for that? |
a5c8d7d
to
1dd63bc
Compare
@vibhatha would appreciate if you could trigger another crossbow run to validate latest changes |
It should fix the problem I mentioned in another issue. Thanks ! |
@github-actions crossbow submit -g java |
Revision: 37f0b16 Submitted crossbow builds: ursacomputing/crossbow @ actions-a6201b76d3 |
I didn't complete it, just tried a few ideas. |
@laurentgo we have an issue in the dataset module: https://github.com/ursacomputing/crossbow/actions/runs/9216288007/job/25356948996#step:6:55162 |
I noticed but I'm not able to reproduce at this time. Looks like there's been changes to java/pom.xml causing a conflict, so will rebase and force push. Would appreciate if someone could trigger a crossbow run just after |
37f0b16
to
55b69e3
Compare
@github-actions crossbow submit -g java |
|
@lidavidm seems like we have an issue here arrow::PoolBuffer::Reserve(long long) We probably need to get this dump, download locally and debug? |
Given the small offset I would guess that Reserve was called on a nullptr buffer |
That said I don't think this has to block the PR? |
Yes I think the same. |
I was able to get a reproduction and capture jvm output, hotspot error log and core dump. I put the link to the archive in #32945 . |
@github-actions crossbow submit -g java |
Revision: 7fbe800 Submitted crossbow builds: ursacomputing/crossbow @ actions-67dd745c51 |
find . \ | ||
"(" -name "*-javadoc.jar" -o -name "*-sources.jar" ")" \ | ||
-exec echo {} ";" \ | ||
-exec cp {} $dist_dir ";" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is covered by the line below?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is covered by the install
phase which also includes the previous phases like compile
or package
. The same steps are already declared in the apache parent pom when using the arrow-release
profile.
assembly:single
was used to generate a single artifact with the whole tree and is handled by the parent plugin with thesource-release-assembly
execution in the parent pom (I should also remove the-DdescriptorId=
property as well I guess)source:jar
is handled byattach-sources
execution bound by default topackage
phasejavadoc:jar
is handled by theattach-javadocs
execution bound by default to thepackage
phase
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah sorry, might I misread your question. If you're asking about removing the find
command, yes, it's because it's handled by the second find
command which will get the single assembly, the sources and javadoc jars from the local repository and copy them to the $dist_dir
directory
<!-- | ||
Downgrade maven-shade-plugin specifically for this module. | ||
Using a newer version up to at least 3.5.1 will cause | ||
issues in the arrow-tools tests looking up FlatBuffer | ||
dependencies. | ||
--> | ||
<version>3.2.4</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, why does this not apply anymore? We saw problems last time we tried to upgrade
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, as discussed in the issue associated to the rollback, the problem was caused by the combination of arrow configuration replaced the main artifact and its associated pom with the shaded artifact and its reduced pom.xml, and the newer versions of the plugins fixing an issue where the reduced pom.xml was not attached to the artifact.
It is solved by disabling the reduced pom.xml generation and attachment using the createDependencyReducedPom
configuration property
Use/update Maven modules to `org.apache:apache:31` and clean up Maven modules to remove unnecessary configuration or outdated workarounds * Add `org.apache:apache:31` to `org.apache.arrow:arrow-bom` and `org.apache.arrow.maven.plugins:arrow-maven-plugins` to make them conformant with ASF standards * Update `org.apache.arrow:arrow-java-root` parent to `org.apache:parent:31` * Use `version.*` and other properties to override plugin versions defined by `org.apache:parent` * Move standalone plugin versions under pluginManagement at the top level * Cleanup redundant plugin version or configuration declaration * Update `maven-dependency-plugin` to 3.6.1 and add the required overrides when necessary * Update `maven-shade-plugin` to 3.5.1 (via `org.apache:parent`) - disable reduced dependency pom creation for non-terminal modules * Remove enforcer check for java and maven version (handled by `org.apache:parent`) * Remove unnecessary `mvnrepository` link comments * Remove `m2e.version` property check in profiles (only needed for errorprone plugin configuration which is incompatible with M2E) * Cleanup `argLine` overrides for surefire/failsafe plugins * Remove unnecessary `../pom.xml` `<relativePath>` directives * Remove source/target/encoding configuration properties for `maven-compiler-plugin`, `maven-javadoc-plugin` and `maven-resources-plugin` as it is handled by `org.apache:parent` and plugin themselves * Remove unnecessary copy of codegen templates in `arrow-vector` module * Remove unnecessary junit jupiter engine dependencies for surefire/failsafe plugins.
Newer versions of javadoc and sources plugins do not allow attaching multiple times the "same" artifact, which causes issues with the `ci/scripts/java_full_build.sh` Update the script to remove the standalone assembly:single sources:jar and javadoc:jar which are already managed by `org.apache:apache` parent/`apache-release` profile Also remove the unnecessary copy of sources and javadoc jars from the projects as they are also installed into the local maven repository and copied from there as well Disable source-release zipfile generation in maven and bom directories as the main artifact generated by java-root will also contains both directories
0d01e78
to
a7cb636
Compare
@github-actions crossbow submit -g java |
I'll merge once I confirm the crossbow jobs |
Thanks @laurentgo for sticking with this! |
Revision: a7cb636 Submitted crossbow builds: ursacomputing/crossbow @ actions-a59d8b70f9 |
There's only a single zip `arrow-java-root-{version}-source-release.zip` containnig the source directory of the whole project.
Ah thanks, I was just about to ask about that |
@github-actions crossbow submit java-jars |
My bad, we discussed about the artifacts generated and I forgot to update the task verifying those. My change include a change in I just pushed a change to the dev task to not look for those two extra zip files (one was generated for the |
Revision: b64c65d Submitted crossbow builds: ursacomputing/crossbow @ actions-d9cdcf68ef
|
After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 01d2fa0. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 1 possible false positive for unstable benchmarks that are known to sometimes produce them. |
Use/update Maven modules to
org.apache:apache:31
and clean up Maven modules to remove unnecessary configuration or outdated workaroundsorg.apache:apache:31
toorg.apache.arrow:arrow-bom
andorg.apache.arrow.maven.plugins:arrow-maven-plugins
to make them conformant with ASF standardsorg.apache.arrow:arrow-java-root
parent toorg.apache:parent:31
version.*
and other properties to override plugin versions defined byorg.apache:parent
maven-dependency-plugin
to 3.6.1 and add the required overrides when necessarymaven-shade-plugin
to 3.5.1 (viaorg.apache:parent
)org.apache:parent
)mvnrepository
link commentsm2e.version
property check in profiles (only needed for errorprone plugin configuration which is incompatible with M2E)argLine
overrides for surefire/failsafe plugins../pom.xml
<relativePath>
directivesmaven-compiler-plugin
,maven-javadoc-plugin
andmaven-resources-plugin
as it is handled byorg.apache:parent
and plugin themselvesarrow-vector
module