Show me an example of a SVN commit with a GERONIMODEVTOOLS-N in it...

--jason


On Sep 29, 2006, at 5:58 AM, Sachin Patel wrote:

FYI this doesn't work for the DEVTOOLS jira's how can I enable it?

On Sep 27, 2006, at 8:52 PM, Jason Dillon wrote:

For the record, I am not pissed off at anyone... it was just a comment, written while I was quite calm and in no way was intended to upset anyone.

I asked this earlier... when I think Joe was doing the same thing (though I do not recall exactly who it was) and he had a reason, because his address was not configured to allow the svn commit mails to come through.   I was just inquiring if there was a reason for the ongoing use of this style of comments... and if there was/is then I would have liked to know about it and work to resolve them to avoid the need for these comments.

 * * *

How come every-time I send email that is not filled with smilies that everyone thinks I hate everyone?

:-P

--jason


On Sep 27, 2006, at 1:54 PM, Paul McMahan wrote:

I'm a new committer and am repeating what I've seen others do.  I
agree its redundant and won't do it any more.   Thanks for the tip.

Paul

On 9/27/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Why do people feel they need to add the output of svn ci to jira
comments?  Add the exact jira id to the svn comment and jira will
link these details.

Adding the output of svn ci to a comment in jira is a poor practice,
which I would like to see stopped.

--jason


On Sep 27, 2006, at 1:22 PM, Paul McMahan (JIRA) wrote:

> page=comments#action_12438211 ]
>
> Paul McMahan commented on GERONIMO-2442:
> ----------------------------------------
>
> Sending        configs\directory\src\main\resources\META-INF
> \geronimo-plugin.xml
> Sending        configs\dojo-jetty\src\main\resources\META-INF
> \geronimo-plugin.xml
> Sending        configs\dojo-tomcat\src\main\resources\META-INF
> \geronimo-plugin.xml
> Sending        configs\jsp-examples-jetty\src\main\resources\META-
> INF\geronimo-plugin.xml
> Sending        configs\jsp-examples-tomcat\src\main\resources\META-
> INF\geronimo-plugin.xml
> Sending        configs\ldap-demo-jetty\src\main\resources\META-INF
> \geronimo-plugin.xml
> Sending        configs\ldap-demo-tomcat\src\main\resources\META-INF
> \geronimo-plugin.xml
> Sending        configs\ldap-realm\src\main\resources\META-INF
> \geronimo-plugin.xml
> Sending        configs\servlet-examples-jetty\src\main\resources
> \META-INF\geronimo-plugin.xml
> Sending        configs\servlet-examples-tomcat\src\main\resources
> \META-INF\geronimo-plugin.xml
> Sending        configs\webconsole-jetty\src\main\resources\META-INF
> \geronimo-plugin.xml
> Sending        configs\webconsole-tomcat\src\main\resources\META-INF
> \geronimo-plugin.xml
> Sending        configs\welcome-jetty\src\main\resources\META-INF
> \geronimo-plugin.xml
> Sending        configs\welcome-tomcat\src\main\resources\META-INF
> \geronimo-plugin.xml
> Transmitting file data ..............
> Committed revision 450564.
>
>> update geronimo-plugin.xml files to use org.apache.geronimo group ids
>> ---------------------------------------------------------------------
>>
>>                 Key: GERONIMO-2442
>>                 URL: http://issues.apache.org/jira/browse/
>> GERONIMO-2442
>>             Project: Geronimo
>>          Issue Type: Bug
>>      Security Level: public(Regular issues)
>>          Components: Plugins
>>    Affects Versions: 1.2
>>            Reporter: Paul McMahan
>>         Assigned To: Paul McMahan
>>             Fix For: 1.2
>>
>>
>> During the m2 conversion effort many of the maven group ids for
>> geronimo modules changed from "geronimo" to
>> "org.apache.geronimo.modules" or "org.apache.geronimo.configs".
>> <prerequisite> and <dependency> elements in several geronimo-
>> plugin.xml files need to be updated to use the new group ids.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the
> Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/
> software/jira
>
>





-sachin



Reply via email to