Hi, Trinidad 123 is deployed on the m2 repos, like here: http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/myfaces/trinidad/trinidad/1.2.3/
I am not sure, why it wants a trinidad-test-war-001 artifact. The metadata points to 1.0.4 b/c we released that guy during this week. So, it is the last release, but tied to JSF 1.1 API http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/myfaces/trinidad/trinidad-api/maven-metadata.xml Not sure, how to fix the "latest" release issue. -M On Nov 16, 2007 10:06 AM, David Heffelfinger <[EMAIL PROTECTED]> wrote: > I did [1,2,) because I want the latest 1.2 version, Maven should > automatically upgrade the version as soon as one comes out. > > In any case, I modified the pom.xml as suggested: > > <dependency> > <groupId> org.apache.myfaces.trinidad</groupId> > <artifactId>trinidad</artifactId> > <version>1.2.3</version> > </dependency> > > And I still can't build create a WAR file via mvn package: > > [INFO] Failed to resolve artifact. > > Missing: > ---------- > 1) org.apache.myfaces.trinidad:trinidad:jar:1.2.3 > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.myfaces.trinidad > -DartifactI > d=trinidad \ > -Dversion=1.2.3 -Dpackaging=jar -Dfile=/path/to/file > > Path to dependency: > 1) trinidadtest:trinidadtest:war: 0.0.1 > 2) org.apache.myfaces.trinidad:trinidad:jar:1.2.3 > > ---------- > 1 required artifact is missing. > > for artifact: > trinidadtest:trinidadtest:war:0.0.1 > > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > > I suspect this is because version 1.2.3 is not listed in the > maven-metadata.xml for Trinidad. > > I'll take a look at the demos later, but I think I looked at them earlier > and they were using 1.0.x, if I remember correctly, the examples might not > be able to help me. Thanks for the tip, though. > > David > > > > On Nov 16, 2007 9:53 AM, Matthias Wessendorf < [EMAIL PROTECTED]> wrote: > > Hi, > > > > 1.2.4 will be out SOON. The recent 1.2.x version is 1.2.3. > > > > I am not really sure, why you did: > > <version>[1.2,)</version> > > > > instead of: > > <version>1.2.3</version> > > > > > > See our demos as an example of how to configure Trinidad inside the pom. > > > > -Matthias > > > > > > > > > > On Nov 16, 2007 9:45 AM, David Heffelfinger <[EMAIL PROTECTED]> > wrote: > > > Hello, > > > > > > I've been reading about Trinidad and it looks like a very nice component > > > library. I would like to give it a try. > > > > > > I would like to use the 1.2.x branch since I am using a server that > supports > > > JSF 1.2 . > > > > > > Unfortunately, adding a dependency of trinidad 1.2 or later to my Maven > 2 > > > pom.xml fails to retrieve the correct JARs from the maven repository. > > > > > > Here is the dependency declaration in my pom.xml: > > > > > > <dependencies> > > > <dependency> > > > <groupId>org.apache.myfaces.trinidad</groupId> > > > <artifactId>trinidad</artifactId> > > > <version>[1.2,)</version> > > > </dependency> > > > > > > Here is the error message I get after mvn package: > > > > > > [ERROR] BUILD ERROR > > > [INFO] > > > ------------------------------------------------------------------------ > > > [INFO] Failed to resolve artifact. > > > > > > Couldn't find a version in [ 1.0.4] to match range [1.2,) > > > org.apache.myfaces.trinidad:trinidad:jar:null > > > > > > from the specified remote repositories: > > > central (http://repo1.maven.org/maven2 ) > > > > > > I looked at the maven-metadata.xml in the repository and it looks like > > > this: > > > > > > <?xml version="1.0" encoding="UTF-8"?><metadata > > > > > > > <groupId> org.apache.myfaces.trinidad</groupId> > > > <artifactId>trinidad</ > > > artifactId> > > > <version>1.0.4</version> > > > <versioning> > > > <versions > > > > > > > <version> 1.0.4</version> > > > > > > </versions> > > > < > > > lastUpdated>20071109100147</lastUpdated> > > > </versioning> > > > </metadata> > > > It looks like the 1.2.x versions are not listed in this file, and I > assume > > > this is why Maven is not able to retrieve them, even though they are in > the > > > repository. > > > > > > Is there anything I can do so that Maven can pull the latest 1.2 version > > > from the Maven repository? > > > > > > Thanks, > > > David R. Heffelfinger > > > > > > > > > > > > -- > > > http://ensode.net - A Guide to Java, Linux and Other Technology Topics > > > http://java-ee-5-glassfish.packtpub.com/ - Java EE 5 Development Using > > > GlassFish Application Server > > > http://jasperreportsbook.packtpub.com - JasperReports For Java > Developers > > > > > > > > -- > > Matthias Wessendorf > > > > further stuff: > > blog: http://matthiaswessendorf.wordpress.com/ > > mail: matzew-at-apache-dot-org > > > > > > -- > http://ensode.net - A Guide to Java, Linux and Other Technology Topics > http://java-ee-5-glassfish.packtpub.com/ - Java EE 5 Development Using > GlassFish Application Server > http://jasperreportsbook.packtpub.com - JasperReports For Java Developers -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
