Thanks Igor,
I have no problem with this. Can you see any problems with me disabling the
workspace resolution? I want maven based configuration to run things,
including Eclipse development time classpaths.

Best regards
Seref


On Mon, Sep 3, 2012 at 12:26 PM, Igor Fedorenko <[email protected]> wrote:

> m2e does not support workspace resolution for classified dependencies.
> As a workaround, you need to install these dependencies to local
> repository and make sure source project is not present in workspace.
>
> I'll be explaining this and other limitations m2e currently has during
> my eclipsecon eu talk [1], if you are interested to know why.
>
>
> [1] http://www.eclipsecon.org/**europe2012/sessions/m2e-**
> exercise-mixing-oil-and-water<http://www.eclipsecon.org/europe2012/sessions/m2e-exercise-mixing-oil-and-water>
>
> --
> Regards,
> Igor
>
>
> On 12-09-03 5:18 AM, Seref Arikan wrote:
>
>> Greetings,
>> I have project A which pulls dependencies from an Eclipse P2 repo via
>> Tycho maven plugin, and it packages these dependencies with emflib
>> classifier during packaging. Project A's pom has eclipse-plugin packaging.
>> Project B is the master pom container, that declares a dependency on A
>> as follows;
>>
>>
>> <dependencies>
>>        <dependency>
>>            <groupId>com.arikan</groupId>
>>            <artifactId>p2tests</**artifactId>
>>            <version>0.0.1</version>
>>            <classifier>emflib</**classifier>
>>        </dependency>
>>    </dependencies>
>>
>> Finally project C declares B as its parent, and uses classes from the
>> repackaged jar from A.
>>
>> The problem is, the classes required in C is not resolved into Eclipse
>> project's class path for C when Resolve dependencies from workspace
>> projects is checked. So m2e is not checking the local repository (which
>> has the required jar). mvn compile from terminal for project C works fine.
>>
>> Likewise, if Resolve dependencies is checked for project B, then no
>> matter what I write into classifer, I don't get an error in Eclipse,
>> that is, it does not check the repository for the classifier.
>> Would I have any trouble if I keep Resolve dependencies from
>> workspace... unchecked? I'd like to run everything based on Maven
>> anyway, for other teams who would use my code base and would not use
>> Eclipse.
>> As a secondary question: am I getting something wrong here?
>>
>> This is maven 3, with JDK 1.7 under 64 bit Ubuntu 12.04, using Eclipse
>> Indigo.
>>
>> Kind regards
>> Seref
>>
>>
>>
>> ______________________________**_________________
>> m2e-users mailing list
>> [email protected]
>> https://dev.eclipse.org/**mailman/listinfo/m2e-users<https://dev.eclipse.org/mailman/listinfo/m2e-users>
>>
>>  ______________________________**_________________
> m2e-users mailing list
> [email protected]
> https://dev.eclipse.org/**mailman/listinfo/m2e-users<https://dev.eclipse.org/mailman/listinfo/m2e-users>
>
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to