[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
[ https://jira.codehaus.org/browse/MINSTALL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318489#comment-318489 ] Henning Gross commented on MINSTALL-94: --- Actually I dont get the behaviour with the pom-packaging because the pom needs to be interpreted anyway. Feels like a bug to me. But has nothing to do with mvn-install. You have been a great help. Thank you. > Optional: limit install to packaging x and or make install plugin not fail if > no artifacts were created for some modules. > - > > Key: MINSTALL-94 > URL: https://jira.codehaus.org/browse/MINSTALL-94 > Project: Maven 2.x Install Plugin > Issue Type: Improvement >Reporter: Henning Gross >Assignee: Robert Scholte > Attachments: MINSTALL-94.patch, MINSTALL-94.zip, MINSTALL-94.zip > > > Background: I am working in a huge project with a lot of modules having a lot > of javascript-optimization and stuff happening in lifecycle-steps after > compile. This results in bad performance on jenkins. I would like to run > mvn compile install:install as I only need the jars/libs to be installed and > not the wars (and more important I do not need them to be built). > Please introduce Parameters like > war > or > false<... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
[
https://jira.codehaus.org/browse/MINSTALL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MINSTALL-94.
--
Resolution: Won't Fix
Assignee: Robert Scholte
If you take a good look at the message, you should see that Maven is looking
for
{{MINSTALL-94:mi94-some-commons-module:jar:1.0-SNAPSHOT}}, but that project has
packaging-type {{pom}}, so no wonder it wasn't found. Removing the packaging
type makes the build succeed.
> Optional: limit install to packaging x and or make install plugin not fail if
> no artifacts were created for some modules.
> -
>
> Key: MINSTALL-94
> URL: https://jira.codehaus.org/browse/MINSTALL-94
> Project: Maven 2.x Install Plugin
> Issue Type: Improvement
>Reporter: Henning Gross
>Assignee: Robert Scholte
> Attachments: MINSTALL-94.patch, MINSTALL-94.zip, MINSTALL-94.zip
>
>
> Background: I am working in a huge project with a lot of modules having a lot
> of javascript-optimization and stuff happening in lifecycle-steps after
> compile. This results in bad performance on jenkins. I would like to run
> mvn compile install:install as I only need the jars/libs to be installed and
> not the wars (and more important I do not need them to be built).
> Please introduce Parameters like
> war
> or
> false<...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
[ https://jira.codehaus.org/browse/MINSTALL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henning Gross updated MINSTALL-94: -- Attachment: MINSTALL-94.zip > Optional: limit install to packaging x and or make install plugin not fail if > no artifacts were created for some modules. > - > > Key: MINSTALL-94 > URL: https://jira.codehaus.org/browse/MINSTALL-94 > Project: Maven 2.x Install Plugin > Issue Type: Improvement >Reporter: Henning Gross > Attachments: MINSTALL-94.patch, MINSTALL-94.zip, MINSTALL-94.zip > > > Background: I am working in a huge project with a lot of modules having a lot > of javascript-optimization and stuff happening in lifecycle-steps after > compile. This results in bad performance on jenkins. I would like to run > mvn compile install:install as I only need the jars/libs to be installed and > not the wars (and more important I do not need them to be built). > Please introduce Parameters like > war > or > false<... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
[ https://jira.codehaus.org/browse/MINSTALL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318482#comment-318482 ] Henning Gross commented on MINSTALL-94: --- Someone at some point thought that the build should break on test failure as well. Someone did have a valid use-case and that when the option to not fail the build on test failure was added. Some time later (not long ago) surefire introduced another parameter to not fail if not tests werde found for a specified filter. Just to proof thath making behaviour configurable is not that uncommon. What you say about package seems to be true. I thought so before, then did a test run which succeeded and I did not question why. Maybe I simply forgot to run clean (me idiot). I just set up a test project and it was as expected and stated by you. The maven3-Feature you named does only work with direct dependencies I guess. I added a zip to demonstrate the issue. It will fail when running mvn clean test. Anyway. I was mistaken and you may close this issue. We need to find another way. Either by making sure that there are only direct inner-module-dependencies or by making sure that those libs are built independently. > Optional: limit install to packaging x and or make install plugin not fail if > no artifacts were created for some modules. > - > > Key: MINSTALL-94 > URL: https://jira.codehaus.org/browse/MINSTALL-94 > Project: Maven 2.x Install Plugin > Issue Type: Improvement >Reporter: Henning Gross > Attachments: MINSTALL-94.patch, MINSTALL-94.zip > > > Background: I am working in a huge project with a lot of modules having a lot > of javascript-optimization and stuff happening in lifecycle-steps after > compile. This results in bad performance on jenkins. I would like to run > mvn compile install:install as I only need the jars/libs to be installed and > not the wars (and more important I do not need them to be built). > Please introduce Parameters like > war > or > false<... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
[ https://jira.codehaus.org/browse/MINSTALL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henning Gross updated MINSTALL-94: -- Attachment: MINSTALL-94.zip > Optional: limit install to packaging x and or make install plugin not fail if > no artifacts were created for some modules. > - > > Key: MINSTALL-94 > URL: https://jira.codehaus.org/browse/MINSTALL-94 > Project: Maven 2.x Install Plugin > Issue Type: Improvement >Reporter: Henning Gross > Attachments: MINSTALL-94.patch, MINSTALL-94.zip > > > Background: I am working in a huge project with a lot of modules having a lot > of javascript-optimization and stuff happening in lifecycle-steps after > compile. This results in bad performance on jenkins. I would like to run > mvn compile install:install as I only need the jars/libs to be installed and > not the wars (and more important I do not need them to be built). > Please introduce Parameters like > war > or > false<... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
[
https://jira.codehaus.org/browse/MINSTALL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318481#comment-318481
]
Robert Scholte commented on MINSTALL-94:
What I don't like about the {{failIf}} option, is that when an artifact should
have been available the build should break, but by defining this option these
build-failures are ignored. So the best way would be to define it per module,
making it equivalent to the skip-parameter.
AFAIK you need to run {{package}} in order to run {{install}} or {{deploy}},
because that's when the jar/war/ear is bound to the {{MavenProject}}, so the
next goals know what to install or deploy.
If you want to confirm that the whole multimodule can be compiled, {{mvn
compile}} is enough with Maven3. For inner-multimodule dependencies the
classes-directory will be used instead of the jar.
Have you thought about the evil options {{maven.test.skip}} and {{skipTests}}?
> Optional: limit install to packaging x and or make install plugin not fail if
> no artifacts were created for some modules.
> -
>
> Key: MINSTALL-94
> URL: https://jira.codehaus.org/browse/MINSTALL-94
> Project: Maven 2.x Install Plugin
> Issue Type: Improvement
>Reporter: Henning Gross
> Attachments: MINSTALL-94.patch
>
>
> Background: I am working in a huge project with a lot of modules having a lot
> of javascript-optimization and stuff happening in lifecycle-steps after
> compile. This results in bad performance on jenkins. I would like to run
> mvn compile install:install as I only need the jars/libs to be installed and
> not the wars (and more important I do not need them to be built).
> Please introduce Parameters like
> war
> or
> false<...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
[
https://jira.codehaus.org/browse/MINSTALL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318426#comment-318426
]
Henning Gross edited comment on MINSTALL-94 at 1/31/13 5:24 PM:
Hi Robert!
I think you did not get my use-case. Its in the nature of a
multi-module-project that there are dependencies between modules. For instance
lets say you have 3 or 4 libraries, a core-lib and maybe like 10 to 20
consumers. You cannot run "mvn test" on the parent as the dependencies will be
missing (or old if already deployed before). You would have to run mvn install
to make sure those artifacts are deployed. When running the install-goal there
are some other phases in the default lifecycle that are passed before. As we
have a rather large amount of war-files with overlays and a lot of javascript
and less-foo configured those phases like packaging take forever. With no
benefit at all. I think the test-install jar thing that I have in mind is a
pretty valid requirement and a lot of projects do need it. In huge projects it
is essential to save as much time as possible in the basic jenkins-Jobs to
allow feedback early.
The approach of running two jenkins-jobs (one that installs the libs and the
other one that runs the tests on the consumers) brings a lot of configuration
overhead. Modules need to be wrapped in profiles and a build-pipeline on
Jenkins is necessary to make sure you are getting exactly the jars that were
just build and not something deployed from anywhere.
To your last question ("what is wrong with the skip-parameter?"): Of course we
could configure the skip-parameter in every single consumer-module wrapped in a
profile but that feels like a hack to me and is a lot of overhead compared to
just one line in the parent. Dont you think so? Thank you anyway for that idea.
I will probably implement it as fast is more important than nice. But fast and
nice would be even better ;)
Can I ask you the other way around? What is wrong with making this behaviour
configurable? Other plugins also expose switches for fail-behaviour.
was (Author: gaffa):
Hi Robert!
I think you did not get my use-case. Its in the nature of a
multi-module-project that there are dependencies between modules. For instance
lets say you have 3 or 4 libraries, a core-lib and maybe like 10 to 20
consumers. You cannot run "mvn test" on the parent as the dependencies will be
missing (or old if already deployed before). You would have to run mvn install
to make sure those artifacts are deployed. When running the install-goal there
are some other phases in the default lifecycle that are passed before. As we
have a rather large amount of war-files with overlays and a lot of javascript
and less-foo configured those phases like packaging take forever. With no
benefit at all. I think the test-install jar thing that I have in mind is a
pretty valid requirement and a lot of projects do need it. In huge projects it
is essential to save as much time as possible in the basic jenkins-Jobs to
allow feedback early.
The approach of running two jenkins-jobs (one that installs the libs and the
other one that runs the tests on the consumers) brings a lot of configuration
overhead. Modules need to be wrapped in profiles and a build-pipeline on
Jenkins is necessary to make sure you are getting exactly the jars that were
just build and not something deployed from anywhere.
To your last question ("what is wrong with the skip-parameter?"): as I stated
and hopefully now explained: its not about skipping anything really. Its about
being able to install stuff w/o running all phases before install (which causes
eg wars to not being build). Of course we could configure the skip-parameter in
every single consumer-module wrapped in a profile but that feels like a hack to
me. Dont you think so? Also I do not have the source available right now. Is
the skip-param evaluated before the check for the artifact is done? That would
be necessary for this approach. Can I ask you the other way around? What is
wrong with making this behaviour configurable? Other plugins also expose
switches for fail-behaviour.
> Optional: limit install to packaging x and or make install plugin not fail if
> no artifacts were created for some modules.
> -
>
> Key: MINSTALL-94
> URL: https://jira.codehaus.org/browse/MINSTALL-94
> Project: Maven 2.x Install Plugin
> Issue Type: Improvement
>Reporter: Henning Gross
> Attachments: MINSTALL-94.patch
>
>
> Background: I am working in a huge project with a lot of modules having a lot
> of javascript-optimization and stuff happening in lifecycle-steps after
> compile. This
[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
[
https://jira.codehaus.org/browse/MINSTALL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318426#comment-318426
]
Henning Gross commented on MINSTALL-94:
---
Hi Robert!
I think you did not get my use-case. Its in the nature of a
multi-module-project that there are dependencies between modules. For instance
lets say you have 3 or 4 libraries, a core-lib and maybe like 10 to 20
consumers. You cannot run "mvn test" on the parent as the dependencies will be
missing (or old if already deployed before). You would have to run mvn install
to make sure those artifacts are deployed. When running the install-goal there
are some other phases in the default lifecycle that are passed before. As we
have a rather large amount of war-files with overlays and a lot of javascript
and less-foo configured those phases like packaging take forever. With no
benefit at all. I think the test-install jar thing that I have in mind is a
pretty valid requirement and a lot of projects do need it. In huge projects it
is essential to save as much time as possible in the basic jenkins-Jobs to
allow feedback early.
The approach of running two jenkins-jobs (one that installs the libs and the
other one that runs the tests on the consumers) brings a lot of configuration
overhead. Modules need to be wrapped in profiles and a build-pipeline on
Jenkins is necessary to make sure you are getting exactly the jars that were
just build and not something deployed from anywhere.
To your last question ("what is wrong with the skip-parameter?"): as I stated
and hopefully now explained: its not about skipping anything really. Its about
being able to install stuff w/o running all phases before install (which causes
eg wars to not being build). Of course we could configure the skip-parameter in
every single consumer-module wrapped in a profile but that feels like a hack to
me. Dont you think so? Also I do not have the source available right now. Is
the skip-param evaluated before the check for the artifact is done? That would
be necessary for this approach. Can I ask you the other way around? What is
wrong with making this behaviour configurable? Other plugins also expose
switches for fail-behaviour.
> Optional: limit install to packaging x and or make install plugin not fail if
> no artifacts were created for some modules.
> -
>
> Key: MINSTALL-94
> URL: https://jira.codehaus.org/browse/MINSTALL-94
> Project: Maven 2.x Install Plugin
> Issue Type: Improvement
>Reporter: Henning Gross
> Attachments: MINSTALL-94.patch
>
>
> Background: I am working in a huge project with a lot of modules having a lot
> of javascript-optimization and stuff happening in lifecycle-steps after
> compile. This results in bad performance on jenkins. I would like to run
> mvn compile install:install as I only need the jars/libs to be installed and
> not the wars (and more important I do not need them to be built).
> Please introduce Parameters like
> war
> or
> false<...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
[
https://jira.codehaus.org/browse/MINSTALL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318391#comment-318391
]
Robert Scholte commented on MINSTALL-94:
Assuming you're using a Artifact Repository Manager, you should use {{verify}}
instead of {{install}} and let Jenkins deploy the artifacts when the job has
ended succesfully.
And what's wrong with the
[skip|http://maven.apache.org/plugins/maven-install-plugin/install-mojo.html#skip]-parameter?
> Optional: limit install to packaging x and or make install plugin not fail if
> no artifacts were created for some modules.
> -
>
> Key: MINSTALL-94
> URL: https://jira.codehaus.org/browse/MINSTALL-94
> Project: Maven 2.x Install Plugin
> Issue Type: Improvement
>Reporter: Henning Gross
> Attachments: MINSTALL-94.patch
>
>
> Background: I am working in a huge project with a lot of modules having a lot
> of javascript-optimization and stuff happening in lifecycle-steps after
> compile. This results in bad performance on jenkins. I would like to run
> mvn compile install:install as I only need the jars/libs to be installed and
> not the wars (and more important I do not need them to be built).
> Please introduce Parameters like
> war
> or
> false<...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
[ https://jira.codehaus.org/browse/MINSTALL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318376#comment-318376 ] Henning Gross edited comment on MINSTALL-94 at 1/31/13 9:36 AM: I attached a patch. It is really drop-dead-simple, works like a charm and we would really benefit from this. Is there any hope to get it into the next release? Do you already have an idea when you will release? We already use a junit 4.12-SNAPSHOT in our build and I do not want to make that a regular habit :D was (Author: gaffa): I attached a patch. It works like a charm and we would really benefit from this. > Optional: limit install to packaging x and or make install plugin not fail if > no artifacts were created for some modules. > - > > Key: MINSTALL-94 > URL: https://jira.codehaus.org/browse/MINSTALL-94 > Project: Maven 2.x Install Plugin > Issue Type: Improvement >Reporter: Henning Gross > Attachments: MINSTALL-94.patch > > > Background: I am working in a huge project with a lot of modules having a lot > of javascript-optimization and stuff happening in lifecycle-steps after > compile. This results in bad performance on jenkins. I would like to run > mvn compile install:install as I only need the jars/libs to be installed and > not the wars (and more important I do not need them to be built). > Please introduce Parameters like > war > or > false<... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
[ https://jira.codehaus.org/browse/MINSTALL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henning Gross updated MINSTALL-94: -- Attachment: MINSTALL-94.patch > Optional: limit install to packaging x and or make install plugin not fail if > no artifacts were created for some modules. > - > > Key: MINSTALL-94 > URL: https://jira.codehaus.org/browse/MINSTALL-94 > Project: Maven 2.x Install Plugin > Issue Type: Improvement >Reporter: Henning Gross > Attachments: MINSTALL-94.patch > > > Background: I am working in a huge project with a lot of modules having a lot > of javascript-optimization and stuff happening in lifecycle-steps after > compile. This results in bad performance on jenkins. I would like to run > mvn compile install:install as I only need the jars/libs to be installed and > not the wars (and more important I do not need them to be built). > Please introduce Parameters like > war > or > false<... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
[ https://jira.codehaus.org/browse/MINSTALL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318376#comment-318376 ] Henning Gross edited comment on MINSTALL-94 at 1/31/13 9:24 AM: I attached a patch. It works like a charm and we would really benefit from this. was (Author: gaffa): We might submit a Patch if theres a fair chance of getting it merged in soon. > Optional: limit install to packaging x and or make install plugin not fail if > no artifacts were created for some modules. > - > > Key: MINSTALL-94 > URL: https://jira.codehaus.org/browse/MINSTALL-94 > Project: Maven 2.x Install Plugin > Issue Type: Improvement >Reporter: Henning Gross > Attachments: MINSTALL-94.patch > > > Background: I am working in a huge project with a lot of modules having a lot > of javascript-optimization and stuff happening in lifecycle-steps after > compile. This results in bad performance on jenkins. I would like to run > mvn compile install:install as I only need the jars/libs to be installed and > not the wars (and more important I do not need them to be built). > Please introduce Parameters like > war > or > false<... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
[ https://jira.codehaus.org/browse/MINSTALL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318376#comment-318376 ] Henning Gross commented on MINSTALL-94: --- We might submit a Patch if theres a fair chance of getting it merged in soon. > Optional: limit install to packaging x and or make install plugin not fail if > no artifacts were created for some modules. > - > > Key: MINSTALL-94 > URL: https://jira.codehaus.org/browse/MINSTALL-94 > Project: Maven 2.x Install Plugin > Issue Type: Improvement >Reporter: Henning Gross > > Background: I am working in a huge project with a lot of modules having a lot > of javascript-optimization and stuff happening in lifecycle-steps after > compile. This results in bad performance on jenkins. I would like to run > mvn compile install:install as I only need the jars/libs to be installed and > not the wars (and more important I do not need them to be built). > Please introduce Parameters like > war > or > false<... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-94) Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules.
Henning Gross created MINSTALL-94: - Summary: Optional: limit install to packaging x and or make install plugin not fail if no artifacts were created for some modules. Key: MINSTALL-94 URL: https://jira.codehaus.org/browse/MINSTALL-94 Project: Maven 2.x Install Plugin Issue Type: Improvement Reporter: Henning Gross Background: I am working in a huge project with a lot of modules having a lot of javascript-optimization and stuff happening in lifecycle-steps after compile. This results in bad performance on jenkins. I would like to run mvn compile install:install as I only need the jars/libs to be installed and not the wars (and more important I do not need them to be built). Please introduce Parameters like war or false<... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
