Re: Unifying maven-nar-plugin implementations
Hi all, Feel free to create it an invite the people :) Done: https://groups.google.com/forum/?fromgroups#!forum/maven-nar Let's continue this thread there! Regards, Curtis On Mon, Oct 8, 2012 at 5:40 PM, Martin Eisengardt martin.eisenga...@gmail.com wrote: 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.
Re: Unifying maven-nar-plugin implementations
Don't forget to change the artifactId to nar-maven-plugin or such as maven-___-plugin is reserved for maven.apache.org owned plugins On Tuesday, 9 October 2012, Curtis Rueden wrote: Hi all, Feel free to create it an invite the people :) Done: https://groups.google.com/forum/?fromgroups#!forum/maven-nar Let's continue this thread there! Regards, Curtis On Mon, Oct 8, 2012 at 5:40 PM, Martin Eisengardt martin.eisenga...@gmail.com javascript:; wrote: 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.
RE: Unifying maven-nar-plugin implementations
Hi All, Apologies for the late reply, this is a work email and I have been on leave for the past few days. Many of the changes that I have made are in reaction to issues found during our somewhat unusual (a mix of multi-module, cross-compile and static) builds. It would be nice to see this work being of value to others and as such am in favour of the unification of the project. I would be interested in having some input into the future development of the plugin. I haven't spent much time looking at other forks, as mentioned previously any work was purely reactionary to immediate issues, so unlike the others I do not have any grand plans for the future of the project at this stage. Regards, Richard From: Martin Eisengardt [mailto:martin.eisenga...@gmail.com] Sent: 08 October 2012 23:40 To: Curtis Rueden Cc: Maven Users List; Johannes Schindelin; Greg Domjan; Richard Kerr; Mark Donszelmann; Mark Donszelmann; Elliot Metsger; sthelen; Peter Janes; Claudio Bantaloukas; Mirko Jahn; sugree Subject: 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.
Re: Maven in Vagrantup?
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project mahout-core: Error occurred in starting fork, check output in log - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. Follow the directions you were given. Run again with -X. There is some failure during the test phase relating to forking which is preventing mahout from building. This does not necessarily mean that Maven has a problem or has been installed incorrectly but it may be some odd interaction between Vagrant and the mahout tests which are failing. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
What diagnostic action to take when Maven hangs ?
Hi, I have a Maven build that hangs and I wonder what to do to get some feedback like a message or stack trace or dump.. I'm stuck trying to run some integration tests http://forum.springsource.org/showthread.php?130859-Maven-build-hangs-on-simple-Roo-scriptp=426888posted=1#post426888 Thanks Stephane -- View this message in context: http://maven.40175.n5.nabble.com/What-diagnostic-action-to-take-when-Maven-hangs-tp5725345.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: What diagnostic action to take when Maven hangs ?
What is it doing when it hangs. It is CPU bound, IO bound or waiting for roo to access a database or remote service? On which test is it hanging? What does that test do? Do you have lots of debug statements in your tests? Just some ideas to think about. Ron On 09/10/2012 2:15 PM, Stephane-3 wrote: Hi, I have a Maven build that hangs and I wonder what to do to get some feedback like a message or stack trace or dump.. I'm stuck trying to run some integration tests http://forum.springsource.org/showthread.php?130859-Maven-build-hangs-on-simple-Roo-scriptp=426888posted=1#post426888 Thanks Stephane -- View this message in context: http://maven.40175.n5.nabble.com/What-diagnostic-action-to-take-when-Maven-hangs-tp5725345.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: What diagnostic action to take when Maven hangs ?
Hi Stephane, I have a Maven build that hangs and I wonder what to do to get some feedback like a message or stack trace or dump.. Did you try Ctrl+\ (or Ctrl+Pause on Windows) from the console to do a full thread dump? It might shed some light on what is going on. You can also run Maven in debug mode (mvn -X) to potentially get more information about where things hang. HTH, Curtis On Tue, Oct 9, 2012 at 1:15 PM, Stephane-3 mittiprove...@yahoo.se wrote: Hi, I have a Maven build that hangs and I wonder what to do to get some feedback like a message or stack trace or dump.. I'm stuck trying to run some integration tests http://forum.springsource.org/showthread.php?130859-Maven-build-hangs-on-simple-Roo-scriptp=426888posted=1#post426888 Thanks Stephane -- View this message in context: http://maven.40175.n5.nabble.com/What-diagnostic-action-to-take-when-Maven-hangs-tp5725345.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: What diagnostic action to take when Maven hangs ?
From the original post, it appears that the hang is in the testing phase so I am not sure how much information will come out in a dump or Maven debug mode but it will not hurt anything. I am more suspicious about a test with a loop that does not terminate or a test with a set of bad credentials or a bad URL that is causing a remote operation or database access to fail and go into a wait state. Ron On 09/10/2012 3:22 PM, Curtis Rueden wrote: Hi Stephane, I have a Maven build that hangs and I wonder what to do to get some feedback like a message or stack trace or dump.. Did you try Ctrl+\ (or Ctrl+Pause on Windows) from the console to do a full thread dump? It might shed some light on what is going on. You can also run Maven in debug mode (mvn -X) to potentially get more information about where things hang. HTH, Curtis On Tue, Oct 9, 2012 at 1:15 PM, Stephane-3 mittiprove...@yahoo.se wrote: Hi, I have a Maven build that hangs and I wonder what to do to get some feedback like a message or stack trace or dump.. I'm stuck trying to run some integration tests http://forum.springsource.org/showthread.php?130859-Maven-build-hangs-on-simple-Roo-scriptp=426888posted=1#post426888 Thanks Stephane -- View this message in context: http://maven.40175.n5.nabble.com/What-diagnostic-action-to-take-when-Maven-hangs-tp5725345.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: What diagnostic action to take when Maven hangs ?
Hello,
How can I find out if it is CPU or OI bound ?
It hangs before the very first test.
The test is an integration test, connecting to a MySql database schema.
For now my test is very simple:
@RooIntegrationTest(entity = Address.class)
public class AddressIntegrationTest {
@Before
public void beforeAnyTest() throws Exception {
}
@After
public void afterAnyTest() throws Exception {
}
@Test
@Transactional
public void testSaveAndRetrieve() {
AddressDataOnDemand dod = new AddressDataOnDemand();
Address address = dod.getRandomAddress();
assertNotNull(address.getId());
Integer version = address.getVersion();
addressRepository.saveAndFlush(address);
assertTrue(version != address.getVersion());
}
}
Doing a Ctrl-C gives me back the prompt but I don't see any console output
like a dump.
This test is within a Spring Roo application.
I also created a pure Spring application last year, not a Roo one, with lots
of integration tests against a Dao layer on the very same MySql database
schema. And this Maven project builds fine. But not the Roo one.
--
View this message in context:
http://maven.40175.n5.nabble.com/What-diagnostic-action-to-take-when-Maven-hangs-tp5725345p5725358.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: What diagnostic action to take when Maven hangs ?
Adding some logging to the tests would help.
In Windows, you can use Task Manager to see what your processes are doing.
In Linux, top will tell you.
Ron
On 09/10/2012 3:59 PM, Stephane-3 wrote:
Hello,
How can I find out if it is CPU or OI bound ?
It hangs before the very first test.
The test is an integration test, connecting to a MySql database schema.
For now my test is very simple:
@RooIntegrationTest(entity = Address.class)
public class AddressIntegrationTest {
@Before
public void beforeAnyTest() throws Exception {
}
@After
public void afterAnyTest() throws Exception {
}
@Test
@Transactional
public void testSaveAndRetrieve() {
AddressDataOnDemand dod = new AddressDataOnDemand();
Address address = dod.getRandomAddress();
assertNotNull(address.getId());
Integer version = address.getVersion();
addressRepository.saveAndFlush(address);
assertTrue(version != address.getVersion());
}
}
Doing a Ctrl-C gives me back the prompt but I don't see any console output
like a dump.
This test is within a Spring Roo application.
I also created a pure Spring application last year, not a Roo one, with lots
of integration tests against a Dao layer on the very same MySql database
schema. And this Maven project builds fine. But not the Roo one.
--
View this message in context:
http://maven.40175.n5.nabble.com/What-diagnostic-action-to-take-when-Maven-hangs-tp5725345p5725358.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: What diagnostic action to take when Maven hangs ?
Hi Stephane,
Doing a Ctrl-C gives me back the prompt but I don't see any console
output like a dump.
Not Ctrl-C. Use Ctrl+\ (Linux/Mac/etc.) or Ctrl+Pause (Windows).
HTH,
Curtis
On Tue, Oct 9, 2012 at 2:59 PM, Stephane-3 mittiprove...@yahoo.se wrote:
Hello,
How can I find out if it is CPU or OI bound ?
It hangs before the very first test.
The test is an integration test, connecting to a MySql database schema.
For now my test is very simple:
@RooIntegrationTest(entity = Address.class)
public class AddressIntegrationTest {
@Before
public void beforeAnyTest() throws Exception {
}
@After
public void afterAnyTest() throws Exception {
}
@Test
@Transactional
public void testSaveAndRetrieve() {
AddressDataOnDemand dod = new AddressDataOnDemand();
Address address = dod.getRandomAddress();
assertNotNull(address.getId());
Integer version = address.getVersion();
addressRepository.saveAndFlush(address);
assertTrue(version != address.getVersion());
}
}
Doing a Ctrl-C gives me back the prompt but I don't see any console output
like a dump.
This test is within a Spring Roo application.
I also created a pure Spring application last year, not a Roo one, with
lots
of integration tests against a Dao layer on the very same MySql database
schema. And this Maven project builds fine. But not the Roo one.
--
View this message in context:
http://maven.40175.n5.nabble.com/What-diagnostic-action-to-take-when-Maven-hangs-tp5725345p5725358.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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
What I understood was that Marks aim in loading to github, and what I think our aim now is to have it available for general use and progress to it being an apache.org plugin. Would that mean we should change the name until it is ready, or is having the apache naming part of being ready. Mark Donszelmann mark.donszelm...@cern.ch 9/10/2012 4:12 PM Hi On Oct 9, 2012, at 7:18 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Don't forget to change the artifactId to nar-maven-plugin or such as maven-___-plugin is reserved for maven.apache.org owned plugins I guess that is correct, however Jason (van Zyl) at the time told me to use maven-nar-plugin... Regards Duns - 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
Hi On Oct 9, 2012, at 7:18 PM, Stephen Connolly stephen.alan.conno...@gmail.commailto:stephen.alan.conno...@gmail.com wrote: Don't forget to change the artifactId to nar-maven-plugin or such as maven-___-plugin is reserved for maven.apache.orghttp://maven.apache.org/ owned plugins I guess that is correct, however Jason (van Zyl) at the time told me to use maven-nar-plugin... Regards Duns On Tuesday, 9 October 2012, Curtis Rueden wrote: Hi all, Feel free to create it an invite the people :) Done: https://groups.google.com/forum/?fromgroups#!forum/maven-nar Let's continue this thread there! Regards, Curtis On Mon, Oct 8, 2012 at 5:40 PM, Martin Eisengardt martin.eisenga...@gmail.comjavascript:; wrote: 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.
Re: Unifying maven-nar-plugin implementations
On 9 October 2012 21:12, Mark Donszelmann mark.donszelm...@cern.ch wrote: Hi On Oct 9, 2012, at 7:18 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Don't forget to change the artifactId to nar-maven-plugin or such as maven-___-plugin is reserved for maven.apache.org owned plugins I guess that is correct, however Jason (van Zyl) at the time told me to use maven-nar-plugin... That guidance has changed. Regards Duns On Tuesday, 9 October 2012, Curtis Rueden wrote: Hi all, Feel free to create it an invite the people :) Done: https://groups.google.com/forum/?fromgroups#!forum/maven-nar Let's continue this thread there! Regards, Curtis On Mon, Oct 8, 2012 at 5:40 PM, Martin Eisengardt martin.eisenga...@gmail.com wrote: 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.
Re: Unifying maven-nar-plugin implementations
felix uses maven-bundle-plugin. Not sure why plugin name is important here. -D On Tue, Oct 9, 2012 at 2:38 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 9 October 2012 21:12, Mark Donszelmann mark.donszelm...@cern.ch wrote: Hi On Oct 9, 2012, at 7:18 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Don't forget to change the artifactId to nar-maven-plugin or such as maven-___-plugin is reserved for maven.apache.org owned plugins I guess that is correct, however Jason (van Zyl) at the time told me to use maven-nar-plugin... That guidance has changed. Regards Duns On Tuesday, 9 October 2012, Curtis Rueden wrote: Hi all, Feel free to create it an invite the people :) Done: https://groups.google.com/forum/?fromgroups#!forum/maven-nar Let's continue this thread there! Regards, Curtis On Mon, Oct 8, 2012 at 5:40 PM, Martin Eisengardt martin.eisenga...@gmail.com wrote: 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. - 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
Newer versions of the plugin-plugin enforce the standard so you have to switch to nar-maven-plugin or whatever unless you use the org.apache.maven groupId... imho I would just change and keep the momentum going on github and not really worry about moving it to apache.. manfred On Tue, October 9, 2012 3:11 pm, Dan Tran wrote: felix uses maven-bundle-plugin. Not sure why plugin name is important here. -D On Tue, Oct 9, 2012 at 2:38 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 9 October 2012 21:12, Mark Donszelmann mark.donszelm...@cern.ch wrote: Hi On Oct 9, 2012, at 7:18 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Don't forget to change the artifactId to nar-maven-plugin or such as maven-___-plugin is reserved for maven.apache.org owned plugins I guess that is correct, however Jason (van Zyl) at the time told me to use maven-nar-plugin... That guidance has changed. Regards Duns On Tuesday, 9 October 2012, Curtis Rueden wrote: Hi all, Feel free to create it an invite the people :) Done: https://groups.google.com/forum/?fromgroups#!forum/maven-nar Let's continue this thread there! Regards, Curtis On Mon, Oct 8, 2012 at 5:40 PM, Martin Eisengardt martin.eisenga...@gmail.com wrote: 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. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - 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
felix will have to change On 9 October 2012 23:11, Dan Tran dant...@gmail.com wrote: felix uses maven-bundle-plugin. Not sure why plugin name is important here. -D On Tue, Oct 9, 2012 at 2:38 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 9 October 2012 21:12, Mark Donszelmann mark.donszelm...@cern.ch wrote: Hi On Oct 9, 2012, at 7:18 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Don't forget to change the artifactId to nar-maven-plugin or such as maven-___-plugin is reserved for maven.apache.org owned plugins I guess that is correct, however Jason (van Zyl) at the time told me to use maven-nar-plugin... That guidance has changed. Regards Duns On Tuesday, 9 October 2012, Curtis Rueden wrote: Hi all, Feel free to create it an invite the people :) Done: https://groups.google.com/forum/?fromgroups#!forum/maven-nar Let's continue this thread there! Regards, Curtis On Mon, Oct 8, 2012 at 5:40 PM, Martin Eisengardt martin.eisenga...@gmail.com wrote: 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. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
