Multiple packaging in one pom

[Marteijn Nouwens <ma...@gmail.com>]

Hello again. A just finisched my a first jbuilder plugin and an application
plugin.

If anyone is interested in developing the jbuilder plugin fther please
contact me. At the moment it only generates library files and that's enough
for me. Same so for my old maven 1.1 plugin. Never needed more since we
distribute the jbuilder files.

If anyone reading this developed the old jbuilder ide intergation contact me
i would like to offer to port this one to maven 2. I think it would be handy
to be able to run the goals from within jbuilder.

A real question for the maven 2 experts. I now have the situation that i
start on migrating my izpack plugin. I used to specify some info in a config
dir and specify a build type of application, installer and my main plugin
would build both types. My question is it possible to have a project with
mutliple packaging types. Or if this is not the recommended way to go what
would be. Combined packagings would only be sensible in a couple of cases
like an application and installer. Which is the main one for me.

I already found that some thing are a lot better structured, I like the
principel of packaging but i still mis some steps in this thinking. However
why not work from a funtional type thinking all the way.

I defined for all the project i am working on, the following functional
types.

   - library (Basicly just the jar packaging at the moment)
   - application - runnable java application (build this pakaging type
   myself)
   - izpack-installer - creates an installer based on a certain installer
   tech ( Use izpack myself)
   - ear (Supprted) (additional the client jar is the interface it
   implements)
   - war (Supprted)
   - Rar (Supprted ?)
   - interface (Library project which defines api)
   - app-plugin (like maven plugin but then implementing interface see
   above)
   - ejb (Supported) (additional the client jar is the interface it
   implements)
   - webstart (Indentied it but still thnking about impplementin it)
   - izpack-plugin (plugin type like maven-plugin for creating izpack
   plugins)
   - waba A plugin for creating waba applications (Hobby)

Anyone ideas or suggestions, Sen me a mail.

It would be nice to be able to say in the dependencies whta type it is. For
instance if you include a library it knows it's a jar.

like :

dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>3.8.1</version>
      <type>library</type>
    </dependency>

Library would be the default type.

Marteijn Nouwens