Task #368
closedUpdate connectors to version 1.4.2
100%
Description
Try install new connector server (1.4.2 - successfully tested on 1.4.0).
Test if we can upgrade connector.
https://mvnrepository.com/artifact/net.tirasa.connid/connector-framework/1.4.2.0
https://mvnrepository.com/artifact/net.tirasa.connid/connector-framework-internal/1.4.2.0
Updated by Ondřej Kopr about 7 years ago
Create remote connector server for test.
Create new bundle with 1.4.2. version of connectors.
Upgrade all version of internal connector to new version.
Upgrade connector-framework and connector-framework-internal
Updated by Ondřej Kopr about 7 years ago
- % Done changed from 0 to 60
Remote connector server has these version 1.4.2 connector-framework and connector-framework-internal
Local connector-framework 1.4.2 and connector-framework-internal 1.4.0
java.lang.NoSuchMethodError: org.identityconnectors.framework.common.objects.ObjectClassInfo.<init>(Ljava/lang/String;Ljava/util/Set;Z)V
Found better solutions with exclusion.
Updated by Ondřej Kopr about 7 years ago
update dependencies:
<!--IC dependency --> <!-- for connectors: csvdir, table, scriptedsql need exclusion to connector-framework-internal version 1.4.0 --> <dependency> <groupId>net.tirasa.connid</groupId> <artifactId>connector-framework</artifactId> <version>1.4.2.0</version> </dependency> <dependency> <groupId>net.tirasa.connid</groupId> <artifactId>connector-framework-internal</artifactId> <version>1.4.2.0</version> </dependency> <dependency> <groupId>net.tirasa.connid.bundles.db</groupId> <artifactId>net.tirasa.connid.bundles.db.table</artifactId> <version>2.2.4</version> <exclusions> <exclusion> <groupId>net.tirasa.connid</groupId> <artifactId>connector-framework-internal</artifactId> <version>1.4.0.0</version> </exclusion> </exclusions> </dependency> <dependency> <groupId>net.tirasa.connid.bundles</groupId> <artifactId>net.tirasa.connid.bundles.ldap</artifactId> <version>1.5.1</version> </dependency> <dependency> <groupId>net.tirasa.connid.bundles</groupId> <artifactId>net.tirasa.connid.bundles.csvdir</artifactId> <version>0.8.5</version> <exclusions> <exclusion> <groupId>net.tirasa.connid</groupId> <artifactId>connector-framework-internal</artifactId> <version>1.4.0.0</version> </exclusion> </exclusions> </dependency> <dependency> <groupId>net.tirasa.connid.bundles.db</groupId> <artifactId>net.tirasa.connid.bundles.db.scriptedsql</artifactId> <version>2.2.4</version> <exclusions> <exclusion> <groupId>net.tirasa.connid</groupId> <artifactId>connector-framework-internal</artifactId> <version>1.4.0.0</version> </exclusion> </exclusions> </dependency>Test:
- DB
- prov - ok
- sync - ok
- ldap
- prov - ok
Updated by Ondřej Kopr about 7 years ago
Test with jenkins fail for exclude specified version, found this:
Forcing a version A version will always be honoured if it is declared in the current POM with a particular version - however, it should be noted that this will also affect other poms downstream if it is itself depended on using transitive dependencies.
resource:
https://cwiki.apache.org/confluence/display/MAVENOLD/Dependency+Mediation+and+Conflict+Resolution
http://stackoverflow.com/questions/3937195/maven-how-to-override-the-dependency-added-by-a-library
exclusion hasnt version tag and there is no need to define it = remove all exclusions
Updated by Ondřej Kopr about 7 years ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100