Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
Orekit
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Orekit
Orekit
Commits
1300cef3
Commit
1300cef3
authored
16 years ago
by
Luc Maisonobe
Browse files
Options
Downloads
Patches
Plain Diff
changes tests configuration
parent
1ecf0f1d
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
pom.xml
+5
-24
5 additions, 24 deletions
pom.xml
with
5 additions
and
24 deletions
pom.xml
+
5
−
24
View file @
1300cef3
...
...
@@ -150,17 +150,11 @@
<artifactId>
maven-surefire-plugin
</artifactId>
<version>
2.4.3
</version>
<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 other ones. This is
the reason why we exclude them here. In order to run them, the
"release" profile must be selected. -->
<excludes>
<exclude>
**/ITRF2000FrameAlternateConfigurationTest.java
</exclude>
<exclude>
**/UTCTAIHistoryFilesLoaderCompressedDataTest.java
</exclude>
<exclude>
**/UTCTAIHistoryFilesLoaderNoDataTest.java
</exclude>
</excludes>
<!-- Some tests play tricks with singletons configuration, using various
IERS data folders. These tests cannot share the singletons, so they
must be run in separated JVMs. This slows down tests but is needed
for tests coverage. So we use a per test mode. -->
<forkMode>
pertest
</forkMode>
</configuration>
</plugin>
<plugin>
...
...
@@ -224,19 +218,6 @@
<id>
release
</id>
<build>
<plugins>
<plugin>
<groupId>
org.apache.maven.plugins
</groupId>
<artifactId>
maven-surefire-plugin
</artifactId>
<version>
2.4.3
</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>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment