ilgrosso

import org.apache.commons.lang3.StringUtils;
import org.apache.syncope.core.persistence.api.dao.PullCorrelationRule;
import org.apache.syncope.core.persistence.api.dao.search.AttributeCond;
import org.apache.syncope.core.persistence.api.dao.search.SearchCond;
import org.apache.syncope.core.persistence.api.entity.resource.Provision;
import org.identityconnectors.framework.common.objects.SyncDelta;

public class GFSLdapPullRule implements PullCorrelationRule {

    @Override

ilgrosso

public class AttributesEnrichingPropagationAction implements PropagationActions {

    @Autowired
    private UserDAO userDAO;

    @Transactional(readonly = true)
    @Override
    public void before(final PropagationTask task, final ConnectorObject beforeObj) {
        // do something only if propagating users
        if (AnyTypeKind.USER == task.getAnyTypeKind()) {

ilgrosso

During the release process for Apache Syncope 2.1.14 I noticed that release:prepare was not advancing POM version from 2.1.14-SNAPSHOT to 2.1.14, nor it was creating the syncope-2.1.14 tag.

Waiting to understand the reason, I was able to replace the actions peformed by release:prepare and release:perform with the following.

Release prepare

Plugin steps: http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html

Change version to 2.1.14

ilgrosso

public class ICLDAPLogic extends AbstractTransactionalLogic<EntityTO> {

    private final UserDAO userDAO;

    private final ExternalResourceDAO resourceDAO;

    private final MappingManager mappingManager;

    private final PropagationTaskExecutor taskExecutor;