Hi ebr-dev-
I’ve spent a couple hours today trying to figure something out but haven’t had any luck, so I thought I’d reach out here.
When ebr tries to retrieve the license file, it times out.
Up till now I have worked around this issue by just letting it time out and then manually adding the license, but this really slows things down.
I believe this happens because I am behind a proxy and AboutFilesUtil (which retrieves the license file) does not support proxies.
I cloned the repo and made some changes to hardcode my proxy in AboutFilesUtil (after I get this to work I will switch from hardcoding to getting it from environment).
I built the repo and installed my version of ebr using ‘mvn -f releng/maven-plugins/pom.xml clean install -DskipTests’.
However, when I try to use ebr (in conjunction with orbit-recipes), the release version gets used instead of the local build that was installed into my maven repository.
I verified that my fork is there in ~/.m2/repository by inspecting the contents of ~/.m2/repository/org/eclipse/ebr.
I’ve tried a couple things, including…
- delete ~/.m2/repository/org/eclipse/ebr, then install my fork (based on 1.1.1): the 1.1.0 release version gets downloaded and used instead
- repeat the above, then invoke ebr using an explicit version (e.g., instead of ebr:create-recipe, use org.eclipse.ebr:ebr-maven-plugin:1.1.1-SNAPSHOT:create-recipe): this seems to get closer, but the 1.1.0
release version gets downloaded and seems to be getting used instead
It seems like using a fork of a maven plugin should be a fairly common workflow, especially for maven plugin developers, so I imagine I am missing some fairly obvious documentation somewhere, but I can’t seem
to find it on my own.
I’d also like to learn how maven resolves the string “ebr” to a plugin, but so far I haven’t found the docs which explain how this resolution occurs.
Thanks in advance for any help with this!
Tony Homer