Hi Shane,
Do you have any plans for switching the local repository mechanism
back to using POMs?
I would at least like to have a flavor that works like Maven normally
does and for this to be the default. For me this is requisite for
NMaven to be integrated into the Maven project. I realize that there
are shortcomings with the artifact resolution mechanism and using RDF
might be good for exploration, but it makes NMaven too divergent from
Maven IMO, is confusing to users and really makes NMaven something
different.
I think you're having a hard enough time getting a community going
and I don't think this fundamental difference in behavior is going to
help much in that respect. For me, the three groups I know who are
using it, use both Java and .NET and I always get asked why doesn't
NMaven use POMs like Maven? Will NMaven not currently work without
RDF? And do you really see there being value in being wholly
different with respect to local repository metadata?
On 30 Sep 07, at 7:57 PM 30 Sep 07, Shane Isbell wrote:
Hi Paul,
When NMaven checks for the existence of a file locally, it looks in
the uac
directory not the repository directory. I am wondering whether the
meta-data
in your RDF repo is correct. Can you try:
mvn org.apache.maven.dotnet.plugins:maven-repository-
plugin:export-rdf
and post the results of the
.m2/uac/rdfRepository/rdf-repository-export.xmlto a jira? I'll take a
look at it as a starting point to track down the
problem.
Thanks,
Shane
On 9/28/07, paul anderson <[EMAIL PROTECTED]> wrote:
Greetings. Seasoned java/regular maven user here. Now working
with .NET .
. . . .
Building went fine - (had csc and xsd.exe on path).
problem came when trying to actually use : mvn compile with a valid
pom.xml file in the directory
(note that I also did not have an nmaven-settings.xml file - not sure
why):
got this (between * for easy parsing):
*********************************************************************
**************
[INFO] Scanning for projects...
[INFO]
---------------------------------------------------------------------
-------
[INFO] Building Unnamed - snipped:ratecube:library:1.0
[INFO] task-segment: [compile]
[INFO]
---------------------------------------------------------------------
-------
[INFO] [compile:initialize]
[INFO] Mojo Execution Time = 0
[INFO] [resolver:resolve]
[INFO]
---------------------------------------------------------------------
---
[ERROR] BUILD ERROR
[INFO]
---------------------------------------------------------------------
---
[INFO] Failed to resolve artifact.
Missing:
----------
1) NMaven.Plugins:NMaven.Plugin.Resx:exe.config:0.14-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=NMaven.Plugins -DartifactId=
NMaven.Plugin.Resx \
-Dversion=0.14-SNAPSHOT -Dpackaging=exe.config-Dfile=/
path/to/file
*********************************************************************
**************************
So, I did just that, where I set /path/tofile = to:
C:\Docume~1\<homedir>\.m2\repository\NMaven\Plugins
\NMaven.Plugin.Resx\0.14-SNAPSHOT\NMaven.Plugin.Resx.exe
Note that I *found* the supposedly not-found resx plugin where it was
supposed to be. Am I missing
something here?
Anyway, that generated my nmaven-settings.xml file, and the
following mvn
compile worked.
Hope this helps at least someone - I scratched my head for a day
over this
one. Oh - I also read
the README.txt, and something in there triggered my thinking about
forcing
the install of the file
that I knew I had.
_____________________________________________________________________
_______________
Shape Yahoo! in your own image. Join our Network Research Panel
today!
http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
