You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-users@incubator.apache.org by Khai Do <kh...@impinj.com> on 2011/05/03 18:08:05 UTC
using npanday to build WPF applications
Hello. I'm trying to build a Windows Presentation Foundation application using NPanday for the first time. I'm attempting to use maven 2.2.1 and npanday ver 1.3-incubating but have not getting it to work yet. It builds just fine in Visual studio 2010, but not with maven+npanday. The documentation is pretty sparse for how to create a pom.xml so I'm not sure whether my pom file is correct. Does anybody know where I can find an example pom.xml for building a WPF application? Thanks.
Re: is repo.npanday.org down?
Posted by Adelita Padilla <ap...@maestrodev.com>.
Hi Khai,
The repo's already up but it's still unstable though.
Thanks,
--
liit
On Tue, May 10, 2011 at 9:55 AM, Adelita Padilla <ap...@maestrodev.com>wrote:
>
> Hi Khai,
>
>
> We are looking into this and we'll keep you posted once the repos are up.
>
>
> Thanks,
>
> --
>
> liit
>
>
> On Tue, May 10, 2011 at 2:48 AM, Khai Do <kh...@impinj.com> wrote:
>
>> Hi. Does anybody know what happened to the npanday repository? I just
>> noticed that
>> http://repo.npanday.org/archiva/repository/npanday-snapshots/ and
>> http://repo.npanday.org/archiva/repository/npanday-group/ are no longer
>> alive.
>>
>>
>>
>>
>
Re: is repo.npanday.org down?
Posted by Adelita Padilla <ap...@maestrodev.com>.
Hi Khai,
We are looking into this and we'll keep you posted once the repos are up.
Thanks,
--
liit
On Tue, May 10, 2011 at 2:48 AM, Khai Do <kh...@impinj.com> wrote:
> Hi. Does anybody know what happened to the npanday repository? I just
> noticed that http://repo.npanday.org/archiva/repository/npanday-snapshots/ and
> http://repo.npanday.org/archiva/repository/npanday-group/ are no longer
> alive.
>
>
>
>
is repo.npanday.org down?
Posted by Khai Do <kh...@impinj.com>.
Hi. Does anybody know what happened to the npanday repository? I just noticed that http://repo.npanday.org/archiva/repository/npanday-snapshots/ and http://repo.npanday.org/archiva/repository/npanday-group/ are no longer alive.
Re: Trouble Getting Going with 1.4.0
Posted by Josimpson Ocaba <jo...@maestrodev.com>.
Is your local repository set to the Maven Default? <UserProfile>/.m2/ ?
There are extra procedures you have to make if this is the case.
Thanks,
Re: Trouble Getting Going with 1.4.0
Posted by Eric Kolotyluk <er...@gmail.com>.
Please see below...
On 2011-05-09 8:29 AM, Lars Corneliussen wrote:
> Please see below.
>
> Am 09.05.11 17:06, schrieb Eric Kolotyluk:
>> Please see below.
>>
>> On 2011-05-09 1:55 AM, Lars Corneliussen wrote:
>>> Am 09.05.11 05:00, schrieb Eric Kolotyluk:
>>>> OK, I added
>>>>
>>>> <dependency>
>>>> <groupId>log4net</groupId>
>>>> <artifactId>log4net</artifactId>
>>>> <version>1.2.10.0-SNAPSHOT</version>
>>>> <name>Log for .Net</name>
>>>> </dependency>
>>> Just interested: Where is this dependency located? Do we have it
>>> uploaded somewhere? Did you build and upload it somewhere?
>> I have no idea where this is located - I thought the point of Maven
>> and having a central repository was I should not have to care.
>>
>> I took the XML from some place I found on a Google search, hoping
>> that if someone else had used it, then it might work for me.
> This is years ago :-)
> http://maven.40175.n5.nabble.com/How-to-make-manual-artifacts-using-classifiers-td328342.html
>
> We do not maintain a repository with all open source artifacts, like
> Maven Central. This had to be done by each individual project, as it
> is been done in Java.
>
> Again, adoption is not broad enough.
>
> So we find ourselves deploying things we need in our private
> enterprise repository (Archiva, Artifactory or Nexus). Then we can
> decide ourselves on group ids, e.g.
>
> Visual Studio/MS just released Nuget, which already has quite some
> libs online. It also comes with dependency management. We plan to
> integrate with the nuget Gallery in some future version. (like
> Sonatype Tycho integrates with Eclipse p2-Repos)
>
OK, I'm beginning to understand - I have been spoiled by m2e and Java ;-)
I need to lower my expectations until the .NET world catches up.
So, in the mean time it's up to me to find other people who have
repositories I can tap into? Fair enough, I've had to do that a few
times with Maven. Unfortunately I have not been able to find a Maven
repository (via Google) for log4net, at least it seems Apache don't have
one. Does anyone have any advice on how to find external repositories
for .NET artifacts (i.e. DLLs)?
>>>>
>>>> to my POM, but if I try to do a build I get
>>>>
>>>> Error in Starting Maven Process: Value cannot be null.
>>>> Parameter name: path1
>>> Could you provide a stack trace?
>>
>> Where would I find the stack trace?
>>
>> By the way, whenever I start Visual Studio I keep getting the
>> following message
>>
>>
> I have seen that before, but I can't remember what the reason was.
> Maybe /_*Joe or liit*_/ can help?
OK, hopefully someone will respond. It's a little frustrating that I
cant' even get a simple build to work.
>>>>
>>>> I still cannot believe how hard this is to get working.
>>>>
>>>> Does anyone have any ideas on what I should try next.
>>>>
>>>> Cheers, Eric
>>>>
>>>>
>>>> On 2011-05-08 7:32 PM, Eric Kolotyluk wrote:
>>>>> Please see below...
>>>>>
>>>>> On 2011-05-08 7:22 PM, Adelita Padilla wrote:
>>>>>>
>>>>>> Hi Eric,
>>>>>>
>>>>>>
>>>>>> On Mon, May 9, 2011 at 10:00 AM, Eric Kolotyluk
>>>>>> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> OK, there was no settings.xml in my ~/.m2 so I added the
>>>>>> default one.
>>>>>>
>>>>>> I have been using Maven and m2e for months never needing to do
>>>>>> that, so I don't understand why NPanday needs it there? I would
>>>>>> consider that a bug.
>>>>>>
>>>>>> Now when I try to add an artifact it complains
>>>>>>
>>>>>>
>>>>>>
>>>>>> How am I supposed to know where that is?
>>>>>>
>>>>>>
>>>>>>
>>>>>> You can add that dependency by configuring the remote
>>>>>> repository. Here's the documentation for that ->
>>>>>> http://incubator.apache.org/npanday/docs/1.4.0-incubating/guide/vs/configureRepository.html
>>>>>>
>>>>> Yes, I found that page already, but it does not give me a URL for
>>>>> any remote repositories. How am I supposed to know where they are?
>>>>>
>>>>> For example, how am I supposed to know how to find log4net?
>>>>>>
>>>>>>
>>>>>> I've been struggling with NPanday for hours just because I want
>>>>>> to try to add a dependency to log4net, and I still cannot see
>>>>>> any
>>>>>> light at the end of the tunnel.
>>>>>>
>>>>>> It is so much easier to use the Sonatype plugin for Eclipse.
>>>>>>
>>>>>> By the way, the file
>>>>>> npanday-repository-builder-1.4.0-incubating-bin.tar.gz had no
>>>>>> npanday directory in it, so I'm using the one from the 1.3.1
>>>>>> release.
>>>>>>
>>>>>>
>>>>>>
>>>>>> The npanday directory is located in
>>>>>> /repository/releases/org/apache/npanday.
>>>>>>
>>>>>>
>>>>> Ahhhh, that's different than 1.3.1. Thanks.
>>>>>
>>>>>>
>>>>>> Cheers, Eric
>>>>>>
>>>>>>
>>>>>> On 2011-05-08 6:37 PM, Deng Ching wrote:
>>>>>>> Hi Eric,
>>>>>>>
>>>>>>> The message from the pop-up was just a warning, so you should
>>>>>>> still be able to add an artifact. What happens afterwards when
>>>>>>> you click OK?
>>>>>>>
>>>>>>> The settings.xml file btw, is a configuration file used by
>>>>>>> Maven
>>>>>>> where you can set the repositories that you want Maven to look
>>>>>>> for artifacts/dependencies of your project when you build
>>>>>>> it. It
>>>>>>> is also used by NPanday in a similar way during project import,
>>>>>>> artifact re-sync and when building your project.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Deng
>>>>>>>
>>>>>>> On Mon, May 9, 2011 at 9:23 AM, Eric Kolotyluk
>>>>>>> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>> I used
>>>>>>>
>>>>>>> *
>>>>>>> npanday-repository-builder-1.4.0-incubating-bin.tar.gz
>>>>>>> * npanday-installer-1.4.0-incubating.msi
>>>>>>>
>>>>>>> to set up NPanday, and I was able to set up my POMs ok.
>>>>>>>
>>>>>>> I'm trying to get NPanday to work with Visual Studio 2010,
>>>>>>> but when I try to add and artifact I get
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Does anyone have any ideas on how to fix this?
>>>>>>>
>>>>>>> Cheers, Eric
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> --
>>>>>>
>>>>>> liit
>>>>
>>>
>
Re: Trouble Getting Going with 1.4.0
Posted by Lars Corneliussen <me...@lcorneliussen.de>.
Please see below.
Am 09.05.11 17:06, schrieb Eric Kolotyluk:
> Please see below.
>
> On 2011-05-09 1:55 AM, Lars Corneliussen wrote:
>> Am 09.05.11 05:00, schrieb Eric Kolotyluk:
>>> OK, I added
>>>
>>> <dependency>
>>> <groupId>log4net</groupId>
>>> <artifactId>log4net</artifactId>
>>> <version>1.2.10.0-SNAPSHOT</version>
>>> <name>Log for .Net</name>
>>> </dependency>
>> Just interested: Where is this dependency located? Do we have it
>> uploaded somewhere? Did you build and upload it somewhere?
> I have no idea where this is located - I thought the point of Maven
> and having a central repository was I should not have to care.
>
> I took the XML from some place I found on a Google search, hoping that
> if someone else had used it, then it might work for me.
This is years ago :-)
http://maven.40175.n5.nabble.com/How-to-make-manual-artifacts-using-classifiers-td328342.html
We do not maintain a repository with all open source artifacts, like
Maven Central. This had to be done by each individual project, as it is
been done in Java.
Again, adoption is not broad enough.
So we find ourselves deploying things we need in our private enterprise
repository (Archiva, Artifactory or Nexus). Then we can decide ourselves
on group ids, e.g.
Visual Studio/MS just released Nuget, which already has quite some libs
online. It also comes with dependency management. We plan to integrate
with the nuget Gallery in some future version. (like Sonatype Tycho
integrates with Eclipse p2-Repos)
>>>
>>> to my POM, but if I try to do a build I get
>>>
>>> Error in Starting Maven Process: Value cannot be null.
>>> Parameter name: path1
>> Could you provide a stack trace?
>
> Where would I find the stack trace?
>
> By the way, whenever I start Visual Studio I keep getting the
> following message
>
>
I have seen that before, but I can't remember what the reason was. Maybe
/_*Joe or liit*_/ can help?
>>>
>>> I still cannot believe how hard this is to get working.
>>>
>>> Does anyone have any ideas on what I should try next.
>>>
>>> Cheers, Eric
>>>
>>>
>>> On 2011-05-08 7:32 PM, Eric Kolotyluk wrote:
>>>> Please see below...
>>>>
>>>> On 2011-05-08 7:22 PM, Adelita Padilla wrote:
>>>>>
>>>>> Hi Eric,
>>>>>
>>>>>
>>>>> On Mon, May 9, 2011 at 10:00 AM, Eric Kolotyluk
>>>>> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> OK, there was no settings.xml in my ~/.m2 so I added the
>>>>> default one.
>>>>>
>>>>> I have been using Maven and m2e for months never needing to do
>>>>> that, so I don't understand why NPanday needs it there? I would
>>>>> consider that a bug.
>>>>>
>>>>> Now when I try to add an artifact it complains
>>>>>
>>>>>
>>>>>
>>>>> How am I supposed to know where that is?
>>>>>
>>>>>
>>>>>
>>>>> You can add that dependency by configuring the remote repository.
>>>>> Here's the documentation for that ->
>>>>> http://incubator.apache.org/npanday/docs/1.4.0-incubating/guide/vs/configureRepository.html
>>>>>
>>>> Yes, I found that page already, but it does not give me a URL for
>>>> any remote repositories. How am I supposed to know where they are?
>>>>
>>>> For example, how am I supposed to know how to find log4net?
>>>>>
>>>>>
>>>>> I've been struggling with NPanday for hours just because I want
>>>>> to try to add a dependency to log4net, and I still cannot see any
>>>>> light at the end of the tunnel.
>>>>>
>>>>> It is so much easier to use the Sonatype plugin for Eclipse.
>>>>>
>>>>> By the way, the file
>>>>> npanday-repository-builder-1.4.0-incubating-bin.tar.gz had no
>>>>> npanday directory in it, so I'm using the one from the 1.3.1
>>>>> release.
>>>>>
>>>>>
>>>>>
>>>>> The npanday directory is located in
>>>>> /repository/releases/org/apache/npanday.
>>>>>
>>>>>
>>>> Ahhhh, that's different than 1.3.1. Thanks.
>>>>
>>>>>
>>>>> Cheers, Eric
>>>>>
>>>>>
>>>>> On 2011-05-08 6:37 PM, Deng Ching wrote:
>>>>>> Hi Eric,
>>>>>>
>>>>>> The message from the pop-up was just a warning, so you should
>>>>>> still be able to add an artifact. What happens afterwards when
>>>>>> you click OK?
>>>>>>
>>>>>> The settings.xml file btw, is a configuration file used by Maven
>>>>>> where you can set the repositories that you want Maven to look
>>>>>> for artifacts/dependencies of your project when you build it. It
>>>>>> is also used by NPanday in a similar way during project import,
>>>>>> artifact re-sync and when building your project.
>>>>>>
>>>>>> Thanks,
>>>>>> Deng
>>>>>>
>>>>>> On Mon, May 9, 2011 at 9:23 AM, Eric Kolotyluk
>>>>>> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> I used
>>>>>>
>>>>>> * npanday-repository-builder-1.4.0-incubating-bin.tar.gz
>>>>>> * npanday-installer-1.4.0-incubating.msi
>>>>>>
>>>>>> to set up NPanday, and I was able to set up my POMs ok.
>>>>>>
>>>>>> I'm trying to get NPanday to work with Visual Studio 2010,
>>>>>> but when I try to add and artifact I get
>>>>>>
>>>>>>
>>>>>>
>>>>>> Does anyone have any ideas on how to fix this?
>>>>>>
>>>>>> Cheers, Eric
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> --
>>>>>
>>>>> liit
>>>
>>
Re: Trouble Getting Going with 1.4.0
Posted by Eric Kolotyluk <er...@gmail.com>.
Please see below.
On 2011-05-09 1:55 AM, Lars Corneliussen wrote:
> Am 09.05.11 05:00, schrieb Eric Kolotyluk:
>> OK, I added
>>
>> <dependency>
>> <groupId>log4net</groupId>
>> <artifactId>log4net</artifactId>
>> <version>1.2.10.0-SNAPSHOT</version>
>> <name>Log for .Net</name>
>> </dependency>
> Just interested: Where is this dependency located? Do we have it
> uploaded somewhere? Did you build and upload it somewhere?
I have no idea where this is located - I thought the point of Maven and
having a central repository was I should not have to care.
I took the XML from some place I found on a Google search, hoping that
if someone else had used it, then it might work for me.
>>
>> to my POM, but if I try to do a build I get
>>
>> Error in Starting Maven Process: Value cannot be null.
>> Parameter name: path1
> Could you provide a stack trace?
Where would I find the stack trace?
By the way, whenever I start Visual Studio I keep getting the following
message
>>
>> I still cannot believe how hard this is to get working.
>>
>> Does anyone have any ideas on what I should try next.
>>
>> Cheers, Eric
>>
>>
>> On 2011-05-08 7:32 PM, Eric Kolotyluk wrote:
>>> Please see below...
>>>
>>> On 2011-05-08 7:22 PM, Adelita Padilla wrote:
>>>>
>>>> Hi Eric,
>>>>
>>>>
>>>> On Mon, May 9, 2011 at 10:00 AM, Eric Kolotyluk
>>>> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> OK, there was no settings.xml in my ~/.m2 so I added the
>>>> default one.
>>>>
>>>> I have been using Maven and m2e for months never needing to do
>>>> that, so I don't understand why NPanday needs it there? I would
>>>> consider that a bug.
>>>>
>>>> Now when I try to add an artifact it complains
>>>>
>>>>
>>>>
>>>> How am I supposed to know where that is?
>>>>
>>>>
>>>>
>>>> You can add that dependency by configuring the remote repository.
>>>> Here's the documentation for that ->
>>>> http://incubator.apache.org/npanday/docs/1.4.0-incubating/guide/vs/configureRepository.html
>>>>
>>> Yes, I found that page already, but it does not give me a URL for
>>> any remote repositories. How am I supposed to know where they are?
>>>
>>> For example, how am I supposed to know how to find log4net?
>>>>
>>>>
>>>> I've been struggling with NPanday for hours just because I want
>>>> to try to add a dependency to log4net, and I still cannot see any
>>>> light at the end of the tunnel.
>>>>
>>>> It is so much easier to use the Sonatype plugin for Eclipse.
>>>>
>>>> By the way, the file
>>>> npanday-repository-builder-1.4.0-incubating-bin.tar.gz had no
>>>> npanday directory in it, so I'm using the one from the 1.3.1
>>>> release.
>>>>
>>>>
>>>>
>>>> The npanday directory is located in
>>>> /repository/releases/org/apache/npanday.
>>>>
>>>>
>>> Ahhhh, that's different than 1.3.1. Thanks.
>>>
>>>>
>>>> Cheers, Eric
>>>>
>>>>
>>>> On 2011-05-08 6:37 PM, Deng Ching wrote:
>>>>> Hi Eric,
>>>>>
>>>>> The message from the pop-up was just a warning, so you should
>>>>> still be able to add an artifact. What happens afterwards when
>>>>> you click OK?
>>>>>
>>>>> The settings.xml file btw, is a configuration file used by Maven
>>>>> where you can set the repositories that you want Maven to look
>>>>> for artifacts/dependencies of your project when you build it. It
>>>>> is also used by NPanday in a similar way during project import,
>>>>> artifact re-sync and when building your project.
>>>>>
>>>>> Thanks,
>>>>> Deng
>>>>>
>>>>> On Mon, May 9, 2011 at 9:23 AM, Eric Kolotyluk
>>>>> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> I used
>>>>>
>>>>> * npanday-repository-builder-1.4.0-incubating-bin.tar.gz
>>>>> * npanday-installer-1.4.0-incubating.msi
>>>>>
>>>>> to set up NPanday, and I was able to set up my POMs ok.
>>>>>
>>>>> I'm trying to get NPanday to work with Visual Studio 2010,
>>>>> but when I try to add and artifact I get
>>>>>
>>>>>
>>>>>
>>>>> Does anyone have any ideas on how to fix this?
>>>>>
>>>>> Cheers, Eric
>>>>>
>>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> --
>>>>
>>>> liit
>>
>
Re: Trouble Getting Going with 1.4.0
Posted by Lars Corneliussen <me...@lcorneliussen.de>.
Am 09.05.11 05:00, schrieb Eric Kolotyluk:
> OK, I added
>
> <dependency>
> <groupId>log4net</groupId>
> <artifactId>log4net</artifactId>
> <version>1.2.10.0-SNAPSHOT</version>
> <name>Log for .Net</name>
> </dependency>
Just interested: Where is this dependency located? Do we have it
uploaded somewhere? Did you build and upload it somewhere?
>
> to my POM, but if I try to do a build I get
>
> Error in Starting Maven Process: Value cannot be null.
> Parameter name: path1
Could you provide a stack trace?
>
> I still cannot believe how hard this is to get working.
>
> Does anyone have any ideas on what I should try next.
>
> Cheers, Eric
>
>
> On 2011-05-08 7:32 PM, Eric Kolotyluk wrote:
>> Please see below...
>>
>> On 2011-05-08 7:22 PM, Adelita Padilla wrote:
>>>
>>> Hi Eric,
>>>
>>>
>>> On Mon, May 9, 2011 at 10:00 AM, Eric Kolotyluk
>>> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> OK, there was no settings.xml in my ~/.m2 so I added the default
>>> one.
>>>
>>> I have been using Maven and m2e for months never needing to do
>>> that, so I don't understand why NPanday needs it there? I would
>>> consider that a bug.
>>>
>>> Now when I try to add an artifact it complains
>>>
>>>
>>>
>>> How am I supposed to know where that is?
>>>
>>>
>>>
>>> You can add that dependency by configuring the remote repository.
>>> Here's the documentation for that ->
>>> http://incubator.apache.org/npanday/docs/1.4.0-incubating/guide/vs/configureRepository.html
>>>
>> Yes, I found that page already, but it does not give me a URL for any
>> remote repositories. How am I supposed to know where they are?
>>
>> For example, how am I supposed to know how to find log4net?
>>>
>>>
>>> I've been struggling with NPanday for hours just because I want
>>> to try to add a dependency to log4net, and I still cannot see any
>>> light at the end of the tunnel.
>>>
>>> It is so much easier to use the Sonatype plugin for Eclipse.
>>>
>>> By the way, the file
>>> npanday-repository-builder-1.4.0-incubating-bin.tar.gz had no
>>> npanday directory in it, so I'm using the one from the 1.3.1
>>> release.
>>>
>>>
>>>
>>> The npanday directory is located in
>>> /repository/releases/org/apache/npanday.
>>>
>>>
>> Ahhhh, that's different than 1.3.1. Thanks.
>>
>>>
>>> Cheers, Eric
>>>
>>>
>>> On 2011-05-08 6:37 PM, Deng Ching wrote:
>>>> Hi Eric,
>>>>
>>>> The message from the pop-up was just a warning, so you should
>>>> still be able to add an artifact. What happens afterwards when
>>>> you click OK?
>>>>
>>>> The settings.xml file btw, is a configuration file used by Maven
>>>> where you can set the repositories that you want Maven to look
>>>> for artifacts/dependencies of your project when you build it. It
>>>> is also used by NPanday in a similar way during project import,
>>>> artifact re-sync and when building your project.
>>>>
>>>> Thanks,
>>>> Deng
>>>>
>>>> On Mon, May 9, 2011 at 9:23 AM, Eric Kolotyluk
>>>> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> I used
>>>>
>>>> * npanday-repository-builder-1.4.0-incubating-bin.tar.gz
>>>> * npanday-installer-1.4.0-incubating.msi
>>>>
>>>> to set up NPanday, and I was able to set up my POMs ok.
>>>>
>>>> I'm trying to get NPanday to work with Visual Studio 2010,
>>>> but when I try to add and artifact I get
>>>>
>>>>
>>>>
>>>> Does anyone have any ideas on how to fix this?
>>>>
>>>> Cheers, Eric
>>>>
>>>>
>>>
>>>
>>> Thanks,
>>>
>>> --
>>>
>>> liit
>
Re: Trouble Getting Going with 1.4.0
Posted by Josimpson Ocaba <jo...@maestrodev.com>.
+1 on 1.4.0
Although I'd like to note that there is a build failure on building wpf
projects missing error CS0234: The type or namespace name 'Automation' does
not exist in the namespace 'System.Windows' (are you missing an assembly
reference?)
I think this could be a potential blocker since this is a regression. It
fails to build on VS2008 and VS2010 WPF project types.
We could open this on a different issue and note it as a regression and work
on it on the next follow up release.
Thanks,
Trouble Getting Going with 1.4.0 - Change Maven settings.xml
Posted by Eric Kolotyluk <er...@gmail.com>.
OK, when I click the Browse button - nothing happens. The dialog just
disappears.
Cheers, Eric
Re: Trouble Getting Going with 1.4.0
Posted by Eric Kolotyluk <er...@gmail.com>.
OK, I added
<dependency>
<groupId>log4net</groupId>
<artifactId>log4net</artifactId>
<version>1.2.10.0-SNAPSHOT</version>
<name>Log for .Net</name>
</dependency>
to my POM, but if I try to do a build I get
Error in Starting Maven Process: Value cannot be null.
Parameter name: path1
I still cannot believe how hard this is to get working.
Does anyone have any ideas on what I should try next.
Cheers, Eric
On 2011-05-08 7:32 PM, Eric Kolotyluk wrote:
> Please see below...
>
> On 2011-05-08 7:22 PM, Adelita Padilla wrote:
>>
>> Hi Eric,
>>
>>
>> On Mon, May 9, 2011 at 10:00 AM, Eric Kolotyluk
>> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>>
>> OK, there was no settings.xml in my ~/.m2 so I added the default one.
>>
>> I have been using Maven and m2e for months never needing to do
>> that, so I don't understand why NPanday needs it there? I would
>> consider that a bug.
>>
>> Now when I try to add an artifact it complains
>>
>>
>>
>> How am I supposed to know where that is?
>>
>>
>>
>> You can add that dependency by configuring the remote repository.
>> Here's the documentation for that ->
>> http://incubator.apache.org/npanday/docs/1.4.0-incubating/guide/vs/configureRepository.html
>>
> Yes, I found that page already, but it does not give me a URL for any
> remote repositories. How am I supposed to know where they are?
>
> For example, how am I supposed to know how to find log4net?
>>
>>
>> I've been struggling with NPanday for hours just because I want
>> to try to add a dependency to log4net, and I still cannot see any
>> light at the end of the tunnel.
>>
>> It is so much easier to use the Sonatype plugin for Eclipse.
>>
>> By the way, the file
>> npanday-repository-builder-1.4.0-incubating-bin.tar.gz had no
>> npanday directory in it, so I'm using the one from the 1.3.1 release.
>>
>>
>>
>> The npanday directory is located in
>> /repository/releases/org/apache/npanday.
>>
>>
> Ahhhh, that's different than 1.3.1. Thanks.
>
>>
>> Cheers, Eric
>>
>>
>> On 2011-05-08 6:37 PM, Deng Ching wrote:
>>> Hi Eric,
>>>
>>> The message from the pop-up was just a warning, so you should
>>> still be able to add an artifact. What happens afterwards when
>>> you click OK?
>>>
>>> The settings.xml file btw, is a configuration file used by Maven
>>> where you can set the repositories that you want Maven to look
>>> for artifacts/dependencies of your project when you build it. It
>>> is also used by NPanday in a similar way during project import,
>>> artifact re-sync and when building your project.
>>>
>>> Thanks,
>>> Deng
>>>
>>> On Mon, May 9, 2011 at 9:23 AM, Eric Kolotyluk
>>> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> I used
>>>
>>> * npanday-repository-builder-1.4.0-incubating-bin.tar.gz
>>> * npanday-installer-1.4.0-incubating.msi
>>>
>>> to set up NPanday, and I was able to set up my POMs ok.
>>>
>>> I'm trying to get NPanday to work with Visual Studio 2010,
>>> but when I try to add and artifact I get
>>>
>>>
>>>
>>> Does anyone have any ideas on how to fix this?
>>>
>>> Cheers, Eric
>>>
>>>
>>
>>
>> Thanks,
>>
>> --
>>
>> liit
Re: Trouble Getting Going with 1.4.0
Posted by Eric Kolotyluk <er...@gmail.com>.
Please see below...
On 2011-05-08 7:22 PM, Adelita Padilla wrote:
>
> Hi Eric,
>
>
> On Mon, May 9, 2011 at 10:00 AM, Eric Kolotyluk
> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>
> OK, there was no settings.xml in my ~/.m2 so I added the default one.
>
> I have been using Maven and m2e for months never needing to do
> that, so I don't understand why NPanday needs it there? I would
> consider that a bug.
>
> Now when I try to add an artifact it complains
>
>
>
> How am I supposed to know where that is?
>
>
>
> You can add that dependency by configuring the remote repository.
> Here's the documentation for that ->
> http://incubator.apache.org/npanday/docs/1.4.0-incubating/guide/vs/configureRepository.html
>
Yes, I found that page already, but it does not give me a URL for any
remote repositories. How am I supposed to know where they are?
For example, how am I supposed to know how to find log4net?
>
>
> I've been struggling with NPanday for hours just because I want to
> try to add a dependency to log4net, and I still cannot see any
> light at the end of the tunnel.
>
> It is so much easier to use the Sonatype plugin for Eclipse.
>
> By the way, the file
> npanday-repository-builder-1.4.0-incubating-bin.tar.gz had no
> npanday directory in it, so I'm using the one from the 1.3.1 release.
>
>
>
> The npanday directory is located in
> /repository/releases/org/apache/npanday.
>
>
Ahhhh, that's different than 1.3.1. Thanks.
>
> Cheers, Eric
>
>
> On 2011-05-08 6:37 PM, Deng Ching wrote:
>> Hi Eric,
>>
>> The message from the pop-up was just a warning, so you should
>> still be able to add an artifact. What happens afterwards when
>> you click OK?
>>
>> The settings.xml file btw, is a configuration file used by Maven
>> where you can set the repositories that you want Maven to look
>> for artifacts/dependencies of your project when you build it. It
>> is also used by NPanday in a similar way during project import,
>> artifact re-sync and when building your project.
>>
>> Thanks,
>> Deng
>>
>> On Mon, May 9, 2011 at 9:23 AM, Eric Kolotyluk
>> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>>
>> I used
>>
>> * npanday-repository-builder-1.4.0-incubating-bin.tar.gz
>> * npanday-installer-1.4.0-incubating.msi
>>
>> to set up NPanday, and I was able to set up my POMs ok.
>>
>> I'm trying to get NPanday to work with Visual Studio 2010,
>> but when I try to add and artifact I get
>>
>>
>>
>> Does anyone have any ideas on how to fix this?
>>
>> Cheers, Eric
>>
>>
>
>
> Thanks,
>
> --
>
> liit
Re: Trouble Getting Going with 1.4.0
Posted by Adelita Padilla <ap...@maestrodev.com>.
Hi Eric,
On Mon, May 9, 2011 at 10:00 AM, Eric Kolotyluk <er...@gmail.com>wrote:
> OK, there was no settings.xml in my ~/.m2 so I added the default one.
>
> I have been using Maven and m2e for months never needing to do that, so I
> don't understand why NPanday needs it there? I would consider that a bug.
>
> Now when I try to add an artifact it complains
>
>
>
> How am I supposed to know where that is?
>
You can add that dependency by configuring the remote repository. Here's
the documentation for that ->
http://incubator.apache.org/npanday/docs/1.4.0-incubating/guide/vs/configureRepository.html
>
> I've been struggling with NPanday for hours just because I want to try to
> add a dependency to log4net, and I still cannot see any light at the end of
> the tunnel.
>
> It is so much easier to use the Sonatype plugin for Eclipse.
>
> By the way, the file npanday-repository-builder-1.4.0-incubating-bin.tar.gz
> had no npanday directory in it, so I'm using the one from the 1.3.1 release.
>
The npanday directory is located in /repository/releases/org/apache/npanday.
>
> Cheers, Eric
>
>
> On 2011-05-08 6:37 PM, Deng Ching wrote:
>
> Hi Eric,
>
> The message from the pop-up was just a warning, so you should still be
> able to add an artifact. What happens afterwards when you click OK?
>
> The settings.xml file btw, is a configuration file used by Maven where
> you can set the repositories that you want Maven to look for
> artifacts/dependencies of your project when you build it. It is also used by
> NPanday in a similar way during project import, artifact re-sync and when
> building your project.
>
> Thanks,
> Deng
>
> On Mon, May 9, 2011 at 9:23 AM, Eric Kolotyluk <er...@gmail.com>wrote:
>
>> I used
>>
>> - npanday-repository-builder-1.4.0-incubating-bin.tar.gz
>> - npanday-installer-1.4.0-incubating.msi
>>
>> to set up NPanday, and I was able to set up my POMs ok.
>>
>> I'm trying to get NPanday to work with Visual Studio 2010, but when I try
>> to add and artifact I get
>>
>>
>>
>> Does anyone have any ideas on how to fix this?
>>
>> Cheers, Eric
>>
>
>
Thanks,
--
liit
Re: Trouble Getting Going with 1.4.0
Posted by Eric Kolotyluk <er...@gmail.com>.
Please see below...
On 2011-05-09 1:54 AM, Lars Corneliussen wrote:
> Hi Eric,
>>
>> I've been struggling with NPanday for hours just because I want to
>> try to add a dependency to log4net, and I still cannot see any light
>> at the end of the tunnel.
>>
>> It is so much easier to use the Sonatype plugin for Eclipse.
>>
>
> I'm really sorry for the trouble you encounter. And we appreciate your
> interest in NPanday.
>
> Though, you can't really compare NPanday and Visual Studio with Maven
> and Eclipse (yet). Allthough NPanday is in use by many, it is far from
> the broad adoption Maven has in the Java space. Hopefully this will
> not stay like it is. That is, what we work for.
>
> Especially the NPanday VS Add-in serves very specific tasks (Project
> import, Reference sync). We hope to engage more users, contributors
> and committers to help us build a better NPanday.
>
> I personally joined the project in late 2010, because I belive this is
> the way to go for building in .NET. But we have still much work to do.
>
> So far, it's been worth it.
Truly I see the value in NPanday, and I understand it's bleeding edge
technology at the moment. It's just that I'm tired and frustrated after
so many hours of trying to get it working. I would really appreciate it
if someone could get me to the point of being able to bring just one
dependency into my project, preferably log4net.
I do agree with you that this is the way to go with .NET, so please keep
working to improve NPanday and some-day I hope it will be as easy to use
as m2e.
>> By the way, the file
>> npanday-repository-builder-1.4.0-incubating-bin.tar.gz had no npanday
>> directory in it, so I'm using the one from the 1.3.1 release.
> As liit already mentioned, we changed the group id to
> org.apache.npanday. This change was nessecary in order to comply with
> apache rules and to get npanday into Maven Central.
NP - it was just confusing for me as I was struggling to understand why
I could not get things working properly.
>>
>> Cheers, Eric
>>
>> On 2011-05-08 6:37 PM, Deng Ching wrote:
>>> Hi Eric,
>>>
>>> The message from the pop-up was just a warning, so you should still
>>> be able to add an artifact. What happens afterwards when you click OK?
>>>
>>> The settings.xml file btw, is a configuration file used by Maven
>>> where you can set the repositories that you want Maven to look for
>>> artifacts/dependencies of your project when you build it. It is also
>>> used by NPanday in a similar way during project import, artifact
>>> re-sync and when building your project.
>>>
>>> Thanks,
>>> Deng
>>>
>>> On Mon, May 9, 2011 at 9:23 AM, Eric Kolotyluk
>>> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> I used
>>>
>>> * npanday-repository-builder-1.4.0-incubating-bin.tar.gz
>>> * npanday-installer-1.4.0-incubating.msi
>>>
>>> to set up NPanday, and I was able to set up my POMs ok.
>>>
>>> I'm trying to get NPanday to work with Visual Studio 2010, but
>>> when I try to add and artifact I get
>>>
>>>
>>>
>>> Does anyone have any ideas on how to fix this?
>>>
>>> Cheers, Eric
>>>
>>>
>
>
Re: Trouble Getting Going with 1.4.0
Posted by Lars Corneliussen <me...@lcorneliussen.de>.
Hi Eric,
>
> I've been struggling with NPanday for hours just because I want to try
> to add a dependency to log4net, and I still cannot see any light at
> the end of the tunnel.
>
> It is so much easier to use the Sonatype plugin for Eclipse.
>
I'm really sorry for the trouble you encounter. And we appreciate your
interest in NPanday.
Though, you can't really compare NPanday and Visual Studio with Maven
and Eclipse (yet). Allthough NPanday is in use by many, it is far from
the broad adoption Maven has in the Java space. Hopefully this will not
stay like it is. That is, what we work for.
Especially the NPanday VS Add-in serves very specific tasks (Project
import, Reference sync). We hope to engage more users, contributors and
committers to help us build a better NPanday.
I personally joined the project in late 2010, because I belive this is
the way to go for building in .NET. But we have still much work to do.
So far, it's been worth it.
> By the way, the file
> npanday-repository-builder-1.4.0-incubating-bin.tar.gz had no npanday
> directory in it, so I'm using the one from the 1.3.1 release.
As liit already mentioned, we changed the group id to
org.apache.npanday. This change was nessecary in order to comply with
apache rules and to get npanday into Maven Central.
>
> Cheers, Eric
>
> On 2011-05-08 6:37 PM, Deng Ching wrote:
>> Hi Eric,
>>
>> The message from the pop-up was just a warning, so you should still
>> be able to add an artifact. What happens afterwards when you click OK?
>>
>> The settings.xml file btw, is a configuration file used by Maven
>> where you can set the repositories that you want Maven to look for
>> artifacts/dependencies of your project when you build it. It is also
>> used by NPanday in a similar way during project import, artifact
>> re-sync and when building your project.
>>
>> Thanks,
>> Deng
>>
>> On Mon, May 9, 2011 at 9:23 AM, Eric Kolotyluk
>> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>>
>> I used
>>
>> * npanday-repository-builder-1.4.0-incubating-bin.tar.gz
>> * npanday-installer-1.4.0-incubating.msi
>>
>> to set up NPanday, and I was able to set up my POMs ok.
>>
>> I'm trying to get NPanday to work with Visual Studio 2010, but
>> when I try to add and artifact I get
>>
>>
>>
>> Does anyone have any ideas on how to fix this?
>>
>> Cheers, Eric
>>
>>
Re: Trouble Getting Going with 1.4.0
Posted by Eric Kolotyluk <er...@gmail.com>.
OK, there was no settings.xml in my ~/.m2 so I added the default one.
I have been using Maven and m2e for months never needing to do that, so
I don't understand why NPanday needs it there? I would consider that a bug.
Now when I try to add an artifact it complains
How am I supposed to know where that is?
I've been struggling with NPanday for hours just because I want to try
to add a dependency to log4net, and I still cannot see any light at the
end of the tunnel.
It is so much easier to use the Sonatype plugin for Eclipse.
By the way, the file
npanday-repository-builder-1.4.0-incubating-bin.tar.gz had no npanday
directory in it, so I'm using the one from the 1.3.1 release.
Cheers, Eric
On 2011-05-08 6:37 PM, Deng Ching wrote:
> Hi Eric,
>
> The message from the pop-up was just a warning, so you should still be
> able to add an artifact. What happens afterwards when you click OK?
>
> The settings.xml file btw, is a configuration file used by Maven where
> you can set the repositories that you want Maven to look for
> artifacts/dependencies of your project when you build it. It is also
> used by NPanday in a similar way during project import, artifact
> re-sync and when building your project.
>
> Thanks,
> Deng
>
> On Mon, May 9, 2011 at 9:23 AM, Eric Kolotyluk
> <eric.kolotyluk@gmail.com <ma...@gmail.com>> wrote:
>
> I used
>
> * npanday-repository-builder-1.4.0-incubating-bin.tar.gz
> * npanday-installer-1.4.0-incubating.msi
>
> to set up NPanday, and I was able to set up my POMs ok.
>
> I'm trying to get NPanday to work with Visual Studio 2010, but
> when I try to add and artifact I get
>
>
>
> Does anyone have any ideas on how to fix this?
>
> Cheers, Eric
>
>
Re: Trouble Getting Going with 1.4.0
Posted by Deng Ching <oc...@apache.org>.
Hi Eric,
The message from the pop-up was just a warning, so you should still be able
to add an artifact. What happens afterwards when you click OK?
The settings.xml file btw, is a configuration file used by Maven where you
can set the repositories that you want Maven to look for
artifacts/dependencies of your project when you build it. It is also used by
NPanday in a similar way during project import, artifact re-sync and when
building your project.
Thanks,
Deng
On Mon, May 9, 2011 at 9:23 AM, Eric Kolotyluk <er...@gmail.com>wrote:
> I used
>
> - npanday-repository-builder-1.4.0-incubating-bin.tar.gz
> - npanday-installer-1.4.0-incubating.msi
>
> to set up NPanday, and I was able to set up my POMs ok.
>
> I'm trying to get NPanday to work with Visual Studio 2010, but when I try
> to add and artifact I get
>
>
>
> Does anyone have any ideas on how to fix this?
>
> Cheers, Eric
>
Trouble Getting Going with 1.4.0
Posted by Eric Kolotyluk <er...@gmail.com>.
I used
* npanday-repository-builder-1.4.0-incubating-bin.tar.gz
* npanday-installer-1.4.0-incubating.msi
to set up NPanday, and I was able to set up my POMs ok.
I'm trying to get NPanday to work with Visual Studio 2010, but when I
try to add and artifact I get
Does anyone have any ideas on how to fix this?
Cheers, Eric
RE: using npanday to build WPF applications
Posted by Khai Do <kh...@impinj.com>.
I rebuilt all of the POM files in my solution from Vis studio and when I run the build this time the dependency issue is no longer happening. However I am running into a problem that I've been trying to deal with for the last few weeks. I get a "Unhandled Exception: System.TypeLoadException" when building the last module, the WPF winexe module. I actually created a different post for this exact error at: http://markmail.org/message/vw4dsxlbchcknbbz
Have you run into this problem?
Re: using npanday to build WPF applications
Posted by Josimpson Ocaba <jo...@maestrodev.com>.
How was that dependency added? Can you post the dependency tag here. You can
also try installing the dependency library first by doing a current project
install on the dependency file and then using add maven artifact on the
project using the dependency.
Hope this helps,
Joe
On Fri, May 6, 2011 at 6:42 AM, Khai Do <kh...@impinj.com> wrote:
> Thanks for the tip Josimpson. I didn't use the VS plugin before just hand
> created the pom.xml and pointed to dependencies straight from the npanday
> repository. Now I just tried installing the npanday-1.3-incubating.msi
> installer (VS add-in + repository), generated the pom from VS 2010 then ran
> a maven build. My VS solution contains 7 projects, so it creates a
> multi-module project with a parent pom. When I run the build the first 6
> modules (all libraries) built without error and it gets installed into the
> my local repository under my home folder. When npanday attempts to build
> the last module (WPF winexe) it fails because it cannot resolve a transitive
> dependency, one of the modules that got built before this module. It seems
> to be looking in the wrong location for some reason. The build attempts to
> look in my "<local repro>/bin/Dashboard/.." folder which isn't correct
> because 'bin' isn't the groupId that was setup when the pom files were
> created. It should be something like "<local repro>/Microsoft/Dashboard/..".
> This is the actual error..
>
> Missing:
> ----------
> 1) bin:Dashboard.LlrpInterop:dotnet-library:Debug
>
> The library does exist, it's just in "<local repro>/Microsoft/Dashboard/.."
>
> Have you run into this problem with your builds?
>
>
RE: using npanday to build WPF applications
Posted by Khai Do <kh...@impinj.com>.
Thanks for the tip Josimpson. I didn't use the VS plugin before just hand created the pom.xml and pointed to dependencies straight from the npanday repository. Now I just tried installing the npanday-1.3-incubating.msi installer (VS add-in + repository), generated the pom from VS 2010 then ran a maven build. My VS solution contains 7 projects, so it creates a multi-module project with a parent pom. When I run the build the first 6 modules (all libraries) built without error and it gets installed into the my local repository under my home folder. When npanday attempts to build the last module (WPF winexe) it fails because it cannot resolve a transitive dependency, one of the modules that got built before this module. It seems to be looking in the wrong location for some reason. The build attempts to look in my "<local repro>/bin/Dashboard/.." folder which isn't correct because 'bin' isn't the groupId that was setup when the pom files were created. It should be something like "<local repro>/Microsoft/Dashboard/..". This is the actual error..
Missing:
----------
1) bin:Dashboard.LlrpInterop:dotnet-library:Debug
The library does exist, it's just in "<local repro>/Microsoft/Dashboard/.."
Have you run into this problem with your builds?
Re: using npanday to build WPF applications
Posted by Josimpson Ocaba <jo...@maestrodev.com>.
Hi Khai,
Did you use the generate pom command in Visual Studios? Looking at the pom
I'm guessing you didn't. After building the source code you can use the
command "mvn npanday.plugin:maven-vsinstaller-plugin:install" so that the
Add In well be reflected in your Visual Studios.
Then go to Tools then start up NPanday, after doing this there should be new
commands when you right click on your project. At the moment however NPanday
only supports the English Version of Visual Studios.
I'm Attaching a generated pom file in Visual Studio 2010, just make sure
that the first .net framework in the environment path is 4.0 if your
building in VS2010, there is still a bug with the msbuild plugin that only
respects the first .net framework it sees in the path.
Thanks,