[ 
https://issues.apache.org/jira/browse/MEECROWAVE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982495#comment-15982495
 ] 

Romain Manni-Bucau commented on MEECROWAVE-27:
----------------------------------------------

Yep,

overall goal is to "prepare to deployment" and simplify/standardize an assembly.

Layout is:

{code}
bin
 `- meecrowave.sh
conf
  `- log4j.xml
lib
 `- *.jar
{code}

we can surely add classes/*.class but dont think it is needed or helping so for 
now we don't and just use .jar.

Then you can "start"/"stop", "run", "jpda start" the server as tomcat. Main 
difference is in this first version the server is killed and not stopped 
through a socket as tomcat - but using a shutdown hook we should be fine.

This supports classpath deployments mainly but since it relies on Cli we should 
be able to wire much more - still need some work on that area.

Pending changes/thoughts:

- server.xml in conf/?
- how do we want to wire all options we have?
- .bat version? (I don't have win ATM to do much on that)

> add bundle maven goal to create a zip of the project
> ----------------------------------------------------
>
>                 Key: MEECROWAVE-27
>                 URL: https://issues.apache.org/jira/browse/MEECROWAVE-27
>             Project: Meecrowave
>          Issue Type: New Feature
>            Reporter: Romain Manni-Bucau
>            Assignee: Romain Manni-Bucau
>             Fix For: 0.3.1
>
>
> Goal is to have a conf/ with at least log4j2.xml, a lib/ with all 
> dependencies of the project and a bin with a sh script to start/stop the 
> server.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to