zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Norbert Kalmar (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (ZOOKEEPER-3223) Create static code analyser
Date Thu, 20 Dec 2018 08:51:00 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Norbert Kalmar reassigned ZOOKEEPER-3223:
-----------------------------------------

    Assignee:     (was: Norbert Kalmar)

> Create static code analyser
> ---------------------------
>
>                 Key: ZOOKEEPER-3223
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3223
>             Project: ZooKeeper
>          Issue Type: Sub-task
>          Components: build, scripts
>    Affects Versions: 3.5.4, 3.6.0, 3.4.13
>            Reporter: Norbert Kalmar
>            Priority: Blocker
>              Labels: pull-request-available
>             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)

Mime
View raw message