[jira] Closed: (MPIR-139) Generation of project-info.html cannot be omitted
[
http://jira.codehaus.org/browse/MPIR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MPIR-139.
--
Assignee: Benjamin Bentmann
Resolution: Not A Bug
The POM provides a way to selectively run report goals via {{}},
see [Run Selective
Reports|http://maven.apache.org/plugins/maven-project-info-reports-plugin/examples/selective-project-info-reports.html]
for an example snippet. For your use-case, you only need to exclude the
{{summary}} from the list.
> Generation of project-info.html cannot be omitted
> -
>
> Key: MPIR-139
> URL: http://jira.codehaus.org/browse/MPIR-139
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: index
>Affects Versions: 2.1
>Reporter: Michael Osipov
>Assignee: Benjamin Bentmann
>
> There is no option to prevent the MPIR to generate the project-info.html.
> Please fix this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MPIR-139) Generation of project-info.html cannot be omitted
[
http://jira.codehaus.org/browse/MPIR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reopened MPIR-139:
-
This is not correct.
This is my code:
{code}
maven-project-info-reports-plugin
dependencies
{code}
And you can see the outcome.png to see the wrong generation.
> Generation of project-info.html cannot be omitted
> -
>
> Key: MPIR-139
> URL: http://jira.codehaus.org/browse/MPIR-139
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: index
>Affects Versions: 2.1
>Reporter: Michael Osipov
>Assignee: Benjamin Bentmann
>
> There is no option to prevent the MPIR to generate the project-info.html.
> Please fix this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPIR-139) Generation of project-info.html cannot be omitted
[ http://jira.codehaus.org/browse/MPIR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPIR-139: Attachment: outcome.png project-info.html still generated > Generation of project-info.html cannot be omitted > - > > Key: MPIR-139 > URL: http://jira.codehaus.org/browse/MPIR-139 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: index >Affects Versions: 2.1 >Reporter: Michael Osipov >Assignee: Benjamin Bentmann > Attachments: outcome.png > > > There is no option to prevent the MPIR to generate the project-info.html. > Please fix this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRESOURCES-8) maven-resources-plugin ignores configuration/resources property (add a new mojo to copy resources)
[
http://jira.codehaus.org/browse/MRESOURCES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MRESOURCES-8:
--
Summary: maven-resources-plugin ignores configuration/resources property
(add a new mojo to copy resources) (was: maven-resources-plugin ignores
configuration/resources property)
> maven-resources-plugin ignores configuration/resources property (add a new
> mojo to copy resources)
> --
>
> Key: MRESOURCES-8
> URL: http://jira.codehaus.org/browse/MRESOURCES-8
> Project: Maven 2.x Resources Plugin
> Issue Type: New Feature
>Affects Versions: 2.1, 2.2
>Reporter: Leszek Gawron
>Assignee: Olivier Lamy
> Fix For: 2.3
>
> Attachments: example.zip, MRESOURCES-8-workaround.patch, pom.xml
>
>
> I am evaluating maven + eclipse combo. In a trivial POM filtered resources
> exist only in target/classes. If one executes Project -> Clean under eclipse
> this information is lost. If filtered resources would appear as source folder
> they would survive cleaning and not got overriden by unfiltered ones.
> I have been trying to implement a scenario which would allow filtered
> resources to appear as "static" source folder under eclipse.
> The POM explains it best:
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.mobilebox.squash.client
> squash-client
> jar
> 1.0-SNAPSHOT
> Maven Quick Start Archetype
> http://maven.apache.org
>
>
>
> maven-resources-plugin
>
>
> prefilter-resources
> generate-resources
>
> resources
>
>
>
> target/generated-resources
>
>
>
> src/main/resource-templates
> true
>
>
>
>
>
>
>
>
> ${ffile}
>
>
>
> src/main/resources
>
>
> target/generated-resources
>
>
>
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
> filter.properties
>
>
> thing is this part:
>
>
> src/main/properties
> true
>
>
> is completely ignored. Instead for both maven-resource-plugin executions (the
> one in generate-resources phase and the default one) this config is used:
>
>
> src/main/resources
>
>
> target/generated-resources
>
>
> which of course breaks the whole idea.
> Is this a bug or a design decision. In latter case is there any equivalent
> approach I might take?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MSITE-354) Generation of project-info.html cannot be omitted
[ http://jira.codehaus.org/browse/MSITE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MPIR-139 to MSITE-354: -- Affects Version/s: (was: 2.1) 2.0-beta-7 Component/s: (was: index) Issue Type: New Feature (was: Bug) Key: MSITE-354 (was: MPIR-139) Project: Maven 2.x Site Plugin (was: Maven 2.x Project Info Reports Plugin) > Generation of project-info.html cannot be omitted > - > > Key: MSITE-354 > URL: http://jira.codehaus.org/browse/MSITE-354 > Project: Maven 2.x Site Plugin > Issue Type: New Feature >Affects Versions: 2.0-beta-7 >Reporter: Michael Osipov > Attachments: outcome.png > > > There is no option to prevent the MPIR to generate the project-info.html. > Please fix this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-354) Generation of project-info.html cannot be omitted
[ http://jira.codehaus.org/browse/MSITE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147259#action_147259 ] Michael Osipov commented on MSITE-354: -- Benjamin, yes I can. I made a customized and flat site for a multimodule project and declared the reports manually in the site.xml. Since I have specialized entry sites for every module, I don't need the project-info.html. You may see my site [here|http://java.fckeditor.net/] (modules documentation) and the current [branch|http://svn.fckeditor.net/FCKeditor.Java/branches/2.5-test/] I am working on at r2439. This may make the point clearer. > Generation of project-info.html cannot be omitted > - > > Key: MSITE-354 > URL: http://jira.codehaus.org/browse/MSITE-354 > Project: Maven 2.x Site Plugin > Issue Type: New Feature >Affects Versions: 2.0-beta-7 >Reporter: Michael Osipov > Attachments: outcome.png > > > There is no option to prevent the MPIR to generate the project-info.html. > Please fix this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPIR-139) Generation of project-info.html cannot be omitted
[ http://jira.codehaus.org/browse/MPIR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MPIR-139: --- Assignee: (was: Benjamin Bentmann) Oh yes, sorry, I misunderstood your description. You actually mean the summary page for the report category "Project Information", this is completely unrelated to the "Project Summary" I had in mind. This document is produced by the Maven Site Plugin. Maybe you could outline your use case a little more to help understanding why the entry point to the reports should be disabled. > Generation of project-info.html cannot be omitted > - > > Key: MPIR-139 > URL: http://jira.codehaus.org/browse/MPIR-139 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: index >Affects Versions: 2.1 >Reporter: Michael Osipov > Attachments: outcome.png > > > There is no option to prevent the MPIR to generate the project-info.html. > Please fix this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-354) Generation of project-info.html cannot be omitted
[ http://jira.codehaus.org/browse/MSITE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147261#action_147261 ] Dennis Lundberg commented on MSITE-354: --- This file project-info.html is an index of all reports which belongs to the category "Project Information. These reports are generated by Maven Project Information Reports Plugin. Your POM has one of these reports configured: dependencies. That's why you get the project-info.html page. What is is that you want to happen? Do you want the page itself (project-info.html) to not be generated? If so why? You have obviously already created a custom menu that links to the dependencies report. > Generation of project-info.html cannot be omitted > - > > Key: MSITE-354 > URL: http://jira.codehaus.org/browse/MSITE-354 > Project: Maven 2.x Site Plugin > Issue Type: New Feature >Affects Versions: 2.0-beta-7 >Reporter: Michael Osipov > Attachments: outcome.png > > > There is no option to prevent the MPIR to generate the project-info.html. > Please fix this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-294) Can't escape ${project.version} as plain text inside apt +---- section, on *.apt.vm files
[
http://jira.codehaus.org/browse/MSITE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MSITE-294.
-
Resolution: Not A Bug
> Can't escape ${project.version} as plain text inside apt + section, on
> *.apt.vm files
> -
>
> Key: MSITE-294
> URL: http://jira.codehaus.org/browse/MSITE-294
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-6
> Environment: *.apt.vm files, and +- escaped section.
>Reporter: Andrew Hughes
>Priority: Critical
>
> You can reproduce this the following way.
> ./src/site/index.apt.vm (start)
> --
> This will appear without the backslashes
> {noformat}$\{project.version\}{noformat} and that's excellent. But you can't
> get this output in the escaped apt text section below.
> {noformat}
> +---
> However this apt escaped section still shows the backslashes inside this
> section $\{project.version\} and there is no known way the text can be shown
> as above.
> To make matters worse, when you put this in without the backslashes, you get
> the properties value (like a filter). See: ${project.version} not the desired
> string as above
> +---
> {noformat}
> -
> ./src/site/index.apt.vm (start)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-293) Submodule inherit menu but this should not happend
[
http://jira.codehaus.org/browse/MSITE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MSITE-293:
--
Description:
Projectstructur:
{noformat}
modul
| pom.xml
| src/site/site.xml
| src/site/xdoc/index.xml
+-- submodul 1
| pom.xml
| src/site/xdoc/index.xml
+-- submodul 2
| pom.xml
| src/site/xdoc/index.xml
{noformat}
modul :: site.xml
{code}
...
http://lp2p067c:82/maven2/repositories/"; />
...
{code}
after "mvn clean install site" each submodules has a menu "Maven" ... but i
want this only for the "main-modul".
whats wrong?
http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
... Inheritance ... "By default, only the basic settings are inherited. From
the body, only the links are inherited, and these accumulate to contain all the
parents' site descriptor links."
was:
Projectstructur:
modul
| pom.xml
| src/site/site.xml
| src/site/xdoc/index.xml
+-- submodul 1
| pom.xml
| src/site/xdoc/index.xml
+-- submodul 2
| pom.xml
| src/site/xdoc/index.xml
modul :: site.xml
...
http://lp2p067c:82/maven2/repositories/"; />
...
after "mvn clean install site" each submodules has a menu "Maven" ... but i
want this only for the "main-modul".
whats wrong?
http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
... Inheritance ... "By default, only the basic settings are inherited. From
the body, only the links are inherited, and these accumulate to contain all the
parents' site descriptor links."
> Submodule inherit menu but this should not happend
> --
>
> Key: MSITE-293
> URL: http://jira.codehaus.org/browse/MSITE-293
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: inheritance, site descriptor
>Affects Versions: 2.0-beta-6
> Environment: maven 2.0.8
> jdk 1.6
> windows
>Reporter: Andreas Höhmann
>Priority: Critical
>
> Projectstructur:
> {noformat}
> modul
> | pom.xml
> | src/site/site.xml
> | src/site/xdoc/index.xml
> +-- submodul 1
> | pom.xml
> | src/site/xdoc/index.xml
> +-- submodul 2
> | pom.xml
> | src/site/xdoc/index.xml
> {noformat}
> modul :: site.xml
> {code}
> ...
>
>
>
>
>
>
>
>
>
>
>
>
>
>href="http://lp2p067c:82/maven2/repositories/"; />
>
>
>
>
>
> ...
> {code}
> after "mvn clean install site" each submodules has a menu "Maven" ... but i
> want this only for the "main-modul".
> whats wrong?
> http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
> ... Inheritance ... "By default, only the basic settings are inherited. From
> the body, only the links are inherited, and these accumulate to contain all
> the parents' site descriptor links."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSHARED-61) Base directory of file set is not excluded from deletion if it contains excluded paths
Base directory of file set is not excluded from deletion if it contains
excluded paths
--
Key: MSHARED-61
URL: http://jira.codehaus.org/browse/MSHARED-61
Project: Maven Shared Components
Issue Type: Bug
Components: file-management
Affects Versions: file-management 1.2
Reporter: Benjamin Bentmann
Priority: Critical
For a directory structure like
{noformat}
base/
excluded
{noformat}
configuring a file set with base directory {{base}} and excludes {{excluded}}
the entire directory tree will be deleted, including the originally excluded
files/dirs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSHARED-61) Base directory of file set is not excluded from deletion if it contains excluded paths
[
http://jira.codehaus.org/browse/MSHARED-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MSHARED-61.
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: file-management 1.2.1
Fixed in [r692879|http://svn.apache.org/viewvc?view=rev&revision=692879].
> Base directory of file set is not excluded from deletion if it contains
> excluded paths
> --
>
> Key: MSHARED-61
> URL: http://jira.codehaus.org/browse/MSHARED-61
> Project: Maven Shared Components
> Issue Type: Bug
> Components: file-management
>Affects Versions: file-management 1.2
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Critical
> Fix For: file-management 1.2.1
>
>
> For a directory structure like
> {noformat}
> base/
> excluded
> {noformat}
> configuring a file set with base directory {{base}} and excludes {{excluded}}
> the entire directory tree will be deleted, including the originally excluded
> files/dirs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-349) Update this plugin's site documentation page: "Configuring the Site Descriptor" to include the element
[ http://jira.codehaus.org/browse/MSITE-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-349. - Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.0-beta-8 Fixed in [r692883|http://svn.apache.org/viewvc?view=rev&revision=692883]. > Update this plugin's site documentation page: "Configuring the Site > Descriptor" to include the element > > > Key: MSITE-349 > URL: http://jira.codehaus.org/browse/MSITE-349 > Project: Maven 2.x Site Plugin > Issue Type: Improvement >Affects Versions: 2.0-beta-7 >Reporter: zac heismann >Assignee: Dennis Lundberg >Priority: Minor > Fix For: 2.0-beta-8 > > > Please update the documentation for this page: > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > to include information about the element. > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-224) [PATCH] please make UTF-8 the default encoding
[ http://jira.codehaus.org/browse/MSITE-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-224. - Resolution: Won't Fix Encoding has been implemented according to [another proposal|http://docs.codehaus.org/display/MAVEN/Reporting+Encoding+Configuration]. > [PATCH] please make UTF-8 the default encoding > -- > > Key: MSITE-224 > URL: http://jira.codehaus.org/browse/MSITE-224 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Components: encoding > Environment: Gentoo Linux, UTF-8 encoded pom files >Reporter: Petr Kozelka >Priority: Minor > Attachments: site-plugin-UTF8-encoding.patch > > > UTF-8 is already widely supported and used by tools, there is hardly a reason > to keep with ISO-8859-1 found through the code. > In my usecases, it typically makes troubles with developer names containing > accented letters. > Attached patch changes the default input and output encoding in > maven-site-plugin which is the most important piece. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-354) Generation of project-info.html cannot be omitted
[
http://jira.codehaus.org/browse/MSITE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147271#action_147271
]
Michael Osipov commented on MSITE-354:
--
{quote}
What is is that you want to happen?
Do you want the page itself (project-info.html) to not be generated?
{quote}
Yes, exactly. No project-info.html generation.
{quote}
If so why? You have obviously already created a custom menu that links to the
dependencies report.
{quote}
I have a custom menu in my site.xml which makes the project-info.html basically
superfluous.
A solution could be:
{noformat}
maven-project-info-reports-plugin
false
dependencies
{noformat}
> Generation of project-info.html cannot be omitted
> -
>
> Key: MSITE-354
> URL: http://jira.codehaus.org/browse/MSITE-354
> Project: Maven 2.x Site Plugin
> Issue Type: New Feature
>Affects Versions: 2.0-beta-7
>Reporter: Michael Osipov
> Attachments: outcome.png
>
>
> There is no option to prevent the MPIR to generate the project-info.html.
> Please fix this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-355) Upgrade to Wagon 1.0-beta-4
Upgrade to Wagon 1.0-beta-4 --- Key: MSITE-355 URL: http://jira.codehaus.org/browse/MSITE-355 Project: Maven 2.x Site Plugin Issue Type: Task Affects Versions: 2.0-beta-7 Reporter: Dennis Lundberg Fix For: 2.0-beta-8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-355) Upgrade to Wagon 1.0-beta-4
[ http://jira.codehaus.org/browse/MSITE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-355. - Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.0-beta-8 Fixed in [r692901|http://svn.apache.org/viewvc?view=rev&revision=692901]. > Upgrade to Wagon 1.0-beta-4 > --- > > Key: MSITE-355 > URL: http://jira.codehaus.org/browse/MSITE-355 > Project: Maven 2.x Site Plugin > Issue Type: Task >Affects Versions: 2.0-beta-7 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.0-beta-8 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-600) missing gnujaxp/gnujaxp/1.0.0
missing gnujaxp/gnujaxp/1.0.0 - Key: MEV-600 URL: http://jira.codehaus.org/browse/MEV-600 Project: Maven Evangelism Issue Type: Bug Components: Dependencies Reporter: Kit Wu The pom http://mirrors.ibiblio.org/pub/mirrors/maven2/jfree/jfreechart/1.0.0-rc1/jfreechart-1.0.0-rc1.pom contains a dependency to gnujaxp gnujaxp 1.0.0 I believe the gnujaxp artifact is missing per another bug http://jira.codehaus.org/browse/MEV-284. Can we remove the dependency for this version of jfreechart as well? Thanks, Kit -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MENFORCER-51) build failure in case of available updates
[ http://jira.codehaus.org/browse/MENFORCER-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147286#action_147286 ] Brian Fox commented on MENFORCER-51: i agree, failing a build is definitely in enforcer territory > build failure in case of available updates > -- > > Key: MENFORCER-51 > URL: http://jira.codehaus.org/browse/MENFORCER-51 > Project: Maven 2.x Enforcer Plugin > Issue Type: Wish >Reporter: Tomasz Pik > > It would be useful to have a possibility to fail build if there's an update > of given dependency. > In some way it would 'solve' problem of 'how to depend of latest stable > version of my company parent pom' problem - build would just not pass > if there's an update. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MENFORCER-51) build failure in case of available updates
[ http://jira.codehaus.org/browse/MENFORCER-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147195#action_147195 ] stephenconnolly edited comment on MENFORCER-51 at 9/8/08 12:44 AM: I moved this to enforcer from versions-maven-plugin because fundamentally I believe this wish to be out of scope for the versions maven plugin. The enforcer plugin is responsible for failing the build if things need to be enforced. I may be able to write a patch to implement this in the standard rules in the next couple of days if nobody else writes one first! was (Author: stephenconnolly): I moved this to enforcer from versions-maven-plugin because fundamentally I believe this wisk to beout of scope for the versions maven plugin. The enforcer plugin is responsible for failing the build if things need to be enforced. I may be able to write a patch to implement this in the standard rules in the next couple of days if nobody else writes one first! > build failure in case of available updates > -- > > Key: MENFORCER-51 > URL: http://jira.codehaus.org/browse/MENFORCER-51 > Project: Maven 2.x Enforcer Plugin > Issue Type: Wish >Reporter: Tomasz Pik > > It would be useful to have a possibility to fail build if there's an update > of given dependency. > In some way it would 'solve' problem of 'how to depend of latest stable > version of my company parent pom' problem - build would just not pass > if there's an update. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
