Viciado em Internet Profissional • Entusiasta de Jogos • Criador de Tecnologia
Viciado em Internet Profissional • Entusiasta de Jogos • Criador de Tecnologia

Compartilhando código entre projetos Java do Google App Engine no Eclipse

Compartilhando código entre vários projetos Java do Google App Engine no Eclipse!
Esta página foi traduzida do inglês pelos meus estagiários de IA altamente motivados para sua conveniência. Eles ainda estão aprendendo, então alguns erros podem ter passado despercebidos. Para informações mais precisas, consulte a versão em inglês.
Lar Blog Compartilhando código entre projetos Java do Google App Engine no Eclipse

Observe que este post foi publicado em janeiro de 2011, portanto, dependendo de quando você o ler, algumas partes podem estar desatualizadas. Infelizmente, nem sempre consigo manter estes posts totalmente atualizados para garantir que as informações permaneçam precisas.

    When working with multiple Google App Engine projects in an Eclipse workspace, you might want extract duplicated code (such as framework and utility code) from those projects into a new shared project.
    However sharing code between projects in Eclipse is already very common thing to do by adding required projects on your build path:
    Build path
    However this won't work when dealing with Google App Engine projects, since you need to gather all the source code into the bin folder when doing a deploy.
    As an example, let's say I have three different projects: two regular sites and one utility and framework project, which contains code that I want to share to for my other sites.
    Shared
    Inside the framework project I have a utility classed call StringUtil which has the method isEmpty.
    Shared
    In my project site1, I am planning to use my utility method, but Eclipse cannot find my StringUtil class.
    Shared
    If I add the "framework" the project as a required project:
    Shared
    Eclipse will find the correct class and method, but after I have deployed and visit the site I would get:
    Error: Server Error The server encountered an error and could not complete your request. If the problem persists, please report your problem and mention this error message and the query that caused it.
    And looking in the logs, I see the site crashed due to not finding my StringUtil class.
    Overview
    This meant that even though Eclipse finds my StringUtil class, the code doesn't actually get deployed up to the Google App Engine. This is because when I added framework as a required project, I told Eclipse to start looking in framework's bin folder as well for classes - but when I am deploying to Google App Engine, I am actually deploying one site, meaning site1 and it's bin folder.
    Image 7
    In the Link Source dialogue you can either point directly to a source folder, but since I am planing to have multiple projects linking in framework, I have have created a variable. Meaning, if I never need to change the path, I only need to change in one place instead of in all my projects.
    Image 8
    Now both Eclipse and the Google App Engine finds my shared StringUtil class!

    Escrito por Special Agent Squeaky. Publicado pela primeira vez em 22/01/2011. Última atualização em 22/01/2011.

    📺 Assista ao vídeo mais recente do Squeaky!

    Como adicionar legendas simples em tempo real à sua transmissão ao vivo