[jira] Created: (MSITE-593) Correction in the french localization
Correction in the french localization - Key: MSITE-593 URL: https://jira.codehaus.org/browse/MSITE-593 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: localization Affects Versions: 2.3 Reporter: Guillaume Husta Priority: Trivial Attachments: site-plugin_fr.properties Here is a correction for the french localization of Maven Site Plugin. A new *site-plugin_fr.properties* is provided, according to [http://maven.apache.org/plugins/maven-site-plugin/i18n.html#Instructions_for_Translators]. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-689) prepare uses SNAPSHOT tag names
[ https://jira.codehaus.org/browse/MRELEASE-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272542#comment-272542 ] Guillaume Husta commented on MRELEASE-689: -- This bug seems to be related to : [MRELEASE-691|http://jira.codehaus.org/browse/MRELEASE-691] (_tagNameFormat property interpolation does not use the release values but the project ones_) > prepare uses SNAPSHOT tag names > --- > > Key: MRELEASE-689 > URL: https://jira.codehaus.org/browse/MRELEASE-689 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.2 > Environment: Ubuntu 11.04, Sun jdk 1.6.0_24 >Reporter: Michael Hartmeier >Priority: Critical > > Preparing a release with the latest 2.2 version of this plugin generates a > tag with the SNAPSHOT version of the project I want to prepare. > E.g. my project has is called sushi, and the current version is > 2.6.0-SNAPSHOT. When I prepare the release, I expect a tag "sushi-2.6.0", but > the tag I get ist sushi-2.6.0-SNAPSHOT. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-692) xxx-SNAPSHOT version tag created in Subversion when executing "release:prepare release:perform" in one call
[ https://jira.codehaus.org/browse/MRELEASE-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272878#comment-272878 ] Guillaume Husta commented on MRELEASE-692: -- This bug seems to be related to : [MRELEASE-691|http://jira.codehaus.org/browse/MRELEASE-691] (_tagNameFormat property interpolation does not use the release values but the project ones_) > xxx-SNAPSHOT version tag created in Subversion when executing > "release:prepare release:perform" in one call > > > Key: MRELEASE-692 > URL: https://jira.codehaus.org/browse/MRELEASE-692 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: scm >Affects Versions: 2.2 > Environment: Maven 2.2.1, Windows 7, Jenkins 1.411 >Reporter: Michael Hinterseher > > Tags created by Jenkins maven release plugin are no longer working correct > after upgrading the release plugin version from 2.1 to 2.2. > The created tag in subversion and the scm information now contains > "-SNAPSHOT". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-335) announcement-mail broken when NOT using the announcementFile parameter
Guillaume Husta created MCHANGES-335: Summary: announcement-mail broken when NOT using the announcementFile parameter Key: MCHANGES-335 URL: https://jira.codehaus.org/browse/MCHANGES-335 Project: Maven Changes Plugin Issue Type: Bug Components: announcement Affects Versions: 2.10 Reporter: Guillaume Husta When using a custom template to generate an announcement, the goal _announcement-mail_ will fail if : * I provide the parameters _template_ (other than announcement.vm) and _templateDirectory_ * and I don't provide the parameter _announcementFile_ Trace : bq. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-changes-plugin:2.10:announcement-mail (default-cli) on project test-changes-sendmail: Announcement file D:\Projets\Workspace_projets_java\test-changes-sendmail\target\announcement\announcement.vm not found... -> [Help 1] This is a *regression* : it worked with version 2.9 Related to MCHANGES-280 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEAR-185) Deprecated reference to 'defaultJavaBundleDir' in plugin documentation
Guillaume Husta created MEAR-185: Summary: Deprecated reference to 'defaultJavaBundleDir' in plugin documentation Key: MEAR-185 URL: https://jira.codehaus.org/browse/MEAR-185 Project: Maven Ear Plugin Issue Type: Task Affects Versions: 2.9 Reporter: Guillaume Husta Priority: Trivial The property 'defaultJavaBundleDir' has been replaced by 'defaultLibBundleDir' (for goal ear:ear). Page : * https://maven.apache.org/plugins/maven-ear-plugin/examples/skinny-wars.html -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-335) announcement-mail broken when NOT using the announcementFile parameter
[ https://jira.codehaus.org/browse/MCHANGES-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345919#comment-345919 ] Guillaume Husta edited comment on MCHANGES-335 at 5/7/14 10:11 AM: --- Comment for the zipped project : Just test with "mvn" or "mvn clean changes:annoucement-mail" was (Author: ghusta): Just test with "mvn" or "mvn clean changes:annoucement-mail" > announcement-mail broken when NOT using the announcementFile parameter > -- > > Key: MCHANGES-335 > URL: https://jira.codehaus.org/browse/MCHANGES-335 > Project: Maven Changes Plugin > Issue Type: Bug > Components: announcement >Affects Versions: 2.10 >Reporter: Guillaume Husta > Attachments: test-changes-335.zip > > > When using a custom template to generate an announcement, the goal > _announcement-mail_ will fail if : > * I provide the parameters _template_ (other than announcement.vm) and > _templateDirectory_ > * and I don't provide the parameter _announcementFile_ > Trace : > bq. [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-changes-plugin:2.10:announcement-mail > (default-cli) on project test-changes-sendmail: Announcement file > D:\Projets\Workspace_projets_java\test-changes-sendmail\target\announcement\announcement.vm > not found... -> [Help 1] > This is a *regression* : it worked with version 2.9 > Related to MCHANGES-280 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-335) announcement-mail broken when NOT using the announcementFile parameter
[
https://jira.codehaus.org/browse/MCHANGES-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345921#comment-345921
]
Guillaume Husta commented on MCHANGES-335:
--
OK thanks.
I did a little test project. (see attachments : test-changes-335.zip)
Here is an extract of the trace :
{quote}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-changes-plugin:2.10:announcement-mail
(default-cli) on project test-changes-335:
Announcement file
D:\Projets\Java\test-mchanges-335\target\announcement\announcement.vm not
found... -> [Help 1]
{quote}
I hope this will help you.
Regards
> announcement-mail broken when NOT using the announcementFile parameter
> --
>
> Key: MCHANGES-335
> URL: https://jira.codehaus.org/browse/MCHANGES-335
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: announcement
>Affects Versions: 2.10
>Reporter: Guillaume Husta
> Attachments: test-changes-335.zip
>
>
> When using a custom template to generate an announcement, the goal
> _announcement-mail_ will fail if :
> * I provide the parameters _template_ (other than announcement.vm) and
> _templateDirectory_
> * and I don't provide the parameter _announcementFile_
> Trace :
> bq. [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-changes-plugin:2.10:announcement-mail
> (default-cli) on project test-changes-sendmail: Announcement file
> D:\Projets\Workspace_projets_java\test-changes-sendmail\target\announcement\announcement.vm
> not found... -> [Help 1]
> This is a *regression* : it worked with version 2.9
> Related to MCHANGES-280
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGES-335) announcement-mail broken when NOT using the announcementFile parameter
[ https://jira.codehaus.org/browse/MCHANGES-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Husta updated MCHANGES-335: - Attachment: test-changes-335.zip Just test with "mvn" or "mvn clean changes:annoucement-mail" > announcement-mail broken when NOT using the announcementFile parameter > -- > > Key: MCHANGES-335 > URL: https://jira.codehaus.org/browse/MCHANGES-335 > Project: Maven Changes Plugin > Issue Type: Bug > Components: announcement >Affects Versions: 2.10 >Reporter: Guillaume Husta > Attachments: test-changes-335.zip > > > When using a custom template to generate an announcement, the goal > _announcement-mail_ will fail if : > * I provide the parameters _template_ (other than announcement.vm) and > _templateDirectory_ > * and I don't provide the parameter _announcementFile_ > Trace : > bq. [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-changes-plugin:2.10:announcement-mail > (default-cli) on project test-changes-sendmail: Announcement file > D:\Projets\Workspace_projets_java\test-changes-sendmail\target\announcement\announcement.vm > not found... -> [Help 1] > This is a *regression* : it worked with version 2.9 > Related to MCHANGES-280 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-335) announcement-mail broken when NOT using the announcementFile parameter
[
https://jira.codehaus.org/browse/MCHANGES-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346752#comment-346752
]
Guillaume Husta commented on MCHANGES-335:
--
OK thanks for your explanations.
So I've chosen the option #2, with adding something like that in my config :
{code:xml}
changes-${project.artifactId}.txt
{code}
> announcement-mail broken when NOT using the announcementFile parameter
> --
>
> Key: MCHANGES-335
> URL: https://jira.codehaus.org/browse/MCHANGES-335
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: announcement
>Affects Versions: 2.10
>Reporter: Guillaume Husta
> Attachments: test-changes-335.zip
>
>
> When using a custom template to generate an announcement, the goal
> _announcement-mail_ will fail if :
> * I provide the parameters _template_ (other than announcement.vm) and
> _templateDirectory_
> * and I don't provide the parameter _announcementFile_
> Trace :
> bq. [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-changes-plugin:2.10:announcement-mail
> (default-cli) on project test-changes-sendmail: Announcement file
> D:\Projets\Workspace_projets_java\test-changes-sendmail\target\announcement\announcement.vm
> not found... -> [Help 1]
> This is a *regression* : it worked with version 2.9
> Related to MCHANGES-280
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] Created: (MASSEMBLY-514) The value for prerequisites/maven in the pom.xml should be 2.2.1 for Maven Assembly Plugin 2.2
The value for prerequisites/maven in the pom.xml should be 2.2.1 for Maven
Assembly Plugin 2.2
--
Key: MASSEMBLY-514
URL: http://jira.codehaus.org/browse/MASSEMBLY-514
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2
Reporter: Guillaume Husta
Priority: Minor
The 2.2 version of the Assembly Plugin doesn't work with Maven 2.0.11.
The pom.xml indicates :
{code:xml}
2.0.11
1.1.2
2.2.1
true
{code}
When I invoke the 'single' goal (jar-with-dependencies) in the package phase of
a module, I get an error when working with Maven 2.0.11.
It seems to already have been fixed in the next version.
See :
[http://svn.apache.org/viewvc/maven/plugins/trunk/maven-assembly-plugin/pom.xml?r1=1021399&r2=1021398&pathrev=1021399]
--
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] (SCM-685) scm:diff doesn't work when using the 'endScmVersion' parameter
Guillaume Husta created SCM-685:
---
Summary: scm:diff doesn't work when using the 'endScmVersion'
parameter
Key: SCM-685
URL: https://jira.codehaus.org/browse/SCM-685
Project: Maven SCM
Issue Type: Bug
Components: maven-plugin
Affects Versions: 1.7
Reporter: Guillaume Husta
When using *scm:diff* with the parameters 'startScmVersion' and
'endScmVersion', both parameters get the value of 'startScmVersion'.
The *'endScmVersion' attribute* of the mojo seems to be erroneously assigned to
the 'startScmVersion' parameter.
Extract of the DiffMojo code :
{code:title=DiffMojo.java}
...
/**
* The version (revision number/branch name/tag name).
*
* @parameter expression="${startScmVersion}"
*/
private String endScmVersion;
...
{code}
--
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] (SCM-685) scm:diff doesn't work when using the 'endScmVersion' parameter
[
https://jira.codehaus.org/browse/SCM-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306039#comment-306039
]
Guillaume Husta commented on SCM-685:
-
Thank you for having fixed it so quickly !
> scm:diff doesn't work when using the 'endScmVersion' parameter
> --
>
> Key: SCM-685
> URL: https://jira.codehaus.org/browse/SCM-685
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-plugin
>Affects Versions: 1.7
>Reporter: Guillaume Husta
>Assignee: Robert Scholte
> Fix For: 1.8
>
>
> When using *scm:diff* with the parameters 'startScmVersion' and
> 'endScmVersion', both parameters get the value of 'startScmVersion'.
> The *'endScmVersion' attribute* of the mojo seems to be erroneously assigned
> to the 'startScmVersion' parameter.
> Extract of the DiffMojo code :
> {code:title=DiffMojo.java}
> ...
> /**
> * The version (revision number/branch name/tag name).
> *
> * @parameter expression="${startScmVersion}"
> */
> private String endScmVersion;
> ...
> {code}
--
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] (MPIR-257) English localization properties misplaced (i18n)
Guillaume Husta created MPIR-257:
Summary: English localization properties misplaced (i18n)
Key: MPIR-257
URL: https://jira.codehaus.org/browse/MPIR-257
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: dependency-info
Affects Versions: 2.6
Reporter: Guillaume Husta
Priority: Minor
These properties :
{code}
report.dependency-info.name = Dependency Information
report.dependency-info.title = Dependency Information
{code}
should be placed in *project-info-report.properties* rather than in
*project-info-report_en.properties*.
As mentioned in project-info-report_en.properties, "_This bundle is
intentionally empty because English strings are provided by the base bundle via
the parent chain._"
The problem is that when I generate the site with a french locale, it outputs
"_report.dependency-info.name_" or "_report.dependency-info.title_" rather than
"_Dependency Information_" (no french localization yet).
--
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] (MPIR-258) Missing english localization property for dependency-info (i18n)
Guillaume Husta created MPIR-258:
Summary: Missing english localization property for dependency-info
(i18n)
Key: MPIR-258
URL: https://jira.codehaus.org/browse/MPIR-258
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Improvement
Components: dependency-info
Affects Versions: 2.6
Reporter: Guillaume Husta
Priority: Minor
This property is missing :
{code}
report.dependency-info.description = This document provides information about
how to add this dependency with different dependency management tools.
{code}
and should be provided in the file *project-info-report.properties*.
It is evaluated when the file *target/site/project-info.html* is generated.
Warning, the description I wrote may need to be reviewed !
--
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] (MPIR-259) Add french localization for dependency-info
Guillaume Husta created MPIR-259:
Summary: Add french localization for dependency-info
Key: MPIR-259
URL: https://jira.codehaus.org/browse/MPIR-259
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Improvement
Components: dependency-info
Affects Versions: 2.6
Reporter: Guillaume Husta
Priority: Minor
Please add the french localization for these properties in
*project-info-report_fr.properties* :
{code}
report.dependency-info.name = Informations de d\u00e9pendance
report.dependency-info.title = Informations de d\u00e9pendance
report.dependency-info.description = Ce document fournit des informations sur
la mani\u00e8re d'ajouter cette d\u00e9pendance avec diff\u00e9rents outils de
gestion des d\u00e9pendances.
{code}
--
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] (MPIR-259) Add french localization for dependency-info
[
https://jira.codehaus.org/browse/MPIR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312842#comment-312842
]
Guillaume Husta commented on MPIR-259:
--
Parfait merci ;-)
> Add french localization for dependency-info
> ---
>
> Key: MPIR-259
> URL: https://jira.codehaus.org/browse/MPIR-259
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Components: dependency-info
>Affects Versions: 2.6
>Reporter: Guillaume Husta
>Assignee: Stéphane Nicoll
>Priority: Minor
> Fix For: 2.7
>
>
> Please add the french localization for these properties in
> *project-info-report_fr.properties* :
> {code}
> report.dependency-info.name = Informations de d\u00e9pendance
> report.dependency-info.title = Informations de d\u00e9pendance
> report.dependency-info.description = Ce document fournit des informations sur
> la mani\u00e8re d'ajouter cette d\u00e9pendance avec diff\u00e9rents outils
> de gestion des d\u00e9pendances.
> {code}
--
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] (MPIR-257) English localization properties misplaced (i18n)
[
https://jira.codehaus.org/browse/MPIR-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312843#comment-312843
]
Guillaume Husta commented on MPIR-257:
--
Very effective, thanks !
> English localization properties misplaced (i18n)
>
>
> Key: MPIR-257
> URL: https://jira.codehaus.org/browse/MPIR-257
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
>Affects Versions: 2.6
>Reporter: Guillaume Husta
>Assignee: Stéphane Nicoll
>Priority: Minor
> Fix For: 2.7
>
>
> These properties :
> {code}
> report.dependency-info.name = Dependency Information
> report.dependency-info.title = Dependency Information
> {code}
> should be placed in *project-info-report.properties* rather than in
> *project-info-report_en.properties*.
> As mentioned in project-info-report_en.properties, "_This bundle is
> intentionally empty because English strings are provided by the base bundle
> via the parent chain._"
> The problem is that when I generate the site with a french locale, it outputs
> "_report.dependency-info.name_" or "_report.dependency-info.title_" rather
> than "_Dependency Information_" (no french localization yet).
--
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] (MSHARED-273) Update documentation for the "Created-By" manifest entry
Guillaume Husta created MSHARED-273:
---
Summary: Update documentation for the "Created-By" manifest entry
Key: MSHARED-273
URL: https://jira.codehaus.org/browse/MSHARED-273
Project: Maven Shared Components
Issue Type: Improvement
Components: maven-archiver
Affects Versions: maven-archiver-2.5
Reporter: Guillaume Husta
Priority: Minor
The site documentation should be updated.
The default value for "Created-By" is now :
*Apache Maven $\{maven.version\}*
This affects the following pages, and maybe others :
* http://maven.apache.org/shared/maven-archiver/examples/manifest.html
* http://maven.apache.org/shared/maven-archiver/examples/manifestEntries.html
* http://maven.apache.org/shared/maven-archiver/examples/manifestSections.html
* http://maven.apache.org/shared/maven-archiver/examples/classpath.html
--
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] (MASSEMBLY-730) jar-with-dependencies : a file in a dependency is overridden by the same file in JDK / JRE
Guillaume Husta created MASSEMBLY-730:
-
Summary: jar-with-dependencies : a file in a dependency is
overridden by the same file in JDK / JRE
Key: MASSEMBLY-730
URL: https://jira.codehaus.org/browse/MASSEMBLY-730
Project: Maven Assembly Plugin
Issue Type: Bug
Components: predefined descriptors
Affects Versions: 2.5
Environment: JDK 6
Maven 3.0.4
Linux / Windows
Reporter: Guillaume Husta
Since version 2.5, when I try to make a "jar-with-dependencies" with the
"single" goal, I get a strange mistake.
A file in a dependency (a JDBC driver in my example) is overridden by a file
with the same path / name included in a dependency from the JDK / JRE (in my
example jre/lib/resources.jar).
In my example, I just add the dependency
_org.postgresql:postgresql:9.3-1102-jdbc4_ to my POM.
Then I package to make a "jar-with-dependencies".
I can find the file _META-INF/services/java.sql.Driver_ in this jar.
But with the version 2.5 of plugin assembly, it contains
* {{sun.jdbc.odbc.JdbcOdbcDriver}} (originated from JRE : resources.jar)
and with version 2.4.1 of the plugin, it contains
* {{org.postgresql.Driver}} (originated from postgresql-9.3-1102-jdbc4.jar),
what I expect
In the previous version (2.4.1) there was no problem.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-730) jar-with-dependencies : a file in a dependency is overridden by the same file in JDK / JRE
[
https://jira.codehaus.org/browse/MASSEMBLY-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355783#comment-355783
]
Guillaume Husta commented on MASSEMBLY-730:
---
I made a test case on GitHub.
You can see it here : https://github.com/ghusta/test-issue-massembly-730
> jar-with-dependencies : a file in a dependency is overridden by the same file
> in JDK / JRE
> --
>
> Key: MASSEMBLY-730
> URL: https://jira.codehaus.org/browse/MASSEMBLY-730
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: predefined descriptors
>Affects Versions: 2.5
> Environment: JDK 6
> Maven 3.0.4
> Linux / Windows
>Reporter: Guillaume Husta
>
> Since version 2.5, when I try to make a "jar-with-dependencies" with the
> "single" goal, I get a strange mistake.
> A file in a dependency (a JDBC driver in my example) is overridden by a file
> with the same path / name included in a dependency from the JDK / JRE (in my
> example jre/lib/resources.jar).
> In my example, I just add the dependency
> _org.postgresql:postgresql:9.3-1102-jdbc4_ to my POM.
> Then I package to make a "jar-with-dependencies".
> I can find the file _META-INF/services/java.sql.Driver_ in this jar.
> But with the version 2.5 of plugin assembly, it contains
> * {{sun.jdbc.odbc.JdbcOdbcDriver}} (originated from JRE : resources.jar)
> and with version 2.4.1 of the plugin, it contains
> * {{org.postgresql.Driver}} (originated from postgresql-9.3-1102-jdbc4.jar),
> what I expect
> In the previous version (2.4.1) there was no problem.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-730) jar-with-dependencies : a file in a dependency is overridden by the same file in JDK / JRE
[
https://jira.codehaus.org/browse/MASSEMBLY-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355807#comment-355807
]
Guillaume Husta commented on MASSEMBLY-730:
---
In fact it looks like this file is resolved by looking into the
SystemClassLoader first, whereas it should look into the dependencies
classloader only.
No other resources of jre/lib/resources.jar are included.
> jar-with-dependencies : a file in a dependency is overridden by the same file
> in JDK / JRE
> --
>
> Key: MASSEMBLY-730
> URL: https://jira.codehaus.org/browse/MASSEMBLY-730
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: predefined descriptors
>Affects Versions: 2.5
> Environment: JDK 6
> Maven 3.0.4
> Linux / Windows
>Reporter: Guillaume Husta
>
> Since version 2.5, when I try to make a "jar-with-dependencies" with the
> "single" goal, I get a strange mistake.
> A file in a dependency (a JDBC driver in my example) is overridden by a file
> with the same path / name included in a dependency from the JDK / JRE (in my
> example jre/lib/resources.jar).
> In my example, I just add the dependency
> _org.postgresql:postgresql:9.3-1102-jdbc4_ to my POM.
> Then I package to make a "jar-with-dependencies".
> I can find the file _META-INF/services/java.sql.Driver_ in this jar.
> But with the version 2.5 of plugin assembly, it contains
> * {{sun.jdbc.odbc.JdbcOdbcDriver}} (originated from JRE : resources.jar)
> and with version 2.4.1 of the plugin, it contains
> * {{org.postgresql.Driver}} (originated from postgresql-9.3-1102-jdbc4.jar),
> what I expect
> In the previous version (2.4.1) there was no problem.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-730) jar-with-dependencies : a file in a dependency is overridden by the same file in JDK / JRE
[
https://jira.codehaus.org/browse/MASSEMBLY-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Husta updated MASSEMBLY-730:
--
Affects Version/s: 2.5.1
> jar-with-dependencies : a file in a dependency is overridden by the same file
> in JDK / JRE
> --
>
> Key: MASSEMBLY-730
> URL: https://jira.codehaus.org/browse/MASSEMBLY-730
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: predefined descriptors
>Affects Versions: 2.5, 2.5.1
> Environment: JDK 6
> Maven 3.0.4
> Linux / Windows
>Reporter: Guillaume Husta
>
> Since version 2.5, when I try to make a "jar-with-dependencies" with the
> "single" goal, I get a strange mistake.
> A file in a dependency (a JDBC driver in my example) is overridden by a file
> with the same path / name included in a dependency from the JDK / JRE (in my
> example jre/lib/resources.jar).
> In my example, I just add the dependency
> _org.postgresql:postgresql:9.3-1102-jdbc4_ to my POM.
> Then I package to make a "jar-with-dependencies".
> I can find the file _META-INF/services/java.sql.Driver_ in this jar.
> But with the version 2.5 of plugin assembly, it contains
> * {{sun.jdbc.odbc.JdbcOdbcDriver}} (originated from JRE : resources.jar)
> and with version 2.4.1 of the plugin, it contains
> * {{org.postgresql.Driver}} (originated from postgresql-9.3-1102-jdbc4.jar),
> what I expect
> In the previous version (2.4.1) there was no problem.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-730) jar-with-dependencies : a file in a dependency is overridden by the same file in JDK / JRE
[
https://jira.codehaus.org/browse/MASSEMBLY-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355907#comment-355907
]
Guillaume Husta commented on MASSEMBLY-730:
---
OK thanks for the information.
My test also failed with Oracle JDK 7 u71 x64 for Windows.
But it succeeded with Oracle JDK 8 u25 x64 for Windows.
It think the reason is that JDK 7 contains
*jre/lib/resources.jar!META-INF/services/java.sql.Driver*
but JDK 8 doesn't anymore !
> jar-with-dependencies : a file in a dependency is overridden by the same file
> in JDK / JRE
> --
>
> Key: MASSEMBLY-730
> URL: https://jira.codehaus.org/browse/MASSEMBLY-730
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: predefined descriptors
>Affects Versions: 2.5, 2.5.1
> Environment: JDK 6
> Maven 3.0.4
> Linux / Windows
>Reporter: Guillaume Husta
> Fix For: 2.5.2
>
>
> Since version 2.5, when I try to make a "jar-with-dependencies" with the
> "single" goal, I get a strange mistake.
> A file in a dependency (a JDBC driver in my example) is overridden by a file
> with the same path / name included in a dependency from the JDK / JRE (in my
> example jre/lib/resources.jar).
> In my example, I just add the dependency
> _org.postgresql:postgresql:9.3-1102-jdbc4_ to my POM.
> Then I package to make a "jar-with-dependencies".
> I can find the file _META-INF/services/java.sql.Driver_ in this jar.
> But with the version 2.5 of plugin assembly, it contains
> * {{sun.jdbc.odbc.JdbcOdbcDriver}} (originated from JRE : resources.jar)
> and with version 2.4.1 of the plugin, it contains
> * {{org.postgresql.Driver}} (originated from postgresql-9.3-1102-jdbc4.jar),
> what I expect
> In the previous version (2.4.1) there was no problem.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-730) jar-with-dependencies : a file in a dependency is overridden by the same file in JDK / JRE
[
https://jira.codehaus.org/browse/MASSEMBLY-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356014#comment-356014
]
Guillaume Husta commented on MASSEMBLY-730:
---
Great work ! Wunderbar ;-)
Thanks
> jar-with-dependencies : a file in a dependency is overridden by the same file
> in JDK / JRE
> --
>
> Key: MASSEMBLY-730
> URL: https://jira.codehaus.org/browse/MASSEMBLY-730
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: predefined descriptors
>Affects Versions: 2.5, 2.5.1
> Environment: JDK 6
> Maven 3.0.4
> Linux / Windows
>Reporter: Guillaume Husta
>Assignee: Kristian Rosenvold
> Fix For: 2.5.2
>
>
> Since version 2.5, when I try to make a "jar-with-dependencies" with the
> "single" goal, I get a strange mistake.
> A file in a dependency (a JDBC driver in my example) is overridden by a file
> with the same path / name included in a dependency from the JDK / JRE (in my
> example jre/lib/resources.jar).
> In my example, I just add the dependency
> _org.postgresql:postgresql:9.3-1102-jdbc4_ to my POM.
> Then I package to make a "jar-with-dependencies".
> I can find the file _META-INF/services/java.sql.Driver_ in this jar.
> But with the version 2.5 of plugin assembly, it contains
> * {{sun.jdbc.odbc.JdbcOdbcDriver}} (originated from JRE : resources.jar)
> and with version 2.4.1 of the plugin, it contains
> * {{org.postgresql.Driver}} (originated from postgresql-9.3-1102-jdbc4.jar),
> what I expect
> In the previous version (2.4.1) there was no problem.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] Commented: (MECLIPSE-156) Plugin should support setting file encoding
[
http://jira.codehaus.org/browse/MECLIPSE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215481#action_215481
]
Guillaume Husta commented on MECLIPSE-156:
--
In the last version of MECLIPSE, this still does't work.
Apparently, the last patch by Jerome Lacoste has not been applied
(IdeUtils.java).
I've tested a little, and discovered some problems :
* the value for the property "project.build.sourceEncoding" is not taken into
account (see upper)
* the value for encoding isn't interpolated, so if you use for example
{code:xml}
${myencoding}
{code}
the string "${myencoding}" will be output instead of the interpolated value in
the settings
* the settings are written in the wrong file : _org.eclipse.jdt.core.prefs_
instead of _org.eclipse.core.resources.prefs_ (see
EclipseSettingsWriter.FILE_ECLIPSE_JDT_CORE_PREFS)
* if a new settings file has to be created by this Mojo, maybe should it be
also deleted in the *eclipse:clean* goal (see EclipseCleanMojo)
> Plugin should support setting file encoding
> ---
>
> Key: MECLIPSE-156
> URL: http://jira.codehaus.org/browse/MECLIPSE-156
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
>Reporter: Ralph Poellath
>Assignee: nicolas de loof
> Fix For: 2.8
>
> Attachments: maven-eclipse-plugin-2.5.1.tar.gz,
> MECLIPSE-156-maven-eclipse-plugin.patch,
> MECLIPSE-156_proper_use_of_project_build_sourceEncoding.patch
>
>
> The plugin should support setting Eclipse's text file encoding on a
> per-project basis.
--
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
