+1
On Wed, 22 Apr 2020 at 15:44, Michael Osipov wrote:
> Hi,
>
> We solved 15 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12346512
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2
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, unlike every
other Maven parent POMs that are in org.apache.maven
Then during staging, they go in a separate staging area.
And given nobody ca
Hi,
Any speed up is welcomed.
Now I have to admit I wondered why targetting only archives.
If an archive does not need to be rebuilt it means nothing changes in the
module+its dependencies so means you can bypass the module completely
instead of bypassing just part of it, no?
Romain Manni-Bucau
well I kind of agree but as it can be a complicated change to implement
(probably generate some bugs).
Even if users still have the option to change the plugin version, I would
leave an option to the user to deactivate it in case of major bug because
honestly assembly is not the easiest one
Assuming it produces the same binaries (and that's sort of the point
of this, right?) IMHO it should not be optional. Every option is an
additional thing to document and test, and in this case, for no
particular user benefit. If you can make the code noticeably faster
while producing the same outpu
Merci Hervé, I was actually referring to the Central deployment. Nothing
in (5,30) and (30,) has been deploy to Central, but the rest of the
reactor is in Central. This looks wrong to me.
See:
https://repo.maven.apache.org/maven2/org/apache/apache/resources/apache-resource-bundles/
Michael
