Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of jason.dillon@gmail.com
 designates 64.233.166.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender;
        b=rmgvGiioQH04iahBo9Qn0xyrYS5KAnR1DIahdjpF7ezqckYauqtcwL/oiSEMasBsbXbffvP1TaX8cC9DpUe/rMiZCI/AtUZtgTQov5Nd1tZ8rV2WosFxEM8mwuJwOkba8Iw9InZlE5274PDq4ge+6QV8wiByWTkL3H8omWsTiZk=
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <20060806163128.98643.qmail@web31707.mail.mud.yahoo.com>
References: <20060806163128.98643.qmail@web31707.mail.mud.yahoo.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <D9674575-723B-4BE7-A312-0C41944C187E@planet57.com>
Content-Transfer-Encoding: 7bit
From: Jason Dillon <jason@planet57.com>
Subject: Re: M2 : car-maven-plugin and geronimo-plugin.xml files
Date: Sun, 6 Aug 2006 19:32:07 -0700
To: dev@geronimo.apache.org
Sender: Jason Dillon <jason.dillon@gmail.com>

Anita, I am aware of this issue.  I have not had time to resolve it  
completely.

More comments below...

On Aug 6, 2006, at 9:31 AM, anita kulshreshtha wrote:
> The car-maven-plugin (trunk rev 429115) still does not add the
> geronimo-plugin.xml file to the generated car. I had submitted a
> working patch for the m2migration branch rev 425727 to include
> geronimo-plugin.xml file to the zipped archive car. The patch was not
> used, instead the plugin code was modified to add this
> functionality.

I only added a few changes you had in the original patch since they  
were the only ones that could be added cleanly.  As you mentioned,  
then functionality is still not there, so I really have issues with  
the last sentence above.


> I do believe in experiments when they work.

Which means?


> I will be happy to elaborate on this, if anyone is interested.  Could
> someone else (PMC member or committer) please explain to me why the
> patch can not be used as is.

Do you really want me to critique the original sources?  I certainly  
can do that, but my feeling is that it will only add more fuel to  
this fire and leave both of us even more frustrated.  I have already  
commented on several major issues with the code in previous emails.


> It is a few lines of code that uses
> geronimo code to do its work, hence AFAICT this is not about not
> trusting the code written by a non committer/non IBMer.

Hrm... what?  How does this have anything to do with IBM?


> I am amazed at the amount of effort being spent to rewrite the  
> plugin without giving
> any technical reason as to why it needs to be modified in the first
> place !

I have posted several technical reasons why I did not take your work  
asis in my response to the last inflammatory email you posted on this  
subject.  But, as I mentioned above if you would like a more  
comprehensive critique...


> The original patch that added this functionality was submitted
> on 19th June 06:
> http://issues.apache.org/jira/browse/GERONIMO-2067#action_12416768
>
> When GERONIMO-2225 was filed, it became clear that there was interest
> in adding this functionality to the plugin. I resubmitted the patch
> for the m2migration branch on 27th July, 06:
> http://issues.apache.org/jira/browse/GERONIMO-2067#action_12416768

Give me a break... I was in the east coast for a week and then was  
camping for this weekend... and when I was working on m2migration I  
had several other issues to resolve on top of the issue which you  
supplied a patch for.


> As expected the patch was not used, and a futile effort to rewrite the
> code was made. I would really appreciate if some other committer/PMC
> member could take a look at this code, and provide some technical
> feedback about its shortcomings.

Yes you did submit a patch on July 27th... thank you.  I fully intend  
to dig into that issue more, I just have not had time to do so yet.   
But I can tell you right now that I will most lilly not take the  
patch asis for the very same reasons why I had changed the plugin  
before.

--jason