[ http://jira.codehaus.org/browse/MOJO-179?page=comments#action_56426 ]
Scott Ryan commented on MOJO-179: --------------------------------- Sorry I have been distracted by Bronco mania here in Denver but now I have my tickets for the game so back to work. You solution makes sense and I am sure is the best solution for now. However i don't have much experience with the sandbox so I assume you have presented the best option. My plan for the future is the following: 1) Flush out the 8.0 version to contain all features I originally had in version 1.0 2) Refactor the 9.0 plugin to use the Java Deployment standard interfaces so that it can work with any app server. 3) Add the Weblogic specific stuff to the 9.0 plugin 4) Contribute the Java Deployment code to the CARGO project. 5) Update the plugin to work with all other app servers that support the standard deployment JSR 6) Contact the author of the APPC plugin and merge that code with my current APPC code to allow that functionality to be in one place and add my code to 9.0 as well. Some Questions? 1) You are creating the weblogic pom and I also think I need one for the BEA webservices jar that supports the appc functionality. I will have to see how the current appc plugin got around that issue. 2) Today I have to include the tools jar in my pom which is not optimum and I know there is a better solution so I need to research that solution. Again maybe the appc plugin has a better solution. Any suggestions? 3) I am contacting BEA to see if they would be willing to host the various versions of weblogic jar and pom for download on their site. 4) I will have to research the structure of the sandbox and learn how to publish the site and get more documentation up on the site along with some samples. 5) Will there also be a JIRA project associated with this project so i can track issues that are reported without sifting all the issues in mojo? 6) Will I have committer status or do i still upload patches to the JIRA issue and you integrate them? I also have an appfuse plugin on the way so I am sure this will not be the last conversation we have lol. Scott > 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
