Re: Official Maven Github Actions

2021-02-12 Thread Romain Manni-Bucau 
Side note: shrinkwrap has a loadSetting (no more 100% sure of the name)
method you can use in the code if -Dmy.setting is set so you can configure
it in surefire and tomee has some too in its Mvn wrapper IIRC so can be a
simpler way to align it all - maybe even using JMX to get JVM arg and
extract -gs/-s since it is a testing tool at the end.

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le ven. 12 févr. 2021 à 23:10, Cesar Hernandez  a
écrit :

> Thank you all for the feedback provided so far.
>
> I was not aware of Maven Wrapper coming in 3.7, and also the plain sh
> script seems to be right the approach the
> https://github.com/sdkman/sdkman-action took.
> I just ping Eddú to know his feedback on the sdkman-action since it's not
> even listed in the market and, from the context, I think that can easily
> pass the Verification requirement since it's hosted in the sdkman
> organization.
>
> As I wrote at the beginning of the thread, defining a specific maven
> version is just one of many other maven related actions. For example, I've
> found issues with the default settings.xml included in GitHub actions
> and shrinkwrap-resolve so I ended up using actions like
> whelk-io/maven-settings-xml-action and then migrated to the sh script
> approach Romain mentioned after Apache infra recommendation was to remove
> the usage to non verified actions.
>
> El vie, 12 feb 2021 a las 14:16, Andres Almiray ()
> escribió:
>
> > FWIW there’s an sdkman GHA in case you’d like to explore that option
> >
> > https://github.com/sdkman/sdkman-action
> >
> > Cheers
> > Andres
> >
> > Sent from my primitive tricorder
> >
> > > On 12 Feb 2021, at 20:52, Romain Manni-Bucau 
> > wrote:
> > >
> > > Hi César,
> > >
> > > Any interesting feature compared to using a plain sh script with
> sdkman?
> > > Looks like saner since it will enable you to setup java and maven
> > properly
> > > at the same stage which is the actual prerequisite of a maven build vs
> > > using multiple random actions.
> > > Did you investigate this option?
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Old Blog
> > >  | Github <
> > https://github.com/rmannibucau> |
> > > LinkedIn  | Book
> > > <
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> > >
> > >
> > >> Le ven. 12 févr. 2021 à 20:39, Robert Scholte 
> a
> > >> écrit :
> > >>
> > >> I'm only aware of MNG-6887.
> > >>
> > >> Robert
> > >>
> > >>
> > >> [1] https://issues.apache.org/jira/browse/MNG-6887
> > >> On 12-2-2021 19:40:24, Gary Gregory  wrote:
> > >> I've been wanting such an GH action myself!
> > >>
> > >> Gary
> > >>
> > >> On Fri, Feb 12, 2021 at 12:52 PM Cesar Hernandez
> > >> wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> The problems:
> > >>>
> > >>> Currently, the official Github actions for building and testing Java
> > with
> > >>> Maven [1] don't offer a way to specify the Maven version a workflow
> can
> > >>> use.
> > >>> Adding this support seems to be out of the scope of the
> > >>> current actions/checkout@v2. [2].
> > >>>
> > >>> In the Github actions market are already a couple of alternatives to
> > >>> perform this setup [3] but are non-verified third parties actions.
> > >>>
> > >>> Currently, in the Github actions market are cero verified Maven
> related
> > >>> actions [5] but there are already a couple really useful maven
> related
> > >>> actions beyond just the version settings [6]
> > >>>
> > >>> Since early 2021, Apache related projects allows only verified
> actions
> > to
> > >>> be used in workflows.
> > >>>
> > >>>
> > >>> The opportunity:
> > >>> Base on the interaction with the Actions team [2] it seems Actions
> > >>> verification can be done if the actions are created as part of the
> > >> official
> > >>> projects. For example Ruby setup action [4].
> > >>>
> > >>> Before brainstorming in solution, creating a JIRA or a PR with draft
> > >>> implementation, I would like to know if there is any interest within
> > the
> > >>> Maven community to offer to users certified Maven Github actions?
> > >>>
> > >>>
> > >>> [1]
> > >>>
> > >>>
> > >>
> >
> https://docs.github.com/en/actions/guides/building-and-testing-java-with-maven
> > >>> [2]
> > >>
> https://github.com/actions/setup-java/issues/40#issuecomment-778028611
> > >>> [3] https://github.com/stCarolas/setup-maven
> > >>> [4] https://github.com/ruby/setup-ruby
> > >>> [5]
> > >>>
> > >>>
> > >>
> >
> https://github.com/marketplace?query=maven&type=actions&verification=verified
> > >>> [6] https://github.com/marketplace?after=Y

