[jbosstools-dev] [gitmigration] ACTION REQUIRED please respond back wether your project git repo is ok or not!

[Snjezana Peco]

On 11.10.2012 11:55, Max Rydahl Andersen wrote:
> weird - but since this just look like an internal compile error on the repo I would say it would be fixed when doing a fresh migration.

Right.

> I assume this error exist when importing the source into eclipse ?

Yes, it does.

Snjeza

> if not, then it must be because you got a newer/older build of the plugins in your .m2e repository that confuses mvn ?
>
> /max
>
> On 11 Oct 2012, at 11:38, Snjezana Peco <snjezana.peco at redhat.com> wrote:
>
>> No, it is not.
>> Now, I get the following error:
>>
>> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.15.0:co
>> mpile (default-compile) on project org.jboss.tools.central.test: Compilation fai
>> lure: Compilation failure:
>> [ERROR] C:\jbtgit\temp-jbosstools-central\central\tests\org.jboss.tools.central.
>> test\src\org\jboss\tools\central\test\CentralTest.java:[66,0]
>> [ERROR] editor = JBossCentralActivator.getJBossCentralEditor();
>> [ERROR] ^^^^^^^^^^^^^^^^^^^^^
>> [ERROR] The method getJBossCentralEditor(boolean) in the type JBossCentralActiva
>> tor is not applicable for the arguments ()
>> [ERROR] 1 problem (1 error)
>> [ERROR] -> [Help 1]
>>
>> The error doesn't exist on svn. The o.j.t.c.test plugins on svn and git aren't synchronized.
>>
>> Snjeza
>>
>> On 11.10.2012 11:20, Max Rydahl Andersen wrote:
>>>> I have tried portlet, birt, runtime, central and examples.
>>>>
>>>> Portlet, birt and runtime work correctly.
>>>> The examples build fails. Denis fixed it in the svn trunk.
>>>> The central build has a problem with building org.jboss.central.themes.feature.source. It works on the svn trunk.
>>> Is this the same error as Fred reported:
>>>
>>>
>>> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to sati
>>> sfy dependency from org.jboss.tools.project.examples 1.4.0.qualifier to bundle org.jboss.tools.seam.core 0.0.0.", "Unable to satisfy dependency from org.jboss.t
>>> ools.project.examples 1.4.0.qualifier to bundle org.jboss.tools.common 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.project.examples 1.4.0.qualif
>>> ier to bundle org.jboss.tools.portlet.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.project.examples 1.4.0.qualifier to bundle org.jboss.tool
>>> s.runtime.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.project.examples 1.4.0.qualifier to bundle org.jboss.tools.runtime.ui 0.0.0.", "No so
>>> lution found because the problem is unsatisfiable."]
>>>
>>> ?
>>>
>>> weird that should fail in gitrepo....should work equally fine assuming you build org.jboss.tools.runtime.ui before this.
>>>
>>> Michael - any idea why this is failing ?
>>>
>>>> When the changes from the svn trunk are added to git?
>>> I can do a rerun for specifc repos if needed. i'll wait a bit for last feedback and see if I can do one for i.e. examples tomorrow.
>>>
>>> /max
>>>
>>>> Snjeza
>>>>
>>>> On 10.10.2012 18:37, Max Rydahl Andersen wrote:
>>>>> Hi,
>>>>>
>>>>> If you have not yet taken a look at the temp-* repositories on https://github.com/jbosstools please do so ASAP
>>>>>
>>>>> If I haven't heard back a +1 or "hey - this works great, except for this and this" for the content of the repositories by Wednesday next week (17th)
>>>>> the git migration will be delayed/postponed *after* GA.
>>>>>
>>>>> Thus if you want to use git *now* is the time to go help verify the content of the repositories are sane.
>>>>>
>>>>> thank you!
>>>>> /max
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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