Re: Maven2 workflow
On Fri, 22 Apr 2005, Brett Porter wrote: About the resource problem: just add your src/main/resources/ directory to the runtime classpath in the Run-Run.. - Classpath-tab, then you should be able to load it using the ClassLoader.getResource(); Though this shouldn't be necessary, since resources are copied to the target/classes/ directory, which is (should be) in the Runtime classpath autmatically. Greetings, Kenney Westerhof I'm quite new to Maven. I've decided to directly start using Maven 2.0, I can avoid a migration that way. Ok, we're happy to help out early adopters, but please keep in mind that Maven2 is alpha software, not expected to have a final release until August - so you may have to do a little work get things going properly. But what is the best workflow to use maven (2) ? For example I have an existing software project which I want to develop very incremently. Suppose I would like to do a release every week. Performing a release means: building and packaging and deploying on my own repository. We have some tools in Maven 1.0 to help prepare releases that we will be adding to 2.0-alpha-2. This manages updating the POM, tagging, etc. You may also like to use the SNAPSHOT facility to publish incremental builds, perhaps even have your continuous integration environment do that, then promote builds to be releases. Though focused on m1, these general principles might help: http://maven.apache.org/using/bestpractices.html http://maven.apache.org/using/releasing.html But I guess I can also use maven to commit my changes to cvs dialy ? You could, though I think this is really more useful for automated changes and releases. Generally, it's better to use your existing IDE and tools to review and commit changes. Does that already works with maven 2 ? Not yet, no. Question is : can I use maven for everythin except editing code ? Theoretically, but you should find the balance that best suits you :) One little thing I find annoying is this: I have restructured the layout of my sources according to the guidelines : resulting the logo of my app ending up in the directory : src/main/resources, when I compile my program using maven that is ok ofcourse. But when I want to run it from eclipse it is not. Usually there is a way to add resources to be copied to the output directory in Eclipse - I'm not sure what it is, though, being an IDEA user. Hope this helps. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 workflow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 One little thing I find annoying is this: I have restructured the layout of my sources according to the guidelines : resulting the logo of my app ending up in the directory : src/main/resources, when I compile my program using maven that is ok ofcourse. But when I want to run it from eclipse it is not. Usually there is a way to add resources to be copied to the output directory in Eclipse - I'm not sure what it is, though, being an IDEA user. The best way I've found to handle non-code resources in the classpath within Eclipse is to add a class folder. The way to do this is to open the properties for your project, select Java Build Path, then the Libraries tab. Once here, click on the Add Class Folder... button, and select your resources directory/directories, then click Ok (you can simply check off the folders you want added to your classpath). Using this approach allows you to have access to those resources from your classpath, without getting into issues of duplicate files on your sourcepath. HTH, john -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFCaPQmK3h2CZwO/4URAs05AJwPxL6h+MJ0am2EGCvvzc8iw7+lpACaAtlk kzVMC/H3Pw+KolXfXpn8Q2c= =caY+ -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven2 workflow
Hi, I'm quite new to Maven. I've decided to directly start using Maven 2.0, I can avoid a migration that way. But what is the best workflow to use maven (2) ? For example I have an existing software project which I want to develop very incremently. Suppose I would like to do a release every week. Performing a release means: building and packaging and deploying on my own repository. I have the habit of checking in my code everyday when it compiles, at least. But at a certain time I wan to make a new development release. I now have a version of my software at 0.1 suppose that I want to make a new release next week, then I will have to adapt my pom, to change the version number. Next I will issue m2 deploy. My sources will get compiled, packaged and deployed on my repository. But I guess I can also use maven to commit my changes to cvs dialy ? Does that already works with maven 2 ? Question is : can I use maven for everythin except editing code ? One little thing I find annoying is this: I have restructured the layout of my sources according to the guidelines : resulting the logo of my app ending up in the directory : src/main/resources, when I compile my program using maven that is ok ofcourse. But when I want to run it from eclipse it is not. I use this line of code to load the logo: ImageIcon logo = new ImageIcon(getClass().getResource( /logo.png), Logo); kind regards, Pieter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 workflow
I'm quite new to Maven. I've decided to directly start using Maven 2.0, I can avoid a migration that way. Ok, we're happy to help out early adopters, but please keep in mind that Maven2 is alpha software, not expected to have a final release until August - so you may have to do a little work get things going properly. But what is the best workflow to use maven (2) ? For example I have an existing software project which I want to develop very incremently. Suppose I would like to do a release every week. Performing a release means: building and packaging and deploying on my own repository. We have some tools in Maven 1.0 to help prepare releases that we will be adding to 2.0-alpha-2. This manages updating the POM, tagging, etc. You may also like to use the SNAPSHOT facility to publish incremental builds, perhaps even have your continuous integration environment do that, then promote builds to be releases. Though focused on m1, these general principles might help: http://maven.apache.org/using/bestpractices.html http://maven.apache.org/using/releasing.html But I guess I can also use maven to commit my changes to cvs dialy ? You could, though I think this is really more useful for automated changes and releases. Generally, it's better to use your existing IDE and tools to review and commit changes. Does that already works with maven 2 ? Not yet, no. Question is : can I use maven for everythin except editing code ? Theoretically, but you should find the balance that best suits you :) One little thing I find annoying is this: I have restructured the layout of my sources according to the guidelines : resulting the logo of my app ending up in the directory : src/main/resources, when I compile my program using maven that is ok ofcourse. But when I want to run it from eclipse it is not. Usually there is a way to add resources to be copied to the output directory in Eclipse - I'm not sure what it is, though, being an IDEA user. Hope this helps. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
