I'm working on a verbose tree serializer in maven-dependency-plugin and
have the dependency management messages like "scope managed from compile"
working but I can't find documentation on why "scope not updated to
compile" messages show up. Line 24 of this test's expected.txt shows this.
thanks Falko, I've been able to raise the PR to enhance a plugin now.
John
On Sat, 25 Jul 2020 at 21:37, Falko Modler wrote:
>
> Inject the MavenSession:
>
> @Parameter(defaultValue ="${session}", readonly = true)
> private MavenSession mavenSession;
>
> and then:
>
>
Hi all,
My team have been using the Maven Invoker Plugin’s run goal to package some
sample test projects during pre-integration-test which we then use during
integration tests. We’re not using it to test a maven plugin but it doesn’t
feel like we’re straying very far from the intended use
The Apache Maven team is pleased to announce the release of the Apache
Maven Dependency Analyzer Plugin, version 1.11.2
This plugin analyzes the dependencies of a project for undeclared and
unused artifacts.
https://maven.apache.org/shared/maven-dependency-analyzer/
You should specify the
elharo opened a new pull request #185:
URL: https://github.com/apache/maven-site/pull/185
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 opened a new pull request #186:
URL: https://github.com/apache/maven-site/pull/186
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
garydgregory commented on pull request #32:
URL: https://github.com/apache/maven-site-plugin/pull/32#issuecomment-665593051
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
elharo merged pull request #185:
URL: https://github.com/apache/maven-site/pull/185
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
elharo merged pull request #186:
URL: https://github.com/apache/maven-site/pull/186
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
garydgregory edited a comment on pull request #32:
URL: https://github.com/apache/maven-site-plugin/pull/32#issuecomment-665593051
This is an automated message from the Apache Git Service.
To respond to the message, please
garydgregory removed a comment on pull request #32:
URL: https://github.com/apache/maven-site-plugin/pull/32#issuecomment-665593791
> please add exclusions for artifacts that are not Java 7 compatible - to
prevent spam about not possible upgrades
Why would this repo care about Java
Version 1.11.2 of maven-dependency-analyzer is now available on Maven
Central. I'm trying to generate an official announcement. However the
changes plugin keeps timing out when trying to load the issues from
Jira:
[ERROR] Failed to execute goal
On 2020-07-29T12:22:33 +0200
Michael Osipov wrote:
>
> I think your usage is correct. Maybe the docs aren't sharp enough saying
> that those case just examples which require a provided scope. You can,
> of course, improve the docs in such a fashion.
> Out of couriosity, can you give you can
OK, got through that. I needed to switch to a different computer with
the credentials.
On Wed, Jul 29, 2020 at 11:07 AM Elliotte Rusty Harold
wrote:
>
> I've gotten as far as step 2 of Promote the release, "Deploy the
> current website " but when I runmvn scm-publish:publish-scm I get
> the
+1 from me,
Those interested in the improvement of the release process docs are welcome
to discuss it in JIRA:
https://issues.apache.org/jira/browse/MNGSITE-419
Dennis Lundberg
Den fre 24 juli 2020 kl 16:08 skrev Dennis Lundberg :
> Hi,
>
> We solved 12
>
I've gotten as far as step 2 of Promote the release, "Deploy the
current website " but when I runmvn scm-publish:publish-scm I get
the below error message. Is this also something that needs to be done
by the PMC?
[ERROR] Failed to execute goal
Well the use case appears to be the same as Gradle’s compileOnly, which as the
name states, it’s used for compilation only and it’s not required for
execution. Also, dependencies set in compileOnly are never exported to
consumers, so in a way, with current Maven semantics Gradle’s compileOnly
Am 2020-07-29 um 12:18 schrieb Elliotte Rusty Harold:
Per Maven docs provided scope "is much like compile, but indicates you
expect the JDK or a container to provide the dependency at runtime.
For example, when building a web application for the Java Enterprise
Edition, you would set the
Per Maven docs provided scope "is much like compile, but indicates you
expect the JDK or a container to provide the dependency at runtime.
For example, when building a web application for the Java Enterprise
Edition, you would set the dependency on the Servlet API and related
Java EE APIs to scope
Hi Elliot,
can you please make a forward to
"Maven Project Management Committee List"
as mentioned in
https://maven.apache.org/developers/release/maven-project-release-procedure.html
Furthermore currently the repository in repository.apache.org is not yet
released ...
Kind regards
Karl
elharo merged pull request #183:
URL: https://github.com/apache/maven-site/pull/183
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
slachiewicz commented on pull request #32:
URL: https://github.com/apache/maven-site-plugin/pull/32#issuecomment-665079696
please add exclusions for artifacts that are not Java 7 compatible - to
prevent spam about not possible upgrades
elharo opened a new pull request #33:
URL: https://github.com/apache/maven-site-plugin/pull/33
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
slachiewicz commented on pull request #33:
URL: https://github.com/apache/maven-site-plugin/pull/33#issuecomment-665078752
please put a surefire version in a commit message - it will be easier to see
that has changed in this commit (without looking into diff)
24 matches
Mail list logo
