You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Poder, Jacob" <ja...@thermofisher.com> on 2012/06/01 13:01:14 UTC

RE: Cannot get component library to load

Eclipse docs for the "Add directory entries" option says "adds an entry for each directory to the JAR file, even if the directory does only contain subdirectories".

In my case, the component rendered in java code (beginRender/afterRender) e.g. src/main/java/.../components/Render.java did not have a corresponding template src/main/resources/.../components/Render.tml and thus left the entire resources folder hierarchy without files.
Omitting said option excludes the empty folder hierarchy from the jar and in turn keeps Tapestry from accepting the component.

Best regards,
Jacob


-----Original Message-----
From: LanceWhite [mailto:groliffe@gmail.com] 
Sent: Thursday, May 31, 2012 5:41 PM
To: users@tapestry.apache.org
Subject: RE: Cannot get component library to load

Yeeha!

That did it for me as well - have to look now & see exactly what that does with the jar.


Thanks a lot folks!


Lance

--
View this message in context: http://tapestry.1045711.n5.nabble.com/Cannot-get-component-library-to-load-tp5713444p5713558.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


RE: Cannot get component library to load

Posted by Lance Java <la...@googlemail.com>.
This is starting to sound like an issue that should be fixed in tapestry
rather than changing the way the jar is generated.

It sounds like tapestry will act differently when referencing a classpath
jar than if unzipping the jar and referencing a classpath directory. I think
tapestry should act exactly the same in these two circumstances.

There is an interesting conversation here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=243163



--
View this message in context: http://tapestry.1045711.n5.nabble.com/Cannot-get-component-library-to-load-tp5713444p5713575.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org