facebook

Build error trying to set up my project in MEB 10

  1. MyEclipse IDE
  2.  > 
  3. WebSphere Development
Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #339569 Reply

    jack long
    Member

    I’m trying to set up my project in MEB 10 following our department’s setup instructions and I receive build errors that no one else gets. We’ve been trying to figure this out for over a week with no solution. My build path libraries, variables and sort order are the same as theirs. Does anyone have any ideas? Here is info from the problem log. Thanks!!!

    !ENTRY org.eclipse.wst.common.modulecore 4 2 2013-05-31 10:41:52.613
    !MESSAGE Problems occurred when invoking code from plug-in: “org.eclipse.wst.common.modulecore”.
    !STACK 0
    java.lang.NullPointerException
    at org.maven.ide.eclipse.wtp.overlay.modulecore.OverlayReferenceResolver.canResolve(OverlayReferenceResolver.java:56)
    at org.eclipse.wst.common.componentcore.resolvers.ReferenceResolverUtil.getResolver(ReferenceResolverUtil.java:43)
    at org.eclipse.wst.common.componentcore.internal.StructureEdit.createVirtualReference(StructureEdit.java:295)
    at org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent.getRawReferences(VirtualComponent.java:404)
    at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl$GraphUpdateJob$1.run(DependencyGraphImpl.java:503)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl$GraphUpdateJob.run(DependencyGraphImpl.java:462)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

    !ENTRY org.eclipse.wst.common.modulecore 4 0 2013-05-31 10:41:52.613
    !MESSAGE
    !STACK 0
    java.lang.NullPointerException
    at org.maven.ide.eclipse.wtp.overlay.modulecore.OverlayReferenceResolver.canResolve(OverlayReferenceResolver.java:56)
    at org.eclipse.wst.common.componentcore.resolvers.ReferenceResolverUtil.getResolver(ReferenceResolverUtil.java:43)
    at org.eclipse.wst.common.componentcore.internal.StructureEdit.createVirtualReference(StructureEdit.java:295)
    at org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent.getRawReferences(VirtualComponent.java:404)
    at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl$GraphUpdateJob$1.run(DependencyGraphImpl.java:503)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl$GraphUpdateJob.run(DependencyGraphImpl.java:462)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

    !ENTRY com.genuitec.eclipse.core 1 0 2013-05-31 10:41:53.143
    !MESSAGE GSDC: MyEclipse subscription has already been activated.

    !ENTRY org.eclipse.core.resources 4 2 2013-05-31 11:13:51.574
    !MESSAGE Problems occurred when invoking code from plug-in: “org.eclipse.core.resources”.
    !STACK 0
    java.lang.NullPointerException
    at org.maven.ide.eclipse.wtp.overlay.modulecore.OverlayReferenceResolver.canResolve(OverlayReferenceResolver.java:56)
    at org.eclipse.wst.common.componentcore.resolvers.ReferenceResolverUtil.getResolver(ReferenceResolverUtil.java:43)
    at org.eclipse.wst.common.componentcore.internal.StructureEdit.createVirtualReference(StructureEdit.java:295)
    at org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent.getReferences(VirtualComponent.java:437)
    at org.eclipse.jst.j2ee.componentcore.util.EARVirtualComponent.getHardReferences(EARVirtualComponent.java:89)
    at org.eclipse.jst.j2ee.componentcore.util.EARVirtualComponent.getReferences(EARVirtualComponent.java:192)
    at org.eclipse.jst.j2ee.project.facet.EarFacetValidator.validate(EarFacetValidator.java:58)
    at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectValidationBuilder.build(FacetedProjectValidationBuilder.java:132)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

    !ENTRY org.eclipse.jst.j2ee 4 0 2013-05-31 11:13:51.589
    !MESSAGE
    !STACK 0
    java.lang.NullPointerException
    at org.maven.ide.eclipse.wtp.overlay.modulecore.OverlayReferenceResolver.canResolve(OverlayReferenceResolver.java:56)
    at org.eclipse.wst.common.componentcore.resolvers.ReferenceResolverUtil.getResolver(ReferenceResolverUtil.java:43)
    at org.eclipse.wst.common.componentcore.internal.StructureEdit.createVirtualReference(StructureEdit.java:295)
    at org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent.getReferences(VirtualComponent.java:437)
    at org.eclipse.jst.j2ee.componentcore.util.EARVirtualComponent.getHardReferences(EARVirtualComponent.java:89)
    at org.eclipse.jst.j2ee.componentcore.util.EARVirtualComponent.getReferences(EARVirtualComponent.java:192)
    at org.eclipse.jst.j2ee.internal.deployables.J2EEDeployableFactory.LEGACY_createBinaryModules(J2EEDeployableFactory.java:156)
    at org.eclipse.jst.j2ee.internal.deployables.J2EEDeployableFactory.createModuleDelegates(J2EEDeployableFactory.java:133)
    at org.eclipse.jst.j2ee.internal.deployables.J2EEDeployableFactory.createModules(J2EEDeployableFactory.java:89)
    at org.eclipse.wst.server.core.util.ProjectModuleFactoryDelegate.cacheModules(ProjectModuleFactoryDelegate.java:60)
    at org.eclipse.wst.server.core.util.ProjectModuleFactoryDelegate.getModules(ProjectModuleFactoryDelegate.java:263)
    at org.eclipse.wst.server.core.internal.ModuleFactory.getModules(ModuleFactory.java:140)
    at org.eclipse.wst.server.core.ServerUtil.getModules(ServerUtil.java:98)
    at org.eclipse.wst.server.core.internal.ResourceManager.publishHandleProjectChange(ResourceManager.java:1079)
    at org.eclipse.wst.server.core.internal.ResourceManager$ServerResourceChangeListener$1.visit(ResourceManager.java:125)
    at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
    at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
    at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
    at org.eclipse.wst.server.core.internal.ResourceManager$ServerResourceChangeListener.resourceChanged(ResourceManager.java:119)
    at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
    at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
    at org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:381)
    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:146)
    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

    !ENTRY org.eclipse.core.resources 4 75 2013-05-31 11:13:51.605
    !MESSAGE Errors occurred during the build.
    !SUBENTRY 1 org.eclipse.wst.common.project.facet.core 4 75 2013-05-31 11:13:51.605
    !MESSAGE Errors running builder ‘Faceted Project Validation Builder’ on project ‘PHSRPT’.
    !STACK 0
    java.lang.NullPointerException
    at org.maven.ide.eclipse.wtp.overlay.modulecore.OverlayReferenceResolver.canResolve(OverlayReferenceResolver.java:56)
    at org.eclipse.wst.common.componentcore.resolvers.ReferenceResolverUtil.getResolver(ReferenceResolverUtil.java:43)
    at org.eclipse.wst.common.componentcore.internal.StructureEdit.createVirtualReference(StructureEdit.java:295)
    at org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent.getReferences(VirtualComponent.java:437)
    at org.eclipse.jst.j2ee.componentcore.util.EARVirtualComponent.getHardReferences(EARVirtualComponent.java:89)
    at org.eclipse.jst.j2ee.componentcore.util.EARVirtualComponent.getReferences(EARVirtualComponent.java:192)
    at org.eclipse.jst.j2ee.project.facet.EarFacetValidator.validate(EarFacetValidator.java:58)
    at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectValidationBuilder.build(FacetedProjectValidationBuilder.java:132)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

    #339606 Reply

    support-swapna
    Moderator

    LongJack,

    Sorry that you are seeing this issue.

    Can you please answer some more questions for us ?

    1. Are you trying to set up a Maven project ? If yes, then did you import it using the Import > Existing Maven projects or ‘Checkout Maven Projects from SCM”?

    2.Can you please use “Update Project Configuration” after importing the project and check if it fixes the issue? Right click on the project > Maven4MyEclipse > Update Project Configuration.

    3. If you are still seeing issues, please share the MyEclipse Build ID from Help > About MyEclipse Edition > Build ID.

    4. Also we need all .* files (.project, .classpath, .settings folder, etc.) and pom.xmls (you can remove dependencies lists) and all files should be aligned in folders as they are in the repository to investigate further.

    #339623 Reply

    jack long
    Member

    Thanks for taking a look at this.
    1) No this is not a Maven project
    2) I did not import this project. It is a new set up
    3) Build id: 10.0-Blue-20111028
    4)

    Attachments:
    You must be logged in to view attached files.
    #339625 Reply

    jack long
    Member

    additional files.

    Attachments:
    You must be logged in to view attached files.
    #339626 Reply

    jack long
    Member

    .settings folder part 1

    Attachments:
    You must be logged in to view attached files.
    #339627 Reply

    jack long
    Member

    .settings folder part 2

    Attachments:
    You must be logged in to view attached files.
    #339661 Reply

    support-tony
    Keymaster

    LongJack,

    Thanks for the attached files; I appreciate the time taken to do this. However, your project is quite confusing. There are no myeclipse (genuitec) project natures in the .project file and no myeclipse builders configured. There are, however, several IBM builders and settings files which might indicate that this was originally a WebSphere Application Developer (WSAD) project, though you stated that the project was set up from scratch. Also, the error appears to be in a Maven related plug-in (hence our question about Maven) but the project doesn’t have any Maven builders.

    Could you provide the steps (at least roughly) you followed for setting up the project?

    If there are other developers who are using this project with MyEclipse Blue 10, is it possible for you to import the project from one of their systems to see if you can get it working that way?

    #339666 Reply

    jack long
    Member

    Thanks for the info Tony. I had this project set up on my old laptop running MEB 8.6 and XP. My company replaced my laptop with a new one running MEB 10 and Windows 7 so I needed to set up the project again. Yes, the project was originally developed on WSAD. I am attaching the document that I used to set up the project.

    Thanks again for you help!

    Attachments:
    You must be logged in to view attached files.
    #339676 Reply

    jack long
    Member

    btw. i did try importing the project using an archive zip file from my old MEB 8.6 project, but i still get the same error. I did the import following these instructions:

    To import an entire Eclipse project from an archive file, follow these steps.

    1.Go to File -> Import. The following dialog will appear.
    2.Select Existing Projects into Workspace.
    NOTE: It may seem counter-intuitive to not be selecting Archive File at this step. The Archive File option is used for importing Eclipse resources into an existing Eclipse project. Since you are importing an entire project, you must select Existing projects.
    3.Click the radio button next to Select archive file and click the Browse button on the following dialog.
    4.Find the archive file on your hard disk. Click Open to select it.
    5.If you have selected an archive file containing an entire Eclipse project, the project name will appear in the box below, already checked. Click Finish to perform the import. The example presented in this Figure is for the CoffeeMaker_WebDB project, but your project may be iTrust, some other version of CoffeeMaker, or any project.

    #339695 Reply

    support-tony
    Keymaster

    LongJack,

    Well, this is a tricky one. It’s not clear that your project was enhanced from RAD/WSAD to work with MyEclipse Blue, as there are still many WSAD builders defined.

    Is it possible for you to check that the builder list and the project facets are the same as for colleagues who are working with the project using MyEclipse Blue 10? You can see the builder list by right clicking on the project, clicking Properties, then going to the Builders page. Facets can be viewed from the same dialog by going to the MyEclipse Project Facets page.

    I’m not sure why the Faceted Project Validation Builder is throwing that exception but you could try de-selecting that builder (you will get a warning but just click OK) to see if that allows the build to go through.

    When you imported the MEB 8.6 project, were you prompted to upgrade it for MyEclipse 9 and above?

    As an alternative to importing the project, you could try using the old workspace in its entirety or using the workspace of a colleague who is not having the problem, if that is possible.

    Please let me know what you find.

    #339724 Reply

    jack long
    Member

    Hi Tony.

    I checked my builders and project facets against a coworkers. Builders match except that I don’t have DeploymentBuilder on any of the projects and she has them on all of them.

    The Project Facets that have their checkboxes selected match between hers and mine. She does have a bunch of unselected ones on her main project that are not listed on mine.

    I unselect the Faceted Project Validation Builder and it builds without getting the error. I still think that there is something wrong because it doesn’t deploy properly so I can’t run on my local server.

    I did not get any prompt to upgrade my project when i imported the 8.6 version into 10.

    I will try copying the entire workspace folder from the old laptop to the new one and see what happens tomorrow.
    Thanks again for your help!

    #339735 Reply

    support-tony
    Keymaster

    LongJack,

    It’s odd that the 8.6 project didn’t require upgrading for release 10. However, the project you have now appears to have been created as a new project, from looking at the document you attached, though this, again, causes confusion since that would imply that only currently available builders would be defined for the project. Maybe the steps, using the CA CSM perspective, don’t use the normal eclipse project creation facilities, doing all the work itself.

    If you click MyEclipse, in the menu bar, then “Upgrade Projects for MyEclipse 9 & above”, does the dialog show any projects to upgrade?

    It’ll be interesting to know how it goes with using the old workspace. If you still have problems, a sanity check would be to get a colleague to go through the workspace and project creation steps on their machine to see if they get the same problem. If not, then there must be some difference between your set up and theirs. A reinstall of MyEclipse Blue would be worth a shot, in that case.

Viewing 12 posts - 1 through 12 (of 12 total)
Reply To: Build error trying to set up my project in MEB 10

You must be logged in to post in the forum log in