|installing swtbot into target (3.7m4) using p2 director [message #654929]
||Thu, 17 February 2011 16:31
| Pete MacLiesh
Registered: July 2009
I have a question about installing swtbot into a target product for testing.
Currently we're trying to get a flow working with eclipse 3.7 m4
Here's how i set up the product:
- unzip eclipse platform (note: not the sdk)
- unzip out product build on top of that
- use p2 director cmdline to install gef into the target
- use p2 to install swtbot into the target
If i do that last step to install swtbot using the "install new software UI" in that running target then the installation works fine.
If i do it using the p2 director cmd line then it doesn't resolve dependencies and fails. So what is the p2 UI doing that the p2 cmd line is not? Is this something to do with swtbot, or is this p2?
I want to make this part of a headless build/test flow, so using the UI is not really an option ... but if there is a different way of dropping in the dependencies that someone can point me to, that would be cool. I don't want the tested platform to be the SDK - that is polluted with lots of stuff that we don't put in our product.
Here's that last cmd:
Q:\temp\test6a>q:\depot\eclipse\370m4\eclipse\eclipsec.exe -application org.eclipse.equinox.p2.director -d eclipse -repository http://download.eclipse.org/technology/swtbot/helios/dev-bui ld/update-site/ -installIU org.eclipse.swtbot.eclipse.gef.feature.group,org.eclipse.swt bot.eclipse.test.junit4.feature.group
Installing org.eclipse.swtbot.eclipse.gef.feature.group 126.96.36.19910117_1743-b492ddb-dev-e36.
Installing org.eclipse.swtbot.eclipse.test.junit4.feature.group 188.8.131.5210117_1743-b492ddb-dev-e36.
Cannot complete the install because one or more required items could not be found.
Software being installed: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 184.108.40.20610117_1743-b492ddb-dev-e36 (org.eclipse.swtbot.eclipse.test.junit4.feature.group 220.127.116.1110117_1743-b492ddb-dev-e36)
Missing requirement: Headless Ant support for JUnit4 18.104.22.16810117_1743-b492ddb-dev-e36 (org.eclipse.swtbot.ant.optional.junit4 22.214.171.12410117_1743-b492ddb-dev-e36) requires 'bundle org.junit4 0.0.0' but it could not be found
Cannot satisfy dependency:
From: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 126.96.36.19910117_1743-b492ddb-dev-e36 (org.eclipse.swtbot.eclipse.test.junit4.feature.group 188.8.131.5210117_1743-b492ddb-dev-e36)
To: org.eclipse.swtbot.ant.optional.junit4 [184.108.40.20610117_1743-b492ddb-dev-e36]
Application failed, log file location: Q:\depot\eclipse\370m4\eclipse\configuration\1297920754563.l og
|Re: installing swtbot into target (3.7m4) using p2 director [message #655600 is a reply to message #655422]
||Mon, 21 February 2011 21:38
| Ketan Padegaonkar
Registered: July 2009
A good start would be to list out the dependencies that SWTBot gets |
pulled in -- or a way to get such a list.
This should pave us a way to either slim these dependencies down -- or
atleast automate and improvie the process of installing these dependencies.
Any volunteers ?
ketan.padegaonkar.name | eclipse.org/swtbot | @ketanpkr
On 2/20/11 10:45 AM, Pete MacLiesh wrote:
> Yes indeed - amongst other things it sucks in about 1/3 of the JDT
> (which we don't suck into our product) and that causes its own problems
> - the workspace .log has over 8000 lines of exceptions generated from
> that partial JDT.
> However, my simple test exercise actually runs with this "larger than
> expected base".
> But i don't know what subset of that i can get away with - and don't
> really have a good idea of how to iterate to get there - because they're
> not "my" direct dependencies. I tried switching to
> org.eclipse.swtbot.eclipse.finder as you suggested, but my test failed
> to load ... so i need to investigate that. Note that even this pulled in
> the same jdt set (i didn't compare the other plugins).
Powered by FUDForum
. Page generated in 0.02519 seconds