You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bigtop.apache.org by "Sean Mackrory (JIRA)" <ji...@apache.org> on 2013/10/09 00:30:42 UTC

[jira] [Updated] (BIGTOP-1070) Add BIGTOP_CLASSPATH functionality to tomcat deployment

     [ https://issues.apache.org/jira/browse/BIGTOP-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Mackrory updated BIGTOP-1070:
----------------------------------

    Attachment: 0001-BIGTOP-1070.-Add-BIGTOP_CLASSPATH-functionality-to-t.patch

[~rvs], would you mind giving this a quick re-review? I had to rebase it on top of some other recent fixes that have gone in and make minor changes. I also simplified the regular expression I was using in sed as that technique appears to not be supported on the older distros.

> Add BIGTOP_CLASSPATH functionality to tomcat deployment
> -------------------------------------------------------
>
>                 Key: BIGTOP-1070
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1070
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>            Priority: Blocker
>             Fix For: 0.7.0
>
>         Attachments: 0001-BIGTOP-1070.-Add-BIGTOP_CLASSPATH-functionality-to-t.patch, 0001-BIGTOP-1070.-Add-BIGTOP_CLASSPATH-functionality-to-t.patch
>
>
> BIGTOP-811 originally wanted to add the ability to detect SQL connectors and other plugins in standard locations and dynmically add them to the classpath. This effort stopped short when it became clear that a major architectural change was needed to make this work for Tomcat-based components. This was one of the main motivations for BIGTOP-939, which is now completed. We need to add a small snippet of code to integrate the two efforts, so the dynamic tomcat deployment can now use BIGTOP_CLASSPATH.



--
This message was sent by Atlassian JIRA
(v6.1#6144)