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?
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
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:
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
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
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
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
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!
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
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
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/
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
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
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
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
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
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
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
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
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
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
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:
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
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
+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:
>
>
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
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
27 matches
Mail list logo
