[jtflores]

I am 4.0 Milestone 3, I added tapestry capabilities to my project. However I figured out that I do not need this. I have deleted all the references I can think of to tapestry in my project, but I still see a build path error “No Tapestry build, the Tapestry jars are missing from the build path”. Is there something that I am missing to remove this.

[Riyad Kalla]

double check your .project file for the builders and .classpath for the library references.

[jtflores]

i double checked and I even tried removing all validation markers. The build path error still shows. How can fully clean out the references to Tapestry in my project?

[Riyad Kalla]

Those two files are it. Try closing your project and restarting MyEclipse. Also if you open up your build path and look at the libraries tab, do you see anything with an “x” or “!” next to it?

[jtflores]

The only way that I can remove from the Problems view is unchecking the Tapestry Build Problem, Tapestry Fatlal Problem, Tapestry Parser Problem from filters. It is still trying to build the project with tapestry settings see the following .project file
settings

<?xml version=”1.0″ encoding=”UTF-8″?>
<projectDescription>
<name>MyProject</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>com.genuitec.eclipse.j2eedt.core.WebClasspathBuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>com.genuitec.eclipse.j2eedt.core.J2EEProjectValidator</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>com.genuitec.eclipse.j2eedt.core.DeploymentDescriptorValidator</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>com.ibm.etools.validation.validationbuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>com.ibm.sse.model.structuredbuilder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>com.genuitec.eclipse.j2eedt.core.webnature</nature>
<nature>org.eclipse.jdt.core.javanature</nature>
</natures>
</projectDescription>

[/list]

[Riyad Kalla]

Here’s the fast workaround: Create a new web project, and drag and drop all artifacts from your broken project to the new one (use the package view so you don’t copy across the (dot) files which may carry the problem over to the new project.

[glongman]

The quick answer now is to put the tapestry stuff back into the .project file. Work the project files until all of the Tapestry markers are gone (ie. no errors or warnings found by the Tapestry integration builder) and *then* remove the nature and builder from the .project file.

Geoff

[Author]

Posts