I wasnt sure this was a flaw in maven or even jetty... i just forgot
to nail down a working iteration, is all.. :-/
i might be wrong, but I think i read that snapshots was meant for say
a team of people with inter-team dependencies that need to be in sync.
With that theres the implication that theres going to be some
instability...
in this case, i depended on that mechanism (incorrectly) accidently
and i noticed that the timetracker example did, also. just trying to
help, not rail against anything...
peace,
josh
On 7/24/06, Josh Long <[EMAIL PROTECTED]> wrote:
Im not sure if anyone else has experienced the same thing, but...
On my windows laptop (at home) yesterday around 6 pm i was testing
code and workng just fine on a tapestry 4.1 app. i ran mvn on it and
everything was fine. then i got home after a roudy night at 1 am and
found that mvn jetty6:run didnt work (to my chagrin) and this was, i
suspect because some scandalous change was introduced, and the error i
got was something about a WebApp getclasspathurl...
anyway,
I then took a look at the timetracker app in svn this morning. i ran
mvn install on all of the examples, and particularly, i cd'ed into
TimeTracker and ran mvn jetty6:run and ran into the same issue becaue
the jetty6 plugin was specified as snapshot (as it had been in my
project last night). ...
Long story short: if you run into this problem, modify the pom to use
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty6-plugin</artifactId>
<version>6.0.0beta17</version>
instead of the snapshot. its a workaround, not a solution, but i
thought id spare someone the 10 mins of stuper...
Josh
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
