Re: Maven feature request

[Scott Wilson]

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 a private implementation detail). This
is just an example of horrible implementation I've seen multiple people do
without thinking. The new  scope will not prevent that however it
will prevent the following.

I've seen people create src/tst/java/helloworld/MyTest.java which accesses
a WebElement directly in their Junit / TestNG class. The new  scope
will prevent stuff like that from happening. What they should really do is
create src/main/java/helloworld/MyPage.java which implements the
functionality using WebElement, then get an instance of MyPage from their
src/tst/java/helloworld/MyTest.java.

That is just one obvious example but I've seen other poor implementations
using other dependencies which are as obvious what is good vs bad design
unless this principle is understood.

Scott



On Wed, Jan 22, 2020 at 11:43 PM Karl Heinz Marbaise 
wrote:

> Hi,
>
> On 23.01.20 00:59, Scott Wilson wrote:
> > *Hi Robert and devs*
> >
> >
> > *I have been using maven for a few years and I LOVE it!*
> >
> >
> > *I have a feature request.*
> >
> >
> > *(1) When adding a dependency to pom.xml the default scope is everywhere*
> >
> > *ie src/main/java/*
> >
> > *and src/tst/java/...*
> >
> >
> > *(2) When adding  as the scope then the dependency can ONLY be used
> > under src/tst/java...*
> >
> > *If referencing the dependency in src/main/java/... then it will not
> > compile* >
> >
> > *(3) My feature request:*
> >
> > *I want the exact opposite. I'd like a new scope called *
> >
> > *If the scope is  then the dependency can ONLY be used under
> > src/main/java/...*
> >
> > *If referencing the dependency in tst/main/java/ then it will not
> > compile*
>
> This would result in the problem that you neever can run / compile your
> unit- and integration tests cause something is missing on the classpath
> so in result your project would be unusable...
>
>
>
> >
> >
> > *I read up on scopes
> > (**
> https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
> > <
> https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
> >)
> > *and
> > AFAIK this is not currently supported, but I have a specific reason for
> > wanting this.
>
> It would be great if you could shared this with us
>
>
> Kind regards
> Karl Heinz Marbaise
>
>
> >
> >
> > *I'd really appreciate if someone can add that for me and let me know
> when
> > it's done.*
> >
> > *Please let me know if you have any questions.*
> >
> >
> > *Regards*
> >
> > *Scott Wilson*
> >
> > *http://linkedin.com/in/hockeyeh *
> >
>

Re: [maven-verifier-plugin] Thoughts on releasing new version

[Robert Scholte]

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/retirement-plan-plugins.html
On 12-1-2020 00:47:04, Sylwester Lachiewicz  wrote:
Hi,
thank you for this finding.
I've checked where we use that plugin and seams that we use
maven-invoker-plugin instead of this plugin.
Quicks scan on all maven project sources shows only 2 usages - 1 in Modello
and two cases in Maven integration tests.

I do not know how others, but we can quickly release just based on the
version based on Maven 3 and then retire plugin completely.
Or just vote to retire now and save time

Sylwester


pt., 10 sty 2020 o 07:56 Artem Krosheninnikov
artem.krosheninni...@gmail.com> napisał(a):

> Hello there,
>
> I was looking for a small task in maven area and found this page [1]
>
> I've looked through plugins [2] and decided to switch maven-verifier-plugin
> [3]
>
> After cloning I found out that in master minimum version is already set to
> 3. Also there are no open issues.
>
> There are some questions:
>
> 1) Is it reasonable to release a new version? Previous version was released
> in 2015, it has an outdated site.
> 2) If yes, is it reasonable to leverage Java version to 1.8?
>
> I've made a small PR with all things in one place [4], please have a look
> and let me know what you think.
>
> [1]
>
> https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies
> [2]
>
> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisites.html
> [3] https://github.com/apache/maven-verifier-plugin/
> [4] https://github.com/apache/maven-verifier-plugin/pull/1
> --
> Sincerely yours,
> Krosheninnikov Artem.
>

Re: Doxia test flakiness

[Elliotte Rusty Harold]

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 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
> > repositories and let you know
> >
> > Regards,
> >
> > Hervé
> >
> > [1]
> > https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration#GitMigratio
> > n-Migratinganaggregatortreeintoacollectionofgitrepos
> > Le mercredi 22 janvier 2020, 23:06:41 CET Elliotte Rusty Harold a écrit :
> > > I was hoping to fix these two issues:
> > >
> > > https://issues.apache.org/jira/browse/DOXIATOOLS-64
> > > https://issues.apache.org/jira/browse/DOXIATOOLS-54?filter=-1
> > >
> > > I sent a PR for one of these, but it turned out to be against the
> > > wrong repo. I know nothing about svn2git.
> > >
> > > On Wed, Jan 22, 2020 at 4:41 PM Hervé BOUTEMY 
> wrote:
> > > > On 4 Doxia Tools, 2 have been migrated: doxia-converter [1] and doxia-
> > > > linkcheck [2], with very little activity (no release in 2 years)
> > > > There are 2 remaining components: doxia-book-renderer and
> > > > doxia-book-maven-
> > > > plugin.
> > > >
> > > > Do you mean that you want to maintain these 2 components?
> > > > Do you want us to create 2 Git repositories? Once created, are you able
> > > > to
> > > > fill these with content filtered from doxia-tools svn2git mirror?
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > [1] https://github.com/apache/maven-doxia-converter
> > > >
> > > > [2] https://github.com/apache/maven-doxia-linkcheck
> > > >
> > > > Le mercredi 22 janvier 2020, 18:12:30 CET Elliotte Rusty Harold a écrit
> :
> > > > > Ping. Any progress on getting Doxia migrated into Github?
> > > > >
> > > > > On Mon, Dec 23, 2019 at 5:38 PM Elliotte Rusty Harold
> > > > >
> > > > >  wrote:
> > > > > > Anyone working on Doxia these days? If so, your review of
> > > > > > https://github.com/apache/maven-doxia-tools/pull/3 would be
> > > > > > appreciated. This PR effectively disables a flaky autogenerated
> > > > > > test.
> > > > > >
> > > > > > This was the best I could come up with on short notice to unblock
> > > > > > some
> > > > > > other bugs in Doxia. However if anyone can figure out how to fix the
> > > > > > autogenerated test instead that would be even better. Details at
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/DOXIATOOLS-64
> > > > > >
> > > > > > --
> > > > > > Elliotte Rusty Harold
> > > > > > elh...@ibiblio.org
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-- 
Elliotte Rusty Harold
elh...@ibiblio.org

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

Re: archiving obsolete Git repository

[Hervé BOUTEMY]

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 them, to get the same result as
> https://github.com/apache/maven-ant-plugin
> 
> Here is the list of such repositories:
> - https://github.com/apache/maven-plugins
> - https://github.com/apache/maven-shared
> - https://github.com/apache/maven-doxia-tools
> - https://github.com/apache/maven-pom
> - https://github.com/apache/maven-artifact
> - https://github.com/apache/maven-mercury
> - https://github.com/apache/maven-app-engine
> - https://github.com/apache/maven-repository-tools
> - https://github.com/apache/maven-resources
> - https://github.com/apache/maven-sandbox
> - https://github.com/apache/maven-doxia-ide
> 
> Any objection to archive any of them? Or any additional repository?
> 
> Regards,
> 
> Hervé
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org





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

Re: Doxia test flakiness

[Hervé BOUTEMY]

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, 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
> repositories and let you know
> 
> Regards,
> 
> Hervé
> 
> [1]
> https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration#GitMigratio
> n-Migratinganaggregatortreeintoacollectionofgitrepos
> Le mercredi 22 janvier 2020, 23:06:41 CET Elliotte Rusty Harold a écrit :
> > I was hoping to fix these two issues:
> > 
> > https://issues.apache.org/jira/browse/DOXIATOOLS-64
> > https://issues.apache.org/jira/browse/DOXIATOOLS-54?filter=-1
> > 
> > I sent a PR for one of these, but it turned out to be against the
> > wrong repo. I know nothing about svn2git.
> > 
> > On Wed, Jan 22, 2020 at 4:41 PM Hervé BOUTEMY  
wrote:
> > > On 4 Doxia Tools, 2 have been migrated: doxia-converter [1] and doxia-
> > > linkcheck [2], with very little activity (no release in 2 years)
> > > There are 2 remaining components: doxia-book-renderer and
> > > doxia-book-maven-
> > > plugin.
> > > 
> > > Do you mean that you want to maintain these 2 components?
> > > Do you want us to create 2 Git repositories? Once created, are you able
> > > to
> > > fill these with content filtered from doxia-tools svn2git mirror?
> > > 
> > > Regards,
> > > 
> > > Hervé
> > > 
> > > [1] https://github.com/apache/maven-doxia-converter
> > > 
> > > [2] https://github.com/apache/maven-doxia-linkcheck
> > > 
> > > Le mercredi 22 janvier 2020, 18:12:30 CET Elliotte Rusty Harold a écrit 
:
> > > > Ping. Any progress on getting Doxia migrated into Github?
> > > > 
> > > > On Mon, Dec 23, 2019 at 5:38 PM Elliotte Rusty Harold
> > > > 
> > > >  wrote:
> > > > > Anyone working on Doxia these days? If so, your review of
> > > > > https://github.com/apache/maven-doxia-tools/pull/3 would be
> > > > > appreciated. This PR effectively disables a flaky autogenerated
> > > > > test.
> > > > > 
> > > > > This was the best I could come up with on short notice to unblock
> > > > > some
> > > > > other bugs in Doxia. However if anyone can figure out how to fix the
> > > > > autogenerated test instead that would be even better. Details at
> > > > > 
> > > > > https://issues.apache.org/jira/browse/DOXIATOOLS-64
> > > > > 
> > > > > --
> > > > > Elliotte Rusty Harold
> > > > > elh...@ibiblio.org
> > > 
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org





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

Re: Doxia test flakiness

[Hervé BOUTEMY]

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 
repositories and let you know

Regards,

Hervé

[1] 
https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration#GitMigration-Migratinganaggregatortreeintoacollectionofgitrepos

Le mercredi 22 janvier 2020, 23:06:41 CET Elliotte Rusty Harold a écrit :
> I was hoping to fix these two issues:
> 
> https://issues.apache.org/jira/browse/DOXIATOOLS-64
> https://issues.apache.org/jira/browse/DOXIATOOLS-54?filter=-1
> 
> I sent a PR for one of these, but it turned out to be against the
> wrong repo. I know nothing about svn2git.
> 
> On Wed, Jan 22, 2020 at 4:41 PM Hervé BOUTEMY  wrote:
> > On 4 Doxia Tools, 2 have been migrated: doxia-converter [1] and doxia-
> > linkcheck [2], with very little activity (no release in 2 years)
> > There are 2 remaining components: doxia-book-renderer and
> > doxia-book-maven-
> > plugin.
> > 
> > Do you mean that you want to maintain these 2 components?
> > Do you want us to create 2 Git repositories? Once created, are you able to
> > fill these with content filtered from doxia-tools svn2git mirror?
> > 
> > Regards,
> > 
> > Hervé
> > 
> > [1] https://github.com/apache/maven-doxia-converter
> > 
> > [2] https://github.com/apache/maven-doxia-linkcheck
> > 
> > Le mercredi 22 janvier 2020, 18:12:30 CET Elliotte Rusty Harold a écrit :
> > > Ping. Any progress on getting Doxia migrated into Github?
> > > 
> > > On Mon, Dec 23, 2019 at 5:38 PM Elliotte Rusty Harold
> > > 
> > >  wrote:
> > > > Anyone working on Doxia these days? If so, your review of
> > > > https://github.com/apache/maven-doxia-tools/pull/3 would be
> > > > appreciated. This PR effectively disables a flaky autogenerated test.
> > > > 
> > > > This was the best I could come up with on short notice to unblock some
> > > > other bugs in Doxia. However if anyone can figure out how to fix the
> > > > autogenerated test instead that would be even better. Details at
> > > > 
> > > > https://issues.apache.org/jira/browse/DOXIATOOLS-64
> > > > 
> > > > --
> > > > Elliotte Rusty Harold
> > > > elh...@ibiblio.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org





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