Home » Modeling » UML2 » Dependency hell with org.eclipse.uml2.types and Maven(org.eclipse.uml2.types dependency in Maven Central is out-of-date)
| Dependency hell with org.eclipse.uml2.types and Maven [message #1737953] |
Thu, 14 July 2016 11:11  |
 Mark Linehan
Messages: 9
Registered: July 2014 |
Junior Member |
|
|
On Maven central, the latest entry for org.eclipse.uml2.types is version 2.0.0-v20140602-0749 from 2014. Besides the fact that this version is out-of-date, I get this Maven dependency error when I try to use it: "No versions available for org.eclipse.emf:ecore:jar:[2.10.0,3.0.0) within specified range". This happens even when I setup my pom.xml file to use the ecore version (2.3.0-v200706262000) that the uml2.types pom file declares as its dependency.
So the question is: why isn't the latest uml2.types available through Maven central? And how do I resolve this dependency issue?
Background: I am developing a web service that runs under Apache Tomcat and invokes some code that is built using EMF. Following Tomcat recommendations, I use Maven to build this web service. The Maven build worked fine until the emf code suddenly added a dependency on uml2.types. And I can't find a way to resolve that dependency.
Mark
|
|
|
| Re: Dependency hell with org.eclipse.uml2.types and Maven [message #1737956 is a reply to message #1737953] |
Thu, 14 July 2016 11:51  |
Ed Willink
Messages: 7655
Registered: July 2009 |
Senior Member |
|
|
<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi<br>
<br>
I think that my earlier reply still apllies.<br>
<br>
<i>My understanding is that provision of sensible Maven
distribution awaits support from Eclipse IT and that it is
dependent on resolution of incompatible version/persistence
policies wrt Eclipse and Maven repos. However since some
projects seem to do it, maybe it is just necessary to tell the
rest of us what to do. Certainly I have done, and plan to do,
exactly nothing until someone tells me what to do for OCL. I
suspect the same goes for UML and EMF and ...
</i><i><br>
</i><i>
</i><br>
I suspect that what you see in Maven is just there to tease you.<br>
<br>
Regards<br>
<br>
Ed Willink<br>
<br>
<br>
On 14/07/2016 12:11, Mark Linehan wrote:<br>
</div>
<blockquote cite="mid:nm7s0h$gjp$1@xxxxxxxxe.org" type="cite">On
Maven central, the latest entry for org.eclipse.uml2.types is
version 2.0.0-v20140602-0749 from 2014. Besides the fact that
this version is out-of-date, I get this Maven dependency error
when I try to use it: "No versions available for
org.eclipse.emf:ecore:jar:[2.10.0,3.0.0) within specified range".
This happens even when I setup my pom.xml file to use the ecore
version (2.3.0-v200706262000) that the uml2.types pom file
declares as its dependency.
<br>
<br>
So the question is: why isn't the latest uml2.types available
through Maven central? And how do I resolve this dependency
issue?
<br>
<br>
Background: I am developing a web service that runs under Apache
Tomcat and invokes some code that is built using EMF. Following
Tomcat recommendations, I use Maven to build this web service.
The Maven build worked fine until the emf code suddenly added a
dependency on uml2.types. And I can't find a way to resolve that
dependency.
<br>
</blockquote>
<p><br>
</p>
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;' />
<table style='border-collapse:collapse;border:none;'>
<tr>
<td style='border:none;padding:0px 15px 0px 8px'>
<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient">
<img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo" />
</a>
</td>
<td>
<p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;'>
This email has been checked for viruses by Avast antivirus software.
<br><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient">www.avast.com</a>
</p>
</td>
</tr>
</table>
<br />
</body>
</html>
|
|
| | |
| Re: Dependency hell with org.eclipse.uml2.types and Maven [message #1738033 is a reply to message #1738017] |
Fri, 15 July 2016 09:30 |
Ed Willink
Messages: 7655
Registered: July 2009 |
Senior Member |
|
|
Hi Ed
My, perhaps very flawed, recollection is that:
Maven/Tycho build and Maven publishing are separate activities. There
should be no problem with publishing a Buckminster build for Maven
consumption.
Maven requires published artefacts to have infinite longevity, so
Eclipse milestones cannot be published to Maven. There is some version
problem with releases too. Therefore Eclipse artefacts are not to be
published on Maven central rather the EF has set up/plans to set up its
own Maven distribution, details of which are eagerly awaited by many
project relengs. Potentially a relatively trivial standard add-on to the
existing P2 publishing should provide Maven publishing. IMHO it should
be possible for a default Maven visibility of the SimRel repo to be
provided without any participation by project releng's at all.
Regards
Ed Willink
On 15/07/2016 07:22, Ed Merks wrote:
> Mark,
>
> Many Eclipse projects have Maven builds, but they use it in
> conjunction with Tycho. One important thing that Tycho adds to the
> picture is that it can resolve p2 dependencies directly through the
> use of a .target file; the same one you can use with PDE to provision
> your target platform in the IDE. This avoids any need to publish
> things to Maven central. I really have no idea how one publishes
> things to Maven central. Once it a while someone else just does that
> for EMF, so it seems kind of a free-for-all to me.
>
> Perhaps that reflects badly on Maven, i.e., who is doing the
> publishing? How can you be sure someone doesn't publish something
> bogus? Why does it all need to be in Maven central?
>
> You could look at how Oomph's Maven/Tycho build is structured:
>
> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree
> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree/releng/org.eclipse.oomph.parent/pom.xml
>
> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree/releng/org.eclipse.oomph.releng/pom.xml
>
> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree/releng/org.eclipse.oomph.releng/org.eclipse.oomph.releng.target
>
>
> I'm not sure that will solve your problem, or if it's relevant if your
> not building plugins...
>
> On 14.07.2016 23:15, Mark Linehan wrote:
>> I'm currently stuck - dead in the water - on development of my Tomcat
>> service. Because of this dependency problem, which I did not create
>> and cannot fix. Who can I contact to get this problem addressed?
>>
>> I can't be the only person out there with this problem. And it
>> certainly reflects badly on both Eclipse and EMF.
>
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
|
|
|
| Re: Dependency hell with org.eclipse.uml2.types and Maven [message #1738039 is a reply to message #1738033] |
Fri, 15 July 2016 09:51 |
Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
Ed,
Comments below.
On 15.07.2016 11:30, Ed Willink wrote:
> Hi Ed
>
> My, perhaps very flawed, recollection is that:
>
> Maven/Tycho build and Maven publishing are separate activities.
Yes, of course.
> There should be no problem with publishing a Buckminster build for
> Maven consumption.
Yes, publishing published some artifacts. How its built is not relevant.
>
> Maven requires published artefacts to have infinite longevity, so
> Eclipse milestones cannot be published to Maven.
Once published, they would become infinitely long lived. So they could
technically be published, but it's probably not a good idea.
> There is some version problem with releases too.
Version problem?
> Therefore Eclipse artefacts are not to be published on Maven central
Yet some people clearly do. In fact it seems anyone can do that. So
something I never published can still be published by someone else. It
seems a bit sketchy to me.
> rather the EF has set up/plans to set up its own Maven distribution,
A Maven repository you mean?
> details of which are eagerly awaited by many project relengs.
> Potentially a relatively trivial standard add-on to the existing P2
> publishing should provide Maven publishing.
Well, p2 publishing is just creating an update site. Making that update
site available to the public is a separate step.
> IMHO it should be possible for a default Maven visibility of the
> SimRel repo to be provided without any participation by project
> releng's at all.
I imagine the information in the POMs is important... But perhaps it
could be synthesized from the p2 information.
>
> Regards
>
> Ed Willink
>
>
> On 15/07/2016 07:22, Ed Merks wrote:
>> Mark,
>>
>> Many Eclipse projects have Maven builds, but they use it in
>> conjunction with Tycho. One important thing that Tycho adds to the
>> picture is that it can resolve p2 dependencies directly through the
>> use of a .target file; the same one you can use with PDE to provision
>> your target platform in the IDE. This avoids any need to publish
>> things to Maven central. I really have no idea how one publishes
>> things to Maven central. Once it a while someone else just does that
>> for EMF, so it seems kind of a free-for-all to me.
>>
>> Perhaps that reflects badly on Maven, i.e., who is doing the
>> publishing? How can you be sure someone doesn't publish something
>> bogus? Why does it all need to be in Maven central?
>>
>> You could look at how Oomph's Maven/Tycho build is structured:
>>
>> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree
>> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree/releng/org.eclipse.oomph.parent/pom.xml
>>
>> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree/releng/org.eclipse.oomph.releng/pom.xml
>>
>> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree/releng/org.eclipse.oomph.releng/org.eclipse.oomph.releng.target
>>
>>
>> I'm not sure that will solve your problem, or if it's relevant if
>> your not building plugins...
>>
>> On 14.07.2016 23:15, Mark Linehan wrote:
>>> I'm currently stuck - dead in the water - on development of my
>>> Tomcat service. Because of this dependency problem, which I did not
>>> create and cannot fix. Who can I contact to get this problem addressed?
>>>
>>> I can't be the only person out there with this problem. And it
>>> certainly reflects badly on both Eclipse and EMF.
>>
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Dependency hell with org.eclipse.uml2.types and Maven [message #1738051 is a reply to message #1738039] |
Fri, 15 July 2016 11:45 |
Ed Willink
Messages: 7655
Registered: July 2009 |
Senior Member |
|
|
Hi
Inline
Regards
Ed Willink
On 15/07/2016 10:51, Ed Merks wrote:
> Ed,
>
> Comments below.
>
>
> On 15.07.2016 11:30, Ed Willink wrote:
>> Hi Ed
>>
>> My, perhaps very flawed, recollection is that:
>>
>> Maven/Tycho build and Maven publishing are separate activities.
> Yes, of course.
>> There should be no problem with publishing a Buckminster build for
>> Maven consumption.
> Yes, publishing published some artifacts. How its built is not relevant.
>>
>> Maven requires published artefacts to have infinite longevity, so
>> Eclipse milestones cannot be published to Maven.
> Once published, they would become infinitely long lived. So they
> could technically be published, but it's probably not a good idea.
>> There is some version problem with releases too.
> Version problem?
I may be confusing memory of an Apache problem with a Maven problem, but
I think there was a possibility that the Eclipse policy of advancing
versions at the start of a development cycle e.g. M1, rather than at the
end e.g. SR0 could lead to a different conclusion as to whether x.y.z
precedes or follows p.q.r.
>> Therefore Eclipse artefacts are not to be published on Maven central
> Yet some people clearly do. In fact it seems anyone can do that. So
> something I never published can still be published by someone else.
> It seems a bit sketchy to me.
>> rather the EF has set up/plans to set up its own Maven distribution,
> A Maven repository you mean?
Probably.
>> details of which are eagerly awaited by many project relengs.
>> Potentially a relatively trivial standard add-on to the existing P2
>> publishing should provide Maven publishing.
> Well, p2 publishing is just creating an update site. Making that
> update site available to the public is a separate step.
>> IMHO it should be possible for a default Maven visibility of the
>> SimRel repo to be provided without any participation by project
>> releng's at all.
> I imagine the information in the POMs is important... But perhaps it
> could be synthesized from the p2 information.
If necessary, I am happy to scatter a few POMs in my build tree. Just
tell me what to do.
>>
>> Regards
>>
>> Ed Willink
>>
>>
>> On 15/07/2016 07:22, Ed Merks wrote:
>>> Mark,
>>>
>>> Many Eclipse projects have Maven builds, but they use it in
>>> conjunction with Tycho. One important thing that Tycho adds to the
>>> picture is that it can resolve p2 dependencies directly through the
>>> use of a .target file; the same one you can use with PDE to
>>> provision your target platform in the IDE. This avoids any need to
>>> publish things to Maven central. I really have no idea how one
>>> publishes things to Maven central. Once it a while someone else
>>> just does that for EMF, so it seems kind of a free-for-all to me.
>>>
>>> Perhaps that reflects badly on Maven, i.e., who is doing the
>>> publishing? How can you be sure someone doesn't publish something
>>> bogus? Why does it all need to be in Maven central?
>>>
>>> You could look at how Oomph's Maven/Tycho build is structured:
>>>
>>> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree
>>> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree/releng/org.eclipse.oomph.parent/pom.xml
>>>
>>> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree/releng/org.eclipse.oomph.releng/pom.xml
>>>
>>> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree/releng/org.eclipse.oomph.releng/org.eclipse.oomph.releng.target
>>>
>>>
>>> I'm not sure that will solve your problem, or if it's relevant if
>>> your not building plugins...
>>>
>>> On 14.07.2016 23:15, Mark Linehan wrote:
>>>> I'm currently stuck - dead in the water - on development of my
>>>> Tomcat service. Because of this dependency problem, which I did not
>>>> create and cannot fix. Who can I contact to get this problem
>>>> addressed?
>>>>
>>>> I can't be the only person out there with this problem. And it
>>>> certainly reflects badly on both Eclipse and EMF.
>>>
>>
>>
>> ---
>> This email has been checked for viruses by Avast antivirus software.
>> https://www.avast.com/antivirus
>>
>
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
|
|
| |
Goto Forum:
Current Time: Fri Apr 19 14:49:48 GMT 2024
Powered by FUDForum. Page generated in 0.02265 seconds |
] 
Search
Help
Register
Login
Home
