Re: Twitter handles of committers
LinkedIn, GitLab, blogs, these are all rather professional references, and I think it makes perfect sense to link those from an ASF hosted website. But how about, let's say, Facebook, Instagram or what not? Would we allow any kind of social links? And if not, who would be accepting/denying it? Just to be clear, I'm all in favour of increasing visibility, even though I'm not a committer myself. I'm just wondering out loud whether/where to draw the line... Regards, Maarten On May 24, 2020 at 19:50, Andres Almiray wrote: Maarten, I don't think these social accounts have anything to do with mirrors of Apache on a particular service, rather to increase visibility on the developers themselves. What if I wanted to link to my Linkedin or Patreon profiles? Personal blog? Would that we allowed? What would be the limits? Cheers, Andres --- 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 Sun, May 24, 2020 at 7:44 PM Maarten Mulders wrote: Great initiative! Deeplinking to the profile would be nice, too, I guess. I would start with Twitter and GitHub. GitLab makes less sense to me, AFAIK there are no mirrors of Maven hosted at GitLab? May I also suggest to do it the other way round: a Twitter list [1] of people who are Maven committer? Or maybe it already exists? Maarten [1] https://help.twitter.com/en/using-twitter/twitter-lists On May 24, 2020 at 19:40, Robert Scholte wrote: Sure we could do that too. Would be nice to improve the team pages for well known properties, but at the moment there's a vote on the maven-project-info-reports-plugin. Maybe an up-for-grabs to include with the next release. Robert On 24-5-2020 19:27:08, Andres Almiray wrote: Good idea Robert! May I suggest adding GitHub account as well? Not everyone follows Twitter or has an account (shocking, I know) but they may have a Github account or consider browsing through an author's profile. And why stop with Github? Let's add Gitlab. I guess, s long as there's no "explicit" or "stardard" social media | social coding column team members are free to choose which accounts they'd like to link, right? Cheers, Andres --- 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 Sun, May 24, 2020 at 7:18 PM Robert Scholte wrote: I had a chat with Chandra (@CGuntur) regarding exposure of Maven committers. My experience is that most Maven users just use it, without knowing the people behind and (yes, people, not a company). Twitter has been a good way to share information regarding Maven. To get more attention, I've added a twitter-property to my profile in the maven parent pom. After triggering the website the team-list[1] has been expanded with a properties-column. Not the nicest look and feel, but having my twitter handle here is more important to me. I could add all known twitter handles, but I leave it up to every committer to add this property as well. Simply update your profile in the maven-parent if you want. thanks, Robert [1] https://maven.apache.org/team.html [2] https://github.com/apache/maven-parent/blob/master/pom.xml - 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: Twitter handles of committers
We can create a public list of developers with the project account. Le dim. 24 mai 2020 à 19:44, Maarten Mulders a écrit : > Great initiative! > > Deeplinking to the profile would be nice, too, I guess. > I would start with Twitter and GitHub. GitLab makes less sense to me, > AFAIK there are no mirrors of Maven hosted at GitLab? > > May I also suggest to do it the other way round: a Twitter list [1] of > people who are Maven committer? Or maybe it already exists? > > Maarten > > [1] https://help.twitter.com/en/using-twitter/twitter-lists > > On May 24, 2020 at 19:40, Robert Scholte wrote: > > > Sure we could do that too. > > Would be nice to improve the team pages for well known properties, but > > at the moment there's a vote on the maven-project-info-reports-plugin. > > Maybe an up-for-grabs to include with the next release. > > > > Robert > > On 24-5-2020 19:27:08, Andres Almiray wrote: > > Good idea Robert! > > May I suggest adding GitHub account as well? Not everyone follows > > Twitter > > or has an account (shocking, I know) but they may have a Github account > > or > > consider browsing through an author's profile. > > > > And why stop with Github? Let's add Gitlab. > > I guess, s long as there's no "explicit" or "stardard" social media | > > social coding column team members are free to choose which accounts > > they'd > > like to link, right? > > > > Cheers, > > Andres > > > > --- > > 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 Sun, May 24, 2020 at 7:18 PM Robert Scholte wrote: > > > >> I had a chat with Chandra (@CGuntur) regarding exposure of Maven > >> committers. > >> My experience is that most Maven users just use it, without knowing > >> the > >> people behind and (yes, people, not a company). Twitter has been a > >> good way > >> to share information regarding Maven. > >> To get more attention, I've added a twitter-property to my profile in > >> the > >> maven parent pom. > >> After triggering the website the team-list[1] has been expanded with a > >> properties-column. > >> Not the nicest look and feel, but having my twitter handle here is > >> more > >> important to me. > >> > >> I could add all known twitter handles, but I leave it up to every > >> committer to add this property as well. > >> Simply update your profile in the maven-parent if you want. > >> > >> thanks, > >> Robert > >> > >> [1] https://maven.apache.org/team.html > >> > >> [2] https://github.com/apache/maven-parent/blob/master/pom.xml > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Release Maven Project Info Reports Plugin version 3.1.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 23.05.20 23:13, Michael Osipov wrote: Hi, We solved 13 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12346620 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MPIR/issues Staging repo: https://repository.apache.org/content/repositories/maven-1579/ https://repository.apache.org/content/repositories/maven-1579/org/apache/maven/plugins/maven-project-info-reports-plugin/3.1.0/maven-project-info-reports-plugin-3.1.0-source-release.zip Source release checksum(s): maven-project-info-reports-plugin-3.1.0-source-release.zip sha512: f0c378217d466d264313ad8b0367354f8e6ea40dee41de3d0e288f1492fa6e5d6e37bf22416c2b19c87185e43f8fbfe59ce47f233dfc8fe0bc07bcdf69eb45a9 Staging site: https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site-plugin] elharo merged pull request #25: [MSITE-859] update apache commons lang and IO
elharo merged pull request #25: URL: https://github.com/apache/maven-site-plugin/pull/25 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: Twitter handles of committers
Maarten, I don't think these social accounts have anything to do with mirrors of Apache on a particular service, rather to increase visibility on the developers themselves. What if I wanted to link to my Linkedin or Patreon profiles? Personal blog? Would that we allowed? What would be the limits? Cheers, Andres --- 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 Sun, May 24, 2020 at 7:44 PM Maarten Mulders wrote: > Great initiative! > > Deeplinking to the profile would be nice, too, I guess. > I would start with Twitter and GitHub. GitLab makes less sense to me, > AFAIK there are no mirrors of Maven hosted at GitLab? > > May I also suggest to do it the other way round: a Twitter list [1] of > people who are Maven committer? Or maybe it already exists? > > Maarten > > [1] https://help.twitter.com/en/using-twitter/twitter-lists > > On May 24, 2020 at 19:40, Robert Scholte wrote: > > > Sure we could do that too. > > Would be nice to improve the team pages for well known properties, but > > at the moment there's a vote on the maven-project-info-reports-plugin. > > Maybe an up-for-grabs to include with the next release. > > > > Robert > > On 24-5-2020 19:27:08, Andres Almiray wrote: > > Good idea Robert! > > May I suggest adding GitHub account as well? Not everyone follows > > Twitter > > or has an account (shocking, I know) but they may have a Github account > > or > > consider browsing through an author's profile. > > > > And why stop with Github? Let's add Gitlab. > > I guess, s long as there's no "explicit" or "stardard" social media | > > social coding column team members are free to choose which accounts > > they'd > > like to link, right? > > > > Cheers, > > Andres > > > > --- > > 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 Sun, May 24, 2020 at 7:18 PM Robert Scholte wrote: > > > >> I had a chat with Chandra (@CGuntur) regarding exposure of Maven > >> committers. > >> My experience is that most Maven users just use it, without knowing > >> the > >> people behind and (yes, people, not a company). Twitter has been a > >> good way > >> to share information regarding Maven. > >> To get more attention, I've added a twitter-property to my profile in > >> the > >> maven parent pom. > >> After triggering the website the team-list[1] has been expanded with a > >> properties-column. > >> Not the nicest look and feel, but having my twitter handle here is > >> more > >> important to me. > >> > >> I could add all known twitter handles, but I leave it up to every > >> committer to add this property as well. > >> Simply update your profile in the maven-parent if you want. > >> > >> thanks, > >> Robert > >> > >> [1] https://maven.apache.org/team.html > >> > >> [2] https://github.com/apache/maven-parent/blob/master/pom.xml > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven Wagon version 3.4.1
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 24.05.20 10:51, Olivier Lamy wrote: +1 On Sat, 23 May 2020 at 05:45, Michael Osipov wrote: Hi, We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12348210 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-1576/ https://repository.apache.org/content/repositories/maven-1576/org/apache/maven/wagon/wagon/3.4.1/wagon-3.4.1-source-release.zip Source release checksum(s): wagon-3.4.1-source-release.zip sha512: 342d3ad88ba3535a0b6cafcfebd3f5b2e0fc6ac4022bebcea78a60703b0c611232e765ea87fb98ada0dc5daf1a9002e9bf7959571eebc4c974efda042246999c Staging site: https://maven.apache.org/wagon-archives/wagon-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Twitter handles of committers
Great initiative! Deeplinking to the profile would be nice, too, I guess. I would start with Twitter and GitHub. GitLab makes less sense to me, AFAIK there are no mirrors of Maven hosted at GitLab? May I also suggest to do it the other way round: a Twitter list [1] of people who are Maven committer? Or maybe it already exists? Maarten [1] https://help.twitter.com/en/using-twitter/twitter-lists On May 24, 2020 at 19:40, Robert Scholte wrote: Sure we could do that too. Would be nice to improve the team pages for well known properties, but at the moment there's a vote on the maven-project-info-reports-plugin. Maybe an up-for-grabs to include with the next release. Robert On 24-5-2020 19:27:08, Andres Almiray wrote: Good idea Robert! May I suggest adding GitHub account as well? Not everyone follows Twitter or has an account (shocking, I know) but they may have a Github account or consider browsing through an author's profile. And why stop with Github? Let's add Gitlab. I guess, s long as there's no "explicit" or "stardard" social media | social coding column team members are free to choose which accounts they'd like to link, right? Cheers, Andres --- 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 Sun, May 24, 2020 at 7:18 PM Robert Scholte wrote: I had a chat with Chandra (@CGuntur) regarding exposure of Maven committers. My experience is that most Maven users just use it, without knowing the people behind and (yes, people, not a company). Twitter has been a good way to share information regarding Maven. To get more attention, I've added a twitter-property to my profile in the maven parent pom. After triggering the website the team-list[1] has been expanded with a properties-column. Not the nicest look and feel, but having my twitter handle here is more important to me. I could add all known twitter handles, but I leave it up to every committer to add this property as well. Simply update your profile in the maven-parent if you want. thanks, Robert [1] https://maven.apache.org/team.html [2] https://github.com/apache/maven-parent/blob/master/pom.xml - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Twitter handles of committers
Sure we could do that too. Would be nice to improve the team pages for well known properties, but at the moment there's a vote on the maven-project-info-reports-plugin. Maybe an up-for-grabs to include with the next release. Robert On 24-5-2020 19:27:08, Andres Almiray wrote: Good idea Robert! May I suggest adding GitHub account as well? Not everyone follows Twitter or has an account (shocking, I know) but they may have a Github account or consider browsing through an author's profile. And why stop with Github? Let's add Gitlab. I guess, s long as there's no "explicit" or "stardard" social media | social coding column team members are free to choose which accounts they'd like to link, right? Cheers, Andres --- 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 Sun, May 24, 2020 at 7:18 PM Robert Scholte wrote: > I had a chat with Chandra (@CGuntur) regarding exposure of Maven > committers. > My experience is that most Maven users just use it, without knowing the > people behind and (yes, people, not a company). Twitter has been a good way > to share information regarding Maven. > To get more attention, I've added a twitter-property to my profile in the > maven parent pom. > After triggering the website the team-list[1] has been expanded with a > properties-column. > Not the nicest look and feel, but having my twitter handle here is more > important to me. > > > I could add all known twitter handles, but I leave it up to every > committer to add this property as well. > Simply update your profile in the maven-parent if you want. > > thanks, > Robert > > [1] https://maven.apache.org/team.html > > [2] https://github.com/apache/maven-parent/blob/master/pom.xml
Re: Twitter handles of committers
Good idea Robert! May I suggest adding GitHub account as well? Not everyone follows Twitter or has an account (shocking, I know) but they may have a Github account or consider browsing through an author's profile. And why stop with Github? Let's add Gitlab. I guess, s long as there's no "explicit" or "stardard" social media | social coding column team members are free to choose which accounts they'd like to link, right? Cheers, Andres --- 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 Sun, May 24, 2020 at 7:18 PM Robert Scholte wrote: > I had a chat with Chandra (@CGuntur) regarding exposure of Maven > committers. > My experience is that most Maven users just use it, without knowing the > people behind and (yes, people, not a company). Twitter has been a good way > to share information regarding Maven. > To get more attention, I've added a twitter-property to my profile in the > maven parent pom. > After triggering the website the team-list[1] has been expanded with a > properties-column. > Not the nicest look and feel, but having my twitter handle here is more > important to me. > > > I could add all known twitter handles, but I leave it up to every > committer to add this property as well. > Simply update your profile in the maven-parent if you want. > > thanks, > Robert > > [1] https://maven.apache.org/team.html > > [2] https://github.com/apache/maven-parent/blob/master/pom.xml
Twitter handles of committers
I had a chat with Chandra (@CGuntur) regarding exposure of Maven committers. My experience is that most Maven users just use it, without knowing the people behind and (yes, people, not a company). Twitter has been a good way to share information regarding Maven. To get more attention, I've added a twitter-property to my profile in the maven parent pom. After triggering the website the team-list[1] has been expanded with a properties-column. Not the nicest look and feel, but having my twitter handle here is more important to me. I could add all known twitter handles, but I leave it up to every committer to add this property as well. Simply update your profile in the maven-parent if you want. thanks, Robert [1] https://maven.apache.org/team.html [2] https://github.com/apache/maven-parent/blob/master/pom.xml
[GitHub] [maven-site-plugin] slachiewicz commented on pull request #24: [MSITE-845] remove Maven 2 support
slachiewicz commented on pull request #24: URL: https://github.com/apache/maven-site-plugin/pull/24#issuecomment-633245302 build looks green https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-site-plugin/job/MSITE-845/ 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-plugin] elharo commented on pull request #24: [MSITE-845] remove Maven 2 support
elharo commented on pull request #24: URL: https://github.com/apache/maven-site-plugin/pull/24#issuecomment-633232518 Can that one be merged? 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-plugin] slachiewicz commented on pull request #24: [MSITE-845] remove Maven 2 support
slachiewicz commented on pull request #24: URL: https://github.com/apache/maven-site-plugin/pull/24#issuecomment-633230040 We already have PR #12 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-plugin] elharo opened a new pull request #25: [MSITE-859] update apache commons lang and IO
elharo opened a new pull request #25: URL: https://github.com/apache/maven-site-plugin/pull/25 @michael-o 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-plugin] elharo merged pull request #22: add .checkstyle to .gitignore
elharo merged pull request #22: URL: https://github.com/apache/maven-site-plugin/pull/22 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-plugin] elharo merged pull request #23: remove unused code
elharo merged pull request #23: URL: https://github.com/apache/maven-site-plugin/pull/23 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: Problem with site generation - maven-site-plugin
I still don't have full grasp of the cause, but I think we can remove our dependency on plexus-classworlds completely by ripping out some Maven 2 support. See https://github.com/apache/maven-site-plugin/pull/24/f On Sun, May 24, 2020 at 6:16 AM Elliotte Rusty Harold wrote: > > getInputLocation seems to have been added in plexus-utils 3.2.0. > > The reproducible builds work for maven-site-plugin upgraded from > plexus 3.0.x to 3.3.0 in > https://github.com/apache/maven-site-plugin/commit/19be00a9bf2a410abb7132487dc24055060b2c70#diff-600376dffeb79835ede4a0b285078036 > > It's not immediately clear to me how the classpath for all this is > pulling in an earlier version of plexus-utils since maven-site-plugin > declares that dependency directly, but that's what seems to be > happening. > > On Sun, May 24, 2020 at 6:02 AM Karl Heinz Marbaise wrote: > > > > Hi to all, > > > > I've stumbled upon the following problem during the site generation > > > > mojo-parent (issue-105)$ mvn site site:stage > > .. > > [INFO] > > [INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent --- > > [INFO] configuring report plugin > > org.apache.maven.plugins:maven-plugin-plugin:3.6.0 > > [INFO] preparing maven-plugin-plugin:report report requires > > 'process-classes' forked phase execution > > [INFO] > > [INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @ > > mojo-parent >>> > > [INFO] > > [INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @ > > mojo-parent --- > > [INFO] > > [INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @ > > mojo-parent <<< > > [INFO] 'process-classes' forked phase execution for > > maven-plugin-plugin:report report preparation done > > [INFO] 1 report detected for maven-plugin-plugin:3.6.0: report > > [INFO] configuring report plugin > > org.apache.maven.plugins:maven-changes-plugin:2.11 > > [INFO] 1 report configured for maven-changes-plugin:2.11: github-report > > [INFO] configuring report plugin > > org.apache.maven.plugins:maven-checkstyle-plugin:2.16 > > [INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle > > [INFO] configuring report plugin > > org.apache.maven.plugins:maven-javadoc-plugin:3.2.0 > > [INFO] > > > > [INFO] BUILD FAILURE > > [INFO] > > > > [INFO] Total time: 2.144 s > > [INFO] Finished at: 2020-05-24T11:50:11+02:00 > > [INFO] Final Memory: 30M/128M > > [INFO] > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on > > project mojo-parent: Execution default-site of goal > > org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API > > incompatibility was encountered while executing > > org.apache.maven.plugins:maven-site-plugin:3.9.0:site: > > java.lang.NoSuchMethodError: 'java.lang.Object > > org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()' > > [ERROR] - > > [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0 > > [ERROR] strategy = > > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > > [ERROR] urls[0] = > > file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.9.0/maven-site-plugin-3.9.0.jar > > > > > > This can be reproduced with 3.0.5 up to 3.6.1. > > > > Versions 3.6.2 and 3.6.3 are working fine. > > > > This means using maven-site-plugin 3.9.0 only working with Maven 3.6.2+ > > ...in contradiction to the site[1] which says it is requirement 3.0.. > > > > Or has someone a different explanation for this? > > > > Kind regards > > Karl Heinz Marbaise > > > > > > [1]: https://maven.apache.org/plugins/maven-site-plugin/plugin-info.html > > > > - > > 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 -- 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
[GitHub] [maven-site-plugin] elharo opened a new pull request #24: remove Maven 2 support
elharo opened a new pull request #24: URL: https://github.com/apache/maven-site-plugin/pull/24 @olamy 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: [VOTE] Release Apache Maven JXR version 3.1.0
Andreas Sewe wrote: > Hervé BOUTEMY wrote: >> We solved 6 issues: >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527=12344185=Text > > thanks for staging the release. The new jxr-no-fork and test-jxr-no-fork > goals work like a charm for me. :-) Spoke too soon. Found one issue where the test-jxr-no-fork goal (and test-jxr as well) generates "Class Summary" entries (in target/site/xref-test/index.html) for classes from src/main/java and not just from src/test/java. This is not only unexpected, but moreover, the links to the non-test classes are broken. :-( This seems to be a regression from 3.0.0 and would IMHO be a release blocker. Best wishes, Andreas signature.asc Description: OpenPGP digital signature
[GitHub] [maven-site-plugin] elharo opened a new pull request #23: remove unused code
elharo opened a new pull request #23: URL: https://github.com/apache/maven-site-plugin/pull/23 @olamy 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-plugin] elharo opened a new pull request #22: add .checkstyle to .gitignore
elharo opened a new pull request #22: URL: https://github.com/apache/maven-site-plugin/pull/22 @michael-o 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: [VOTE] Release Apache Maven JXR version 3.1.0
Hervé BOUTEMY wrote: > We solved 6 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527=12344185=Text thanks for staging the release. The new jxr-no-fork and test-jxr-no-fork goals work like a charm for me. :-) Best wishes, Andreas signature.asc Description: OpenPGP digital signature
Re: Problem with site generation - maven-site-plugin
getInputLocation seems to have been added in plexus-utils 3.2.0. The reproducible builds work for maven-site-plugin upgraded from plexus 3.0.x to 3.3.0 in https://github.com/apache/maven-site-plugin/commit/19be00a9bf2a410abb7132487dc24055060b2c70#diff-600376dffeb79835ede4a0b285078036 It's not immediately clear to me how the classpath for all this is pulling in an earlier version of plexus-utils since maven-site-plugin declares that dependency directly, but that's what seems to be happening. On Sun, May 24, 2020 at 6:02 AM Karl Heinz Marbaise wrote: > > Hi to all, > > I've stumbled upon the following problem during the site generation > > mojo-parent (issue-105)$ mvn site site:stage > .. > [INFO] > [INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent --- > [INFO] configuring report plugin > org.apache.maven.plugins:maven-plugin-plugin:3.6.0 > [INFO] preparing maven-plugin-plugin:report report requires > 'process-classes' forked phase execution > [INFO] > [INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @ > mojo-parent >>> > [INFO] > [INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @ > mojo-parent --- > [INFO] > [INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @ > mojo-parent <<< > [INFO] 'process-classes' forked phase execution for > maven-plugin-plugin:report report preparation done > [INFO] 1 report detected for maven-plugin-plugin:3.6.0: report > [INFO] configuring report plugin > org.apache.maven.plugins:maven-changes-plugin:2.11 > [INFO] 1 report configured for maven-changes-plugin:2.11: github-report > [INFO] configuring report plugin > org.apache.maven.plugins:maven-checkstyle-plugin:2.16 > [INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle > [INFO] configuring report plugin > org.apache.maven.plugins:maven-javadoc-plugin:3.2.0 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 2.144 s > [INFO] Finished at: 2020-05-24T11:50:11+02:00 > [INFO] Final Memory: 30M/128M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on > project mojo-parent: Execution default-site of goal > org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API > incompatibility was encountered while executing > org.apache.maven.plugins:maven-site-plugin:3.9.0:site: > java.lang.NoSuchMethodError: 'java.lang.Object > org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()' > [ERROR] - > [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0 > [ERROR] strategy = > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > [ERROR] urls[0] = > file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.9.0/maven-site-plugin-3.9.0.jar > > > This can be reproduced with 3.0.5 up to 3.6.1. > > Versions 3.6.2 and 3.6.3 are working fine. > > This means using maven-site-plugin 3.9.0 only working with Maven 3.6.2+ > ...in contradiction to the site[1] which says it is requirement 3.0.. > > Or has someone a different explanation for this? > > Kind regards > Karl Heinz Marbaise > > > [1]: https://maven.apache.org/plugins/maven-site-plugin/plugin-info.html > > - > 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
Problem with site generation - maven-site-plugin
Hi to all, I've stumbled upon the following problem during the site generation mojo-parent (issue-105)$ mvn site site:stage .. [INFO] [INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent --- [INFO] configuring report plugin org.apache.maven.plugins:maven-plugin-plugin:3.6.0 [INFO] preparing maven-plugin-plugin:report report requires 'process-classes' forked phase execution [INFO] [INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @ mojo-parent >>> [INFO] [INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @ mojo-parent --- [INFO] [INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @ mojo-parent <<< [INFO] 'process-classes' forked phase execution for maven-plugin-plugin:report report preparation done [INFO] 1 report detected for maven-plugin-plugin:3.6.0: report [INFO] configuring report plugin org.apache.maven.plugins:maven-changes-plugin:2.11 [INFO] 1 report configured for maven-changes-plugin:2.11: github-report [INFO] configuring report plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.16 [INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle [INFO] configuring report plugin org.apache.maven.plugins:maven-javadoc-plugin:3.2.0 [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.144 s [INFO] Finished at: 2020-05-24T11:50:11+02:00 [INFO] Final Memory: 30M/128M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on project mojo-parent: Execution default-site of goal org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-site-plugin:3.9.0:site: java.lang.NoSuchMethodError: 'java.lang.Object org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()' [ERROR] - [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0 [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy [ERROR] urls[0] = file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.9.0/maven-site-plugin-3.9.0.jar This can be reproduced with 3.0.5 up to 3.6.1. Versions 3.6.2 and 3.6.3 are working fine. This means using maven-site-plugin 3.9.0 only working with Maven 3.6.2+ ...in contradiction to the site[1] which says it is requirement 3.0.. Or has someone a different explanation for this? Kind regards Karl Heinz Marbaise [1]: https://maven.apache.org/plugins/maven-site-plugin/plugin-info.html - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Wagon version 3.4.1
+1 On Sat, 23 May 2020 at 05:45, Michael Osipov wrote: > Hi, > > We solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12348210 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1576/ > > https://repository.apache.org/content/repositories/maven-1576/org/apache/maven/wagon/wagon/3.4.1/wagon-3.4.1-source-release.zip > > Source release checksum(s): > wagon-3.4.1-source-release.zip > sha512: > > 342d3ad88ba3535a0b6cafcfebd3f5b2e0fc6ac4022bebcea78a60703b0c611232e765ea87fb98ada0dc5daf1a9002e9bf7959571eebc4c974efda042246999c > > Staging site: > https://maven.apache.org/wagon-archives/wagon-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: next level of compatibility (was Re: [maven-site] branch master updated: few precisions)
Am 2020-05-24 um 10:41 schrieb Olivier Lamy: On Sat, 23 May 2020 at 21:33, Robert Scholte wrote: As discussed before: compatibility should either be 3.3.1 (since 3.3.0 didn't make it) or 3.5.0, we should not include the (highest) bugfix version. Great this means we can can rid of this hackhish refection stuff for aether... you mean we should support 3.3.1 3.3.3 and 3.3.9? by support I mean fixing security issues. so in this case what happen in case of a security issue for 3.3.1 do we have a to release 3.3.1.1 3.3.3.1 3.3.9.1 Not sure I understand what we mean with support? anyway if we say all plugins must be at least 3.3.1 it's good progress I think we have discussed this before as I have raised this at least once this one. The upshot is that we try to support (in terms of API and ABI) in Plugins and Components a huge variety of Maven versions, but only the last stable minor branch of Maven receives fixes. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: next level of compatibility (was Re: [maven-site] branch master updated: few precisions)
On Sat, 23 May 2020 at 21:33, Robert Scholte wrote: > As discussed before: compatibility should either be 3.3.1 (since 3.3.0 > didn't make it) or 3.5.0, we should not include the (highest) bugfix > version. > Great this means we can can rid of this hackhish refection stuff for aether... you mean we should support 3.3.1 3.3.3 and 3.3.9? by support I mean fixing security issues. so in this case what happen in case of a security issue for 3.3.1 do we have a to release 3.3.1.1 3.3.3.1 3.3.9.1 Not sure I understand what we mean with support? anyway if we say all plugins must be at least 3.3.1 it's good progress > Robert > > > On 23-5-2020 12:43:35, Arnaud Héritier wrote: > +1 > > On Sat, May 23, 2020 at 11:13 AM Enrico Olivelli > wrote: > > > +1 > > > > Enrico > > > > Il Sab 23 Mag 2020, 09:40 Sylwester Lachiewicz ha > > scritto: > > > > > +1 > > > > > > sob., 23 maj 2020, 09:22 użytkownik Hervé BOUTEMY > > > > > > napisał: > > > > > > > Le vendredi 22 mai 2020, 02:13:16 CEST Olivier Lamy a écrit : > > > > > > + * discussions on Maven > 3.0.x (3.1 or 3.2 or 3.3? details > still > > > > TDB) + > > > > > > Java 8 prerequisites > > > > > > > > > > Don't be shy Hervé we can definitely says >= 3.3.9 (at least you > will > > > not > > > > > hear any objections from me :) ) > > > > > > > > looking at our history https://maven.apache.org/docs/history.html, > > there > > > > is 1 > > > > year between 3.1.max and 3.2.max then 1 year to 3.3.max: not so much > > > > and AFAIK, many people went from 3.0 to 3.3+ > > > > > > > > looks a good idea to me: +1 > > > > > > > > any objection? > > > > > > > > Regards, > > > > > > > > Hervé > > > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > > > > > > > -- > - > Arnaud Héritier > http://aheritier.net > Mail/GTalk: aheritier AT gmail DOT com > Twitter/Skype : aheritier > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
