You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Emmanuel Lécharny <el...@gmail.com> on 2014/11/14 10:50:08 UTC
[Fortress] pom.xml update
Hi Shawn,
this morning, I was trying to get the fortress-core pom updated with all
the new plugin versions and dependencies.
Here are the list of versions we should use :
for the plugins :
[WARNING] The following plugins do not have their version specified:
[WARNING] maven-assembly-plugin ....................... (from
super-pom) 2.4
[WARNING] maven-clean-plugin .......................... (from
super-pom) 2.5
[WARNING] maven-deploy-plugin ....................... (from super-pom)
2.8.1
[WARNING] maven-install-plugin ...................... (from super-pom)
2.5.1
[WARNING] maven-jar-plugin ............................ (from
super-pom) 2.5
[WARNING] maven-site-plugin ........................... (from
super-pom) 3.3
[WARNING] maven-surefire-plugin ...................... (from
super-pom) 2.17
[WARNING] org.apache.rat:apache-rat-plugin
............................ 0.11
and for the dependencies :
[INFO] The following dependencies in Dependencies have newer versions:
[INFO] commons-configuration:commons-configuration .............. 1.6
-> 1.10
[INFO] junit:junit ...................................... 4.11 ->
4.12-beta-3 // Should be ignored
[INFO] org.apache.ant:ant .................................... 1.9.1
-> 1.9.4
[INFO] org.apache.cxf:cxf-common-utilities ................. 2.5.10 ->
2.5.11
[INFO] org.apache.directory.jdbm:apacheds-jdbm1 ........ 2.0.0-M2 ->
2.0.0-M3
[INFO] org.apache.jmeter:ApacheJMeter_core ..................... 2.11
-> 2.12 // needs a dep on
d-haven-managed-pool:d-haven-managed-pool:jar:1.0
[INFO] org.apache.jmeter:ApacheJMeter_java ..................... 2.11
-> 2.12
[INFO] org.jasypt:jasypt ....................................... 1.8
-> 1.9.2
I have updated the pom for those new versions.
When I run the test with mvn clean install, I get many errors, most
certainly due to the missing configuration file. At some point, we
should probably create such a configuration file, instead of generating
it with ant.
In any case, feel free to revert the pom.xml to what it was before my
change if you have any pb, as I can't test the code.
Thanks !
Re: [Fortress] pom.xml update
Posted by Emmanuel Lécharny <el...@gmail.com>.
One more thing I forgot to mention : I changed the version for the
project from 1.0-RC40 to 1.0-RC40-SNAPSHOT, otherwise it will be a real
problem for the release process.
The idea is that we don't work on a specific version number, but on a
SNAPSHOT until the release is voted. It clarifies the status of the
component, if anyone is going - by mistake or not - to use a jar being
pushed on a repo : it's curently a SNAPSHOT, not a released version.
We should do that for the three other fortress pom
(the release process will bump the SNAPSHOT to a full revision
automatically)
Le 14/11/14 10:50, Emmanuel Lécharny a écrit :
> Hi Shawn,
>
> this morning, I was trying to get the fortress-core pom updated with all
> the new plugin versions and dependencies.
>
> Here are the list of versions we should use :
>
> for the plugins :
>
> [WARNING] The following plugins do not have their version specified:
> [WARNING] maven-assembly-plugin ....................... (from
> super-pom) 2.4
> [WARNING] maven-clean-plugin .......................... (from
> super-pom) 2.5
> [WARNING] maven-deploy-plugin ....................... (from super-pom)
> 2.8.1
> [WARNING] maven-install-plugin ...................... (from super-pom)
> 2.5.1
> [WARNING] maven-jar-plugin ............................ (from
> super-pom) 2.5
> [WARNING] maven-site-plugin ........................... (from
> super-pom) 3.3
> [WARNING] maven-surefire-plugin ...................... (from
> super-pom) 2.17
> [WARNING] org.apache.rat:apache-rat-plugin
> ............................ 0.11
>
> and for the dependencies :
>
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] commons-configuration:commons-configuration .............. 1.6
> -> 1.10
> [INFO] junit:junit ...................................... 4.11 ->
> 4.12-beta-3 // Should be ignored
> [INFO] org.apache.ant:ant .................................... 1.9.1
> -> 1.9.4
> [INFO] org.apache.cxf:cxf-common-utilities ................. 2.5.10 ->
> 2.5.11
> [INFO] org.apache.directory.jdbm:apacheds-jdbm1 ........ 2.0.0-M2 ->
> 2.0.0-M3
> [INFO] org.apache.jmeter:ApacheJMeter_core ..................... 2.11
> -> 2.12 // needs a dep on
> d-haven-managed-pool:d-haven-managed-pool:jar:1.0
> [INFO] org.apache.jmeter:ApacheJMeter_java ..................... 2.11
> -> 2.12
> [INFO] org.jasypt:jasypt ....................................... 1.8
> -> 1.9.2
>
> I have updated the pom for those new versions.
>
> When I run the test with mvn clean install, I get many errors, most
> certainly due to the missing configuration file. At some point, we
> should probably create such a configuration file, instead of generating
> it with ant.
>
> In any case, feel free to revert the pom.xml to what it was before my
> change if you have any pb, as I can't test the code.
>
> Thanks !
>
Re: [Fortress] pom.xml update
Posted by Shawn McKinney <mc...@att.net>.
On 11/14/2014 09:22 AM, Emmanuel Lécharny wrote:
>
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.29 sec
> <<< FAILURE! - in org.apache.directory.fortress.core.rbac.FortressJUnitTest
> initializationError(org.apache.directory.fortress.core.rbac.FortressJUnitTest)
> Time elapsed: 0.006 sec <<< ERROR!
> java.lang.ExceptionInInitializerError: null
> at
> org.apache.directory.fortress.core.cfg.Config.<clinit>(Config.java:70)
> at
> org.apache.directory.fortress.core.util.attr.VUtil.<clinit>(VUtil.java:49)
> at
> org.apache.directory.fortress.core.util.LogUtil.getContext(LogUtil.java:75)
> at
> org.apache.directory.fortress.core.util.LogUtil.logIt(LogUtil.java:46)
> at
> org.apache.directory.fortress.core.rbac.ReviewMgrImplTest.teardownRequired(ReviewMgrImplTest.java:339)
> at
> org.apache.directory.fortress.core.rbac.FortressJUnitTest.getFirstRun(FortressJUnitTest.java:70)
> at
> org.apache.directory.fortress.core.rbac.FortressJUnitTest.<clinit>(FortressJUnitTest.java:65)
>
>
> Results :
>
> Tests in error:
> FortressJUnitTest.<clinit>:65->getFirstRun:70 » ExceptionInInitializer
try running these steps first to setup the DIT and base policies:
mvn install -Dload.file=./ldap/setup/refreshLDAPData.xml -DskipTests=true
mvn install -Dload.file=./ldap/setup/DelegatedAdminManagerLoad.xml -DskipTests=true
Re: [Fortress] pom.xml update
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 14/11/14 14:49, Shawn McKinney a écrit :
> On 11/14/2014 03:50 AM, Emmanuel Lécharny wrote:
>> I have updated the pom for those new versions.
>>
>> When I run the test with mvn clean install, I get many errors, most
>> certainly due to the missing configuration file. At some point, we
>> should probably create such a configuration file, instead of generating
>> it with ant.
> What errors do you get for which test(s)? To run for a specific test try:
>
> $M2_HOME/bin/mvn -Dtest=FortressJUnitTest test
This is what I get :
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.29 sec
<<< FAILURE! - in org.apache.directory.fortress.core.rbac.FortressJUnitTest
initializationError(org.apache.directory.fortress.core.rbac.FortressJUnitTest)
Time elapsed: 0.006 sec <<< ERROR!
java.lang.ExceptionInInitializerError: null
at
org.apache.directory.fortress.core.cfg.Config.<clinit>(Config.java:70)
at
org.apache.directory.fortress.core.util.attr.VUtil.<clinit>(VUtil.java:49)
at
org.apache.directory.fortress.core.util.LogUtil.getContext(LogUtil.java:75)
at
org.apache.directory.fortress.core.util.LogUtil.logIt(LogUtil.java:46)
at
org.apache.directory.fortress.core.rbac.ReviewMgrImplTest.teardownRequired(ReviewMgrImplTest.java:339)
at
org.apache.directory.fortress.core.rbac.FortressJUnitTest.getFirstRun(FortressJUnitTest.java:70)
at
org.apache.directory.fortress.core.rbac.FortressJUnitTest.<clinit>(FortressJUnitTest.java:65)
Results :
Tests in error:
FortressJUnitTest.<clinit>:65->getFirstRun:70 » ExceptionInInitializer
Re: [Fortress] pom.xml update
Posted by Shawn McKinney <mc...@att.net>.
On 11/14/2014 03:50 AM, Emmanuel Lécharny wrote:
> I have updated the pom for those new versions.
>
> When I run the test with mvn clean install, I get many errors, most
> certainly due to the missing configuration file. At some point, we
> should probably create such a configuration file, instead of generating
> it with ant.
What errors do you get for which test(s)? To run for a specific test try:
$M2_HOME/bin/mvn -Dtest=FortressJUnitTest test
On 11/14/2014 03:50 AM, Emmanuel Lécharny wrote:> In any case, feel free to revert the pom.xml to what it was before my
> change if you have any pb, as I can't test the code.
We can discuss install options which should include config file usage. I am able to run the above test successfully using the latest versions contained in the pom.