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 2006/03/22 07:20:13 UTC
Migration complete: changes, changelog, jxr and surefire report plugins
Hi,
The migration of these plugins from mojo to the Maven sandbox is complete.
I will work on JXR and Surefire to get them released and promoted, soon.
The others require more work, so if you are able to contribute, please do!
I have not yet moved the dependency plugin - since to date Brian has
worked solely on that, he can commit it to the plugins repo after his
account is created (CLA is already filed).
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Migration complete: changes, changelog, jxr and surefire report
plugins
Posted by Brett Porter <br...@apache.org>.
Right... I was referring to the m1 version :)
Edwin Punzalan wrote:
>
> fyi, I've seen changelog and it already uses maven-scm
>
>
> Brett Porter wrote:
>> I've been in favour of this since day 1. JXR, for example, is almost
>> entirely shared.
>>
>> For changelog, this will happen by refactoring to Maven SCM. For
>> changes/jira/announcement, it will be by refactoring around
>> issue-management library in the sandbox.
>>
>> The Surefire report looks the same, but is completely different. That
>> said, m1 could use it as a replacement for the JSL based junit-report.
>> I'll leave that up to you :)
>>
>> It's essential that the m1 plugins be refactored around java code for
>> this to be feasible though. That's the reason JXR was so straight
>> forward.
>>
>> Cheers,
>> Brett
>>
>> Arnaud HERITIER wrote:
>>
>>> I'm seeing that we are duplicating/adapting code between plugins in
>>> m1 and
>>> m2.
>>> Can't we try to create some shared libraries to use them in both
>>> plugins ?
>>> We could we create them ?
>>>
>>> Is it interesting ?
>>>
>>> Arnaud
>>>
>>> On 3/22/06, Brett Porter <br...@apache.org> wrote:
>>>
>>>> Hi,
>>>>
>>>> The migration of these plugins from mojo to the Maven sandbox is
>>>> complete.
>>>>
>>>> I will work on JXR and Surefire to get them released and promoted,
>>>> soon.
>>>> The others require more work, so if you are able to contribute,
>>>> please do!
>>>>
>>>> I have not yet moved the dependency plugin - since to date Brian has
>>>> worked solely on that, he can commit it to the plugins repo after his
>>>> account is created (CLA is already filed).
>>>>
>>>> - Brett
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Migration complete: changes, changelog, jxr and surefire report
plugins
Posted by Edwin Punzalan <ep...@exist.com>.
fyi, I've seen changelog and it already uses maven-scm
Brett Porter wrote:
> I've been in favour of this since day 1. JXR, for example, is almost
> entirely shared.
>
> For changelog, this will happen by refactoring to Maven SCM. For
> changes/jira/announcement, it will be by refactoring around
> issue-management library in the sandbox.
>
> The Surefire report looks the same, but is completely different. That
> said, m1 could use it as a replacement for the JSL based junit-report.
> I'll leave that up to you :)
>
> It's essential that the m1 plugins be refactored around java code for
> this to be feasible though. That's the reason JXR was so straight forward.
>
> Cheers,
> Brett
>
> Arnaud HERITIER wrote:
>
>> I'm seeing that we are duplicating/adapting code between plugins in m1 and
>> m2.
>> Can't we try to create some shared libraries to use them in both plugins ?
>> We could we create them ?
>>
>> Is it interesting ?
>>
>> Arnaud
>>
>> On 3/22/06, Brett Porter <br...@apache.org> wrote:
>>
>>> Hi,
>>>
>>> The migration of these plugins from mojo to the Maven sandbox is complete.
>>>
>>> I will work on JXR and Surefire to get them released and promoted, soon.
>>> The others require more work, so if you are able to contribute, please do!
>>>
>>> I have not yet moved the dependency plugin - since to date Brian has
>>> worked solely on that, he can commit it to the plugins repo after his
>>> account is created (CLA is already filed).
>>>
>>> - Brett
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Migration complete: changes, changelog, jxr and surefire report
plugins
Posted by Brett Porter <br...@apache.org>.
I've been in favour of this since day 1. JXR, for example, is almost
entirely shared.
For changelog, this will happen by refactoring to Maven SCM. For
changes/jira/announcement, it will be by refactoring around
issue-management library in the sandbox.
The Surefire report looks the same, but is completely different. That
said, m1 could use it as a replacement for the JSL based junit-report.
I'll leave that up to you :)
It's essential that the m1 plugins be refactored around java code for
this to be feasible though. That's the reason JXR was so straight forward.
Cheers,
Brett
Arnaud HERITIER wrote:
> I'm seeing that we are duplicating/adapting code between plugins in m1 and
> m2.
> Can't we try to create some shared libraries to use them in both plugins ?
> We could we create them ?
>
> Is it interesting ?
>
> Arnaud
>
> On 3/22/06, Brett Porter <br...@apache.org> wrote:
>> Hi,
>>
>> The migration of these plugins from mojo to the Maven sandbox is complete.
>>
>> I will work on JXR and Surefire to get them released and promoted, soon.
>> The others require more work, so if you are able to contribute, please do!
>>
>> I have not yet moved the dependency plugin - since to date Brian has
>> worked solely on that, he can commit it to the plugins repo after his
>> account is created (CLA is already filed).
>>
>> - Brett
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Migration complete: changes, changelog, jxr and surefire report plugins
Posted by Arnaud HERITIER <ah...@gmail.com>.
I'm seeing that we are duplicating/adapting code between plugins in m1 and
m2.
Can't we try to create some shared libraries to use them in both plugins ?
We could we create them ?
Is it interesting ?
Arnaud
On 3/22/06, Brett Porter <br...@apache.org> wrote:
>
> Hi,
>
> The migration of these plugins from mojo to the Maven sandbox is complete.
>
> I will work on JXR and Surefire to get them released and promoted, soon.
> The others require more work, so if you are able to contribute, please do!
>
> I have not yet moved the dependency plugin - since to date Brian has
> worked solely on that, he can commit it to the plugins repo after his
> account is created (CLA is already filed).
>
> - Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>