[jira] [Updated] (ZOOKEEPER-3029) Create assembly for maven

2018-12-20 Thread Norbert Kalmar (JIRA)


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

Norbert Kalmar updated ZOOKEEPER-3029:
--
Summary: Create assembly for maven  (was: Create pom.xml for jute and 
server)

> Create assembly for maven
> -
>
> Key: ZOOKEEPER-3029
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3029
> 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
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 3.6.0, 3.5.5, 3.4.14
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> 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)


[jira] [Updated] (ZOOKEEPER-3029) Create assembly for maven

2018-12-20 Thread Norbert Kalmar (JIRA)


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

Norbert Kalmar updated ZOOKEEPER-3029:
--
Description: 
Create the tarball assembly for the maven build. End results should be similar 
what ant did, at least it should contain all the source and jar the ant tarball 
did. Doesn't have to make the same mistakes. (Duplicate source codes).

First, master only.

  was:
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}


> Create assembly for maven
> -
>
> Key: ZOOKEEPER-3029
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3029
> 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
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 3.6.0, 3.5.5, 3.4.14
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Create the tarball assembly for the maven build. End results should be 
> similar what ant did, at least it should contain all the source and jar the 
> ant tarball did. Doesn't have to make the same mistakes. (Duplicate source 
> codes).
> First, master only.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)