Matt & M@,
Thanks for your work on this issue. I just upgraded to 2.01, and this works
like a charm...
Matthew Sinclair wrote:
>
> Matt and Mark,
>
> I think I may have isolated the problem here (if not completely solved
> it). Because the code works as advertised when running jetty:run-war
On 11/23/07, traceon <[EMAIL PROTECTED]> wrote:
>
>
> i've done the following:
> - run mvn package
> - copied changes (see below)
> "myproject\target\myproject-
> 1.0-SNAPSHOT\META-INF\maven\org.appfuse\appfuse-tapestry\pom.xml"
> to
> "myproject\pom.xml"
> - run mvn clean
> - run mvn package
> - o
i've done the following:
- run mvn package
- copied changes (see below)
"myproject\target\myproject-1.0-SNAPSHOT\META-INF\maven\org.appfuse\appfuse-tapestry\pom.xml"
to
"myproject\pom.xml"
- run mvn clean
- run mvn package
- open
"myproject\target\myproject-1.0-SNAPSHOT\META-INF\maven\org.appfuse\
On 11/23/07, traceon <[EMAIL PROTECTED]> wrote:
>
>
> the point is, that i there are no "tapestry-flash, tapestry-spring"
> entries
> in my pom.xml under "myproject/pom.xml" which i can change from "runtime"
> to
> "compile". the entries only appear in the pom's under the target folder.
Then that
the point is, that i there are no "tapestry-flash, tapestry-spring" entries
in my pom.xml under "myproject/pom.xml" which i can change from "runtime" to
"compile". the entries only appear in the pom's under the target folder.
Mike Horwitz wrote:
>
> Have you tried a mvn clean then full build a
Have you tried a mvn clean then full build after changing the pom files (as
a note you should never change/need to change anything under target - target
is Maven's work area so gets overwritten frequently).
Mike
On 11/23/07, traceon <[EMAIL PROTECTED]> wrote:
>
>
> okay.. i'm running a tapestry-
okay.. i'm running a tapestry-basic app. after changing all pom's, i still
have the problem. has anyone an idea?
Matthew Sinclair wrote:
>
> Good point about the pom - the one I made the change in was the root pom
> at the top level, above the "core" and "web" directories (in a
> tapestry-modu
Good point about the pom - the one I made the change in was the root pom at
the top level, above the "core" and "web" directories (in a tapestry-modular
archetype). HTH, M@
traceon wrote:
>
> hi together,
>
> unfortunatley this doesn't work for me. in which specific pom i have to do
> this cha
hi together,
unfortunatley this doesn't work for me. in which specific pom i have to do
this changes!? i have upto 5 pom's (wich tapestry-spring, tapestry-flash
entries) in my target and 1 in my src folder. i've changed all specific
entries from "runtime" to compile, but i still get the error. ar
Can you please enter an issue for this in JIRA so we can solve this
before the next release?
http://issues.appfuse.org/browse/APF
Thanks,
Matt
On Nov 20, 2007, at 8:18 PM, Matthew Sinclair wrote:
Matt and Mark,
I think I may have isolated the problem here (if not completely
solved it).
Matt and Mark,
I think I may have isolated the problem here (if not completely solved it).
Because the code works as advertised when running jetty:run-war (and
tomcat:run), it has to be something to do with the way packaging works for
the container that causes the problem. So, after looking at th
Outstanding, Matt! I can continue development with frequent restarts,
but it'll be so much nicer to have directory scanning and
auto-reloading. I'm new to the world of Maven, and find it somewhat
frustrating to not see what's going on under the covers. In the
meantime, I'll give tomcat:run a
FWIW, I've posted this to the Tapestry users mailing list:
http://www.nabble.com/Problem-with-jetty%3Arun-when-using-Tapestry-4.1.3-tf4489399.html#a12805568
Matt
mraible wrote:
>
> That's certainly a strange one. I was able to reproduce it, but have
> no idea how to fix it. jetty:run-war work
That's certainly a strange one. I was able to reproduce it, but have
no idea how to fix it. jetty:run-war works fine, as does tomcat:run. I
don't think tomcat:run does directory scanning and auto-reloading, so
I don't know if it's as good as the Jetty plugin. Here's the
configuration for it:
Hi,
I'm running into the following error on certain tapestry pages after
login, including MainMenu. It looks as if the hivemind/spring wiring
is broken. The app runs fine with jetty:run-war.
[ +/- ] Exception: Error at
context:/WEB-INF/tapestry/mainMenu.page, lin
15 matches
Mail list logo
