this vote passes. Thank you all!
On 13/09/2018 23:40, Sven Meier wrote:
+1 checked checksum and random examples
Sven
Am 13.09.2018 um 13:14 schrieb Andrea Del Bene:
+1 to release. Checked tutorial examples and randomly some Wicket
examples.
On Wed, Sep 12, 2018 at 12:19 PM Andrea Del
+1 checked checksum and random examples
Sven
Am 13.09.2018 um 13:14 schrieb Andrea Del Bene:
+1 to release. Checked tutorial examples and randomly some Wicket examples.
On Wed, Sep 12, 2018 at 12:19 PM Andrea Del Bene
wrote:
It's an issue with maven-jetty-plugin:
+1 to release
checked:
- local build
- random wicket-examples
- build wicket-jquery-selectors, wicket-webjars and wicket-bootstrap
The only minor problem that I've found is :
Caused by: java.lang.IllegalArgumentException: A Cookie name can not be
null or empty
at
+1 - :-)
kind regards
Tobias
> Am 13.09.2018 um 13:38 schrieb Emond Papegaaij :
>
> Agreed, that's why I did not vote yet
>
> +1 to release. Checked the source for release errors and checked the hashes.
> Also did a build locally and it was fine (except for jetty:run).
>
> Emond
>
>> On
Agreed, that's why I did not vote yet
+1 to release. Checked the source for release errors and checked the hashes.
Also did a build locally and it was fine (except for jetty:run).
Emond
On woensdag 12 september 2018 12:19:38 CEST Andrea Del Bene wrote:
> It's an issue with maven-jetty-plugin:
+1 to release. Checked tutorial examples and randomly some Wicket examples.
On Wed, Sep 12, 2018 at 12:19 PM Andrea Del Bene
wrote:
> It's an issue with maven-jetty-plugin:
> https://stackoverflow.com/questions/44848409/cdi-invalid-bean-archive-scanning-in-jetty-not-in-tomcat.
> It should
It's an issue with maven-jetty-plugin:
https://stackoverflow.com/questions/44848409/cdi-invalid-bean-archive-scanning-in-jetty-not-in-tomcat.
It should affect 8.0.0 as well, I will check it. IMHO is not a blocking
issue.
On Wed, Sep 12, 2018 at 10:20 AM Emond Papegaaij
wrote:
> Hi,
>
> I'm
Hi,
I'm trying to test the examples, but all I get is '503 Service Unavailable'
and several stacktraces in the terminal:
java.lang.IllegalStateException: WELD-ENV-33: Invalid bean archive
scanning result - found multiple results with the same reference: /home/
Ok, I just seen your commit for rg.apache:apache:21 parent pom which
addresses this issue.
On Tue, Sep 11, 2018 at 12:19 PM Andrea Del Bene
wrote:
> 100% agree. Distribution files have been already upgraded from md5 to
> sha256. We have to find the way to tell Maven what algorithm we want to
100% agree. Distribution files have been already upgraded from md5 to
sha256. We have to find the way to tell Maven what algorithm we want to use.
On Tue, Sep 11, 2018 at 10:46 AM Martin Grigorov
wrote:
> Hi,
>
> I see Maven still produces .md5 and .sha1 files: that
>
>
Hi,
I see Maven still produces .md5 and .sha1 files: that
https://repository.apache.org/content/repositories/orgapachewicket-1112/org/apache/wicket/wicket-core/8.1.0/
I don't think this is a blocker but we should see how to improve it (drop
.md5 and produce .sha256 or .sha512 instead of .sha1).
This is a vote to release Apache Wicket 8.1.0
Please download the source distributions found in our staging area
linked below.
I have included the signatures for both the source archives. This vote
lasts for 72 hours minimum.
[ ] Yes, release Apache Wicket 8.1.0
[ ] No, don't release Apache
12 matches
Mail list logo
