after diving into the build routines and turning on -X i narrowed down to plugin.xml version mismatch since the version i am working with is 1.0 i corrected to <version>1.0</version> and the version mismatch errors are resolved
velocity classes missing for remote-resources-plugin 1.1-SNAPSHOT should I repackage the velocity classes into remote-resources-plugin ? or should i add it as a dependency ? if so where? thanks Martin Gainty ______________________________________________ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Mon, 14 Sep 2009 11:25:08 +0200 > From: benjamin.bentm...@udo.edu > To: dev@maven.apache.org > Subject: Re: 3.0 Maven Model Builder Failure > > Martin Gainty wrote: > > > i downloaded maven-3.0 full > > at command line ran > > mvn -e -X install > > I don't want to sound rude but those few lines aren't really helpful either. > > You "downloaded maven-3.0 full", is that "downloaded" as in you > downloaded some source/binary archive from some URL, or more as in you > checked out some SVN URL? > > You ran "mvn -e -X install". Which version of Maven was that, the > "maven-3.0 full" you just downloaded or something else? > > What I wanted to illustrate is that the given information doesn't allow > us to reproduce your issue, making proper assistance impossible. I can > imagine that it might be hard to consider all the pieces that somebody > else needs to reproduce an issue. For a case like this where you're > building Maven itself the best I can suggest is to provide instructions > that are as detailed that we could create a CI job from them. > > Maven being a build tool, the minimum of information required to analyze > build errors are: > > - the project sources including but not limited to a complete POM, > either given by a SCM URL + Revision or a ready-made archive to unpack > > - the sequence of Maven commands that were executed on the project, for > multi-module projects also indicating the working directory for each > command, last but not least, the version of Maven being used > > - especially for issues related to dependency resolution, some infos > about the network infrastructure, configured repos, mirrors, proxies, > authentication yes/no > > - the JDK (vendor/version) being used to run Maven > > Maven's trunk is building fine on CI [0] so what's the difference > between our CI and your environment? > > > Benjamin > > > [0] https://grid.sonatype.org/ci/job/maven-3.0.x/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > _________________________________________________________________ Bing brings you health info from trusted sources. http://www.bing.com/search?q=pet+allergy&form=MHEINA&publ=WLHMTAG&crea=TXT_MHEINA_Health_Health_PetAllergy_1x1
