That's not the target platform, that's the Indigo M7 mirror. You're
missing stuff from the Eclipse 3.7M7 repo, which is here:
Rebuild your target platform pom & parent pom, and then rebuild AS using
just this:
cd ~/trunk/build; mvn clean install -Pas-bootstrap
N
On 05/19/2011 05:22 PM, Denis Golovin wrote:
Current target platform still have problems.
http://download.jboss.org/jbosstools/updates/requirements/indigo/20110506...
is actually broken and if build is using only this only repo it fails with
[INFO]
{org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,
osgi.ws=cocoa, osgi.arch=x86, osgi.os=macosx,
org.eclipse.update.install.features=true,
org.osgi.framework.system.packages=}
[INFO] [Software being installed: org.jboss.ide.eclipse.as.test
2.2.0.qualifier, Missing requirement: org.jboss.ide.eclipse.as.test
2.2.0.qualifier requires 'bundle org.eclipse.core.runtime 0.0.0' but it
could not be found]
[ERROR] Internal error: java.lang.RuntimeException:
org.eclipse.equinox.p2.core.ProvisionException: No solution found
because the problem is unsatisfiable. -> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
java.lang.RuntimeException:
org.eclipse.equinox.p2.core.ProvisionException: No solution found
because the problem is unsatisfiable.
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:163)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.RuntimeException:
org.eclipse.equinox.p2.core.ProvisionException: No solution found
because the problem is unsatisfiable.
at
org.sonatype.tycho.p2.impl.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:98)
at
org.sonatype.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:335)
at
org.sonatype.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:300)
at
org.sonatype.tycho.p2.facade.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:406)
at
org.sonatype.tycho.p2.facade.P2TargetPlatformResolver.resolvePlatform(P2TargetPlatformResolver.java:105)
at
org.codehaus.tycho.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:68)
at
org.codehaus.tycho.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:94)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:268)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
... 11 more
Caused by: org.eclipse.equinox.p2.core.ProvisionException: No solution
found because the problem is unsatisfiable.
... 20 more
which is seems to be a problems with artifacts.jar content. It says that
org.eclipse.core.runtime is packed
<artifact classifier='osgi.bundle' id='org.eclipse.core.runtime'
version='3.7.0.v20110110'>
<processing size='1'>
<step id='org.eclipse.equinox.p2.processing.Pack200Unpacker'
required='true'/>
</processing>
</artifact>
but there is only jar version of it (I'm not sure it is a reason, just
guessing)
Denis
On 05/18/2011 08:44 AM, Nick Boldt wrote:
> Thanks, I've added the missing feature.
>
> Keep reporting snafus - we'll eventually get something that works for
> the whole stack - I promise! :)
>
> (And then hopefully it won't break again for RC1 or RC2, which we'll
> pick up once it's all released and happy. I'd be happy to NOT move up
> again unless someone *actually* needs something newer... is that
> possible?)
>
> N
>
> On 05/18/2011 09:37 AM, Xavier Coulon wrote:
>> Hello Nick,
>>
>> It seems like some bundles are still missing :�
>>
>> [INFO]
>> {org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,
>>
>> osgi.ws<http://osgi.ws>=cocoa, osgi.arch=x86, osgi.os=macosx,
>> org.eclipse.update.install.features=true,
>> org.osgi.framework.system.packages=}
>> [INFO] [Software being installed: org.jboss.tools.ws.creation.core.test
>> 1.0.0.qualifier, Missing requirement: org.eclipse.persistence.jpa.jpql
>> 1.0.0.v20110426-r9259 *requires 'bundle org.eclipse.persistence.core
>> 2.3.0.v20110426-r9259'* but it could not be found, Cannot satisfy
>> dependency: org.eclipse.jpt.jpa.core 3.0.0.v201104270001 depends on:
>> bundle org.eclipse.persistence.jpa.jpql [1.0.0,2.0.0), Cannot satisfy
>> dependency: org.jboss.ide.eclipse.as.test 2.2.0.v20110421-2216-M1
>> depends on: bundle org.eclipse.jpt.jpa.core 0.0.0, Cannot satisfy
>> dependency: org.jboss.tools.ws.creation.core.test 1.0.0.qualifier
>> depends on: bundle org.jboss.ide.eclipse.as.test 0.0.0]
>> [ERROR] Internal error: java.lang.RuntimeException:
>> org.eclipse.equinox.p2.core.ProvisionException: No solution found
>> because the problem is unsatisfiable. -> [Help 1]
>>
>> The 'org.eclipse.persistence.jpa.jpql_1.0.0.v20110426-r9259.jar' is
>> actually part of yesterday's TP you published, but
>> 'org.eclipse.persistence.core 2.3.0.v20110426-r9259' is missing.
>>
>> Regards,
>> Xavier
>>
>> On Tue, May 17, 2011 at 4:06 PM, Nick Boldt<nboldt(a)redhat.com
>> <mailto:nboldt@redhat.com>> wrote:
>>
>>
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.target-platform/
>>
>> and
>>
https://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.target-platform/
>>
>> respinning to include a couple missing features& update to newer
>> versions.
>>
>> When the jobs are done, the URLs below (*target-platform_3.3.indigo/)
>> will update automatically w/ newer timestamped files.
>>
>> Nick
>>
>> On 05/17/2011 03:52 PM, Gary Brown wrote:
>> > Also possibly org.eclipse.wst.css:core
>> >
>> > [ERROR] � � Unresolveable build extension: Plugin
>> org.jboss.maven.plugins:maven-jdocbook-plugin:2.2.3 or one of its
>> dependencies could not be resolved: Could not transfer artifact
>> org.eclipse.wst.css:core:jar:1.1.101-v200705302225 from
>> repository.jboss.org<http://repository.jboss.org>
>> (
http://repository.jboss.org/maven2): Error transferring file:
>> Connection refused -> �[Help 2]
>> >
>> > ----- Original Message -----
>> >> Nick,
>> >>
>> >> It seems that the following three plug-ins were lost from the
>> >> 3.3.Indigo
>> >> target platform (e37M7-wtp33M7.target.zip):
>> >>
>> >> org.eclipse.jpt.common.utility
>> >> org.eclipse.jpt.common.core
>> >> org.eclipse.jpt.common.ui
>> >>
>> >> Victor
>> >>
>> >>
>> >> On 05/16/2011 07:46 PM, Nick Boldt wrote:
>> >>> Available here as sites and/or zips:
>> >>>
>> >>> For use with JBoss Tools 3.3.0.M2:
>> >>>
>> >>>
>>
http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/
>> >>>
>> >>> For use with JBoss Developer Studio 5.0.0.M2:
>> >>>
>> >>>
>>
http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_3.3.in...
>>
>> >>>
>> >>>
>> >>
>> >> _______________________________________________
>> >> jbosstools-dev mailing list
>> >> jbosstools-dev(a)lists.jboss.org
>> <mailto:jbosstools-dev@lists.jboss.org>
>> >>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools& Dev Studio
>>
http://nick.divbyzero.com
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev@lists.jboss.org<mailto:jbosstools-dev@lists.jboss.org>
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>>
>>
>> --
>> Xavier
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio