directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lécharny <elecha...@gmail.com>
Subject Re: [Fortress] pom.xml update
Date Fri, 14 Nov 2014 09:56:08 GMT
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 !
>


Mime
View raw message