abstractdog commented on PR #441: URL: https://github.com/apache/tez/pull/441#issuecomment-3791239002
> > > I'm speculating and might be wrong but is it possible that the `-Dmaven.repo.local=/home/jenkins/jenkins-home/workspace/tez-multibranch_PR-441/yetus-m2/tez-master-patch-0` is gone by the time this ran? > > > ``` > > > /patch-mvninstall-tez-tests.txt > > > /patch-mvninstall-tez-tools_tez-javadoc-tools.txt > > > ``` > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ``` > > > WARNING] The POM for org.apache.tez:tez-api:jar:1.0.0-SNAPSHOT is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details > > > [WARNING] The POM for org.apache.tez:tez-runtime-library:jar:1.0.0-SNAPSHOT is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details > > > [WARNING] The POM for org.apache.tez:tez-mapreduce:jar:1.0.0-SNAPSHOT is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details > > > [WARNING] The POM for org.apache.tez:tez-dag:jar:1.0.0-SNAPSHOT is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details > > > ``` > > > > > > As its not able to find the previously build modules > > That's what I was suspecting yesterday as well. Maybe I couldn't communicate it better. I agree that building the project module by module is not necessarily the most optimal way, because we can figure out what went wrong even if the whole project is built in one go, I'm totally fine with a patch where the maven build phase is done in one go, and as a positive side effect, this issue would already go away -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
