Works. Got that:

Downloading: 
http://repo1.maven.org/maven2/org/apache/myfaces/trinidad/trinidad-api/1.0.3/trinidad-api-1.0.3.pom
5K downloaded

Greetings,
Matthias


On Nov 19, 2007 6:09 PM, David Heffelfinger <[EMAIL PROTECTED]> wrote:
> If it's not too much trouble, can you delete your 1.0.3 jar files from any
> local repositories and try again?
>
> I think what might be happening is Maven is finding the 1.0.3 jar files in
> your local repository, therefore it never looks for them in the central
> repo.
>
> Deleting the 1.0.3 jar files and doing an "mvn clean package" *should* fail.
>
> Thanks,
> David
>
>
>
> On Nov 19, 2007 12:02 PM, Matthias Wessendorf < [EMAIL PROTECTED]> wrote:
> > gpg=> ups :-)
> >
> > well... i have also apps with 1.0.3 and that works.
> > Never seen that issue...
> >
> > Perhaps "maven random" is true here as well.
> > Maven builds (should) just work :-)
> >
> >
> >
> >
> > On Nov 19, 2007 5:29 PM, David Heffelfinger < [EMAIL PROTECTED]>
> wrote:
> > > The problem is maven-metadata.xml only lists 1.0.4.
> > >
> > > Maven reads this file to determine what versions are available in the
> > > repository. Therefore, the following dependency declaration fails:
> > >
> > >
> > > <dependency>
> > >    <groupId>org.apache.myfaces.trinidad</groupId>
> > >   <artifactId>trinidad-api</artifactId>
> > >
> > >   <version>1.2.3</version>
> > > </dependency>
> > >
> > > It fails because Maven can't find version 1.2.3 in the repository, even
> > > though it is there.
> > >
> > > The reason it can't find it is because it is not listed in
> > > maven-metadata.xml.
> > >
> > > BTW, I forgot to mention earlier, the trinidad pom.xml is set up to ask
> for
> > > a passphrase to digitally sign the build, since I don't have a
> passphrase, I
> > > had to comment out that section of the pom.xml:
> > >
> > >  <!--plugin>
> > >    <groupId>org.apache.maven.plugins</groupId>
> > >    <artifactId>maven-gpg-plugin</artifactId>
> > >    <executions>
> > >      <execution>
> > >        <id>sign-artifacts</id>
> > >        <phase>verify</phase>
> > >        <goals>
> > >          <goal>sign</goal>
> > >        </goals>
> > >      </execution>
> > >    </executions>
> > >  </plugin-->
> > >
> > > After commenting that out, my build was successful.
> > >
> > > David
> > >
> > >
> > > On Nov 19, 2007 11:20 AM, Matthias Wessendorf < [EMAIL PROTECTED]>
> wrote:
> > > > I think I still don't get the source of issue.
> > > > I had had never problems with downloading the trinidad dependencies
> via
> > > maven.
> > > >
> > > > -Matthias
> > > >
> > > >
> > > >
> > > >
> > > > On Nov 19, 2007 5:12 PM, David Heffelfinger < [EMAIL PROTECTED]
> >
> > > wrote:
> > > > > FWIW, I was able to work around the issue by downloading the source
> for
> > > > > Trinidad 1.2.3 and building it locally.
> > > > >
> > > > > An "mvn install" later, I had the 1.2.3 libraries in my local
> > > repository.
> > > > >
> > > > > David
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > 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
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > 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/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > >
> > > >
> > > >
> > > > 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/
> > sessions: http://www.slideshare.net/mwessendorf
> > 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/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org

Reply via email to