Re: Parent pom or BOM not resolved using DefaultProjectBuildingRequest

2021-02-12 Thread Anthony Dahanne 
Hello,
I still could not find any solution to this problem
I have cross posted on stackoverflow :
https://stackoverflow.com/questions/66181515/defaultprojectbuildingrequest-org-apache-maven-project-projectbuildingexception
Please let me know if my question is not posted in the right mailing list...
Thanks

Le jeu. 11 févr. 2021, à 21 h 36, Anthony Dahanne 
a écrit :

> Hello Maven devs,
> I'm trying to programmatically ingest a pom.xml and start a Maven
> dependency resolution on it.
> For that end, I'm using DefaultProjectBuildingRequest and a
> ProjectBuilder.
> I could successfully issue the request, but when trying against a pom that
> relies on a parent or a BOM (spring boot pom for example), it seems like
> the properties set in the poms (including dependencies poms) aren't
> considered.
>
> I have set up a Github project there to reproduce the issue:
>
> Code:
> https://github.com/anthonydahanne/maven-resolver/blob/master/src/main/java/net/dahanne/mavenresolver/MavenResolverApplication.java#L37
>
> Error output :
> https://github.com/anthonydahanne/maven-resolver/runs/1884304754?check_suite_focus=true
> (not sure it's public though)
>
> Pom I tried to resolve:
> https://github.com/anthonydahanne/maven-resolver/blob/master/pom.xml
>
> For convenience, I have copied the code, pom that I tried to resolve and
> the error log at the end of this email
>
> I am kindly asking for your help, in case I missed an option in request or
> the session or.. both...
> A debug session did not reveal much unfortunately...
>
> Thanks in advance for your help!
>
> Anthony
>
>
>
>
> Code snippet:
>
> ContainerConfiguration config = new DefaultContainerConfiguration();
>   config.setAutoWiring(true);
>   config.setClassPathScanning(PlexusConstants.SCANNING_INDEX);
>   PlexusContainer plexusContainer = new DefaultPlexusContainer(config);
>   ProjectBuilder projectBuilder = 
> plexusContainer.lookup(ProjectBuilder.class);
>   RepositorySystem repositorySystem = 
> plexusContainer.lookup(RepositorySystem.class);
>   DefaultRepositorySystemSession session = 
> MavenRepositorySystemUtils.newSession();
>   LocalRepository localRepository = new LocalRepository("target/.m2");
>   
> session.setLocalRepositoryManager(repositorySystem.newLocalRepositoryManager(session,
>  localRepository));
>
>   DefaultProjectBuildingRequest request = new DefaultProjectBuildingRequest();
>   request.setRepositorySession(session);
>   request.setResolveDependencies(true);
> ArtifactRepository centralRepository = new MavenArtifactRepository();
> centralRepository.setUrl("https://repo.maven.apache.org/maven2/";);
> centralRepository.setLayout(new DefaultRepositoryLayout());
> request.setRemoteRepositories(Collections.singletonList(centralRepository));
>
>   ProjectBuildingResult result = projectBuilder.build(new File("pom.xml"), 
> request);
>
> and here is the output:
>
> Caused by: org.apache.maven.project.ProjectBuildingException:
> Some problems were encountered while processing the POMs:
> [ERROR] Invalid artifact repository: null @
> [ERROR] Failed to determine Java version for profile jdk8 @
> io.dropwizard.metrics:metrics-parent:4.1.17,
> /Users/anthony.dahanne/workspaces/maven-resolver/target/.m2/io/dropwizard/metrics/metrics-parent/4.1.17/metrics-parent-4.1.17.pom,
> line 160, column 22
> [ERROR] Failed to determine Java version for profile doclint-java8-disable
> @ org.jboss:jboss-parent:36,
> /Users/anthony.dahanne/workspaces/maven-resolver/target/.m2/org/jboss/jboss-parent/36/jboss-parent-36.pom,
> line 839, column 17
> [ERROR] Failed to determine Java version for profile
> compile-java8-release-flag @ org.jboss:jboss-parent:36,
> /Users/anthony.dahanne/workspaces/maven-resolver/target/.m2/org/jboss/jboss-parent/36/jboss-parent-36.pom,
> line 879, column 18
> [ERROR] Failed to determine Java version for profile include-jdk-misc @
> org.jboss:jboss-parent:36,
> /Users/anthony.dahanne/workspaces/maven-resolver/target/.m2/org/jboss/jboss-parent/36/jboss-parent-36.pom,
> line 910, column 22
> [ERROR] Failed to determine Java version for profile java8-test @
> org.jboss:jboss-parent:36,
> /Users/anthony.dahanne/workspaces/maven-resolver/target/.m2/org/jboss/jboss-parent/36/jboss-parent-36.pom,
> line 961, column 22
> [ERROR] Failed to determine Java version for profile java9-mr-build @
> org.jboss:jboss-parent:36,
> /Users/anthony.dahanne/workspaces/maven-resolver/target/.m2/org/jboss/jboss-parent/36/jboss-parent-36.pom,
> line 998, column 22
> [ERROR] Failed to determine Java version for profile java9-test @
> org.jboss:jboss-parent:36,
> /Users/anthony.dahanne/workspaces/maven-resolver/target/.m2/org/jboss/jboss-parent/36/jboss-parent-36.pom,
> line 1047, column 22
> [ERROR] Failed to determine Java version for profile java10-mr-build @
> org.jboss:jboss-parent:36,
> /Users/anthony.dahanne/workspaces/maven-resolver/target/.m2/org/jboss/jboss-parent/36/jboss-parent-36.pom,
> line 1087, column 22
> [ERROR] Failed to determine Java version

[GitHub] [maven-site] asfgit merged pull request #228: [MNGSITE-430] add dependency POMs

2021-02-12 Thread GitBox 


asfgit merged pull request #228:
URL: https://github.com/apache/maven-site/pull/228


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-site] hboutemy commented on pull request #228: [MNGSITE-430] add dependency POMs

