Re: Troubles creating Hudson plugin
this is a question for d...@hudson.dev.java.net Sent from my [rhymes with myPod] ;-) On 17 Apr 2009, at 22:06, david.schroeder david.schroe...@i- cubed.com wrote: I am trying to use maven to build a plugin to Hudson org.jvnet.hudson.tools:maven-hpi-plugin:1.34:create Is giving me a BUILD ERROR Internal error in the pluging manager executing goal 'org.jvnet.hudson.tools:maven-hpi-plugin:1.34:create': Unable to find the mojo 'org.jvnet.hudson.tools:maven-hpi-plugin:1.34:create' in the plugin '.jvnet.hudson.tools:maven-hpi-plugin' org/jvnet/hudson/maven/plugins/hpi/CreateMojo (Unsupported major.minor version 49.0) This is the first I am using maven and unfamiliar with these results. Any insight? Thanks! -- View this message in context: http://n2.nabble.com/Troubles-creating-Hudson-plugin-tp2652943p2652943.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Properties files proper location
Markos Fragkakis wrote: Hi, I am having some problems that I expected to be common, however I could not find a solution online for either. I want create a maven project for a swing application. My IDE is Eclipse. In order to run, the application needs to read a a couple of text configuration files, which are located in a params directory, in the root directory of the application. So, if ${root} id the application directory, these files should be in ${root}/params. Furthermore, the application needs to log into the directory ${root}/log. Until now, without Maven, I had created the directories params and log (log was in .cvsignore) in my Eclipse project directory. Every time the project was run, the two directories were found and used. Now, Maven puts its classes in target/classes. In order to run the project from within the IDE, I have put the two directories in the resources directory. So, when I compile the project, they are put inside the target directory, along with the classes and everything works. This placing, however, will put them also in the jar file of the project, which I would not like, since the configuration files in the params directory are supposed to be changes by the user. What is the correct (by-the-book) placing of the files if I need to be able run my project as before, from within the IDE? Are there any additional steps, like using the assembly plugin to create the directory structure? This is probably a best practices issue. Any suggestions / ideas are welcome. Best regards, Markos Fragkakis - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Any suggestions? I believe this is an issue other people have as well, and many would benefit if solutions, or even a discussion is documented. Thanks, Markos Fragkakis - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Properties files proper location
Hello Markos, Maybe you could place fail-safe-params.properties with default settings within jar, thus within src/main/resources, and support them to be overridden by user using external params.properties file. Regards, Stevo. On Sat, Apr 18, 2009 at 2:52 PM, Markos Fragkakis markos.fragka...@agilis-sa.gr wrote: Markos Fragkakis wrote: Hi, I am having some problems that I expected to be common, however I could not find a solution online for either. I want create a maven project for a swing application. My IDE is Eclipse. In order to run, the application needs to read a a couple of text configuration files, which are located in a params directory, in the root directory of the application. So, if ${root} id the application directory, these files should be in ${root}/params. Furthermore, the application needs to log into the directory ${root}/log. Until now, without Maven, I had created the directories params and log (log was in .cvsignore) in my Eclipse project directory. Every time the project was run, the two directories were found and used. Now, Maven puts its classes in target/classes. In order to run the project from within the IDE, I have put the two directories in the resources directory. So, when I compile the project, they are put inside the target directory, along with the classes and everything works. This placing, however, will put them also in the jar file of the project, which I would not like, since the configuration files in the params directory are supposed to be changes by the user. What is the correct (by-the-book) placing of the files if I need to be able run my project as before, from within the IDE? Are there any additional steps, like using the assembly plugin to create the directory structure? This is probably a best practices issue. Any suggestions / ideas are welcome. Best regards, Markos Fragkakis - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Any suggestions? I believe this is an issue other people have as well, and many would benefit if solutions, or even a discussion is documented. Thanks, Markos Fragkakis - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Properties files proper location
My take on this is that there is no 'standard' by the book so-to-speak maven way of doing this. The standard thing in maven is to create one artifact per project so its standard to include files, etc in jar but not to externalize them. But that doesn't solve your problem. However, like you suggested, you can add these other resources via the assembly plugin however there is no standard folder(s) or practices here you can do what you want. If there is something more standard than this; I too, would like to know about it. -Dave On Sat, Apr 18, 2009 at 7:12 AM, Stevo Slavić ssla...@gmail.com wrote: Hello Markos, Maybe you could place fail-safe-params.properties with default settings within jar, thus within src/main/resources, and support them to be overridden by user using external params.properties file. Regards, Stevo. On Sat, Apr 18, 2009 at 2:52 PM, Markos Fragkakis markos.fragka...@agilis-sa.gr wrote: Markos Fragkakis wrote: Hi, I am having some problems that I expected to be common, however I could not find a solution online for either. I want create a maven project for a swing application. My IDE is Eclipse. In order to run, the application needs to read a a couple of text configuration files, which are located in a params directory, in the root directory of the application. So, if ${root} id the application directory, these files should be in ${root}/params. Furthermore, the application needs to log into the directory ${root}/log. Until now, without Maven, I had created the directories params and log (log was in .cvsignore) in my Eclipse project directory. Every time the project was run, the two directories were found and used. Now, Maven puts its classes in target/classes. In order to run the project from within the IDE, I have put the two directories in the resources directory. So, when I compile the project, they are put inside the target directory, along with the classes and everything works. This placing, however, will put them also in the jar file of the project, which I would not like, since the configuration files in the params directory are supposed to be changes by the user. What is the correct (by-the-book) placing of the files if I need to be able run my project as before, from within the IDE? Are there any additional steps, like using the assembly plugin to create the directory structure? This is probably a best practices issue. Any suggestions / ideas are welcome. Best regards, Markos Fragkakis - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Any suggestions? I believe this is an issue other people have as well, and many would benefit if solutions, or even a discussion is documented. Thanks, Markos Fragkakis - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven child site has unresolved image in top-right corner
Hi. I'm using maven 2.1.0, maven-site-plugin 2.0-beta-7. When I go to my child site, I see an image in the top right-hand corner which is unresolved, and I looked at its url, and it's trying to load an image from http://childhttp://%3cchild module name/child module name What does this image do, and how can I properly configure it? Thanks. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]