[jira] Updated: (MECLIPSE-137) Developed RAD-6 Plugin Extention
[ http://jira.codehaus.org/browse/MECLIPSE-137?page=all ] Brandon Burk updated MECLIPSE-137: -- Attachment: MECLIPSE-137-maven-rad-plugin.zip This file contains the changes my organization needed. This includes several months of bug fixes and feature additions so I'll hit the highlights, and these are from memory as I am doing this from home and not on company time. Primary bug fix (that I can remember)... -- Rad6ApplicationXMLWriter.java: changed: private static final String XMLNS_SCHEMA_LOCATION = xmlns:schemaLocation; to: private static final String XMLNS_SCHEMA_LOCATION = xsi:schemaLocation; Primary functionality changes (that I can remember)... Added... -- AbstractRad6Writer.java: This class provides some functionality that I found myself needing in several of the other writers. Things such as: getMetaInfDirectory() getWarSourceDirectory() getJ2eeSpecVersion() getWarContextRoot() - this one was interesting... could probably be written better but seems to work nicely. I don't know a better way to share configuration information between plugins (i.e. maven-war-plugin looking something up from the maven-ear-plugin of a sibling project) Added... -- Rad6CvsIgnoreWriter.java: This class creates or appends to the .cvsignore files for CVS projects. My organization needed this for easier transition to using the plugin as we had hundreds of projects with the Eclipse/RAD specific configuration files checked into CVS. Now that the Eclipse/RAD plugin so lovingly configures all these files dynamically we had lots of questions from users wondering if they needed to commit their dot files back to CVS every time they ran the plugin. My goal was to keep all that junk out of version control and let the POM+Eclipse/RAD plugin abstract away the details of IDE configuration. This will add things like target .* MANIFEST.MF to the appropriate .cvsignore files in the projects. This functionality could be equally necessary for subversion or other version control systems. Also the ability to enable/disable this feature is needed for users who don't use CVS, I have not implemented that. Modified... -- Rad6ApplicationXMLWriter.java Added support for multiple J2EE specification versions (i.e. 1.3 as well as the default of 1.4). createNewApplicationXml() will now create the appropriate 1.3 spec application.xml Added support for custom WAR context roots to be maintained. updateApplicationXml() uses getWarContextRoot() from the AbstractRad6Writer -- Rad6J2EEWriter.java Added support for multiple J2EE specification versions (i.e. 1.3 as well as the default 1.4). writeModuleTypeFacetCore() will now write the .j2ee file specific to the j2eeSpecVersion -- Rad6ManifestWriter.java Refactored to take advantage of the AbstractRad6Writer.getMetaInfDirectory() -- Rad6WarClasspathWriter.java Refactored to take advantage of the AbstractRad6Writer.getRelativeWebInfDirectory() -- Rad6WebSettingsWriter.java writeModuleTypeFacetCore() updated to use getWarContextRoot() instead of hardcoding the artifactId and use the AbstractRad6Writer.getRelativeWarSourceDirectory() I hope this helps anyones struggling with similar issues. Developed RAD-6 Plugin Extention Key: MECLIPSE-137 URL: http://jira.codehaus.org/browse/MECLIPSE-137 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Reporter: Richard van Nieuwenhoven Assigned To: John Casey Attachments: maven-rad-plugin-WebContent.zip, maven-rad-plugin.tar.gz, maven-rad-plugin.zip, MECLIPSE-137-maven-eclipse-plugin.patch, MECLIPSE-137-maven-rad-plugin.zip 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: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-137) Developed RAD-6 Plugin Extention
[ http://jira.codehaus.org/browse/MECLIPSE-137?page=all ] Lee Jonas updated MECLIPSE-137: --- Attachment: MECLIPSE-137-maven-eclipse-plugin.patch John, I have attached a patch file containing an initial attempt at honouring the warSourceDirectory setting on the maven-war-plugin, based on something done elsewhere in the maven-eclipse-plugin. It also contains a modification to the RadWebSettingsWriter to include referenced projects within the same RAD workspace - they were not getting loaded when launching the web app in a test server. regards Lee Developed RAD-6 Plugin Extention Key: MECLIPSE-137 URL: http://jira.codehaus.org/browse/MECLIPSE-137 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Reporter: Richard van Nieuwenhoven Assigned To: John Casey Attachments: maven-rad-plugin-WebContent.zip, maven-rad-plugin.tar.gz, maven-rad-plugin.zip, MECLIPSE-137-maven-eclipse-plugin.patch 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: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-137) Developed RAD-6 Plugin Extention
[ http://jira.codehaus.org/browse/MECLIPSE-137?page=all ] Lee Jonas updated MECLIPSE-137: --- Attachment: maven-rad-plugin-WebContent.zip Alternative version of this plugin that uses the WebContent directory for web content files. Developed RAD-6 Plugin Extention Key: MECLIPSE-137 URL: http://jira.codehaus.org/browse/MECLIPSE-137 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Reporter: Richard van Nieuwenhoven Attachments: maven-rad-plugin-WebContent.zip, maven-rad-plugin.tar.gz, maven-rad-plugin.zip 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: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-137) Developed RAD-6 Plugin Extention
[ http://jira.codehaus.org/browse/MECLIPSE-137?page=all ] Richard van Nieuwenhoven updated MECLIPSE-137: -- Attachment: maven-rad-plugin.zip I have not much time to spend for support on this plugin, i made/appened it for a customer (UNIQA Austria). But still any extentions are welcome, and as long as there is no own project and it is not integerated in the eclipse plugin we should post them here. i have not the time to make and support a seperate project. Because the project (i worked on) ended successfuly, i do not work on this plugin anymore (for now). Please feel free to contact me, i will give you an email kontact of the responsible person in UNIQA Austria. They are happy to meet and work together with others also using Maven-2, RAD6 and websphere. They also ported or working on porting a lot of the was-5/6 admin ant tasks to maven-2 goals for websphere-6 integration tests. in this updated version i deleted the localreposetorys (sorry for that) so it should build anywhere now. Developed RAD-6 Plugin Extention Key: MECLIPSE-137 URL: http://jira.codehaus.org/browse/MECLIPSE-137 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Reporter: Richard van Nieuwenhoven Attachments: maven-rad-plugin.tar.gz, maven-rad-plugin.zip 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: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-137) Developed RAD-6 Plugin Extention
[ http://jira.codehaus.org/browse/MECLIPSE-137?page=all ] Richard van Nieuwenhoven updated MECLIPSE-137: -- Attachment: maven-rad-plugin.tar.gz sorry that it took so long but i was not at work... this is the tarball with the plugin. some hints for RAD6 users - do not use java classes in a war project, put all java classes in dependent projects - best thing to do is to make all jars in the war project provided and put them in the ear dependencys - there will be a classpath directory included in ejb projects here you can put your generated ejb classes for nor i use the websphere-ant jobs in the project-pom to generate them. (in the package phase overwiting the jar and the client-jar and copieing the classes to the classes-folder included by this plugin, the ant-job does not generate the java files...) - the META-INF of the ejb project MUST!!! be a toplevel folder so include this top-level-folder in your resources list of the pom (the java files can stay in src/main/java - don't forget to fill the .cvsignore files especialy the jar's and wars in the ear-project's and the war-project's regards, Ritchie Developed RAD-6 Plugin Extention Key: MECLIPSE-137 URL: http://jira.codehaus.org/browse/MECLIPSE-137 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: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
