1.0.2 Installation Problems

Sep 3, 2009 at 10:49 AM

Hi,

we have some questions and problems installing the new 1.0.2 Release:

1. Why is there no simple setup for download?

2. [minor important] Why are you compressing using .zipx which forces users to install the latest WinZip release?

3. I tried to build the setup in the following ways but failed with errors:

bootstrap-build.bat -DMicrosoft , bootstrap-build.bat -DVisualStudio2005 and mvn npanday.plugin:maven-vsinstaller-plugin:install

Log:

Downloading: http://repo1.maven.org/maven2/npanday/plugin/maven-vsinstaller-plug

in/1.0.2/maven-vsinstaller-plugin-1.0.2.jar

[WARNING] Unable to get resource 'npanday.plugin:maven-vsinstaller-plugin:maven-

plugin:1.0.2' from repository central (http://repo1.maven.org/maven2): Read time

d out

[INFO] Cannot find mojo descriptor for: 'npanday.plugin:maven-vsinstaller-plugin

:1.0.2:install' - Treating as non-aggregator.

Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ssh-exte

rnal/1.0-beta-2/wagon-ssh-external-1.0-beta-2.pom

[WARNING] Unable to get resource 'org.apache.maven.wagon:wagon-ssh-external:pom:

1.0-beta-2' from repository central (http://repo1.maven.org/maven2): Read timed

out

Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/

plexus-utils-1.1.pom

[WARNING] Unable to get resource 'org.codehaus.plexus:plexus-utils:pom:1.1' from

 repository central (http://repo1.maven.org/maven2): Read timed out

Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/

plexus-utils-1.1.jar

Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ssh-exte

rnal/1.0-beta-2/wagon-ssh-external-1.0-beta-2.jar

[WARNING] Unable to get resource 'org.apache.maven.wagon:wagon-ssh-external:jar:

1.0-beta-2' from repository central (http://repo1.maven.org/maven2): Read timed

out

[WARNING] Unable to get resource 'org.codehaus.plexus:plexus-utils:jar:1.1' from

 repository central (http://repo1.maven.org/maven2): Read timed out

[INFO] ------------------------------------------------------------------------

[ERROR] BUILD ERROR

[INFO] ------------------------------------------------------------------------

[INFO] Failed to resolve artifact.

 

I tried to manually download the missing jar's but I couldn't find them, may be they are no longer provided?

 

Thanks for your support!

 

Developer
Sep 3, 2009 at 2:23 PM
On Thu, Sep 3, 2009 at 2:49 AM, embe<notifications@codeplex.com> wrote:

> 1. Why is there no simple setup for download?

There was an installer for previous versions, I asked recently whether
there would be one for 1.0.2 as well.

> 3. I tried to build the setup in the following ways but failed with errors:
>
> bootstrap-build.bat -DMicrosoft , bootstrap-build.bat -DVisualStudio2005 and
> mvn npanday.plugin:maven-vsinstaller-plugin:install
>
> Log:
>
> Downloading:
> http://repo1.maven.org/maven2/npanday/plugin/maven-vsinstaller-plug
> in/1.0.2/maven-vsinstaller-plugin-1.0.2.jar
> [WARNING] Unable to get resource
> 'npanday.plugin:maven-vsinstaller-plugin:maven-
> plugin:1.0.2' from repository central (http://repo1.maven.org/maven2): Read
> timed out

What did you download? What directory did you type this in? The
artifacts are not available in central, but you should be able to
build from source if you want to.

I've had success with the 'repository builder' download, which is
actually a binary distribution in Maven remote repository format.

Unpack that somewhere, and add a profile to your settings.xml with
(this is important) an id of (exactly) "npanday.id" and a <repository>
and <pluginRepository> both pointing to
file:///path/to/your/npanday/1.0.2/repository.

Then the vsinstaller plugin should work.

--
Wendy
Developer
Sep 3, 2009 at 6:41 PM
embe wrote:

> 2. [minor important] Why are you compressing using .zipx which forces users to install the latest WinZip release?

I opened an issue for this, as well as the fact that the source distribution doesn't contain any pom.xml files (or the bootstrap.bat file either now that I look again.)

I've published the latest docs at http://wsmoak.net/npanday/1.1-SNAPSHOT -- I doubt they have changed much since the release.  I'll try to check out from the tag and publish the 1.0.2 docs later.

In particular, there is some information about manual installation at http://wsmoak.net/npanday/1.1-SNAPSHOT/installation/manual.html .  Just executing the vsinstaller plugin worked for me, but I already had my PATH set up from using previous NPanday versions.

Let us know whether this works for you.

--
Wendy

Sep 8, 2009 at 3:39 PM

Hi Wendy,

sorry for my late reply, I was on the go for a few days.

Today I was able try what you told us, the good news is, it worked.

This is how it worked:

1. I downloaded NPanday 1.0.2 Repository Builder and unzipped it.

2. I copied ...\npandayRepository102\repository\releases\*.* directly to ....\m2\repository (not under .m2\repository\releases!)

3. I changed my .m2/settings.xml file and added a new profile with id="npanday.id"

</profiles>

     <profile>
          <id>npanday.id</id>
            <repositories>
                <repository>
                    <id>npandaylocal</id>
                    <url>file:///C:/Users/Mario/.m2/repository</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>true</enabled>
                    </snapshots>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>npandaylocal</id>
                    <url>file:///C:/Users/Mario/.m2/repository</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>true</enabled>
                    </snapshots>
                </pluginRepository>
            </pluginRepositories>            
        </profile>
    </profiles>

    <activeProfiles>
        <activeProfile>npanday.id</activeProfile>
    </activeProfiles>

4. Since I'm using Windows Vista I had to start my cmd shell as an Administrator (Start->All Programs->Accessories->Right click on "command prompt" and select "Run as administrator"), otherwise the gacutil wasn't able to add the plugin into the gac.

5. Now I executed "mvn npanday.plugin:maven-vsinstaller-plugin:1.0.2:install", it was able to build and register the "NPanday.Plugin.dll".

Thanks for your support!

Mario

Developer
Sep 8, 2009 at 5:22 PM
On Tue, Sep 8, 2009 at 7:39 AM, embe<notifications@codeplex.com> wrote:

> Today I was able try what you told us, the good news is, it worked.

Good to hear!

> 2. I copied ...\npandayRepository102\repository\releases\*.* directly to
> ....\m2\repository (not under .m2\repository\releases!)

This is not entirely correct... you have added it directly to your
_local_ repository instead of setting it up as a remote repository for
Maven to retrieve from.

> 3. I changed my .m2/settings.xml file and added a new profile with
> id="npanday.id"

Pointing at your local repo as a remote repo is definitely not a good idea.

I suggest unpacking the zip file somewhere else (C:\data\repository ?)
and changing the file:// urls in your settings.xml.

--
Wendy
Sep 23, 2009 at 4:45 PM

I needed to manually create the Home/Documents/Visual Studio 2008/Addins folder before the installation procedure would work (it doesn't create the folder if it isn't there already).  This should be added to the manual install page (I wasted a bunch of time on this).

 

And for future reference, is this the correct way to set up remote (but on the same machine) file repositories?

<profiles>
    <profile>
      <id>npanday.id</id>
      <repositories>
        <repository>
          <id>npandaylocal</id>
      <url>file://c:/data/repository</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>true</enabled>
                    </snapshots>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>npandaylocal</id>
            <url>file://c:/data/repository</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>true</enabled>
                    </snapshots>
                </pluginRepository>
            </pluginRepositories>            
        </profile>
  </profiles>