Page 2 of 2 FirstFirst 12
Results 11 to 20 of 20

Thread: Error importing grails 1.3.7 project

  1. #11
    Join Date
    Aug 2008
    Location
    Vancouver, BC
    Posts
    768

    Default

    It is possible to upgrade, but not simple or straight forward. I would recommend asking the best way to do this on the grails forum. There are lots of little things that need to change.

    Here's the place to put your question:
    http://forum.springsource.org/forumd....php?76-Grails
    Andrew Eisenberg, Ph.D.
    SpringSource, a division of VMware
    SpringSource Tools Team
    More about AJDT, Groovy-Eclipse, and Grails tooling

  2. #12
    Join Date
    Sep 2012
    Location
    India
    Posts
    10

    Exclamation

    Quote Originally Posted by nithya.krishnan View Post
    Is it possible to convert 1.3.7 grails project 2.0.4,If i am updating that i am getting errors.
    Thanks a lot for your reply,currently i am not upgrading the existing projects

    If i import project in STS i am able to see the output window,

    but i am unsure why i am getting these build errors

    Message:
    JavaBuilder handling ImageBuilderInternalException while building: branchV2
    Exception Stack Trace:org.eclipse.core.internal.resources.Resource Exception: A resource exists with a different case: '/branchV2/target-eclipse/classes/branchV2'.
    at org.eclipse.core.internal.resources.Resource.check DoesNotExist(Resource.java:308)
    at org.eclipse.core.internal.resources.Resource.check DoesNotExist(Resource.java:286)
    at org.eclipse.core.internal.resources.Folder.assertC reateRequirements(Folder.java:30)
    at org.eclipse.core.internal.resources.Folder.create( Folder.java:95)
    at org.eclipse.jdt.internal.core.builder.AbstractImag eBuilder.createFolder(AbstractImageBuilder.java:52 3)
    at org.eclipse.jdt.internal.core.builder.AbstractImag eBuilder$1.visit(AbstractImageBuilder.java:298)
    at org.eclipse.core.internal.resources.Resource$1.vis itElement(Resource.java:65)
    at org.eclipse.core.internal.watson.ElementTreeIterat or.doIteration(ElementTreeIterator.java:82)
    at org.eclipse.core.internal.watson.ElementTreeIterat or.doIteration(ElementTreeIterator.java:86)
    at org.eclipse.core.internal.watson.ElementTreeIterat or.iterate(ElementTreeIterator.java:127)
    at org.eclipse.core.internal.resources.Resource.accep t(Resource.java:75)
    at org.eclipse.jdt.internal.core.builder.AbstractImag eBuilder.addAllSourceFiles(AbstractImageBuilder.ja va:255)
    at org.eclipse.jdt.internal.core.builder.BatchImageBu ilder.build(BatchImageBuilder.java:52)
    at org.eclipse.jdt.internal.core.builder.JavaBuilder. buildAll(JavaBuilder.java:254)
    at org.eclipse.jdt.internal.core.builder.JavaBuilder. build(JavaBuilder.java:178)
    at org.eclipse.core.internal.events.BuildManager$2.ru n(BuildManager.java:728)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner .java:42)
    at org.eclipse.core.internal.events.BuildManager.basi cBuild(BuildManager.java:199)
    at org.eclipse.core.internal.events.BuildManager.basi cBuild(BuildManager.java:239)
    at org.eclipse.core.internal.events.BuildManager$1.ru n(BuildManager.java:292)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner .java:42)
    at org.eclipse.core.internal.events.BuildManager.basi cBuild(BuildManager.java:295)
    at org.eclipse.core.internal.events.BuildManager.basi cBuild(BuildManager.java:256)
    at org.eclipse.core.internal.events.BuildManager.buil d(BuildManager.java:394)
    at org.eclipse.core.internal.resources.Project$1.run( Project.java:618)
    at org.eclipse.core.internal.resources.Workspace.run( Workspace.java:2344)
    at org.eclipse.core.internal.resources.Project.intern alBuild(Project.java:597)
    at org.eclipse.core.internal.resources.Project.build( Project.java:114)
    at org.eclipse.debug.core.model.LaunchConfigurationDe legate$1.run(LaunchConfigurationDelegate.java:423)
    at org.eclipse.core.internal.resources.Workspace.run( Workspace.java:2344)
    at org.eclipse.core.internal.resources.Workspace.run( Workspace.java:2326)
    at org.eclipse.debug.core.model.LaunchConfigurationDe legate.buildProjects(LaunchConfigurationDelegate.j ava:430)
    at org.eclipse.debug.core.model.LaunchConfigurationDe legate.buildForLaunch(LaunchConfigurationDelegate. java:126)
    at org.eclipse.debug.internal.core.LaunchConfiguratio n.launch(LaunchConfiguration.java:822)
    at org.eclipse.debug.internal.core.LaunchConfiguratio n.launch(LaunchConfiguration.java:703)
    at org.eclipse.debug.internal.ui.DebugUIPlugin.buildA ndLaunch(DebugUIPlugin.java:937)
    at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run( DebugUIPlugin.java:1141)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.j ava:54)

    .version=1.7.0_07
    java.vendor=Oracle Corporation
    BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
    Framework arguments: -product com.springsource.sts.ide
    Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.springsource.sts.ide

    is it os byte issue could you please explain where i went wrong ?

    Thanks & Regards,
    Nithya.

  3. #13
    Join Date
    Aug 2008
    Location
    Vancouver, BC
    Posts
    768

    Default

    Looks like you are trying to build a project where there are two packages coming from different source folders that have the same names, but with different capitalization. In windows, this means that the packages are the same, but in Eclipse, this is confusing and causes an error.

    The package/folder is called this: '/branchV2/target-eclipse/classes/branchV2'. Do you know of any other folders out there with the same name, but different capitalization?
    Andrew Eisenberg, Ph.D.
    SpringSource, a division of VMware
    SpringSource Tools Team
    More about AJDT, Groovy-Eclipse, and Grails tooling

  4. #14
    Join Date
    Sep 2012
    Location
    India
    Posts
    10

    Default

    Quote Originally Posted by Andrew Eisenberg View Post
    Looks like you are trying to build a project where there are two packages coming from different source folders that have the same names, but with different capitalization. In windows, this means that the packages are the same, but in Eclipse, this is confusing and causes an error.

    The package/folder is called this: '/branchV2/target-eclipse/classes/branchV2'. Do you know of any other folders out there with the same name, but different capitalization?
    Thank you so much,Andrew Eisenberg for your replies,Currently i can run my application without any compilation errors

    I would like to get my application in cloud can u give me some useful links illustrating this.especially db connectivity,

    Thanks & Regards,
    Nithya.

  5. #15
    Join Date
    Sep 2012
    Location
    India
    Posts
    10

    Default

    Thank you so much,Andrew Eisenberg for your replies,Currently i can run my application without any compilation errors

    grails run-app -https from command line

    http://localhost:8080/home and http://localhost:8443/home

    when i create a tc server instance i am not able to view this could you please help

    whether i have to build my app using -https how i can create such a instance.I am not sure on this.

    Thanks & Regards,
    Nithya.

  6. #16
    Join Date
    Aug 2008
    Location
    Vancouver, BC
    Posts
    768

    Default

    Quote Originally Posted by nithya.krishnan View Post
    I would like to get my application in cloud can u give me some useful links illustrating this.especially db connectivity,
    Take a look at cloud foundry and its grails support. See
    http://grails.org/plugin/cloud-foundry
    and
    http://docs.cloudfoundry.com/framewo...ng/grails.html
    Andrew Eisenberg, Ph.D.
    SpringSource, a division of VMware
    SpringSource Tools Team
    More about AJDT, Groovy-Eclipse, and Grails tooling

  7. #17
    Join Date
    Aug 2008
    Location
    Vancouver, BC
    Posts
    768

    Default

    Quote Originally Posted by nithya.krishnan View Post
    Thank you so much,Andrew Eisenberg for your replies,Currently i can run my application without any compilation errors

    grails run-app -https from command line

    http://localhost:8080/home and http://localhost:8443/home

    when i create a tc server instance i am not able to view this could you please help

    whether i have to build my app using -https how i can create such a instance.I am not sure on this.

    Thanks & Regards,
    Nithya.
    This question is outside my area of expertise. Please ask the question on the grails forum.
    Andrew Eisenberg, Ph.D.
    SpringSource, a division of VMware
    SpringSource Tools Team
    More about AJDT, Groovy-Eclipse, and Grails tooling

  8. #18
    Join Date
    May 2010
    Posts
    412

    Default

    Updating projects is possible. There is a command 'grails upgrade'. However, the command is not 'magic' and upgraded projects more often than not do need you to manually fix things before they will actually work.

    If the project is known to be a 1.3.7 project I think you should start by importing it as such. When you are confident is working as a 1.3.7 project, you can try upgrading to 2.0.4 after that. Trying to do too many things at once, it is much harder to tell what is causing your problems. Is it some problem importing, is it the wrong grails version, a problem with project, a problem in incorrect migration to 2.0.4?

    How can we tell?

    Take it one step at a time.
    Kris De Volder -- SpringSource

  9. #19
    Join Date
    Sep 2012
    Location
    India
    Posts
    10

    Default

    Quote Originally Posted by Kris De Volder View Post
    Updating projects is possible. There is a command 'grails upgrade'. However, the command is not 'magic' and upgraded projects more often than not do need you to manually fix things before they will actually work.

    If the project is known to be a 1.3.7 project I think you should start by importing it as such. When you are confident is working as a 1.3.7 project, you can try upgrading to 2.0.4 after that. Trying to do too many things at once, it is much harder to tell what is causing your problems. Is it some problem importing, is it the wrong grails version, a problem with project, a problem in incorrect migration to 2.0.4?

    How can we tell?

    Take it one step at a time.
    Hi Kris De Volder,

    Thanks for the reply,

    My error in project solved when i changed jdk to 6,Currently my project is grails 1.3.7 I have not upgraded the project When i am creating instance of TC server it is not running.

    Thanks & Regards,
    Nithya.

  10. #20
    Join Date
    May 2010
    Posts
    412

    Default

    > My error in project solved when i changed jdk to 6,Currently my project is grails 1.3.7 I have not upgraded the project When i am > creating instance of TC server it is not running.

    Without some more specific information, nobody is going to be able to help you. Do you have error messages? How did you create the server instance? How did you deploy the app?

    Anyway... following 'one step at a time' philosophy, maybe first try running your app with Grails 'run-app' before trying to deploy it. You get a faster turnaround with run-app and can confirm the app is working or not before trying to deploy it to an actual server.

    To run with run app, Right click on the project and select "Run As >> Grails Command (run-app)"
    Kris De Volder -- SpringSource

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •