You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Norbert Kalmar (JIRA)" <ji...@apache.org> on 2018/12/20 09:02:00 UTC
[jira] [Created] (ZOOKEEPER-3225) Create code coverage analysis
with maven build
Norbert Kalmar created ZOOKEEPER-3225:
-----------------------------------------
Summary: Create code coverage analysis with maven build
Key: ZOOKEEPER-3225
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3225
Project: ZooKeeper
Issue Type: Sub-task
Components: build, scripts
Affects Versions: 3.5.4, 3.6.0, 3.4.13
Reporter: Norbert Kalmar
Assignee: Norbert Kalmar
Fix For: 3.6.0, 3.5.5, 3.4.14
After the directory structures has been created, it is time to create the pom files for all the modules, and create the build hierarchy.
At first, ant should remain in place until we are sure maven works fine.
jute and server should be priority first. docs is handled in a different jira, as it is also being migrated. Recipes and contrib will remain for last.
The different modules will get their maven structure:
{noformat}
zookeeper-[something]
| -src
| | -main
| | | -java
| | | \org...
| | \resources
| | -test (unit tests only)
| | | -java
| | | \org...
| | \ resources
| | - it (integration tests)
| \pom.xml
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)