You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-dev@incubator.apache.org by Dennis Lundberg <de...@apache.org> on 2011/03/02 17:47:34 UTC
Re: [VOTE] NPANDAY Version 1.3 Incubating
On 2011-02-28 20:43, Dennis Lundberg wrote:
> On 2011-02-27 16:04, Dennis Lundberg wrote:
>> Hi
>>
>> First off - sorry for the long delay. I didn't realize that I was
>> supposed to vote.
>>
>> I've checked the signatures and checksums of the staged artifacts, and
>> they are all fine.
>>
>> I tried to build the source bundle, but didn't get very far because the
>> npanday repo seems to be down, as Lars noted in related thread.
>
> Now that the repo is back up again I got a lot further - all the way to
> "NPanday :: .NET Model :: POM". There the build fails, as expected,
> because I don't have Visual Studio (or its tools) installed.
>
> Will hopefully have time to try building on another machine tomorrow.
Now I've done enough testing to give this release my +1 vote.
Installation from msi package works fine.
A couple of things that we have run into during testing, that can be
fixed in later versions. These were all found running on Windows 7 64-bit.
1. We were not able to build from the source bundle all the way to the
end. This was on a machine with VS2008 and VS2010 installed. See log
file at the end of this message. The build fails in the module "NPanday
:: Repository Builder".
2. Some interdependency between different modules is standing in the way
of doing 'mvn clean verify' on a machine without any npanday
1.3-incubating artifacts in the local repo. One must run 'mvn clean
install' instead. This is caused by a bug in Maven 2, which has been
fixed in Maven 3.
3. Building with Maven 3 fails on one of the modules related to the
lifecycle. Sorry, don't remember which one now. I think Lars already has
done some work to fix this on trunk.
4. Running a 'mvn verify' that failed halfway through, and after that
running 'mvn verify' again (without mvn clean in between) fails with an
error saying that a mkdir command failed.
5. We ran into the 260 char max path length issue with the source bundle
unpacked in the users home directory. Moving the sources to the root
directory solved this.
The log from the failed build under 1.
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) VsWebSite.Interop:VsWebSite.Interop:gac:b03f5f7f11d50a3a:8.0.0.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=VsWebSite.Interop
-DartifactId=VsWebSite.Interop -Dversion=8.0.0.0
-Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=VsWebSite.Interop
-DartifactId=VsWebSite.Interop -Dversion=8.0.0.0
-Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) npanday:dotnet-repository-builder:pom:1.3-incubating
2)
npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
3) VsWebSite.Interop:VsWebSite.Interop:gac:b03f5f7f11d50a3a:8.0.0.0
2) EnvDTE:EnvDTE:gac:b03f5f7f11d50a3a:8.0.0.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=EnvDTE -DartifactId=EnvDTE
-Dversion=8.0.0.0 -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=EnvDTE -DartifactId=EnvDTE
-Dversion=8.0.0.0 -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac
-Dfile=/path/to/file-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) npanday:dotnet-repository-builder:pom:1.3-incubating
2) npanday.visualstudio:NPanday.VisualStudio:library:1.3-incubating
3) EnvDTE:EnvDTE:gac:b03f5f7f11d50a3a:8.0.0.0
3)
Microsoft.Build.Engine:Microsoft.Build.Engine:gac_msil:b03f5f7f11d50a3a:2.0.0.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=Microsoft.Build.Engine
-DartifactId=Microsoft.Build.Engine -Dversion=2.0.0.0
-Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac_msil -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=Microsoft.Build.Engine
-DartifactId=Microsoft.Build.Engine -Dversion=2.0.0.0
-Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac_msil -Dfile=/path/to/file
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) npanday:dotnet-repository-builder:pom:1.3-incubating
2)
npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
3)
npanday.projectimporter:NPanday.ProjectImporterEngine:library:1.3-incubating
4)
Microsoft.Build.Engine:Microsoft.Build.Engine:gac_msil:b03f5f7f11d50a3a:2.0.0.0
4)
Microsoft.VisualStudio.CommandBars:Microsoft.VisualStudio.CommandBars:gac:b03f5f7f11d50a3a:8.0.0.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file
-DgroupId=Microsoft.VisualStudio.CommandBars
-DartifactId=Microsoft.VisualStudio.CommandBars -Dversion=8.0.0.0
-Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file
-DgroupId=Microsoft.VisualStudio.CommandBars
-DartifactId=Microsoft.VisualStudio.CommandBars -Dversion=8.0.0.0
-Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) npanday:dotnet-repository-builder:pom:1.3-incubating
2)
npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
3)
Microsoft.VisualStudio.CommandBars:Microsoft.VisualStudio.CommandBars:gac:b03f5f7f11d50a3a:8.0.0.0
5) EnvDTE80:EnvDTE80:gac:b03f5f7f11d50a3a:8.0.0.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=EnvDTE80 -DartifactId=EnvDTE80
-Dversion=8.0.0.0 -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=EnvDTE80 -DartifactId=EnvDTE80
-Dversion=8.0.0.0 -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) npanday:dotnet-repository-builder:pom:1.3-incubating
2)
npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
3) EnvDTE80:EnvDTE80:gac:b03f5f7f11d50a3a:8.0.0.0
6) VSLangProj:VSLangProj:gac:b03f5f7f11d50a3a:7.0.3300.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=VSLangProj
-DartifactId=VSLangProj -Dversion=7.0.3300.0
-Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=VSLangProj
-DartifactId=VSLangProj -Dversion=7.0.3300.0
-Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) npanday:dotnet-repository-builder:pom:1.3-incubating
2)
npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
3) VSLangProj:VSLangProj:gac:b03f5f7f11d50a3a:7.0.3300.0
7) VSLangProj80:VSLangProj80:gac:b03f5f7f11d50a3a:8.0.0.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=VSLangProj80
-DartifactId=VSLangProj80 -Dversion=8.0.0.0
-Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=VSLangProj80
-DartifactId=VSLangProj80 -Dversion=8.0.0.0
-Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) npanday:dotnet-repository-builder:pom:1.3-incubating
2)
npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
3) VSLangProj80:VSLangProj80:gac:b03f5f7f11d50a3a:8.0.0.0
8) Extensibility:Extensibility:gac:b03f5f7f11d50a3a:7.0.3300.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=Extensibility
-DartifactId=Extensibility -Dversion=7.0.3300.0
-Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=Extensibility
-DartifactId=Extensibility -Dversion=7.0.3300.0
-Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) npanday:dotnet-repository-builder:pom:1.3-incubating
2)
npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
3) Extensibility:Extensibility:gac:b03f5f7f11d50a3a:7.0.3300.0
----------
8 required artifacts are missing.
for artifact:
npanday:dotnet-repository-builder:pom:1.3-incubating
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
internal (http://xxx/archiva/repository/internal),
npanday (http://xxx/archiva/repository/npanday),
aduna.org (http://repository.aduna-software.org/maven2),
snapshots (http://repo.mdh.se/archiva/repository/snapshots),
npanday.repo.1 (http://xxx/archiva/repository/internal/),
npanday.repo.0 (http://xxx/archiva/repository/internal),
npanday.releases
(http://repo.npanday.org/archiva/repository/npanday-releases),
npanday.3rdparty (http://repo.npanday.org/archiva/repository/3rdparty),
apache.snapshots (http://repository.apache.org/snapshots)
--
Dennis Lundberg
Re: [VOTE] NPANDAY Version 1.3 Incubating
Posted by Lars Corneliussen <me...@lcorneliussen.de>.
both 3 and 4 should be fixed on trunk
--
Message sent from mobile device
Am 02.03.2011 um 18:47 schrieb Dennis Lundberg <de...@apache.org>:
> On 2011-02-28 20:43, Dennis Lundberg wrote:
>> On 2011-02-27 16:04, Dennis Lundberg wrote:
>>> Hi
>>>
>>> First off - sorry for the long delay. I didn't realize that I was
>>> supposed to vote.
>>>
>>> I've checked the signatures and checksums of the staged artifacts, and
>>> they are all fine.
>>>
>>> I tried to build the source bundle, but didn't get very far because the
>>> npanday repo seems to be down, as Lars noted in related thread.
>>
>> Now that the repo is back up again I got a lot further - all the way to
>> "NPanday :: .NET Model :: POM". There the build fails, as expected,
>> because I don't have Visual Studio (or its tools) installed.
>>
>> Will hopefully have time to try building on another machine tomorrow.
>
> Now I've done enough testing to give this release my +1 vote.
>
> Installation from msi package works fine.
>
>
>
> A couple of things that we have run into during testing, that can be
> fixed in later versions. These were all found running on Windows 7 64-bit.
>
> 1. We were not able to build from the source bundle all the way to the
> end. This was on a machine with VS2008 and VS2010 installed. See log
> file at the end of this message. The build fails in the module "NPanday
> :: Repository Builder".
>
> 2. Some interdependency between different modules is standing in the way
> of doing 'mvn clean verify' on a machine without any npanday
> 1.3-incubating artifacts in the local repo. One must run 'mvn clean
> install' instead. This is caused by a bug in Maven 2, which has been
> fixed in Maven 3.
>
> 3. Building with Maven 3 fails on one of the modules related to the
> lifecycle. Sorry, don't remember which one now. I think Lars already has
> done some work to fix this on trunk.
>
> 4. Running a 'mvn verify' that failed halfway through, and after that
> running 'mvn verify' again (without mvn clean in between) fails with an
> error saying that a mkdir command failed.
>
> 5. We ran into the 260 char max path length issue with the source bundle
> unpacked in the users home directory. Moving the sources to the root
> directory solved this.
>
>
>
> The log from the failed build under 1.
>
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) VsWebSite.Interop:VsWebSite.Interop:gac:b03f5f7f11d50a3a:8.0.0.0
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=VsWebSite.Interop
> -DartifactId=VsWebSite.Interop -Dversion=8.0.0.0
> -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=VsWebSite.Interop
> -DartifactId=VsWebSite.Interop -Dversion=8.0.0.0
> -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) npanday:dotnet-repository-builder:pom:1.3-incubating
> 2)
> npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
> 3) VsWebSite.Interop:VsWebSite.Interop:gac:b03f5f7f11d50a3a:8.0.0.0
>
> 2) EnvDTE:EnvDTE:gac:b03f5f7f11d50a3a:8.0.0.0
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=EnvDTE -DartifactId=EnvDTE
> -Dversion=8.0.0.0 -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=EnvDTE -DartifactId=EnvDTE
> -Dversion=8.0.0.0 -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac
> -Dfile=/path/to/file-Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) npanday:dotnet-repository-builder:pom:1.3-incubating
> 2) npanday.visualstudio:NPanday.VisualStudio:library:1.3-incubating
> 3) EnvDTE:EnvDTE:gac:b03f5f7f11d50a3a:8.0.0.0
>
> 3)
> Microsoft.Build.Engine:Microsoft.Build.Engine:gac_msil:b03f5f7f11d50a3a:2.0.0.0
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=Microsoft.Build.Engine
> -DartifactId=Microsoft.Build.Engine -Dversion=2.0.0.0
> -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac_msil -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=Microsoft.Build.Engine
> -DartifactId=Microsoft.Build.Engine -Dversion=2.0.0.0
> -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac_msil -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) npanday:dotnet-repository-builder:pom:1.3-incubating
> 2)
> npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
> 3)
> npanday.projectimporter:NPanday.ProjectImporterEngine:library:1.3-incubating
> 4)
> Microsoft.Build.Engine:Microsoft.Build.Engine:gac_msil:b03f5f7f11d50a3a:2.0.0.0
>
> 4)
> Microsoft.VisualStudio.CommandBars:Microsoft.VisualStudio.CommandBars:gac:b03f5f7f11d50a3a:8.0.0.0
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file
> -DgroupId=Microsoft.VisualStudio.CommandBars
> -DartifactId=Microsoft.VisualStudio.CommandBars -Dversion=8.0.0.0
> -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file
> -DgroupId=Microsoft.VisualStudio.CommandBars
> -DartifactId=Microsoft.VisualStudio.CommandBars -Dversion=8.0.0.0
> -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) npanday:dotnet-repository-builder:pom:1.3-incubating
> 2)
> npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
> 3)
> Microsoft.VisualStudio.CommandBars:Microsoft.VisualStudio.CommandBars:gac:b03f5f7f11d50a3a:8.0.0.0
>
> 5) EnvDTE80:EnvDTE80:gac:b03f5f7f11d50a3a:8.0.0.0
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=EnvDTE80 -DartifactId=EnvDTE80
> -Dversion=8.0.0.0 -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=EnvDTE80 -DartifactId=EnvDTE80
> -Dversion=8.0.0.0 -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) npanday:dotnet-repository-builder:pom:1.3-incubating
> 2)
> npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
> 3) EnvDTE80:EnvDTE80:gac:b03f5f7f11d50a3a:8.0.0.0
>
> 6) VSLangProj:VSLangProj:gac:b03f5f7f11d50a3a:7.0.3300.0
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=VSLangProj
> -DartifactId=VSLangProj -Dversion=7.0.3300.0
> -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=VSLangProj
> -DartifactId=VSLangProj -Dversion=7.0.3300.0
> -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) npanday:dotnet-repository-builder:pom:1.3-incubating
> 2)
> npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
> 3) VSLangProj:VSLangProj:gac:b03f5f7f11d50a3a:7.0.3300.0
>
> 7) VSLangProj80:VSLangProj80:gac:b03f5f7f11d50a3a:8.0.0.0
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=VSLangProj80
> -DartifactId=VSLangProj80 -Dversion=8.0.0.0
> -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=VSLangProj80
> -DartifactId=VSLangProj80 -Dversion=8.0.0.0
> -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) npanday:dotnet-repository-builder:pom:1.3-incubating
> 2)
> npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
> 3) VSLangProj80:VSLangProj80:gac:b03f5f7f11d50a3a:8.0.0.0
>
> 8) Extensibility:Extensibility:gac:b03f5f7f11d50a3a:7.0.3300.0
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=Extensibility
> -DartifactId=Extensibility -Dversion=7.0.3300.0
> -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=Extensibility
> -DartifactId=Extensibility -Dversion=7.0.3300.0
> -Dclassifier=b03f5f7f11d50a3a -Dpackaging=gac -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) npanday:dotnet-repository-builder:pom:1.3-incubating
> 2)
> npanday.visualstudio:NPanday.VisualStudio.Addin:visual-studio-addin:1.3-incubating
> 3) Extensibility:Extensibility:gac:b03f5f7f11d50a3a:7.0.3300.0
>
> ----------
> 8 required artifacts are missing.
>
> for artifact:
> npanday:dotnet-repository-builder:pom:1.3-incubating
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> internal (http://xxx/archiva/repository/internal),
> npanday (http://xxx/archiva/repository/npanday),
> aduna.org (http://repository.aduna-software.org/maven2),
> snapshots (http://repo.mdh.se/archiva/repository/snapshots),
> npanday.repo.1 (http://xxx/archiva/repository/internal/),
> npanday.repo.0 (http://xxx/archiva/repository/internal),
> npanday.releases
> (http://repo.npanday.org/archiva/repository/npanday-releases),
> npanday.3rdparty (http://repo.npanday.org/archiva/repository/3rdparty),
> apache.snapshots (http://repository.apache.org/snapshots)
>
> --
> Dennis Lundberg