|P2 app : builder Juno on target Indigo supported ? [message #884017]
||Sat, 09 June 2012 22:59
| Alix Lourme
Registered: April 2012
I use P2 app (+ant script) to provisioning multiple Eclipse packages automatically (php, java, etc).
I use :
- Juno as builder because some installed plugin must be self signed (bugs.eclipse.org/bugs/show_bug.cgi?id=340345)
- target product (=> "-destination" argument) because I need to have proxy configuration in builder
I have some problem with one plugin : Spring Tool Suite. After install it, platform has many errors (and not usable) after second start.
[JunoBuilder]\eclipsec.exe -application org.eclipse.equinox.p2.director -repository [http]dist.springsource.com/release/TOOLS/update/e3.7,[http]dist.springsource.com/release/TOOLS/composite/e3.7,[http]download.eclipse.org/releases/indigo -installIU org.springframework.ide.eclipse.feature.feature.group,com.springsource.sts.feature.group -tag AddSTS -destination [IndigoPath] -profile epp.package.jee
I thought it was a STS problem => I opened a bug (jira.springsource.org/browse/IDE-1251)
But I tried recently :
- with Juno RC3 as builder, STS 18.104.22.168205010750-M1, no changes
- use Indigo as builder : it works
=> I hypothesized a osgi/dependencies problem (some strange things about Mylyn dependencies in my STS bug description) when builder version is not the same as target product.
Is this case supported by P2 app ? if yes what could I do to determine the cause ?
Thanks in advance.
(Sorry for links, I can't before my 25 first post)
Powered by FUDForum
. Page generated in 0.05952 seconds