[jira] (MPH-98) help:effective-pom produces an invalid issueManagement element
David Grant created MPH-98: -- Summary: help:effective-pom produces an invalid issueManagement element Key: MPH-98 URL: https://jira.codehaus.org/browse/MPH-98 Project: Maven Help Plugin Issue Type: Bug Components: effective-pom Affects Versions: 2.2 Reporter: David Grant Given a POM with an "issueManagement" element, help:effective-pom produces a POM containing an element named "issuanagement" instead of "issueManagement". Please see the following URL for an example: https://travis-ci.org/adaptive-logic/adaptive-logic-pom#L471 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPH-98) help:effective-pom produces an invalid issueManagement element
[ https://jira.codehaus.org/browse/MPH-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Grant closed MPH-98. -- Resolution: Not A Bug > help:effective-pom produces an invalid issueManagement element > -- > > Key: MPH-98 > URL: https://jira.codehaus.org/browse/MPH-98 > Project: Maven Help Plugin > Issue Type: Bug > Components: effective-pom >Affects Versions: 2.2 >Reporter: David Grant > > Given a POM with an "issueManagement" element, help:effective-pom produces a > POM containing an element named "issuanagement" instead of "issueManagement". > Please see the following URL for an example: > https://travis-ci.org/adaptive-logic/adaptive-logic-pom#L471 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-184) Allow src/main/resources to be searched by Checkstyle
[
https://jira.codehaus.org/browse/MCHECKSTYLE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333838#comment-333838
]
Mass Dosage commented on MCHECKSTYLE-184:
-
I have run into this same issue - checkstyle is now trying to apply Java checks
on all .properties files in src/main/resources and there appears to be no way
to turn it off. I have tried the includes and excludes elements but these don't
seem to apply to files under src/main/resources. Should I add a feature request
for this?
I tried using a SuppressionFilter but this would seem to require a suppressions
file in each and every project which has this issue which isn't ideal. I tried
putting my suppressions XML file in the same jar (a plugin-config jar) as the
checkstyle-config.xml but getResourceAsStream doesn't appear to find it, it
only finds files local to my project. Either way, having to go via the
SuppressionsFilter feels like a hack, one should be able to configure files to
include/exclude from the plugin config itself.
> Allow src/main/resources to be searched by Checkstyle
> -
>
> Key: MCHECKSTYLE-184
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-184
> Project: Maven Checkstyle Plugin
> Issue Type: New Feature
>Affects Versions: 2.9.1
>Reporter: Dennis Lundberg
>Assignee: Dennis Lundberg
> Fix For: 2.10
>
>
> There is a nice check in Checkstyle that allows you to keep your localized
> resource bundles in sync.
>
> http://checkstyle.sourceforge.net/config_misc.html
> In its current state maven-checkstyle-plugin cannot make use of this check,
> for two reasons:
> # maven-checkstyle-plugin only recognizes {{\*\*/\*.java}} files. This can be
> re-configured with the parameter.
> # maven-checkstyle-plugin supports only one source directory, which is
> configured with the parameter.
> We need to be able to add a resource directory (/src/main/resources by
> default) that is searched for {{\*\*/\*.properties}} files by default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-184) Allow src/main/resources to be searched by Checkstyle
[
https://jira.codehaus.org/browse/MCHECKSTYLE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333853#comment-333853
]
Dennis Lundberg commented on MCHECKSTYLE-184:
-
A work-around is to go back to the previous version of the plugin: 2.9.1.
I'll create another issue about making this configurable.
> Allow src/main/resources to be searched by Checkstyle
> -
>
> Key: MCHECKSTYLE-184
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-184
> Project: Maven Checkstyle Plugin
> Issue Type: New Feature
>Affects Versions: 2.9.1
>Reporter: Dennis Lundberg
>Assignee: Dennis Lundberg
> Fix For: 2.10
>
>
> There is a nice check in Checkstyle that allows you to keep your localized
> resource bundles in sync.
>
> http://checkstyle.sourceforge.net/config_misc.html
> In its current state maven-checkstyle-plugin cannot make use of this check,
> for two reasons:
> # maven-checkstyle-plugin only recognizes {{\*\*/\*.java}} files. This can be
> re-configured with the parameter.
> # maven-checkstyle-plugin supports only one source directory, which is
> configured with the parameter.
> We need to be able to add a resource directory (/src/main/resources by
> default) that is searched for {{\*\*/\*.properties}} files by default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-199) Make resource file processing configurable
Dennis Lundberg created MCHECKSTYLE-199: --- Summary: Make resource file processing configurable Key: MCHECKSTYLE-199 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-199 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.10 Reporter: Dennis Lundberg In MCHECKSTYLE-184 processing of resource files was added. This is currently hard coded, which leads to problems under certain conditions. See comments in MCHECKSTYLE-184. Add configuration parameters for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-301) webResources filtering not happening properly
[
https://jira.codehaus.org/browse/MWAR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333877#comment-333877
]
Juan Miguel Bernal Gonzalez commented on MWAR-301:
--
I've the same issue. For a workaround, you have to add a ** tag in
**:
{code:borderStyle=solid}
org.apache.maven.plugins
maven-war-plugin
2.4
...
${project.basedir}/src/main/filters/my-filter.properties
{code}
> webResources filtering not happening properly
> -
>
> Key: MWAR-301
> URL: https://jira.codehaus.org/browse/MWAR-301
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: filtering
>Affects Versions: 2.4
> Environment: Linux
>Reporter: Mukarram Baig
> Attachments: mwar-tester.zip
>
>
> I noticed that webResources were not getting filtered when I upgraded from
> 2.3 to 2.4 and could not find an open issue related to it, so letting you
> guys know if I am doing something incorrect that was working till 2.3 and got
> fixed in 2.4. I am attaching a sample project where a JS file was getting
> filtered properly when using 2.3 and not when using 2.4.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-301) webResources filtering not happening properly
[
https://jira.codehaus.org/browse/MWAR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333877#comment-333877
]
Juan Miguel Bernal Gonzalez edited comment on MWAR-301 at 10/9/13 11:14 AM:
I've the same issue.
The problem is that the maven-shade doesn't get the default base filter of the
project *pom.xml*.
For a workaround, you have to add a ** tag in **:
{code:borderStyle=solid}
org.apache.maven.plugins
maven-war-plugin
2.4
...
${project.basedir}/src/main/filters/my-filter.properties
{code}
was (Author: juanmiguelbg):
I've the same issue. For a workaround, you have to add a ** tag in
**:
{code:borderStyle=solid}
org.apache.maven.plugins
maven-war-plugin
2.4
...
${project.basedir}/src/main/filters/my-filter.properties
{code}
> webResources filtering not happening properly
> -
>
> Key: MWAR-301
> URL: https://jira.codehaus.org/browse/MWAR-301
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: filtering
>Affects Versions: 2.4
> Environment: Linux
>Reporter: Mukarram Baig
> Attachments: mwar-tester.zip
>
>
> I noticed that webResources were not getting filtered when I upgraded from
> 2.3 to 2.4 and could not find an open issue related to it, so letting you
> guys know if I am doing something incorrect that was working till 2.3 and got
> fixed in 2.4. I am attaching a sample project where a JS file was getting
> filtered properly when using 2.3 and not when using 2.4.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-301) webResources filtering not happening properly
[
https://jira.codehaus.org/browse/MWAR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333877#comment-333877
]
Juan Miguel Bernal Gonzalez edited comment on MWAR-301 at 10/9/13 11:19 AM:
I've the same issue.
The problem is that the maven-shade doesn't get the default base filter
(declared in tag) of the project *pom.xml*.
For a workaround, you have to add a ** tag in **:
{code:borderStyle=solid}
org.apache.maven.plugins
maven-war-plugin
2.4
...
${project.basedir}/src/main/filters/my-filter.properties
{code}
was (Author: juanmiguelbg):
I've the same issue.
The problem is that the maven-shade doesn't get the default base filter of the
project *pom.xml*.
For a workaround, you have to add a ** tag in **:
{code:borderStyle=solid}
org.apache.maven.plugins
maven-war-plugin
2.4
...
${project.basedir}/src/main/filters/my-filter.properties
{code}
> webResources filtering not happening properly
> -
>
> Key: MWAR-301
> URL: https://jira.codehaus.org/browse/MWAR-301
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: filtering
>Affects Versions: 2.4
> Environment: Linux
>Reporter: Mukarram Baig
> Attachments: mwar-tester.zip
>
>
> I noticed that webResources were not getting filtered when I upgraded from
> 2.3 to 2.4 and could not find an open issue related to it, so letting you
> guys know if I am doing something incorrect that was working till 2.3 and got
> fixed in 2.4. I am attaching a sample project where a JS file was getting
> filtered properly when using 2.3 and not when using 2.4.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-301) webResources filtering not happening properly
[
https://jira.codehaus.org/browse/MWAR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333877#comment-333877
]
Juan Miguel Bernal Gonzalez edited comment on MWAR-301 at 10/9/13 11:19 AM:
I've the same issue.
The problem is that the maven-shade doesn't get the default base filter
(declared in tag) of the project *pom.xml*.
For a workaround, you have to add a ** tag again in **:
{code:borderStyle=solid}
org.apache.maven.plugins
maven-war-plugin
2.4
...
${project.basedir}/src/main/filters/my-filter.properties
{code}
was (Author: juanmiguelbg):
I've the same issue.
The problem is that the maven-shade doesn't get the default base filter
(declared in tag) of the project *pom.xml*.
For a workaround, you have to add a ** tag in **:
{code:borderStyle=solid}
org.apache.maven.plugins
maven-war-plugin
2.4
...
${project.basedir}/src/main/filters/my-filter.properties
{code}
> webResources filtering not happening properly
> -
>
> Key: MWAR-301
> URL: https://jira.codehaus.org/browse/MWAR-301
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: filtering
>Affects Versions: 2.4
> Environment: Linux
>Reporter: Mukarram Baig
> Attachments: mwar-tester.zip
>
>
> I noticed that webResources were not getting filtered when I upgraded from
> 2.3 to 2.4 and could not find an open issue related to it, so letting you
> guys know if I am doing something incorrect that was working till 2.3 and got
> fixed in 2.4. I am attaching a sample project where a JS file was getting
> filtered properly when using 2.3 and not when using 2.4.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-301) webResources filtering not happening properly
[
https://jira.codehaus.org/browse/MWAR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333877#comment-333877
]
Juan Miguel Bernal Gonzalez edited comment on MWAR-301 at 10/9/13 11:20 AM:
I've the same issue.
The problem is that the maven-shade doesn't get the default base filter
(declared in tag) of the project *pom.xml*.
For a workaround, you have to add a ** tag in **, again:
{code:borderStyle=solid}
org.apache.maven.plugins
maven-war-plugin
2.4
...
${project.basedir}/src/main/filters/my-filter.properties
{code}
was (Author: juanmiguelbg):
I've the same issue.
The problem is that the maven-shade doesn't get the default base filter
(declared in tag) of the project *pom.xml*.
For a workaround, you have to add a ** tag again in **:
{code:borderStyle=solid}
org.apache.maven.plugins
maven-war-plugin
2.4
...
${project.basedir}/src/main/filters/my-filter.properties
{code}
> webResources filtering not happening properly
> -
>
> Key: MWAR-301
> URL: https://jira.codehaus.org/browse/MWAR-301
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: filtering
>Affects Versions: 2.4
> Environment: Linux
>Reporter: Mukarram Baig
> Attachments: mwar-tester.zip
>
>
> I noticed that webResources were not getting filtered when I upgraded from
> 2.3 to 2.4 and could not find an open issue related to it, so letting you
> guys know if I am doing something incorrect that was working till 2.3 and got
> fixed in 2.4. I am attaching a sample project where a JS file was getting
> filtered properly when using 2.3 and not when using 2.4.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-301) webResources filtering not happening properly
[
https://jira.codehaus.org/browse/MWAR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333877#comment-333877
]
Juan Miguel Bernal Gonzalez edited comment on MWAR-301 at 10/9/13 11:25 AM:
I've the same issue.
The problem is that the maven-filtering doesn't get the default base filter
(declared in tag) of the project *pom.xml*.
For a workaround, you have to add a ** tag in **, again:
{code:borderStyle=solid}
org.apache.maven.plugins
maven-war-plugin
2.4
...
${project.basedir}/src/main/filters/my-filter.properties
{code}
was (Author: juanmiguelbg):
I've the same issue.
The problem is that the maven-shade doesn't get the default base filter
(declared in tag) of the project *pom.xml*.
For a workaround, you have to add a ** tag in **, again:
{code:borderStyle=solid}
org.apache.maven.plugins
maven-war-plugin
2.4
...
${project.basedir}/src/main/filters/my-filter.properties
{code}
> webResources filtering not happening properly
> -
>
> Key: MWAR-301
> URL: https://jira.codehaus.org/browse/MWAR-301
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: filtering
>Affects Versions: 2.4
> Environment: Linux
>Reporter: Mukarram Baig
> Attachments: mwar-tester.zip
>
>
> I noticed that webResources were not getting filtered when I upgraded from
> 2.3 to 2.4 and could not find an open issue related to it, so letting you
> guys know if I am doing something incorrect that was working till 2.3 and got
> fixed in 2.4. I am attaching a sample project where a JS file was getting
> filtered properly when using 2.3 and not when using 2.4.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-301) webResources filtering not happening properly
[
https://jira.codehaus.org/browse/MWAR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333881#comment-333881
]
Grzegorz Grzybek commented on MWAR-301:
---
Please see MWAR-305, where I've done some analysis. The problem occured when
upgrading to {{maven-filtering:1.0-beta-3}}.
regards
Grzegorz Grzybek
> webResources filtering not happening properly
> -
>
> Key: MWAR-301
> URL: https://jira.codehaus.org/browse/MWAR-301
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: filtering
>Affects Versions: 2.4
> Environment: Linux
>Reporter: Mukarram Baig
> Attachments: mwar-tester.zip
>
>
> I noticed that webResources were not getting filtered when I upgraded from
> 2.3 to 2.4 and could not find an open issue related to it, so letting you
> guys know if I am doing something incorrect that was working till 2.3 and got
> fixed in 2.4. I am attaching a sample project where a JS file was getting
> filtered properly when using 2.3 and not when using 2.4.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-243) Motion Chart does not show graphic view when browsing on https
cforce created MANTTASKS-243: Summary: Motion Chart does not show graphic view when browsing on https Key: MANTTASKS-243 URL: https://jira.codehaus.org/browse/MANTTASKS-243 Project: Maven Ant Tasks Issue Type: Bug Environment: SonarQube Version 3.7, Motion Chart 1.5, Windows Service on 2008 srv Reporter: cforce When we call the web frontend dashbaord with motion charts on http it works but on https(verisign cert) there are no charts rendered - flash it not loaded in the widget for the graphics. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-243) Motion Chart does not show graphic view when browsing on https
[ https://jira.codehaus.org/browse/MANTTASKS-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333884#comment-333884 ] cforce commented on MANTTASKS-243: -- Sory, worng category, but can't move or change away from manttasks. > Motion Chart does not show graphic view when browsing on https > > > Key: MANTTASKS-243 > URL: https://jira.codehaus.org/browse/MANTTASKS-243 > Project: Maven Ant Tasks > Issue Type: Bug > Environment: SonarQube Version 3.7, Motion Chart 1.5, Windows > Service on 2008 srv >Reporter: cforce > > When we call the web frontend dashbaord with motion charts on http it works > but on https(verisign cert) there are no charts rendered - flash it not > loaded in the widget for the graphics. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-243) Motion Chart does not show graphic view when browsing on https
[ https://jira.codehaus.org/browse/MANTTASKS-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] cforce updated MANTTASKS-243: - Description: When we call the web frontend dashbaord with motion charts on http it works but on https(verisign cert) there are no charts rendered - flash it not loaded in the widget for the graphics. Instead i se circle for loading any data all the waym without sucessfully loading it. was:When we call the web frontend dashbaord with motion charts on http it works but on https(verisign cert) there are no charts rendered - flash it not loaded in the widget for the graphics. > Motion Chart does not show graphic view when browsing on https > > > Key: MANTTASKS-243 > URL: https://jira.codehaus.org/browse/MANTTASKS-243 > Project: Maven Ant Tasks > Issue Type: Bug > Environment: SonarQube Version 3.7, Motion Chart 1.5, Windows > Service on 2008 srv >Reporter: cforce > > When we call the web frontend dashbaord with motion charts on http it works > but on https(verisign cert) there are no charts rendered - flash it not > loaded in the widget for the graphics. > Instead i se circle for loading any data all the waym without sucessfully > loading it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-305) Filtering doesn't work as expected after switching from maven-filtering:1.0-beta-2 to maven-filtering:1.1
[
https://jira.codehaus.org/browse/MWAR-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333887#comment-333887
]
Juan Miguel Bernal Gonzalez commented on MWAR-305:
--
Thank's Grzegorz, you are right.
In the page [Adding Filtering
Webresources|http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html]
of the *maven-war-plugin* documentation, section *Filtering*, you say:
{code}
...
properties/config.prop
pdf
resource2
false
configurations
true
**/properties
...
{code}
but now, it isn't achieve this functionality.
> Filtering doesn't work as expected after switching from
> maven-filtering:1.0-beta-2 to maven-filtering:1.1
> --
>
> Key: MWAR-305
> URL: https://jira.codehaus.org/browse/MWAR-305
> Project: Maven WAR Plugin
> Issue Type: Bug
>Reporter: Grzegorz Grzybek
>Priority: Critical
>
> {{maven-filtering:1.0-beta-3}} introduced a setting
> {{org.apache.maven.shared.filtering.AbstractMavenFilteringRequest.injectProjectBuildFilters}}
> defaulted to {{false}}.
> While constructing {{defaultFilterWrappers}} in
> {{org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(MavenProject,
> File)}} the {{MavenResourcesExecution}} is constructed.
> In {{maven-filtering:1.0-beta-2}} there's unconditional call:
> {code:java}
> loadProperties( filterProperties, mavenProject.getBuild().getFilters(),
> baseProps );
> {code}
> In {{maven-filtering:1.1}}+ there's conditional call:
> {code:java}
> if ( request.isInjectProjectBuildFilters() )
> {
> List buildFilters = new ArrayList(
> request.getMavenProject().getBuild().getFilters() );
> buildFilters.removeAll( request.getFileFilters() );
> loadProperties( filterProperties, buildFilters, baseProps );
> }
> {code}
> So my filters declared (as always) in:
> {code:xml}
>
>
> ../src/config/env/envX/config.properties
>
>
> {code}
> are *not taken into account* forcing me to set (configuration duplicate)
> [maven-war-plugin's
> filter|http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#filters]
> property.
> Please change (in
> {{org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp()}}) the line:
> {code:xml}
> mavenResourcesExecution.setFilters( filters );
> {code}
> to
> {code:xml}
> mavenResourcesExecution.setFilters( filters == null ?
> project.getBuild().getFilters() : filters );
> {code}
> regards
> Grzegorz Grzybek
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-301) webResources filtering not happening properly
[ https://jira.codehaus.org/browse/MWAR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333889#comment-333889 ] Gabriel Belingueres commented on MWAR-301: -- Please see https://jira.codehaus.org/browse/MWAR-303. May be it is related to this issue. I attached a patch with a modified IT case for the plugin that shows the problem. (My current workaround is keep using version 2.3.) TIA, Gabriel > webResources filtering not happening properly > - > > Key: MWAR-301 > URL: https://jira.codehaus.org/browse/MWAR-301 > Project: Maven WAR Plugin > Issue Type: Bug > Components: filtering >Affects Versions: 2.4 > Environment: Linux >Reporter: Mukarram Baig > Attachments: mwar-tester.zip > > > I noticed that webResources were not getting filtered when I upgraded from > 2.3 to 2.4 and could not find an open issue related to it, so letting you > guys know if I am doing something incorrect that was working till 2.3 and got > fixed in 2.4. I am attaching a sample project where a JS file was getting > filtered properly when using 2.3 and not when using 2.4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-99) InstallAtEnd should respect plugin-configuration per project
[
https://jira.codehaus.org/browse/MINSTALL-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MINSTALL-99.
--
Resolution: Fixed
Fix Version/s: 2.5.1
Assignee: Robert Scholte
Fixed in [r1530748|http://svn.apache.org/r1530748]
> InstallAtEnd should respect plugin-configuration per project
>
>
> Key: MINSTALL-99
> URL: https://jira.codehaus.org/browse/MINSTALL-99
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install
>Affects Versions: 2.5
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: 2.5.1
>
>
> For {{installAtEnd}} the plugin should keep track of which artifacts should
> be installed and with which configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1038) Regression: Method depends on nonexistent group
Gili created SUREFIRE-1038:
--
Summary: Regression: Method depends on nonexistent group
Key: SUREFIRE-1038
URL: https://jira.codehaus.org/browse/SUREFIRE-1038
Project: Maven Surefire
Issue Type: Bug
Components: TestNG support
Affects Versions: 2.16
Reporter: Gili
Priority: Critical
Version 2.16 contains a regression that prevents the use of TestNG groups.
Version 2.15 works fine.
When I run my unit tests I get the following error:
{code}
Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test
(default-test) on project web.backend: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.16:test failed: There was an
error in the forked process
org.testng.TestNGException:
DependencyMap::Method "CallTest.createCall()[pri:0,
instance:com.vtlr.web.backend.resource.CallTest@53635ac1]" depends on
nonexistent group "department"
at org.testng.DependencyMap.getMethodsThatBelongTo(DependencyMap.java:46)
at org.testng.TestRunner.createDynamicGraph(TestRunner.java:1074)
at org.testng.TestRunner.privateRun(TestRunner.java:734)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
at org.testng.TestNG.run(TestNG.java:1057)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:91)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
{code}
I checked and group "department" exists. Furthermore, downgrading back to 2.15
makes the problem go away.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-699) Allow inclusion of files outside of src/site into the built site
Archimedes Trajano created MSITE-699: Summary: Allow inclusion of files outside of src/site into the built site Key: MSITE-699 URL: https://jira.codehaus.org/browse/MSITE-699 Project: Maven Site Plugin Issue Type: Improvement Affects Versions: 3.3 Reporter: Archimedes Trajano I would like to have the capability of using README.md on the root of the project as the index.html that gets generated. This means it should also allow specifying which doxia to use. I was thinking of -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
