You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fortress@directory.apache.org by Shawn McKinney <sm...@apache.org> on 2022/07/17 19:47:37 UTC
[VOTE] Apache Fortress 2.0.8 release
Hello,
This is an announcement to vote for the next release of Apache Directory Fortress, 2.0.8.
Here are the list of bugs and enhancements:
https://issues.apache.org/jira/projects/FC/versions/12351048
A tag created for git: ‘2.0.8', and the sources may be pulled using git commands:
git clone --branch 2.0.8 https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git
git clone --branch 2.0.8 https://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git
git clone --branch 2.0.8 https://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git
git clone --branch 2.0.8 https://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git
with their associated checksums:
- core: 137c2019218903a06da0522530251db4c942b111
- realm: 101e24e4e7758f67bbd992d6193a59934c73ffe3
- rest: b7de2edf30881eadcbe86ceb6f7cb90f78ccff3d
- web: a496b8dd3ca2f4421dca06f8604a8cd52a47becc
Or, source and binary distros may be downloaded from SVN:
- https://dist.apache.org/repos/dist/dev/directory/fortress/2.0.8/
The staging repo on Nexus:
- https://repository.apache.org/content/repositories/orgapachedirectory-1207
Test against LDAP using one of these:
- https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-APACHEDS.md
- https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-SLAPD.md
** OR (new) **
— https://gitlab.symas.net/symas-public/ansible-apache-fortress
- run plays:
```
ansible-playbook -i inventory slapd.yml
# OR:
ansible-playbook -i inventory apacheds.yml
# +:
ansible-playbook -i inventory fortress.yml
```
- [set host var fortress_version to 2.0.8](https://gitlab.symas.net/symas-public/ansible-apache-fortress/-/blob/master/ansible/inventory/group_vars/fortress.yml#L6)
***
- Choose one of the above. Complete (only) the sections leading up to and including the SECTION entitled: 'Apache Fortress Core Integration Test’
Please vote:
[ ] +1 | Release Fortress 2.0.8
[ ] +/-0 | Abstain
[ ] -1 | Do *NOT* Release Fortress 2.0.8
—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
Re: [RESULT][VOTE] Apache Fortress 2.0.8 release
Posted by Shawn McKinney <sm...@apache.org>.
Closing with 3 +1 binding votes. Emmanuel, Colm and I.
Will move the packages into distribution folders and update the website over the next couple of days.
Thanks
—
Shawn
> On Jul 21, 2022, at 5:06 AM, Colm O hEigeartaigh <co...@apache.org> wrote:
>
> Hi Shawn,
>
> I guess you could override the versions of the following jars to 5.3.22:
>
> [INFO] | +- org.springframework:spring-aop:jar:5.3.21:compile
>> [INFO] | +- org.springframework:spring-beans:jar:5.3.21:compile
>> [INFO] | +- org.springframework:spring-context:jar:5.3.21:compile
>> [INFO] | +- org.springframework:spring-expression:jar:5.3.21:compile
>> [INFO] | \- org.springframework:spring-web:jar:5.3.21:compile
>
> It's not ideal but otherwise there might be a small risk of
> incompatibility between spring-core 5.3.22 and the other 5.3.21 jars.
> Anyway I'll leave it up to you, if you're happy with it as it stands I
> am +1 on the release.
>
> Colm.
>
> On Wed, Jul 20, 2022 at 5:18 PM Shawn McKinney <sm...@apache.org> wrote:
>>
>>
>>> On Jul 20, 2022, at 8:43 AM, Shawn McKinney <sm...@apache.org> wrote:
>>>
>>> I’d need to be convinced that going with a previous version of spring security to match the core is advisable due to all of the CVE’s. In any case, there isn’t a a 5.3.22 spring core version.
>>
>> Err, the other way around. … There isn’t a spring security core version that matches up with spring core.
>>
>> Going with a previous spring security release means picking up CVE’s. As most of their previous releases are flagged with vulnerabilities:
>>
>> https://mvnrepository.com/artifact/org.springframework.security/spring-security-core
>>
>> Meaning we need to use the latest of each. What am I missing here?
>>
>> Thanks
>>
>> —
>> Shawn
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
>> For additional commands, e-mail: fortress-help@directory.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
> For additional commands, e-mail: fortress-help@directory.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
Re: [RESULT][VOTE] Apache Fortress 2.0.8 release
Posted by Shawn McKinney <sm...@apache.org>.
Closing with 3 +1 binding votes. Emmanuel, Colm and I.
Will move the packages into distribution folders and update the website over the next couple of days.
Thanks
—
Shawn
> On Jul 21, 2022, at 5:06 AM, Colm O hEigeartaigh <co...@apache.org> wrote:
>
> Hi Shawn,
>
> I guess you could override the versions of the following jars to 5.3.22:
>
> [INFO] | +- org.springframework:spring-aop:jar:5.3.21:compile
>> [INFO] | +- org.springframework:spring-beans:jar:5.3.21:compile
>> [INFO] | +- org.springframework:spring-context:jar:5.3.21:compile
>> [INFO] | +- org.springframework:spring-expression:jar:5.3.21:compile
>> [INFO] | \- org.springframework:spring-web:jar:5.3.21:compile
>
> It's not ideal but otherwise there might be a small risk of
> incompatibility between spring-core 5.3.22 and the other 5.3.21 jars.
> Anyway I'll leave it up to you, if you're happy with it as it stands I
> am +1 on the release.
>
> Colm.
>
> On Wed, Jul 20, 2022 at 5:18 PM Shawn McKinney <sm...@apache.org> wrote:
>>
>>
>>> On Jul 20, 2022, at 8:43 AM, Shawn McKinney <sm...@apache.org> wrote:
>>>
>>> I’d need to be convinced that going with a previous version of spring security to match the core is advisable due to all of the CVE’s. In any case, there isn’t a a 5.3.22 spring core version.
>>
>> Err, the other way around. … There isn’t a spring security core version that matches up with spring core.
>>
>> Going with a previous spring security release means picking up CVE’s. As most of their previous releases are flagged with vulnerabilities:
>>
>> https://mvnrepository.com/artifact/org.springframework.security/spring-security-core
>>
>> Meaning we need to use the latest of each. What am I missing here?
>>
>> Thanks
>>
>> —
>> Shawn
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
>> For additional commands, e-mail: fortress-help@directory.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
> For additional commands, e-mail: fortress-help@directory.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 21, 2022, at 5:06 AM, Colm O hEigeartaigh <co...@apache.org> wrote:
>
> I guess you could override the versions of the following jars to 5.3.22:
>
> [INFO] | +- org.springframework:spring-aop:jar:5.3.21:compile
>> [INFO] | +- org.springframework:spring-beans:jar:5.3.21:compile
>> [INFO] | +- org.springframework:spring-context:jar:5.3.21:compile
>> [INFO] | +- org.springframework:spring-expression:jar:5.3.21:compile
>> [INFO] | \- org.springframework:spring-web:jar:5.3.21:compile
>
> It's not ideal but otherwise there might be a small risk of
> incompatibility between spring-core 5.3.22 and the other 5.3.21 jars.
> Anyway I'll leave it up to you, if you're happy with it as it stands I
> am +1 on the release.
OK. I’ll look into it as item for the next release.
Thanks Colm!
—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 21, 2022, at 5:06 AM, Colm O hEigeartaigh <co...@apache.org> wrote:
>
> I guess you could override the versions of the following jars to 5.3.22:
>
> [INFO] | +- org.springframework:spring-aop:jar:5.3.21:compile
>> [INFO] | +- org.springframework:spring-beans:jar:5.3.21:compile
>> [INFO] | +- org.springframework:spring-context:jar:5.3.21:compile
>> [INFO] | +- org.springframework:spring-expression:jar:5.3.21:compile
>> [INFO] | \- org.springframework:spring-web:jar:5.3.21:compile
>
> It's not ideal but otherwise there might be a small risk of
> incompatibility between spring-core 5.3.22 and the other 5.3.21 jars.
> Anyway I'll leave it up to you, if you're happy with it as it stands I
> am +1 on the release.
OK. I’ll look into it as item for the next release.
Thanks Colm!
—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Colm O hEigeartaigh <co...@apache.org>.
Hi Shawn,
I guess you could override the versions of the following jars to 5.3.22:
[INFO] | +- org.springframework:spring-aop:jar:5.3.21:compile
> [INFO] | +- org.springframework:spring-beans:jar:5.3.21:compile
> [INFO] | +- org.springframework:spring-context:jar:5.3.21:compile
> [INFO] | +- org.springframework:spring-expression:jar:5.3.21:compile
> [INFO] | \- org.springframework:spring-web:jar:5.3.21:compile
It's not ideal but otherwise there might be a small risk of
incompatibility between spring-core 5.3.22 and the other 5.3.21 jars.
Anyway I'll leave it up to you, if you're happy with it as it stands I
am +1 on the release.
Colm.
On Wed, Jul 20, 2022 at 5:18 PM Shawn McKinney <sm...@apache.org> wrote:
>
>
> > On Jul 20, 2022, at 8:43 AM, Shawn McKinney <sm...@apache.org> wrote:
> >
> > I’d need to be convinced that going with a previous version of spring security to match the core is advisable due to all of the CVE’s. In any case, there isn’t a a 5.3.22 spring core version.
>
> Err, the other way around. … There isn’t a spring security core version that matches up with spring core.
>
> Going with a previous spring security release means picking up CVE’s. As most of their previous releases are flagged with vulnerabilities:
>
> https://mvnrepository.com/artifact/org.springframework.security/spring-security-core
>
> Meaning we need to use the latest of each. What am I missing here?
>
> Thanks
>
> —
> Shawn
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
> For additional commands, e-mail: fortress-help@directory.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Colm O hEigeartaigh <co...@apache.org>.
Hi Shawn,
I guess you could override the versions of the following jars to 5.3.22:
[INFO] | +- org.springframework:spring-aop:jar:5.3.21:compile
> [INFO] | +- org.springframework:spring-beans:jar:5.3.21:compile
> [INFO] | +- org.springframework:spring-context:jar:5.3.21:compile
> [INFO] | +- org.springframework:spring-expression:jar:5.3.21:compile
> [INFO] | \- org.springframework:spring-web:jar:5.3.21:compile
It's not ideal but otherwise there might be a small risk of
incompatibility between spring-core 5.3.22 and the other 5.3.21 jars.
Anyway I'll leave it up to you, if you're happy with it as it stands I
am +1 on the release.
Colm.
On Wed, Jul 20, 2022 at 5:18 PM Shawn McKinney <sm...@apache.org> wrote:
>
>
> > On Jul 20, 2022, at 8:43 AM, Shawn McKinney <sm...@apache.org> wrote:
> >
> > I’d need to be convinced that going with a previous version of spring security to match the core is advisable due to all of the CVE’s. In any case, there isn’t a a 5.3.22 spring core version.
>
> Err, the other way around. … There isn’t a spring security core version that matches up with spring core.
>
> Going with a previous spring security release means picking up CVE’s. As most of their previous releases are flagged with vulnerabilities:
>
> https://mvnrepository.com/artifact/org.springframework.security/spring-security-core
>
> Meaning we need to use the latest of each. What am I missing here?
>
> Thanks
>
> —
> Shawn
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
> For additional commands, e-mail: fortress-help@directory.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 20, 2022, at 8:43 AM, Shawn McKinney <sm...@apache.org> wrote:
>
> I’d need to be convinced that going with a previous version of spring security to match the core is advisable due to all of the CVE’s. In any case, there isn’t a a 5.3.22 spring core version.
Err, the other way around. … There isn’t a spring security core version that matches up with spring core.
Going with a previous spring security release means picking up CVE’s. As most of their previous releases are flagged with vulnerabilities:
https://mvnrepository.com/artifact/org.springframework.security/spring-security-core
Meaning we need to use the latest of each. What am I missing here?
Thanks
—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 20, 2022, at 8:43 AM, Shawn McKinney <sm...@apache.org> wrote:
>
> I’d need to be convinced that going with a previous version of spring security to match the core is advisable due to all of the CVE’s. In any case, there isn’t a a 5.3.22 spring core version.
Err, the other way around. … There isn’t a spring security core version that matches up with spring core.
Going with a previous spring security release means picking up CVE’s. As most of their previous releases are flagged with vulnerabilities:
https://mvnrepository.com/artifact/org.springframework.security/spring-security-core
Meaning we need to use the latest of each. What am I missing here?
Thanks
—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 20, 2022, at 2:53 AM, Colm O hEigeartaigh <co...@apache.org> wrote:
>
> I noticed in the rest project that there are two Spring versions:
>
> [INFO] +- org.springframework:spring-core:jar:5.3.22:compile
> [INFO] | \- org.springframework:spring-jcl:jar:5.3.22:compile
> [INFO] +- org.springframework.security:spring-security-web:jar:5.7.2:compile
> [INFO] | +- org.springframework.security:spring-security-core:jar:5.7.2:compile
> [INFO] | | \-
> org.springframework.security:spring-security-crypto:jar:5.7.2:compile
> [INFO] | +- org.springframework:spring-aop:jar:5.3.21:compile
> [INFO] | +- org.springframework:spring-beans:jar:5.3.21:compile
> [INFO] | +- org.springframework:spring-context:jar:5.3.21:compile
> [INFO] | +- org.springframework:spring-expression:jar:5.3.21:compile
> [INFO] | \- org.springframework:spring-web:jar:5.3.21:compile
>
> Not sure if it's worth aligning these to 5.3.22?
Colm,
Those are the latest dependencies for each.
I’d need to be convinced that going with a previous version of spring security to match the core is advisable due to all of the CVE’s. In any case, there isn’t a a 5.3.22 spring core version.
Or, did I misunderstand your intent here? Please advise.
In any case, part of the release process is to upgrade all dependencies to latest, which has been done here.
> Also I noticed all
> the repos have a NOTICE with a date range ending in 2018:
>
> Apache Fortress Rest
> Copyright 2003-2018 The Apache Software Foundation
Good catch. It’s been updated in the source repo.
—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 20, 2022, at 2:53 AM, Colm O hEigeartaigh <co...@apache.org> wrote:
>
> I noticed in the rest project that there are two Spring versions:
>
> [INFO] +- org.springframework:spring-core:jar:5.3.22:compile
> [INFO] | \- org.springframework:spring-jcl:jar:5.3.22:compile
> [INFO] +- org.springframework.security:spring-security-web:jar:5.7.2:compile
> [INFO] | +- org.springframework.security:spring-security-core:jar:5.7.2:compile
> [INFO] | | \-
> org.springframework.security:spring-security-crypto:jar:5.7.2:compile
> [INFO] | +- org.springframework:spring-aop:jar:5.3.21:compile
> [INFO] | +- org.springframework:spring-beans:jar:5.3.21:compile
> [INFO] | +- org.springframework:spring-context:jar:5.3.21:compile
> [INFO] | +- org.springframework:spring-expression:jar:5.3.21:compile
> [INFO] | \- org.springframework:spring-web:jar:5.3.21:compile
>
> Not sure if it's worth aligning these to 5.3.22?
Colm,
Those are the latest dependencies for each.
I’d need to be convinced that going with a previous version of spring security to match the core is advisable due to all of the CVE’s. In any case, there isn’t a a 5.3.22 spring core version.
Or, did I misunderstand your intent here? Please advise.
In any case, part of the release process is to upgrade all dependencies to latest, which has been done here.
> Also I noticed all
> the repos have a NOTICE with a date range ending in 2018:
>
> Apache Fortress Rest
> Copyright 2003-2018 The Apache Software Foundation
Good catch. It’s been updated in the source repo.
—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Colm O hEigeartaigh <co...@apache.org>.
Hi,
I noticed in the rest project that there are two Spring versions:
[INFO] +- org.springframework:spring-core:jar:5.3.22:compile
[INFO] | \- org.springframework:spring-jcl:jar:5.3.22:compile
[INFO] +- org.springframework.security:spring-security-web:jar:5.7.2:compile
[INFO] | +- org.springframework.security:spring-security-core:jar:5.7.2:compile
[INFO] | | \-
org.springframework.security:spring-security-crypto:jar:5.7.2:compile
[INFO] | +- org.springframework:spring-aop:jar:5.3.21:compile
[INFO] | +- org.springframework:spring-beans:jar:5.3.21:compile
[INFO] | +- org.springframework:spring-context:jar:5.3.21:compile
[INFO] | +- org.springframework:spring-expression:jar:5.3.21:compile
[INFO] | \- org.springframework:spring-web:jar:5.3.21:compile
Not sure if it's worth aligning these to 5.3.22? Also I noticed all
the repos have a NOTICE with a date range ending in 2018:
Apache Fortress Rest
Copyright 2003-2018 The Apache Software Foundation
Colm.
On Tue, Jul 19, 2022 at 3:36 PM Shawn McKinney <sm...@apache.org> wrote:
>
>
> > On Jul 19, 2022, at 8:30 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
> >
> > BTW, just noticed that fortress-commanderrequires Java 11, while the other components only require java 8. Is this intended?
>
> Emmanuel,
>
> Yes. The upgrade to latest Wicket v9 requires the jump to java 11.
>
> The others still happily run on 8 although the day is coming soon where that'll change.
>
> —
> Shawn
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
> For additional commands, e-mail: fortress-help@directory.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Colm O hEigeartaigh <co...@apache.org>.
Hi,
I noticed in the rest project that there are two Spring versions:
[INFO] +- org.springframework:spring-core:jar:5.3.22:compile
[INFO] | \- org.springframework:spring-jcl:jar:5.3.22:compile
[INFO] +- org.springframework.security:spring-security-web:jar:5.7.2:compile
[INFO] | +- org.springframework.security:spring-security-core:jar:5.7.2:compile
[INFO] | | \-
org.springframework.security:spring-security-crypto:jar:5.7.2:compile
[INFO] | +- org.springframework:spring-aop:jar:5.3.21:compile
[INFO] | +- org.springframework:spring-beans:jar:5.3.21:compile
[INFO] | +- org.springframework:spring-context:jar:5.3.21:compile
[INFO] | +- org.springframework:spring-expression:jar:5.3.21:compile
[INFO] | \- org.springframework:spring-web:jar:5.3.21:compile
Not sure if it's worth aligning these to 5.3.22? Also I noticed all
the repos have a NOTICE with a date range ending in 2018:
Apache Fortress Rest
Copyright 2003-2018 The Apache Software Foundation
Colm.
On Tue, Jul 19, 2022 at 3:36 PM Shawn McKinney <sm...@apache.org> wrote:
>
>
> > On Jul 19, 2022, at 8:30 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
> >
> > BTW, just noticed that fortress-commanderrequires Java 11, while the other components only require java 8. Is this intended?
>
> Emmanuel,
>
> Yes. The upgrade to latest Wicket v9 requires the jump to java 11.
>
> The others still happily run on 8 although the day is coming soon where that'll change.
>
> —
> Shawn
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
> For additional commands, e-mail: fortress-help@directory.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 19, 2022, at 8:30 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
>
> BTW, just noticed that fortress-commanderrequires Java 11, while the other components only require java 8. Is this intended?
Emmanuel,
Yes. The upgrade to latest Wicket v9 requires the jump to java 11.
The others still happily run on 8 although the day is coming soon where that'll change.
—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 19, 2022, at 8:30 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
>
> BTW, just noticed that fortress-commanderrequires Java 11, while the other components only require java 8. Is this intended?
Emmanuel,
Yes. The upgrade to latest Wicket v9 requires the jump to java 11.
The others still happily run on 8 although the day is coming soon where that'll change.
—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Emmanuel Lécharny <el...@gmail.com>.
BTW, just noticed that fortress-commanderrequires Java 11, while the
other components only require java 8. Is this intended?
On 19/07/2022 06:35, Emmanuel Lécharny wrote:
> [X] +1 | Release Fortress 2.0.8
>
> Checked the build from sources, checked the packages signatures, checked
> the build from packages, checked fortress against ApacheDS, all was
> smooth and green !
>
> Many thanks, Shawn, great job !
>
> On 17/07/2022 21:47, Shawn McKinney wrote:
>> Hello,
>>
>> This is an announcement to vote for the next release of Apache
>> Directory Fortress, 2.0.8.
>>
>> Here are the list of bugs and enhancements:
>>
>> https://issues.apache.org/jira/projects/FC/versions/12351048
>>
>> A tag created for git: ‘2.0.8', and the sources may be pulled using
>> git commands:
>> git clone --branch 2.0.8
>> https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git
>> git clone --branch 2.0.8
>> https://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git
>> git clone --branch 2.0.8
>> https://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git
>> git clone --branch 2.0.8
>> https://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git
>>
>> with their associated checksums:
>> - core: 137c2019218903a06da0522530251db4c942b111
>> - realm: 101e24e4e7758f67bbd992d6193a59934c73ffe3
>> - rest: b7de2edf30881eadcbe86ceb6f7cb90f78ccff3d
>> - web: a496b8dd3ca2f4421dca06f8604a8cd52a47becc
>>
>> Or, source and binary distros may be downloaded from SVN:
>> - https://dist.apache.org/repos/dist/dev/directory/fortress/2.0.8/
>>
>> The staging repo on Nexus:
>> -
>> https://repository.apache.org/content/repositories/orgapachedirectory-1207
>>
>>
>> Test against LDAP using one of these:
>> -
>> https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-APACHEDS.md
>>
>> -
>> https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-SLAPD.md
>>
>>
>> ** OR (new) **
>> — https://gitlab.symas.net/symas-public/ansible-apache-fortress
>>
>> - run plays:
>> ```
>> ansible-playbook -i inventory slapd.yml
>> # OR:
>> ansible-playbook -i inventory apacheds.yml
>>
>> # +:
>> ansible-playbook -i inventory fortress.yml
>> ```
>>
>> - [set host var fortress_version to
>> 2.0.8](https://gitlab.symas.net/symas-public/ansible-apache-fortress/-/blob/master/ansible/inventory/group_vars/fortress.yml#L6)
>>
>>
>> ***
>>
>> - Choose one of the above. Complete (only) the sections leading up to
>> and including the SECTION entitled: 'Apache Fortress Core Integration
>> Test’
>>
>> Please vote:
>> [ ] +1 | Release Fortress 2.0.8
>> [ ] +/-0 | Abstain
>> [ ] -1 | Do *NOT* Release Fortress 2.0.8
>>
>> —
>> Shawn
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
>> For additional commands, e-mail: fortress-help@directory.apache.org
>>
>
--
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
emmanuel.lecharny@busit.com https://www.busit.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Emmanuel Lécharny <el...@gmail.com>.
BTW, just noticed that fortress-commanderrequires Java 11, while the
other components only require java 8. Is this intended?
On 19/07/2022 06:35, Emmanuel Lécharny wrote:
> [X] +1 | Release Fortress 2.0.8
>
> Checked the build from sources, checked the packages signatures, checked
> the build from packages, checked fortress against ApacheDS, all was
> smooth and green !
>
> Many thanks, Shawn, great job !
>
> On 17/07/2022 21:47, Shawn McKinney wrote:
>> Hello,
>>
>> This is an announcement to vote for the next release of Apache
>> Directory Fortress, 2.0.8.
>>
>> Here are the list of bugs and enhancements:
>>
>> https://issues.apache.org/jira/projects/FC/versions/12351048
>>
>> A tag created for git: ‘2.0.8', and the sources may be pulled using
>> git commands:
>> git clone --branch 2.0.8
>> https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git
>> git clone --branch 2.0.8
>> https://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git
>> git clone --branch 2.0.8
>> https://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git
>> git clone --branch 2.0.8
>> https://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git
>>
>> with their associated checksums:
>> - core: 137c2019218903a06da0522530251db4c942b111
>> - realm: 101e24e4e7758f67bbd992d6193a59934c73ffe3
>> - rest: b7de2edf30881eadcbe86ceb6f7cb90f78ccff3d
>> - web: a496b8dd3ca2f4421dca06f8604a8cd52a47becc
>>
>> Or, source and binary distros may be downloaded from SVN:
>> - https://dist.apache.org/repos/dist/dev/directory/fortress/2.0.8/
>>
>> The staging repo on Nexus:
>> -
>> https://repository.apache.org/content/repositories/orgapachedirectory-1207
>>
>>
>> Test against LDAP using one of these:
>> -
>> https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-APACHEDS.md
>>
>> -
>> https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-SLAPD.md
>>
>>
>> ** OR (new) **
>> — https://gitlab.symas.net/symas-public/ansible-apache-fortress
>>
>> - run plays:
>> ```
>> ansible-playbook -i inventory slapd.yml
>> # OR:
>> ansible-playbook -i inventory apacheds.yml
>>
>> # +:
>> ansible-playbook -i inventory fortress.yml
>> ```
>>
>> - [set host var fortress_version to
>> 2.0.8](https://gitlab.symas.net/symas-public/ansible-apache-fortress/-/blob/master/ansible/inventory/group_vars/fortress.yml#L6)
>>
>>
>> ***
>>
>> - Choose one of the above. Complete (only) the sections leading up to
>> and including the SECTION entitled: 'Apache Fortress Core Integration
>> Test’
>>
>> Please vote:
>> [ ] +1 | Release Fortress 2.0.8
>> [ ] +/-0 | Abstain
>> [ ] -1 | Do *NOT* Release Fortress 2.0.8
>>
>> —
>> Shawn
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
>> For additional commands, e-mail: fortress-help@directory.apache.org
>>
>
--
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
emmanuel.lecharny@busit.com https://www.busit.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Emmanuel Lécharny <el...@gmail.com>.
[X] +1 | Release Fortress 2.0.8
Checked the build from sources, checked the packages signatures, checked
the build from packages, checked fortress against ApacheDS, all was
smooth and green !
Many thanks, Shawn, great job !
On 17/07/2022 21:47, Shawn McKinney wrote:
> Hello,
>
> This is an announcement to vote for the next release of Apache Directory Fortress, 2.0.8.
>
> Here are the list of bugs and enhancements:
>
> https://issues.apache.org/jira/projects/FC/versions/12351048
>
> A tag created for git: ‘2.0.8', and the sources may be pulled using git commands:
> git clone --branch 2.0.8 https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git
> git clone --branch 2.0.8 https://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git
> git clone --branch 2.0.8 https://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git
> git clone --branch 2.0.8 https://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git
>
> with their associated checksums:
> - core: 137c2019218903a06da0522530251db4c942b111
> - realm: 101e24e4e7758f67bbd992d6193a59934c73ffe3
> - rest: b7de2edf30881eadcbe86ceb6f7cb90f78ccff3d
> - web: a496b8dd3ca2f4421dca06f8604a8cd52a47becc
>
> Or, source and binary distros may be downloaded from SVN:
> - https://dist.apache.org/repos/dist/dev/directory/fortress/2.0.8/
>
> The staging repo on Nexus:
> - https://repository.apache.org/content/repositories/orgapachedirectory-1207
>
> Test against LDAP using one of these:
> - https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-APACHEDS.md
> - https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-SLAPD.md
>
> ** OR (new) **
> — https://gitlab.symas.net/symas-public/ansible-apache-fortress
>
> - run plays:
> ```
> ansible-playbook -i inventory slapd.yml
> # OR:
> ansible-playbook -i inventory apacheds.yml
>
> # +:
> ansible-playbook -i inventory fortress.yml
> ```
>
> - [set host var fortress_version to 2.0.8](https://gitlab.symas.net/symas-public/ansible-apache-fortress/-/blob/master/ansible/inventory/group_vars/fortress.yml#L6)
>
> ***
>
> - Choose one of the above. Complete (only) the sections leading up to and including the SECTION entitled: 'Apache Fortress Core Integration Test’
>
> Please vote:
> [ ] +1 | Release Fortress 2.0.8
> [ ] +/-0 | Abstain
> [ ] -1 | Do *NOT* Release Fortress 2.0.8
>
> —
> Shawn
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
> For additional commands, e-mail: fortress-help@directory.apache.org
>
--
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
emmanuel.lecharny@busit.com https://www.busit.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
Re: [VOTE] Apache Fortress 2.0.8 release
Posted by Emmanuel Lécharny <el...@gmail.com>.
[X] +1 | Release Fortress 2.0.8
Checked the build from sources, checked the packages signatures, checked
the build from packages, checked fortress against ApacheDS, all was
smooth and green !
Many thanks, Shawn, great job !
On 17/07/2022 21:47, Shawn McKinney wrote:
> Hello,
>
> This is an announcement to vote for the next release of Apache Directory Fortress, 2.0.8.
>
> Here are the list of bugs and enhancements:
>
> https://issues.apache.org/jira/projects/FC/versions/12351048
>
> A tag created for git: ‘2.0.8', and the sources may be pulled using git commands:
> git clone --branch 2.0.8 https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git
> git clone --branch 2.0.8 https://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git
> git clone --branch 2.0.8 https://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git
> git clone --branch 2.0.8 https://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git
>
> with their associated checksums:
> - core: 137c2019218903a06da0522530251db4c942b111
> - realm: 101e24e4e7758f67bbd992d6193a59934c73ffe3
> - rest: b7de2edf30881eadcbe86ceb6f7cb90f78ccff3d
> - web: a496b8dd3ca2f4421dca06f8604a8cd52a47becc
>
> Or, source and binary distros may be downloaded from SVN:
> - https://dist.apache.org/repos/dist/dev/directory/fortress/2.0.8/
>
> The staging repo on Nexus:
> - https://repository.apache.org/content/repositories/orgapachedirectory-1207
>
> Test against LDAP using one of these:
> - https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-APACHEDS.md
> - https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-SLAPD.md
>
> ** OR (new) **
> — https://gitlab.symas.net/symas-public/ansible-apache-fortress
>
> - run plays:
> ```
> ansible-playbook -i inventory slapd.yml
> # OR:
> ansible-playbook -i inventory apacheds.yml
>
> # +:
> ansible-playbook -i inventory fortress.yml
> ```
>
> - [set host var fortress_version to 2.0.8](https://gitlab.symas.net/symas-public/ansible-apache-fortress/-/blob/master/ansible/inventory/group_vars/fortress.yml#L6)
>
> ***
>
> - Choose one of the above. Complete (only) the sections leading up to and including the SECTION entitled: 'Apache Fortress Core Integration Test’
>
> Please vote:
> [ ] +1 | Release Fortress 2.0.8
> [ ] +/-0 | Abstain
> [ ] -1 | Do *NOT* Release Fortress 2.0.8
>
> —
> Shawn
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
> For additional commands, e-mail: fortress-help@directory.apache.org
>
--
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
emmanuel.lecharny@busit.com https://www.busit.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org