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\appfuse-tapestry\pom.xml"
tapestry-flash, tapestry-spring scope is still set to "runtime" and not (as
specified in main pom.xml) to "compile".
<dependency>
<groupId>com.javaforge.tapestry</groupId>
<artifactId>tapestry-flash</artifactId>
<version>${tapestry.flash.version}</version>
<scope>compile</scope>
<exclusions>
<exclusion>
<groupId>tapestry</groupId>
<artifactId>tapestry</artifactId>
</exclusion>
<exclusion>
<groupId>tapestry</groupId>
<artifactId>tapestry-annotations</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.javaforge.tapestry</groupId>
<artifactId>tapestry-spring</artifactId>
<version>${tapestry.spring.version}</version>
<scope>compile</scope>
<exclusions>
<exclusion>
<groupId>tapestry</groupId>
<artifactId>tapestry</artifactId>
</exclusion>
<exclusion>
<groupId>tapestry</groupId>
<artifactId>tapestry-annotations</artifactId>
</exclusion>
</exclusions>
</dependency>
...
<properties>
<!-- Application settings -->
....
<tapestry.spring.version>1.0.0</tapestry.spring.version>
<tapestry.flash.version>1.0.0</tapestry.flash.version>
...
Mike Horwitz wrote:
>
> 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 explains it. Your entries are being inherited transitively
> through
> the appfuse-tapestry project. Point still stands though - changing
> anything
> under the target folder will have no effect on the build. What you will
> have
> to do to get things working is to copy the two dependencies from one of
> the
> pom.xml files in target to the pom at the root of your project (assuming
> you
> are using a basic archetype). Change the scope of the dependency there and
> they will override the ones inherited transitively. Remember to do a clean
> before recompiling ...
>
> Mike
>
> Mike Horwitz wrote:
>> >
>> > 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-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-modular archetype). HTH, M@
>> >> >
>> >> >
>> >> > traceon wrote:
>> >> >>
>> >> >> 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. are there any more requried steps?
>> >> >>
>> >> >> thx for your help!
>> >> >>
>> >> >>
>> >> >>
>> >> >> 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
>> >> >>> (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
>> >> >>> this page:
>> >> >>>
>> >> >>> http://static.appfuse.org/appfuse-tapestry/dependencies.html
>> >> >>>
>> >> >>> And comparing that with my pom, I noticed that I had
>> scope="compile"
>> >> for
>> >> >>> tapestry-spring and scope="runtime" for tapestry-flash. Then it
>> >> dawned
>> >> >>> on me, I'd changed the scope for tapestry-spring in an earlier
>> >> attempt
>> >> >>> to hunt down this problem. What made me twig was the fact that the
>> >> >>> problem reported by tapestry had *moved* from not knowing about
>> >> >>> "type='spring'", to not knowing about "persist='flash'".
>> >> >>>
>> >> >>> Changing the scope from "runtime" to "compile" time for both
>> >> >>> tapestry-spring and tapestry-flash in the web/pom.xml allowed
>> >> jetty:run
>> >> >>> to work.
>> >> >>>
>> >> >>> Wow, that took me a lot longer to work through than I had hoped,
>> but
>> >> at
>> >> >>> least it's fixed. I can't say I know *why* changing the scope from
>> >> >>> runtime to compile makes jetty:run work, but I'll leave that for
>> >> another
>> >> >>> day.
>> >> >>>
>> >> >>> Regards,
>> >> >>> M@
>> >> >>>
>> >> >>>
>> >> >>> Mark Rosenthal-2 wrote:
>> >> >>>>
>> >> >>>> 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 go.
>> >> >>>>
>> >> >>>> mraible wrote:
>> >> >>>>> 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
>> >> >>>>
>> >> >>>
>> >> >>>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Problem-with-jetty%3Arun-in-Tapestry-basic-archetype-tf4485474s2369.html#a13909545
>> >> Sent from the AppFuse - User mailing list archive at Nabble.com.
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Problem-with-jetty%3Arun-in-Tapestry-basic-archetype-tf4485474s2369.html#a13912288
>> Sent from the AppFuse - User mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Problem-with-jetty%3Arun-in-Tapestry-basic-archetype-tf4485474s2369.html#a13914187
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
