You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2009/02/25 02:53:11 UTC

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

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.

>
>
> I'll be posting shortly about a dev meetup around EclipseCon where  
> myself, Oleg and Shane will be giving some presentations on the core  
> architecture for the primary components to try and get people  
> involved, but until then we're just going to be working full tilt to  
> make 3.x a replacement for 2.x. Until we're finished I don't know  
> what the core will look like exactly and doing any license work  
> before that would be premature.

For those of us not going to be anywhere near EclipseCon, can you post  
details here first?

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


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

Posted by Jason van Zyl <jv...@sonatype.com>.
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.
>

Full details will be coming in a day or two. Just in the middle of  
some refactoring. The reporting cannot be fixed until I finish  
refactoring the plugin manager.

I plan to fully extract Doxia and create a separate execution  
environment for reporting. The Doxia can be an implementation, I am  
going to work on a version of reporting based on the XWiki rendering  
engine. But right now the plugin manager is too much of a mess to  
attempt anything. The primary refactoring the project builder, plugin  
manager and lifecycle executor are still required before anything  
significant can be added.

>>
>>
>> I'll be posting shortly about a dev meetup around EclipseCon where  
>> myself, Oleg and Shane will be giving some presentations on the  
>> core architecture for the primary components to try and get people  
>> involved, but until then we're just going to be working full tilt  
>> to make 3.x a replacement for 2.x. Until we're finished I don't  
>> know what the core will look like exactly and doing any license  
>> work before that would be premature.
>
> For those of us not going to be anywhere near EclipseCon, can you  
> post details here first?
>
> 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
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------

To do two things at once is to do neither.

  -—Publilius Syrus, Roman slave, first century B.C.


---------------------------------------------------------------------
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


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

Posted by Jesse McConnell <je...@gmail.com>.
>>>
>>> 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.

sounds promising, thinking I can make it to the meetings :)

---------------------------------------------------------------------
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 Jason van Zyl <jv...@sonatype.com>.
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.

>>
>>
>> I'll be posting shortly about a dev meetup around EclipseCon where  
>> myself, Oleg and Shane will be giving some presentations on the  
>> core architecture for the primary components to try and get people  
>> involved, but until then we're just going to be working full tilt  
>> to make 3.x a replacement for 2.x. Until we're finished I don't  
>> know what the core will look like exactly and doing any license  
>> work before that would be premature.
>
> For those of us not going to be anywhere near EclipseCon, can you  
> post details here first?
>
> 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
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------

People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more  
examples
you look at, the more general your framework will be.

   -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks


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