2021-02-12 Thread GitBox 


hboutemy commented on pull request #228:
URL: https://github.com/apache/maven-site/pull/228#issuecomment-778500519


   yes, we can add such an image in a future step



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

Re: Official Maven Github Actions

2021-02-12 Thread Cesar Hernandez 
Thank you all for the feedback provided so far.

I was not aware of Maven Wrapper coming in 3.7, and also the plain sh
script seems to be right the approach the
https://github.com/sdkman/sdkman-action took.
I just ping Eddú to know his feedback on the sdkman-action since it's not
even listed in the market and, from the context, I think that can easily
pass the Verification requirement since it's hosted in the sdkman
organization.

As I wrote at the beginning of the thread, defining a specific maven
version is just one of many other maven related actions. For example, I've
found issues with the default settings.xml included in GitHub actions
and shrinkwrap-resolve so I ended up using actions like
whelk-io/maven-settings-xml-action and then migrated to the sh script
approach Romain mentioned after Apache infra recommendation was to remove
the usage to non verified actions.

El vie, 12 feb 2021 a las 14:16, Andres Almiray ()
escribió:

> FWIW there’s an sdkman GHA in case you’d like to explore that option
>
> https://github.com/sdkman/sdkman-action
>
> Cheers
> Andres
>
> Sent from my primitive tricorder
>
> > On 12 Feb 2021, at 20:52, Romain Manni-Bucau 
> wrote:
> >
> > Hi César,
> >
> > Any interesting feature compared to using a plain sh script with sdkman?
> > Looks like saner since it will enable you to setup java and maven
> properly
> > at the same stage which is the actual prerequisite of a maven build vs
> > using multiple random actions.
> > Did you investigate this option?
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github <
> https://github.com/rmannibucau> |
> > LinkedIn  | Book
> > <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
> >
> >
> >> Le ven. 12 févr. 2021 à 20:39, Robert Scholte  a
> >> écrit :
> >>
> >> I'm only aware of MNG-6887.
> >>
> >> Robert
> >>
> >>
> >> [1] https://issues.apache.org/jira/browse/MNG-6887
> >> On 12-2-2021 19:40:24, Gary Gregory  wrote:
> >> I've been wanting such an GH action myself!
> >>
> >> Gary
> >>
> >> On Fri, Feb 12, 2021 at 12:52 PM Cesar Hernandez
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> The problems:
> >>>
> >>> Currently, the official Github actions for building and testing Java
> with
> >>> Maven [1] don't offer a way to specify the Maven version a workflow can
> >>> use.
> >>> Adding this support seems to be out of the scope of the
> >>> current actions/checkout@v2. [2].
> >>>
> >>> In the Github actions market are already a couple of alternatives to
> >>> perform this setup [3] but are non-verified third parties actions.
> >>>
> >>> Currently, in the Github actions market are cero verified Maven related
> >>> actions [5] but there are already a couple really useful maven related
> >>> actions beyond just the version settings [6]
> >>>
> >>> Since early 2021, Apache related projects allows only verified actions
> to
> >>> be used in workflows.
> >>>
> >>>
> >>> The opportunity:
> >>> Base on the interaction with the Actions team [2] it seems Actions
> >>> verification can be done if the actions are created as part of the
> >> official
> >>> projects. For example Ruby setup action [4].
> >>>
> >>> Before brainstorming in solution, creating a JIRA or a PR with draft
> >>> implementation, I would like to know if there is any interest within
> the
> >>> Maven community to offer to users certified Maven Github actions?
> >>>
> >>>
> >>> [1]
> >>>
> >>>
> >>
> https://docs.github.com/en/actions/guides/building-and-testing-java-with-maven
> >>> [2]
> >> https://github.com/actions/setup-java/issues/40#issuecomment-778028611
> >>> [3] https://github.com/stCarolas/setup-maven
> >>> [4] https://github.com/ruby/setup-ruby
> >>> [5]
> >>>
> >>>
> >>
> https://github.com/marketplace?query=maven&type=actions&verification=verified
> >>> [6] https://github.com/marketplace?after=Y3Vyc29yOjIw&query=maven
> >>> --
> >>> Atentamente:
> >>> César Hernández.
> >>>
> >>
>


