When I explored and worked on HttpUnit 3 yrs back I liked it for what it does. Though after 3 yrs of not tracking it, when I suggested a solution based on it to my colleague, he told me it is deprecated? The apache status tells it is active. No where I could find if this is true. I will be shocked if that is true. Went thro the bug list and found no assignees for last 1 year. Should I conclude from this inference that it is deprecated?
The news has not been updated because the website has not been updated, and is no longer current with the changes to sourceforge. I am looking into moving the project to github.
My name is Wolfgang Fahl and I am one of the committers of httpunit.
The project is not dead. Russell and me still commit changes regularly. Progress is slow since there are not too many developers involved. You are kindly invited to participate if you'd like to see any improvements. We have just released 1.7.2 to maven.org a few weeks ago:
http://search.maven.org/#artifactdetails|org.httpunit|httpunit|1.7.2|jar
See
https://stackoverflow.com/questions/21705675/patch-process-for-httpunit/21706183#21706183
for an ongoing activity. Please feel free to ask more questions here.
Related
Easily seen in the JSON result from this:
https://www.linkedin.com/countserv/count/share?url=https://www.linkedin.com
Which currently returns:
IN.Tags.Share.handleCount(
{
"count":0,
"fCnt":"0",
"fCntPlusOne":"1",
"url":"https:\/\/www.linkedin.com"
});
Apparently it affects most of the LinkedIn Share buttons/counters out there on the web, including WordPress and other blogs. This has been "broken" since late last week (13 Jan 2018).
I opened a ticket with LinkedIn support. Response was to post here, as this is where the LinkedIn Developers support resides. Hoping for a response that says "Oops, we'll fix this." Or, if deliberately crippled, an announcement that says so. (Twitter made a similar move a few years ago. It was unpopular among developers, but we've moved on.)
Further to Chris Hemedingers response, this feature has now been entirely deprecated
Deprecating the inShare Counter
As you can see they have deprecated this saying:
The share count on its own doesn’t fully reflect the impact that a piece of content delivers, and we encourage publishers and other content creators to leverage the inShare plugin as a way to drive conversation and engage with members on LinkedIn.
They then link to the Documentation saying:
Share on LinkedIn plugin will no longer return share count.
This is massively inconvenient for my company as we have just finished construction of a suite of tools powered by this.
The share count service is back in operation, working as it was before. The outage was deliberate (apparently) but temporary.
As far as I know this is an undocumented API, but it's integral to the "LinkedIn Share" buttons that are used in countless websites/blogs around the world. As such, LinkedIn has no contract/obligation to keep that service running...so consumers of the service in non-LinkedIn components should beware.
Thank you for the update! That was quite frustrating to track this down. I had to research the code, request from the API itself with multiple URLs, submitted a ticket to LinkedIn... and ultimately found myself here and read this. Just a recommendation, I think it would be better to return some kind of error code than a 0. Many people actually display the count on their sites.
I'm just starting with meteor (and programming) and I am having problems with the sorting in Chapter 13 (Upvoting).
It should sort the to 5 pages based on the number of votes. Currently the sort order is:
2 votes
2 votes
1 vote
2 votes
2 votes
I already tried debugging, but still failing miserably because I cannot figure out where the query is built and where it is executed.
So I would still have problems pinpointing to where to problematic code is.
I have a github repository where my current state is available.
Personal Github 13-5
Offical discovermeteor github commit
It would be great if someone could pinpoint me to where I should look, how to debug it or what line(s) are problematic.
Thx for the clue. But as I mentioned in the question, I do not have enough experience to tell where the problem lies. Anyway. I found the problem. It had a template helper (without the correct parameters) which was used instead of the find method I created in the router.
Is thegraphpackage still available in Roo? I would like to create graphs with Neo4J but i can't find any recent documentation or examples about the feature.
No, the graph package Neo4j is not available in the current, 1.2.5, release of Roo and history informs us that any promise to restore support should be viewed skeptically
This antiquated exchange suggests, along with 3-4 others dated as recently as one year ago, that there is little ground for hope. Moreover, the GitHub activity charts (Sorry, my SO "reputation" is not adequate to post another link. You'll have to figure this one out without help.) show zero development activity related to Spring Roo during the last month. I didn't dig much deeper but the front page shows essentially no activity in the last six months. That's not a good sign. I did read that a new development partner has just signed on, so maybe things will improve. I'm very new to Roo but I'm finding bug after bug, and problem after problem, many of them outstanding, like the absence of Neo4j, for years. I really like Roo's ideas and design but I'm not sure that I'm willing to bet on its robustness let alone its longevity. I don't seem to be alone. I searched the web and asked here but can't find direct evidence (that is, code that I can examine) that it's being used on real-world projects. Folks pick it up and toy around with it. But if they write more than 40 lines or so of code they don't open their source. (Please understand that I'm no deliberate detractor; I'd be delighted to be proven wrong on this point!)
One of the saddest consequences of not having Neo4j is that one of the three existing Roo books, Getting Started with Roo, takes it on the chin beginning near the end of the first chapter. This is otherwise an outstanding book. But the absence of Neo4j kicks its ongoing-project model right upside the head. I know the labor entailed by writing a book. Josh Long must be severely disappointed.
More generally, it seems that tech authors are being implicitly encouraged to write small chunks of code that stand on their own, so that their book won't be damaged overall by one or two technological changes. Of course, readers then never get to see code of significant size. I don't have a solution to offer but I'm definitely feeling the problem.
Edited: Because at least one passerby is demonstrably incapable of understanding the implications of repeatedly broken promises to restore support for Neo4j "in the next few days" several years ago I have explicitly spelled out the fact that support is not currently available and no credible promise of soon restoration is to be found. Please note that a broken promise to restore support implies that support was not restored and subsequent promises to restore support should be treated with some degree of skepticism. So, those who suppose that this answer is "not useful" would likely benefit from the web site. readingcomprehensionconnection.com. Or perhaps the problem is one of attention deficit, which makes it difficult to read more than a few phrases before forming a necessarily hasty conclusion. In that case, one might consider cutting back on the comic books in favor of some reading material without speech balloons. I suppose that I am not alone in finding it difficult to incorporate speech balloons in my merely textual SO comments. Perhaps a future release of SO will support a communication style more familiar and therefore more to one's liking.
Demonstration that Neo4j Is Currently Absent from the Upcoming Release, 1.2.6
The method of search follows the instructions given in (Long & Mayzak, 2011), apparently by Michael Hunger of Neo Technology, Inc., the company that developed Neo4j.
/_/ |_|\____/\____/ 1.2.6.BUILD-SNAPSHOT [rev 32b413d]
Welcome to Spring Roo. For assistance press TAB or type "hint" then hit ENTER.
roo> project --topLevelPackage org.hagiasmon.gswr --projectName gswr
Created ROOT/pom.xml
Created SRC_MAIN_RESOURCES
Created SRC_MAIN_RESOURCES/log4j.properties
Created SPRING_CONFIG_ROOT
Created SPRING_CONFIG_ROOT/applicationContext.xml
roo> pgp trust -keyId 0x29c2d8fd
You must specify option 'keyId' for this command
roo> pgp trust --keyId 0x29c2d8fd
Added trust for key:
>>>> KEY ID: 0x29C2D8FD <<<<
More Info: http://keyserver.ubuntu.com/pks/lookup?fingerprint=on&op=index&search=0x29C2D8FD
Created: 2011-Jan-06 10:48:11 +0000
Fingerprint: 558eb0489fe5500c68fa8a306107f33d29c2d8fd
Algorithm: RSA_GENERAL
User ID: Michael Hunger <Michael.Hunger#jexp.de>
Signed By: Key 0x29C2D8FD (Michael Hunger <Michael.Hunger#jexp.de>)
Subkey ID: 0xDEFB5FB1 [RSA_GENERAL]
roo> addon search graph
0 found, sorted by rank; T = trusted developer; R = Roo 1.2 compatible
ID T R DESCRIPTION -------------------------------------------------------------
--------------------------------------------------------------------------------
[HINT] use 'addon info id --searchResultId ..' to see details about a search result
[HINT] use 'addon install id --searchResultId ..' to install a specific search result, or
[HINT] use 'addon install bundle --bundleSymbolicName TAB' to install a specific add-on version
roo>
P.S. I initiated Facebook correspondence with Josh Long, who along with Michael Hunger, are the two folks driving the Roo - Neo4j interface, as far as I can tell. If he responds, I'll update this comment.
Others have said Apple's bug-tracking system only allows you to see bug reports you yourself have filed. (See Can I browse other people's (Apple) bug reports?.)
But I keep seeing comments in various developer forums (such as xcode-users) along the lines of "I'm fairly sure this is a dup of < rdar://problem/7715072>".
How do they know? Does this mean they must have filed that bug report themselves?
And what use are such comments if no one else can see what that bug report says? (I checked, this one is not on OpenRadar http://openradar.appspot.com/.)
In my opinion apple is not sharing the bugs (a) due to security issues and (b) to get the people report bugs even if they are duplicated. In that way the reported bugs with the most reports will jump up in the priority and will eventually be solved faster.
How do they know? Does this mean they must have filed that bug report themselves?
Yes, I think so. If you file a bug which already has been filed before by others, apple will mark your bug being a duplicate and close it with an advice to follow the original bug id.
If the 1st statement is true, and you can't browse someone else's bugs, there are two possibilities:
apple developers can see them
they filled these bugs
My team works mostly w/ Flex-based applications. That being said, there are nearly no conventions at all (even getting them to refactor is a miracle in itself) and the like.
Coming from a .NET + CruiseControl.NET background, I've been aching to getting everyone to use some decent tracking software (we're using a todo list coded in PHP now) and CI; I figured trac+BuildBot would be a nice option.
How would you convince upper management that this is the way to go, as well as some of the rules mentioned in this post? One of my main issues is that everyone codes without thinking (You'd be amazed at the type of "logic" this spawns...)
Thanks
Is there anything you could do now that wouldn't require permission from anyone else? Could you start by just using trac/buildbot/etc for just your own work, then add in others as they are interested?
In my experience you can get quite far by doing w/out asking.
Tell the management that they'll be better able to keep their eye on progress with such a tool.
Are there specific benefits to the route that you're suggesting that you could show them without them having to buy in?
I had an experience with getting my team to accept a maven + cruisecontrol CI setup. Basically I tried to get them to go along with it for a few days and they kept balking because it was unfamiliar. Then I just did it on my own and had all broken builds emailed to the mailing list. That night the project lead made a check in that broke the build (he just forgot a file) and, of course, everybody was emailed with his screw up.
The next day he came over to me and said, "I get it now."
It required no effort from him to get involved and got to see the benefits for free.