It looks a bit like MRELEASE-798[1] and MRELEASE-962[2]
For the 3.0.0 already a lot of refactoring has been done, so it should be
easier to add such a feature.
I haven't thought about the implementation details, only that some hook or
extension should be able to become part of the release
Il gio 3 ott 2019, 17:53 Anthony Whitford ha scritto:
> Wouldn’t it make more sense to hook into the generate-sources or
> process-sources phase?
>
In this case I can't because C sources must be buildable even without maven
Enrico
> I would also think that the need to do that token
Wouldn’t it make more sense to hook into the generate-sources or
process-sources phase?
I would also think that the need to do that token replacement to set the
version applies for any build — not just the release process.
> On Oct 3, 2019, at 8:13 AM, Enrico Olivelli wrote:
>
> Hello,
> I
Hello,
I am going to propose a new release procedure in Apache ZooKeeper project
in the direction of using the Maven Release Plugin.
Usually with the Maven Release Plugin you are performing to tasks:
mvn release:prepare -> change version + create tag
mvn release:perform -> create final artifacts
Hi,
first thanks...
I have several question regarding your blog post ...
Apart from beeing not accurate in some part I miss one very important thing:
What is the real problem when doing a release via release plugin etc.
which works well (I haven't said that it could be improved)...
I want to
Hi Debraj,
There is nice technical idea from Enrico.
If you apply it and you are convinced that it would work properly for all
the Java community, feel free to show it and we can discuss it on how we
would adopt your solution in Surefire project.
Cheers
Tibor17
On Thu, Oct 3, 2019 at 2:49 PM
Hi,
you can create a simple Listener like this one:
https://github.com/apache/bookkeeper/blob/master/bookkeeper-common/src/test/java/org/apache/bookkeeper/common/testing/util/TimedOutTestsListener.java
check on the pom.xml file about how to enable it:
Hello Maven Dev & Community
Sine a long time I thought, it would be cool to have a well defined process to
prepare a release of an artifact and deploy it on mvn central. Now I got a bit
time to formulate a short proposal of my idea. I published a description of my
thought on my bolg:
Sometimes I have maven surefire tests that get hung, due to either races or
deadlocks.
When this happens I have to discover what slave is being used, and then I
have to log on that slave, sudo to jenkins account and execute either
jstack or kill -3
I am looking for a simple solution like doing
