On 12 Nov 2017, at 23:06, Stephen Connolly wrote:
> That could end up duplicating the local repo cache... unless we default the
> cache to ~/.m2/repository anyway... otoh a concurrency safe local repo
> cache may mandate a new location... but double the downloads for inter-op
> with older Maven in
hboutemy closed pull request #1: Fix typos in AbstractJxrReport.
URL: https://github.com/apache/maven-jxr/pull/1
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (f
hboutemy commented on issue #1: Fix typos in AbstractJxrReport.
URL: https://github.com/apache/maven-jxr/pull/1#issuecomment-343755961
merged in
https://github.com/apache/maven-jxr/commit/b1bc166e6335f1526ef902f49ab59b32f3475ab1
thank you
On 2017-11-12T15:15:49 +0100
"Robert Scholte" wrote:
> MJAVADOC-475 is about replacing a parameter, which makes it as critical as
> MJAVADOC-457.
> We just consider 3.0.0 to be THE version to be able to do a cleanup, hence
> MJAVADOC-475 must be fixed as well.
>
> The good news is: MJAVADOC-
bhav0904 opened a new pull request #1: Fix typos in AbstractJxrReport.
URL: https://github.com/apache/maven-jxr/pull/1
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub
Hi,
This is the initial release of the Maven JDeprScan Plugin.
It is a wrapper around the jdeprscan tool, available since Java 9:
https://docs.oracle.com/javase/9/tools/jdeprscan.htm
There are zero issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MJDEPRSCAN%20AND%
MJAVADOC-475 is about replacing a parameter, which makes it as critical as
MJAVADOC-457.
We just consider 3.0.0 to be THE version to be able to do a cleanup, hence
MJAVADOC-475 must be fixed as well.
The good news is: MJAVADOC-457 and MJAVADOC-475 are finished. I don't see
any deprecated pa
Hi,
I like the idea of simplification: I just factorized mavenVersion property to
parent pom.
I have only one fear: what happens when the API changes in an incompatible way
then we must release maven-artifact-resolver, then maven-resolver provider,
then ant-tasks and demos.
AFAIK, this chicke
'Ello.
On 2017-11-11T14:40:16 +0100
"Robert Scholte" wrote:
> I'd hope to do a release this month. Not sure if it'll be a M2 or not,
> depends if all 3.0.0 prerequisites are met.
Right.
From what I can see, only MJAVADOC-475 is not really *critical* to the
release as it's just a new feature.
Keep in mind, Maven is not the only pom consumer. Expression changes
outside the pom are probably fine. Expression changes inside the pom will
probably require the 4.0.0 (optional scope) feature to bring flatten Maven
plugin type features to first class core support (ie deploy the pom with
new prop
On Sun 12 Nov 2017 at 07:41, Chris Graham wrote:
> required:
> - *everything* in settings.xml can be put in a profile section in
> settings.xml.
>
> I often move around/between projects and having to redo mirrors section,
> and unable to add servers into the profile section for clarity is a pain
11 matches
Mail list logo
