Brian Demers created DIRAPI-398:
---
Summary: Release Pooled LDAP Connections when closed
Key: DIRAPI-398
URL: https://issues.apache.org/jira/browse/DIRAPI-398
Project: Directory Client API
Issue
+1 - Binding
I checked that the artifacts were reproducible.
Jars were good, the cyclonedx plugin output was generated differently on my
machine, different hash algorithms. I assume there is something environment
specific happening, but that's not a blocker for release (and I'm guessing
it's user
The Directory team is pleased to announce the release of SCIMple
version 1.0.0-M1. [1]
SCIMple is a Jakarta EE implementation of the SCIM 2.0 specification.
It can be used to build custom SCIM servers and clients used to
synchronize users and groups between systems.
This is the first release
The vote to accept SCIMple 1.0.0-M1 passed with 3 +1 PMC [binding]
votes and no dissenting votes:
+1 Colm O hEigeartaigh
+1 Shawn McKinney
+1 Brian Demers
And 1 non-binding vote:
+1 Eran Toledano
Thanks to all who voted!
I'll promote the staged artifacts and send out the announcement emails
+1 from me
On Wed, Jan 17, 2024 at 1:21 PM Shawn McKinney wrote:
>
>
>
> > On Jan 16, 2024, at 4:09 PM, Brian Demers wrote:
> >
> > Hey All!
> >
> > Great questions added by Shawn!
> >
> > Hopefully I hit them all:
> >
> >> Gui
Hey All!
Great questions added by Shawn!
Hopefully I hit them all:
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
This is optional, _techniall_ this is a guide explaining how to test
the convenience binaries that will be deployed to
This is a call to vote in favor of releasing Apache Directory SCIMple
version 1.0.0-M1.
This is the initial release since moving the project from
https://github.com/PennState/SCIMple-Identity to the Apache Software
Foundation: https://github.com/apache/directory-scimple
Maven Staging Repo:
TL;DR My next email will be the release vote email!
I ran into a couple more minor issues with the release process.
The biggest one is there was an odd interaction between the Maven Javadoc
plugin's aggregate-jar goal and the Quarkus server example (it uses an
extension).
(We can work around that
I think I've worked out all the issues with the SCIMple build getting
it ready for release.
Side note: I think I've been missing some of the dev@directory.a.o
messages due to poor email filtering on my part, sorry about that!
Quick recap, in case any of these bits are useful to other Directory
There was a bit of discussion in the Maven BoF last week at Community Over
Code on the topic of parent POM release processes.
This was a follow up to a thread on the board mailing list in September
"RFC: Releasing with lazy consensus".
TL;DR A few different projects have not been voting on parent
I've been working on getting SCIMple in release shape, but I've hit a few
snags along the way.
Mostly small things, or process related issues.
For example, there is an issue with generating the javadoc for the Spring
module because both the Spring dependencies and Glassfish have a split
package:
Brian Demers created DIR-344:
Summary: Use of shade plugin replaces files required for
distribution
Key: DIR-344
URL: https://issues.apache.org/jira/browse/DIR-344
Project: Directory
Issue Type
I took a pass at updating the Directory parent pom.
I updated to the latest apache pom and a bunch of other plugin versions:
https://github.com/apache/directory-project/pull/3
Of note, I changed how the compiler plugin gets configured; this removes a
deprecated (no-op) warning from child
t; automated testing and packaging?
>
> I know we do that with other projects. For example, fortress has a
> pipeline.
>
> Stefan was the one who helped us get that going.
>
> —
> Shawn
>
> > On May 20, 2022, at 9:52 AM, Brian Demers wrote:
> >
> > I'm
I'm not sure when the Jenkins PR builder was added, but based on the
history, I was the first person to trigger the job.
It failed:
https://ci-builds.apache.org/job/Directory/job/dir-scimple-pull-requests
Connection timeout connecting to GitHub. It's possible this was a one-time
problem, but...
We switched the Apache Shiro site from SVN to git a little while back. I cannot
fine the original blog/doc. But it was something like this
https://blogs.apache.org/infra/entry/git_based_websites_available
The process basically works like the SVN pub sub, but with a github repo. How
you
IMHO, setting the source & target to 1.8 (or whatever the lower end of your
support range is) and running a CI job with a range of versions is the
way to go (1.8, 11, etc)
That way this uncovers the issues similar to you have mentioned and retains
backward compatibility with any of the
https://www.apache.org/dev/release-publishing.html
CD gets a little tricky given the above. Personally, I'd like to see an
initial release before worrying about the CD portion (but I have a
non-binding vote here)
On Wed, Oct 3, 2018 at 10:21 AM, Moyer, Steven William
wrote:
> I've read
I’d suggest executing the plunging from a non-default profile. The configure
that profile to run at release time and CI. That way local builds are still
fast by default.
-Brian
> On Aug 6, 2018, at 10:42 AM, Smith, Shawn Eion wrote:
>
> That's where we have it. It slows down the build,
PRs build too
(with a big thanks to Infra for fixing a few issues)
On Wed, Jul 25, 2018 at 3:45 PM, Brian Demers wrote:
> It's blue!
>
> On Wed, Jul 25, 2018 at 10:50 AM, Brian Demers
> wrote:
>
>>
>> Almost there :)
>>
>> Fixes OWASP dep scan issue:
It's blue!
On Wed, Jul 25, 2018 at 10:50 AM, Brian Demers
wrote:
>
> Almost there :)
>
> Fixes OWASP dep scan issue:
> https://github.com/apache/directory-scimple/pull/6
>
> On Tue, Jul 24, 2018 at 1:59 PM, Brian Demers wrote:
>
>> > * I didn't see
Almost there :)
Fixes OWASP dep scan issue:
https://github.com/apache/directory-scimple/pull/6
On Tue, Jul 24, 2018 at 1:59 PM, Brian Demers wrote:
> > * I didn't see directory-scimple listed on https://git.apache.org/, so I
>> > used the GitHub URL. What is the canonical UR
Brian Demers created DIR-331:
Summary: Remove usage of restfuse from SCIMple (the project is
dead)
Key: DIR-331
URL: https://issues.apache.org/jira/browse/DIR-331
Project: Directory
Issue Type
>
> > * I didn't see directory-scimple listed on https://git.apache.org/, so I
> > used the GitHub URL. What is the canonical URL for this repo?
>
> SCIMple already uses gitbox, the canonical URL is
> https://gitbox.apache.org/repos/asf/directory-scimple.git
>
> Also listed at [1], there you
I've added directory-scimple to Jenkins:
https://builds.apache.org/view/D/view/Directory/job/dir-scimple/ (copied
from the dir-kerby job)
You may have noticed a build failure, I just turned off notifications until
the initial build is healthy.
Open questions/issues
* The dist management section
25 matches
Mail list logo
