You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Patrick Mueller (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/17 18:02:00 UTC

[jira] [Resolved] (CB-176) add vendor files to weinre instead of pulling in at build time

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

Patrick Mueller resolved CB-176.
--------------------------------

    Resolution: Fixed

fixed in massive commit to master

https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-weinre.git;a=commit;h=c4fbd3d0b3c988025ca17da34bd715be6535a36d
                
> add vendor files to weinre instead of pulling in at build time
> --------------------------------------------------------------
>
>                 Key: CB-176
>                 URL: https://issues.apache.org/jira/browse/CB-176
>             Project: Apache Callback
>          Issue Type: Task
>          Components: weinre
>            Reporter: Patrick Mueller
>            Assignee: Patrick Mueller
>
> The weinre runtime and build currently depends on a number of 3rd party libraries.  These libraries are not currently maintained with the rest of the weinre source, but are pulled in as part of the build.  
> This needs to change so that the libraries are actually maintained with the rest of the source.
> Various NOTICE files and what not will need to be created to note the licenses of this 3rd party software.
> In terms of the actual work, a couple of things will be going on here:
> - adding 3rd party libs like the Web Inspector source to the SCM, with appropriate notices
> - adding 3rd party libs, for which I'm the only author, like modjewel, to the SCM with an ASLv2 license
> - disabling some existing 3rd party lib usage, like the Eclipse SWT libs (which are a licensing nightmare), so that we no longer build or ship things dependent on them

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira