[jira] Created: (MPDF-49) Upgrade to Doxia 1.2
Upgrade to Doxia 1.2 Key: MPDF-49 URL: http://jira.codehaus.org/browse/MPDF-49 Project: Maven 2.x PDF Plugin Issue Type: Task Affects Versions: 1.1 Reporter: Lukas Theussl -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPDF-49) Upgrade to Doxia 1.2
[ http://jira.codehaus.org/browse/MPDF-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MPDF-49. - Resolution: Fixed Fix Version/s: 1.2 Assignee: Lukas Theussl Done in [r1102965|http://svn.apache.org/viewvc?rev=1102965&view=rev]. > Upgrade to Doxia 1.2 > > > Key: MPDF-49 > URL: http://jira.codehaus.org/browse/MPDF-49 > Project: Maven 2.x PDF Plugin > Issue Type: Task >Affects Versions: 1.1 >Reporter: Lukas Theussl >Assignee: Lukas Theussl > Fix For: 1.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] Closed: (MPDF-32) PDF generation fails due to velocity template error
[ http://jira.codehaus.org/browse/MPDF-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MPDF-32. - Resolution: Fixed Fix Version/s: 1.2 Assignee: Lukas Theussl Fixed with MPDF-49. > PDF generation fails due to velocity template error > --- > > Key: MPDF-32 > URL: http://jira.codehaus.org/browse/MPDF-32 > Project: Maven 2.x PDF Plugin > Issue Type: Bug >Affects Versions: 1.1 > Environment: Maven 2.0.10 JDK6, XP SP3 >Reporter: Michael Osipov >Assignee: Lukas Theussl > Fix For: 1.2 > > Attachments: pdf.log > > > I was trying to run mvn pdf:pdf and it suddenly failed. See attached log. The > failing template works flawlessly with the site goal. -- 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: (MEAR-139) earSourceDirectory named in documentation as earSourcesDirectory
[ http://jira.codehaus.org/browse/MEAR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEAR-139: - Fix Version/s: 2.6 > earSourceDirectory named in documentation as earSourcesDirectory > > > Key: MEAR-139 > URL: http://jira.codehaus.org/browse/MEAR-139 > Project: Maven 2.x Ear Plugin > Issue Type: Bug > Environment: http://maven.apache.org/plugins/maven-ear-plugin/ >Reporter: Alexey Tomin > Fix For: 2.6 > > > http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html > resourcesDirFile- Deprecated. please use > earSourcesDirectory instead in table and below) > http://maven.apache.org/plugins/maven-ear-plugin/examples/filtering-sources.html > Filtering the content of the src/main/application directory or the one > defined by the earSourcesDirectory parameter is as easy as > http://maven.apache.org/plugins/maven-ear-plugin/usage.html > The default resource directory for an EAR is src/main/application as > defined by the earSourcesDirectory parameter -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MEAR-139) earSourceDirectory named in documentation as earSourcesDirectory
[ http://jira.codehaus.org/browse/MEAR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEAR-139. Resolution: Fixed Thank you for the report Alexey. It has been fixed and the site will be updated for the next release. > earSourceDirectory named in documentation as earSourcesDirectory > > > Key: MEAR-139 > URL: http://jira.codehaus.org/browse/MEAR-139 > Project: Maven 2.x Ear Plugin > Issue Type: Bug > Environment: http://maven.apache.org/plugins/maven-ear-plugin/ >Reporter: Alexey Tomin >Assignee: Stephane Nicoll > Fix For: 2.6 > > > http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html > resourcesDirFile- Deprecated. please use > earSourcesDirectory instead in table and below) > http://maven.apache.org/plugins/maven-ear-plugin/examples/filtering-sources.html > Filtering the content of the src/main/application directory or the one > defined by the earSourcesDirectory parameter is as easy as > http://maven.apache.org/plugins/maven-ear-plugin/usage.html > The default resource directory for an EAR is src/main/application as > defined by the earSourcesDirectory parameter -- 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: (MJARSIGNER-15) ${jarsigner.arguments} expression does not work.
${jarsigner.arguments} expression does not work.
Key: MJARSIGNER-15
URL: http://jira.codehaus.org/browse/MJARSIGNER-15
Project: Maven 2.x Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.2
Reporter: Christian Schulte
Trying to set additional arguments using -Djarsigner.arguments fails with:
[INFO] Failed to configure plugin parameters for:
org.apache.maven.plugins:maven-jarsigner-plugin:1.2
on the command line, specify: '-Djarsigner.arguments=VALUE'
Cause: Cannot assign configuration entry 'arguments' to 'class
[Ljava.lang.String;' from '${jarsigner.arguments}', which is of type class
java.lang.String
--
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: (MJARSIGNER-15) ${jarsigner.arguments} expression does not work.
[
http://jira.codehaus.org/browse/MJARSIGNER-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MJARSIGNER-15:
Attachment: MJARSIGNER-15.patch
Patch adding a new 'args' parameter of type string for use with
-Djarsigner.arguments=VALUE.
> ${jarsigner.arguments} expression does not work.
>
>
> Key: MJARSIGNER-15
> URL: http://jira.codehaus.org/browse/MJARSIGNER-15
> Project: Maven 2.x Jar Signer Plugin
> Issue Type: Bug
>Affects Versions: 1.2
>Reporter: Christian Schulte
> Attachments: MJARSIGNER-15.patch
>
>
> Trying to set additional arguments using -Djarsigner.arguments fails with:
> [INFO] Failed to configure plugin parameters for:
> org.apache.maven.plugins:maven-jarsigner-plugin:1.2
> on the command line, specify: '-Djarsigner.arguments=VALUE'
> Cause: Cannot assign configuration entry 'arguments' to 'class
> [Ljava.lang.String;' from '${jarsigner.arguments}', which is of type class
> java.lang.String
--
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-243) Allow setting cc and bcc recipients when sending announcement mail
Allow setting cc and bcc recipients when sending announcement mail -- Key: MCHANGES-243 URL: http://jira.codehaus.org/browse/MCHANGES-243 Project: Maven 2.x Changes Plugin Issue Type: New Feature Components: announcement Affects Versions: 2.4 Reporter: Dennis Lundberg Currently only to recipients are allowed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCHANGES-243) Allow setting cc and bcc recipients when sending announcement mail
[ http://jira.codehaus.org/browse/MCHANGES-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-243. Resolution: Fixed Fix Version/s: 2.5 Assignee: Dennis Lundberg Fixed in [r1103215|http://svn.apache.org/viewvc?view=revision&revision=1103215]. > Allow setting cc and bcc recipients when sending announcement mail > -- > > Key: MCHANGES-243 > URL: http://jira.codehaus.org/browse/MCHANGES-243 > Project: Maven 2.x Changes Plugin > Issue Type: New Feature > Components: announcement >Affects Versions: 2.4 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.5 > > > Currently only to recipients are allowed. -- 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-210) Update to Java 5
[ http://jira.codehaus.org/browse/MCHANGES-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267004#action_267004 ] Dennis Lundberg commented on MCHANGES-210: -- I've added generics where it is possible. There are still a few places that hasn't been converted, but they cannot be converted until we can get Modello to generate Java 5 code for the changes model. Unfortunately we cannot upgrade to a later Modello Plugin at this time, so these will have to wait for now. See MCHANGES-150 for some reasons why we cannot upgrade. > Update to Java 5 > > > Key: MCHANGES-210 > URL: http://jira.codehaus.org/browse/MCHANGES-210 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.5 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCHANGES-210) Update to Java 5
[ http://jira.codehaus.org/browse/MCHANGES-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-210. Resolution: Fixed > Update to Java 5 > > > Key: MCHANGES-210 > URL: http://jira.codehaus.org/browse/MCHANGES-210 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.5 > > -- 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-115) Add title to type images
[ http://jira.codehaus.org/browse/MCHANGES-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267005#action_267005 ] Dennis Lundberg commented on MCHANGES-115: -- Anyone? > 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] Updated: (MCHANGES-233) Add option to skip announcement if there are no changes or changes.xml file is missing
[ http://jira.codehaus.org/browse/MCHANGES-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHANGES-233: - Component/s: changes.xml > Add option to skip announcement if there are no changes or changes.xml file > is missing > -- > > Key: MCHANGES-233 > URL: http://jira.codehaus.org/browse/MCHANGES-233 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: changes.xml >Affects Versions: 2.4 >Reporter: Ivan Khalopik > > It will be good to have some option to skip announcement generation if there > are no changes for artifact. Now if there are no changes build fails with > error: > No releases found in any of the configured issue management systems. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCHANGES-238) Add default issueLinkTemplatePerSystem for MKS Integrity issue tracking system
[
http://jira.codehaus.org/browse/MCHANGES-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCHANGES-238.
Resolution: Fixed
Fix Version/s: 2.5
Assignee: Dennis Lundberg
Fixed in [r1103219|http://svn.apache.org/viewvc?view=revision&revision=1103219].
> Add default issueLinkTemplatePerSystem for MKS Integrity issue tracking system
> --
>
> Key: MCHANGES-238
> URL: http://jira.codehaus.org/browse/MCHANGES-238
> Project: Maven 2.x Changes Plugin
> Issue Type: New Feature
> Components: other issue-trackers
>Affects Versions: 2.4
>Reporter: Jeremie BOUSQUET
>Assignee: Dennis Lundberg
>Priority: Minor
> Fix For: 2.5
>
>
> Add default template in issueLinkTemplatePerSystem for MKS Integrity ("mks").
> Pattern for MKS Integrity urls to an issue is as follows and works for me :
> %URL%/viewissue?selection=%ISSUE%
--
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-230) Add ability for changes-check to validate that the changes.xml release date is the day of the release
[ http://jira.codehaus.org/browse/MCHANGES-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHANGES-230: - Component/s: changes.xml > Add ability for changes-check to validate that the changes.xml release date > is the day of the release > - > > Key: MCHANGES-230 > URL: http://jira.codehaus.org/browse/MCHANGES-230 > Project: Maven 2.x Changes Plugin > Issue Type: New Feature > Components: changes.xml >Affects Versions: 2.4 >Reporter: Philip Maher > > I like the functionality included in the changes-check in MCHANGES-140. It > would be nice, in addition to checking the format of the date, if an option > could be added to have it check to see if the date of the release in the > changes.xml is the current date when the goal is run. I would like to be > able to have release:prepare or release:perform fail if the changes.xml did > not have the right day. This definitely should be an option that is off by > default. -- 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-199) changes:trac-report fails with [Fatal Error] :1:50: White spaces are required between publicId and systemId.
[ http://jira.codehaus.org/browse/MCHANGES-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267007#action_267007 ] Dennis Lundberg commented on MCHANGES-199: -- It sounds as if the xml header is not correct. Can someone attach a sample xml file downloaded through xmlrpc? > changes:trac-report fails with [Fatal Error] :1:50: White spaces are required > between publicId and systemId. > > > Key: MCHANGES-199 > URL: http://jira.codehaus.org/browse/MCHANGES-199 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: trac >Affects Versions: 2.3 > Environment: Server: > Trac 0.11.5 (with XML-RPC plugin 1.1.0) on Apache 2.2.12 > Client: > Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200) > Java version: 1.6.0_17 > Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home > Default locale: de_DE, platform encoding: MacRoman > OS name: "mac os x" version: "10.6.3" arch: "x86_64" Family: "mac" >Reporter: Alexander Papaspyrou > > The changes plugin fails on changes:trac-report invocation (and as part of > mvn site:site) with > [Fatal Error] :1:50: White spaces are required between publicId and > systemId. > and later (end of build) with > Embedded error: XmlRpc Error. > Failed to parse servers response: White spaces are required between > publicId and systemId. > The XML-RPC installation in Trac is working fine > (http://trac.localhost/trac//xmlrpc renders help pages; Eclipse > Mylyn able to access), and XML_RPC/TICKET_VIEW/REPORT_VIEW permissions are > granted to anonymous. > Ideas? -- 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-241) Failed to execute goal announcement-generate (include-announcement-file) on child project
[
http://jira.codehaus.org/browse/MCHANGES-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MCHANGES-241:
-
Description:
I have a child project which has a separate changes.xml which will be included
in a separate zip assembly.
When I run it on it's own, it works fine, but when I run it as part of a multi
module project I get the following error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-changes-plugin:2.4:announcement-generate
(include-announcement-file) on project : Resource not found.
Template not found. ( announcements/announcement.vm ) -> [Help 1]
{code:xml}
org.apache.maven.plugins
maven-changes-plugin
2.4
include-announcement-file
generate-resources
announcement-generate
announcement.vm
announcements
true
CHANGES.txt
${project.dist.directory}
{code}
As I said, the file
/src/main/resources/announcements/announcement.vm is
present and it works fine, when the project is run on its own.
I'm using Maven 3.0.3
was:
I have a child project which has a separate changes.xml which will be included
in a separate zip assembly.
When I run it on it's own, it works fine, but when I run it as part of a multi
module project I get the following error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-changes-plugin:2.4:announcement-generate
(include-announcement-file) on project : Resource not found.
Template not found. ( announcements/announcement.vm ) -> [Help 1]
org.apache.maven.plugins
maven-changes-plugin
2.4
include-announcement-file
generate-resources
announcement-generate
announcement.vm
announcements
true
CHANGES.txt
${project.dist.directory}
As I said, the file
/src/main/resources/announcements/announcement.vm is
present and it works fine, when the project is run on its own.
I'm using Maven 3.0.3
> Failed to execute goal announcement-generate (include-announcement-file) on
> child project
> -
>
> Key: MCHANGES-241
> URL: http://jira.codehaus.org/browse/MCHANGES-241
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: announcement
>Affects Versions: 2.4
>Reporter: Florian Brunner
>Priority: Blocker
>
> I have a child project which has a separate changes.xml which will be
> included in a separate zip assembly.
> When I run i
[jira] Updated: (MCHANGES-241) Failed to execute goal announcement-generate (include-announcement-file) on child project
[
http://jira.codehaus.org/browse/MCHANGES-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MCHANGES-241:
-
Description:
I have a child project which has a separate changes.xml which will be included
in a separate zip assembly.
When I run it on it's own, it works fine, but when I run it as part of a multi
module project I get the following error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-changes-plugin:2.4:announcement-generate
(include-announcement-file) on project : Resource not found.
Template not found. ( announcements/announcement.vm ) -> [Help 1]
{code:xml}
org.apache.maven.plugins
maven-changes-plugin
2.4
include-announcement-file
generate-resources
announcement-generate
announcement.vm
announcements
true
CHANGES.txt
${project.dist.directory}
{code}
As I said, the file
/src/main/resources/announcements/announcement.vm is
present and it works fine, when the project is run on its own.
I'm using Maven 3.0.3
was:
I have a child project which has a separate changes.xml which will be included
in a separate zip assembly.
When I run it on it's own, it works fine, but when I run it as part of a multi
module project I get the following error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-changes-plugin:2.4:announcement-generate
(include-announcement-file) on project : Resource not found.
Template not found. ( announcements/announcement.vm ) -> [Help 1]
{code:xml}
org.apache.maven.plugins
maven-changes-plugin
2.4
include-announcement-file
generate-resources
announcement-generate
announcement.vm
announcements
true
CHANGES.txt
${project.dist.directory}
{code}
As I said, the file
/src/main/resources/announcements/announcement.vm is
present and it works fine, when the project is run on its own.
I'm using Maven 3.0.3
> Failed to execute goal announcement-generate (include-announcement-file) on
> child project
> -
>
> Key: MCHANGES-241
> URL: http://jira.codehaus.org/browse/MCHANGES-241
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: announcement
>Affects Versions: 2.4
>Reporter: Florian Brunner
>Priority: Blocker
>
> I have a child project which has a separate changes.xml which will be
> included in a separate zip assembly.
> When I run it on it's own, it works fine, but when I run it as part of a
> multi module project I get the following error:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-changes-plugin:2.4:announcement-generate
> (include-announcement-file) on project : Resource not
> found. Template not found. ( announcements/announcement.vm ) -> [Help 1]
> {code:xml}
> org.apache.maven.plugins
> maven-changes-plugin
> 2.4
>
>
> include-announcement-file
> generate-resources
>
> announcement-generate
>
>
> announcement.vm
> announcements
> true
> CHANGES.txt
> ${project.dist.directory}
>
>
>
> {code}
> As I said, the file
> /src/main/resources/announcements/announcement.vm
> is present and it works fine, when the project is run on
[jira] Updated: (MCHANGES-155) When an empty element is present in changes.xml the parser fails
[
http://jira.codehaus.org/browse/MCHANGES-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MCHANGES-155:
-
Description:
With this changelog:
{code:xml}
Some changelog
Martin Vyný
Foo
{code}
mvn changes:announcement-generate fails with
[ERROR] An error occured when parsing the changes.xml file:
org.codehaus.plexus.util.xml.pull.XmlPullParserException: expected START_TAG or
END_TAG not TEXT (position: TEXT seen ...Foo(ChangesXML.java:65)
at
org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:322)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] Creating announcement file from
/home/vyzivus/work/lsabpm/lsabpm-1.206.x/src/changes/changes.xml...
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Couldn't find the release '1.206.6' among the supplied releases.
changes-2.0 does not suffer from this problem.
was:
With this changelog:
Some changelog
Martin Vyný
Foo
mvn changes:announcement-generate fails with
[ERROR] An error occured when parsing the changes.xml file:
org.codehaus.plexus.util.xml.pull.XmlPullParserException: expected START_TAG or
END_TAG not TEXT (position: TEXT seen ...Foo(ChangesXML.java:65)
at
org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:322)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] Creating announcement file from
/hom
[jira] Commented: (MCHANGES-241) Failed to execute goal announcement-generate (include-announcement-file) on child project
[
http://jira.codehaus.org/browse/MCHANGES-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267008#action_267008
]
Dennis Lundberg commented on MCHANGES-241:
--
Can you please put together a complete sample project that we can use to test
this?
> Failed to execute goal announcement-generate (include-announcement-file) on
> child project
> -
>
> Key: MCHANGES-241
> URL: http://jira.codehaus.org/browse/MCHANGES-241
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: announcement
>Affects Versions: 2.4
>Reporter: Florian Brunner
>Priority: Blocker
>
> I have a child project which has a separate changes.xml which will be
> included in a separate zip assembly.
> When I run it on it's own, it works fine, but when I run it as part of a
> multi module project I get the following error:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-changes-plugin:2.4:announcement-generate
> (include-announcement-file) on project : Resource not
> found. Template not found. ( announcements/announcement.vm ) -> [Help 1]
> {code:xml}
> org.apache.maven.plugins
> maven-changes-plugin
> 2.4
>
>
> include-announcement-file
> generate-resources
>
> announcement-generate
>
>
> announcement.vm
> announcements
> true
> CHANGES.txt
> ${project.dist.directory}
>
>
>
> {code}
> As I said, the file
> /src/main/resources/announcements/announcement.vm
> is present and it works fine, when the project is run on its own.
> I'm using Maven 3.0.3
--
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: (MJARSIGNER-16) Add the option -tsa to the configuration
Add the option -tsa to the configuration
Key: MJARSIGNER-16
URL: http://jira.codehaus.org/browse/MJARSIGNER-16
Project: Maven 2.x Jar Signer Plugin
Issue Type: New Feature
Affects Versions: 1.2
Environment: all
Reporter: Anthony Dahanne
Attachments: maven-jarsigner-plugin.patch
Since JDK 5, Sun/Oracle added to the JDK jarsigner tool, the possibility to use
a Timestamp authority while signing.
The option is docuemnted there :
http://download.oracle.com/javase/6/docs/technotes/tools/windows/jarsigner.html#Options
and for those interested in this feature (timestamping), some good explanation
about this technology can be found there :
http://en.wikipedia.org/wiki/Trusted_timestamping
I have attached a patch that includes the addition of this argument to the
command line; and a new integration test.
Applying this patch, you should be able to ask a timestamp authority to certify
the date of signing, using this configuration for example :
{code:xml}
org.apache.maven.plugins
maven-jarsigner-plugin
@project.version@
test-01
key-passwd
TESTING
https://timestamp.geotrust.com/tsa
sign-jars
sign
verify-jars
verify
{code}
you can find this code in the patch integration test (timestampauthority ,
src/it/timestampauthority)
Working on this patch, I THOUGHT there was a workaround, playing around with
the option :
{code:xml}
org.apache.maven.plugins
maven-jarsigner-plugin
@project.version@
test-01
key-passwd
TESTING
-tsa https://timestamp.geotrust.com/tsa
etc...
{code}
but it wraps this argument with quotes ("-tsa
https://timestamp.geotrust.com/tsa"; ) ; something the JDK jarsigner tool does
not accept; so... no workaround possible :-(
--
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-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