-- 
Atentamente:
César Hernández.

Re: Official Maven Github Actions

2021-02-12 Thread Andres Almiray 
FWIW there’s an sdkman GHA in case you’d like to explore that option 

https://github.com/sdkman/sdkman-action

Cheers
Andres

Sent from my primitive tricorder

> On 12 Feb 2021, at 20:52, Romain Manni-Bucau  wrote:
> 
> Hi César,
> 
> Any interesting feature compared to using a plain sh script with sdkman?
> Looks like saner since it will enable you to setup java and maven properly
> at the same stage which is the actual prerequisite of a maven build vs
> using multiple random actions.
> Did you investigate this option?
> 
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  |
> LinkedIn  | Book
> 
> 
> 
>> Le ven. 12 févr. 2021 à 20:39, Robert Scholte  a
>> écrit :
>> 
>> I'm only aware of MNG-6887.
>> 
>> Robert
>> 
>> 
>> [1] https://issues.apache.org/jira/browse/MNG-6887
>> On 12-2-2021 19:40:24, Gary Gregory  wrote:
>> I've been wanting such an GH action myself!
>> 
>> Gary
>> 
>> On Fri, Feb 12, 2021 at 12:52 PM Cesar Hernandez
>> wrote:
>> 
>>> Hi,
>>> 
>>> The problems:
>>> 
>>> Currently, the official Github actions for building and testing Java with
>>> Maven [1] don't offer a way to specify the Maven version a workflow can
>>> use.
>>> Adding this support seems to be out of the scope of the
>>> current actions/checkout@v2. [2].
>>> 
>>> In the Github actions market are already a couple of alternatives to
>>> perform this setup [3] but are non-verified third parties actions.
>>> 
>>> Currently, in the Github actions market are cero verified Maven related
>>> actions [5] but there are already a couple really useful maven related
>>> actions beyond just the version settings [6]
>>> 
>>> Since early 2021, Apache related projects allows only verified actions to
>>> be used in workflows.
>>> 
>>> 
>>> The opportunity:
>>> Base on the interaction with the Actions team [2] it seems Actions
>>> verification can be done if the actions are created as part of the
>> official
>>> projects. For example Ruby setup action [4].
>>> 
>>> Before brainstorming in solution, creating a JIRA or a PR with draft
>>> implementation, I would like to know if there is any interest within the
>>> Maven community to offer to users certified Maven Github actions?
>>> 
>>> 
>>> [1]
>>> 
>>> 
>> https://docs.github.com/en/actions/guides/building-and-testing-java-with-maven
>>> [2]
>> https://github.com/actions/setup-java/issues/40#issuecomment-778028611
>>> [3] https://github.com/stCarolas/setup-maven
>>> [4] https://github.com/ruby/setup-ruby
>>> [5]
>>> 
>>> 
>> https://github.com/marketplace?query=maven&type=actions&verification=verified
>>> [6] https://github.com/marketplace?after=Y3Vyc29yOjIw&query=maven
>>> --
>>> Atentamente:
>>> César Hernández.
>>> 
>>

