Jesse Glick

Oh, understood! For the moment this is not much of a priority I think, but if it becomes one I would certainly try to offer a PR.

You can remove executions of the `clean` goal and override ```xml ${project.build.directory} ${project.artifactId}-${project.version}.pom ``` (This `flattenedPomFilename` ensures that the filename inside `target` matches that which `install:install` will pick for the...

FYI my core fix was accepted. So whenever that is released, it would suffice to set ```xml 3.6.2 ``` (or whatever it is), as I guess this advanced plugin is...

Not sure. @kzantow do you know?

If you implement the project recognizer, you do not need a custom trait like that—branches (or PRs) will be mapped to branch projects iff they have the right file. Check...

Filed as https://issues.jenkins.io/browse/JENKINS-67363 since that is probably more precise.

Not sure what it is you are trying to accomplish here (there is no test which might demonstrate its usage, or help file, or JIRA issue), but probably you just...

More concisely: ```groovy library identifier: "syndesis-pipeline-library@$BRANCH_NAME", retriever: workspaceRetriever(WORKSPACE) ```

Perhaps instead try just ```groovy library identifier: '...', retriever: legacySCM(scm) ``` I think that would address your use case, assuming you were not patching the library after checkout. Needs testing...

(note: no `@` in the `identifier`) Actually I think that would not work as is, but probably a retriever based on the concept could. TBD