Hi Paul
I write test automation and try to stick to a solid design. I find others
break solid design principles so having a scope will prevent people
from breaking some basic principles.
For example, if using Selenium I've seen multiple people expose WebElement
in a public method (that should be
I suggest to start a [VOTE] for it as I did last year for other plugins.
There's a page that describes the actions[1] (I hope it is complete by now)
I would not go for a 3.0, just leave it as it is and spend your energy on other
issues.
thanks,
Robert
[1] https://maven.apache.org/developers/reti
Thanks!
On Thu, Jan 23, 2020 at 3:16 AM Hervé BOUTEMY wrote:
>
> maven-doxia-book-renderer and maven-doxia-book-maven-plugin Git repositories
> created and filled with history
>
> Regards,
>
> Hervé
>
> Le jeudi 23 janvier 2020, 09:01:08 CET Hervé BOUTEMY a écrit :
> > for DOXIATOOLS-54, just com
INFRA issue created:
https://issues.apache.org/jira/browse/INFRA-19755
Le dimanche 19 janvier 2020, 20:56:23 CET Hervé BOUTEMY a écrit :
> As discussed recently, we have multiple obsolete Git repositories from old
> projects or read-only svn2git, that are confusing for users: we should
> archive t
maven-doxia-book-renderer and maven-doxia-book-maven-plugin Git repositories
created and filled with history
Regards,
Hervé
Le jeudi 23 janvier 2020, 09:01:08 CET Hervé BOUTEMY a écrit :
> for DOXIATOOLS-54, just commit on
> https://github.com/apache/maven-doxia-linkcheck
>
> for DOXIA-64, dox
for DOXIATOOLS-54, just commit on
https://github.com/apache/maven-doxia-linkcheck
for DOXIA-64, doxia-book-* are the 2 components not yet migrated since nobody
seemed to care: see the tracking of Git migration [1]
I'll try to reuse my migration script to prepare the 2 components dedicated Git
r
