SHA512 ok, successful local build
but an Error in ASF build #38 and #39 with the last two commits from
maven-release-plugin but not from the #37.
Pls have a look into this:
https://builds.apache.org/job/maven-box/job/maven-wagon/job/master/39/testReport/junit/org.apache.maven.wagon.providers.http/
I did a quick review of the various components in core
and StringVisitorModelInterpolator / StringSearchModelInterpolator appears
to be the only case where a role (ModelInterpolator) has two non-default
implementations and another component only asks for the first
implementation. There are other ro
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12345956&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC
Well I have a new candidate:
maven-bundle-plugin
Creates: Bnd-LastModified in the MANIFEST.MF
Gotta find out a way to either suppress that entry (Would be great if it could
consume the same property)
Chris
Am 03.11.19, 20:25 schrieb "herve.bout...@free.fr" :
ok, Reproducible Builds a
ok, Reproducible Builds are not so easy to get: each plugin that you use can
cause an issue
I really recommend you diffoscope to investigate differences, it really helps a
lot by easily giving you precise differences
Good luck for the investigations :)
Regards,
Hervé
- Mail original
Hi Herve,
unfortunately I now have implemented some tooling to compare the stuff produced
by the updated reproducible builds.
And it does show quite a number of non binary equal files.
Will investigate what's the difference.
Chris
Am 03.11.19, 11:08 schrieb "Hervé BOUTEMY" :
great feed
Hi Hervé:
I was thinking in the lines of some checking at the maven core level only,
enough to detect problems and ensure there are no regressions.
At the plugin level, I guess the assurance that the right component is
injected can be checked with an integration test.
The way I realized the prob
Raised PR with unit test and integration test included:
https://github.com/apache/maven-javadoc-plugin/pull/34
This is my first PR for any of the maven project. Although I made my best
effort to follow all the coding conventions, surely there will be something
missing. So feel free to point out.
The Apache Maven team is pleased to announce the release of the Apache Maven
JAR Plugin, version 3.2.0
This plugin provides the capability to build jars.
https://maven.apache.org/plugins/maven-jar-plugin/
You should specify the version in your project's plugin configuration:
org.apache.ma
The Apache Maven team is pleased to announce the release of the Apache Maven
Assembly Plugin, version 3.2.0
This plugin is primarily intended to allow users to aggregate the project
output along with its dependencies, modules, site documentation, and other
files into a single distributable arch
The Apache Maven team is pleased to announce the release of the Apache Maven
JAR Plugin, version 3.2.0
This plugin provides the capability to build jars.
https://maven.apache.org/plugins/maven-jar-plugin/
You should specify the version in your project's plugin configuration:
org.apache.ma
The Apache Maven team is pleased to announce the release of the Apache Maven
Source Plugin, version 3.2.0
This plugin creates a jar archive of the source files of the current project.
https://maven.apache.org/plugins/maven-source-plugin/
You should specify the version in your project's plugin c
Hi,
I'm working on Struts Archetypes [1] and discovered that running:
mvn clean install archetype:update-local-catalog
will create/update "~/.m2/repository/archetype-catalog.xml" but using command:
mvn archetype:generate -DarchetypeCatalog=local
reads data from "~/.m2/archetype-catalog.xml
As Hervé noted, much of this is the way Maven (and Plexus) has always
behaved - the core defines component roles that plugins/extensions can
implement. There will typically be a core implementation (sometimes named
as the default, but not always) but that implementation can be
overridden by impleme
https://builds.apache.org/job/maven-box/job/maven-compiler-plugin/
[https://builds.apache.org/job/maven-box/job/maven-compiler-plugin/]
master is blue...
On 2-11-2019 11:19:42, GitBox wrote:
eolivelli commented on issue #1: [MCOMPILER-320] Introduce
additionalClasspathElements property
URL:
h
great feedback, thank you: this proves the initial set of only 3 plugins is a
good basis.
For checking the many output artifacts from a build, future buildinfo file [1]
should help a lot. I still have many usability concerns for Maven multi-module
builds (starting with: should we generate only t
thanks.
Created: https://issues.apache.org/jira/browse/MJAVADOC-628
Max
On Sun, Nov 3, 2019 at 4:51 AM Enrico Olivelli wrote:
> Hi Max.
> sorry for late reply.
>
> I think your idea is interesting and you work is valuable,
> You can follow up by creating a JIRA in issues.apache.org in MJAVADOC
nice idea, but overriding by adding a new implementation in classpath is the
normal overriding way: not sure how "ambiguity checker" could make a difference
between such wanted override vs unwanted ambiguity
BTW, how did you see that StringVisitorModelInterpolator was not used but
StringSearchM
Hi,
The vote has passed with the following result:
+1 : Sylwester Lachiewicz, Karl Heinz Marbaise, Enrico Olivelli, Tibor Digana,
Hervé Boutemy
PMC quorum reached
I will promote the artifacts to the central repo.
-
To unsub
Hi,
The vote has passed with the following result:
+1 : Olivier Lamy, Karl Heinz Marbaise, Sylwester Lachiewicz, Hervé Boutemy,
Tibor Digana,
PMC quorum reached
I will promote the artifacts to the central repo.
-
To unsubs
Hi,
The vote has passed with the following result:
+1 : Olivier Lamy, Romain Manni-Bucau, Tibor Digana, Hervé Boutemy, Karl Heinz
Marbaise, Sylwester Lachiewicz
PMC quorum reached
I will promote the artifacts to the central repo.
-
here is my +1
Regards,
Hervé
Le mardi 29 octobre 2019, 23:10:46 CET Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 9 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220&ve
> rsion=12344773&styleName=Text
>
> Staging repo:
> https://repository.apache.org/content/rep
22 matches
Mail list logo