[wildfly-dev] WFLY/WFCORE PRs

Brian Stansberry brian.stansberry at redhat.com
Tue Sep 6 14:17:17 EDT 2016


Thanks!

The install process shown on https://developer.chrome.com/extensions/getstarted#unpacked didn’t work for Max’s but it did for yours. :)

I suspect I could get Max’s to work if I stuck the js I have in its own dir and added a manifest.json that looks like yours. But instead I’ll try yours out now!

> On Sep 2, 2016, at 3:47 PM, Peter Palaga <ppalaga at redhat.com> wrote:
> 
> It is still possible to load a non-Web Store extension in Chrome. I am not 100% sure it works for the one from Max, it works for my [1] Jira linker for sure. -- P
> 
> [1] https://github.com/ppalaga/jboss-jira-content-script#jboss-jira-content-script
> 
> On 2016-09-01 15:37, Brian Stansberry wrote:
>> I’ll try and be better about that. I used to count on Max Andersen's AutoLink browser extension (which was great!) to generate links from just the issue number text, but now Chrome has been updated to block extensions that aren’t from the Chrome Web Store. Grumble grumble.
>> 
>>> On Sep 1, 2016, at 5:07 AM, Kabir Khan <kabir.khan at jboss.com> wrote:
>>> 
>>> Please try to include a link to the Jira in the pull request when opening them. I want to be a good citizen and resolve them when merging, but it is a PITA to have to manually find the Jira issue in the absence of links.
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> 
> 

-- 
Brian Stansberry
Manager, Senior Principal Software Engineer
JBoss by Red Hat






More information about the wildfly-dev mailing list