Re: Official Maven Github Actions

2021-02-12 Thread Romain Manni-Bucau 
Hi César,

Any interesting feature compared to using a plain sh script with sdkman?
Looks like saner since it will enable you to setup java and maven properly
at the same stage which is the actual prerequisite of a maven build vs
using multiple random actions.
Did you investigate this option?

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le ven. 12 févr. 2021 à 20:39, Robert Scholte  a
écrit :

> I'm only aware of MNG-6887.
>
> Robert
>
>
> [1] https://issues.apache.org/jira/browse/MNG-6887
> On 12-2-2021 19:40:24, Gary Gregory  wrote:
> I've been wanting such an GH action myself!
>
> Gary
>
> On Fri, Feb 12, 2021 at 12:52 PM Cesar Hernandez
> wrote:
>
> > Hi,
> >
> > The problems:
> >
> > Currently, the official Github actions for building and testing Java with
> > Maven [1] don't offer a way to specify the Maven version a workflow can
> > use.
> > Adding this support seems to be out of the scope of the
> > current actions/checkout@v2. [2].
> >
> > In the Github actions market are already a couple of alternatives to
> > perform this setup [3] but are non-verified third parties actions.
> >
> > Currently, in the Github actions market are cero verified Maven related
> > actions [5] but there are already a couple really useful maven related
> > actions beyond just the version settings [6]
> >
> > Since early 2021, Apache related projects allows only verified actions to
> > be used in workflows.
> >
> >
> > The opportunity:
> > Base on the interaction with the Actions team [2] it seems Actions
> > verification can be done if the actions are created as part of the
> official
> > projects. For example Ruby setup action [4].
> >
> > Before brainstorming in solution, creating a JIRA or a PR with draft
> > implementation, I would like to know if there is any interest within the
> > Maven community to offer to users certified Maven Github actions?
> >
> >
> > [1]
> >
> >
> https://docs.github.com/en/actions/guides/building-and-testing-java-with-maven
> > [2]
> https://github.com/actions/setup-java/issues/40#issuecomment-778028611
> > [3] https://github.com/stCarolas/setup-maven
> > [4] https://github.com/ruby/setup-ruby
> > [5]
> >
> >
> https://github.com/marketplace?query=maven&type=actions&verification=verified
> > [6] https://github.com/marketplace?after=Y3Vyc29yOjIw&query=maven
> > --
> > Atentamente:
> > César Hernández.
> >
>

Re: Official Maven Github Actions

2021-02-12 Thread Robert Scholte 
I'm only aware of MNG-6887.

Robert


[1] https://issues.apache.org/jira/browse/MNG-6887
On 12-2-2021 19:40:24, Gary Gregory  wrote:
I've been wanting such an GH action myself!

Gary

On Fri, Feb 12, 2021 at 12:52 PM Cesar Hernandez
wrote:

> Hi,
>
> The problems:
>
> Currently, the official Github actions for building and testing Java with
> Maven [1] don't offer a way to specify the Maven version a workflow can
> use.
> Adding this support seems to be out of the scope of the
> current actions/checkout@v2. [2].
>
> In the Github actions market are already a couple of alternatives to
> perform this setup [3] but are non-verified third parties actions.
>
> Currently, in the Github actions market are cero verified Maven related
> actions [5] but there are already a couple really useful maven related
> actions beyond just the version settings [6]
>
> Since early 2021, Apache related projects allows only verified actions to
> be used in workflows.
>
>
> The opportunity:
> Base on the interaction with the Actions team [2] it seems Actions
> verification can be done if the actions are created as part of the official
> projects. For example Ruby setup action [4].
>
> Before brainstorming in solution, creating a JIRA or a PR with draft
> implementation, I would like to know if there is any interest within the
> Maven community to offer to users certified Maven Github actions?
>
>
> [1]
>
> https://docs.github.com/en/actions/guides/building-and-testing-java-with-maven
> [2] https://github.com/actions/setup-java/issues/40#issuecomment-778028611
> [3] https://github.com/stCarolas/setup-maven
> [4] https://github.com/ruby/setup-ruby
> [5]
>
> https://github.com/marketplace?query=maven&type=actions&verification=verified
> [6] https://github.com/marketplace?after=Y3Vyc29yOjIw&query=maven
> --
> Atentamente:
> César Hernández.
>

[GitHub] [maven-site] rfscholte commented on pull request #228: [MNGSITE-430] add dependency POMs

2021-02-12 Thread GitBox 


rfscholte commented on pull request #228:
URL: https://github.com/apache/maven-site/pull/228#issuecomment-778408664


   Sometimes images say more than words. Looks like this one should have a 
picture of a graph to support the logic.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-site] hboutemy commented on pull request #228: [MNGSITE-430] add dependency POMs

2021-02-12 Thread GitBox 


hboutemy commented on pull request #228:
URL: https://github.com/apache/maven-site/pull/228#issuecomment-778379785


   yes, the last description is the hard one where we need creativity...
   
   "POMs from dependency path to the artifact"?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

Re: Official Maven Github Actions

2021-02-12 Thread Gary Gregory 
I've been wanting such an GH action myself!

Gary

On Fri, Feb 12, 2021 at 12:52 PM Cesar Hernandez 
wrote:

> Hi,
>
> The problems:
>
> Currently, the official Github actions for building and testing Java with
> Maven [1] don't offer a way to specify the Maven version a workflow can
> use.
> Adding this support seems to be out of the scope of the
> current actions/checkout@v2. [2].
>
> In the Github actions market are already a couple of alternatives to
> perform this setup [3] but are non-verified third parties actions.
>
> Currently, in the Github actions market are cero verified Maven related
> actions [5] but there are already a couple really useful maven related
> actions beyond just the version settings [6]
>
> Since early 2021, Apache related projects allows only verified actions to
> be used in workflows.
>
>
> The opportunity:
> Base on the interaction with the Actions team [2] it seems Actions
> verification can be done if the actions are created as part of the official
> projects. For example Ruby setup action [4].
>
> Before brainstorming in solution, creating a JIRA or a PR with draft
> implementation, I would like to know if there is any interest within the
> Maven community to offer to users certified Maven Github actions?
>
>
> [1]
>
> https://docs.github.com/en/actions/guides/building-and-testing-java-with-maven
> [2] https://github.com/actions/setup-java/issues/40#issuecomment-778028611
> [3] https://github.com/stCarolas/setup-maven
> [4] https://github.com/ruby/setup-ruby
> [5]
>
> https://github.com/marketplace?query=maven&type=actions&verification=verified
> [6] https://github.com/marketplace?after=Y3Vyc29yOjIw&query=maven
> --
> Atentamente:
> César Hernández.
>

