Hello Julian,

the project name is Tobago.

The svn has moved to the myfaces part of the repository.
You can switch to the new svn url with

svn sw https://svn.apache.org/repos/asf/myfaces/tobago/trunk

in the tobago main directory.

Note http or https depends on your checkout.

Which test has an failure?

Regards

Bernd


Julian Klappenbach schrieb:
I intend to use Tabago with JBoss Seam, which features MyFaces and
Facelets. I'll need to read more about Tabago's layout facilities. If they're sufficient, perhaps all templating can be done with Tabago.

Looks like it builds fine, as jar and tlds have been generated.  Maven
did report an error when executing tests:

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: There are test
failures.        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: There are
test failures.
        at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:389)
       at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)


On 4/15/06, Michael Baranov <[EMAIL PROTECTED]> wrote:

Hi Julian!

Please report if you have successfully built and used Tabago, as I'm very
curious about it. Did it gave you any benefits? Can it replace (at some
extent) Facelets or Tiles or similar?

Michael.


Thanks. The root data isn't visible via subclipse. That's what I get
for being tricky.

;)

On 4/15/06, Bernd Bohmann <[EMAIL PROTECTED]> wrote:


Hello Julian,

please follow the instructions in

http://myfaces.apache.org/tobago/getting-started.html

a mvn install in the tobago root dir should build all required artifacts.

Bernd

Julian Klappenbach schrieb:


Here's the output from mvn -X on core:

~/workspace/tobago-core$ mvn -X
+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from:
'/home/julian/.m2/plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'/home/julian/workspace/maven-2.0/conf/plugin-registry.xml'
[INFO] Scanning for projects...
[DEBUG] Retrieving parent-POM from the repository for project:
null:tobago-core:jar:null
[DEBUG] Skipping disabled repository central
[DEBUG] tobago: using locally installed snapshot
[DEBUG] Skipping disabled repository central
[INFO]
----------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
----------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: org.apache.myfaces.tobago
ArtifactId: tobago
Version: 1.0.7-SNAPSHOT

Reason: Unable to download the artifact from any repository
org.apache.myfaces.tobago:tobago:1.0.7-SNAPSHOT:pom

from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
----------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.reactor.MavenExecutionException: POM
'org.apache.myfaces.tobago:tobago' not found in repository:
Unable to
download the artifact from any repository
org.apache.myfaces.tobago:tobago:1.0.7-SNAPSHOT:pom

from the specified remote repositories:
central (http://repo1.maven.org/maven2)

at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:359)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:276)
at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
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.project.ProjectBuildingException: POM
'org.apache.myfaces.tobago:tobago' not found in repository:
Unable to
download the artifact from any repository
org.apache.myfaces.tobago:tobago:1.0.7-SNAPSHOT:pom

from the specified remote repositories:
central (http://repo1.maven.org/maven2)

at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:423)
at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:955)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:586)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:298)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:276)
at
org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:509)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:441)
at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:345)
... 11 more
Caused by:
org.apache.maven.artifact.resolver.ArtifactNotFoundException:
Unable to download the artifact from any repository
org.apache.myfaces.tobago:tobago:1.0.7-SNAPSHOT:pom

from the specified remote repositories:
central (http://repo1.maven.org/maven2)

at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:136)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:380)
... 18 more
Caused by:
org.apache.maven.wagon.ResourceDoesNotExistException:
Unable to download the artifact from any repository
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:260)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:124)
... 20 more
[INFO]
----------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Sat Apr 15 11:30:06 PDT 2006
[INFO] Final Memory: 1M/2M
[INFO]
----------------------------------------------------------------------------




On 4/15/06, Julian Klappenbach <[EMAIL PROTECTED]> wrote:



First, I'm using code from
svn.apache.org/repos/asf/incubator/tobago/trunk. Is that
the correct
repository?

If so, there's several "modules" under trunk:

contrib, core, doc, example, src, theme, tobago-assembly, and tobago-tool.

Do I need to compile in any certain order? Or do I just focus on one.
The most promising would appear to be core.

I'll try running mvn -X on core to see what's going on.

-jjk

On 4/15/06, Bernd Bohmann <[EMAIL PROTECTED]> wrote:



Hello Julian,

Tobago is not in a immature state.
Can you send the error?

May be the mvn debug output with mvn -X helps.

Regards

Bernd

Julian Klappenbach schrieb:



I'm considering using Tabago as a project, but noticed that it may
either be in a very immature state, or perhaps abandoned.

Has anyone had any experience with it? I downloaded the source from
SVN, along with Maven, but I can't seem to get anything to build. So,
if this is a successful path, that's where I would need to start off.

Thanks in advance!


--
Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333


--
Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333








--
Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333

Reply via email to