+1
On 5-1-2020 18:45:55, Hervé BOUTEMY wrote:
Hi,
We solved N issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12343925=Text
https://github.com/apache/maven-apache-parent/compare/apache-21...apache-22
Staging repo:
Hi,
+1 from me.
Kind regards
Karl Heinz Marbaise
On 05.01.20 18:45, Hervé BOUTEMY wrote:
Hi,
We solved N issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12343925=Text
https://github.com/apache/maven-apache-parent/compare/apache-21...apache-22
Staging repo:
+1 (non binding)
Enrico
Il dom 5 gen 2020, 19:48 Mark Struberg ha
scritto:
> +1
>
> LieGrue,
> strub
>
>
> > Am 05.01.2020 um 18:45 schrieb Hervé BOUTEMY :
> >
> > Hi,
> >
> > We solved N issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12343925=Text
> >
Hi,
On 05.01.20 19:33, Benjamin Marwell wrote:
Hi,
thanks for sharing your idea. While I can see the benefits, I also do see
some drawbacks.
If only one part of the plugin has an invalid state, it will be impossible
to create a release.
Also, the Unix philosophy (make a tool which does one
> We have tens of plugins, most of them are rarely updated and released
... is the key problem you're trying to solve right?
Team to actively process issues and PRs and push releases minor releases
efficiently is the real wish, right?
+1
LieGrue,
strub
> Am 05.01.2020 um 18:45 schrieb Hervé BOUTEMY :
>
> Hi,
>
> We solved N issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12343925=Text
>
> https://github.com/apache/maven-apache-parent/compare/apache-21...apache-22
>
> Staging repo:
>
Hi,
thanks for sharing your idea. While I can see the benefits, I also do see
some drawbacks.
If only one part of the plugin has an invalid state, it will be impossible
to create a release.
Also, the Unix philosophy (make a tool which does one thing well) would be
broken.
If voting is a
I understand the issue you're trying to solve, but I don't think it is the
right solution.
To me a plugin contains a number of goals that are related to each other.
If there are issues, they are very easy to pinpoint.
If we start with with a monolithic plugin, you'll likely introduce more issues.
If you want to execute a plugin goal apart from a lifecycle, then I think it
should be for only one module.
So I'd expect the call more to be like -pl module -am
That said, if you know you want to execute this goal for 1 specific module, I
would like to be able to start from that pom and run
Hi,
We solved N issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12343925=Text
https://github.com/apache/maven-apache-parent/compare/apache-21...apache-22
Staging repo:
https://repository.apache.org/content/repositories/orgapacheapache-1017/
Hi Herve,
he'll only get the same content if everything is done right ... unfortunately
for example the IoTDB project had to re-do quite a number of RCs as they were
still not 100% doing things the maven way.
In PLC4X we just had to cancel a release of a sub-project due to the
notice that with Reproducible Builds being active by default, the source
archive is reproducible and RM will get the same content in both locations
There is only the .asc signature file that contains a different timestamp
I'm just launching the long overdue Apache Parent 22 vote that will
Hi Enrico
Technically concatenating all goals for all modules will do it but will be
quite long - guess it is why we do it in 2 times.
That said i always wondered why maven can read commands from a file/stdin
as any unix like soft so it would be something like:
mvn --commands-file ci.cmdlist
Hi community,
I just want to share this idea, maybe it is silly but why not talk about it.
We have tens of plugins, most of them are rarely updated and released.
So it happens that users contribute patches in order to fix real problems
but they have to wait an indefinite time before seeing the
Hello,
Sometimes it happens that you have to launch twice Maven to:
- build a whole reactor project (warmup)
- run some specific mojo only a selection of modules
mvn clean install -DskipTests -Dmaven.repo.local=tmprepo
mvn do:something -pl module1,module1-Dmaven.repo.local=tmprepo
I think that
You might want to take a peek at what we do over at Apache Commons. We have
attempted to make things easier for ourselves with two custom Maven plugins
but IMO it is still error prone and a pain. Some of the pain is due to
having to perform a "double release" by pushing various files to both Nexus
Hi Robert,
I would be more than happy to assist with making releases with maven easier for
Apache projects ...
So if you give me a little update on what needs to be done, I might be able to
spare some time and work on this.
But using the files from the prepare is the issue I'm trying to
ASF deserves a customized release strategy, which is now possible with
MRELEASE-956
My idea is that during "prepare" the plugin should upload several files to the
ASF dist folder besides the tagging.
During "perform" it should use these files instead of the tag in SCM (because
these files are
Hi all,
I just wanted to suggest something I have noticed a lot of Apache projects were
doing wrong. Especially when unexperienced RMs are doing the releases.
Several times now after doing a release, the RMs have uploaded the source
bundles from “target” to the SVN. However they should have
19 matches
Mail list logo
