Re: [tycho-user] Project generated from tycho-eclipse-plugin-archetype i

[Doug Schaefer <dschaefer@xxxxxxx>]

On 11/12/2013, 4:34 PM, "Igor Fedorenko" <igor@xxxxxxxxxxxxxx> wrote:

>
>
>On 11/12/2013, 4:15 PM, Doug Schaefer wrote:
>> On a bit of a tangent, I¹ve always felt we needed some sort of
>> virtualization layer that lets us get information for the project from
>> other sources than a .project file. That way, the pom.xml file could be
>>a
>> replacement for .project and we wouldn¹t need to worry about this.
>>
>> BTW, I think the .class file is different. We probably should be
>>creating
>> a container there just like the PDE container to pull dependency
>> information from the poms as well.
>>
>
>Not sure I follow. Assuming you mean .classpath, what classpath
>container do you expect to see there? For Tycho projects, workspace
>dependencies are managed by PDE, so these projects have "Plugin
>Dependencies" container that is populated based on information from
>bundle manifest. For plain m2e projects, there is "Maven Dependencies"
>container populated from pom.xml.

Yes sorry, .classpath. And, cool, you already have that. I have to admit I
haven’t tried m2e really yet. But I am concerned our maven builds are so
much different than our workspace builds especially as I cheat and have
the odd antrun into our poms. Would m2e help me there?

BTW, the .project thing is my real question. We have the same problem with
CDT workspaces where the .project file is overly constraining, especially
compared to Visual Studio and Xcode.

Thanks!
Doug.

>
>--
>Regards,
>Igor
>
>
>> Just a crazy thought and wonder if that would help here.
>> Doug.
>>
>> On 11/12/2013, 1:57 PM, "Steinar Bang" <sb@xxxxxx> wrote:
>>
>>>>>>>> Igor Fedorenko <igor@xxxxxxxxxxxxxx>:
>>>
>>>> Tycho projects do not use dependency information from pom.xml (at
>>>>least
>>>> not directly). Instead, dependencies are derived from OSGi/Eclipse
>>>> project metadata, things like OSGi bundle manifest
>>>
>>> Thanks!
>>>
>>> I opened the MANIFEST.MF of the failing httpcomposer.test project, and
>>> then:
>>> - selected the "Dependencies" tab
>>> - selected the failing org.junit package
>>> - clicked on "Properties..."
>>> - Selected the 4.10.0 version of JUnit in "Available versions to match"
>>> - clicked on "Match", and the "Minimum Version" field was set to
>>>"4.10.0"
>>> - clicked on ok
>>> - saved the MANIFEST.MF, and the project changed from red to not-red
>>>    (ie. the error went away)
>>>
>>>> and Eclipse feature.xml. Inside Eclipse workspace Tycho projects
>>>> dependency resolution is managed by PDE (not m2e) and dependencies are
>>>> additionally constraint by PDE workspace target platform.
>>>
>>> Right.  But when I ran archetype:create from the command line, it
>>> probably picked the newest JUnit from .m2/repository, without any
>>>regard
>>> for what's in the OSGi runtime...?
>>>
>>> Anyway, now it builds (without the .project and .classpath files being
>>> committed to git).
>>>
>>> Thanks again!
>>>
>>> _______________________________________________
>>> tycho-user mailing list
>>> tycho-user@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>>
>> _______________________________________________
>> tycho-user mailing list
>> tycho-user@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>>
>_______________________________________________
>tycho-user mailing list
>tycho-user@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/tycho-user