Re: Official Maven Github Actions

2021-02-12 Thread Falko Modler 

Hi all,

FWIW, a wrapper also doesn't help if you want to test extensions or
plugins with multiple Maven versions.
E.g.:
-
https://github.com/gitflow-incremental-builder/gitflow-incremental-builder/blob/master/.github/workflows/maven.yml#L105-L136
-
https://github.com/gitflow-incremental-builder/gitflow-incremental-builder/blob/master/.github/workflows/maven.yml#L144-L155

So in general I like the idea, if such actions are maintained properly.

Cheers,
Falko

Am 12.02.2021 um 18:56 schrieb Andres Almiray:

Cesar,

Maven 4 will include a wrapper script that should take care of this issue.

For Maven 3.x you may use Takari's Maven Wrapper[1] to get similar behavior.

However for those that can't set a wrapper for several reasons (for example
Apache projects do not allow JARs in their repositories those the wrapper
cannot be set before hand).
the a Github Action may be thew way to go.

Cheers,
Andres

[1] https://github.com/takari/maven-wrapper

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Fri, Feb 12, 2021 at 6:52 PM Cesar Hernandez 
wrote:


Hi,

The problems:

Currently, the official Github actions for building and testing Java with
Maven [1] don't offer a way to specify the Maven version a workflow can
use.
Adding this support seems to be out of the scope of the
current actions/checkout@v2. [2].

In the Github actions market are already a couple of alternatives to
perform this setup [3] but are non-verified third parties actions.

Currently, in the Github actions market are cero verified Maven related
actions [5] but there are already a couple really useful maven related
actions beyond just the version settings [6]

Since early 2021, Apache related projects allows only verified actions to
be used in workflows.


The opportunity:
Base on the interaction with the Actions team [2] it seems Actions
verification can be done if the actions are created as part of the official
projects. For example Ruby setup action [4].

Before brainstorming in solution, creating a JIRA or a PR with draft
implementation, I would like to know if there is any interest within the
Maven community to offer to users certified Maven Github actions?


[1]

https://docs.github.com/en/actions/guides/building-and-testing-java-with-maven
[2] https://github.com/actions/setup-java/issues/40#issuecomment-778028611
[3] https://github.com/stCarolas/setup-maven
[4] https://github.com/ruby/setup-ruby
[5]

https://github.com/marketplace?query=maven&type=actions&verification=verified
[6] https://github.com/marketplace?after=Y3Vyc29yOjIw&query=maven
--
Atentamente:
César Hernández.




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

Re: Official Maven Github Actions

2021-02-12 Thread Andres Almiray 
Cesar,

Maven 4 will include a wrapper script that should take care of this issue.

For Maven 3.x you may use Takari's Maven Wrapper[1] to get similar behavior.

However for those that can't set a wrapper for several reasons (for example
Apache projects do not allow JARs in their repositories those the wrapper
cannot be set before hand).
the a Github Action may be thew way to go.

Cheers,
Andres

[1] https://github.com/takari/maven-wrapper

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Fri, Feb 12, 2021 at 6:52 PM Cesar Hernandez 
wrote:

