Re: [eclipse.org-architecture-council] Eclipse and Maven working group

["Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>]

Thanks Wayne,

I was about to suggest the same.

Antoine has already demonstrated some leadership on 
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=288644
which I find good, despite some pushback.

I haven't ever used Maven myself either, so I'm in the 
same boat as Wayne ... That I cannot really comment with 
authority. 

My feeling is that

  1.) Community wants a Maven Repo for Maven 2 -- waiting 
      for Maven3 / Tycho / Autoconverters won't work

  2.) Providing released bits only is sufficient - no need
      for I-builds or snapshot

  3.) Mavenizing the Release train makes most sense, since
      this allows converting version ranges in dependencies
      into explicit dependencies (which helps adopters).

  4.) Publishing on Maven Central would be desirable by
      the community, but it's not a short term solution 
      since Maven Central requires additional artifacts
      (Javadoc Jar's, Committer Lists) that we cannot suck
      out of thin air.

That being said, I feel like the simplest thign we can do
is move forward with b3 mavenizing the Helios Repo, and 
serve from Eclipse.org as suggested in 
   https://bugs.eclipse.org/bugs/show_bug.cgi?id=312656

Again, these statements are my personal impression, which
May be totally bogus since I haven't used Maven (thus I
don't publish these on the bug). 

So... Maven users out there, please step up! From Wayne's
statement I take that the Foundation is willing to put 
some resources into this. Right?

Thanks,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
direct +43.662.457915.85  fax +43.662.457915.6

-----Original Message-----
From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf
Of Wayne Beaton
Sent: Dienstag, 16. November 2010 16:56
To: eclipse.org-architecture-council
Subject: [eclipse.org-architecture-council] Eclipse and Maven working
group

Greetings fellow Architecture Council members.

I assume that many/most of you have been following Bug 283745 [1]. I
feel that this is a good opportunity for the Architecture Council to
demonstrate leadership.

There has been a lot of ideas presented and quite a bit of
back-and-forth on what we should do. I think we're at a point where the
AC should "grab the reigns" and put together a working group to come up
with best practices, specific recommendations, and a plan for what we
collectively should do for Maven. I really need to know what actions the
Foundation needs to take and what ongoing investment is going to be
required. I believe that the output for this initial exercise would be a
wiki page. I also think that we should add this to the next call's
agenda.

I am not knowledgeable enough about Maven myself to convincingly lead
this sort of effort. Can somebody else step up? Ideally, it'd be great
we could get two or three members to take ownership of this.

Thanks,

Wayne

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=283745

--
Wayne Beaton, The Eclipse Foundation
http://www.eclipse.org
--
Join me at EclipseCon 2011
http://eclipsecon.org/

_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-counci
l

IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation.  To be permanently removed from this list, you
must contact emo@xxxxxxxxxxx to request removal.