geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Mulder <>
Subject Re: [vote] Creation of Tooling Subproject
Date Thu, 25 Aug 2005 23:01:46 GMT
+1 on the intent, not so happy with the name:

Is the deployment tool a tool?
Is the web console a tool?
If we had a tool to immutabilize and import and export configurations, 
  would that be a tool?

I think those are all tools and should be very closely tied to the
Geronimo release schedule and not the Eclipse plugin release schedule.  
Therefore I'd lean toward calling this the "IDE" subproject, or the "tool
integration" subproject or something like that.  Though this does seem to 
be a logical place to put the XDoclet code we talked about...  Maybe 
a "Development Tools" subproject name & "devtools" repo name?


On Thu, 25 Aug 2005, Geir Magnusson Jr. wrote:
> We've had the subject out for discussion for a few days, and had some  
> good feedback.  I think we should take a vote on the creation of a  
> Tooling subproject.  I'm going to just wing it here as this is our  
> first one, so any additions and mods are welcome, protests are  
> welcome, etc.  I'd prefer if we can do this by lazy consensus, but  
> maybe that's an add-on poll for next time.
> Apache Geronimo Tooling Subproject
> ----------------------------------
> The Apache Geronimo PMC hereby creates a subproject focused on  
> tooling related to the Apache Geronimo project.  The subproject will  
> be a home for software tools that are independent of the operation of  
> the general Geronimo container, or the J2EE server configuration.   
> Decisions about appropriateness for inclusion shall remain up to the  
> Geronimo PMC.
> 1) The tooling subproject shall have a separate root in the project  
> subversion repository.  Proposed :
> 2) The tooling subproject shall have a separate entry under a  
> "Subprojects" heading on the website.
> 3) The artifacts of the tooling subproject shall have an independent  
> release cycle as appropriate for the sub-project, and is strongly  
> encouraged to time releases to that of the main server to ensure that  
> users get appropriate tooling for new server releases.
> 4) The tooling subproject will be organized anticipating multiple  
> tools of equal status in the subproject.
> 5) The eclipse plugin source base, currently residing in trunk/ 
> sandbox, shall be moved to the tooling subproject.
> This vote will run until Sat, Aug 27 at 12 Noon EDT.
> [ ] +1 Create the tooling subproject.
> [ ] -1 Do not create the tooling subproject.
> Comments : (Anyone have a better name?)
> -- 
> Geir Magnusson Jr                                  +1-203-665-6437

View raw message