I just started using PhpDocumentor 2. Everything seems to works and all the files are processed but when it reaches this 'Transform analyzed project into artifacts' it gets stucked for hours and never finishes it.
I was wondering if anybody had this issue before, it would be awesome if you can point me out to the right direction to fix it
Thanks!
phpDocumentor has a mailing list at https://groups.google.com/forum/#!forum/phpdocumentor and issues can be logged at https://github.com/phpDocumentor/phpDocumentor2/issues. You may want to bring this problem to either of those places.
Related
As of today, the STS has started displaying strange little question marks throughout its output every time I run a project (any project). I'm not sure why. Does anyone have any clue why and how I can fix it?
Thanks!
Whilst coding a fun new trash can for a Minecraft server network that I develop for, I came across a pretty strange, and therefore infuriating, bug concerning Maven. I've been using it for a year or two now and have only gotten a single build error before, when I first started using it. Suddenly, this problem has shown itself.
The red arrows indicate the lines that are causing the build failure.
This is a screenshot of the Maven logs that are causing the issue.
Well, according to the Bukkit API docs (note that the official docs seem to be down, thus third party), the class InventoryClickEvent has no method getClickedInventory().
This fact definitely explains your compilation error. The error comes from your Java compiler, Maven has nothing to do with it.
Recently we upgraded our SONAR from 3.x to 4.3. There was an error in our Jenkins build (squidindex was null) which triggered the upgrade of the java from 2.2 to 2.2.1 along with the plugins for JaCoCo, Findbugs, Squid for Java, and Surefire.
Once SonarQube was up and running again, we discovered that although no code changes had taken place, we now had over 200 critical issues as well as a high number of major ones. Upon research, it became apparent that all of our previously marked false-positives had now reappeared.
Obviously we want to find a way to fix this besides walking through over a thousand various issues and re-marking them.
We have done some research in the database and have discovered a puzzle that we think might be related. In the Issues table, we have found that there are duplicate entries where the first difference is that one entry has the simple file name and the other entry has the file name along with the extension.
(I had an image of a few lines from the database to put here, but as I do not yet have a 10 reputation, I cannot. Please contact me and I will be glad to email the image. Sigh.)
As you can see, Lines 2 & 3 both refer to line 134 in the file PersistentObjectCollection.java. Line 2 shows that the issue is FIXED and CLOSED while Line 3 shows the same issue as Open and null resolution.
We are wondering if we could safely use SQL to find matched pairs like this and copy the necessary columns across to register the issues properly?
Can you please take a look and tell me if this is something feasible to do, or if there is a better alternative to try.
Question already asked on the SonarQube mailing list : http://sonar.markmail.org/thread/kpx3une24lwoilli
Please don't duplicate question !!
I make extensive use of the CoffeeScript Maven Plugin which used to live here: https://github.com/iron9light/coffeescript-maven-plugin. (if that link is no longer 404'ing then it must have come back; consider the question answered!)
It seems to have disappeared which is odd as it's always been there in the past. I have local copy so it's not a mega problem but I would be sad if the chap who maintains it has deleted it / stopped maintaining it!
Does anyone know what happened to it?
Huh, it's back now! I guess it took a little holiday. https://github.com/iron9light/coffeescript-maven-plugin
I've just followed the steps on the cocos2d site to install the latest xcode 4 project templates, however every time I try and create a Chipmunk/Box2d project it fails to build, stating there are ~26 issues.
I've read up on this a little and found that Xcode 4 change the way templates are handled which is causing the issue, but I haven't found what I need to do to fix this.
Any help would be appreciated!
Andy
Hey, I had the same issue as you but after a lot of searching I found a solution.
For some reason if your project name has a space in it then Xcode 4 doesn't link the Box2D framework in properly, thus giving you the 26 errors.
I recreated my project with a name without spaces and it compiled perfectly.