Re: Unifying maven-nar-plugin implementations
On 7 October 2012 16:36, Martin Eisengardt martin.eisenga...@gmail.comwrote: OK. Thanks four your responses, Mark and Jason. Lets sum up. We have the agreement of the authors to build up a new working group. I recently created a new organization at github: https://github.com/maven-nar (just to give this a kickstart) Please tell me who wants to become a project owner. I have added the three active fork users (richardkerr, grogdomjahn and 1spatial). I suggest to now vote on one fork to be moved to the organization and merging all the pull requests, solving issues etc. Unperiodical users can always create pull requests on the project. New regular users are welcome :) Technical features can be discussed in the github wiki at the moment. I will create website and other things too, the website and repository can be hosted by github. After doing this homework with merging all the forks we can discuss the future of this project. As long as there is no organization selected I will use my jenkins to push the website to a github repository. My employers (CloudBees) will give free jenkins instance to any Open Source project that asks for one. And the (separate, but also free) BuildHive feature we provide will even validate pull requests and add the results to the pull request for you. If you want a cloud based Jenkins to do the pushing to the github repo, it doesn't take long to get one. -Stephen That said if you were going to take it to a foundation, in the long run I would take it to the Eclipse Foundation. They have just converted the whole platform build to Maven and there is a large native component to that for SWT and the launchers. Redhat has done a lot of the work there lately and I'm sure they would be interested as they do their own builds of the Eclipse Platform for their users and customers. I happy to talk any of the groups as Sonatype would have to make a donation of code to move it to a foundation, but honestly I really think Github is the best place for you to spark up the project again. I do not preferr any of the codehaus, mavens core or eclipse foundation. All three solutions are fine for me as well as having a lonesome project group using github and publishing to maven central. For eclipse: This should be discussed with an eclipse foundation guru and with an eclipse cdt guru. As soon as we are ready with the project team and voted for an active project lead I would be happy to contact them. I am already involved in eclipse pdt (commiting patches) and already had some contact to some of the gurus.
Re: Corrupted Assembly, when using a type:pom dependency
Hi, is there nobody, who can confirm, if this is a known issue? Thanks, Stefan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Corrupted Assembly, when using a type:pom dependency
You probably should provide some information about your problem, like what you tried to do, the setup ... Anyway there are a few issues in the tracker, maybe you stumbled accross http://jira.codehaus.org/browse/MASSEMBLY-609? 2012/10/8 Stefan Rademacher rademac...@hhla.de Hi, is there nobody, who can confirm, if this is a known issue? Thanks, Stefan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Unifying maven-nar-plugin implementations
Hello, am new to working with Maven, but I would also like to be a project owner. I would like to teach myself to use maven, jenkins, and eclipse. Ishmael Mosby From: Stephen Connolly stephen.alan.conno...@gmail.com To: Maven Users List users@maven.apache.org Cc: joerg.schai...@gmx.de; Donszelmann Mark d...@cern.ch Sent: Monday, October 8, 2012 10:06 AM Subject: Re: Unifying maven-nar-plugin implementations On 7 October 2012 16:36, Martin Eisengardt martin.eisenga...@gmail.comwrote: OK. Thanks four your responses, Mark and Jason. Lets sum up. We have the agreement of the authors to build up a new working group. I recently created a new organization at github: https://github.com/maven-nar (just to give this a kickstart) Please tell me who wants to become a project owner. I have added the three active fork users (richardkerr, grogdomjahn and 1spatial). I suggest to now vote on one fork to be moved to the organization and merging all the pull requests, solving issues etc. Unperiodical users can always create pull requests on the project. New regular users are welcome :) Technical features can be discussed in the github wiki at the moment. I will create website and other things too, the website and repository can be hosted by github. After doing this homework with merging all the forks we can discuss the future of this project. As long as there is no organization selected I will use my jenkins to push the website to a github repository. My employers (CloudBees) will give free jenkins instance to any Open Source project that asks for one. And the (separate, but also free) BuildHive feature we provide will even validate pull requests and add the results to the pull request for you. If you want a cloud based Jenkins to do the pushing to the github repo, it doesn't take long to get one. -Stephen That said if you were going to take it to a foundation, in the long run I would take it to the Eclipse Foundation. They have just converted the whole platform build to Maven and there is a large native component to that for SWT and the launchers. Redhat has done a lot of the work there lately and I'm sure they would be interested as they do their own builds of the Eclipse Platform for their users and customers. I happy to talk any of the groups as Sonatype would have to make a donation of code to move it to a foundation, but honestly I really think Github is the best place for you to spark up the project again. I do not preferr any of the codehaus, mavens core or eclipse foundation. All three solutions are fine for me as well as having a lonesome project group using github and publishing to maven central. For eclipse: This should be discussed with an eclipse foundation guru and with an eclipse cdt guru. As soon as we are ready with the project team and voted for an active project lead I would be happy to contact them. I am already involved in eclipse pdt (commiting patches) and already had some contact to some of the gurus.
Re: Unifying maven-nar-plugin implementations
My employers (CloudBees) will give free jenkins instance to any Open Source project that asks for one. Thanks for your support. Is your jenkins aware of native builds for win, linux, sunosx, macosx and aware of doing cross-compiles? However please let us talk directly. Maybe we need more than one jenkins to ensure the tests will work on various platforms.
Re: Unifying maven-nar-plugin implementations
On 8 October 2012 13:30, Martin Eisengardt martin.eisenga...@gmail.comwrote: My employers (CloudBees) will give free jenkins instance to any Open Source project that asks for one. Thanks for your support. Is your jenkins aware of native builds for win, linux, sunosx, macosx and aware of doing cross-compiles? However please let us talk directly. Maybe we need more than one jenkins to ensure the tests will work on various platforms. At present our cloud of slaves is Linux only. There is http://developer.cloudbees.com/bin/view/DEV/Customer%2BProvided%2BSlaves%2BWindowsif you have volunteers willing to lend you other build targets
Re: noob confusion about dependencies and repositories
Steinar Bang s...@dod.no: On the recommended book list mentioned earlier, I will in particular mention Maven by example http://www.sonatype.com/Support/Books/Maven-By-Example The download page lists PDF and HTML versions. I was able to build myself an ePub version for my Sony PRS-T1 ebook reader, with: git clone https://github.com/sonatype/maven-example-en.git cd maven-example-en git checkout production mvn install The mvn install command failed for me, while creating the PDF file (a 403 when trying to load the Docbook DTD, with HTTP, I think). But ePub succeeded, and the result was in maven-example-en/mvnex-epub/target/epub/public-book.epub I ran the ePub file through an epub-epub conversion in calibre to get a more pleasing result in the Sony: I first added some missing metadata (authors, and some tags), then did the conversion, picking the cover from the existing epub files (otherwise the cover showed up as a blank in the Sony reader), and told it not to split on page breaks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Unifying maven-nar-plugin implementations
Also, rather than migrating a fork directly, perhaps (if Mark agrees) we could migrate the @duns repo, then push all of Greg's changes back on top? That way, existing GitHub forks will all state forked from maven-nar/maven-nar-plugin afterward, which would be ideal. And to preserve old links Mark could fork it back into @duns again and update the README to state what happened. Thoughts? Sounds like a good plan. However I did not compare the forks so I do not have an idea how many work has to be done. But I will have a look in the next days. Presumably we would also want to similarly migrate cpptasks-parallel? I think so. It isn't maintained too (correct me if I am wrong). Technical features can be discussed in the github wiki at the moment. Martin, shall we create a mailing list for the project? Perhaps a Google group? Then we can migrate this discussion there instead. Feel free to create it an invite the people :) Regarding cross-compilation: I know it is of interest (wouldn't it be great to build for multiple target platforms all from the CloudBees Jenkins on Linux?). My colleague has done quite a lot of work in that area, but there are some substantial obstacles. Shall we discuss further on our shiny new maven-nar-plugin mailing list, once it exists? Yeah, we should discuss it in a working group with experience on this topic. Setting up cross compilation and having a maven-nar-plugin supporting it is not that easy.
