Building NMaven

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Building NMaven

Wendy Smoak
Some thoughts from a new user...

The build-bootstrap.sh script doesn't work in Cygwin.  (Build output
captured and viewed in vi, I don't think the extra character shows on
the console.)

INFO] Invalid task 'install^M': you must specify a valid lifecycle phase, or a
goal in the format plugin:goal or
pluginGroupId:pluginArtifactId:pluginVersion:goal

Next I had an adventure trying to find 'csc.exe' which wasn't on my
path, nor anywhere programs ought to be found, despite having all
sorts of Microsoft stuff (Visual Studio, etc.,) installed on my laptop
from various class projects.

Then NUnit needed to be installed (which is mentioned on the getting
started page) and finally the bootstrap build completed.

Here's a suggestion for the readme file.  (Is there wiki space yet for
the project?)

Index: README.txt
===================================================================
--- README.txt  (revision 509411)
+++ README.txt  (working copy)
@@ -1,3 +1,7 @@
+Prerequisites
+* csc.exe must be available on your PATH.  Usually it can be found in
C:\WINDOWS\Microsoft.NET\Framework\[version]
+* NUnit must be installed or otherwise configured, see
http://incubator.apache.org/nmaven/getting-started.html
+
 Initial Build
 * On the first build, execute the bootstrap-build script. On
subsequent builds, you can just type mvn install from
 the command prompt.

Thanks,
--
Wendy
http://wiki.wsmoak.net/cgi-bin/wiki.pl?NMaven
Reply | Threaded
Open this post in threaded view
|

Re: Building NMaven

Shane Isbell
Hi  Wendy,

I haven't tested the shell script on Cygwin before. I do see the behavior
that you mentioned below; I will need to investigate. For Windows, you
shouldn't need to specify the csc in the path: NMaven reads the windows
registry for .NET install roots and writes the information to ~/.m2/nmaven-
settings.xml. Did this file generate for you?

Shane


On 2/19/07, Wendy Smoak <[hidden email]> wrote:

>
> Some thoughts from a new user...
>
> The build-bootstrap.sh script doesn't work in Cygwin.  (Build output
> captured and viewed in vi, I don't think the extra character shows on
> the console.)
>
> INFO] Invalid task 'install^M': you must specify a valid lifecycle phase,
> or a
> goal in the format plugin:goal or
> pluginGroupId:pluginArtifactId:pluginVersion:goal
>
> Next I had an adventure trying to find 'csc.exe' which wasn't on my
> path, nor anywhere programs ought to be found, despite having all
> sorts of Microsoft stuff (Visual Studio, etc.,) installed on my laptop
> from various class projects.
>
> Then NUnit needed to be installed (which is mentioned on the getting
> started page) and finally the bootstrap build completed.
>
> Here's a suggestion for the readme file.  (Is there wiki space yet for
> the project?)
>
> Index: README.txt
> ===================================================================
> --- README.txt  (revision 509411)
> +++ README.txt  (working copy)
> @@ -1,3 +1,7 @@
> +Prerequisites
> +* csc.exe must be available on your PATH.  Usually it can be found in
> C:\WINDOWS\Microsoft.NET\Framework\[version]
> +* NUnit must be installed or otherwise configured, see
> http://incubator.apache.org/nmaven/getting-started.html
> +
> Initial Build
> * On the first build, execute the bootstrap-build script. On
> subsequent builds, you can just type mvn install from
> the command prompt.
>
> Thanks,
> --
> Wendy
> http://wiki.wsmoak.net/cgi-bin/wiki.pl?NMaven
>
Reply | Threaded
Open this post in threaded view
|

Re: Building NMaven

Wendy Smoak
On 2/19/07, Shane Isbell <[hidden email]> wrote:

> For Windows, you
> shouldn't need to specify the csc in the path:

Prior to adding csc.exe to my path, I got:

[ERROR] 'csc' is not recognized as an internal or external command,
[ERROR] operable program or batch file.

Full details here:  http://wiki.wsmoak.net/cgi-bin/wiki.pl?NMaven

> NMaven reads the windows
> registry for .NET install roots and writes the information to ~/.m2/nmaven-
> settings.xml. Did this file generate for you?

No, it's not there, even now that the bootstrap build has completed
successfully.

--
Wendy
Reply | Threaded
Open this post in threaded view
|

Re: Building NMaven

Shane Isbell
I filed the bug here: http://jira.codehaus.org/browse/NMAVEN-7. NMaven
should not be executing based on the path (unless it is unable to locate a
valid fullly qualified directory path to the compiler).  I will branch the
trunk and see what the problem is.

Shane


On 2/19/07, Wendy Smoak <[hidden email]> wrote:

