RE: maven constantly rebuilding everything
So the fix would be something like: 1 - Make process-resources look at the source of the activated profiles and make sure they are newer than the templates and then (and only then) process the templates. 2 - Make the install plugin test what's in the repository is out of date with the just built jar before installing. 3 - Make the war plugin able to ignore/exclude maven generated files (such as pom.properties) - this may/may not solve our war rebuilding issues. ??? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 9:33 PM To: Maven Users List Subject: RE: maven constantly rebuilding everything Well, maybe I'm not quite out of the woods. Process-resources always moves some files into classes so I guess this will forever jar stuff up, right? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 1:13 PM To: Maven Users List Subject: RE: maven constantly rebuilding everything Yeah, I'm able to prevent rebuilding of all the jars, not re-downloading the resources as part of the maven-dependency-plugin - so that much is ok. I'm still getting everything installed every time I build even if it didn't have to re-jar the source. Is there a solution/jira for that (I couldn't find anything with my searches). -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 11:59 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything It certainly sounds like you are dealing with a large project. Since you mentioned images, I wonder how much of the 200mb is actually code and how much is everything else? I assume you've run an analysis. I've looked into this rebuilding every jar issue at some point. In short, Maven creates a pom.properties file every time it executes in a given module. Thus you *always* have changes, even when you don't. Also the filtered resources thing that Daniel mentioned is another forgotten source of changes. Damien just sent the link to this bug, he must have been reading my mind... ;-) Wayne On 11/9/07, EJ Ciramella [EMAIL PROTECTED] wrote: I'd love to know what people are building and the size of things, I think our project is larger than most (I'm not stepping into a pissing contest, simply stating the facts). We're working on a massive refactoring both in codeline management and actual code refactoring. Even with the refactoring done, that will only help to a certain degree. With testing, we're talking about 1 - 1.5 hours. The resulting assembly for our main application is 195 - 200 mb (full of jsps, images, classes, jars, etc). I wish I could better show you the size of the application (we have three ears and 4 - 5 wars depending on what you're building). There's no real honest to goodness code in the jsps (as it should be), all business logic is handled else where. As a release engineer, it's not my business to make sweeping changes like that. I can make suggestions, but in the end, it's up to development to decide what projects have merit/profit/etc associated with them. It'd be nice if you could work at the lowest directory all the time (the one responsible for building the ear file), but when your change effects a module that the ear you want depends on (or MULTIPLE subprojects), most developers here build from the top. Also, when profiles.xml lives at the root of the overall project and contains 90% the configuration for a developers box, sitting at a lower level, aren't these properties unavailable (doesn't maven only look in the working directory for profiles.xml)? If maven wouldn't try to rebuild every jar and then every war and then every ear, life would be much better. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 8:10 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Sounds like your projects are entirely too big -- break 'em up a bit. Even 10min builds sounds rather long -- is this compilation only or including testing? And what portion of that time is consumed by your tests -- at this level (compilation), you should be running very fast unit tests, generally not integration tests. Artifacts/modules are cheap in Maven. War modules in particular should not have a lot of code associated with them -- move the code into Jars and extract the code out of your JSPs etc into classes that go into those Jars. Also when you're working, you don't clean install from the top parent, but instead run it from the module you're working on. At least, this is what we do... Wayne On 11/9/07, EJ Ciramella [EMAIL PROTECTED] wrote: That's incredible, doing that takes 30 - 40 minutes here. Most developers here are used to a 10 build time. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:08 PM
Re: maven constantly rebuilding everything
Sounds reasonable, but how would you do #2? One way I was thinking was grab latest jar from repo, compare contents to just built jar (hash both and compare?). Or did you have another plan? Wayne On 11/12/07, EJ Ciramella [EMAIL PROTECTED] wrote: So the fix would be something like: 1 - Make process-resources look at the source of the activated profiles and make sure they are newer than the templates and then (and only then) process the templates. 2 - Make the install plugin test what's in the repository is out of date with the just built jar before installing. 3 - Make the war plugin able to ignore/exclude maven generated files (such as pom.properties) - this may/may not solve our war rebuilding issues. ??? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven constantly rebuilding everything
Here's the pseudo code: 1 - Don't have to build new jar because everything is uptodate? Don't install - maybe this means install takes a new param true/false style on whether it needs to be installed or not. 2 - If local jar has newer timestamp - install. Install only cares about local repository, right? It's deploy that looks across to the internal repository - and the only machine to do that is the build machine. About the process-resources solution - is that kind of info available? Can I track back via the profiles on the commandline to the files in question (where the profiles came from)? Am I missing anything? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Monday, November 12, 2007 12:06 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything Sounds reasonable, but how would you do #2? One way I was thinking was grab latest jar from repo, compare contents to just built jar (hash both and compare?). Or did you have another plan? Wayne On 11/12/07, EJ Ciramella [EMAIL PROTECTED] wrote: So the fix would be something like: 1 - Make process-resources look at the source of the activated profiles and make sure they are newer than the templates and then (and only then) process the templates. 2 - Make the install plugin test what's in the repository is out of date with the just built jar before installing. 3 - Make the war plugin able to ignore/exclude maven generated files (such as pom.properties) - this may/may not solve our war rebuilding issues. ??? - 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: maven constantly rebuilding everything
When a child pom indicates there is a parent pom, the parent pom is always processed. It doesn't depend on where in the hierarchy the child pom is sitting. Notice that the child pom will have a parent section that completely identifies the parent OR defaults to the parent being in the parent folder. Notice that with all the things you can inject into the generated artifacts, it is very difficult to tell if the current generated artifact is going to be different than the last version. The problem is that the output file doesn't just depend on the input files. It depends on various properties and such, as well. (Think build number.) It probably isn't any faster to build the new version (say, in memory) and then read the old version and compare than to just build the new version and store it. (You do have the down side of having a new file date/time on the output.) Once you change the one output file, then all the downstream dependencies have to be fired off as well. (That may be a reason to try to keep from changing the date/time on what was the output file but has become the input for the next phase.) But, if that didn't happen, you would still have to build the next phase because you don't know if it depends on some changed property. Sorting out which properties can change and NOT cause the next phase to be built is a big problem too. You would have to say stuff like, When the date/time changes, you don't do a build. But when the deployment environment changes you do need a build. And, you can define properties on the command line and they can come from the system environment. Do you store all the properties values on each build and then compare on the next build to see if anything changed? As you can see, there might be some things that could be done to make less stuff get built. But there may not ever be a way to make it work 100%. This may take a lot of thought and testing and defining to even know. -- Lee On Nov 9, 2007 7:57 AM, EJ Ciramella [EMAIL PROTECTED] wrote: I'd love to know what people are building and the size of things, I think our project is larger than most (I'm not stepping into a pissing contest, simply stating the facts). We're working on a massive refactoring both in codeline management and actual code refactoring. Even with the refactoring done, that will only help to a certain degree. With testing, we're talking about 1 - 1.5 hours. The resulting assembly for our main application is 195 - 200 mb (full of jsps, images, classes, jars, etc). I wish I could better show you the size of the application (we have three ears and 4 - 5 wars depending on what you're building). There's no real honest to goodness code in the jsps (as it should be), all business logic is handled else where. As a release engineer, it's not my business to make sweeping changes like that. I can make suggestions, but in the end, it's up to development to decide what projects have merit/profit/etc associated with them. It'd be nice if you could work at the lowest directory all the time (the one responsible for building the ear file), but when your change effects a module that the ear you want depends on (or MULTIPLE subprojects), most developers here build from the top. Also, when profiles.xml lives at the root of the overall project and contains 90% the configuration for a developers box, sitting at a lower level, aren't these properties unavailable (doesn't maven only look in the working directory for profiles.xml)? If maven wouldn't try to rebuild every jar and then every war and then every ear, life would be much better. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 8:10 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Sounds like your projects are entirely too big -- break 'em up a bit. Even 10min builds sounds rather long -- is this compilation only or including testing? And what portion of that time is consumed by your tests -- at this level (compilation), you should be running very fast unit tests, generally not integration tests. Artifacts/modules are cheap in Maven. War modules in particular should not have a lot of code associated with them -- move the code into Jars and extract the code out of your JSPs etc into classes that go into those Jars. Also when you're working, you don't clean install from the top parent, but instead run it from the module you're working on. At least, this is what we do... Wayne On 11/9/07, EJ Ciramella [EMAIL PROTECTED] wrote: That's incredible, doing that takes 30 - 40 minutes here. Most developers here are used to a 10 build time. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:08 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything I nearly always build clean package or clean install so I expect them to rebuild
RE: maven constantly rebuilding everything
I'm not sure what you're trying to tell me to do, nothing? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lee Meador Sent: Monday, November 12, 2007 2:22 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything When a child pom indicates there is a parent pom, the parent pom is always processed. It doesn't depend on where in the hierarchy the child pom is sitting. Notice that the child pom will have a parent section that completely identifies the parent OR defaults to the parent being in the parent folder. Notice that with all the things you can inject into the generated artifacts, it is very difficult to tell if the current generated artifact is going to be different than the last version. The problem is that the output file doesn't just depend on the input files. It depends on various properties and such, as well. (Think build number.) It probably isn't any faster to build the new version (say, in memory) and then read the old version and compare than to just build the new version and store it. (You do have the down side of having a new file date/time on the output.) Once you change the one output file, then all the downstream dependencies have to be fired off as well. (That may be a reason to try to keep from changing the date/time on what was the output file but has become the input for the next phase.) But, if that didn't happen, you would still have to build the next phase because you don't know if it depends on some changed property. Sorting out which properties can change and NOT cause the next phase to be built is a big problem too. You would have to say stuff like, When the date/time changes, you don't do a build. But when the deployment environment changes you do need a build. And, you can define properties on the command line and they can come from the system environment. Do you store all the properties values on each build and then compare on the next build to see if anything changed? As you can see, there might be some things that could be done to make less stuff get built. But there may not ever be a way to make it work 100%. This may take a lot of thought and testing and defining to even know. -- Lee On Nov 9, 2007 7:57 AM, EJ Ciramella [EMAIL PROTECTED] wrote: I'd love to know what people are building and the size of things, I think our project is larger than most (I'm not stepping into a pissing contest, simply stating the facts). We're working on a massive refactoring both in codeline management and actual code refactoring. Even with the refactoring done, that will only help to a certain degree. With testing, we're talking about 1 - 1.5 hours. The resulting assembly for our main application is 195 - 200 mb (full of jsps, images, classes, jars, etc). I wish I could better show you the size of the application (we have three ears and 4 - 5 wars depending on what you're building). There's no real honest to goodness code in the jsps (as it should be), all business logic is handled else where. As a release engineer, it's not my business to make sweeping changes like that. I can make suggestions, but in the end, it's up to development to decide what projects have merit/profit/etc associated with them. It'd be nice if you could work at the lowest directory all the time (the one responsible for building the ear file), but when your change effects a module that the ear you want depends on (or MULTIPLE subprojects), most developers here build from the top. Also, when profiles.xml lives at the root of the overall project and contains 90% the configuration for a developers box, sitting at a lower level, aren't these properties unavailable (doesn't maven only look in the working directory for profiles.xml)? If maven wouldn't try to rebuild every jar and then every war and then every ear, life would be much better. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 8:10 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Sounds like your projects are entirely too big -- break 'em up a bit. Even 10min builds sounds rather long -- is this compilation only or including testing? And what portion of that time is consumed by your tests -- at this level (compilation), you should be running very fast unit tests, generally not integration tests. Artifacts/modules are cheap in Maven. War modules in particular should not have a lot of code associated with them -- move the code into Jars and extract the code out of your JSPs etc into classes that go into those Jars. Also when you're working, you don't clean install from the top parent, but instead run it from the module you're working on. At least, this is what we do... Wayne On 11/9/07, EJ Ciramella [EMAIL PROTECTED] wrote: That's incredible, doing that takes 30 - 40 minutes here. Most developers here are used to a 10 build time
Re: maven constantly rebuilding everything
I always assumed this was just the way maven does things :). I think this would be a really useful improvement, thank you! On Nov 8, 2007 9:53 PM, EJ Ciramella [EMAIL PROTECTED] wrote: So no one else has mentioned this? Multiple war files rebuilding every pass? Or jars rebuilding all the time? I'll try to get a patch together for the war stuffs sometime over the next few days. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 2:57 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything This is certainly the right way to do it, but as far as I know/have seen, this is not currently how it is being done. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: Ok, so we're going to copy/paste a solution? Shouldn't there be a generic artifact type jar that jar/war/ear/zip depend upon? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 1:05 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything Probably need to add the addMavenDescriptor option to the war plugin. Its annoying when the plugins aren't all in sync on these common jar issues. I'd copy the code from m-jar-p and if it does what you need it to do, then I'd go file a JIRA and attach your patch. (Thanks EJ.) Or just open a JIRA but you know it will not be resolved as quickly as you require. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: And the saga continues - I can see pom.properties going into the mvn generated war file as well (so that's getting built every time). I see that war doesn't have the addMavenDescriptor option, I can't seem to get either warSourceExcludes or dependentWarExcludes to work either. Any suggestions guys? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:04 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Done! http://jira.codehaus.org/browse/MSOURCES-28 (apparently, I already had an account) To the next issue - install apparently installs regardless of if the jar is new or not, see below: [INFO] Installing E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore- P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P200712-SNAPSHOT\backofficeCore- P200712-SNAPSHOT.jar Since I added the following to my pom, I'd expect this to NOT be happening: plugin artifactIdmaven-jar-plugin/artifactId configuration archive addMavenDescriptorfalse/addMavenDescriptor /archive /configuration /plugin -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:55 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Go here: http://jira.codehaus.org/browse/MSOURCES Open up an account (it's free ;-) ) and fill out a new issue. On Thursday 08 November 2007 16:52, EJ Ciramella wrote: Um, how does one file a jira ticket for something like this? -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:50 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything From the description of the source:jar-plugin (http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I derive that this configuration is not possible in the source-jar. Maybe filing a JIRA might help, until then you can only ignore it (and live with the rebuild every time) or remove the source:jar-run from your POM. On Thursday 08 November 2007 16:33, EJ Ciramella wrote: So I added a snippet of configuration from here: http://jira.codehaus.org/browse/MJAR-7 But the same kind of configuration supplied to the source plugin does nothing (and it too rebuilds the source jar every time even though there are no changes). -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:20 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Rebuilding this same module with -X -e turned on, I see this: [DEBUG] isUp2date: false (Input file E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is newer.) What exactly is this file and how does it get created? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:12 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything So we
RE: maven constantly rebuilding everything
That's incredible, doing that takes 30 - 40 minutes here. Most developers here are used to a 10 build time. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:08 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything I nearly always build clean package or clean install so I expect them to rebuild from scratch every time... So no. ;-) Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: So no one else has mentioned this? Multiple war files rebuilding every pass? Or jars rebuilding all the time? I'll try to get a patch together for the war stuffs sometime over the next few days. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 2:57 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything This is certainly the right way to do it, but as far as I know/have seen, this is not currently how it is being done. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: Ok, so we're going to copy/paste a solution? Shouldn't there be a generic artifact type jar that jar/war/ear/zip depend upon? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 1:05 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything Probably need to add the addMavenDescriptor option to the war plugin. Its annoying when the plugins aren't all in sync on these common jar issues. I'd copy the code from m-jar-p and if it does what you need it to do, then I'd go file a JIRA and attach your patch. (Thanks EJ.) Or just open a JIRA but you know it will not be resolved as quickly as you require. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: And the saga continues - I can see pom.properties going into the mvn generated war file as well (so that's getting built every time). I see that war doesn't have the addMavenDescriptor option, I can't seem to get either warSourceExcludes or dependentWarExcludes to work either. Any suggestions guys? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:04 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Done! http://jira.codehaus.org/browse/MSOURCES-28 (apparently, I already had an account) To the next issue - install apparently installs regardless of if the jar is new or not, see below: [INFO] Installing E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore- P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar Since I added the following to my pom, I'd expect this to NOT be happening: plugin artifactIdmaven-jar-plugin/artifactId configuration archive addMavenDescriptorfalse/addMavenDescriptor /archive /configuration /plugin -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:55 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Go here: http://jira.codehaus.org/browse/MSOURCES Open up an account (it's free ;-) ) and fill out a new issue. On Thursday 08 November 2007 16:52, EJ Ciramella wrote: Um, how does one file a jira ticket for something like this? -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:50 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything From the description of the source:jar-plugin (http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I derive that this configuration is not possible in the source-jar. Maybe filing a JIRA might help, until then you can only ignore it (and live with the rebuild every time) or remove the source:jar-run from your POM. On Thursday 08 November 2007 16:33, EJ Ciramella wrote: So I added a snippet of configuration from here: http://jira.codehaus.org/browse/MJAR-7 But the same kind of configuration supplied to the source plugin does nothing (and it too rebuilds the source jar every time even though there are no changes). -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:20 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Rebuilding this same module with -X -e turned on, I see this: [DEBUG] isUp2date: false (Input file E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties
Re: maven constantly rebuilding everything
Sounds like your projects are entirely too big -- break 'em up a bit. Even 10min builds sounds rather long -- is this compilation only or including testing? And what portion of that time is consumed by your tests -- at this level (compilation), you should be running very fast unit tests, generally not integration tests. Artifacts/modules are cheap in Maven. War modules in particular should not have a lot of code associated with them -- move the code into Jars and extract the code out of your JSPs etc into classes that go into those Jars. Also when you're working, you don't clean install from the top parent, but instead run it from the module you're working on. At least, this is what we do... Wayne On 11/9/07, EJ Ciramella [EMAIL PROTECTED] wrote: That's incredible, doing that takes 30 - 40 minutes here. Most developers here are used to a 10 build time. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:08 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything I nearly always build clean package or clean install so I expect them to rebuild from scratch every time... So no. ;-) Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: So no one else has mentioned this? Multiple war files rebuilding every pass? Or jars rebuilding all the time? I'll try to get a patch together for the war stuffs sometime over the next few days. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 2:57 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything This is certainly the right way to do it, but as far as I know/have seen, this is not currently how it is being done. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: Ok, so we're going to copy/paste a solution? Shouldn't there be a generic artifact type jar that jar/war/ear/zip depend upon? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 1:05 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything Probably need to add the addMavenDescriptor option to the war plugin. Its annoying when the plugins aren't all in sync on these common jar issues. I'd copy the code from m-jar-p and if it does what you need it to do, then I'd go file a JIRA and attach your patch. (Thanks EJ.) Or just open a JIRA but you know it will not be resolved as quickly as you require. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: And the saga continues - I can see pom.properties going into the mvn generated war file as well (so that's getting built every time). I see that war doesn't have the addMavenDescriptor option, I can't seem to get either warSourceExcludes or dependentWarExcludes to work either. Any suggestions guys? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:04 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Done! http://jira.codehaus.org/browse/MSOURCES-28 (apparently, I already had an account) To the next issue - install apparently installs regardless of if the jar is new or not, see below: [INFO] Installing E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore- P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar Since I added the following to my pom, I'd expect this to NOT be happening: plugin artifactIdmaven-jar-plugin/artifactId configuration archive addMavenDescriptorfalse/addMavenDescriptor /archive /configuration /plugin -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:55 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Go here: http://jira.codehaus.org/browse/MSOURCES Open up an account (it's free ;-) ) and fill out a new issue. On Thursday 08 November 2007 16:52, EJ Ciramella wrote: Um, how does one file a jira ticket for something like this? -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:50 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything From the description of the source:jar-plugin (http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I derive that this configuration is not possible in the source-jar. Maybe filing a JIRA might help, until then you
RE: maven constantly rebuilding everything
I'd love to know what people are building and the size of things, I think our project is larger than most (I'm not stepping into a pissing contest, simply stating the facts). We're working on a massive refactoring both in codeline management and actual code refactoring. Even with the refactoring done, that will only help to a certain degree. With testing, we're talking about 1 - 1.5 hours. The resulting assembly for our main application is 195 - 200 mb (full of jsps, images, classes, jars, etc). I wish I could better show you the size of the application (we have three ears and 4 - 5 wars depending on what you're building). There's no real honest to goodness code in the jsps (as it should be), all business logic is handled else where. As a release engineer, it's not my business to make sweeping changes like that. I can make suggestions, but in the end, it's up to development to decide what projects have merit/profit/etc associated with them. It'd be nice if you could work at the lowest directory all the time (the one responsible for building the ear file), but when your change effects a module that the ear you want depends on (or MULTIPLE subprojects), most developers here build from the top. Also, when profiles.xml lives at the root of the overall project and contains 90% the configuration for a developers box, sitting at a lower level, aren't these properties unavailable (doesn't maven only look in the working directory for profiles.xml)? If maven wouldn't try to rebuild every jar and then every war and then every ear, life would be much better. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 8:10 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Sounds like your projects are entirely too big -- break 'em up a bit. Even 10min builds sounds rather long -- is this compilation only or including testing? And what portion of that time is consumed by your tests -- at this level (compilation), you should be running very fast unit tests, generally not integration tests. Artifacts/modules are cheap in Maven. War modules in particular should not have a lot of code associated with them -- move the code into Jars and extract the code out of your JSPs etc into classes that go into those Jars. Also when you're working, you don't clean install from the top parent, but instead run it from the module you're working on. At least, this is what we do... Wayne On 11/9/07, EJ Ciramella [EMAIL PROTECTED] wrote: That's incredible, doing that takes 30 - 40 minutes here. Most developers here are used to a 10 build time. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:08 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything I nearly always build clean package or clean install so I expect them to rebuild from scratch every time... So no. ;-) Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: So no one else has mentioned this? Multiple war files rebuilding every pass? Or jars rebuilding all the time? I'll try to get a patch together for the war stuffs sometime over the next few days. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 2:57 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything This is certainly the right way to do it, but as far as I know/have seen, this is not currently how it is being done. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: Ok, so we're going to copy/paste a solution? Shouldn't there be a generic artifact type jar that jar/war/ear/zip depend upon? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 1:05 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything Probably need to add the addMavenDescriptor option to the war plugin. Its annoying when the plugins aren't all in sync on these common jar issues. I'd copy the code from m-jar-p and if it does what you need it to do, then I'd go file a JIRA and attach your patch. (Thanks EJ.) Or just open a JIRA but you know it will not be resolved as quickly as you require. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: And the saga continues - I can see pom.properties going into the mvn generated war file as well (so that's getting built every time). I see that war doesn't have the addMavenDescriptor option, I can't seem to get either warSourceExcludes or dependentWarExcludes to work either. Any suggestions guys? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:04 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Done
RE: maven constantly rebuilding everything
I've managed to isolate a local project that is small and repeatable. When I
run mvn install, it always reinstalls the jar into the local repository (seems
like another bug with the install plugin):
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\matchServermvn install
-Dtest=none
[INFO] Scanning for projects...
[INFO]
[INFO] Building Match(Server)
[INFO]task-segment: [install]
[INFO]
[INFO] [dependency:unpack-dependencies {execution: unpack}]
[INFO] lty-utils-resources-1.0.0.13.jar already exists in destination.
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] [install:install]
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\matchServer\target\lib\matchServer-P200712-SNAPSHOT.jar
to E:\work\m2\Repository\lty\matchServe
r\P200712-SNAPSHOT\matchServer-P200712-SNAPSHOT.jar
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 3 seconds
[INFO] Finished at: Fri Nov 09 11:04:02 EST 2007
[INFO] Final Memory: 11M/254M
[INFO]
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, November 09, 2007 8:58 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
I'd love to know what people are building and the size of things, I think our
project is larger than most (I'm not stepping into a pissing contest, simply
stating the facts). We're working on a massive refactoring both in codeline
management and actual code refactoring.
Even with the refactoring done, that will only help to a certain degree. With
testing, we're talking about 1 - 1.5 hours.
The resulting assembly for our main application is 195 - 200 mb (full of jsps,
images, classes, jars, etc). I wish I could better show you the size of the
application (we have three ears and 4 - 5 wars depending on what you're
building). There's no real honest to goodness code in the jsps (as it should
be), all business logic is handled else where. As a release engineer, it's not
my business to make sweeping changes like that. I can make suggestions, but in
the end, it's up to development to decide what projects have merit/profit/etc
associated with them.
It'd be nice if you could work at the lowest directory all the time (the one
responsible for building the ear file), but when your change effects a module
that the ear you want depends on (or MULTIPLE subprojects), most developers
here build from the top. Also, when profiles.xml lives at the root of the
overall project and contains 90% the configuration for a developers box,
sitting at a lower level, aren't these properties unavailable (doesn't maven
only look in the working directory for profiles.xml)?
If maven wouldn't try to rebuild every jar and then every war and then every
ear, life would be much better.
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Friday, November 09, 2007 8:10 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
Sounds like your projects are entirely too big -- break 'em up a bit.
Even 10min builds sounds rather long -- is this compilation only or
including testing? And what portion of that time is consumed by your
tests -- at this level (compilation), you should be running very fast
unit tests, generally not integration tests.
Artifacts/modules are cheap in Maven. War modules in particular
should not have a lot of code associated with them -- move the code
into Jars and extract the code out of your JSPs etc into classes that
go into those Jars.
Also when you're working, you don't clean install from the top
parent, but instead run it from the module you're working on. At
least, this is what we do...
Wayne
On 11/9/07, EJ Ciramella [EMAIL PROTECTED] wrote:
That's incredible, doing that takes 30 - 40 minutes here.
Most developers here are used to a 10 build time.
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 11:08 PM
To: Maven Users List
Subject: Re: maven
Re: maven constantly rebuilding everything
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
Are there actually resources being filtered? If so, that would cause
it. Filtered resources are always regenerated (you may be filtering in
a build number or timestamp or something). Thus, the resource always
changes which causes the jar to be rebuilt and re-installed.
Dan
On Friday 09 November 2007, EJ Ciramella wrote:
I've managed to isolate a local project that is small and repeatable.
When I run mvn install, it always reinstalls the jar into the local
repository (seems like another bug with the install plugin):
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\matchServermvn
install -Dtest=none [INFO] Scanning for projects...
[INFO]
--
-- [INFO] Building Match(Server)
[INFO]task-segment: [install]
[INFO]
--
-- [INFO] [dependency:unpack-dependencies {execution: unpack}]
[INFO] lty-utils-resources-1.0.0.13.jar already exists in destination.
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] [install:install]
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\matchServer\target\lib
\matchServer-P200712-SNAPSHOT.jar to
E:\work\m2\Repository\lty\matchServe
r\P200712-SNAPSHOT\matchServer-P200712-SNAPSHOT.jar
[INFO]
--
-- [INFO] BUILD SUCCESSFUL
[INFO]
--
-- [INFO] Total time: 3 seconds
[INFO] Finished at: Fri Nov 09 11:04:02 EST 2007
[INFO] Final Memory: 11M/254M
[INFO]
--
--
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, November 09, 2007 8:58 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
I'd love to know what people are building and the size of things, I
think our project is larger than most (I'm not stepping into a pissing
contest, simply stating the facts). We're working on a massive
refactoring both in codeline management and actual code refactoring.
Even with the refactoring done, that will only help to a certain
degree. With testing, we're talking about 1 - 1.5 hours. The
resulting assembly for our main application is 195 - 200 mb (full of
jsps, images, classes, jars, etc). I wish I could better show you the
size of the application (we have three ears and 4 - 5 wars depending
on what you're building). There's no real honest to goodness code in
the jsps (as it should be), all business logic is handled else where.
As a release engineer, it's not my business to make sweeping changes
like that. I can make suggestions, but in the end, it's up to
development to decide what projects have merit/profit/etc associated
with them.
It'd be nice if you could work at the lowest directory all the time
(the one responsible for building the ear file), but when your change
effects a module that the ear you want depends on (or MULTIPLE
subprojects), most developers here build from the top. Also, when
profiles.xml lives at the root of the overall project and contains 90%
the configuration for a developers box, sitting at a lower level,
aren't these properties unavailable (doesn't maven only look in the
working directory for profiles.xml)?
If maven wouldn't try to rebuild every jar and then every war and then
every ear, life would be much better.
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Friday, November 09, 2007 8:10 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
Sounds like your projects are entirely too big -- break 'em up a bit.
Even 10min builds sounds rather long -- is this compilation only or
including testing? And what portion of that time is consumed by your
tests -- at this level (compilation), you should be running very fast
unit tests, generally not integration tests.
Artifacts/modules are cheap in Maven. War modules in particular
should not have a lot of code associated with them -- move the code
into Jars and extract the code out of your JSPs etc into classes that
go into those Jars
Re: maven constantly rebuilding everything
Interested by this Jira ?
http://jira.codehaus.org/browse/MNG-2854
It seems to be corrected in maven-archiver 2.3 (not released)
You could ask for a release.
Then maven-jar-plugin, maven-ear-plugin, maven-war-plugin, ... will
have to upgrade ...
Damien
2007/11/9, EJ Ciramella [EMAIL PROTECTED]:
I've managed to isolate a local project that is small and repeatable. When I
run mvn install, it always reinstalls the jar into the local repository
(seems like another bug with the install plugin):
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\matchServermvn install
-Dtest=none
[INFO] Scanning for projects...
[INFO]
[INFO] Building Match(Server)
[INFO]task-segment: [install]
[INFO]
[INFO] [dependency:unpack-dependencies {execution: unpack}]
[INFO] lty-utils-resources-1.0.0.13.jar already exists in destination.
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] [install:install]
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\matchServer\target\lib\matchServer-P200712-SNAPSHOT.jar
to E:\work\m2\Repository\lty\matchServe
r\P200712-SNAPSHOT\matchServer-P200712-SNAPSHOT.jar
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 3 seconds
[INFO] Finished at: Fri Nov 09 11:04:02 EST 2007
[INFO] Final Memory: 11M/254M
[INFO]
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, November 09, 2007 8:58 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
I'd love to know what people are building and the size of things, I think our
project is larger than most (I'm not stepping into a pissing contest, simply
stating the facts). We're working on a massive refactoring both in codeline
management and actual code refactoring.
Even with the refactoring done, that will only help to a certain degree.
With testing, we're talking about 1 - 1.5 hours.
The resulting assembly for our main application is 195 - 200 mb (full of
jsps, images, classes, jars, etc). I wish I could better show you the size
of the application (we have three ears and 4 - 5 wars depending on what
you're building). There's no real honest to goodness code in the jsps (as it
should be), all business logic is handled else where. As a release engineer,
it's not my business to make sweeping changes like that. I can make
suggestions, but in the end, it's up to development to decide what projects
have merit/profit/etc associated with them.
It'd be nice if you could work at the lowest directory all the time (the one
responsible for building the ear file), but when your change effects a module
that the ear you want depends on (or MULTIPLE subprojects), most developers
here build from the top. Also, when profiles.xml lives at the root of the
overall project and contains 90% the configuration for a developers box,
sitting at a lower level, aren't these properties unavailable (doesn't maven
only look in the working directory for profiles.xml)?
If maven wouldn't try to rebuild every jar and then every war and then every
ear, life would be much better.
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Friday, November 09, 2007 8:10 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
Sounds like your projects are entirely too big -- break 'em up a bit.
Even 10min builds sounds rather long -- is this compilation only or
including testing? And what portion of that time is consumed by your
tests -- at this level (compilation), you should be running very fast
unit tests, generally not integration tests.
Artifacts/modules are cheap in Maven. War modules in particular
should not have a lot of code associated with them -- move the code
into Jars and extract the code out of your JSPs etc into classes that
go into those Jars.
Also when you're working, you don't clean install from the top
parent, but instead run it from
Re: maven constantly rebuilding everything
It certainly sounds like you are dealing with a large project. Since you mentioned images, I wonder how much of the 200mb is actually code and how much is everything else? I assume you've run an analysis. I've looked into this rebuilding every jar issue at some point. In short, Maven creates a pom.properties file every time it executes in a given module. Thus you *always* have changes, even when you don't. Also the filtered resources thing that Daniel mentioned is another forgotten source of changes. Damien just sent the link to this bug, he must have been reading my mind... ;-) Wayne On 11/9/07, EJ Ciramella [EMAIL PROTECTED] wrote: I'd love to know what people are building and the size of things, I think our project is larger than most (I'm not stepping into a pissing contest, simply stating the facts). We're working on a massive refactoring both in codeline management and actual code refactoring. Even with the refactoring done, that will only help to a certain degree. With testing, we're talking about 1 - 1.5 hours. The resulting assembly for our main application is 195 - 200 mb (full of jsps, images, classes, jars, etc). I wish I could better show you the size of the application (we have three ears and 4 - 5 wars depending on what you're building). There's no real honest to goodness code in the jsps (as it should be), all business logic is handled else where. As a release engineer, it's not my business to make sweeping changes like that. I can make suggestions, but in the end, it's up to development to decide what projects have merit/profit/etc associated with them. It'd be nice if you could work at the lowest directory all the time (the one responsible for building the ear file), but when your change effects a module that the ear you want depends on (or MULTIPLE subprojects), most developers here build from the top. Also, when profiles.xml lives at the root of the overall project and contains 90% the configuration for a developers box, sitting at a lower level, aren't these properties unavailable (doesn't maven only look in the working directory for profiles.xml)? If maven wouldn't try to rebuild every jar and then every war and then every ear, life would be much better. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 8:10 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Sounds like your projects are entirely too big -- break 'em up a bit. Even 10min builds sounds rather long -- is this compilation only or including testing? And what portion of that time is consumed by your tests -- at this level (compilation), you should be running very fast unit tests, generally not integration tests. Artifacts/modules are cheap in Maven. War modules in particular should not have a lot of code associated with them -- move the code into Jars and extract the code out of your JSPs etc into classes that go into those Jars. Also when you're working, you don't clean install from the top parent, but instead run it from the module you're working on. At least, this is what we do... Wayne On 11/9/07, EJ Ciramella [EMAIL PROTECTED] wrote: That's incredible, doing that takes 30 - 40 minutes here. Most developers here are used to a 10 build time. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:08 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything I nearly always build clean package or clean install so I expect them to rebuild from scratch every time... So no. ;-) Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: So no one else has mentioned this? Multiple war files rebuilding every pass? Or jars rebuilding all the time? I'll try to get a patch together for the war stuffs sometime over the next few days. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 2:57 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything This is certainly the right way to do it, but as far as I know/have seen, this is not currently how it is being done. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: Ok, so we're going to copy/paste a solution? Shouldn't there be a generic artifact type jar that jar/war/ear/zip depend upon? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 1:05 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything Probably need to add the addMavenDescriptor option to the war plugin. Its annoying when the plugins aren't all in sync on these common jar issues. I'd copy the code from m-jar-p and if it does what you need it to do, then I'd go file a JIRA and attach your
RE: maven constantly rebuilding everything
Yeah, I'm able to prevent rebuilding of all the jars, not re-downloading the resources as part of the maven-dependency-plugin - so that much is ok. I'm still getting everything installed every time I build even if it didn't have to re-jar the source. Is there a solution/jira for that (I couldn't find anything with my searches). -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 11:59 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything It certainly sounds like you are dealing with a large project. Since you mentioned images, I wonder how much of the 200mb is actually code and how much is everything else? I assume you've run an analysis. I've looked into this rebuilding every jar issue at some point. In short, Maven creates a pom.properties file every time it executes in a given module. Thus you *always* have changes, even when you don't. Also the filtered resources thing that Daniel mentioned is another forgotten source of changes. Damien just sent the link to this bug, he must have been reading my mind... ;-) Wayne On 11/9/07, EJ Ciramella [EMAIL PROTECTED] wrote: I'd love to know what people are building and the size of things, I think our project is larger than most (I'm not stepping into a pissing contest, simply stating the facts). We're working on a massive refactoring both in codeline management and actual code refactoring. Even with the refactoring done, that will only help to a certain degree. With testing, we're talking about 1 - 1.5 hours. The resulting assembly for our main application is 195 - 200 mb (full of jsps, images, classes, jars, etc). I wish I could better show you the size of the application (we have three ears and 4 - 5 wars depending on what you're building). There's no real honest to goodness code in the jsps (as it should be), all business logic is handled else where. As a release engineer, it's not my business to make sweeping changes like that. I can make suggestions, but in the end, it's up to development to decide what projects have merit/profit/etc associated with them. It'd be nice if you could work at the lowest directory all the time (the one responsible for building the ear file), but when your change effects a module that the ear you want depends on (or MULTIPLE subprojects), most developers here build from the top. Also, when profiles.xml lives at the root of the overall project and contains 90% the configuration for a developers box, sitting at a lower level, aren't these properties unavailable (doesn't maven only look in the working directory for profiles.xml)? If maven wouldn't try to rebuild every jar and then every war and then every ear, life would be much better. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 8:10 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Sounds like your projects are entirely too big -- break 'em up a bit. Even 10min builds sounds rather long -- is this compilation only or including testing? And what portion of that time is consumed by your tests -- at this level (compilation), you should be running very fast unit tests, generally not integration tests. Artifacts/modules are cheap in Maven. War modules in particular should not have a lot of code associated with them -- move the code into Jars and extract the code out of your JSPs etc into classes that go into those Jars. Also when you're working, you don't clean install from the top parent, but instead run it from the module you're working on. At least, this is what we do... Wayne On 11/9/07, EJ Ciramella [EMAIL PROTECTED] wrote: That's incredible, doing that takes 30 - 40 minutes here. Most developers here are used to a 10 build time. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:08 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything I nearly always build clean package or clean install so I expect them to rebuild from scratch every time... So no. ;-) Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: So no one else has mentioned this? Multiple war files rebuilding every pass? Or jars rebuilding all the time? I'll try to get a patch together for the war stuffs sometime over the next few days. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 2:57 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything This is certainly the right way to do it, but as far as I know/have seen, this is not currently how it is being done. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: Ok, so we're going to copy/paste a solution? Shouldn't there be a generic artifact type jar that jar/war/ear/zip
RE: maven constantly rebuilding everything
Well, maybe I'm not quite out of the woods. Process-resources always moves some files into classes so I guess this will forever jar stuff up, right? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 1:13 PM To: Maven Users List Subject: RE: maven constantly rebuilding everything Yeah, I'm able to prevent rebuilding of all the jars, not re-downloading the resources as part of the maven-dependency-plugin - so that much is ok. I'm still getting everything installed every time I build even if it didn't have to re-jar the source. Is there a solution/jira for that (I couldn't find anything with my searches). -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 11:59 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything It certainly sounds like you are dealing with a large project. Since you mentioned images, I wonder how much of the 200mb is actually code and how much is everything else? I assume you've run an analysis. I've looked into this rebuilding every jar issue at some point. In short, Maven creates a pom.properties file every time it executes in a given module. Thus you *always* have changes, even when you don't. Also the filtered resources thing that Daniel mentioned is another forgotten source of changes. Damien just sent the link to this bug, he must have been reading my mind... ;-) Wayne On 11/9/07, EJ Ciramella [EMAIL PROTECTED] wrote: I'd love to know what people are building and the size of things, I think our project is larger than most (I'm not stepping into a pissing contest, simply stating the facts). We're working on a massive refactoring both in codeline management and actual code refactoring. Even with the refactoring done, that will only help to a certain degree. With testing, we're talking about 1 - 1.5 hours. The resulting assembly for our main application is 195 - 200 mb (full of jsps, images, classes, jars, etc). I wish I could better show you the size of the application (we have three ears and 4 - 5 wars depending on what you're building). There's no real honest to goodness code in the jsps (as it should be), all business logic is handled else where. As a release engineer, it's not my business to make sweeping changes like that. I can make suggestions, but in the end, it's up to development to decide what projects have merit/profit/etc associated with them. It'd be nice if you could work at the lowest directory all the time (the one responsible for building the ear file), but when your change effects a module that the ear you want depends on (or MULTIPLE subprojects), most developers here build from the top. Also, when profiles.xml lives at the root of the overall project and contains 90% the configuration for a developers box, sitting at a lower level, aren't these properties unavailable (doesn't maven only look in the working directory for profiles.xml)? If maven wouldn't try to rebuild every jar and then every war and then every ear, life would be much better. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 8:10 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Sounds like your projects are entirely too big -- break 'em up a bit. Even 10min builds sounds rather long -- is this compilation only or including testing? And what portion of that time is consumed by your tests -- at this level (compilation), you should be running very fast unit tests, generally not integration tests. Artifacts/modules are cheap in Maven. War modules in particular should not have a lot of code associated with them -- move the code into Jars and extract the code out of your JSPs etc into classes that go into those Jars. Also when you're working, you don't clean install from the top parent, but instead run it from the module you're working on. At least, this is what we do... Wayne On 11/9/07, EJ Ciramella [EMAIL PROTECTED] wrote: That's incredible, doing that takes 30 - 40 minutes here. Most developers here are used to a 10 build time. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:08 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything I nearly always build clean package or clean install so I expect them to rebuild from scratch every time... So no. ;-) Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: So no one else has mentioned this? Multiple war files rebuilding every pass? Or jars rebuilding all the time? I'll try to get a patch together for the war stuffs sometime over the next few days. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 2:57 PM To: Maven Users List Subject: Re: maven constantly
Re: maven constantly rebuilding everything
What command are you running? If you start (or end) your builds with 'clean', it is only logical that Maven rebuilds everything. Also, if you checkout your sources from SCM, Maven can't see that there's no changes and therefor will build everything again. On Thursday 08 November 2007 15:49, EJ Ciramella wrote: I've just noticed kinda a little delemma here. From build to build, when NOTHING has changed inside module A, I can see that its still rebuilding the jar for this particular module. Is there any reason this should be happening? Like say it is set to build a snapshot version? I think it would notice that the source directory doesn't contain any changes and not build. Any help/suggestions would be greatly appreciated. -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven constantly rebuilding everything
So we regularly use mvn install. I didn't think that did a clean anywhere
in its lifecycle.
And yes, I understand that if the sources have changed, it will recompile, etc
on down the line, but there are not source file changes, no sync, just mvn
install then up arrow and run it again and it will build up the jars again,
here's a look at the output from the up arrow pass. Is this because of our
use of snapshot versions or something?
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Backoffice Core Engine
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT.jar
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-source}]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT-sources.jar
[INFO] [install:install]
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT.jar
to E:\work\m2\Repository\lty\backofficeCore\P20
0712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT-sources.jar
to E:\work\m2\Repository\lty\backoffice
Core\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT-sources.jar
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Thu Nov 08 10:08:12 EST 2007
[INFO] Final Memory: 8M/254M
[INFO]
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 9:55 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
What command are you running? If you start (or end) your builds with 'clean',
it is only logical that Maven rebuilds everything.
Also, if you checkout your sources from SCM, Maven can't see that there's no
changes and therefor will build everything again.
On Thursday 08 November 2007 15:49, EJ Ciramella wrote:
I've just noticed kinda a little delemma here. From build to build,
when NOTHING has changed inside module A, I can see that its still
rebuilding the jar for this particular module.
Is there any reason this should be happening? Like say it is set to
build a snapshot version? I think it would notice that the source
directory doesn't contain any changes and not build.
Any help/suggestions would be greatly appreciated.
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
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: maven constantly rebuilding everything
Done!
http://jira.codehaus.org/browse/MSOURCES-28
(apparently, I already had an account)
To the next issue - install apparently installs regardless of if the jar is
new or not, see below:
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-
P200712-SNAPSHOT.jar to
E:\work\m2\Repository\lty\backofficeCore\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar
Since I added the following to my pom, I'd expect this to NOT be happening:
plugin
artifactIdmaven-jar-plugin/artifactId
configuration
archive
addMavenDescriptorfalse/addMavenDescriptor
/archive
/configuration
/plugin
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:55 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
Go here: http://jira.codehaus.org/browse/MSOURCES
Open up an account (it's free ;-) ) and fill out a new issue.
On Thursday 08 November 2007 16:52, EJ Ciramella wrote:
Um, how does one file a jira ticket for something like this?
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:50 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
From the description of the source:jar-plugin
(http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I
derive that this configuration is not possible in the source-jar.
Maybe filing a JIRA might help, until then you can only ignore it (and live
with the rebuild every time) or remove the source:jar-run from your POM.
On Thursday 08 November 2007 16:33, EJ Ciramella wrote:
So I added a snippet of configuration from here:
http://jira.codehaus.org/browse/MJAR-7
But the same kind of configuration supplied to the source plugin does
nothing (and it too rebuilds the source jar every time even though there
are no changes).
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:20 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
Rebuilding this same module with -X -e turned on, I see this:
[DEBUG] isUp2date: false (Input file
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is
newer.)
What exactly is this file and how does it get created?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:12 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
So we regularly use mvn install. I didn't think that did a clean
anywhere in its lifecycle.
And yes, I understand that if the sources have changed, it will
recompile, etc on down the line, but there are not source file changes,
no sync, just mvn install then up arrow and run it again and it will
build up the jars again, here's a look at the output from the up arrow
pass. Is this because of our use of snapshot versions or something?
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in
your local repository will be inaccessible.
[INFO] Scanning for projects...
[INFO]
-
-- - [INFO] Building Backoffice Core Engine
[INFO]task-segment: [install]
[INFO]
-
-- - [INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCor
e- P200712-SNAPSHOT.jar [INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation. [INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-source}]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCor
e- P200712-SNAPSHOT-sources.jar [INFO] [install:install]
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCor
e- P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P20
0712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar
RE: maven constantly rebuilding everything
Um, how does one file a jira ticket for something like this?
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:50 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
From the description of the source:jar-plugin
(http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I derive
that this configuration is not possible in the source-jar.
Maybe filing a JIRA might help, until then you can only ignore it (and live
with the rebuild every time) or remove the source:jar-run from your POM.
On Thursday 08 November 2007 16:33, EJ Ciramella wrote:
So I added a snippet of configuration from here:
http://jira.codehaus.org/browse/MJAR-7
But the same kind of configuration supplied to the source plugin does
nothing (and it too rebuilds the source jar every time even though there
are no changes).
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:20 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
Rebuilding this same module with -X -e turned on, I see this:
[DEBUG] isUp2date: false (Input file
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is
newer.)
What exactly is this file and how does it get created?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:12 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
So we regularly use mvn install. I didn't think that did a clean
anywhere in its lifecycle.
And yes, I understand that if the sources have changed, it will recompile,
etc on down the line, but there are not source file changes, no sync, just
mvn install then up arrow and run it again and it will build up the jars
again, here's a look at the output from the up arrow pass. Is this
because of our use of snapshot versions or something?
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local repository will be inaccessible.
[INFO] Scanning for projects...
[INFO]
---
- [INFO] Building Backoffice Core Engine
[INFO]task-segment: [install]
[INFO]
---
- [INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-
P200712-SNAPSHOT.jar [INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation. [INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-source}]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-
P200712-SNAPSHOT-sources.jar [INFO] [install:install]
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-
P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P20
0712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-
P200712-SNAPSHOT-sources.jar to E:\work\m2\Repository\lty\backoffice
Core\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT-sources.jar
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Thu Nov 08 10:08:12 EST 2007
[INFO] Final Memory: 8M/254M
[INFO]
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 9:55 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
What command are you running? If you start (or end) your builds with
'clean', it is only logical that Maven rebuilds everything.
Also, if you checkout your sources from SCM, Maven can't see that there's
no changes and therefor will build everything again.
On Thursday 08 November 2007 15:49, EJ Ciramella wrote:
I've just noticed kinda a little delemma here. From build to build,
when NOTHING
Re: maven constantly rebuilding everything
From the description of the source:jar-plugin
(http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I derive
that this configuration is not possible in the source-jar.
Maybe filing a JIRA might help, until then you can only ignore it (and live
with the rebuild every time) or remove the source:jar-run from your POM.
On Thursday 08 November 2007 16:33, EJ Ciramella wrote:
So I added a snippet of configuration from here:
http://jira.codehaus.org/browse/MJAR-7
But the same kind of configuration supplied to the source plugin does
nothing (and it too rebuilds the source jar every time even though there
are no changes).
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:20 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
Rebuilding this same module with -X -e turned on, I see this:
[DEBUG] isUp2date: false (Input file
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is
newer.)
What exactly is this file and how does it get created?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:12 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
So we regularly use mvn install. I didn't think that did a clean
anywhere in its lifecycle.
And yes, I understand that if the sources have changed, it will recompile,
etc on down the line, but there are not source file changes, no sync, just
mvn install then up arrow and run it again and it will build up the jars
again, here's a look at the output from the up arrow pass. Is this
because of our use of snapshot versions or something?
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local repository will be inaccessible.
[INFO] Scanning for projects...
[INFO]
---
- [INFO] Building Backoffice Core Engine
[INFO]task-segment: [install]
[INFO]
---
- [INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-
P200712-SNAPSHOT.jar [INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation. [INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-source}]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-
P200712-SNAPSHOT-sources.jar [INFO] [install:install]
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-
P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P20
0712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-
P200712-SNAPSHOT-sources.jar to E:\work\m2\Repository\lty\backoffice
Core\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT-sources.jar
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Thu Nov 08 10:08:12 EST 2007
[INFO] Final Memory: 8M/254M
[INFO]
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 9:55 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
What command are you running? If you start (or end) your builds with
'clean', it is only logical that Maven rebuilds everything.
Also, if you checkout your sources from SCM, Maven can't see that there's
no changes and therefor will build everything again.
On Thursday 08 November 2007 15:49, EJ Ciramella wrote:
I've just noticed kinda a little delemma here. From build to build,
when NOTHING has changed inside module A, I can see that its still
rebuilding the jar for this particular module.
Is there any reason this should be happening? Like say it is set to
build a snapshot version? I think it would notice that the source
directory
RE: maven constantly rebuilding everything
So I added a snippet of configuration from here:
http://jira.codehaus.org/browse/MJAR-7
But the same kind of configuration supplied to the source plugin does nothing
(and it too rebuilds the source jar every time even though there are no
changes).
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:20 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
Rebuilding this same module with -X -e turned on, I see this:
[DEBUG] isUp2date: false (Input file
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is newer.)
What exactly is this file and how does it get created?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:12 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
So we regularly use mvn install. I didn't think that did a clean anywhere
in its lifecycle.
And yes, I understand that if the sources have changed, it will recompile, etc
on down the line, but there are not source file changes, no sync, just mvn
install then up arrow and run it again and it will build up the jars again,
here's a look at the output from the up arrow pass. Is this because of our
use of snapshot versions or something?
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Backoffice Core Engine
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT.jar
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-source}]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT-sources.jar
[INFO] [install:install]
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT.jar
to E:\work\m2\Repository\lty\backofficeCore\P20
0712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT-sources.jar
to E:\work\m2\Repository\lty\backoffice
Core\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT-sources.jar
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Thu Nov 08 10:08:12 EST 2007
[INFO] Final Memory: 8M/254M
[INFO]
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 9:55 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
What command are you running? If you start (or end) your builds with 'clean',
it is only logical that Maven rebuilds everything.
Also, if you checkout your sources from SCM, Maven can't see that there's no
changes and therefor will build everything again.
On Thursday 08 November 2007 15:49, EJ Ciramella wrote:
I've just noticed kinda a little delemma here. From build to build,
when NOTHING has changed inside module A, I can see that its still
rebuilding the jar for this particular module.
Is there any reason this should be happening? Like say it is set to
build a snapshot version? I think it would notice that the source
directory doesn't contain any changes and not build.
Any help/suggestions would be greatly appreciated.
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
RE: maven constantly rebuilding everything
Rebuilding this same module with -X -e turned on, I see this:
[DEBUG] isUp2date: false (Input file
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is newer.)
What exactly is this file and how does it get created?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:12 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
So we regularly use mvn install. I didn't think that did a clean anywhere
in its lifecycle.
And yes, I understand that if the sources have changed, it will recompile, etc
on down the line, but there are not source file changes, no sync, just mvn
install then up arrow and run it again and it will build up the jars again,
here's a look at the output from the up arrow pass. Is this because of our
use of snapshot versions or something?
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Backoffice Core Engine
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT.jar
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-source}]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT-sources.jar
[INFO] [install:install]
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT.jar
to E:\work\m2\Repository\lty\backofficeCore\P20
0712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT-sources.jar
to E:\work\m2\Repository\lty\backoffice
Core\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT-sources.jar
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Thu Nov 08 10:08:12 EST 2007
[INFO] Final Memory: 8M/254M
[INFO]
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 9:55 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
What command are you running? If you start (or end) your builds with 'clean',
it is only logical that Maven rebuilds everything.
Also, if you checkout your sources from SCM, Maven can't see that there's no
changes and therefor will build everything again.
On Thursday 08 November 2007 15:49, EJ Ciramella wrote:
I've just noticed kinda a little delemma here. From build to build,
when NOTHING has changed inside module A, I can see that its still
rebuilding the jar for this particular module.
Is there any reason this should be happening? Like say it is set to
build a snapshot version? I think it would notice that the source
directory doesn't contain any changes and not build.
Any help/suggestions would be greatly appreciated.
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven constantly rebuilding everything
Go here: http://jira.codehaus.org/browse/MSOURCES
Open up an account (it's free ;-) ) and fill out a new issue.
On Thursday 08 November 2007 16:52, EJ Ciramella wrote:
Um, how does one file a jira ticket for something like this?
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:50 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
From the description of the source:jar-plugin
(http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I
derive that this configuration is not possible in the source-jar.
Maybe filing a JIRA might help, until then you can only ignore it (and live
with the rebuild every time) or remove the source:jar-run from your POM.
On Thursday 08 November 2007 16:33, EJ Ciramella wrote:
So I added a snippet of configuration from here:
http://jira.codehaus.org/browse/MJAR-7
But the same kind of configuration supplied to the source plugin does
nothing (and it too rebuilds the source jar every time even though there
are no changes).
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:20 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
Rebuilding this same module with -X -e turned on, I see this:
[DEBUG] isUp2date: false (Input file
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is
newer.)
What exactly is this file and how does it get created?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:12 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
So we regularly use mvn install. I didn't think that did a clean
anywhere in its lifecycle.
And yes, I understand that if the sources have changed, it will
recompile, etc on down the line, but there are not source file changes,
no sync, just mvn install then up arrow and run it again and it will
build up the jars again, here's a look at the output from the up arrow
pass. Is this because of our use of snapshot versions or something?
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in
your local repository will be inaccessible.
[INFO] Scanning for projects...
[INFO]
-
-- - [INFO] Building Backoffice Core Engine
[INFO]task-segment: [install]
[INFO]
-
-- - [INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCor
e- P200712-SNAPSHOT.jar [INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation. [INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-source}]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCor
e- P200712-SNAPSHOT-sources.jar [INFO] [install:install]
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCor
e- P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P20
0712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCor
e- P200712-SNAPSHOT-sources.jar to E:\work\m2\Repository\lty\backoffice
Core\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT-sources.jar [INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Thu Nov 08 10:08:12 EST 2007
[INFO] Final Memory: 8M/254M
[INFO]
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 9:55 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
What command are you running? If you start (or end) your builds with
'clean', it is only logical that Maven rebuilds
RE: maven constantly rebuilding everything
And the saga continues - I can see pom.properties going into the mvn generated war file as well (so that's getting built every time). I see that war doesn't have the addMavenDescriptor option, I can't seem to get either warSourceExcludes or dependentWarExcludes to work either. Any suggestions guys? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:04 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Done! http://jira.codehaus.org/browse/MSOURCES-28 (apparently, I already had an account) To the next issue - install apparently installs regardless of if the jar is new or not, see below: [INFO] Installing E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore- P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar Since I added the following to my pom, I'd expect this to NOT be happening: plugin artifactIdmaven-jar-plugin/artifactId configuration archive addMavenDescriptorfalse/addMavenDescriptor /archive /configuration /plugin -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:55 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Go here: http://jira.codehaus.org/browse/MSOURCES Open up an account (it's free ;-) ) and fill out a new issue. On Thursday 08 November 2007 16:52, EJ Ciramella wrote: Um, how does one file a jira ticket for something like this? -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:50 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything From the description of the source:jar-plugin (http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I derive that this configuration is not possible in the source-jar. Maybe filing a JIRA might help, until then you can only ignore it (and live with the rebuild every time) or remove the source:jar-run from your POM. On Thursday 08 November 2007 16:33, EJ Ciramella wrote: So I added a snippet of configuration from here: http://jira.codehaus.org/browse/MJAR-7 But the same kind of configuration supplied to the source plugin does nothing (and it too rebuilds the source jar every time even though there are no changes). -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:20 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Rebuilding this same module with -X -e turned on, I see this: [DEBUG] isUp2date: false (Input file E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is newer.) What exactly is this file and how does it get created? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:12 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything So we regularly use mvn install. I didn't think that did a clean anywhere in its lifecycle. And yes, I understand that if the sources have changed, it will recompile, etc on down the line, but there are not source file changes, no sync, just mvn install then up arrow and run it again and it will build up the jars again, here's a look at the output from the up arrow pass. Is this because of our use of snapshot versions or something? [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] - -- - [INFO] Building Backoffice Core Engine [INFO]task-segment: [install] [INFO] - -- - [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] Surefire report directory: E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory --- T E S T S --- There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [jar:jar] [INFO] Building jar: E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCor e- P200712-SNAPSHOT.jar [INFO] Preparing source:jar [WARNING] Removing: jar from forked lifecycle, to prevent
Re: maven constantly rebuilding everything
Probably need to add the addMavenDescriptor option to the war plugin. Its annoying when the plugins aren't all in sync on these common jar issues. I'd copy the code from m-jar-p and if it does what you need it to do, then I'd go file a JIRA and attach your patch. (Thanks EJ.) Or just open a JIRA but you know it will not be resolved as quickly as you require. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: And the saga continues - I can see pom.properties going into the mvn generated war file as well (so that's getting built every time). I see that war doesn't have the addMavenDescriptor option, I can't seem to get either warSourceExcludes or dependentWarExcludes to work either. Any suggestions guys? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:04 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Done! http://jira.codehaus.org/browse/MSOURCES-28 (apparently, I already had an account) To the next issue - install apparently installs regardless of if the jar is new or not, see below: [INFO] Installing E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore- P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar Since I added the following to my pom, I'd expect this to NOT be happening: plugin artifactIdmaven-jar-plugin/artifactId configuration archive addMavenDescriptorfalse/addMavenDescriptor /archive /configuration /plugin -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:55 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Go here: http://jira.codehaus.org/browse/MSOURCES Open up an account (it's free ;-) ) and fill out a new issue. On Thursday 08 November 2007 16:52, EJ Ciramella wrote: Um, how does one file a jira ticket for something like this? -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:50 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything From the description of the source:jar-plugin (http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I derive that this configuration is not possible in the source-jar. Maybe filing a JIRA might help, until then you can only ignore it (and live with the rebuild every time) or remove the source:jar-run from your POM. On Thursday 08 November 2007 16:33, EJ Ciramella wrote: So I added a snippet of configuration from here: http://jira.codehaus.org/browse/MJAR-7 But the same kind of configuration supplied to the source plugin does nothing (and it too rebuilds the source jar every time even though there are no changes). -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:20 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Rebuilding this same module with -X -e turned on, I see this: [DEBUG] isUp2date: false (Input file E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is newer.) What exactly is this file and how does it get created? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:12 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything So we regularly use mvn install. I didn't think that did a clean anywhere in its lifecycle. And yes, I understand that if the sources have changed, it will recompile, etc on down the line, but there are not source file changes, no sync, just mvn install then up arrow and run it again and it will build up the jars again, here's a look at the output from the up arrow pass. Is this because of our use of snapshot versions or something? [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] - -- - [INFO] Building Backoffice Core Engine [INFO]task-segment: [install] [INFO] - -- - [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] Surefire report
RE: maven constantly rebuilding everything
Ok, so we're going to copy/paste a solution? Shouldn't there be a generic artifact type jar that jar/war/ear/zip depend upon? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 1:05 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything Probably need to add the addMavenDescriptor option to the war plugin. Its annoying when the plugins aren't all in sync on these common jar issues. I'd copy the code from m-jar-p and if it does what you need it to do, then I'd go file a JIRA and attach your patch. (Thanks EJ.) Or just open a JIRA but you know it will not be resolved as quickly as you require. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: And the saga continues - I can see pom.properties going into the mvn generated war file as well (so that's getting built every time). I see that war doesn't have the addMavenDescriptor option, I can't seem to get either warSourceExcludes or dependentWarExcludes to work either. Any suggestions guys? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:04 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Done! http://jira.codehaus.org/browse/MSOURCES-28 (apparently, I already had an account) To the next issue - install apparently installs regardless of if the jar is new or not, see below: [INFO] Installing E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore- P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar Since I added the following to my pom, I'd expect this to NOT be happening: plugin artifactIdmaven-jar-plugin/artifactId configuration archive addMavenDescriptorfalse/addMavenDescriptor /archive /configuration /plugin -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:55 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Go here: http://jira.codehaus.org/browse/MSOURCES Open up an account (it's free ;-) ) and fill out a new issue. On Thursday 08 November 2007 16:52, EJ Ciramella wrote: Um, how does one file a jira ticket for something like this? -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:50 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything From the description of the source:jar-plugin (http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I derive that this configuration is not possible in the source-jar. Maybe filing a JIRA might help, until then you can only ignore it (and live with the rebuild every time) or remove the source:jar-run from your POM. On Thursday 08 November 2007 16:33, EJ Ciramella wrote: So I added a snippet of configuration from here: http://jira.codehaus.org/browse/MJAR-7 But the same kind of configuration supplied to the source plugin does nothing (and it too rebuilds the source jar every time even though there are no changes). -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:20 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Rebuilding this same module with -X -e turned on, I see this: [DEBUG] isUp2date: false (Input file E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is newer.) What exactly is this file and how does it get created? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:12 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything So we regularly use mvn install. I didn't think that did a clean anywhere in its lifecycle. And yes, I understand that if the sources have changed, it will recompile, etc on down the line, but there are not source file changes, no sync, just mvn install then up arrow and run it again and it will build up the jars again, here's a look at the output from the up arrow pass. Is this because of our use of snapshot versions or something? [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] - -- - [INFO] Building Backoffice Core Engine [INFO]task-segment: [install] [INFO] - -- - [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO
Re: maven constantly rebuilding everything
This is certainly the right way to do it, but as far as I know/have seen, this is not currently how it is being done. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: Ok, so we're going to copy/paste a solution? Shouldn't there be a generic artifact type jar that jar/war/ear/zip depend upon? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 1:05 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything Probably need to add the addMavenDescriptor option to the war plugin. Its annoying when the plugins aren't all in sync on these common jar issues. I'd copy the code from m-jar-p and if it does what you need it to do, then I'd go file a JIRA and attach your patch. (Thanks EJ.) Or just open a JIRA but you know it will not be resolved as quickly as you require. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: And the saga continues - I can see pom.properties going into the mvn generated war file as well (so that's getting built every time). I see that war doesn't have the addMavenDescriptor option, I can't seem to get either warSourceExcludes or dependentWarExcludes to work either. Any suggestions guys? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:04 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Done! http://jira.codehaus.org/browse/MSOURCES-28 (apparently, I already had an account) To the next issue - install apparently installs regardless of if the jar is new or not, see below: [INFO] Installing E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore- P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar Since I added the following to my pom, I'd expect this to NOT be happening: plugin artifactIdmaven-jar-plugin/artifactId configuration archive addMavenDescriptorfalse/addMavenDescriptor /archive /configuration /plugin -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:55 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Go here: http://jira.codehaus.org/browse/MSOURCES Open up an account (it's free ;-) ) and fill out a new issue. On Thursday 08 November 2007 16:52, EJ Ciramella wrote: Um, how does one file a jira ticket for something like this? -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:50 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything From the description of the source:jar-plugin (http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I derive that this configuration is not possible in the source-jar. Maybe filing a JIRA might help, until then you can only ignore it (and live with the rebuild every time) or remove the source:jar-run from your POM. On Thursday 08 November 2007 16:33, EJ Ciramella wrote: So I added a snippet of configuration from here: http://jira.codehaus.org/browse/MJAR-7 But the same kind of configuration supplied to the source plugin does nothing (and it too rebuilds the source jar every time even though there are no changes). -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:20 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Rebuilding this same module with -X -e turned on, I see this: [DEBUG] isUp2date: false (Input file E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is newer.) What exactly is this file and how does it get created? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:12 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything So we regularly use mvn install. I didn't think that did a clean anywhere in its lifecycle. And yes, I understand that if the sources have changed, it will recompile, etc on down the line, but there are not source file changes, no sync, just mvn install then up arrow and run it again and it will build up the jars again, here's a look at the output from the up arrow pass. Is this because of our use of snapshot versions or something? [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO
RE: maven constantly rebuilding everything
I'm not sure, but either way, nothing has changed in the source tree. Neither jar should be rebuilt for any reason. -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 2:03 PM To: Maven Users List Subject: RE: maven constantly rebuilding everything Not sure if the install-plugin checks if the file has been built, but if so, could it be it installs the JAR because it sees the source-jar is updated? Or did you (temporarily) remove it from the POM? Done! http://jira.codehaus.org/browse/MSOURCES-28 (apparently, I already had an account) To the next issue - install apparently installs regardless of if the jar is new or not, see below: [INFO] Installing E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore- P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar Since I added the following to my pom, I'd expect this to NOT be happening: plugin artifactIdmaven-jar-plugin/artifactId configuration archive addMavenDescriptorfalse/addMavenDescriptor /archive /configuration /plugin -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:55 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Go here: http://jira.codehaus.org/browse/MSOURCES Open up an account (it's free ;-) ) and fill out a new issue. On Thursday 08 November 2007 16:52, EJ Ciramella wrote: Um, how does one file a jira ticket for something like this? -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:50 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything From the description of the source:jar-plugin (http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I derive that this configuration is not possible in the source-jar. Maybe filing a JIRA might help, until then you can only ignore it (and live with the rebuild every time) or remove the source:jar-run from your POM. On Thursday 08 November 2007 16:33, EJ Ciramella wrote: So I added a snippet of configuration from here: http://jira.codehaus.org/browse/MJAR-7 But the same kind of configuration supplied to the source plugin does nothing (and it too rebuilds the source jar every time even though there are no changes). -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:20 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Rebuilding this same module with -X -e turned on, I see this: [DEBUG] isUp2date: false (Input file E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is newer.) What exactly is this file and how does it get created? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:12 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything So we regularly use mvn install. I didn't think that did a clean anywhere in its lifecycle. And yes, I understand that if the sources have changed, it will recompile, etc on down the line, but there are not source file changes, no sync, just mvn install then up arrow and run it again and it will build up the jars again, here's a look at the output from the up arrow pass. Is this because of our use of snapshot versions or something? [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] - -- - [INFO] Building Backoffice Core Engine [INFO]task-segment: [install] [INFO] - -- - [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] Surefire report directory: E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory --- T E S T S --- There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [jar:jar] [INFO] Building jar: E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCor e- P200712-SNAPSHOT.jar [INFO] Preparing source:jar [WARNING] Removing: jar
RE: maven constantly rebuilding everything
Not sure if the install-plugin checks if the file has been built, but if
so, could it be it installs the JAR because it sees the source-jar is
updated? Or did you (temporarily) remove it from the POM?
Done!
http://jira.codehaus.org/browse/MSOURCES-28
(apparently, I already had an account)
To the next issue - install apparently installs regardless of if the jar
is new or not, see below:
[INFO] Installing
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-
P200712-SNAPSHOT.jar to
E:\work\m2\Repository\lty\backofficeCore\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar
Since I added the following to my pom, I'd expect this to NOT be
happening:
plugin
artifactIdmaven-jar-plugin/artifactId
configuration
archive
addMavenDescriptorfalse/addMavenDescriptor
/archive
/configuration
/plugin
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:55 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
Go here: http://jira.codehaus.org/browse/MSOURCES
Open up an account (it's free ;-) ) and fill out a new issue.
On Thursday 08 November 2007 16:52, EJ Ciramella wrote:
Um, how does one file a jira ticket for something like this?
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:50 AM
To: Maven Users List
Subject: Re: maven constantly rebuilding everything
From the description of the source:jar-plugin
(http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I
derive that this configuration is not possible in the source-jar.
Maybe filing a JIRA might help, until then you can only ignore it (and
live
with the rebuild every time) or remove the source:jar-run from your POM.
On Thursday 08 November 2007 16:33, EJ Ciramella wrote:
So I added a snippet of configuration from here:
http://jira.codehaus.org/browse/MJAR-7
But the same kind of configuration supplied to the source plugin does
nothing (and it too rebuilds the source jar every time even though
there
are no changes).
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:20 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
Rebuilding this same module with -X -e turned on, I see this:
[DEBUG] isUp2date: false (Input file
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is
newer.)
What exactly is this file and how does it get created?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 10:12 AM
To: Maven Users List
Subject: RE: maven constantly rebuilding everything
So we regularly use mvn install. I didn't think that did a clean
anywhere in its lifecycle.
And yes, I understand that if the sources have changed, it will
recompile, etc on down the line, but there are not source file
changes,
no sync, just mvn install then up arrow and run it again and it will
build up the jars again, here's a look at the output from the up
arrow
pass. Is this because of our use of snapshot versions or something?
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in
your local repository will be inaccessible.
[INFO] Scanning for projects...
[INFO]
-
-- - [INFO] Building Backoffice Core Engine
[INFO]task-segment: [install]
[INFO]
-
-- - [INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCor
e- P200712-SNAPSHOT.jar [INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation. [INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-source}]
[INFO] Building jar:
E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCor
e- P200712-SNAPSHOT-sources.jar [INFO] [install:install
RE: maven constantly rebuilding everything
So no one else has mentioned this? Multiple war files rebuilding every pass? Or jars rebuilding all the time? I'll try to get a patch together for the war stuffs sometime over the next few days. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 2:57 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything This is certainly the right way to do it, but as far as I know/have seen, this is not currently how it is being done. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: Ok, so we're going to copy/paste a solution? Shouldn't there be a generic artifact type jar that jar/war/ear/zip depend upon? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 1:05 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything Probably need to add the addMavenDescriptor option to the war plugin. Its annoying when the plugins aren't all in sync on these common jar issues. I'd copy the code from m-jar-p and if it does what you need it to do, then I'd go file a JIRA and attach your patch. (Thanks EJ.) Or just open a JIRA but you know it will not be resolved as quickly as you require. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: And the saga continues - I can see pom.properties going into the mvn generated war file as well (so that's getting built every time). I see that war doesn't have the addMavenDescriptor option, I can't seem to get either warSourceExcludes or dependentWarExcludes to work either. Any suggestions guys? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:04 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Done! http://jira.codehaus.org/browse/MSOURCES-28 (apparently, I already had an account) To the next issue - install apparently installs regardless of if the jar is new or not, see below: [INFO] Installing E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore- P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar Since I added the following to my pom, I'd expect this to NOT be happening: plugin artifactIdmaven-jar-plugin/artifactId configuration archive addMavenDescriptorfalse/addMavenDescriptor /archive /configuration /plugin -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:55 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Go here: http://jira.codehaus.org/browse/MSOURCES Open up an account (it's free ;-) ) and fill out a new issue. On Thursday 08 November 2007 16:52, EJ Ciramella wrote: Um, how does one file a jira ticket for something like this? -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:50 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything From the description of the source:jar-plugin (http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I derive that this configuration is not possible in the source-jar. Maybe filing a JIRA might help, until then you can only ignore it (and live with the rebuild every time) or remove the source:jar-run from your POM. On Thursday 08 November 2007 16:33, EJ Ciramella wrote: So I added a snippet of configuration from here: http://jira.codehaus.org/browse/MJAR-7 But the same kind of configuration supplied to the source plugin does nothing (and it too rebuilds the source jar every time even though there are no changes). -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:20 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Rebuilding this same module with -X -e turned on, I see this: [DEBUG] isUp2date: false (Input file E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is newer.) What exactly is this file and how does it get created? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:12 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything So we regularly use mvn install. I didn't think that did a clean anywhere in its lifecycle. And yes, I understand that if the sources have changed, it will recompile, etc on down the line, but there are not source file changes, no sync, just mvn install then up arrow and run it again
Re: maven constantly rebuilding everything
I nearly always build clean package or clean install so I expect them to rebuild from scratch every time... So no. ;-) Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: So no one else has mentioned this? Multiple war files rebuilding every pass? Or jars rebuilding all the time? I'll try to get a patch together for the war stuffs sometime over the next few days. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 2:57 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything This is certainly the right way to do it, but as far as I know/have seen, this is not currently how it is being done. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: Ok, so we're going to copy/paste a solution? Shouldn't there be a generic artifact type jar that jar/war/ear/zip depend upon? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 1:05 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything Probably need to add the addMavenDescriptor option to the war plugin. Its annoying when the plugins aren't all in sync on these common jar issues. I'd copy the code from m-jar-p and if it does what you need it to do, then I'd go file a JIRA and attach your patch. (Thanks EJ.) Or just open a JIRA but you know it will not be resolved as quickly as you require. Wayne On 11/8/07, EJ Ciramella [EMAIL PROTECTED] wrote: And the saga continues - I can see pom.properties going into the mvn generated war file as well (so that's getting built every time). I see that war doesn't have the addMavenDescriptor option, I can't seem to get either warSourceExcludes or dependentWarExcludes to work either. Any suggestions guys? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 11:04 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Done! http://jira.codehaus.org/browse/MSOURCES-28 (apparently, I already had an account) To the next issue - install apparently installs regardless of if the jar is new or not, see below: [INFO] Installing E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore- P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar Since I added the following to my pom, I'd expect this to NOT be happening: plugin artifactIdmaven-jar-plugin/artifactId configuration archive addMavenDescriptorfalse/addMavenDescriptor /archive /configuration /plugin -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:55 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything Go here: http://jira.codehaus.org/browse/MSOURCES Open up an account (it's free ;-) ) and fill out a new issue. On Thursday 08 November 2007 16:52, EJ Ciramella wrote: Um, how does one file a jira ticket for something like this? -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:50 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything From the description of the source:jar-plugin (http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html), I derive that this configuration is not possible in the source-jar. Maybe filing a JIRA might help, until then you can only ignore it (and live with the rebuild every time) or remove the source:jar-run from your POM. On Thursday 08 November 2007 16:33, EJ Ciramella wrote: So I added a snippet of configuration from here: http://jira.codehaus.org/browse/MJAR-7 But the same kind of configuration supplied to the source plugin does nothing (and it too rebuilds the source jar every time even though there are no changes). -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:20 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Rebuilding this same module with -X -e turned on, I see this: [DEBUG] isUp2date: false (Input file E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is newer.) What exactly is this file and how does it get created? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:12 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything
