You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@maven.apache.org by Abel Muiño <am...@gmail.com> on 2009/02/24 19:32:32 UTC

Alignment of maven 3.0 dependencies and Eclipse IP approved libraries

Hello!

Eclipse IAM will start integrating the alpha builds (the goal is adapt to
the changes as they come along).

The first step for that is getting IP clearance from Eclipse, so we have
submitted most of the alpha-2 dependencies quite successfully.

However, we have been asked if it would be possible to replace a few of them
with versions that have been already approved by the Eclipse legal team.

Since m2e is also an Eclipse project, I think that it could be interesting
to align the dependencies (when that's possible).

Let me know if that is interesting and I'll get back to you with the
details.

Yours,
  Abel Muiño, Eclipse IAM project lead.

-----
http://www.linkedin.com/in/amuino Abel Mui&ntilde;o Vizcaino  -  
http://ramblingabout.wordpress.com http://ramblingabout.wordpress.com 
-- 
View this message in context: http://www.nabble.com/Alignment-of-maven-3.0-dependencies-and-Eclipse-IP-approved-libraries-tp22187681p22187681.html
Sent from the Maven Developers mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: refactoring Was: Alignment of maven 3.0 dependencies and Eclipse IP approved libraries

Posted by Brett Porter <br...@apache.org>.

On 26/02/2009, at 6:17 AM, Jason van Zyl wrote:

>
> On 24-Feb-09, at 5:53 PM, Brett Porter wrote:
>
>>
>> On 25/02/2009, at 6:57 AM, Jason van Zyl wrote:
>>
>>>
>>> We actually don't know until the round of refactoring that's going  
>>> to happen starting next week. Myself, Benjamin, John, Oleg, and  
>>> Shane will be doing the lion's share of the refactoring in the  
>>> project builder, plugin manager, lifecycle executor and the  
>>> repository system so we don't know what exactly will work as  
>>> expected and how that will effect changes in plexus.
>>
>> Are you going to post some details beforehand? I'm kind of  
>> interested in fixing the reporting mess.
>>
>
> Kohsuke is going to be at the meetup and I plan to address the idea  
> or reporting in Hudson and in Maven. There is a proliferation of  
> duplicated reporting plugins and the crux of the issue is data  
> generation versus document generation. Maven itself needs to move  
> toward the production of data. Then anything can pick up the data  
> and generate reports, or create trending information. But this whole  
> system needs to be decoupled from Maven's core so really anything  
> can be worked on independently which is what I'm trying to do with  
> Vincent and the separation of the rendering engine in XWiki. I plan  
> to give a presentation at the meetup on the XWiki rendering engine.

Yes, I'm fully in support of this. I did this back to front  
originally, trying to replicate M1 functionality and add data point  
handling to the reporting-api later, but it never quite fit without  
being there from the outset. Unfortunately now the rendering part that  
really isn't core is wound in too tightly because there was no way to  
do that from within the site plugin where it really belongs. I'm  
actually way more interested in getting involved in data point  
tracking than rendering now TBH :)

Anyway, I just want to make sure all this stuff cycles through the  
list since that's really key to your objective of getting more people  
involved. I know my face time/phone time/IRC time is becoming more  
limited by the day :)

Thanks,
Brett

--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org