>
> On 2/19/07, Shane Isbell <[hidden email]> wrote:
>
> > For Windows, you
> > shouldn't need to specify the csc in the path:
>
> Prior to adding csc.exe to my path, I got:
>
> [ERROR] 'csc' is not recognized as an internal or external command,
> [ERROR] operable program or batch file.
>
> Full details here:  http://wiki.wsmoak.net/cgi-bin/wiki.pl?NMaven
>
> > NMaven reads the windows
> > registry for .NET install roots and writes the information to
> ~/.m2/nmaven-
> > settings.xml. Did this file generate for you?
>
> No, it's not there, even now that the bootstrap build has completed
> successfully.
>
> --
> Wendy
>
Reply | Threaded
Open this post in threaded view
|

Re: Building NMaven

Shane Isbell
HI Wendy,

I removed the csc from my path and everything worked fine (in DOS prompt). I
think that the problem is related to NMaven not generating the
nmaven-settings.xml file. I have attached a sample settings file to the
issue: http://jira.codehaus.org/browse/NMAVEN-7. Try 1) removing csc from
your Path; 2) downloading the nmaven-settings.xml file and placing it within
your ~/.m2 directory; 3) recompiling. If that works, I'll need to look into
why the settings file is not being auto-generated.

Thanks,
Shane


On 2/19/07, Shane Isbell <[hidden email]> wrote:

>
> I filed the bug here: http://jira.codehaus.org/browse/NMAVEN-7. NMaven
> should not be executing based on the path (unless it is unable to locate a
> valid fullly qualified directory path to the compiler).  I will branch the
> trunk and see what the problem is.
>
> Shane
>
>
> On 2/19/07, Wendy Smoak <[hidden email]> wrote:
> >
> > On 2/19/07, Shane Isbell <[hidden email]> wrote:
> >
> > > For Windows, you
> > > shouldn't need to specify the csc in the path:
> >
> > Prior to adding csc.exe to my path, I got:
> >
> > [ERROR] 'csc' is not recognized as an internal or external command,
> > [ERROR] operable program or batch file.
> >
> > Full details here:  http://wiki.wsmoak.net/cgi-bin/wiki.pl?NMaven
> >
> > > NMaven reads the windows
> > > registry for .NET install roots and writes the information to
> > ~/.m2/nmaven-
> > > settings.xml. Did this file generate for you?
> >
> > No, it's not there, even now that the bootstrap build has completed
> > successfully.
> >
> > --
> > Wendy
> >
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Building NMaven

Shane Isbell
I managed to reproduce this problem: it required clearing the local maven
repository, removing the nmaven-settings.xml file and running the bootstrap
build. NMaven relies on the nmaven-settings.xml file to locate the .NET
framework install roots but NMaven needs to build the settings utility (with
csc) before it can generate the nmaven-settings.xml file. I'll update the
documentation.

Shane


On 2/19/07, Shane Isbell <[hidden email]> wrote:

>
> HI Wendy,
>
> I removed the csc from my path and everything worked fine (in DOS
> prompt). I think that the problem is related to NMaven not generating the
> nmaven-settings.xml file. I have attached a sample settings file to the
> issue: http://jira.codehaus.org/browse/NMAVEN-7. Try 1) removing csc from
> your Path; 2) downloading the nmaven-settings.xml file and placing it
> within your ~/.m2 directory; 3) recompiling. If that works, I'll need to
> look into why the settings file is not being auto-generated.
>
> Thanks,
> Shane
>
>
>  On 2/19/07, Shane Isbell <[hidden email]> wrote:
> >
> > I filed the bug here: http://jira.codehaus.org/browse/NMAVEN-7. NMaven
> > should not be executing based on the path (unless it is unable to locate a
> > valid fullly qualified directory path to the compiler).  I will branch the
> > trunk and see what the problem is.
> >
> > Shane
> >
> >
> > On 2/19/07, Wendy Smoak <[hidden email] > wrote:
> > >
> > > On 2/19/07, Shane Isbell < [hidden email]> wrote:
> > >
> > > > For Windows, you
> > > > shouldn't need to specify the csc in the path:
> > >
> > > Prior to adding csc.exe to my path, I got:
> > >
> > > [ERROR] 'csc' is not recognized as an internal or external command,
> > > [ERROR] operable program or batch file.
> > >
> > > Full details here:  http://wiki.wsmoak.net/cgi-bin/wiki.pl?NMaven
> > >
> > > > NMaven reads the windows
> > > > registry for .NET install roots and writes the information to
> > > ~/.m2/nmaven-
> > > > settings.xml. Did this file generate for you?
> > >
> > > No, it's not there, even now that the bootstrap build has completed
> > > successfully.
> > >
> > > --
> > > Wendy
> > >
> >
> >
>