You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Bruce Snyder (JIRA)" <ji...@apache.org> on 2009/03/08 20:25:39 UTC

[jira] Created: (CAMEL-1436) Archeypes will not output debug level logging

Archeypes will not output debug level logging 
----------------------------------------------

                 Key: CAMEL-1436
                 URL: https://issues.apache.org/activemq/browse/CAMEL-1436
             Project: Apache Camel
          Issue Type: Bug
          Components: tooling
    Affects Versions: 1.6.0
            Reporter: Bruce Snyder
             Fix For: 1.6.1


The archetypes work great but they won't output debug level logging because they don't include a dependency on Log4J. By simply adding the dependency on Log4J, outputting debug level logging is possible. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-1436) Archeypes will not output debug level logging

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated CAMEL-1436:
--------------------------------

    Attachment:     (was: CAMEL-1436.patch)

> Archeypes will not output debug level logging 
> ----------------------------------------------
>
>                 Key: CAMEL-1436
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1436
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 1.6.0
>            Reporter: Bruce Snyder
>             Fix For: 2.0.0, 1.6.1
>
>         Attachments: CAMEL-1436-camel-1.x.patch, CAMEL-1436-camel-2.0.patch
>
>
> The archetypes work great but they won't output debug level logging because they don't include a dependency on Log4J. By simply adding the dependency on Log4J, outputting debug level logging is possible. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-1436) Archeypes will not output debug level logging

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated CAMEL-1436:
--------------------------------

    Attachment: CAMEL-1436.patch

> Archeypes will not output debug level logging 
> ----------------------------------------------
>
>                 Key: CAMEL-1436
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1436
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 1.6.0
>            Reporter: Bruce Snyder
>             Fix For: 1.6.1
>
>         Attachments: CAMEL-1436.patch
>
>
> The archetypes work great but they won't output debug level logging because they don't include a dependency on Log4J. By simply adding the dependency on Log4J, outputting debug level logging is possible. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-1436) Archeypes will not output debug level logging

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated CAMEL-1436:
--------------------------------

    Attachment: CAMEL-1436-camel-2.0.patch
                CAMEL-1436-camel-1.x.patch

> Archeypes will not output debug level logging 
> ----------------------------------------------
>
>                 Key: CAMEL-1436
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1436
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 1.6.0
>            Reporter: Bruce Snyder
>             Fix For: 2.0.0, 1.6.1
>
>         Attachments: CAMEL-1436-camel-1.x.patch, CAMEL-1436-camel-2.0.patch
>
>
> The archetypes work great but they won't output debug level logging because they don't include a dependency on Log4J. By simply adding the dependency on Log4J, outputting debug level logging is possible. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-1436) Archeypes will not output debug level logging

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50322#action_50322 ] 

Bruce Snyder commented on CAMEL-1436:
-------------------------------------

Committed to branches/camel-1.x/: 

Sending        archetypes/camel-archetype-activemq/pom.xml
Sending        archetypes/camel-archetype-activemq/src/main/resources/archetype-resources/pom.xml
Sending        archetypes/camel-archetype-java/pom.xml
Sending        archetypes/camel-archetype-java/src/main/resources/archetype-resources/pom.xml
Sending        archetypes/camel-archetype-scala/pom.xml
Sending        archetypes/camel-archetype-scala/src/main/resources/archetype-resources/pom.xml
Sending        archetypes/camel-archetype-spring/pom.xml
Sending        archetypes/camel-archetype-spring/src/main/resources/archetype-resources/pom.xml
Transmitting file data ........
Committed revision 751507.


Committed to trunk/: 

Sending        archetypes/camel-archetype-activemq/pom.xml
Sending        archetypes/camel-archetype-activemq/src/main/resources/archetype-resources/pom.xml
Sending        archetypes/camel-archetype-java/pom.xml
Sending        archetypes/camel-archetype-java/src/main/resources/archetype-resources/pom.xml
Sending        archetypes/camel-archetype-scala/pom.xml
Sending        archetypes/camel-archetype-scala/src/main/resources/archetype-resources/pom.xml
Sending        archetypes/camel-archetype-spring/pom.xml
Sending        archetypes/camel-archetype-spring/src/main/resources/archetype-resources/pom.xml
Transmitting file data ........
Committed revision 751511.


> Archeypes will not output debug level logging 
> ----------------------------------------------
>
>                 Key: CAMEL-1436
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1436
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 1.6.0
>            Reporter: Bruce Snyder
>             Fix For: 2.0.0, 1.6.1
>
>         Attachments: CAMEL-1436-camel-1.x.patch, CAMEL-1436-camel-2.0.patch
>
>
> The archetypes work great but they won't output debug level logging because they don't include a dependency on Log4J. By simply adding the dependency on Log4J, outputting debug level logging is possible. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CAMEL-1436) Archeypes will not output debug level logging

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder resolved CAMEL-1436.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
         Assignee: Bruce Snyder

> Archeypes will not output debug level logging 
> ----------------------------------------------
>
>                 Key: CAMEL-1436
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1436
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 1.6.0
>            Reporter: Bruce Snyder
>            Assignee: Bruce Snyder
>             Fix For: 2.0.0, 1.6.1
>
>         Attachments: CAMEL-1436-camel-1.x.patch, CAMEL-1436-camel-2.0.patch
>
>
> The archetypes work great but they won't output debug level logging because they don't include a dependency on Log4J. By simply adding the dependency on Log4J, outputting debug level logging is possible. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.