Hi there guys,

Finnally I got there.
Sorry for being a such a newbie at this!
You were right, the pom.xml did not exist. It had the original name I got
from the repo. I forgot to change it| :-( Shame on me big time!
Since I got a similar error with java dump and all previouslly when a
correct pom.xml existed I got lazy and did not check properly. Sorry once
again.

Using the pom that Andy had dumped all worked fine.
It just and a little issue... the "issue" word in the middle of the
dependency tags! :-D After removing it all works fine.

So thanks again to all of you for lending me a hand on this and for yout
pacience with my lack of knowledge mavenwise!

regards,

On 8/17/06, andyhot <[EMAIL PROTECTED]> wrote:

Latest jars can be found in

http://people.apache.org/repo/m2-snapshot-repository/org/apache/tapestry/tapestry-framework/4.1.1-SNAPSHOT/

http://people.apache.org/repo/m2-snapshot-repository/org/apache/tapestry/tapestry-contrib/4.1.1-SNAPSHOT/

http://people.apache.org/repo/m2-snapshot-repository/org/apache/tapestry/tapestry-annotations/4.1.1-SNAPSHOT/

Pedro Viegas wrote:
> So am I! :-(
>
> Mark, what I am trying to do is simply get the latest SNAPSHOT of
> Tapestry
> 4.1.1.
> Honnestly I haven't fully understand what this exactly means!
> My app is build another way, nothing to do with this.
> All I want to do is get the latest JAR files os tapestry 4.1.1. I still
> haven't figured it out it it means that Ia have to compile them, just
> deploy
> them, I don't know. All I understand right now is that there is a maven2
> script with would do it for me... it I can get it to work!
>
> The pom is in the directory. The pom file I'm using latest is the one
> Andy
> provided in a previous post witch I will translate bellow.
> I also created the directory sctructure Andy instructed. But it still
> does
> not work!!! Help!!!
>
> Just for the record I'm not trying to integrate my app in the maven
build
> process, nor trying to get the Tap4.1.1 in any peculiar specific way.
Any
> approuch is good for me. All I want to do it get the latest JAR files
> daily
> or whenever Jesse launches them so I can test Tap 4.1.1 with the daily
> error
> corrections and new features/enhancements. So, I know several people
> on this
> list are actually using this without problems... how did you do it?
> Can you
> post your pom files? Did you had to make any changes to maven
> configuration
> like libs or anything?
>
> Thanks,
>
> Thas pom file!
>
> <project>
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>my.group</groupId>
>   <artifactId>my-project< /artifactId>
>   <packaging>war</packaging>
>   <version>0.1.1-SNAPSHOT</version>
>   <description>My description</description>
>   <name>My project name</name>
>
>   <dependencies>
>       <dependency>
>           <groupId>org.apache.tapestry</groupId>
>           <artifactId>tapestry-framework</artifactId>
>       <version>4.1.1-SNAPSHOT</version>
>       </dependency>issue
>       <dependency>
>           <groupId>org.apache.tapestry</groupId>
>           <artifactId>tapestry-contrib</artifactId>
>       <version>4.1.1-SNAPSHOT</version>
>       </dependency>
>       <dependency>
>           <groupId>org.apache.tapestry</groupId>
>           <artifactId>tapestry-annotations</artifactId>
>       <version>4.1.1-SNAPSHOT</version>
>       </dependency>
>   </dependencies>
>
>   <repositories>
>       <repository>
>           <id>apache.snapshots</id>
>           <url>http://people.apache.org/repo/m2-snapshot-repository
</url>
>       </repository>
>       <repository>
>           <id>tapestry.javaforge</id>
>           <url>http://howardlewisship.com/repository</url>
>       </repository>
>   </repositories>
>
>   <pluginRepositories>
>       <pluginRepository>
>           <id>apache.snapshots</id>
>           <url>http://people.apache.org/repo/m2-snapshot-repository
</url>
>       </pluginRepository>
>       <pluginRepository>
>           <id>tapestry.javaforge</id>
>           <url>http://howardlewisship.com/repository</url>
>       </pluginRepository>
>   </pluginRepositories>
>
> </project>
>
>
> On 8/17/06, andyhot <[EMAIL PROTECTED]> wrote:
>>
>> Looks like it can't find the pom.xml file in the current directory...
>> errr... i'm out of ideas...
>>
>> Pedro Viegas wrote:
>> > Thanks Andy for your response.
>> > But unfortunatly I still get the same error of this MOJO
>> dependency! :-(
>> >
>> > + Error stacktraces are turned on.
>> > [INFO] Scanning for projects...
>> > [INFO]
>> >
>>
----------------------------------------------------------------------------
>>
>> >
>> > [INFO] Building Maven Default Project
>> > [INFO]    task-segment: [compile]
>> > [INFO]
>> >
>>
----------------------------------------------------------------------------
>>
>> >
>> > [INFO]
>> >
>>
------------------------------------------------------------------------
>> > [ERROR] BUILD ERROR
>> > [INFO]
>> >
>>
------------------------------------------------------------------------
>> > [INFO] Cannot execute mojo: resources. It requires a project with an
>> > existing pom.xml, but the build is not using one.
>> > [INFO]
>> >
>>
------------------------------------------------------------------------
>> > [INFO] Trace
>> > org.apache.maven.lifecycle.LifecycleExecutionException: Cannot
execute
>> > mojo:
>> > resources. It requires a project with an existing pom.xml, but the
>> > build is
>> > not using one.
>> >        at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>> > DefaultLifecycleExecutor.java:559)
>> >        at
>> >
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
>>
>> >
>> > (DefaultLifecycleExecutor.java:475)
>> >        at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
>> > DefaultLifecycleExecutor.java:454)
>> >        at
>> >
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
>>
>> >
>> > (DefaultLifecycleExecutor.java:306)
>> >        at
>> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
(
>> > DefaultLifecycleExecutor.java:273)
>> >        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(
>> > DefaultLifecycleExecutor.java:140)
>> >        at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>> >        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java
:115)
>> >        at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
>> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >        at sun.reflect.NativeMethodAccessorImpl.invoke(
>> > NativeMethodAccessorImpl.java:39)
>> >        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>> > DelegatingMethodAccessorImpl.java:25)
>> >        at java.lang.reflect.Method.invoke(Method.java:585)
>> >        at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java
>> > :315)
>> >        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> >        at
>> > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java
>> > :430)
>> >        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> > Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot
>> execute
>> > mojo: resources. It requires a project with an existing pom.xml,
>> but the
>> > build is not using one.
>> >        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
>> > DefaultPluginManager.java:339)
>> >        at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>> > DefaultLifecycleExecutor.java:534)
>> >        ... 16 more
>> > [INFO]
>> >
>>
------------------------------------------------------------------------
>> > [INFO] Total time: < 1 second
>> > [INFO] Finished at: Thu Aug 17 01:06:01 BST 2006
>> > [INFO] Final Memory: 2M/3M
>> > [INFO]
>> >
>>
------------------------------------------------------------------------
>> >
>> >
>> > Do you know how to solve this?
>> >
>> > Regards,
>> >
>> >>
>> >
>> >
>>
>>
>> --
>> Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr
>> Tapestry / Tacos developer
>> Open Source / J2EE Consulting
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Pedro Viegas

Reply via email to