Commit b7e1a121 authored by Luc Maisonobe's avatar Luc Maisonobe

set version to 3.0, for first public release!

parent f584be8f
......@@ -5,7 +5,7 @@
<groupId>org.orekit</groupId>
<artifactId>orekit</artifactId>
<packaging>jar</packaging>
<version>3.0-SNAPSHOT</version>
<version>3.0</version>
<name>ORbit Extrapolation KIT</name>
<url>http://www.orekit.org/</url>
......@@ -142,6 +142,18 @@
<artifactId>maven-surefire-plugin</artifactId>
<version>2.4</version>
<configuration>
<configuration>
<!-- for default profile, we want the tests to run quickly, so we
avoid the "pertest" fork mode used in release profile. This
prevents us from playing with the singletons and hence the few
tests that do this cannot be run with the others. This is the
reason why we exclude them here. In order to run them, the
"release" profile must be selected. -->
<excludes>
<exclude>**/UTCTAIHistoryFilesLoaderCompressedDataTest.java</exclude>
<exclude>**/UTCTAIHistoryFilesLoaderNoDataTest.java</exclude>
</excludes>
</configuration>
<!-- we need different JVM for some tests which use different
singletons configurations (tests-specific IERS reference files) -->
<forkMode>pertest</forkMode>
......@@ -208,7 +220,20 @@
<id>release</id>
<build>
<plugins>
<plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.4</version>
<configuration>
<!-- for release profile, we run ALL tests, including the few small
ones that play with singletons and hence need to be run on
separate JVM. This implies the "pertest" fork mode which is
quite slow. This is the reason why we use this configuration
only when this profile is selected -->
<forkMode>pertest</forkMode>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>2.0.4</version>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment