Building NPanday
Hi, so I had a look at building NPanday. It was quite a hastle getting the build to run, but in the end I seem to have gotten it working. I would however suggest to modify the build slightly. There is one Problem in every plugin Project: You Need the plugin itself somewhere in the build of the rest of the plugins suilte. Unfortunately Maven doesn't respect plugins when building the reactor order of the modules and you usually get Errors about the plugin not being available in any repo ... of course ... it hasn't been built yet. The solution is usually to provide a minimal maven Profile that builds only the plugin as well as the dependencies of the plugin. So a full build from scratch usually Looks like this: mvn clean install -Pminimal mvn clean install Additionally I changed the Version of the openrdf dependencies in the module dotnet-registry to 2.0.1 and added two missing deps to openrdf-model and openrdf-sail-api ... after this the whole build worked like a charm. I guess I will fine-tune my modifications and post a patch here in the next few days ... my next step will be getting the Integration-tests to run. Hopefully this will not be such a Monster Task as it was with another Project I worked on Flexmojos. Chris
AW: Incubator
Having a look at Jira, it seems that the two blocker issues NPANDAY-565 and NPANDAY-564 should be pretty easy to fix. Think I'll give them a spin. Hopefully some comitter is still around to apply the patches as soon as they are done. Chris Von: Raphael Bircher [r.birc...@gmx.ch] Gesendet: Sonntag, 10. November 2013 13:28 An: npanday-dev@incubator.apache.org Betreff: Re: Incubator Hi christofer Am 10.11.13 11:54, schrieb christofer.d...@c-ware.de: Hi, I am intending on using NPanday in an upcoming project (Have used it just a little in an experimental project before) but am willing to help :-) Great to hear. Would be good to have some sort of Things that have to be done List. The problem is, I can't tell much here. I'm a Shepherd from the Incubator. We are a group or people who review a project every month. The projects ar randomly attached to a person. I'm a PMC and a Committer from the Apache OpenOffice Project. But I'm willing to help to restart this project. For work, look at the jira issue tracker. I hope this mails reactivate some old contributors too here. Greetings Raphael Chris -Ursprüngliche Nachricht- Von: dhakehu...@gmail.com [mailto:dhakehu...@gmail.com] Im Auftrag von David Akehurst Gesendet: Samstag, 9. November 2013 23:12 An: npanday-dev@incubator.apache.org Betreff: Incubator What is needed to be done to take this beyond incubator, We use v 1.5 on this. -- Hi all My name is Raphael Bircher. I'm from the Incubator and doing shepherding for this project this month. In my review i saw nearly no activity in the last three months. There is also only one mentor who is inactive since one year, (according dev ml). The big question is: Is here still some willing and energy to develop this project, or not. You have not filled the bord report now, pleas do it. I will do my shepherd report anyway, and bring the topic to the incubator list. Greetings Raphael
Re: Status of the project?
Hi Raphael, Thanks for checking in. You were right in another message, I was on holidays. There are people here willing to develop on the project, but time comes and goes for each. When we first brought the project into Apache, there was interest from several others, including some Apache committers, but it waned - and though we get occasional patches from new people, we've had trouble getting them on as committers. I'm glad to see the interest sparked by your message, which I'll respond to separately. In terms of mentors, we've gradually lost them over time, and I was unsuccessful in recruiting new ones from general@. We very much need an active mentor to keep us honest :) I hope you'll volunteer... For the overall status: We need to ship 1.5.0. Unfortunately, while the Windows build slave was broken for a while some changes were made that broke compatibility. They are good changes, but the regressions need to be fixed to ship a release. Aside from that, the project is reasonably stable. There are additions here and there for new releases that come out, and some potential architectural changes to take advantage of recent developments in .NET and Maven and cruft to clear out, but otherwise it pretty much does what you need it to do. That can make it hard to attract new contributors. One thing that could be improved is Mono support. While some things exist, the existing developers don't use it - so that's an area for new contributors to get involved. Another challenge I've found is that contributors tend to interact purely over JIRA or even reach out over Skype. It has been difficult to get more happening on this list as it should. I'll put this in as a report for this month if it is not too late. Thanks again for following up. Cheers, Brett On 8 Nov 2013, at 2:03 pm, Raphael Bircher r.birc...@gmx.ch wrote: Hi all My name is Raphael Bircher. I'm from the Incubator and doing shepherding for this project this month. In my review i saw nearly no activity in the last three months. There is also only one mentor who is inactive since one year, (according dev ml). The big question is: Is here still some willing and energy to develop this project, or not. You have not filled the bord report now, pleas do it. I will do my shepherd report anyway, and bring the topic to the incubator list. Greetings Raphael -- Brett Porter @brettporter http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter
Re: Incubator
On 12 Nov 2013, at 8:52 pm, christofer.d...@c-ware.de wrote: Having a look at Jira, it seems that the two blocker issues NPANDAY-565 and NPANDAY-564 should be pretty easy to fix. Think I'll give them a spin. Hopefully some comitter is still around to apply the patches as soon as they are done. Thanks! I'd be happy to review any work or answer questions if you're looking to contribute to these, or to other tickets marked for 1.5.0. Cheers, Brett -- Brett Porter @brettporter http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter
Re: Requested Addidtion to compile plugin
Absolutely. David, please submit the patch into a new (or relevant existing) JIRA ticket, and then follow up here. Let us know if you need any help. Thanks, Brett On 11 Nov 2013, at 7:24 am, Raphael Bircher r.birc...@gmx.ch wrote: Hi David Am 10.11.13 20:43, schrieb David Akehurst: I'm after a way to override (or set) the artifactType in the compile plugin configuration. I have made a couple of additions to my local copy of the code base. What process should I go through in order to commit these? You can provide a patch, so other people can test it, and the patchs can be openly discused. Then the patch has to be applied by a committer. I'm not a committer, so I'can't do it. But I'm sure, same committers will show up. Give them a week to wake up ;-) Greetings Raphael -- Brett Porter @brettporter http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter
Re: Incubator
On 10 Nov 2013, at 9:54 pm, christofer.d...@c-ware.de wrote: Hi, I am intending on using NPanday in an upcoming project (Have used it just a little in an experimental project before) but am willing to help :-) Would be good to have some sort of Things that have to be done List. Off the top of my head, the things to be done list is: - fix the problems that lead to integration test failures - fix the regressions that have been filed in JIRA against 1.5.0 - run through the list of other tickets marked for 1.5.0. Some just need to be updated based on progress already made, some may need to be fixed, and others could be bumped out. - finish migrating the site to svnpubsub so we can update the site (I started this) We welcome help on any of these. There are other things that might interest people (like improving mono results, and some folks have been contributing to PDB support) that are always welcome, but those are what come to mind for the next release. Cheers, Brett -- Brett Porter @brettporter http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter
AW: Building NPanday
Hi Brett, Well in my checkout I added two profiles default and minimal each containing only a modules section. Minimal only referencing the compiler-maven-plugin and the default containing the normal modules-section. I then disabled the Profile which automatically disables itself as soon as the bootstrap property is set. At least this way is buildable using mvn clean install -Pminimal mvn clean install without having to have any Prior Version available in any repo. I would much favour this Approach and it would be much more like other maven plugin Projects are Setup. Chris Von: Brett Porter [br...@porterclan.net] im Auftrag von Brett Porter [br...@apache.org] Gesendet: Mittwoch, 13. November 2013 08:12 An: npanday-dev@incubator.apache.org Betreff: Re: Building NPanday Hi Chris, On 12 Nov 2013, at 8:21 pm, christofer.d...@c-ware.de wrote: Hi, so I had a look at building NPanday. It was quite a hastle getting the build to run, but in the end I seem to have gotten it working. I would however suggest to modify the build slightly. There is one Problem in every plugin Project: You Need the plugin itself somewhere in the build of the rest of the plugins suilte. Unfortunately Maven doesn't respect plugins when building the reactor order of the modules and you usually get Errors about the plugin not being available in any repo ... of course ... it hasn't been built yet. The solution is usually to provide a minimal maven Profile that builds only the plugin as well as the dependencies of the plugin. So a full build from scratch usually Looks like this: mvn clean install -Pminimal mvn clean install Currently we have a bootstrap script which runs mvn with a --projects list, up until the right plugin is available, then lets you run the full one. Is there something we can do to make that clearer? Ideally, with a more recent release available, the default build could just depend on a previous version of the plugins. Additionally I changed the Version of the openrdf dependencies in the module dotnet-registry to 2.0.1 and added two missing deps to openrdf-model and openrdf-sail-api ... after this the whole build worked like a charm. That's good - did you find these artifacts in the central repo, or in the repo in the top level POM? It's been our objective to remove RDF for some time, but it's not completely happened yet. I guess I will fine-tune my modifications and post a patch here in the next few days ... my next step will be getting the Integration-tests to run. Hopefully this will not be such a Monster Task as it was with another Project I worked on Flexmojos. Thanks again for your help. The integration tests may be a bit of a tough one - though it's just a few changes some of them are rather deep in the code. There was some discussion on this list about it a while ago - I'm happy to give some pointers when you get to this. Cheers, Brett -- Brett Porter @brettporter http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter
