<div><span class="gmail_quote">2006/9/11, Arnaud Bailly <<a href="mailto:abailly@oqube.com">abailly@oqube.com</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Chandru <<a href="mailto:chandrashekhar.mullaparthi@gmail.com">chandrashekhar.mullaparthi@gmail.com</a>
> writes:<br><br>>><br>><br>> I don't know anything about Maven, but maybe you can use the OTP structure<br>> for your system installation and the "mavenish" structure for your code<br>> repository?
<br><br>I agree. The OTP structure could be constructed from the maven<br>standard layout using assembly plugin or even a custom artefact<br>type. For simplicity's and consistency's sake, it is better to keep<br>adhering to maven's structure.
</blockquote>
<div> </div>
<div>I also agree (it does seem obvious now...)</div><br> </div><span class="gmail_quote">2006/9/11, Vance Shipley <<a href="mailto:vances@motivity.ca">vances@motivity.ca</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On 10/09/06, Olivier Sambourg <<a href="mailto:olivier.sambourg@gmail.com">olivier.sambourg@gmail.com</a>
> wrote:<br>><br>>If we take a look at various OTP applications, the common directory<br>>structure seems to be :<br>><br>>application/<br>>|-> src/ (source files, flat)<br>>|-> include/ (include files...)
<br>>|-> doc/ (documentation)<br>>|-> ebin/ (beam files)<br><br>The convention in OTP when mixing languages is to have a "c_src"<br>directory. For example:<br><br> $ ls lib/erlang/lib/asn1-<a href="http://1.4.4.10">
1.4.4.10</a><br> c_src ebin examples priv src<br><br>In this case there is a ddll driver and the C source is in c_src.<br>The library with the driver code is in:<br><br> lib/erlang/lib/asn1-<a href="http://1.4.4.10/priv/lib/asn1_erl_drv.so">
1.4.4.10/priv/lib/asn1_erl_drv.so</a><br><br>Another example is the IC application which uses java:<br><br> $ ls lib/erlang/lib/ic-4.2.11<br> c_src ebin examples include java_src priv src<br></blockquote>
<div><br>Thank you for the information :)</div>
<div> </div>
<div> </div>
<div>I've started working on the plugin, slowly at first as I'm still struggling with Maven's documentation... For the moment, it's capable of generating an Emakefile with various user defined options and use it to compile the source files. Quite dull actually :)
</div>
<div>Next step will be packaging, automatically running test cases and generating the edoc (not necessarily in this order). Then there'll be dynamic code loading (Cargo really seems a good idea...) and dependencies management (REPOS is still my only lead).
</div>
<div> </div>
<div>I've also started an archetype plugin (a special breed of maven plugins used to set up a typical project, such as web apps, j2ee, etc.). It creates the project directory structure, along with exemple sources files and a basic POM file, so you can start coding right away...
</div>
<div> </div>
<div>I'll let you know when I make significant progress.</div>
<div> </div>
<div>Thanks for the help</div>
<div> </div>
<div> </div>
<div>--</div>
<div>Olivier</div>