Jochen Wiedmann wrote:
Hi,
as some of you possibly know, I've got a third life (apart from being
Husband/Dad or Apache Committer), in which I am working as an employee
of Software AG.
SAG is the vendor of several proprietary software solutions, one of
them being the crossvision Application Designer
(http://www.softwareag.com/Corporate/products/cv/appldes/default.asp),
which is basically a GUI editor for Ajax applications. While I like
the product, I always rejected its builtin "war packager", because it
misleads people to use a "quick'n dirty" build process, or none at
all. To overcome that problem, I have written a Maven 2 plugin
(cis-maven-plugin), which meets all Maven standards.
To simplify my own life, I would like to contribute this plugin to
Mojo. However, the following things should be noted:
- The plugin can be built without the AD. However, it cannot be tested
without AD. Hence
the current absence of a test suite.
- To use the plugin, you need an AD distribution. For obvious reasons,
I cannot add this
to ibiblio. In other words, the plugins description contains as a
first step the deployment
of the distributed war file to a local repository.
- The plugin was developed without my employers permissions and in my
spare time.
My question is, whether I may proceed to add the plugin to the sandbox
or whether the above problems are violating some Mojo policy. In which
case I would need to find a different home.
I see other has already replied but anyway:
The Mojo project is here to support all kinds of development and as long
as the plugin itself is open source and meet the normal Mojo "quality" I
have no objections what so ever. I would like you to include the test
cases and rather put the plugin in a "ad" profile or something.
--
Trygve
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
