Method XXX was discovered in the .class file but cannot be resolved in the class

这个经过测试,发现是 git pull整合代码 解决冲突后,没有重新发布项目导致的。

提示:以后记得重新发布再测试功能。

  • 1
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
The first edition of Node.js in Action was about web development with a particular focus on the Connect and Express web frameworks. Node.js in Action, Second Edition has been updated to suit the changing requirements of Node development. You’ll learn about front-end build systems, popular Node web frameworks, and how to build a web application with Express from scratch. You’ll also learn how to create automated tests and deploy Node web applications., Node is being increasingly used for command-line developer tools and desktop applications with Electron, so you’ll find chapters dedicated to both of these areas., This book assumes you’re familiar with basic programming concepts. The first chapter provides an overview of JavaScript and ES2015 for those of you who haven’t yet discovered the joys of modern JavaScript., Roadmap, This book is organized into three parts., Part 1 provides an introduction to Node.js, teaching the fundamental techniques needed to develop with it. Chapter 1 explains the characteristics of JavaScript and Node and steps through example code. Chapter 2 guides you through fundamental Node.js programming concepts. Chapter 3 is a full tutorial on how to build a web application from scratch., Part 2, the largest section of the book, focuses on web application development. Chapter 4 dispels some of the mystery around front-end build systems: if you’ve ever had to use webpack or Gulp in a project but didn’t really understand it, this is the chapter for you. Chapter 5 reviews some of the most popular server-side frameworks available for Node, and chapter 6 goes into Connect and Express in more depth. Chapter 7 is dedicated to templating languages, which can improve your productivity when writing server-side code. Most web applications need a database, so chapter 8 covers the many types of databases that you can use with Node, from relational to NoSQL. Chapters 9 and 10 deal with testing and deployment, and this includes cloud deployment., Part 3 goes beyond web application development. Chapter 11 is about building command-line applications with Node so you can create developer-friendly text interfaces. If you’re excited about the prospect of building desktop apps such as Atom with Node, then take a look at chapter 12, which is all about Electron.
The first edition of Node.js in Action was about web development with a particular focus on the Connect and Express web frameworks. Node.js in Action, Second Edition has been updated to suit the changing requirements of Node development. You’ll learn about front-end build systems, popular Node web frameworks, and how to build a web application with Express from scratch. You’ll also learn how to create automated tests and deploy Node web applications. Node is being increasingly used for command-line developer tools and desktop applications with Electron, so you’ll find chapters dedicated to both of these areas. This book assumes you’re familiar with basic programming concepts. The first chapter provides an overview of JavaScript and ES2015 for those of you who haven’t yet discovered the joys of modern JavaScript. Roadmap This book is organized into three parts. Part 1 provides an introduction to Node.js, teaching the fundamental techniques needed to develop with it. Chapter 1 explains the characteristics of JavaScript and Node and steps through example code. Chapter 2 guides you through fundamental Node.js programming concepts. Chapter 3 is a full tutorial on how to build a web application from scratch. Part 2, the largest section of the book, focuses on web application development. Chapter 4 dispels some of the mystery around front-end build systems: if you’ve ever had to use webpack or Gulp in a project but didn’t really understand it, this is the chapter for you. Chapter 5 reviews some of the most popular server-side frameworks available for Node, and chapter 6 goes into Connect and Express in more depth. Chapter 7 is dedicated to templating languages, which can improve your productivity when writing server-side code. Most web applications need a database, so chapter 8 covers the many types of databases that you can use with Node, from relational to NoSQL. Chapters 9 and 10 deal with testing and deployment, and this includes cloud deployment. Part 3 goes be
In fall 2010 Michael Stephens from Manning contacted me about writing a Scala Book. I was working for a small virtualization/security startup where I had been learning Scala and applying it to our codebase. During that first conversation Michael and I dis- cussed the Scala ecosystem and what kind of a book would best serve the community. I believed Scala needed a “practical Scala” book to help guide those new to the lan- guage. Scala is a beautiful language, but it brings many new concepts to the table. I had watched as the community slowly discovered best practices and a code style that was wholly “Scala.” But I wasn’t sure whether I was the right person to write such a book. When it came down to it, I was passionate about the topic, had enough free time to do the research, and had the support of the magnates of the community to help achieve what you are reading today—so I decided to go ahead. I’ve learned a lot during the writing process. One reason it took so long was the evolving nature of Scala and the emergence of new best practices. Another reason was that I realized my own knowledge was woefully inadequate in some areas of Scala. To all aspiring authors out there, I will tell you that writing a book makes you an expert. You may think you are one before you start, but true expertise grows from the blood, sweat, and tears of teaching, of trying to convey complex concepts to your readers with clarity. Working on this book was a journey that I never could have completed without a very supportive and loving wife, a great publisher, and an amazing community of Scala developers and readers willing to read my manuscript in various stages, point out my typos and misspellings, and offer advice on how to make Scala in Depth a much better book than I could have achieved alone.
The wxPython part of the story actually begins in 1995, with Harri Pasanen and Robin Dunn. Robin, who is one of the co-authors of the book, wrote the following about the history of wxPython, and we decided that it was a story better told in his own voice than paraphrased: In 1995 I was working on a project that needed a GUI to be deployed on HP-UX systems, but my boss also wanted to show something at a trade show on his Windows 3.1 laptop in a few weeks’ time. So I started searching for a cross platform C++ GUI toolkit to do a prototype with. In those days it wasn’t easy without Google, but I found that there were several commercial alternatives available (none of which is still available today) and lots of tool- kits with freely available source. While evaluating each of the free toolkits for my immediate needs and deciding which of the commercial offerings would be best for our long-term needs, I ran into the term “Python bindings” on the wxWidgets website (in this case “binding” refers to the connection between the Python language and the wxWidgets toolkit). Full of curiosity at how one would “bind” a soft- ware toolkit to a reptile (I had never heard of the Python language up to this point), I clicked on the link, and the next link, and the next, until I finally ended up at the Python 1.2 Tutorial document. Three hours later I was con- verted from being the local C++ guru to a Python evangelist bugging all xx PREFACE the developers in the immediate vicinity and showing them the cool new thing I had discovered. Instead of working on my prototype, I started working with Harri Pasanen in Finland to advance the Python bindings for wxWidgets, otherwise known as wxPython 0.2, with some help from Edward Zimmerman. The mailing list announcement of that release is archived here: (http://www.google.com/ [email protected]&oe=UTF-8). We got it to be functional enough that I could build the prototype for my boss using Python, but wxPython was a nightmare to maintain and to enhance because everything (C++ extension module code, Python proxy modules, build system, etc.) was done by hand, and little changes or enhancements to wxWidgets would often require changes to several places in wxPython code to add the support for the enhancement or fix to wxPython. When it reached many tens of thousands of lines of code it became very awkward and fragile to continue working in that manner. Add to that the fact that there was no central source code repository (this was also before SourceForge’s time) so we were emailing code changes to each other—you can get an inkling of the difficulties involved. About that time, I had to start doing “real” work again as my main project was building up from a gleam in the eye to a full-force development project with several developers under my control with design meetings and deadlines, and I found myself fully back in the C++ world again, although I was able to use Python for some of the build and test scripts for the project. Harri wasn’t able to spend any time on it either, so wxPython development slowed to less than a crawl and eventually stopped. In 1997 I discovered SWIG (Simple Wrapper and Interface Generator), and realized that it could help with all the maintenance issues that had pained us in the wxPython project. In three or four weeks of spare time using SWIG, I almost completely reimplemented everything in wxPython that had taken several weeks of full-time work on my part and several months of part-time work for Harri doing it by hand. After getting sidetracked on another project for a while, I discovered that wxWidgets 2.0 was in active develop- ment, but had a whole new architecture, so I had to do it all again. But this time the new architecture simplified things enough that it took only about a week’s worth of spare time! So in the summer of 1998 the first “modern ver- sion” of wxPython was released and has been in active development ever PREFACE xxi since. The first announcement is archived here: (http://groups.yahoo.com/ group/python-announce-list/message/95). The rest is, as they say, history. It’s important to note that SWIG is allowing me to easily create and maintain literally hundreds of thousands of lines of code, so much of the credit for the vastness of wxPython’s feature set deserves to go to David Beazley and the other developers contributing to that project. With this book, we hope to share with you our excitement about wxPython, a toolkit that is truly unique in the ease that it brings to GUI application develop- ment. We wrote it with the goal of creating a useful resource for both the novice and the pro.

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值