maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard van Nieuwenhoven (JIRA)" <>
Subject [jira] Commented: (MECLIPSE-137) Developed RAD-6 Plugin Extention
Date Fri, 13 Oct 2006 11:41:54 GMT
    [ ] 
Richard van Nieuwenhoven commented on MECLIPSE-137:


you did it the wrong way around, at least as i do it. this plugin is 
designed to work the maven way and adapting the project in such a
way that it also works in RAD-6. So there should NOT be a "WebContent" 
directory there should be "src/main/webapp" as a webcontent.

all dependent libraries are copied into src/main/webapp/WEB-INF/lib . 
this directory should be ignored in scm.


> Developed RAD-6 Plugin Extention
> --------------------------------
>                 Key: MECLIPSE-137
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: New Feature
>            Reporter: Richard van Nieuwenhoven
>         Attachments: maven-rad-plugin.tar.gz,
> I just finisched developing a RAD-6 (IBM Rational Application Developer 6.0) extention
to the eclipse plugin.
> It supports J2EE projects with the websphere development envorment, supported are
> - EJB projects
> - Web projects
> - EAR- projects
> all these projects are recognized by rad-6 as what they. The websphere development enviorment
including hot-deployment features funktions out of the box.
> i wrote writers for:
> - the ".j2ee" files
> - the "application.xml" and the "modulemaps" file
> - copying the extrenal libs in the ear project root
> - adapting the MANIFEST.MF of the projects (nessesary for the websphere development enviorment)
> - the ".websettings" file
> - the ".websiteconfig" file
> - the ".project" (only alternative project natures/builders)
> do you want to include it the the eclipse plugin or sould it be an extra plugin? i should
not be complicated to include it because i did the real work in writer-classes.
> should i add a tgz with the sources? or how do you want the sources?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message