by first finishing the migration from svn [1] to Git
there are 2 key choices to deal with:
1. 1 Git repository per bundle = 4 to 6 Git repositories? Or only 1 Git
repository, with 1 multi-module build (and bundles versions consolidation)?
2. what name for the(se) Git repository(ies)?
The first
+1
checked that the build was reproducible: JDK 8 + CRLF => ok for 33 output files
FYI, from my Linux box, using the -source-release.zip, checked by running
following command:
rm DEPENDENCIES LICENSE NOTICE && mvn -Papache-release -Dgpg.skip -DskipTests
-Dmaven.javadoc.skip verify -e
> On 22 Apr 2020, at 02:42, Olivier Lamy wrote:
>
>>
>>
>> Should I be targeting my change at the assembly plugin or would it make
>> more sense to try and get this deeper into plexus-archiver? Do you have any
>> further advice where best to start??
>>
>
> Well you're hitting the real
Hi all,
When copying resources with filtering on, files are always overwritten even
when the filters have not changed. I’d like to change this such that repeated
filtering copies do not modify the destination file.
I’ve prepared a change to write the filtered content to a temporary file and
Hi Tibor,
I've just updated https://issues.apache.org/jira/browse/MGPG-79.
Hope this helps.
Best regards,
Falko
Am 24.04.2020 um 13:11 schrieb Tibor Digana:
Hi Falko,
Can you attach the Thread dump while the GPG plugin hangs?
This would simplify our work.
Thx
T
On Wed, Apr 15, 2020 at
The structure which I want is;
src/main/java
src/main/java11
src/main/java14
src/test/java
src/test/java11
src/test/java14
I'm wanting to create a java 1.8 jar, with java 11 LTS support and the
latest release java version supported. So newer projects can use
modules and older projects still have
Robert (?) wrote this page [0] about supporting MR-JAR files.
There're several approaches to the topic. It'd be nice, if the compiler- and
the jar-plugin would pick one by default or based on a directory layout
convention.
[0]:
I've been thinking about multirelease jars. First step is source layout.
Here's a strawman modeled after the jar layout.
We add a versions directory to the existing src directory. Inside the
versions directory one can have directories named 9, 10, 11, etc. for each
major Java version that has
Hi,
We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12346099
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MRESOLVER/issues?filter=allopenissues
Staging repo:
Folks,
I'd like to retry both for 3.7.0. Will rebase both for master and run
all ITs. If everything passes, can we merge then into master? Any
objections?
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
How am I then supposed to solve MASFRES-31?
Release Parent 35 w/o dropping staging repos?
M
Am 2020-04-22 um 19:04 schrieb Hervé BOUTEMY:
if that your point of interest, I can explain because I did last releases of
parent POMs
as you can see, apache-resource-bundles is in org.apache.apache,
Hi Falko,
Can you attach the Thread dump while the GPG plugin hangs?
This would simplify our work.
Thx
T
On Wed, Apr 15, 2020 at 10:45 PM Falko Modler wrote:
>
> Hi,
>
> I just tried to to sign the output of
> https://github.com/vackosar/gitflow-incremental-builder and I do not see
> this
Am 2020-04-22 um 07:44 schrieb Michael Osipov:
Hi,
We solved 15 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12346512
There are still a couple of issues left in JIRA:
Hi,
+1 from me.
Kind regards
Karl Heinz Marbaise
On 22.04.20 07:44, Michael Osipov wrote:
Hi,
We solved 15 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12346512
There are still a couple of issues left in JIRA:
Hearing no objections, so I'll merge this to master
Robert
On 20-4-2020 20:44:19, Robert Scholte wrote:
I have reviewed MNG-6863 and want to merge it into master but want someone to
second that.
It contains the next set of improvements regarding --resume-from:
MNG-6863: -rf combined with -am
+1
On 22-4-2020 07:44:48, Michael Osipov wrote:
Hi,
We solved 15 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12346512
There are still a couple of issues left in JIRA:
marking a plugin parameter as read-only is a choice of the plugin developer,
who does not consider configuration as a provided plugin/goal feature, but
wants to inject default values that are consistent with other POM configuration
if you think the plugin needs to be improved to be more
17 matches
Mail list logo