[jira] Created: (CONTINUUM-1097) Release start and end time are set to Jan 01, 1970 01:00:00 AM CET when a release error occurs before the actual release process
Release start and end time are set to Jan 01, 1970 01:00:00 AM CET when a release error occurs before the actual release process -- Key: CONTINUUM-1097 URL: http://jira.codehaus.org/browse/CONTINUUM-1097 Project: Continuum Issue Type: Bug Components: Core system Reporter: Edwin Punzalan Also, does not include the actual start time of the release process. -- 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: (CONTINUUM-1097) Release start and end time are set to Jan 01, 1970 01:00:00 AM CET when a release error occurs before the actual release process
[ http://jira.codehaus.org/browse/CONTINUUM-1097?page=all ] Edwin Punzalan updated CONTINUUM-1097: -- Attachment: CONTINUUM-1097-continuum-release.patch Patch attached... please apply, thanks. ^_^ Release start and end time are set to Jan 01, 1970 01:00:00 AM CET when a release error occurs before the actual release process -- Key: CONTINUUM-1097 URL: http://jira.codehaus.org/browse/CONTINUUM-1097 Project: Continuum Issue Type: Bug Components: Core system Reporter: Edwin Punzalan Attachments: CONTINUUM-1097-continuum-release.patch Also, does not include the actual start time of the release process. -- 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: (MANTRUN-63) ant classpath resolves incorrectly if project is invoked as part of multi-project builds
[ http://jira.codehaus.org/browse/MANTRUN-63?page=comments#action_83490 ]
Filippos Slavik commented on MANTRUN-63:
Well, I have the same problem and I finally have an explanation. The problem
occurs in a multi-module projects where the antrun plugin is being used in more
than one module.
In my case, let's say that my multi-module project has modules A and B. Both
modules are using the antrun plugin, but only module B specifies an additional
classpath for the antrun plugin. If I invoke the antrun plugin within module B
everything works great but if I do that from the parent, then my build fails.
This is because module A run it's build cycle before B and for some reason the
maven.plugin.classpath was not altered for the antrun plugin when running
module B build (perhaps because it was already defined from module A).
Thanks
ant classpath resolves incorrectly if project is invoked as part of
multi-project builds
Key: MANTRUN-63
URL: http://jira.codehaus.org/browse/MANTRUN-63
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Affects Versions: 1.1
Environment: maven-2.0.4, java 5, XP and linux
Reporter: Binyan
I have the following pom definition:
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasepackage/phase
configuration
tasks
property name=mpc refid=maven.plugin.classpath/
echoMPC: ${mpc}/echo
ant antfile=build.xml inheritRefs=true
target=build-installer/
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdant/groupId
artifactIdant-nodeps/artifactId
version1.6.5/version
/dependency
/dependencies
/plugin
with the output being:
[INFO] Executing tasks
[echo] MPC: C:\Documents and
Settings\binyan\.m2\repository\ant\ant-nodeps\1.6.5\ant-nodeps-1.6.5.jar;C:\Documents
and Settings\binyan\.m2\repository\ant\ant\1.6.5\ant-1.6.5.jar;C:\Documents
and
Settings\binyan\.m2\repository\ant\ant-launcher\1.6.5\ant-launcher-1.6.5.jar;E:\maven\lib\maven-project-2.0.4.jar;E:\maven\lib\maven-plugin-api-2.0.4.jar
... [ sucessful build performed] ...
Everything works fine if I build the project standalone, however, if the
project is part of a maven multi-project build and invoked by the top level
project then I get the following output:
[INFO] Executing tasks
[echo] MPC: C:\Documents and
Settings\binyan\.m2\repository\ant\ant\1.6.5\ant-1.6.5.jar;C:\Documents and
Settings\binyan\.m2\repository\ant\ant-launcher\1.6.5\ant-launcher-1.6.5.jar;E:\maven\lib\maven-project-2.0.4.jar;E:\maven\lib\maven-plugin-api-2.0.4.jar
init:
[mkdir] Created dir:
E:\dev\workspace-eclipse\MX\installs\target\installer-staging\mxscripts
[mkdir] Created dir:
E:\dev\workspace-eclipse\MX\installs\target\installer-staging\wars
build-staging:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: The following error occurred while executing this line:
E:\dev\workspace-eclipse\MX\installs\build.xml:23: Could not create type
regexpmapper due to No supported regular expression matcher found
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant
tasks
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
[jira] Commented: (MANTRUN-51) Can't find plugin dependency in multiproject
[ http://jira.codehaus.org/browse/MANTRUN-51?page=comments#action_83491 ]
Filippos Slavik commented on MANTRUN-51:
Well, I have the same problem and I finally have an explanation. The problem
occurs in a multi-module projects where the antrun plugin is being used in more
than one module.
In my case, let's say that my multi-module project has modules A and B. Both
modules are using the antrun plugin, but only module B specifies an additional
classpath for the antrun plugin. If I invoke the antrun plugin within module B
everything works great but if I do that from the parent, then my build fails.
This is because module A ran it's build cycle before B and for some reason the
maven.plugin.classpath was not altered for the antrun plugin when running
module B build (perhaps because it was already defined from module A).
Thanks
Can't find plugin dependency in multiproject
Key: MANTRUN-51
URL: http://jira.codehaus.org/browse/MANTRUN-51
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Affects Versions: 1.0, 1.1
Environment: maven 2.0.4, antrun 1.0 1.1, jdk 1.5.0_06, windows xp
Reporter: Fredrik Vraalsen
I'm using antrun in my project to create an IzPack installation. The plugin
configuration is below.
When maven is run from the top-level project, the ant taskdef fails because
it cannot find the IzPackTask class. However, when I run maven from the
subproject itself, it works fine. Not sure if this is related to
http://jira.codehaus.org/browse/MANTRUN-49. The error message from maven is
at the bottom.
{noformat}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasepackage/phase
configuration
tasks
taskdef name=izpack
classname=com.izforge.izpack.ant.IzPackTask/
izpack
input=${project.build.directory}/classes/izPack.xml
output=${project.build.directory}/CorasTool-${coras.version}-installer.jar
basedir=${project.build.directory}/
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdizpack/groupId
artifactIdstandalone-compiler/artifactId
version3.8.0/version
/dependency
/dependencies
/plugin
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: taskdef class com.izforge.izpack.ant.IzPackTask cannot be
found
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant
tasks
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error
[jira] Commented: (MWAR-60) Source Excludes are being applied to WAR file
[ http://jira.codehaus.org/browse/MWAR-60?page=comments#action_83493 ] Fabrice BELLINGARD commented on MWAR-60: Hi Stephane, (and merry Xmas ;-)) I should be working on this, but I currently doesn't have the time to do it. So if you want to go for it, feel free! BTW, on top of that source excludes/includes problem, it seemed to me that some parts of the plugin needed some refactoring (some methods were unused). But maybe it has been refactored meanwhile. Source Excludes are being applied to WAR file - Key: MWAR-60 URL: http://jira.codehaus.org/browse/MWAR-60 Project: Maven 2.x War Plugin Issue Type: Bug Affects Versions: 2.0.1 Environment: WinXP, jdk1.5.0_07, mvn 2.0.4 Reporter: Chuck Deal Assigned To: Fabrice BELLINGARD Fix For: 2.0.2 My scenario: I use Eclipse 3.1.1 to develop the web app. I run Tomcat 5.5.17 with it's docbase pointed at the source tree (/src/main/webapp). As a result, I have files that are required by Tomcat to run, but not to be included in the WAR. Specifically, I have a WEB-INF folder with a classes directory that includes classes that will actually be included in the WAR as a JAR (as well as a few other things). As you can see in the following plugin snippet, I specifically exclude the WEB-INF folder from the source tree because all of its contents will be gathered by the various stages of the build process (process-resources, etc) and included in the WAR when it is exploded I had been using the following plugin snippet for generating my War (war plugin 2.0) plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration webXmltarget/jspweb.xml/webXml warNameaims/warName excludes**/*.jsp*, **/JasperReports/*.*, **/WEB-INF/**/*.*/excludes /configuration /plugin If you change the version from 2.0 to 2.0.1, you will no longer generate the same WAR file! Instead, v2.0.1 uses the source excludes and applies them to the WAR construction as well. This means that the exploded WEB-INF (the correct one) is also removed from the WAR file. I don't think that the source excludes should be applied to the WAR construction, only to the stage where the source files are exploded (as in v2.0) -- 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: (MASSEMBLY-172) Extension-Name and Specification-Title added to MANIFEST.MF
Extension-Name and Specification-Title added to MANIFEST.MF --- Key: MASSEMBLY-172 URL: http://jira.codehaus.org/browse/MASSEMBLY-172 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Heinrich Nirschl Priority: Minor The assembly plugin (at least when using the predefined descriptor jar-with-dependencies; I did not check others) adds the Extension-Name and Specification-Title attributes to the generated jar. See also MJAR-38 which describes the same problem for the jar plugin. Here is the configuration I used: ... plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptorRefs descriptorRefjar-with-dependencies/descriptorRef /descriptorRefs archive manifest mainClass example.Main /mainClass /manifest /archive /configuration /plugin ... -- 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: (MPH-18) Plugin site out of date?
[ http://jira.codehaus.org/browse/MPH-18?page=all ] fabrizio giustina closed MPH-18. Assignee: fabrizio giustina Resolution: Fixed Fix Version/s: 2.1 The site speaks about a prefix parameter looks like it has already been fixed, published documentation is already corrected Plugin site out of date? Key: MPH-18 URL: http://jira.codehaus.org/browse/MPH-18 Project: Maven 2.x Help Plugin Issue Type: Improvement Affects Versions: 2.0.1 Reporter: Andrea Aime Assigned To: fabrizio giustina Fix For: 2.1 The site speaks about a prefix parameter here: http://maven.apache.org/plugins/maven-help-plugin/describe-mojo.html but it doesn't seem to work, whilst the following: mvn help:describe -Dplugin=help Does work fine (happily the eror message when using prefix gave me an hint on the right parameter name) -- 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: (MAVENUPLOAD-1290) Upload DbUnit 2.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1290?page=comments#action_83500 ] Felipe Leme commented on MAVENUPLOAD-1290: -- Oops, forgot to add a description: This is a long-awaited new DbUnit official release, generated more than 2 years after DbUnit 2.1! Hope everything is fine in the bundle - it should be, as it was generated with the Maven 2 plugin. Anyway, Happy New Year everybody Upload DbUnit 2.2 - Key: MAVENUPLOAD-1290 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1290 Project: maven-upload-requests Issue Type: Task Reporter: Felipe Leme -- 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: (MJAR-26) Need the ability to unsign a jar
[ http://jira.codehaus.org/browse/MJAR-26?page=comments#action_83520 ] Jerome Lacoste commented on MJAR-26: FYI, after an almost year stall, I finally commited the code in the webstart plugin. If you need to unsign jars, look at the unsign mojo inside that plugin. Need the ability to unsign a jar Key: MJAR-26 URL: http://jira.codehaus.org/browse/MJAR-26 Project: Maven 2.x Jar Plugin Issue Type: New Feature Reporter: Jerome Lacoste Priority: Critical There are some issues with doubly signed jars. We need a way to unsign those jars. I have some code in the webstart plugin (not yet committed to svn) that deals with that (patch came from Andrius Šabanas). But this is also something that once may want to do once and for all. I will wait for the code to stabilize and will submit it here when we have tested it sufficiently. -- 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: (MNG-2551) pom metadata file gets truncated during install into local repository
[ http://jira.codehaus.org/browse/MNG-2551?page=comments#action_83522 ] Des Lownds commented on MNG-2551: - I am getting the same results, with and without continuum, linux box, sun java version 1.5.0_10 Maven version: 2.0.4 using a file distribution management url pom metadata file gets truncated during install into local repository - Key: MNG-2551 URL: http://jira.codehaus.org/browse/MNG-2551 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories, Artifacts Affects Versions: 2.0.4 Environment: Win XP, JDK 1.4 Reporter: Sharmarke Aden Attachments: pom.xml, shared-1.9.0.pom When I attempt to install my project artifact to my local repository it seems that sometimes an incomplete/truncated .pom is deployed to my local repository. It's kind of weird because sometimes it happens and sometimes it doesn't. Any thoughts as to what could cause this? Attached is my pom.xml and the truncated pom meta data artifact deployed to my local repository. One thing I found that's odd is that the size of the truncated pom generated is consistently 4096 bytes. p.s. my pom.xml is UTF-8 encoded and uses Unix style line delimiters. -- 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: (MNG-2551) pom metadata file gets truncated during install into local repository
[ http://jira.codehaus.org/browse/MNG-2551?page=comments#action_83527 ] Des Lownds commented on MNG-2551: - I was able to work around the problem by using scp for distributionManagement repository urls pom metadata file gets truncated during install into local repository - Key: MNG-2551 URL: http://jira.codehaus.org/browse/MNG-2551 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories, Artifacts Affects Versions: 2.0.4 Environment: Win XP, JDK 1.4 Reporter: Sharmarke Aden Attachments: pom.xml, shared-1.9.0.pom When I attempt to install my project artifact to my local repository it seems that sometimes an incomplete/truncated .pom is deployed to my local repository. It's kind of weird because sometimes it happens and sometimes it doesn't. Any thoughts as to what could cause this? Attached is my pom.xml and the truncated pom meta data artifact deployed to my local repository. One thing I found that's odd is that the size of the truncated pom generated is consistently 4096 bytes. p.s. my pom.xml is UTF-8 encoded and uses Unix style line delimiters. -- 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: (DOXIA-83) Incorrect handling of images in menuitems
Incorrect handling of images in menuitems - Key: DOXIA-83 URL: http://jira.codehaus.org/browse/DOXIA-83 Project: doxia Issue Type: Bug Components: Site Renderer Reporter: Dennis Lundberg Attachments: siteRenderer.patch In the macro for menuItems I think there's an error when creating the src for images. Compare the handling of #set ( $currentItemHref ... and #set ( $src ... I'm not fluent enough in Velocity to sure though... -- 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: (MAVENUPLOAD-1292) Upload Canoo WebTest 1454
Upload Canoo WebTest 1454 - Key: MAVENUPLOAD-1292 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1292 Project: maven-upload-requests Issue Type: Task Reporter: Matt Raible Canoo WebTest is a spectacular tool for doing functional testing. -- 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: (MAVENUPLOAD-1293) Upload Hibernate EntityManager 3.2.1.ga
Upload Hibernate EntityManager 3.2.1.ga --- Key: MAVENUPLOAD-1293 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1293 Project: maven-upload-requests Issue Type: Task Reporter: Matt Raible Hibernate core and Hibernate annotations have 3.2.1.ga releases in the repo, but EntityManager is not in there. -- 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-203) bannerRight is not right aligned if no image is used
bannerRight is not right aligned if no image is used Key: MSITE-203 URL: http://jira.codehaus.org/browse/MSITE-203 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-5 Reporter: Wendy Smoak Priority: Minor Attachments: site-plugin-banner-right.jpg In site.xml, if bannerRight does not contain a src element with a URL, then the text or link produced from the name and href elements is not right aligned. To reproduce, generate a site module using the site archetype and make the following change to site.xml: @@ -6,7 +6,8 @@ hrefhttp://maven.apache.org//href /bannerLeft bannerRight -srchttp://maven.apache.org/images/maven-small.gif/src +nameMy Site/name +hrefhttp://maven.apache.org/href /bannerRight body links See attached image. The link with text My Site should be right aligned, but isn't. -- 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
