Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] Dependency resolution problem 
From your original question it is not clear which m2e version has the
problem. If the problem only exists in older versions of m2e or cannot
be reproduced with m2e 1.5 (snapshot) then just update m2e, there is no
point troubleshooting old m2e versions.

If the problem can be reproduced with current m2e 1.5 snapshot, then you
will need to setup m2e development environment as explained in [1]. When
you start m2e in self-hosted mode, i.e. from m2e development workspace,
you can debug project dependency resolution through m2e, maven and
aether code. ProjectRegistryManager#readProjectWithDependencies is where
m2e calls into Maven during workspace project dependency resolution,
there is where I'd start debugging.


[1] http://wiki.eclipse.org/M2E_Development_Environment

--
Regards,
Igor

On 2014-02-28, 9:04, László Váradi wrote:

Hi Igor!

I will try to setup a small project... but it is tricky... I think it
won't work, and the project is not open sourced... However, If you can
tell me hints what to debug, I'll try to remote debug the failing
workspaces...

Best regards,

-- Vazul


2014-02-28 14:32 GMT+01:00 Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>>:

    Please provide small standalone example and exact steps to reproduce
    the problem and I'll have a look.

    Also, this list is meant for m2e development discussions so please
    use m2e-user list for this kind of questions in the future.



    On February 28, 2014 8:25:47 AM EST, "László Váradi"
    <laszlo.varadi@xxxxxxxxx <mailto:laszlo.varadi@xxxxxxxxx>> wrote:
     >Hi!
     >
     >We have some dependency resolution problem. We have a project with a
     >lot of
     >dependencies, mostly transitively, and we have dependency for jaxws
     >artifacts:
     >...
     ><dependency>
     > <groupId>javax.xml.ws <http://javax.xml.ws></groupId>
     ><artifactId>jaxws-api</artifactId>
     > </dependency>
     ><dependency>
     ><groupId>com.sun.xml.ws <http://com.sun.xml.ws></groupId>
     > <artifactId>jaxws-rt</artifactId>
     ></dependency>
     ><dependency>
     > <groupId>com.sun.xml.ws <http://com.sun.xml.ws></groupId>
     ><artifactId>jaxws-local-transport</artifactId>
     > <optional>true</optional>
     ></dependency>
     ><dependency>
     > <groupId>javax.jws</groupId>
     ><artifactId>jsr181-api</artifactId>
     ></dependency>
     > </dependencies>
     >
     >Our team has 6 people, 3 of them have problems, 3 of them have no
     >problems.
     >The 3 people having problems, has different version of m2e (1.2 and
     >1.4),
     >but each version contains maven 3.0.4 embedded (Apache Maven 3.0.4
     >(r1232337; 2012-01-17 09:44:56+0100)).
     >
     >The dependency:tree produces normal output at each people using the
     >embedded maven:
     >
     >[INFO] +- javax.xml.ws:jaxws-api:jar:2.2.11:compile
     >[INFO] |  +- javax.xml.bind:jaxb-api:jar:2.1:provided
     >[INFO] |  |  \- javax.xml.stream:stax-api:jar:1.0-2:provided (scope
     >managed
     >from compile)
     >[INFO] |  +- javax.xml.soap:javax.xml.soap-api:jar:1.3.5:compile
     >[INFO] |  \- javax.annotation:javax.annotation-api:jar:1.2-b03:runtime
     >[INFO] +- com.sun.xml.ws:jaxws-rt:jar:2.2.8-promoted-b146:compile
     >[INFO] |  +- javax.xml.soap:saaj-api:jar:1.3.4:compile
     >[INFO] |  +- com.sun.xml.bind:jaxb-impl:jar:2.2.7-b41:compile
     >[INFO] |  +- com.sun.xml.ws:policy:jar:2.3.1:compile
     >[INFO] |  +- org.glassfish.gmbal:gmbal-api-only:jar:3.1.0-b001:compile
     >[INFO] |  |  \-
     >org.glassfish.external:management-api:jar:3.0.0-b012:compile
     >[INFO] |  +- org.jvnet.staxex:stax-ex:jar:1.7.1:compile
     >[INFO] |  +- com.sun.xml.stream.buffer:streambuffer:jar:1.5:compile
     >[INFO] |  +- org.jvnet.mimepull:mimepull:jar:1.8:compile
     >[INFO] |  +- com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
     >[INFO] |  +- org.glassfish.ha:ha-api:jar:3.1.8:compile
     >[INFO] |  \- com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.9:compile
     >[INFO] |     \- org.jvnet:mimepull:jar:1.4:compile
     >[INFO] +- com.sun.xml.ws <http://com.sun.xml.ws>:
     >jaxws-local-transport:jar:2.2.8-promoted-b146:compile
     >[INFO] +- javax.jws:jsr181-api:jar:1.0-MR1:compile
     >
     >However, in the Dependency Hierarchy view, 3 of us has this:
     >
     >[image: Szövegközi kép 1]
     >
     >And who has no problems, he can see this:
     >
     >[image: Szövegközi kép 2]
     >
     >We had problems with aether version 1.11, but each embedded maven
     >contains
     >1.13.1 of aether.
     >
     >Do anybody faced such problems? What should we try to solve this?
     >
     >Best regards,
     >
     >-- Vazul
     >
     >
     >------------------------------------------------------------------------
     >
     >_______________________________________________
     >m2e-dev mailing list
     >m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
     >https://dev.eclipse.org/mailman/listinfo/m2e-dev

    --
    Sent from my Android device with K-9 Mail. Please excuse my brevity.




--
"Tőled tudják, hogy testvérek vagyunk?"
http://www.youtube.com/watch?feature=player_detailpage&v=qw1R794sutQ#t=2765s

Back to the top