Open ops4j-issues opened 14 years ago
PeteP commented
I gather from the Priority of 'minor' that this is not a problem for others but it wasn't intuitive at all for me to figure out a workaround for this bug. Just in case that happens to you, here is what I had to do. Finding and adding the right repository did NOT work for me, despite lots of time searching for one.
searched the web for the string '3.5.1.R35x_v20090827' and came up with many false leads, and also this good link:
From here, I downloaded the jar.
Then I installed the jar into my repository using the normal methods for installing a 3rd party jar (in my case nexus UI but you can also use the command line version)
I used these parameters
groupId=org.eclipse
artifactId=osgi
version=3.5.1.R35x_v20090827
Niels B Nielsen created PAXCONSTRUCT-129
When the pax-provision script fails to download a bundle (in my case Eclipse not in my Maven proxy), this ascii art is displayed
_
/ /
/ / Oops, there has been a problem!
/ /
/__/ URL mvn:org.eclipse/osgi/3.5.1.R35x_v20090827 could not be resolved.
_
/__/ Use --log=debug to see details.
But unfortunately the pax-provision does not accept the --log options, and also subsequently fail to stop.
$ pax-provision -f equinox --log=debug
Unable to parse command line options: Unrecognized option: --log=debug
usage: mvn options <goal(s)> <phase(s)>
Affects: 1.4 Votes: 0, Watches: 0