> Hi,
>
> The problems:
>
> Currently, the official Github actions for building and testing Java with
> Maven [1] don't offer a way to specify the Maven version a workflow can
> use.
> Adding this support seems to be out of the scope of the
> current actions/checkout@v2. [2].
>
> In the Github actions market are already a couple of alternatives to
> perform this setup [3] but are non-verified third parties actions.
>
> Currently, in the Github actions market are cero verified Maven related
> actions [5] but there are already a couple really useful maven related
> actions beyond just the version settings [6]
>
> Since early 2021, Apache related projects allows only verified actions to
> be used in workflows.
>
>
> The opportunity:
> Base on the interaction with the Actions team [2] it seems Actions
> verification can be done if the actions are created as part of the official
> projects. For example Ruby setup action [4].
>
> Before brainstorming in solution, creating a JIRA or a PR with draft
> implementation, I would like to know if there is any interest within the
> Maven community to offer to users certified Maven Github actions?
>
>
> [1]
>
> https://docs.github.com/en/actions/guides/building-and-testing-java-with-maven
> [2] https://github.com/actions/setup-java/issues/40#issuecomment-778028611
> [3] https://github.com/stCarolas/setup-maven
> [4] https://github.com/ruby/setup-ruby
> [5]
>
> https://github.com/marketplace?query=maven&type=actions&verification=verified
> [6] https://github.com/marketplace?after=Y3Vyc29yOjIw&query=maven
> --
> Atentamente:
> César Hernández.
>

Official Maven Github Actions

2021-02-12 Thread Cesar Hernandez 
Hi,

The problems:

Currently, the official Github actions for building and testing Java with
Maven [1] don't offer a way to specify the Maven version a workflow can use.
Adding this support seems to be out of the scope of the
current actions/checkout@v2. [2].

In the Github actions market are already a couple of alternatives to
perform this setup [3] but are non-verified third parties actions.

Currently, in the Github actions market are cero verified Maven related
actions [5] but there are already a couple really useful maven related
actions beyond just the version settings [6]

Since early 2021, Apache related projects allows only verified actions to
be used in workflows.


The opportunity:
Base on the interaction with the Actions team [2] it seems Actions
verification can be done if the actions are created as part of the official
projects. For example Ruby setup action [4].

Before brainstorming in solution, creating a JIRA or a PR with draft
implementation, I would like to know if there is any interest within the
Maven community to offer to users certified Maven Github actions?


[1]
https://docs.github.com/en/actions/guides/building-and-testing-java-with-maven
[2] https://github.com/actions/setup-java/issues/40#issuecomment-778028611
[3] https://github.com/stCarolas/setup-maven
[4] https://github.com/ruby/setup-ruby
[5]
https://github.com/marketplace?query=maven&type=actions&verification=verified
[6] https://github.com/marketplace?after=Y3Vyc29yOjIw&query=maven
-- 
Atentamente:
César Hernández.

[GitHub] [maven-site] rfscholte commented on pull request #228: [MNGSITE-430] add dependency POMs

2021-02-12 Thread GitBox 


rfscholte commented on pull request #228:
URL: https://github.com/apache/maven-site/pull/228#issuecomment-778141870


   The last description is still not clear for me. I think what we're trying to 
say: repositories within context, i.e the reposities of the pom that defined 
this pom as a dependency.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-site] hboutemy edited a comment on pull request #228: [MNGSITE-430] add dependency POMs

2021-02-12 Thread GitBox 


hboutemy edited a comment on pull request #228:
URL: https://github.com/apache/maven-site/pull/228#issuecomment-778125511


   @rfscholte local POM does not have any resolution: it is locally on disk, 
from Git
   resolution is always for dependencies
   
   > transitive dependencies are never effected by repos of their calling pom.
   
   they are affected by repos of their calling pom, that is exactly what 
resolution order is about



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-site] hboutemy commented on pull request #228: [MNGSITE-430] add dependency POMs

2021-02-12 Thread GitBox 


hboutemy commented on pull request #228:
URL: https://github.com/apache/maven-site/pull/228#issuecomment-778125511


   @rfscholte local POM does not have any resolution: it is locally on disk, 
from Git
   resolution is always for dependencies
   
   > transitive dependencies are never effected by repos of their calling pom.
   they are affected by repos of their calling pom, that is exactly what 
resolution order is about



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-site] rfscholte commented on pull request #228: [MNGSITE-430] add dependency POMs

2021-02-12 Thread GitBox 


rfscholte commented on pull request #228:
URL: https://github.com/apache/maven-site/pull/228#issuecomment-778089075


   I suggest to split this up into two: 
   - The repository resolution order for a local/reactor pom
   - The repository resolution order for a dependency pom
   
   It must be very clear that transitive dependencies are never effected by 
repos of their calling pom.




This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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