[jira] [Commented] (MRELEASE-294) Generated release-pom.xml does not contain plugins configured in a super pom.
[
https://issues.apache.org/jira/browse/MRELEASE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533435#comment-16533435
]
Bruno Marti commented on MRELEASE-294:
--
problem still exists in version 2.5.3.
Why not using help:effective-pom to generate release-pom.xml?
I would really appreciate this feature(y)
> Generated release-pom.xml does not contain plugins configured in a super pom.
> -
>
> Key: MRELEASE-294
> URL: https://issues.apache.org/jira/browse/MRELEASE-294
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare-with-pom
>Affects Versions: 2.0-beta-6
>Reporter: Reinhard Nägele
>Priority: Major
> Attachments: patch.txt
>
>
> Finally, since 2.0-beta-6 it has been possible to generate release poms.
> Unfortunately, plugins configured in a super pom don't make it into the
> {{release-pom.xml}}.
> We have a multi-module project. Each module inherits from a super pom that
> also defines the modules. The super pom, amongst others, configures the
> compiler plugin for {{source}} and {{target 1.5}}. Since these plugin
> configurations only make it into the release pom of the super pom, but not
> into the release poms of the modules, the modules fail to build using the
> release plugin.
> {{generics are not supported in -source 1.3 (try -source 1.5 to enable
> generics)}}
> {{annotations are not supported in -source 1.3 (try -source 1.5 to enable
> annotations) @Override}}
> So, we still have to set {{generateReleasePoms}} to {{false}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MWAR-420) build failure in lifecycle deploy: 'Could not copy webapp sources'
Bruno Marti created MWAR-420:
Summary: build failure in lifecycle deploy: 'Could not copy webapp
sources'
Key: MWAR-420
URL: https://issues.apache.org/jira/browse/MWAR-420
Project: Maven WAR Plugin
Issue Type: Bug
Affects Versions: 3.2.2, 3.2.1, 3.2.0
Reporter: Bruno Marti
Since version 3.2.x there is a build failure in maven-war-plugin on lifecycle
'deploy'.
{code:java}
mvn cean install deploy -e{code}
If you build sample webapp (see attachement) with version 3.2.2 following error
occurs:
{code:java}
[INFO] --- maven-war-plugin:3.2.2:war (default-war) @ testWarPlugin ---
[INFO] Packaging webapp
[INFO] Assembling webapp [testWarPlugin] in
[C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [C:\TEMP\testWarPlugin\src\main\webapp]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5.106 s
[INFO] Finished at: 2018-11-07T10:11:58+01:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-war-plugin:3.2.2:war (default-war) on project
testWarPlugin: Could not copy webapp sources
[C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]:
C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT\images\ajaxloading.gif
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-war-plugin:3.2.2:war (default-war) on project
testWarPlugin: Could not copy webapp sources
[C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]
...
Caused by: java.nio.file.AccessDeniedException:
C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT\images\ajaxloading.gif
at sun.nio.fs.WindowsException.translateToIOException
(WindowsException.java:83)
at sun.nio.fs.WindowsException.rethrowAsIOException
(WindowsException.java:97)
at sun.nio.fs.WindowsException.rethrowAsIOException
(WindowsException.java:102)
at sun.nio.fs.WindowsFileCopy.copy (WindowsFileCopy.java:165)
at sun.nio.fs.WindowsFileSystemProvider.copy
(WindowsFileSystemProvider.java:278)
at java.nio.file.Files.copy (Files.java:1274)
{code}
It only occurs on {color:#FF}windows{color} and with
maven-war-plugin{color:#FF} 3.2.x{color}.
Version {color:#14892c}3.1.0 and older{color} works fine
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MWAR-420) build failure in lifecycle deploy: 'Could not copy webapp sources'
[
https://issues.apache.org/jira/browse/MWAR-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Marti updated MWAR-420:
-
Attachment: build-error.log
> build failure in lifecycle deploy: 'Could not copy webapp sources'
> --
>
> Key: MWAR-420
> URL: https://issues.apache.org/jira/browse/MWAR-420
> Project: Maven WAR Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0, 3.2.1, 3.2.2
>Reporter: Bruno Marti
>Priority: Major
> Attachments: build-error.log
>
>
> Since version 3.2.x there is a build failure in maven-war-plugin on lifecycle
> 'deploy'.
> {code:java}
> mvn cean install deploy -e{code}
> If you build sample webapp (see attachement) with version 3.2.2 following
> error occurs:
> {code:java}
> [INFO] --- maven-war-plugin:3.2.2:war (default-war) @ testWarPlugin ---
> [INFO] Packaging webapp
> [INFO] Assembling webapp [testWarPlugin] in
> [C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]
> [INFO] Processing war project
> [INFO] Copying webapp resources [C:\TEMP\testWarPlugin\src\main\webapp]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 5.106 s
> [INFO] Finished at: 2018-11-07T10:11:58+01:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-war-plugin:3.2.2:war (default-war) on project
> testWarPlugin: Could not copy webapp sources
> [C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]:
> C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT\images\ajaxloading.gif
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-war-plugin:3.2.2:war (default-war) on
> project testWarPlugin: Could not copy webapp sources
> [C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]
> ...
> Caused by: java.nio.file.AccessDeniedException:
> C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT\images\ajaxloading.gif
> at sun.nio.fs.WindowsException.translateToIOException
> (WindowsException.java:83)
> at sun.nio.fs.WindowsException.rethrowAsIOException
> (WindowsException.java:97)
> at sun.nio.fs.WindowsException.rethrowAsIOException
> (WindowsException.java:102)
> at sun.nio.fs.WindowsFileCopy.copy (WindowsFileCopy.java:165)
> at sun.nio.fs.WindowsFileSystemProvider.copy
> (WindowsFileSystemProvider.java:278)
> at java.nio.file.Files.copy (Files.java:1274)
> {code}
> It only occurs on {color:#FF}windows{color} and with
> maven-war-plugin{color:#FF} 3.2.x{color}.
> Version {color:#14892c}3.1.0 and older{color} works fine
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MWAR-420) build failure in lifecycle deploy: 'Could not copy webapp sources'
[
https://issues.apache.org/jira/browse/MWAR-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Marti updated MWAR-420:
-
Attachment: testWarPlugin.zip
> build failure in lifecycle deploy: 'Could not copy webapp sources'
> --
>
> Key: MWAR-420
> URL: https://issues.apache.org/jira/browse/MWAR-420
> Project: Maven WAR Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0, 3.2.1, 3.2.2
>Reporter: Bruno Marti
>Priority: Major
> Attachments: build-error.log, testWarPlugin.zip
>
>
> Since version 3.2.x there is a build failure in maven-war-plugin on lifecycle
> 'deploy'.
> {code:java}
> mvn cean install deploy -e{code}
> If you build sample webapp (see attachement) with version 3.2.2 following
> error occurs:
> {code:java}
> [INFO] --- maven-war-plugin:3.2.2:war (default-war) @ testWarPlugin ---
> [INFO] Packaging webapp
> [INFO] Assembling webapp [testWarPlugin] in
> [C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]
> [INFO] Processing war project
> [INFO] Copying webapp resources [C:\TEMP\testWarPlugin\src\main\webapp]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 5.106 s
> [INFO] Finished at: 2018-11-07T10:11:58+01:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-war-plugin:3.2.2:war (default-war) on project
> testWarPlugin: Could not copy webapp sources
> [C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]:
> C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT\images\ajaxloading.gif
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-war-plugin:3.2.2:war (default-war) on
> project testWarPlugin: Could not copy webapp sources
> [C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]
> ...
> Caused by: java.nio.file.AccessDeniedException:
> C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT\images\ajaxloading.gif
> at sun.nio.fs.WindowsException.translateToIOException
> (WindowsException.java:83)
> at sun.nio.fs.WindowsException.rethrowAsIOException
> (WindowsException.java:97)
> at sun.nio.fs.WindowsException.rethrowAsIOException
> (WindowsException.java:102)
> at sun.nio.fs.WindowsFileCopy.copy (WindowsFileCopy.java:165)
> at sun.nio.fs.WindowsFileSystemProvider.copy
> (WindowsFileSystemProvider.java:278)
> at java.nio.file.Files.copy (Files.java:1274)
> {code}
> It only occurs on {color:#FF}windows{color} and with
> maven-war-plugin{color:#FF} 3.2.x{color}.
> Version {color:#14892c}3.1.0 and older{color} works fine
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MWAR-420) build failure in lifecycle deploy: 'Could not copy webapp sources'
[
https://issues.apache.org/jira/browse/MWAR-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Marti updated MWAR-420:
-
Description:
Since version 3.2.x there is a build failure in maven-war-plugin on lifecycle
'deploy'.
{code:java}
mvn cean install deploy -e{code}
If you build sample webapp (see attachement: [^testWarPlugin.zip]) with version
3.2.2 following error occurs:
{code:java}
[INFO] --- maven-war-plugin:3.2.2:war (default-war) @ testWarPlugin ---
[INFO] Packaging webapp
[INFO] Assembling webapp [testWarPlugin] in
[C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [C:\TEMP\testWarPlugin\src\main\webapp]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5.106 s
[INFO] Finished at: 2018-11-07T10:11:58+01:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-war-plugin:3.2.2:war (default-war) on project
testWarPlugin: Could not copy webapp sources
[C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]:
C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT\images\ajaxloading.gif
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-war-plugin:3.2.2:war (default-war) on project
testWarPlugin: Could not copy webapp sources
[C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]
...
Caused by: java.nio.file.AccessDeniedException:
C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT\images\ajaxloading.gif
at sun.nio.fs.WindowsException.translateToIOException
(WindowsException.java:83)
at sun.nio.fs.WindowsException.rethrowAsIOException
(WindowsException.java:97)
at sun.nio.fs.WindowsException.rethrowAsIOException
(WindowsException.java:102)
at sun.nio.fs.WindowsFileCopy.copy (WindowsFileCopy.java:165)
at sun.nio.fs.WindowsFileSystemProvider.copy
(WindowsFileSystemProvider.java:278)
at java.nio.file.Files.copy (Files.java:1274)
{code}
It only occurs on {color:#ff}windows{color} and with
maven-war-plugin{color:#ff} 3.2.x{color}. Fullstacktrace here:
[^build-error.log]
Version {color:#14892c}3.1.0 and older{color} works fine
was:
Since version 3.2.x there is a build failure in maven-war-plugin on lifecycle
'deploy'.
{code:java}
mvn cean install deploy -e{code}
If you build sample webapp (see attachement) with version 3.2.2 following error
occurs:
{code:java}
[INFO] --- maven-war-plugin:3.2.2:war (default-war) @ testWarPlugin ---
[INFO] Packaging webapp
[INFO] Assembling webapp [testWarPlugin] in
[C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [C:\TEMP\testWarPlugin\src\main\webapp]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5.106 s
[INFO] Finished at: 2018-11-07T10:11:58+01:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-war-plugin:3.2.2:war (default-war) on project
testWarPlugin: Could not copy webapp sources
[C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]:
C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT\images\ajaxloading.gif
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-war-plugin:3.2.2:war (default-war) on project
testWarPlugin: Could not copy webapp sources
[C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT]
...
Caused by: java.nio.file.AccessDeniedException:
C:\TEMP\testWarPlugin\target\testWarPlugin-1.0-SNAPSHOT\images\ajaxloading.gif
at sun.nio.fs.WindowsException.translateToIOException
(WindowsException.java:83)
at sun.nio.fs.WindowsException.rethrowAsIOException
(WindowsException.java:97)
at sun.nio.fs.WindowsException.rethrowAsIOException
(WindowsException.java:102)
at sun.nio.fs.WindowsFileCopy.copy (WindowsFileCopy.java:165)
at sun.nio.fs.WindowsFileSystemProvider.copy
(WindowsFileSystemProvider.java:278)
at java.nio.file.Files.copy (Files.java:1274)
{code}
It only occurs on {color:#FF}windows{color} and with
maven-war-plugin{color:#FF} 3.2.x{color}.
Version {color:#14892c}3.1.0 and older{color} works fine
> build failure in lifecycle deploy: 'Could not copy webapp sources'
> --
>
> Key: MWAR-420
> URL: https://issues.apache.org/jira/browse/MWAR-420
> Project: Maven WAR Plugin
> Issue Type: Bug
>Affects
[jira] Commented: (MCHANGES-115) Add title to type images
[ http://jira.codehaus.org/browse/MCHANGES-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267033#action_267033 ] Bruno Marti commented on MCHANGES-115: -- yes, because a little title on the images would be helpful and the layout is ok, too. > Add title to type images > > > Key: MCHANGES-115 > URL: http://jira.codehaus.org/browse/MCHANGES-115 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: changes.xml >Affects Versions: 2.0 >Reporter: Michael Osipov > Fix For: 2.5 > > Attachments: screen capture 2011-5-1-19-29-54.png > > > Right now the type images are just images without any text. Every unknowing > person cannot identify the affiliation of this image to its type. I would be > great to add a title attribute to the img tag. Would clarify a lot. > Tried myself to create a patch and found out that this issue is related to > DOXIA-75 but Doxia 1.0-beta-1 has not been released yet. -- 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] (MCHANGES-98) Add paging capatibility to changes report
[
https://jira.codehaus.org/browse/MCHANGES-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347360#comment-347360
]
Bruno Marti commented on MCHANGES-98:
-
Why not using footable-jquery [http://fooplugins.com/plugins/footable-jquery/]
and adding it on html rendering?
I've added a little demo ZIP, which demonstrates pagination in a current
changes-report.htm as a result report
*usage:*
{code}
$(function () {
$('.footable').footable();
});
{code}
{code}
Version
Date
Description
...
{code}
> Add paging capatibility to changes report
> -
>
> Key: MCHANGES-98
> URL: https://jira.codehaus.org/browse/MCHANGES-98
> Project: Maven Changes Plugin
> Issue Type: Improvement
> Components: changes.xml
>Affects Versions: 2.0-beta-3
>Reporter: Benjamin Bentmann
> Attachments: footable-pagination.zip
>
>
> The current report generation does not scale well for projects with a large
> release history because one ends up with a very long HTML page. Preferable
> would be to introduce a configuration parameter like "releasesPerPage" that
> the mojo could use to split up the change log onto several web pages.
> Usually, such paging should only apply to web content and not something like
> PDF or other print-related formats.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGES-98) Add paging capatibility to changes report
[ https://jira.codehaus.org/browse/MCHANGES-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Marti updated MCHANGES-98: Attachment: footable-pagination.zip footable pagination sample > Add paging capatibility to changes report > - > > Key: MCHANGES-98 > URL: https://jira.codehaus.org/browse/MCHANGES-98 > Project: Maven Changes Plugin > Issue Type: Improvement > Components: changes.xml >Affects Versions: 2.0-beta-3 >Reporter: Benjamin Bentmann > Attachments: footable-pagination.zip > > > The current report generation does not scale well for projects with a large > release history because one ends up with a very long HTML page. Preferable > would be to introduce a configuration parameter like "releasesPerPage" that > the mojo could use to split up the change log onto several web pages. > Usually, such paging should only apply to web content and not something like > PDF or other print-related formats. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-98) Add paging capatibility to changes report
[ https://jira.codehaus.org/browse/MCHANGES-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Marti updated MCHANGES-98: Attachment: screenshot-1.jpg changes-report sample with pagination > Add paging capatibility to changes report > - > > Key: MCHANGES-98 > URL: https://jira.codehaus.org/browse/MCHANGES-98 > Project: Maven Changes Plugin > Issue Type: Improvement > Components: changes.xml >Affects Versions: 2.0-beta-3 >Reporter: Benjamin Bentmann > Attachments: footable-pagination.zip, screenshot-1.jpg > > > The current report generation does not scale well for projects with a large > release history because one ends up with a very long HTML page. Preferable > would be to introduce a configuration parameter like "releasesPerPage" that > the mojo could use to split up the change log onto several web pages. > Usually, such paging should only apply to web content and not something like > PDF or other print-related formats. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-308) Support filters when using REST API / JQL
[
https://jira.codehaus.org/browse/MCHANGES-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349354#comment-349354
]
Bruno Marti commented on MCHANGES-308:
--
current patch does not honor maven variables.
this *works*:
{code}labels=my-custom-label{code}
this *doesn't work*:
{code}labels=${project_specification_title}{code}
> Support filters when using REST API / JQL
> -
>
> Key: MCHANGES-308
> URL: https://jira.codehaus.org/browse/MCHANGES-308
> Project: Maven Changes Plugin
> Issue Type: Wish
> Components: jira
>Affects Versions: 2.8, 2.9
>Reporter: Johannes Odland
> Attachments:
> MCHANGES-308__Support_filters_when_using_REST_API___JQL.patch
>
>
> The original JiraDownloader supported a custom filter for downloading issues.
> After migrating to REST, the
> JiraDownloader/ClassicDownloader/RestJiraDownloader does not support this
> filter.
> Can you reintroduce support for custom filter?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGES-308) Support filters when using REST API / JQL
[
https://jira.codehaus.org/browse/MCHANGES-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Marti updated MCHANGES-308:
-
Comment: was deleted
(was: current patch does not honor maven variables.
this *works*:
{code}labels=my-custom-label{code}
this *doesn't work*:
{code}labels=${project_specification_title}{code})
> Support filters when using REST API / JQL
> -
>
> Key: MCHANGES-308
> URL: https://jira.codehaus.org/browse/MCHANGES-308
> Project: Maven Changes Plugin
> Issue Type: Wish
> Components: jira
>Affects Versions: 2.8, 2.9
>Reporter: Johannes Odland
> Attachments:
> MCHANGES-308__Support_filters_when_using_REST_API___JQL.patch
>
>
> The original JiraDownloader supported a custom filter for downloading issues.
> After migrating to REST, the
> JiraDownloader/ClassicDownloader/RestJiraDownloader does not support this
> filter.
> Can you reintroduce support for custom filter?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGES-308) Support filters when using REST API / JQL
[
https://jira.codehaus.org/browse/MCHANGES-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349356#comment-349356
]
Bruno Marti commented on MCHANGES-308:
--
Patch is working great.
You can also use filters like this:
Filter by specific labels
{code}labels=${project.name}{code}
> Support filters when using REST API / JQL
> -
>
> Key: MCHANGES-308
> URL: https://jira.codehaus.org/browse/MCHANGES-308
> Project: Maven Changes Plugin
> Issue Type: Wish
> Components: jira
>Affects Versions: 2.8, 2.9
>Reporter: Johannes Odland
> Attachments:
> MCHANGES-308__Support_filters_when_using_REST_API___JQL.patch
>
>
> The original JiraDownloader supported a custom filter for downloading issues.
> After migrating to REST, the
> JiraDownloader/ClassicDownloader/RestJiraDownloader does not support this
> filter.
> Can you reintroduce support for custom filter?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] Created: (MJAVADOC-294) javadoc:fix add first sentence ends proper punctuation
javadoc:fix add first sentence ends proper punctuation -- Key: MJAVADOC-294 URL: http://jira.codehaus.org/browse/MJAVADOC-294 Project: Maven 2.x Javadoc Plugin Issue Type: New Feature Affects Versions: 2.7 Environment: win xp, maven 2.2.1 Reporter: Bruno Marti javadoc:fix fixes automatically missing first sentences like /** *myMethode * But there is a missing sentence-end punctuation (*.?!*). This is for the maven-checkstyle-plugin, rule: JavadocStyle Otherwise checkstyle reports a javadoc error by default. Better: /** *myMethode. * -- 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: (MCHANGES-213) Update Velocity 1.7
Update Velocity 1.7 --- Key: MCHANGES-213 URL: http://jira.codehaus.org/browse/MCHANGES-213 Project: Maven 2.x Changes Plugin Issue Type: Improvement Affects Versions: 2.3 Environment: jdk 6, maven 2.2.1 Reporter: Bruno Marti whats about with updating to velocity 1.7 -- 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: (MCHANGES-213) Update Velocity 1.7
[ http://jira.codehaus.org/browse/MCHANGES-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252529#action_252529 ] Bruno Marti commented on MCHANGES-213: -- I'm so sorry, I cannot remember what my original cause for this update wish was. But there are lots of fixes since velocity engine 1.5 to 1.7. Why not updating? Close this, if you dont think so. greetings > Update Velocity 1.7 > --- > > Key: MCHANGES-213 > URL: http://jira.codehaus.org/browse/MCHANGES-213 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement >Affects Versions: 2.3 > Environment: jdk 6, maven 2.2.1 >Reporter: Bruno Marti > > whats about with updating to velocity 1.7 -- 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: (MCHANGES-197) Add parameter for output encoding
[
http://jira.codehaus.org/browse/MCHANGES-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252755#action_252755
]
Bruno Marti commented on MCHANGES-197:
--
I've tested. Fix works fine.
Thanks
Looking forward to next release.
> Add parameter for output encoding
> -
>
> Key: MCHANGES-197
> URL: http://jira.codehaus.org/browse/MCHANGES-197
> Project: Maven 2.x Changes Plugin
> Issue Type: New Feature
> Components: changes.xml
>Affects Versions: 2.1, 2.3
> Environment: Win XP, JDK 1.6.0_18, Maven 2.2.1
>Reporter: Bruno Marti
>Assignee: Dennis Lundberg
> Fix For: 2.4
>
> Attachments: changes_encoding.zip, screenshot-1.jpg, screenshot-2.jpg
>
>
> Add an additional parameter to define the output encoding like in site-plugin.
> __
> If I generate the changes-report by changes:changes-report, I get this in the
> html output:
> {code:xml}
> http://www.w3.org/1999/xhtml";>
>
>
> ...
> {code}
> If I generate the same changes-report by site:site, I get this:
> {code:xml}
> http://www.w3.org/1999/xhtml";>
>
>
> {code}
> Whereas, here I've defined
> _ISO-8859-1_
> and as default in the parent pom
> _ISO-8859-1_
--
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: (MANTRUN-162) Update Ant 1.8.2, avoid insufficient system resources error
Update Ant 1.8.2, avoid insufficient system resources error
---
Key: MANTRUN-162
URL: http://jira.codehaus.org/browse/MANTRUN-162
Project: Maven 2.x Antrun Plugin
Issue Type: Improvement
Affects Versions: 1.6
Environment: winxp, maven 3.0.3
Reporter: Bruno Marti
There is a bug in ant 1.8.1 on copy files bigger than 64mb.
Something like :
{code}
{code}
wont work in antrun-plugin 1.6 if the file is bigger than 64mb.
{color:red}
Error:
{color}
{code}
An Ant BuildException has occured: Failed to copy \\...my.zip to \\ due to
Insufficient system resources exist to complete the requested service -> [Help
1]
Caused by: java.io.IOException: Insufficient system resources exist to complete
the requested servic
at sun.nio.ch.FileDispatcher.write0(Native Method)
{code}
see also: [Ant Bug|https://issues.apache.org/bugzilla/show_bug.cgi?id=49341]
Update dependency Ant to 1.8.2 or use this workaround for antrun 1.6:
{code:xml}
org.apache.maven.plugins
maven-antrun-plugin
org.apache.ant
ant
1.8.2
{code}
--
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] (MCHANGES-287) JIRA report add capatibility for custom locale
Bruno Marti created MCHANGES-287:
Summary: JIRA report add capatibility for custom locale
Key: MCHANGES-287
URL: https://jira.codehaus.org/browse/MCHANGES-287
Project: Maven 2.x Changes Plugin
Issue Type: Wish
Components: jira
Affects Versions: 2.8
Environment: OS XP, Maven 3.0.4
Reporter: Bruno Marti
Priority: Minor
My JIRA Query has german dates, which cannot be converted.
Getting warning: _Element "Updated". Unparseable date: "Do, 13 Sep 2012
13:52:39 +0200". Using the pattern "EE, d MMM HH:mm:ss Z"_
this is because the dates in the jira-result.xml are in german format:
_Di, 1 Nov 2011 10:47:24 +0100_ ('Di' means Thuesday)
pls, add capatibility to override the current locale 'en' for the date
conversion to 'de', like de
--
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] (MCHANGES-288) JIRA url not fully respected
Bruno Marti created MCHANGES-288:
Summary: JIRA url not fully respected
Key: MCHANGES-288
URL: https://jira.codehaus.org/browse/MCHANGES-288
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.8
Environment: OS XP, maven 3.0.4
Reporter: Bruno Marti
Issue url is not fully used by maven-changes-plugin:2.8
have following issue url:
{quote}
JIRA
https://my.ch/prod/jira/?pid=1
{quote}
with changes-plugin:2.7.1 works well:
{quote}
[INFO] Generating "JIRA Report" report--- maven-changes-plugin:2.7.1
[DEBUG] JIRA lives at: https://my.ch/prod/jira
[DEBUG] Login URL:
https://my.ch/prod/jira/login.jsp?os_destination=/secure/&os_username=*&os_password=*
[DEBUG] Successfully logged in into JIRA.
{quote}
BUT with changes-plugin:2.8, got error:
{quote}
[INFO] Generating "JIRA Report" report--- maven-changes-plugin:2.8
[DEBUG] JIRA lives at: https://my.ch
[DEBUG] Login URL:
https://my.ch/login.jsp?os_destination=/secure/&os_username=*&os_password=*
[ERROR] Error trying to login into JIRA.
java.net.SocketException: Connection reset
{quote}
Problem is, that the additional context */prod/jira/* gets lost.
--
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] Created: (MCHANGES-194) Add pagination
Add pagination -- Key: MCHANGES-194 URL: http://jira.codehaus.org/browse/MCHANGES-194 Project: Maven 2.x Changes Plugin Issue Type: Wish Components: changes-report Affects Versions: 2.4 Reporter: Bruno Marti Priority: Minor Whats about a pagination if there are more than 10 (counter defined by parameter) Releases? -- 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: (MCHANGES-195) Manually override report textes
Manually override report textes --- Key: MCHANGES-195 URL: http://jira.codehaus.org/browse/MCHANGES-195 Project: Maven 2.x Changes Plugin Issue Type: Wish Components: changes-report Affects Versions: 2.4 Reporter: Bruno Marti Priority: Minor I should have a possibility to manually override the resource textes: - report.changes.text.thanx - report.changes.text.fixes Add a plugin parameter to override the text property in the pom Or any other suggestions? -- 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: (MCHANGES-197) Parameter for output encoding
Parameter for output encoding
-
Key: MCHANGES-197
URL: http://jira.codehaus.org/browse/MCHANGES-197
Project: Maven 2.x Changes Plugin
Issue Type: New Feature
Components: changes-report
Affects Versions: 2.3, 2.1
Environment: Win XP, JDK 1.6.0_18, Maven 2.2.1
Reporter: Bruno Marti
Add an additional parameter to define the output encoding like in site-plugin.
__
If I generate the changes-report by changes:changes-report, I get this in the
html output:
{code:xml}
http://www.w3.org/1999/xhtml";>
...
{code}
If I generate the same changes-report by site:site, I get this:
{code:xml}
http://www.w3.org/1999/xhtml";>
{code}
Whereas, here I've defined
_ISO-8859-1_
and as default in the parent pom
_ISO-8859-1_
--
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: (MCHANGES-197) Parameter for output encoding
[
http://jira.codehaus.org/browse/MCHANGES-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209711#action_209711
]
Bruno Marti commented on MCHANGES-197:
--
It's for german language.
The report generated from site:site does show the characters "äöü", but with
changes:changes-report not. Here there are some undefined characters.
Or do I misunderstand the encoding and charset attributes?
> Parameter for output encoding
> -
>
> Key: MCHANGES-197
> URL: http://jira.codehaus.org/browse/MCHANGES-197
> Project: Maven 2.x Changes Plugin
> Issue Type: New Feature
> Components: changes-report
>Affects Versions: 2.1, 2.3
> Environment: Win XP, JDK 1.6.0_18, Maven 2.2.1
>Reporter: Bruno Marti
>
> Add an additional parameter to define the output encoding like in site-plugin.
> __
> If I generate the changes-report by changes:changes-report, I get this in the
> html output:
> {code:xml}
> http://www.w3.org/1999/xhtml";>
>
>
> ...
> {code}
> If I generate the same changes-report by site:site, I get this:
> {code:xml}
> http://www.w3.org/1999/xhtml";>
>
>
> {code}
> Whereas, here I've defined
> _ISO-8859-1_
> and as default in the parent pom
> _ISO-8859-1_
--
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: (MCHANGES-197) Parameter for output encoding
[
http://jira.codehaus.org/browse/MCHANGES-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Marti updated MCHANGES-197:
-
Attachment: changes_encoding.zip
a little demo project.
Usage:
- mvn clean site
-> changes-report is correct, especially german characters äöü or the
publishing date
- mvn clean changes:changes-report
-> publishing date an special characters aren't rendered
> Parameter for output encoding
> -
>
> Key: MCHANGES-197
> URL: http://jira.codehaus.org/browse/MCHANGES-197
> Project: Maven 2.x Changes Plugin
> Issue Type: New Feature
> Components: changes-report
>Affects Versions: 2.1, 2.3
> Environment: Win XP, JDK 1.6.0_18, Maven 2.2.1
>Reporter: Bruno Marti
> Attachments: changes_encoding.zip
>
>
> Add an additional parameter to define the output encoding like in site-plugin.
> __
> If I generate the changes-report by changes:changes-report, I get this in the
> html output:
> {code:xml}
> http://www.w3.org/1999/xhtml";>
>
>
> ...
> {code}
> If I generate the same changes-report by site:site, I get this:
> {code:xml}
> http://www.w3.org/1999/xhtml";>
>
>
> {code}
> Whereas, here I've defined
> _ISO-8859-1_
> and as default in the parent pom
> _ISO-8859-1_
--
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: (MCHANGES-197) Parameter for output encoding
[
http://jira.codehaus.org/browse/MCHANGES-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Marti updated MCHANGES-197:
-
Attachment: screenshot-1.jpg
correct characters
> Parameter for output encoding
> -
>
> Key: MCHANGES-197
> URL: http://jira.codehaus.org/browse/MCHANGES-197
> Project: Maven 2.x Changes Plugin
> Issue Type: New Feature
> Components: changes-report
>Affects Versions: 2.1, 2.3
> Environment: Win XP, JDK 1.6.0_18, Maven 2.2.1
>Reporter: Bruno Marti
> Attachments: changes_encoding.zip, screenshot-1.jpg, screenshot-2.jpg
>
>
> Add an additional parameter to define the output encoding like in site-plugin.
> __
> If I generate the changes-report by changes:changes-report, I get this in the
> html output:
> {code:xml}
> http://www.w3.org/1999/xhtml";>
>
>
> ...
> {code}
> If I generate the same changes-report by site:site, I get this:
> {code:xml}
> http://www.w3.org/1999/xhtml";>
>
>
> {code}
> Whereas, here I've defined
> _ISO-8859-1_
> and as default in the parent pom
> _ISO-8859-1_
--
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: (MCHANGES-197) Parameter for output encoding
[
http://jira.codehaus.org/browse/MCHANGES-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Marti updated MCHANGES-197:
-
Attachment: screenshot-2.jpg
incorrect
> Parameter for output encoding
> -
>
> Key: MCHANGES-197
> URL: http://jira.codehaus.org/browse/MCHANGES-197
> Project: Maven 2.x Changes Plugin
> Issue Type: New Feature
> Components: changes-report
>Affects Versions: 2.1, 2.3
> Environment: Win XP, JDK 1.6.0_18, Maven 2.2.1
>Reporter: Bruno Marti
> Attachments: changes_encoding.zip, screenshot-1.jpg, screenshot-2.jpg
>
>
> Add an additional parameter to define the output encoding like in site-plugin.
> __
> If I generate the changes-report by changes:changes-report, I get this in the
> html output:
> {code:xml}
> http://www.w3.org/1999/xhtml";>
>
>
> ...
> {code}
> If I generate the same changes-report by site:site, I get this:
> {code:xml}
> http://www.w3.org/1999/xhtml";>
>
>
> {code}
> Whereas, here I've defined
> _ISO-8859-1_
> and as default in the parent pom
> _ISO-8859-1_
--
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-440) Site document validation fails if unable to retrieve schema (in offline mode)
[ http://jira.codehaus.org/browse/MSITE-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222580#action_222580 ] Bruno Marti commented on MSITE-440: --- I've tested with 2.1.1-SNAPSHOT No more validation exceptions. Will the fix be added to the next release? > Site document validation fails if unable to retrieve schema (in offline mode) > - > > Key: MSITE-440 > URL: http://jira.codehaus.org/browse/MSITE-440 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: doxia integration >Affects Versions: 2.1 > Environment: Maven 2.2.1 > Site Plugin 2.1-SNAPSHOT > Doxia 1.1.2 >Reporter: Dave Meibusch >Priority: Critical > Fix For: 2.1.1 > > > The changes included DOXIA-263 to validate XML documents retrieves the > DTD/Schema to validate the document. > For example, for FML, xsi:schemaLocation="http://maven.apache.org/FML/1.0.1 > http://maven.apache.org/xsd/fml-1.0.1.xsd"; the Doxia FML parser will retrieve > http://maven.apache.org/xsd/fml-1.0.1.xsd before validating the document. > If in offline mode, or in an environment without connectivity to apache.org, > site generation will appear to hang until the HTTP client code times out > (which is many minutes for each retry) then fail. > Workaround: remove the schema definition from the document (and lose > validation when online and IDE editing support). > Perhaps each Doxia parser should have some embedded schemas (for FML, at > least http://maven.apache.org/FML/1.0.1) so the entities can be resolved > locally. > Or at least a property for disabling document validation. > I don't think v2.1 can be released with this issue unresolved. -- 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: (MCHANGES-98) Add paging capatibility to changes report
[ http://jira.codehaus.org/browse/MCHANGES-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227823#action_227823 ] Bruno Marti commented on MCHANGES-98: - Does anybody care about this? There is no Assignee yet. I would really appreciate this feature > Add paging capatibility to changes report > - > > Key: MCHANGES-98 > URL: http://jira.codehaus.org/browse/MCHANGES-98 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: changes-report >Affects Versions: 2.0-beta-3 >Reporter: Benjamin Bentmann > > The current report generation does not scale well for projects with a large > release history because one ends up with a very long HTML page. Preferable > would be to introduce a configuration parameter like "releasesPerPage" that > the mojo could use to split up the change log onto several web pages. > Usually, such paging should only apply to web content and not something like > PDF or other print-related formats. -- 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: (MCHECKSTYLE-132) Upgrade to Checkstyle 5.1
[ http://jira.codehaus.org/browse/MCHECKSTYLE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229387#action_229387 ] Bruno Marti commented on MCHECKSTYLE-132: - Who installed checkstyle 5.0 on central repo? Perhaps this guy can help. I would really appreciate this improvement in the near future. > Upgrade to Checkstyle 5.1 > - > > Key: MCHECKSTYLE-132 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-132 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Improvement >Reporter: Simon Brandhof > > [Release notes|http://checkstyle.sourceforge.net/releasenotes.html] -- 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: (MCHANGES-152) page encoding ISO-8859-1 not definable
page encoding ISO-8859-1 not definable -- Key: MCHANGES-152 URL: http://jira.codehaus.org/browse/MCHANGES-152 Project: Maven 2.x Changes Plugin Issue Type: Bug Affects Versions: 2.1 Environment: Windows XP, Maven 2.09 Reporter: Bruno Marti Neither property ISO-8859-1 nor ISO-8859-1 is accepted for report generation (changes:changes-report). German characters like 'äöü' are misinterpreted. -- 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: (MCHANGES-152) page encoding ISO-8859-1 not definable
[ http://jira.codehaus.org/browse/MCHANGES-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Marti updated MCHANGES-152: - Attachment: screenshot-1.jpg see entry in Release 1.0.0 comment. Characters should be 'äöü ÄÖÜ' > page encoding ISO-8859-1 not definable > -- > > Key: MCHANGES-152 > URL: http://jira.codehaus.org/browse/MCHANGES-152 > Project: Maven 2.x Changes Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: Windows XP, Maven 2.09 >Reporter: Bruno Marti > Attachments: screenshot-1.jpg > > > Neither property > ISO-8859-1 > > nor ISO-8859-1 is > accepted for report generation (changes:changes-report). > German characters like 'äöü' are misinterpreted. -- 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: (MCHANGES-152) page encoding ISO-8859-1 not definable
[ http://jira.codehaus.org/browse/MCHANGES-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Marti updated MCHANGES-152: - Attachment: changes-report.zip a littler demo project to regenerate the bug. useage: mvn changes:changes-report > page encoding ISO-8859-1 not definable > -- > > Key: MCHANGES-152 > URL: http://jira.codehaus.org/browse/MCHANGES-152 > Project: Maven 2.x Changes Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: Windows XP, Maven 2.09 >Reporter: Bruno Marti > Attachments: changes-report.zip, screenshot-1.jpg > > > Neither property > ISO-8859-1 > > nor ISO-8859-1 is > accepted for report generation (changes:changes-report). > German characters like 'äöü' are misinterpreted. -- 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: (MECLIPSE-562) Configuration of additional source folders
Configuration of additional source folders
--
Key: MECLIPSE-562
URL: http://jira.codehaus.org/browse/MECLIPSE-562
Project: Maven 2.x Eclipse Plugin
Issue Type: Wish
Components: M2Eclipse support
Affects Versions: 2.6
Environment: M2 2.0.10
Reporter: Bruno Marti
Priority: Minor
I need to define some additional source folders in classpath (.classpath) like
Please, could you add an additional parameter to the m2eclipse goal, or perhaps
in plugins general configuration:
${project.build.directory}/generated-sources/mySources
--
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-278) site.xml attribute no more working
site.xml attribute no more working - Key: MSITE-278 URL: http://jira.codehaus.org/browse/MSITE-278 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-6, 2.0-beta-7 Environment: JDK 1.6, Maven 2.0.8 Reporter: Bruno Marti In maven 1.x xdoc site documentation there could be defined the following for menus (navigation.xml): http://maven.apache.org/maven-1.x/"; target="_new" /> ... (creates a link to maven 1.x in a new window or tab) In maven 2.x site.xml this doesn't work anymore. The target attribute is ignored. -- 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: (MCHANGES-174) Release v2.2
Release v2.2 Key: MCHANGES-174 URL: http://jira.codehaus.org/browse/MCHANGES-174 Project: Maven 2.x Changes Plugin Issue Type: Wish Affects Versions: 2.2 Reporter: Bruno Marti Priority: Minor Which is the roadmap/timeline for release 2.2? -- 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: (MCHANGES-152) page encoding ISO-8859-1 not definable
[ http://jira.codehaus.org/browse/MCHANGES-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196948#action_196948 ] Bruno Marti commented on MCHANGES-152: -- I changed site.xml and changes.xml to Problem has gone away. This issue can be closed > page encoding ISO-8859-1 not definable > -- > > Key: MCHANGES-152 > URL: http://jira.codehaus.org/browse/MCHANGES-152 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: changes-report >Affects Versions: 2.1 > Environment: Windows XP, Maven 2.09 >Reporter: Bruno Marti > Attachments: changes-report.zip, screenshot-1.jpg > > > Neither property > ISO-8859-1 > > nor ISO-8859-1 is > accepted for report generation (changes:changes-report). > German characters like 'äöü' are misinterpreted. -- 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
