[jira] (MNGSITE-195) Default folder layout documentation update
[
https://jira.codehaus.org/browse/MNGSITE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MNGSITE-195:
Description:
Based [on the discussion on the mailing
list|http://maven.40175.n5.nabble.com/maven-assembly-plugin-Maven-default-folder-layout-td5787276.html]
the folder layout should be changed according to the following:
src/main
* are files required during compile time (production)
** src/main/java
** src/main/resources
** src/main/filters
src/test
* are files required during test time (unit testing; based on naming
schema we could also have integration tests here)
** src/test/java
** src/test/resources
** src/test/filters
src/it
* are files required during integration tests (primarily for plugins)
src/assembly
* for assembly descriptors and appropriate filter property files.
src/main/config
* for configuration files.
src/main/filters
* Resource filter files
src/main/scripts
* Application/Library scripts
src/main/webapp
* Web application sources
src/site
* Maven Site
In the end this means currently only {{src/it}} must be added to the default
folder layout page.
{{src/config}} is currently under discussion
was:
Based [on the discussion on the mailing
list|http://maven.40175.n5.nabble.com/maven-assembly-plugin-Maven-default-folder-layout-td5787276.html]
the folder layout should be changed according to the following:
src/main
* are files required during compile time (production)
** src/main/java
** src/main/resources
** src/main/filters
src/test
* are files required during test time (unit testing; based on naming
schema we could also have integration tests here)
** src/test/java
** src/test/resources
** src/test/filters
src/it
* are files required during integration tests (primarily for plugins)
src/assembly
* for assembly descriptors and appropriate filter property files.
src/config
* for configuration files.
src/main/filters
* Resource filter files
src/main/scripts
* Application/Library scripts
src/main/webapp
* Web application sources
src/site
* Maven Site
In the end this means currently only {{src/it}} must be added to the default
folder layout page.
{{src/config}} is currently under discussion
> Default folder layout documentation update
> --
>
> Key: MNGSITE-195
> URL: https://jira.codehaus.org/browse/MNGSITE-195
> Project: Maven Project Web Site
> Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> Based [on the discussion on the mailing
> list|http://maven.40175.n5.nabble.com/maven-assembly-plugin-Maven-default-folder-layout-td5787276.html]
> the folder layout should be changed according to the following:
> src/main
> * are files required during compile time (production)
> ** src/main/java
> ** src/main/resources
> ** src/main/filters
> src/test
> * are files required during test time (unit testing; based on naming
> schema we could also have integration tests here)
> ** src/test/java
> ** src/test/resources
> ** src/test/filters
> src/it
> * are files required during integration tests (primarily for plugins)
> src/assembly
> * for assembly descriptors and appropriate filter property files.
> src/main/config
> * for configuration files.
> src/main/filters
> * Resource filter files
> src/main/scripts
> * Application/Library scripts
> src/main/webapp
> * Web application sources
> src/site
> * Maven Site
> In the end this means currently only {{src/it}} must be added to the default
> folder layout page.
> {{src/config}} is currently under discussion
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNGSITE-195) Default folder layout documentation update
[
https://jira.codehaus.org/browse/MNGSITE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MNGSITE-195:
Description:
Based [on the discussion on the mailing
list|http://maven.40175.n5.nabble.com/maven-assembly-plugin-Maven-default-folder-layout-td5787276.html]
the folder layout should be changed according to the following:
src/main
* are files required during compile time (production)
** src/main/java
** src/main/resources
** src/main/filters
src/test
* are files required during test time (unit testing; based on naming
schema we could also have integration tests here)
** src/test/java
** src/test/resources
** src/test/filters
src/it
* are files required during integration tests (primarily for plugins)
src/assembly
* for assembly descriptors and appropriate filter property files.
src/main/config
* for configuration files.
src/main/filters
* Resource filter files
src/main/scripts
* Application/Library scripts
src/main/webapp
* Web application sources
src/site
* Maven Site
In the end this means currently only {{src/it}} must be added to the default
folder layout page.
was:
Based [on the discussion on the mailing
list|http://maven.40175.n5.nabble.com/maven-assembly-plugin-Maven-default-folder-layout-td5787276.html]
the folder layout should be changed according to the following:
src/main
* are files required during compile time (production)
** src/main/java
** src/main/resources
** src/main/filters
src/test
* are files required during test time (unit testing; based on naming
schema we could also have integration tests here)
** src/test/java
** src/test/resources
** src/test/filters
src/it
* are files required during integration tests (primarily for plugins)
src/assembly
* for assembly descriptors and appropriate filter property files.
src/main/config
* for configuration files.
src/main/filters
* Resource filter files
src/main/scripts
* Application/Library scripts
src/main/webapp
* Web application sources
src/site
* Maven Site
In the end this means currently only {{src/it}} must be added to the default
folder layout page.
{{src/config}} is currently under discussion
> Default folder layout documentation update
> --
>
> Key: MNGSITE-195
> URL: https://jira.codehaus.org/browse/MNGSITE-195
> Project: Maven Project Web Site
> Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> Based [on the discussion on the mailing
> list|http://maven.40175.n5.nabble.com/maven-assembly-plugin-Maven-default-folder-layout-td5787276.html]
> the folder layout should be changed according to the following:
> src/main
> * are files required during compile time (production)
> ** src/main/java
> ** src/main/resources
> ** src/main/filters
> src/test
> * are files required during test time (unit testing; based on naming
> schema we could also have integration tests here)
> ** src/test/java
> ** src/test/resources
> ** src/test/filters
> src/it
> * are files required during integration tests (primarily for plugins)
> src/assembly
> * for assembly descriptors and appropriate filter property files.
> src/main/config
> * for configuration files.
> src/main/filters
> * Resource filter files
> src/main/scripts
> * Application/Library scripts
> src/main/webapp
> * Web application sources
> src/site
> * Maven Site
> In the end this means currently only {{src/it}} must be added to the default
> folder layout page.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSITE-697) Add ability to filter site resources
[
https://jira.codehaus.org/browse/MSITE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342929#comment-342929
]
Michael Osipov commented on MSITE-697:
--
We do have this already, add {{.vm}} and the resource should be filtered.
> Add ability to filter site resources
>
>
> Key: MSITE-697
> URL: https://jira.codehaus.org/browse/MSITE-697
> Project: Maven Site Plugin
> Issue Type: New Feature
>Affects Versions: 3.3
>Reporter: Dennis Lundberg
>
> It would be great if it was possible to filter the site resources, similar to
> how you can filter web resources in the WAR Plugin. This feature would need
> to be configurable and default to being off, for backwards compatibility.
> There should also be a configuration parameter for which file extensions
> should be excluded from the filtering process. That should have a good
> default value covering the standard image formats (gif, jpg and png) and also
> PDFs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGES-329) RestJiraDownloader does not handle issuetype
Dennis Lundberg created MCHANGES-329: Summary: RestJiraDownloader does not handle issuetype Key: MCHANGES-329 URL: https://jira.codehaus.org/browse/MCHANGES-329 Project: Maven Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.9 Reporter: Dennis Lundberg If you set the parameter useJQL the plugin uses the RestJiraDownloader to fetch issues from JIRA. It currently does not parse the issuetype field, which results in all issues being of type "Task". -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-329) RestJiraDownloader does not handle issuetype
[ https://jira.codehaus.org/browse/MCHANGES-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg reassigned MCHANGES-329: Assignee: Dennis Lundberg > RestJiraDownloader does not handle issuetype > > > Key: MCHANGES-329 > URL: https://jira.codehaus.org/browse/MCHANGES-329 > Project: Maven Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.9 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.10 > > > If you set the parameter useJQL the plugin uses the RestJiraDownloader to > fetch issues from JIRA. It currently does not parse the issuetype field, > which results in all issues being of type "Task". -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-329) RestJiraDownloader does not handle issuetype
[ https://jira.codehaus.org/browse/MCHANGES-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHANGES-329: - Fix Version/s: 2.10 > RestJiraDownloader does not handle issuetype > > > Key: MCHANGES-329 > URL: https://jira.codehaus.org/browse/MCHANGES-329 > Project: Maven Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.9 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.10 > > > If you set the parameter useJQL the plugin uses the RestJiraDownloader to > fetch issues from JIRA. It currently does not parse the issuetype field, > which results in all issues being of type "Task". -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-329) RestJiraDownloader does not handle components, type, updated or version
[ https://jira.codehaus.org/browse/MCHANGES-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHANGES-329: - Summary: RestJiraDownloader does not handle components, type, updated or version (was: RestJiraDownloader does not handle issuetype) > RestJiraDownloader does not handle components, type, updated or version > --- > > Key: MCHANGES-329 > URL: https://jira.codehaus.org/browse/MCHANGES-329 > Project: Maven Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.9 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.10 > > > If you set the parameter useJQL the plugin uses the RestJiraDownloader to > fetch issues from JIRA. It currently does not parse the issuetype field, > which results in all issues being of type "Task". -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-329) RestJiraDownloader does not handle components, type, updated or version
[
https://jira.codehaus.org/browse/MCHANGES-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MCHANGES-329:
-
Description:
If you set the parameter useJQL the plugin uses the RestJiraDownloader to fetch
issues from JIRA. It currently does not parse the {{issuetype}} field, which
results in all issues being of type "Task". The {{components}} field is also
not parsed.
The fields {{updated}} and {{version}} are parsed, but in the wrong way, always
returning null.
was:If you set the parameter useJQL the plugin uses the RestJiraDownloader to
fetch issues from JIRA. It currently does not parse the issuetype field, which
results in all issues being of type "Task".
> RestJiraDownloader does not handle components, type, updated or version
> ---
>
> Key: MCHANGES-329
> URL: https://jira.codehaus.org/browse/MCHANGES-329
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.9
>Reporter: Dennis Lundberg
>Assignee: Dennis Lundberg
> Fix For: 2.10
>
>
> If you set the parameter useJQL the plugin uses the RestJiraDownloader to
> fetch issues from JIRA. It currently does not parse the {{issuetype}} field,
> which results in all issues being of type "Task". The {{components}} field is
> also not parsed.
> The fields {{updated}} and {{version}} are parsed, but in the wrong way,
> always returning null.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGES-329) RestJiraDownloader does not handle components, type, updated or version
[
https://jira.codehaus.org/browse/MCHANGES-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCHANGES-329.
Resolution: Fixed
Fixed in [r1577954|http://svn.apache.org/viewvc?view=revision&revision=1577954].
> RestJiraDownloader does not handle components, type, updated or version
> ---
>
> Key: MCHANGES-329
> URL: https://jira.codehaus.org/browse/MCHANGES-329
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.9
>Reporter: Dennis Lundberg
>Assignee: Dennis Lundberg
> Fix For: 2.10
>
>
> If you set the parameter useJQL the plugin uses the RestJiraDownloader to
> fetch issues from JIRA. It currently does not parse the {{issuetype}} field,
> which results in all issues being of type "Task". The {{components}} field is
> also not parsed.
> The fields {{updated}} and {{version}} are parsed, but in the wrong way,
> always returning null.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGES-329) RestJiraDownloader does not handle components, type, updated or version
[
https://jira.codehaus.org/browse/MCHANGES-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MCHANGES-329:
-
Description:
If the plugin uses the RestJiraDownloader to fetch issues from JIRA, it does
not parse the {{issuetype}} field. This results in all issues being of type
"Task". The {{components}} field is also not parsed.
The fields {{updated}} and {{version}} are parsed, but in the wrong way, always
returning null.
was:
If you set the parameter useJQL the plugin uses the RestJiraDownloader to fetch
issues from JIRA. It currently does not parse the {{issuetype}} field, which
results in all issues being of type "Task". The {{components}} field is also
not parsed.
The fields {{updated}} and {{version}} are parsed, but in the wrong way, always
returning null.
> RestJiraDownloader does not handle components, type, updated or version
> ---
>
> Key: MCHANGES-329
> URL: https://jira.codehaus.org/browse/MCHANGES-329
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.9
>Reporter: Dennis Lundberg
>Assignee: Dennis Lundberg
> Fix For: 2.10
>
>
> If the plugin uses the RestJiraDownloader to fetch issues from JIRA, it does
> not parse the {{issuetype}} field. This results in all issues being of type
> "Task". The {{components}} field is also not parsed.
> The fields {{updated}} and {{version}} are parsed, but in the wrong way,
> always returning null.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
