[ http://jira.codehaus.org/browse/MOJO-179?page=comments#action_56213 ]
Corridor Software Developer commented on MOJO-179: -------------------------------------------------- Thanks for the clarification. I'm assuming you've already considered a commit 8.x-branch 8.x-commit 9.x the ideal option for handling the multiple versions. Here's a rundown of what I plan to do barring other ideas. Create a single weblogic-maven-plugin project underneath the mojo-sandbox. I'll commit the 8.x series as weblogic-maven-plugin-2.8-SNAPSHOT. We'll establish a branch from there for modifications to this line. Then the 9.x code will be commited to the trunk. An explanation of the version mapping between Maven and Weblogic will be included on the site. If it isn't there already, I'll put in a ticket for the weblogic.jar pom.xml. Thoughts? > Maven-2 Weblogic Plugin > ----------------------- > > Key: MOJO-179 > URL: http://jira.codehaus.org/browse/MOJO-179 > Project: Mojo > Type: New Feature > Environment: Maven 2.0 and Weblogic 8.1.5 > Reporter: Scott Ryan > Assignee: Corridor Software Developer > Attachments: maven-weblogic-plugin-2.0-alpha-1-SNAPSHOT.jar, > maven-weblogic-plugin-2.8.0.jar, maven-weblogic-plugin-2.8.0.jar, > maven-weblogic-plugin-2.9.0-alpha.jar, sampleconfigfile.txt, > weblogicplugin-2.8.0.zip, weblogicplugin-2.8.0.zip, weblogicplugin-2.9.0.zip, > weblogicplugin.zip > > > I have ported the maven 1.0 weblogic plugin over to Maven2.0. Currently it > is in alpha and only supports a subset of the functions of the Maven 1.0 > plugin. Today the plugin supports deploy, undeploy, redeploy, start > application and stop application. In order to use the plugin you will need > to place the plugin in the correct location in your repository. You will > also need to install a copy of the weblogic.jar from your installation into > the directory weblogic\weblogic\8.1.5.0\weblogic-8.1.5.0.jar in your > repository. You can use the 8.1.2,8.1.3, or 8.1.4 library but have to use > the 8.1.5.0 name for now. i am also working on a 9.0 version. There are > logical defaults for all parameters but below I have presented a sample of a > pom.xml plugin configuration for all parameters. The targets can be servers > or cluster names. All goal are tied to the integration-test phase. > I welcome all feedback and suggestions on what to add next and my team and I > will work to make it happen. I hope this moves to the sandbox soon. > <plugins> > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>maven-weblogic-plugin</artifactId> > <configuration> > <adminServerHostName>localhost</adminServerHostName> > <adminServerPort>7001</adminServerPort> > <userId>weblogic</userId> > > <objectPath>${project.build.outputDirectory}/../${project.artifactId}.${project.packaging}</objectPath> > <password>weblogic</password> > <name>${project.artifactId}</name> > <staging>nostage</staging> > <targetNames> > <targetName>myserver</targetName> > </targetNames> > </configuration> > </plugin> > </plugins> -- 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
