RE: contribution/donation of websphere 5.x and weblogic 8.x plugins
On Sat, 2004-03-13 at 17:53, Tim Reilly wrote: > > [Jason van Zyl wrote:] > > > If you're not a Maven committer the best place to put the plugin is > > somewhere you have access to it. > > If you want to share it with others a place like, > http://maven-plugins.sourceforge.net/ seems appropriate. > I'd suggest to Edward perhaps re-posting the question to one of the lists > found here: > http://sourceforge.net/mail/?group_id=61626 > > > We're not going to go through the > > process of making someone a committer for a plugin. > > I didn't think being committer was required to make a contribution. It isn't, but if you contribute a plugin for which you are the only author then maintaining it becomes a problem because you need to rely on a committer to keep the plugin updated. That's not something we want to do. I'm been trying to flush the plugins out to locations where those most interested can work on it freely without being bottlenecked by how fast we process patches. > (I do believe ASF is asking for CLA's for everyone; contributors of patches, > those posting useful ideas on mailing lists, anything intellectual property > related - not just for committers.) It's not an IP issue, it's a maintenance issue. I would like releases for plugins to become fully independent of the core and we're getting there. Having plugins developed elsewhere also encourages this. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org believe nothing, no matter where you read it, or who has said it, not even if i have said it, unless it agrees with your own reason and your own common sense. -- Buddha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cannot get plugin variable values
Hi,
I am having some trouble getting variable values from a plugin context. From one
plugin, the
following expression retrieves the expected value:
${pom.getPluginContext('maven-javadoc-plugin').getVariable('maven.javadoc.destdir')
However, from another plugin, this expression returns no value. How can this happen?
Also, this
expression returns no value when placed within my maven.xml file. Should I be able to
use this
type of expression in maven.xml?
Cheers,
Chuck
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: contribution/donation of websphere 5.x and weblogic 8.x plugins
> [Jason van Zyl wrote:] > If you're not a Maven committer the best place to put the plugin is > somewhere you have access to it. If you want to share it with others a place like, http://maven-plugins.sourceforge.net/ seems appropriate. I'd suggest to Edward perhaps re-posting the question to one of the lists found here: http://sourceforge.net/mail/?group_id=61626 > We're not going to go through the > process of making someone a committer for a plugin. I didn't think being committer was required to make a contribution. (I do believe ASF is asking for CLA's for everyone; contributors of patches, those posting useful ideas on mailing lists, anything intellectual property related - not just for committers.) > It doesn't matter where plugins are developed anymore, "The Apache Software Foundation exists to provide organizational, legal, and financial support." -ASF If you're not looking for that, then the above is true I suppose. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem while downloading dependency?
Hi, I specified XDoclet 1.2 as dependency in my project with the following element: xdoclet xdoclet 1.2 http://xdoclet.sourceforge.net/ When executing Maven, I obtain the following message from the console: Attempting to download xdoclet-1.2.jar. . . Error retrieving artifact from [d:\Program Files\Apache Software Foundation\Maven 1.0-rc1/plugins/xdoclet/jars/xdoc let-1.2.jar]: java.net.MalformedURLException: unknown protocol: d The application continues without particular problems. Shall I worry about it? Thanks for any reply, Marco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: contribution/donation of websphere 5.x and weblogic 8.x plugins
On Sat, 2004-03-13 at 15:25, Tim Reilly wrote: > Here's what I know. Hopefully a more authoritative voice chimes in. > > > 1. What is the process of donating plugins to maven.apache? I'll just nip this in the bud. If you're not a Maven committer the best place to put the plugin is somewhere you have access to it. We're not going to go through the process of making someone a committer for a plugin. It doesn't matter where plugins are developed anymore, they are easy to install and integrate into a Maven build. If you have a plugin you want to share it ultimately doesn't matter where it's developed and we would actually prefer not to host them here at Apache. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: contribution/donation of websphere 5.x and weblogic 8.x plugins
Here's what I know. Hopefully a more authoritative voice chimes in. > 1. What is the process of donating plugins to maven.apache? Donating code in general; You'll need to do one or both of the following; fax or mail a signed Corporate Contributor License Agreement or Software Grant; http://www.apache.org/licenses/cla-corporate.txt or http://www.apache.org/licenses/software-grant.txt If you're an individual contributing then its the individual CLA. It's totally UNclear what constitutes a "body" of work, as opposed to a patch / contribution to an existing project or body of work. My thinking is that the CLA is appropriate for your contribution and not a grant, but I'm no expert. This page discusses the process: http://www.apache.org/foundation/contributing.html , and this page links to the various licenses http://www.apache.org/licenses/ > 2. How long does it take to go through this process? - CLA Process: Discuss if the community wants the patches such as you're doing here. Send in the CLA paperwork. Apply the Apache 2.0 license to your work. Send patch(es), usually using the project's issue tracking tool. - Grant Process: If you have to do the software grant process, I'm not sure how long it takes or how it works. > 3. Are there any requirements/obligations for further support of these > plugins on my part? Not as far as I'm aware unless you want to. I think the operative word(s) are require or obligated. Normally people want to see their contributions through. Of course there's no obligation for the committers of a project to apply the patches or contributions. To that end you should try to re-format your contribution to fit the project's style guidelines, as well as provide unit-tests, documentation, etc. ** One note: The fact the optional plugin's are hosted on Sourceforge.net and not on Apache.org tells me that all of the above may or may not apply. ?? I don't think these codebases are technically ASF anymore? Anyone else know? ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
contribution/donation of websphere 5.x and weblogic 8.x plugins
dIon, thanks for url. maven-was5-plugin does not provide goals to
setup/destroy cluster(s), start/stop cluster(s) and deploy/undeploy to/from
cluster(s). I'll try to contact Richard Lewis-Shell to see his thoughts on
functionalities provided by both plug-ins (may be merge to one) but before
further development in this direction I still need to provide to my
corporate execs the answers to the following questions:
1. What is the process of donating plugins to maven.apache?
2. How long does it take to go through this process?
3. Are there any requirements/obligations for further support of these
plugins on my part?
Thanks,
-edward
P.S. Here is a listing of goals and table of properties used to control
plugins described in e-mail below (For best viewing paste it in
non-word-wrapped text editor (notepad, etc.):
1) plugin for weblogic 8.x
2) plugin for websphere 5.x
3) plugin that executes goals provided by the previous 2 plugins.
Determination of which one to use is derived from the property set by
user.
This property can indicate to use both plugins and the order of the
usage.
The following listing contains "" that should be substituted by
either "weblogic" or "websphere".
Here is the listing of goals provided by plugin 1 and 2:
:init-env - setup your J2EE appserver environment
according to the properties that you specify in project.properties,
$USER_HOME/build.properties or properties provided on maven command line
(-Dprop.x=x -Dprop.y=y ...).
:deploy-ejb - starts necessary servers and deploys your
ejb artifacts on , this goal tries to attain
:config-resources which in turn calls
${pom.artifactId}::config-resources goal before deploying ejb and
calls :post-deploy-config-resources which calls
${pom.artifactId}::post-deploy-config-resources after ejb deployment
:deploy-ear - starts necessary servers and deploys your
ear artifacts on , this goal tries to attain
:config-resources which in turn calls
${pom.artifactId}::config-resources goal before deploying ear and
calls :post-deploy-config-resources which calls
${pom.artifactId}::post-deploy-config-resources after ear deployment
:undeploy - starts necessary servers and undeploys your
j2ee artifacts from this goal tries to attain
:clean-resources which in turn calls
${pom.artifactId}::clean-resources goal before undeploying ejb and
calls :post-undeploy-clean-resources which calls
${pom.artifactId}::post-undeploy-cleean-resources after undeployment
So what ${pom.artifactId}:websphere:blah-blah-blah and
${pom.artifactId}:weblogic:blah-blah-blah goals are for?
- These goals must be implemented in every J2EE project's maven.xml.
Implementation may be blank. If you are deploying an artifact that requires
setup of J2EE resources (ex: deploy MDB that requires JMSQueue) then ths
goals should contain the implementation of setup and clean up of J2EE
resources (JMSQueue in this case).
${pom.artifactId}::config-resources - goal to accomplish
the setup of necessary J2EE resources on required for successful
j2ee artifact deployment, this goal is called prior the j2ee artifact
deployment
${pom.artifactId}::post-deploy-config-resources - goal to
accomplish the setup of necessary J2EE resources on required for
successful execution of j2ee artifact, this goal is called after j2ee
artifact deployment
${pom.artifactId}::clean-resources - goal to accomplish
the cleanup of necessary J2EE resources from required for
successful j2ee artifact undeployment, this goal is called prior the j2ee
artifact undeployment
${pom.artifactId}:weblogic:post-undeploy-cleean-resources - goal to
accomplish the cleanup of necessary J2EE resources from after j2ee
artifact undeployment
:clean-env - removes all managed servers and clusters
form environment that were created at the attainment of
:init-env goal
In addition you can use the following goals out of band to manage your J2EE
runtime environment
:startadminserver - starts adminserver
:stopadminserver- stops adminserver
:startup- starts all admin and
managed servers and clusters
:shutdown - stops all admin and managed
servers and clusters
:startmanagedservers- starts all managed servers
and clusters
:stopmanagedservers - stops all managed servers
and clusters
:startstandaloneservers - starts all managed
standalone servers
:stopstandaloneservers - stops all managed
standalone servers
:startclusters - starts all managed clusters
:stopclusters - stops all managed clusters
The following table lists the properties used to control the above plugins:
#---
--
Re: [javadoc plugin] Javadocs not generated correctly
Any takers? --- Charles Daniels <[EMAIL PROTECTED]> wrote: > I posted this issue earlier, but had only a couple of replies without any > suggestions for a fix, > so I will ask again to see if there is a solution. The problem I am encountering is > that the > javadoc plugin does not generate the package summary table, nor does it generate the > standard > frame that appears in the upper left of the browser (where the package list should > appear). > > An earlier reply indicated that the javadocs are correctly generated when using JDK > 1.4, but I > must be able to use JDK 1.3. I cannot create a dependency on JDK 1.4 for this > project. I > looked > at the plugin script, but can't see anything wrong with it. Any pointers? > > Cheers, > Chuck > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: contribution/donation of websphere 5.x and weblogic 8.x plugins
FYI, there is a websphere 5.x plugin under development on sourceforge. See http://maven-plugins.sourceforge.net/maven-was5-plugin/ -- dIon Gillard, Multitask Consulting "Kaganovich, Edward" <[EMAIL PROTECTED]> wrote on 13/03/2004 08:18:39 PM: > > Hello All, let me first appologize if I'm using wrong mailing list. I have > developed the following plugins that I'm interested to donate to > maven.apache for further development and maintanence: > > 1) plugin for weblogic 8.x > 2) plugin for websphere 5.x > 3) plugin that executes goals provided by the previous 2 plugins. > Determination of which one to use is derived from the property set by user. > This property can indicate to use both plugins and the order of the usage. > > The first two plugins provide symmetric functionality to setup/destroy > servers/clusters; startup/shutdown of servers/clusters; ejb/ear (war, rar > type artifacts can be added easily) deployment/undeployment to > servers/clusters or subset of servers in a cluster; j2ee resource > setup/destroy from servers/clusters. So before you dive into the details of > these plugins I'm looking for answers to the following questions: > > 1. What is the process of donating plugins to maven.apache? > 2. How long does it take to go through this process? > 3. Are there any requirements/obligations for further support of these > plugins on my part? > > I need these answers to provide to corporate execs before they can make any > decisions on the donation of these plugins. (There may be follow up > questions) > > The attached file contains the listing of goals and properties used to > control the above plugins. > > Thanks for your feedback and response. > -edward > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
contribution/donation of websphere 5.x and weblogic 8.x plugins
Hello All, let me first appologize if I'm using wrong mailing list. I have developed the following plugins that I'm interested to donate to maven.apache for further development and maintanence: 1) plugin for weblogic 8.x 2) plugin for websphere 5.x 3) plugin that executes goals provided by the previous 2 plugins. Determination of which one to use is derived from the property set by user. This property can indicate to use both plugins and the order of the usage. The first two plugins provide symmetric functionality to setup/destroy servers/clusters; startup/shutdown of servers/clusters; ejb/ear (war, rar type artifacts can be added easily) deployment/undeployment to servers/clusters or subset of servers in a cluster; j2ee resource setup/destroy from servers/clusters. So before you dive into the details of these plugins I'm looking for answers to the following questions: 1. What is the process of donating plugins to maven.apache? 2. How long does it take to go through this process? 3. Are there any requirements/obligations for further support of these plugins on my part? I need these answers to provide to corporate execs before they can make any decisions on the donation of these plugins. (There may be follow up questions) The attached file contains the listing of goals and properties used to control the above plugins. Thanks for your feedback and response. -edward - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
