[jbosstools-dev] Source lookup in maven component

Wed May 2 17:07:04 EDT 2012

m2e 1.1 has been removed. TP is respinning to revert this change. 
Apologies, everyone that was my mistake. Ran the m2e juno mirror script 
instead of the m2e indigo one.

https://issues.jboss.org/browse/JBDS-2114
https://issues.jboss.org/browse/JBIDE-11700

N

On 05/02/2012 03:48 PM, Snjezana Peco wrote:
> m2e 1.1.0 has been added today. This is milestone release targeted for
> Eclipse Juno.
> Do we have to use this release when we test our maven plugins?
>
> Snjeza
>
> Denis Golovin wrote:
>> Current trunk continuous build fails, because of
>>
>> org.jboss.tools.maven.sourcelookup.core declares dependency to
>> org.eclipse.m2e.core;bundle-version="[1.0.0,1.1.0)";visibility:=reexport.
>> But latest target platform has only
>> http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.SR2/latest/plugins/org.eclipse.m2e.core_1.1.0.20120320-0058.jar.
>>
>>
>> [ERROR] Internal error: java.lang.RuntimeException: "No solution found
>> because the problem is unsatisfiable.": ["Unable to satisfy dependency
>> from org.jboss.tools.maven.sourcelookup.core 1.3.0.qualifier to bundle
>> org.eclipse.m2e.jdt [1.0.0,1.1.0).", "Unable to satisfy dependency
>> from org.jboss.tools.maven.sourcelookup.core 1.3.0.qualifier to bundle
>> org.eclipse.m2e.core [1.0.0,1.1.0).", "Unable to satisfy dependency
>> from org.jboss.tools.maven.sourcelookup.core 1.3.0.qualifier to bundle
>> org.eclipse.m2e.maven.runtime [1.0.0,1.1.0).", "No solution found
>> because the problem is unsatisfiable."] -> [Help 1]
>> org.apache.maven.InternalErrorException: Internal error:
>> java.lang.RuntimeException: "No solution found because the problem is
>> unsatisfiable.": ["Unable to satisfy dependency from
>> org.jboss.tools.maven.sourcelookup.core 1.3.0.qualifier to bundle
>> org.eclipse.m2e.jdt [1.0.0,1.1.0).", "Unable to satisfy dependency
>> from org.jboss.tools.maven.sourcelookup.core 1.3.0.qualifier to bundle
>> org.eclipse.m2e.core [1.0.0,1.1.0).", "Unable to satisfy dependency
>> from org.jboss.tools.maven.sourcelookup.core 1.3.0.qualifier to bundle
>> org.eclipse.m2e.maven.runtime [1.0.0,1.1.0).", "No solution found
>> because the problem is unsatisfiable."]
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>> 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: "No solution found because the
>> problem is unsatisfiable.": ["Unable to satisfy dependency from
>> org.jboss.tools.maven.sourcelookup.core 1.3.0.qualifier to bundle
>> org.eclipse.m2e.jdt [1.0.0,1.1.0).", "Unable to satisfy dependency
>> from org.jboss.tools.maven.sourcelookup.core 1.3.0.qualifier to bundle
>> org.eclipse.m2e.core [1.0.0,1.1.0).", "Unable to satisfy dependency
>> from org.jboss.tools.maven.sourcelookup.core 1.3.0.qualifier to bundle
>> org.eclipse.m2e.maven.runtime [1.0.0,1.1.0).", "No solution found
>> because the problem is unsatisfiable."]
>> at
>> org.eclipse.tycho.p2.impl.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:79)
>>
>> at
>> org.eclipse.tycho.p2.impl.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:83)
>>
>> at
>> org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:118)
>>
>> at
>> org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:76)
>>
>> at
>> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:445)
>>
>> at
>> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:422)
>>
>> at
>> org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:98)
>>
>> at
>> org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:61)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:273)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>> ... 11 more
>>
>> Denis
>>
>> On 05/02/2012 10:07 AM, Nick Boldt wrote:
>>> Yes, there is: you run the update site aggregation build locally.
>>>
>>> You either get a build, or an error.
>>>
>>> If content on disk is newer than remote, site will be built from local
>>> .m2 repo.
>>>
>>> This is how I've been building/testing Central& all the aggregate sites
>>> (JBT Core, JBT SOA, webtools, JBT Core tests, JBT SOA tests, JBDS Core,
>>> JBDS Extras, JBDS SOA), locally for months.
>>>
>>> N
>>>
>>> On 05/02/2012 11:07 AM, Max Rydahl Andersen wrote:
>>>>> No, because the build is an aggregation designed to pull from
>>>>> upstream.
>>>> hmm....that sucks.
>>>>
>>>> so no way for devs to actually test their local files such as
>>>> site.xml for correctness ;(
>>>>
>>>> /max
>>>>
>>>>> See also this pom, which explains how to build the other aggregates
>>>>> and
>>>>> skip unneeded download steps:
>>>>>
>>>>> http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/pom.xml
>>>>>
>>>>>
>>>>> On 04/30/2012 07:59 AM, Snjezana Peco wrote:
>>>>>> This command downloads components from the JBoss site.
>>>>>> Is there any command that uses components that are built locally?
>>>>>>
>>>>>> Snjeza
>>>>>>
>>>>>> Mickael Istria wrote:
>>>>>>> When you got a CI build OK for the component your worked on, try
>>>>>>> that:
>>>>>>>
>>>>>>> cd build/aggregate/site/
>>>>>>> mvn clean install -P jbosstools-nightly-staging-composite
>>>>>>>
>>>>>>> It will create the aggregated site locally using the latest CI
>>>>>>> builds
>>>>>>> for all components. If you did something wrong in site.xml, it fails
>>>>>>> quickly.
>>>>>>>
>>>>>>> On 04/29/2012 09:47 PM, Snjezana Peco wrote:
>>>>>>>> I have built locally the whole JBoss Tools without any error. I
>>>>>>>> have used:
>>>>>>>>
>>>>>>>> mvn clean install -DskipTests
>>>>>>>>
>>>>>>>> How can I check if site.xml is valid?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Snjeza
>>>>>>>>
>>>>>>>> Nick Boldt wrote:
>>>>>>>>
>>>>>>>>> Found& fixed a typo in the aggregate/site/site.xml which was
>>>>>>>>> preventing it from finding the new feature.
>>>>>>>>>
>>>>>>>>> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Next spin should be good - also running locally to verify.
>>>>>>>>>
>>>>>>>>> Devs, when you're adding new features, please ensure your
>>>>>>>>> changes to
>>>>>>>>> shared components (eg., build/aggregate/site/site.xml) build
>>>>>>>>> locally
>>>>>>>>> before committing!
>>>>>>>>>
>>>>>>>>> Thanks in advance,
>>>>>>>>>
>>>>>>>>> Nick
>>>>>>>>>
>>>>>>>>> On 04/27/2012 06:30 PM, Snjezana Peco wrote:
>>>>>>>>>
>>>>>>>>>> The source lookup feature builds locally.
>>>>>>>>>>
>>>>>>>>>> Snjeza
>>>>>>>>>>
>>>>>>>>>> Max Andersen wrote:
>>>>>>>>>>
>>>>>>>>>>> Nick - forgot to mention snjezana will be adding sourcelookup
>>>>>>>>>>> to the
>>>>>>>>>>> maven component as a separate feature.
>>>>>>>>>>> If you spot something problematic dependency/build wise then
>>>>>>>>>>> let me
>>>>>>>>>>> know.
>>>>>>>>>>> /max (sent from my phone)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> jbosstools-dev mailing list
>>>>>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> jbosstools-dev mailing list
>>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>>>>
>>>>>>> --
>>>>>>> Mickael Istria
>>>>>>> Eclipse developer at JBoss, by Red Hat<http://www.jboss.org/tools>
>>>>>>> My blog<http://mickaelistria.wordpress.com> - My Tweets
>>>>>>> <http://twitter.com/mickaelistria>
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> jbosstools-dev mailing list
>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>> _______________________________________________
>>>>>> jbosstools-dev mailing list
>>>>>> jbosstools-dev at 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 at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at 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