|
|
|
Re: Emf libraries to Central Maven Repository [message #431377 is a reply to message #431311] |
Wed, 08 July 2009 09:31 |
Ed Merks Messages: 33218 Registered: July 2009 |
Senior Member |
|
|
Johan,
Comments below.
Johan Vogelzang wrote:
> Well, I would like to step up, but don't know were to begin...
Welcome to my world. :-P
>
> The ideal solution, for as well Eclipse projects as for the Java
> projects that uses them is as follows:
> 1- Setup a central Maven repository within the walls of the
> org.eclipse environment. Only Eclipse projects (org.eclipse.*) are
> allowed to deploy to this repository. Lets name it the Eclipse Maven
> Repository.
> 2- Let the Eclipse Maven Repository automatically synchronize with the
> Central Maven Repository. This is the preferred way by Maven, see for
> more details:
> http://maven.apache.org/guides/mini/guide-central-repository -upload.html
> 3- For individual Eclipse projects (for which its appropriate) its
> only necessary to deploy their released libraries to the Eclipse Maven
> Repository. The automatic synchronization process will take care of
> the rest. Maven has support for this step, see:
> http://maven.apache.org/plugins/maven-eclipse-plugin/to-mave n-mojo.html
That sounds very sensible.
>
> I suppose point 1- and 2- go beyond the scope of the EMF project. But
> I know that there are more Eclipse projects that have to wrestle this
> same problem. For instance the org.eclipse.xtext project deploys to a
> third party Maven repository. But Java projects in general don't want
> to rely on third party repositories. The only Maven repositories they
> can trust are the Central Maven Repository or mirrors of it.
It would be good to have a sensible strategy around this stuff. What
if, for example, a p2 repository could be automatically converted to a
maven repository and vice versa...
>
> I hope I made a bit clear that this is a common problem for Eclipse
> projects that want to publish their libraries as Maven artifacts to
> the world. The described solution provides a standard way to deal with
> it, so each Eclipse project could benefit from it.
There are two Maven projects at Eclipse. I'll take the opportunity at
the Architecture Council meeting tomorrow to ask about support for Maven...
> Regards,
> Johan.
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
|
|
|
|
Re: Emf libraries to Central Maven Repository [message #431534 is a reply to message #431512] |
Wed, 15 July 2009 13:38 |
Ed Merks Messages: 33218 Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------070209040908040404050602
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Johan,
There should be information in the minutes:
http://wiki.eclipse.org/Architecture_Council/Meetings
E.g., the July 9 minutes are there already.
Johan Vogelzang wrote:
> Ed,
>
> Thanks for taking the initiative. What can I do to keep me informed of
> the outcome of the next moth meeting? If more input about this issue
> is needed, let me know.
>
> Regards,
> Johan.
>
--------------070209040908040404050602
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Johan,<br>
<br>
There should be information in the minutes:
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.04726 seconds