Re: Complete Maven Noob, Is this possible?
well at the end of the compile, and package there should be only 1 WAR file, but the problem right now is figuring out how to make jars out of different folders, and different files in each part of the Main project (different projects folders). Manos Batsis wrote: A major issue if you are new, is how many artifacts (WAR, EAR, whatever) your current build produces. You may have to do a lot of refactoring due to this as Maven wants one artifact per project. This often leads into more modules/projects than one may think. Cheers, Manos Quoting Quakky [EMAIL PROTECTED]: Hey guys, thanks for ur input on this... I had talked with the programmers of this project and they said they might be willing to follow Maven's default layout, and Im willing to kinda work on it day and night so does that improve my chances? :D Wayne Fay wrote: I'll go out on a limb and say a non-programmer without any Maven experience has less than a 5% chance of doing this in 2 weeks. Unless the project is extremely simple... and you've already said it is complex. I've previously helped someone in a similar situation and it was not fun for either of us, and I'm not going to repeat that experience. Not having the programming and XML background means you'll have a hard time interpreting the error messages that are bound to occur not just in Maven itself but also those produced by the Java compiler and in various plugins you'll undoubtedly need to utilize. Little errors in the XML can create significant problems. A failure to understand how Java works in terms of locating files in the proper place etc will also lead to a huge number of failures during the compilation process. Given the 2 week deadline, perhaps it might make more sense for your company to pursue Maven migration services provided by third parties like Devzuz, Sonatype, etc -- though I'm not certain who if anyone actually does this, and it would certainly cost a few bucks. Wayne On 10/12/07, John Casey [EMAIL PROTECTED] wrote: How complex is the project, and what was it using to build before? Complexity is in terms of the number of different types of packagings used, number of different entry points into the build, etc...not just the number of projects. If the previous build was Ant, and the projects can be categorized together in terms of how they're built, it's fairly likely that they use common logic in the Ant script...which means these projects don't add a lot in terms of complexity for conversion, since you only have to convert the build process once for that category, and apply it to them all. The XML syntax that Maven uses for POMs is very straightforward. As far as being able to code, that's usually helpful for debugging tests that stop working, etc. It can also help a lot if it comes to writing custom plugins for Maven to fill in a gap here or there that isn't provided by standard plugins from ASF or the Mojo project (mojo.codehaus.org). But in any case, if the build complexity is high in the terms I mentioned above, I would bet that you'll be at it awhile longer than two weeks. Really the time depends on you having a very intimate understanding of how the current build runs. Good luck, -john On Oct 12, 2007, at 12:14 PM, Quakky wrote: Hello, I am currently in need of some advice concerning Maven. I am a new user, trying to get maven to work with a project that is pretty complex (doesn't follow the default tree structure of maven, has to be packaged in a certain way, etc) . I didn't work on the project, I dont know how to code anything, infact I only figured out what Maven does after reading the Maven book. I do not know how to code XML, which pom.xml is written with(?), but I can learn fast. My question: Is there anyway a user like me (a noob, who only finished the simple project and never really got it to work 100%) can be able to make maven work with a complex project that was Not made with maven and be able to implement this project into a maven environment, and be able to have maven work in about 2 weeks? or do I need more time to learn Maven? Thanks -- View this message in context: http://www.nabble.com/Complete-Maven- Noob%2C-Is-this-possible--tf4614185s177.html#a13177028 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john rss: http://feeds.feedburner.com/ejlife/john - To unsubscribe, e-mail: [EMAIL
Re: Complete Maven Noob, Is this possible?
-Is-this-possible--tf4614185s177.html#a13177028 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john rss: http://feeds.feedburner.com/ejlife/john - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Complete-Maven-Noob%2C-Is-this-possible--tf4614185s177.html#a13192212 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Complete-Maven-Noob%2C-Is-this-possible--tf4614185s177.html#a13234710 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Complete Maven Noob, Is this possible?
Quakky wrote: Hey guys, thanks for ur input on this... I had talked with the programmers of this project and they said they might be willing to follow Maven's default layout, and Im willing to kinda work on it day and night so does that improve my chances? :D Having buy-in from your developers improves your chances a whole bunch (seriously). Focus on the end goal, which is Standardisation Is Good, and switch on the features you get for free, like the documentation and reports. And use the release plugin, it is probably the most useful plugin in the whole maven suite. Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Complete Maven Noob, Is this possible?
Hey guys, thanks for ur input on this... I had talked with the programmers of this project and they said they might be willing to follow Maven's default layout, and Im willing to kinda work on it day and night so does that improve my chances? :D Wayne Fay wrote: I'll go out on a limb and say a non-programmer without any Maven experience has less than a 5% chance of doing this in 2 weeks. Unless the project is extremely simple... and you've already said it is complex. I've previously helped someone in a similar situation and it was not fun for either of us, and I'm not going to repeat that experience. Not having the programming and XML background means you'll have a hard time interpreting the error messages that are bound to occur not just in Maven itself but also those produced by the Java compiler and in various plugins you'll undoubtedly need to utilize. Little errors in the XML can create significant problems. A failure to understand how Java works in terms of locating files in the proper place etc will also lead to a huge number of failures during the compilation process. Given the 2 week deadline, perhaps it might make more sense for your company to pursue Maven migration services provided by third parties like Devzuz, Sonatype, etc -- though I'm not certain who if anyone actually does this, and it would certainly cost a few bucks. Wayne On 10/12/07, John Casey [EMAIL PROTECTED] wrote: How complex is the project, and what was it using to build before? Complexity is in terms of the number of different types of packagings used, number of different entry points into the build, etc...not just the number of projects. If the previous build was Ant, and the projects can be categorized together in terms of how they're built, it's fairly likely that they use common logic in the Ant script...which means these projects don't add a lot in terms of complexity for conversion, since you only have to convert the build process once for that category, and apply it to them all. The XML syntax that Maven uses for POMs is very straightforward. As far as being able to code, that's usually helpful for debugging tests that stop working, etc. It can also help a lot if it comes to writing custom plugins for Maven to fill in a gap here or there that isn't provided by standard plugins from ASF or the Mojo project (mojo.codehaus.org). But in any case, if the build complexity is high in the terms I mentioned above, I would bet that you'll be at it awhile longer than two weeks. Really the time depends on you having a very intimate understanding of how the current build runs. Good luck, -john On Oct 12, 2007, at 12:14 PM, Quakky wrote: Hello, I am currently in need of some advice concerning Maven. I am a new user, trying to get maven to work with a project that is pretty complex (doesn't follow the default tree structure of maven, has to be packaged in a certain way, etc) . I didn't work on the project, I dont know how to code anything, infact I only figured out what Maven does after reading the Maven book. I do not know how to code XML, which pom.xml is written with(?), but I can learn fast. My question: Is there anyway a user like me (a noob, who only finished the simple project and never really got it to work 100%) can be able to make maven work with a complex project that was Not made with maven and be able to implement this project into a maven environment, and be able to have maven work in about 2 weeks? or do I need more time to learn Maven? Thanks -- View this message in context: http://www.nabble.com/Complete-Maven- Noob%2C-Is-this-possible--tf4614185s177.html#a13177028 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john rss: http://feeds.feedburner.com/ejlife/john - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Complete-Maven-Noob%2C-Is-this-possible--tf4614185s177.html#a13192212 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Complete Maven Noob, Is this possible?
A major issue if you are new, is how many artifacts (WAR, EAR, whatever) your current build produces. You may have to do a lot of refactoring due to this as Maven wants one artifact per project. This often leads into more modules/projects than one may think. Cheers, Manos Quoting Quakky [EMAIL PROTECTED]: Hey guys, thanks for ur input on this... I had talked with the programmers of this project and they said they might be willing to follow Maven's default layout, and Im willing to kinda work on it day and night so does that improve my chances? :D Wayne Fay wrote: I'll go out on a limb and say a non-programmer without any Maven experience has less than a 5% chance of doing this in 2 weeks. Unless the project is extremely simple... and you've already said it is complex. I've previously helped someone in a similar situation and it was not fun for either of us, and I'm not going to repeat that experience. Not having the programming and XML background means you'll have a hard time interpreting the error messages that are bound to occur not just in Maven itself but also those produced by the Java compiler and in various plugins you'll undoubtedly need to utilize. Little errors in the XML can create significant problems. A failure to understand how Java works in terms of locating files in the proper place etc will also lead to a huge number of failures during the compilation process. Given the 2 week deadline, perhaps it might make more sense for your company to pursue Maven migration services provided by third parties like Devzuz, Sonatype, etc -- though I'm not certain who if anyone actually does this, and it would certainly cost a few bucks. Wayne On 10/12/07, John Casey [EMAIL PROTECTED] wrote: How complex is the project, and what was it using to build before? Complexity is in terms of the number of different types of packagings used, number of different entry points into the build, etc...not just the number of projects. If the previous build was Ant, and the projects can be categorized together in terms of how they're built, it's fairly likely that they use common logic in the Ant script...which means these projects don't add a lot in terms of complexity for conversion, since you only have to convert the build process once for that category, and apply it to them all. The XML syntax that Maven uses for POMs is very straightforward. As far as being able to code, that's usually helpful for debugging tests that stop working, etc. It can also help a lot if it comes to writing custom plugins for Maven to fill in a gap here or there that isn't provided by standard plugins from ASF or the Mojo project (mojo.codehaus.org). But in any case, if the build complexity is high in the terms I mentioned above, I would bet that you'll be at it awhile longer than two weeks. Really the time depends on you having a very intimate understanding of how the current build runs. Good luck, -john On Oct 12, 2007, at 12:14 PM, Quakky wrote: Hello, I am currently in need of some advice concerning Maven. I am a new user, trying to get maven to work with a project that is pretty complex (doesn't follow the default tree structure of maven, has to be packaged in a certain way, etc) . I didn't work on the project, I dont know how to code anything, infact I only figured out what Maven does after reading the Maven book. I do not know how to code XML, which pom.xml is written with(?), but I can learn fast. My question: Is there anyway a user like me (a noob, who only finished the simple project and never really got it to work 100%) can be able to make maven work with a complex project that was Not made with maven and be able to implement this project into a maven environment, and be able to have maven work in about 2 weeks? or do I need more time to learn Maven? Thanks -- View this message in context: http://www.nabble.com/Complete-Maven- Noob%2C-Is-this-possible--tf4614185s177.html#a13177028 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john rss: http://feeds.feedburner.com/ejlife/john - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Complete-Maven-Noob%2C-Is-this-possible--tf4614185s177.html#a13192212 Sent from the Maven - Users mailing list archive at Nabble.com
Re: Complete Maven Noob, Is this possible?
On Fri, October 12, 2007 6:14 pm, Quakky wrote: My question: Is there anyway a user like me (a noob, who only finished the simple project and never really got it to work 100%) can be able to make maven work with a complex project that was Not made with maven and be able to implement this project into a maven environment, and be able to have maven work in about 2 weeks? or do I need more time to learn Maven? You'll very probably need more time. Maven's strength lies in standardisation: Because source code is in a standard place, you don't need to tell the compiler or javadocs where to find the code. Because test output is written to a standard place, you don't need to tell maven how to incorporate your test results in your documentation, etc. The trouble is that when you start to depart from this standardisation, you have to start overriding the default behaviour and increasing the size of your maven config, which can end up giving the impression that maven is harder than it needs to be. Start small, and get some basic stuff working first. If you can, refactor your code to conform with the maven structure, updating your previous build as appropriate. Eventually, you can wean yourself off the previous build system entirely. Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Complete Maven Noob, Is this possible?
I'll go out on a limb and say a non-programmer without any Maven experience has less than a 5% chance of doing this in 2 weeks. Unless the project is extremely simple... and you've already said it is complex. I've previously helped someone in a similar situation and it was not fun for either of us, and I'm not going to repeat that experience. Not having the programming and XML background means you'll have a hard time interpreting the error messages that are bound to occur not just in Maven itself but also those produced by the Java compiler and in various plugins you'll undoubtedly need to utilize. Little errors in the XML can create significant problems. A failure to understand how Java works in terms of locating files in the proper place etc will also lead to a huge number of failures during the compilation process. Given the 2 week deadline, perhaps it might make more sense for your company to pursue Maven migration services provided by third parties like Devzuz, Sonatype, etc -- though I'm not certain who if anyone actually does this, and it would certainly cost a few bucks. Wayne On 10/12/07, John Casey [EMAIL PROTECTED] wrote: How complex is the project, and what was it using to build before? Complexity is in terms of the number of different types of packagings used, number of different entry points into the build, etc...not just the number of projects. If the previous build was Ant, and the projects can be categorized together in terms of how they're built, it's fairly likely that they use common logic in the Ant script...which means these projects don't add a lot in terms of complexity for conversion, since you only have to convert the build process once for that category, and apply it to them all. The XML syntax that Maven uses for POMs is very straightforward. As far as being able to code, that's usually helpful for debugging tests that stop working, etc. It can also help a lot if it comes to writing custom plugins for Maven to fill in a gap here or there that isn't provided by standard plugins from ASF or the Mojo project (mojo.codehaus.org). But in any case, if the build complexity is high in the terms I mentioned above, I would bet that you'll be at it awhile longer than two weeks. Really the time depends on you having a very intimate understanding of how the current build runs. Good luck, -john On Oct 12, 2007, at 12:14 PM, Quakky wrote: Hello, I am currently in need of some advice concerning Maven. I am a new user, trying to get maven to work with a project that is pretty complex (doesn't follow the default tree structure of maven, has to be packaged in a certain way, etc) . I didn't work on the project, I dont know how to code anything, infact I only figured out what Maven does after reading the Maven book. I do not know how to code XML, which pom.xml is written with(?), but I can learn fast. My question: Is there anyway a user like me (a noob, who only finished the simple project and never really got it to work 100%) can be able to make maven work with a complex project that was Not made with maven and be able to implement this project into a maven environment, and be able to have maven work in about 2 weeks? or do I need more time to learn Maven? Thanks -- View this message in context: http://www.nabble.com/Complete-Maven- Noob%2C-Is-this-possible--tf4614185s177.html#a13177028 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john rss: http://feeds.feedburner.com/ejlife/john - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Complete Maven Noob, Is this possible?
How complex is the project, and what was it using to build before? Complexity is in terms of the number of different types of packagings used, number of different entry points into the build, etc...not just the number of projects. If the previous build was Ant, and the projects can be categorized together in terms of how they're built, it's fairly likely that they use common logic in the Ant script...which means these projects don't add a lot in terms of complexity for conversion, since you only have to convert the build process once for that category, and apply it to them all. The XML syntax that Maven uses for POMs is very straightforward. As far as being able to code, that's usually helpful for debugging tests that stop working, etc. It can also help a lot if it comes to writing custom plugins for Maven to fill in a gap here or there that isn't provided by standard plugins from ASF or the Mojo project (mojo.codehaus.org). But in any case, if the build complexity is high in the terms I mentioned above, I would bet that you'll be at it awhile longer than two weeks. Really the time depends on you having a very intimate understanding of how the current build runs. Good luck, -john On Oct 12, 2007, at 12:14 PM, Quakky wrote: Hello, I am currently in need of some advice concerning Maven. I am a new user, trying to get maven to work with a project that is pretty complex (doesn't follow the default tree structure of maven, has to be packaged in a certain way, etc) . I didn't work on the project, I dont know how to code anything, infact I only figured out what Maven does after reading the Maven book. I do not know how to code XML, which pom.xml is written with(?), but I can learn fast. My question: Is there anyway a user like me (a noob, who only finished the simple project and never really got it to work 100%) can be able to make maven work with a complex project that was Not made with maven and be able to implement this project into a maven environment, and be able to have maven work in about 2 weeks? or do I need more time to learn Maven? Thanks -- View this message in context: http://www.nabble.com/Complete-Maven- Noob%2C-Is-this-possible--tf4614185s177.html#a13177028 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john rss: http://feeds.feedburner.com/ejlife/john
Complete Maven Noob, Is this possible?
Hello, I am currently in need of some advice concerning Maven. I am a new user, trying to get maven to work with a project that is pretty complex (doesn't follow the default tree structure of maven, has to be packaged in a certain way, etc) . I didn't work on the project, I dont know how to code anything, infact I only figured out what Maven does after reading the Maven book. I do not know how to code XML, which pom.xml is written with(?), but I can learn fast. My question: Is there anyway a user like me (a noob, who only finished the simple project and never really got it to work 100%) can be able to make maven work with a complex project that was Not made with maven and be able to implement this project into a maven environment, and be able to have maven work in about 2 weeks? or do I need more time to learn Maven? Thanks -- View this message in context: http://www.nabble.com/Complete-Maven-Noob%2C-Is-this-possible--tf4614185s177.html#a13177028 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
