-
Notifications
You must be signed in to change notification settings - Fork 13
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
Builder not found #13
Comments
I also don't see a timing file created in |
I also tried executing this extension and creating an <extensions xmlns="http://maven.apache.org/EXTENSIONS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/EXTENSIONS/1.0.0 http://maven.apache.org/xsd/core-extensions-1.0.0.xsd">
<extension>
<groupId>io.takari.maven</groupId>
<artifactId>takari-smart-builder</artifactId>
<version>0.6.1</version>
</extension>
</extensions> If you execute with |
I can include any JAR in the classpath - it doesn't mean the routines are necessarily active in my build.
The reason I'm suspicious of this extension is the lack of interest in it, it has no configurable parameters, it doesn't register with the builder interface switch '--builder' which the documentation instructs me to use, and its replacing default Maven functionality. How do I know that its playing nicely with the above MultiThreadedBuilder and gitflow-incremental-builder? I compared the reactor order of projects with and without the extension, and they are identical. In a reactor of over 500 projects I expect at least something to change when critical path scheduling is applied. |
I cannot reproduce this when smart-builder installed according to documentation in README: |
When I run
I get this error
Apache Maven 3.6.3
Maven home: /usr/share/maven
Java version: 1.8.0_275, vendor: Private Build, runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_ZA, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-58-generic", arch: "amd64", family: "unix"
The text was updated successfully, but these errors were encountered: