wicketstuff/core

First release with Wicket 10?

ilgrosso opened this issue · 23 comments

ilgrosso commented

Now that Wicket 10.0.0-M1 is out, any chance to cut a relase from the master branch here?

solomax commented

I can create release in a couple of weeks
Currently on vacation :))

  • 👍1
ilgrosso commented

Sure, thank you @solomax !

reiern70 commented
martin-g commented

@reiern70 Do you volunteer ? :-)
Several other devs have the credentials but lack the time and/or desire.

reiern70 commented

@reiern70 Do you volunteer ? :-) Several other devs have the credentials but lack the time and/or desire.

Yes. This week I can do :-)

  • 👍1
reiern70 commented

@reiern70 Do you volunteer ? :-) Several other devs have the credentials but lack the time and/or desire.

This is perfectly understandable. I think only other fellow open source developers can understand this. And again many thanks to all of you for the countless hours you have spent away from family fixing problems for people (companies) that many times do not properly say thanks! More and more I'm convinced that people do not value what they get for free and no efforts ;-) And I;m refering not only to software

  • ❤️1
martin-g commented

I haven't released Wicketstuff core in many years but you could try with:

JAVA_HOME=$JAVA_17_HOME mvn clean release:clean release:prepare release:perform -Dgpg.passphrase=YOUR_GPG_PASS_PHRASE
solomax commented

No need to specify java-home :)
Toolchain will select correct version :)

Release process is described here: https://github.com/wicketstuff/core/wiki/Wicket-Stuff-Core-Release-Process

  • 👍1
bitstorm commented
solomax commented

Hello All

I'm back :)))

It seem there is a blocker for this release: <wicket-webjars.version>4.0.0-SNAPSHOT</wicket-webjars.version>

@martin-g maybe you can release wicket-webjars :)))

martin-g commented

Doing it!

martin-g commented

Done!

solomax commented

Another blocker seems to be:
./portlet-parent/wicketstuff-portlet/pom.xml

                <dependency>
                        <!-- FIXME TODO temporary, wicket version doesn't have `portlet` -->
                        <groupId>org.apache.commons</groupId>
                        <artifactId>commons-fileupload2</artifactId>
                        <version>2.0-SNAPSHOT</version>
                        <exclusions>
                                <exclusion>
                                        <groupId>javax.portlet</groupId>
                                        <artifactId>portlet-api</artifactId>
                                </exclusion>
                        </exclusions>
                </dependency>

I'm afraid the only option here is to wait for commons-fileupload :(

hopefully it will be released this week ..... :(

Alternatively I can turn off portlet-parent for M1 ....

WDYT?

martin-g commented

Alternatively I can turn off portlet-parent for M1 ....

Does anyone still use Portlets ?!

solomax commented

To be fair I have no idea what portlets is :)))

Are you proposing to drop them from master all-together?

  • 👍1
martin-g commented

I'm 99.9% certain no one would complain about it!

  • 👍1
solomax commented

OK :)
Let's drop it :)))

  • 👍1
solomax commented

I'm going to create release notes using git shortlog -n wicketstuff-core-9.14.0..wicketstuff-core-10.0.0-M1

Is this OK?

martin-g commented

Yes!

reckart commented

@solomax do you know the release notes generation feature in GitHub itself?

solomax commented

@reckart no :)
I'm following release process as described in wiki :)

BTW most changes are done without PR or GH issue, so they will not get into generated notes ....

reckart commented

Yea... when using PRs consistently, GitHub can actually generate quite nice release notes. I'm using that nowadays quite happily for my release notes needs ;)