[jira] Created: (MAVEN-1464) PDF Plugin Error on Table with Many Columns
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1464 Here is an overview of the issue: - Key: MAVEN-1464 Summary: PDF Plugin Error on Table with Many Columns Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Versions: 1.1 Assignee: Reporter: Jojo Paderes Created: Thu, 14 Oct 2004 2:38 AM Updated: Thu, 14 Oct 2004 2:38 AM Environment: Fedora Core 1 Linux, Java Runtime 1.4.2_05 Description: PDF Plugin failed to generate file while processing Xdoc XML data containing table with 19 columns. Here's the debug log while running PDF plugin: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 build:start: xdoc:init: [mkdir] Created dir: /home/jojo/projects/java/u2/u2_release_1_0_bug/target/generated-xdocs [mkdir] Created dir: /home/jojo/projects/java/u2/u2_release_1_0_bug/target/docs pdf:init: [echo] ### Debug mode is on ### == === xdoc plugin properties === == maven.docs.src = [/home/jojo/projects/java/u2/u2_release_1_0_bug/xdocs] maven.docs.dest = [/home/jojo/projects/java/u2/u2_release_1_0_bug/target/docs] maven.gen.docs = [/home/jojo/projects/java/u2/u2_release_1_0_bug/target/generated-xdocs] maven.xdoc.date.format = [dd ] maven.xdoc.date.locale = [en] == === pdf plugin properties === == maven.pdf.confidential = [false] maven.pdf.paperType = [A4] maven.pdf.companyIncName= [Company] maven.pdf.copyrightYear = [2003] maven.pdf.imageDpi = [72] maven.pdf.debug = [true] maven.pdf.navigationFile= [navigation.xml] maven.pdf.navigationFilePath= [/home/jojo/projects/java/u2/u2_release_1_0_bug/xdocs] maven.pdf.pdfName = [project.pdf] maven.pdf.cover.projectCompany = [Company] maven.pdf.cover.projectName = [Project] maven.pdf.cover.type= [Project Documentation] maven.pdf.cover.version = [1.0] maven.pdf.cover.date= [14 October 2004] maven.pdf.projectLogo = [] maven.pdf.companyLogo = [] == === pdf internal variables === == internal_pdf_workingDir = [/home/jojo/projects/java/u2/u2_release_1_0_bug/target/pdf] [mkdir] Created dir: /home/jojo/projects/java/u2/u2_release_1_0_bug/target/pdf pdf:prepare: [copy] Copying 3 files to /home/jojo/projects/java/u2/u2_release_1_0_bug/target/pdf [copy] Copying 7 files to /home/jojo/projects/java/u2/u2_release_1_0_bug/target/pdf fo:fo: [echo] Generating /home/jojo/projects/java/u2/u2_release_1_0_bug/target/docs/project.fo from /home/jojo/projects/java/u2/u2_release_1_0_bug/xdocs/navigation.xml ... [style] Processing /home/jojo/projects/java/u2/u2_release_1_0_bug/xdocs/navigation.xml to /home/jojo/projects/java/u2/u2_release_1_0_bug/target/pdf/project.fo [style] Loading stylesheet /home/jojo/.maven/cache/maven-pdf-plugin-2.2/plugin-resources/project2fo.xslt [style] home/jojo/.maven/cache/maven-pdf-plugin-2.2/plugin-resources/project2fo.xslt:153:46: Warning! Creating XSL:FO for /home/jojo/projects/java/u2/u2_release_1_0_bug/target/pdf/installation/configuration.xml [style] file:/home/jojo/.maven/cache/maven-pdf-plugin-2.2/plugin-resources/fo-table-column-widths.xslt:349:26: Warning! Cell (1,1) text()='CODE' rowspan=1 colspan=1 width=NaN [style] file:/home/jojo/.maven/cache/maven-pdf-plugin-2.2/plugin-resources/fo-table-column-widths.xslt:351:26: Warning! Current cell mask: --in 1-out [style] file:/home/jojo/.maven/cache/maven-pdf-plugin-2.2/plugin-resources/fo-table-column-widths.xslt:352:26: Warning! Next row mask: --in --out [style] file:/home/jojo/.maven/cache/maven-pdf-plugin-2.2/plugin-resources/fo-table-column-widths.xslt:353:26: Warning! Estimated cell widths: [style] file:/home/jojo/.maven/cache/maven-pdf-plugin-2.2/plugin-resources/fo-table-column-widths.xslt:355:26: Warning! Cell widths so far : 5? 5? 5? 5? 5? 5? 5? 5? 5? 5? [style] file:/home/jojo/.maven/cache/maven-pdf-plugin-2.2/plugin-resources/fo-table-column-widths.xslt:349:26: Warning! Cell (1,2) text()='M' rowspan=1 colspan=1 width=NaN [style] file:/home/jojo/.maven/cache/maven-pdf-plugin-2.2/plugin-resources/fo-table-column-widths.xslt:351:26: Warning! Current cell mask: 1-in 11out [style]
Re: [VOTE] Release of Dashoard plugin v1.5
+1. On Wed, 13 Oct 2004 12:02:07 +0200, Vincent Massol [EMAIL PROTECTED] wrote: Hi, I'd like to release the Dashboard plugin v1.5. The reason is simply that there are several changes already applied and I'd like to make a version available for end users. The other reason is that Nascif is preparing a big overhaul of the report format and I'd like to have something released before this happens. Here are the changes done since v1.4: http://maven.apache.org/reference/plugins/dashboard/changes-report.html Here's my +1 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1465) Incorrect transformation of xdoc xml file to HTML file
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1465 Here is an overview of the issue: - Key: MAVEN-1465 Summary: Incorrect transformation of xdoc xml file to HTML file Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Versions: 1.0 Assignee: Reporter: Atluri Satish Created: Thu, 14 Oct 2004 3:36 AM Updated: Thu, 14 Oct 2004 3:36 AM Environment: Windows XP, 1GB RAM,2 GHZ Processor, JDK 1.3.1 (IBM) Description: I am encountering a strange behavior, Maven 1.0 some times doesn't transform xdoc xml file to HTML. it just renames xdoc.xml to .Html extension with all xdoc tags. The subject document is a well formed XML, This behavior is isolated to only a document and when used with dist:build goal. However the HTML is rendered is corrected for xdoc goal --- Xdoc xml file -- ?xml version=1.0? document properties author email=[EMAIL PROTECTED]Atluri Satish/author titleTool Reference/title /properties meta name=keyword content=somebay java UnitTest Testing / body section name=Overview pThis document provides basic reference to the tools usage/p subsection pESTestHarness comprises of the following command line productivity tools to create test cases and test data/p table tr tdTool Name/td tdDescription/td /tr tr tdMavenDependencyCreator/td tdThis tool generates Maven Dependency tags for jars/zips in a specified folder/td /tr tr tdESResultsetXMLGenerator/td tdThis tool generates XML template for ESResultset using Command Object invocation/td /tr tr tdESObjectXMLGenerator/td tdThis tool generates XML template for ES Resultset or any other Java Object/td /tr tr tdCastor CodeGenerator/td tdThis tool generates Castor objects for a given XML Schema file/td /tr tr tdXML DTD Generator for Database Schema/td tdThis tool generates XML DTD for all the tables in a database schema/td /tr tr tdXML Data Generator for Database Schema/td tdThis tool generates XML Dataset files from given SQL Statement or Schema/td /tr tr tdJUNIT code generator/td tdThis tool generates JUNIT code from a XML file/td /tr /table /subsection subsection name=Maven Dependency Tag Creator pThis tool is creates XML Maven Dependency Tags for list of jars supplied. This tool can be used to create depedencies tags for existing projects and this generated XML dependency tags are specified in in maven project.xml file /p puser profile:Developer/User/p piusage/i/p source ![CDATA[ main class: com.somebay..es.testharness.util.MavenDependencyCreator usage: MavenDependencyCreator [-m] -v arg -g arg -f arg
[jira] Commented: (MPPDF-16) Maven PDF fails
The following comment has been added to this issue: Author: Archimedes Trajano Created: Thu, 14 Oct 2004 4:02 AM Body: I'm using JDK1.5 which might be causing the issue since org.apache.xalan.processor.TransformerFactoryImpl does not look like its available in 1.5. It seems to be using trax, but I am not 100% sure. - View this comment: http://jira.codehaus.org/browse/MPPDF-16?page=comments#action_25350 - View the issue: http://jira.codehaus.org/browse/MPPDF-16 Here is an overview of the issue: - Key: MPPDF-16 Summary: Maven PDF fails Type: Bug Status: Open Priority: Blocker Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-pdf-plugin Versions: 2.1 Assignee: Arnaud HERITIER Reporter: bflorat Created: Fri, 8 Oct 2004 3:36 PM Updated: Thu, 14 Oct 2004 4:02 AM Environment: Maven 1.0, Linux. Description: maven pdf __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 Plugin cache will be regenerated build:start: xdoc:init: pdf:init: pdf:prepare: [copy] Copying 14 files to /data/projects/jajuk/maven_rep/target/pdf fo:fo: [echo] Generating /data/projects/jajuk/maven_rep/target/docs/project.fo ... [style] Processing /data/projects/jajuk/maven_rep/xdocs/navigation.xml to /data/projects/jajuk/maven_rep/target/pdf/project.fo [style] Loading stylesheet /home/bflorat/.maven/cache/maven-pdf-plugin-2.1/plugin-resources/project2fo.xslt BUILD FAILED File.. /home/bflorat/.maven/cache/maven-pdf-plugin-2.1/plugin.jelly Element... style Line.. 70 Column 113 Provider org.apache.xalan.processor.TransformerFactoryImpl not found Total time: 14 seconds Finished at: Fri Oct 08 21:17:20 CEST 2004 - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven-plugins/dashboard project.xml
On 13 Oct 2004 20:00:10 -, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Modified:dashboard project.xml Log: Thomas is an excellent contributor but we don't need to add him twice... :-) Oh thanks, I thank I had to clone myself :-) -- Thomas Recloux - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPPDF-16) Maven PDF fails
The following issue has been updated: Updater: Archimedes Trajano (mailto:[EMAIL PROTECTED]) Date: Thu, 14 Oct 2004 5:20 AM Comment: This patch file provides the fix for the issue. It uses Jelly to perform the transformation rather than relying on ant:style. This does not require the hack that was from latka plugin anymore, but the Xalan XSLT processor is hardcoded (though the original one also had it hardcoded). I added my name contributors on the project.xml This has been tested on JDK 1.5 on Windows. Changes: Attachment changed to pdf.patch - For a full history of the issue, see: http://jira.codehaus.org/browse/MPPDF-16?page=history - View the issue: http://jira.codehaus.org/browse/MPPDF-16 Here is an overview of the issue: - Key: MPPDF-16 Summary: Maven PDF fails Type: Bug Status: Open Priority: Blocker Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-pdf-plugin Versions: 2.1 Assignee: Arnaud HERITIER Reporter: bflorat Created: Fri, 8 Oct 2004 3:36 PM Updated: Thu, 14 Oct 2004 5:20 AM Environment: Maven 1.0, Linux. Description: maven pdf __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 Plugin cache will be regenerated build:start: xdoc:init: pdf:init: pdf:prepare: [copy] Copying 14 files to /data/projects/jajuk/maven_rep/target/pdf fo:fo: [echo] Generating /data/projects/jajuk/maven_rep/target/docs/project.fo ... [style] Processing /data/projects/jajuk/maven_rep/xdocs/navigation.xml to /data/projects/jajuk/maven_rep/target/pdf/project.fo [style] Loading stylesheet /home/bflorat/.maven/cache/maven-pdf-plugin-2.1/plugin-resources/project2fo.xslt BUILD FAILED File.. /home/bflorat/.maven/cache/maven-pdf-plugin-2.1/plugin.jelly Element... style Line.. 70 Column 113 Provider org.apache.xalan.processor.TransformerFactoryImpl not found Total time: 14 seconds Finished at: Fri Oct 08 21:17:20 CEST 2004 - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1465) Incorrect transformation of xdoc xml file to HTML file
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Thu, 14 Oct 2004 5:48 AM Changes: Fix Version changed to 1.0.1 - For a full history of the issue, see: http://jira.codehaus.org/browse/MAVEN-1465?page=history - View the issue: http://jira.codehaus.org/browse/MAVEN-1465 Here is an overview of the issue: - Key: MAVEN-1465 Summary: Incorrect transformation of xdoc xml file to HTML file Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.0.1 Versions: 1.0 Assignee: Reporter: Atluri Satish Created: Thu, 14 Oct 2004 3:36 AM Updated: Thu, 14 Oct 2004 5:48 AM Environment: Windows XP, 1GB RAM,2 GHZ Processor, JDK 1.3.1 (IBM) Description: I am encountering a strange behavior, Maven 1.0 some times doesn't transform xdoc xml file to HTML. it just renames xdoc.xml to .Html extension with all xdoc tags. The subject document is a well formed XML, This behavior is isolated to only a document and when used with dist:build goal. However the HTML is rendered is corrected for xdoc goal --- Xdoc xml file -- ?xml version=1.0? document properties author email=[EMAIL PROTECTED]Atluri Satish/author titleTool Reference/title /properties meta name=keyword content=somebay java UnitTest Testing / body section name=Overview pThis document provides basic reference to the tools usage/p subsection pESTestHarness comprises of the following command line productivity tools to create test cases and test data/p table tr tdTool Name/td tdDescription/td /tr tr tdMavenDependencyCreator/td tdThis tool generates Maven Dependency tags for jars/zips in a specified folder/td /tr tr tdESResultsetXMLGenerator/td tdThis tool generates XML template for ESResultset using Command Object invocation/td /tr tr tdESObjectXMLGenerator/td tdThis tool generates XML template for ES Resultset or any other Java Object/td /tr tr tdCastor CodeGenerator/td tdThis tool generates Castor objects for a given XML Schema file/td /tr tr tdXML DTD Generator for Database Schema/td tdThis tool generates XML DTD for all the tables in a database schema/td /tr tr tdXML Data Generator for Database Schema/td tdThis tool generates XML Dataset files from given SQL Statement or Schema/td /tr tr tdJUNIT code generator/td tdThis tool generates JUNIT code from a XML file/td /tr /table /subsection subsection name=Maven Dependency Tag Creator pThis tool is creates XML Maven Dependency Tags for list of jars supplied. This tool can be used to create depedencies tags for existing projects and this generated XML dependency tags are specified in in maven project.xml
[jira] Created: (MPWAR-35) war.bundle's dependency need to war.bundle dependency's of dependency
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPWAR-35 Here is an overview of the issue: - Key: MPWAR-35 Summary: war.bundle's dependency need to war.bundle dependency's of dependency Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-war-plugin Versions: 1.7 Assignee: Reporter: Torsten Knodt Created: Thu, 14 Oct 2004 5:48 AM Updated: Thu, 14 Oct 2004 5:48 AM Description: When you declare a dependency to be war.bundle's, they often also have their dependencies which are also needed at runtime. These need to be war.bundle'd too. Else you have to include the dependencies of your dependencies which is really hard work, e.g. when depending on openejb. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPDF-16) Maven PDF fails
The following comment has been added to this issue: Author: Arnaud HERITIER Created: Thu, 14 Oct 2004 5:50 AM Body: Ok it works for me. Thanks Archimed. I'll apply it tonight. - View this comment: http://jira.codehaus.org/browse/MPPDF-16?page=comments#action_25358 - View the issue: http://jira.codehaus.org/browse/MPPDF-16 Here is an overview of the issue: - Key: MPPDF-16 Summary: Maven PDF fails Type: Bug Status: Open Priority: Blocker Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-pdf-plugin Versions: 2.1 Assignee: Arnaud HERITIER Reporter: bflorat Created: Fri, 8 Oct 2004 3:36 PM Updated: Thu, 14 Oct 2004 5:50 AM Environment: Maven 1.0, Linux. Description: maven pdf __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 Plugin cache will be regenerated build:start: xdoc:init: pdf:init: pdf:prepare: [copy] Copying 14 files to /data/projects/jajuk/maven_rep/target/pdf fo:fo: [echo] Generating /data/projects/jajuk/maven_rep/target/docs/project.fo ... [style] Processing /data/projects/jajuk/maven_rep/xdocs/navigation.xml to /data/projects/jajuk/maven_rep/target/pdf/project.fo [style] Loading stylesheet /home/bflorat/.maven/cache/maven-pdf-plugin-2.1/plugin-resources/project2fo.xslt BUILD FAILED File.. /home/bflorat/.maven/cache/maven-pdf-plugin-2.1/plugin.jelly Element... style Line.. 70 Column 113 Provider org.apache.xalan.processor.TransformerFactoryImpl not found Total time: 14 seconds Finished at: Fri Oct 08 21:17:20 CEST 2004 - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPNATIVE-8) Dependency fix
Message: The following issue has been closed. Resolver: Brett Porter Date: Thu, 14 Oct 2004 6:24 AM applied, thanks - View the issue: http://jira.codehaus.org/browse/MPNATIVE-8 Here is an overview of the issue: - Key: MPNATIVE-8 Summary: Dependency fix Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: 10 minutes Time Spent: Unknown Remaining: 10 minutes Project: maven-native-plugin Fix Fors: 1.2 Assignee: Reporter: Joachim Bader Created: Thu, 15 Jul 2004 2:35 AM Updated: Thu, 14 Oct 2004 6:24 AM Description: change dependency version: cpptasks to 1.0b3: for cross compile bcel to 5.1: other plugins use this version - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/native project.xml
brett 2004/10/14 03:28:20 Modified:native project.xml Log: PR: MPNATIVE-8 Submitted by: Joachim Bader update cpptasks dependency for cross compile Revision ChangesPath 1.21 +3 -3 maven-plugins/native/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/native/project.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- project.xml 25 Jun 2004 15:24:30 - 1.20 +++ project.xml 14 Oct 2004 10:28:20 - 1.21 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-native-plugin/id nameMaven Native Plug-in/name - currentVersion1.1/currentVersion + currentVersion1.2-SNAPSHOT/currentVersion descriptionPlugin for native compilation c,c++, fortran/description shortDescriptionNative plugin/shortDescription urlhttp://maven.apache.org/reference/plugins/native//url @@ -70,12 +70,12 @@ dependency groupIdant-contrib/groupId artifactIdcpptasks/artifactId - version20030309.134440/version + version1.0b3/version /dependency dependency groupIdbcel/groupId artifactIdbcel/artifactId - version5.0/version + version5.1/version /dependency /dependencies /project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPOM-4) pom:install should produce a temporary standalone POM to copy to repo
The following comment has been added to this issue:
Author: Felipe Leme
Created: Thu, 14 Oct 2004 7:46 AM
Body:
I was going to open a similar issue, as sometimes we have JEXL/EL expressions on the
POM that should be resolved before being the POM is deployed.
Take for instance the Cactus plugin:
dependency
groupIdcactus/groupId
artifactIdcactus/artifactId
version13-${pom.currentVersion}/version
/dependency
I could start the work on the pom:generate-standalone task, so it would resolve the
EL expressions, but I wouldn't be able to solve the XML issues (I don't know how to do
it and it would take to much time to figure it out).
-- Felipe
-
View this comment:
http://jira.codehaus.org/browse/MPPOM-4?page=comments#action_25361
-
View the issue:
http://jira.codehaus.org/browse/MPPOM-4
Here is an overview of the issue:
-
Key: MPPOM-4
Summary: pom:install should produce a temporary standalone POM to copy to repo
Type: Improvement
Status: Open
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-pom-plugin
Assignee: Jason van Zyl
Reporter: John Casey
Created: Fri, 23 Jul 2004 11:47 AM
Updated: Thu, 14 Oct 2004 7:46 AM
Description:
Currently, pom:install does a file copy to the local repo. This has multiple problems.
* Entities are not resolved, and entity imports are not copied.
* Extends path can be relative, which makes it nearly impossible to use the pom in a
meaningful way without also finding it's parent (usually the only way to resolve
../project.xml would be to do an scm checkout; but that info is in the pom that won't
parse).
I propose the following:
prior to the file copy inside pom:install and pom:deploy, there should be a
prereq=pom:generate-standalone which would literally take the Project instance in
memory and serialize it to a temporary project.xml (let's say target/project.xml or
something). The pom:install and pom:deploy goals would then copy *that file* to the
repo rather than the original project.xml file.
It would:
* Remove the extends element, because the Project instance is the result of any merges
* Remove the issue of discorporeal entities, since entity resolution would have
happened before parsing the project.xml at the beginning of pom:xxx
I think this is still logically valid, since any pom in the repo is considered an
artifact, and should be able to stand on it's own without complex interpretation. It
would also be easy to do with xstream or any other type of xml serialization...even
xpp3's XmlSerializer could do it, and the code to do so would be of minimal size.
-
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPEAR-24) Duplicated entries if maven.ear.src and maven.ear.resources are the same
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPEAR-24
Here is an overview of the issue:
-
Key: MPEAR-24
Summary: Duplicated entries if maven.ear.src and maven.ear.resources are the same
Type: Bug
Status: Open
Priority: Critical
Original Estimate: 1 hour
Time Spent: Unknown
Remaining: 1 hour
Project: maven-ear-plugin
Fix Fors:
1.6
Versions:
1.5
Assignee: Felipe Leme
Reporter: Felipe Leme
Created: Thu, 14 Oct 2004 9:33 AM
Updated: Thu, 14 Oct 2004 9:33 AM
Description:
The value of these 2 variables are different by default, but if the user change them
so they become equals, the entries on that directory will be added twice in the
generated ear.
That happens because we have 2 fileset entries in the Jelly script:
fileset dir=${maven.ear.resources} /
fileset dir=${maven.ear.src} casesensitive=false
excludes=**/META-INF/application.xml/
The solution is simple, it's just a matter of adding an j:if as shown below:
j:if test=${!pom.build.resources.isEmpty()}
mkdir dir=${maven.ear.resources}/
maven:copy-resources resources=${pom.build.resources}
todir=${maven.ear.resources}/
!-- if added below --
j:if test=${context.getVariable('maven.ear.resources') !=
context.getVariable('maven.ear.src')}
fileset dir=${maven.ear.resources} /
/j:if
/j:if
(and also, that block should come before the other fileset block)
I will fix it later (the most difficult part will be writing a test case :-)
-- Felipe
-
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPDASHBOARD-6) dashboard report not compatible with multiproject plugin
The following comment has been added to this issue:
Author: Thomas Recloux
Created: Thu, 14 Oct 2004 10:18 AM
Body:
Hi,
I'm trying to reproduce your project tree, I'd like to know if you got source code in
the mysubproject-one ?
For information, I'm using dashboard with this organisation :
--base project
|-- webapp ancestor
| |-- Web app one
| |-- Web app two
|-- business ancestor
| |-- business one
| |-- business two
|-- main project
With the main project using multiproject plugin to generate the site.
-
View this comment:
http://jira.codehaus.org/browse/MPDASHBOARD-6?page=comments#action_25364
-
View the issue:
http://jira.codehaus.org/browse/MPDASHBOARD-6
Here is an overview of the issue:
-
Key: MPDASHBOARD-6
Summary: dashboard report not compatible with multiproject plugin
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-dashboard-plugin
Assignee:
Reporter: Ryan Sonnek
Created: Thu, 20 May 2004 10:11 PM
Updated: Thu, 14 Oct 2004 10:18 AM
Environment: maven-1.0-rc3, WinXP
Description:
This is to reopen issue MPDASHBOARD-5. I've gone through the quick start guide, and
my subprojects are still re-executing the dashboard on other subprojects.
my project is structured as follows (notice the flattened directory structure)
/myproject-parent (parent project)
/mysubproject-one (extends ../myproject-parent/project.xml)
/mysubproject-two (extends ../myproject-parent/project.xml, depends on
mysubproject-one)
I have added the maven-dashboard-plugin to my parent project's project.xml and have
set the dashboard properties correctly. when i run maven:site from the parent
project, here's the execution path:
-myproject-parent (get's list of child projects)
mysubproject-one (dashboard-single is run)
mysubproject-one (get's list of child projects)
mysubproject-two (dashboard-single is run)
mysubproject-two (dashboard-single is run)
the parent project has the following dashboard settings (which are inherited by all
subprojects)
maven.dashboard.basedir=${maven.multiproject.basedir}
maven.dashboard.includes=${maven.multiproject.includes}
maven.dashboard.excludes=${maven.multiproject.excludes}
maven.dashboard.runreactor=false
maven.dashboard.rungoals=false
is there some way to run dashboard with a multiproject:site?
-
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JellySwt : problem running demo
Hi
I am interested to use jelly swt for our project.
http://compiere-mfgscm.sourceforge.net
I when I try to run jelly swt demo on Linux fedora 2 I get this :
I already sent this mail to common-users but may be it is better here ?
Any help welcome.
Thank's for any reply
Andre Legendre
{orion:rcs} maven demo
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0
build:start:
java:prepare-filesystem:
java:compile:
[echo] Compiling to
/home/rcs/Master/extern/java/jakarta/jakarta-commons/jelly/jelly-tags/swt/target/classes
java:jar-resources:
test:prepare-filesystem:
test:test-resources:
test:compile:
create-classpath:
demo:
[java] Exception in thread main java.lang.UnsatisfiedLinkError: no
swt-win32-2128 in java.library.path
[java] at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1491)
[java] at java.lang.Runtime.loadLibrary0(Runtime.java:788)
[java] at org.eclipse.swt.internal.win32.OS.clinit(OS.java:42)
[java] at
org.eclipse.swt.internal.win32.TCHAR.clinit(TCHAR.java:26)
[java] at org.eclipse.swt.widgets.Widget.clinit(Widget.java:79)
[java] at java.lang.Class.forName0(Native Method)
[java] at java.lang.Class.forName(Class.java:141)
[java] at
org.apache.commons.jelly.tags.swt.SwtTagLibrary.class$(SwtTagLibrary.java:84)
[java] at
org.apache.commons.jelly.tags.swt.SwtTagLibrary.init(SwtTagLibrary.java:94)
[java] at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[java] at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[java] at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[java] at
java.lang.reflect.Constructor.newInstance(Constructor.java:274)
[java] at java.lang.Class.newInstance0(Class.java:308)
[java] at java.lang.Class.newInstance(Class.java:261)
[java] at
org.apache.commons.jelly.JellyContext.getTagLibrary(JellyContext.java:454)
[java] at
org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java:979)
[java] at
org.apache.commons.jelly.parser.XMLParser.startElement(XMLParser.java:593)
[java] at
org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:446)
[java] at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:306)
[java] at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1568)
[java] at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:355)
[java] at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:539)
[java] at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:595)
[java] at
org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
[java] at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1125)
[java] at
org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:238)
[java] at
org.apache.commons.jelly.Jelly.compileScript(Jelly.java:125)
[java] at
org.apache.commons.jelly.util.CommandLineParser.invokeCommandLineJelly(CommandLineParser.java:98)
[java] at org.apache.commons.jelly.Jelly.main(Jelly.java:92)
[java] [ERROR] Java Result: 1
BUILD SUCCESSFUL
Total time: 5 seconds
Finished at: Thu Oct 14 11:30:44 EEST 2004
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/changelog/xdocs changes.xml
evenisse2004/10/14 08:01:44
Modified:changelog/src/main/org/apache/maven/perforcelib
PerforceChangeLogFactory.java
PerforceChangeLogParser.java
changelog/src/test/org/apache/maven/perforcelib
PerforceChangeLogParserTest.java
changelog/xdocs changes.xml
Log:
MPCHANGELOG-45. Perforce Repository URL should include project.
Revision ChangesPath
1.3 +11 -7
maven-plugins/changelog/src/main/org/apache/maven/perforcelib/PerforceChangeLogFactory.java
Index: PerforceChangeLogFactory.java
===
RCS file:
/home/cvs/maven-plugins/changelog/src/main/org/apache/maven/perforcelib/PerforceChangeLogFactory.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- PerforceChangeLogFactory.java 2 Mar 2004 15:00:18 - 1.2
+++ PerforceChangeLogFactory.java 14 Oct 2004 15:01:44 - 1.3
@@ -28,23 +28,27 @@
* It expects the repository connection element in the POM to be of
* this form: bcodescm:perforce[:P4PORT]:FILESPEC/code/b. If
* the P4PORT is omitted, the corresponding environment variable will
- * be used. The FILESPEC should use the appropriate Perforce
- * wildcards to represent all of the project's files. For example,
+ * be used. The FILESPEC should use depot syntax with the
+ * appropriate Perforce wildcards to represent all of the project's
+ * files, i.e. '...'
*
+ * The repository URL element should refer to a a
+ * href=http://www.perforce.com/perforce/products/p4web.html;p4web/a
+ * instance. The portion of the URL following the host:port should
+ * match the FILESPEC in the repository connection element, sans the
+ * '...'. It must end with a '/'.
+ *
+ * For example,
* pre
* lt;repositorygt;
* lt;connectiongt;
* scm:perforce:some.host.com:1666://depot/projects/maven/...
* lt;/connectiongt;
* lt;urlgt;
- * http://public.perforce.com:8080
+ * http://public.perforce.com:8080//depot/projects/maven/
* lt;/urlgt;
* lt;/repositorygt;
* /pre
- *
- * The repository url element should reference the root context of a a
- * href=http://www.perforce.com/perforce/products/p4web.html;p4web/a
- * instance.
*
* @author a href=mailto:[EMAIL PROTECTED]Jim Crossley/a
* @version $Id:
1.5 +7 -3
maven-plugins/changelog/src/main/org/apache/maven/perforcelib/PerforceChangeLogParser.java
Index: PerforceChangeLogParser.java
===
RCS file:
/home/cvs/maven-plugins/changelog/src/main/org/apache/maven/perforcelib/PerforceChangeLogParser.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- PerforceChangeLogParser.java 8 Jul 2004 08:36:51 - 1.4
+++ PerforceChangeLogParser.java 14 Oct 2004 15:01:44 - 1.5
@@ -91,6 +91,9 @@
/** the before date */
private Date beforeDate;
+/** The depot filespec will be stripped from each filename */
+private int prefixLength;
+
private static final String pattern =
^\\.\\.\\. #(\\d+) + // revision number
change (\\d+) .* + // changelist number
@@ -119,6 +122,9 @@
{
this.changeLog = changeLog;
setDateRange();
+String conn = changeLog.getRepositoryConnection();
+String filespec = conn.substring(conn.lastIndexOf(':')+1);
+this.prefixLength = 1 + filespec.lastIndexOf ('/');
}
/**
@@ -171,8 +177,6 @@
*/
private void addEntry(ChangeLogEntry entry, ChangeLogFile file)
{
-System.out.println();
-System.out.println(entry.toXML());
if (beforeDate != null) {
if (entry.getDate().before(beforeDate)) {
return;
@@ -197,7 +201,7 @@
private void processGetRevision(String line)
{
if (line.startsWith(FILE_BEGIN_TOKEN)) {
-currentFile = line;
+currentFile = line.substring (this.prefixLength);
return;
}
1.3 +9 -5
maven-plugins/changelog/src/test/org/apache/maven/perforcelib/PerforceChangeLogParserTest.java
Index: PerforceChangeLogParserTest.java
===
RCS file:
/home/cvs/maven-plugins/changelog/src/test/org/apache/maven/perforcelib/PerforceChangeLogParserTest.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- PerforceChangeLogParserTest.java 2 Mar 2004 15:00:19 - 1.2
+++ PerforceChangeLogParserTest.java 14 Oct 2004 15:01:44 - 1.3
@@ -23,6 +23,7 @@
import junit.framework.TestCase;
[jira] Closed: (MPCHANGELOG-45) Perforce Repository URL should include project
Message: The following issue has been closed. Resolver: Emmanuel Venisse Date: Thu, 14 Oct 2004 11:02 AM Applied. Thanks. - View the issue: http://jira.codehaus.org/browse/MPCHANGELOG-45 Here is an overview of the issue: - Key: MPCHANGELOG-45 Summary: Perforce Repository URL should include project Type: Improvement Status: Closed Priority: Minor Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-changelog-plugin Fix Fors: 1.8 Assignee: Reporter: Jim Crossley Created: Fri, 17 Sep 2004 8:47 PM Updated: Thu, 14 Oct 2004 11:02 AM Description: For the Perforce changelog factory, the repository URL element from the POM is too generic -- it doesn't link directly to the project's root. This also makes the file names in the file-activity report too verbose. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/eclipse/xdocs changes.xml
evenisse2004/10/14 08:24:51
Modified:eclipse/src/plugin-resources/templates classpath.jelly
eclipse/xdocs changes.xml
Log:
MPECLIPSE-47. Add resources directories and test resources directories to .classpath.
Revision ChangesPath
1.23 +28 -0
maven-plugins/eclipse/src/plugin-resources/templates/classpath.jelly
Index: classpath.jelly
===
RCS file:
/home/cvs/maven-plugins/eclipse/src/plugin-resources/templates/classpath.jelly,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- classpath.jelly 8 Oct 2004 15:46:48 - 1.22
+++ classpath.jelly 14 Oct 2004 15:24:51 - 1.23
@@ -54,6 +54,19 @@
/j:if
/j:forEach
classpathentry kind=src path=${srcDir} excluding=${excluding} /
+
+j:if test=${!pom.build.resources.isEmpty()}
+ j:forEach var=resource items=${pom.build.resources}
+j:new var=file className=java.io.File
+ j:arg value=${basedir}/
+/j:new
+j:invokeStatic var=resourceDirectory
className=org.apache.maven.MavenUtils method=makeRelativePath
+ j:arg value=${file}/
+ j:arg value=${resource.directory}/
+/j:invokeStatic
+classpathentry kind=src path=${resourceDirectory}/
+ /j:forEach
+/j:if
/j:if
!-- Add the list of additional directories for the classpath from
${maven.eclipse.classpath.include}--
@@ -108,6 +121,21 @@
j:if test=${depVersion != 'none'}
j:set var=ignoreJUnit value=true /
classpathentry kind=var
path=MAVEN_REPO/junit/jars/junit-${depVersion}.jar/
+/j:if
+
+j:if test=${pom.build.unitTest != null}
+ j:if test=${!pom.build.unitTest.resources.isEmpty()}
+j:forEach var=resource items=${pom.build.unitTest.resources}
+ j:new var=file className=java.io.File
+j:arg value=${basedir}/
+ /j:new
+ j:invokeStatic var=resourceDirectory
className=org.apache.maven.MavenUtils method=makeRelativePath
+j:arg value=${file}/
+j:arg value=${resource.directory}/
+ /j:invokeStatic
+ classpathentry kind=src path=${resourceDirectory}
output=${testOutputDir}/
+/j:forEach
+ /j:if
/j:if
/j:if
1.32 +1 -0 maven-plugins/eclipse/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/eclipse/xdocs/changes.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- changes.xml 8 Oct 2004 15:46:48 - 1.31
+++ changes.xml 14 Oct 2004 15:24:51 - 1.32
@@ -25,6 +25,7 @@
/properties
body
release version=1.9 date=in cvs
+ action dev=evenisse type=fix issue=MPECLIPSE-47Add resources
directories and test resources directories to .classpath./action
action dev=epugh type=fix issue=MPECLIPSE-46 due-to=Archimedes
TrajanoOverriden jar that resides outside maven repo doesn't get resolved
properly./action
action dev=epugh type=fix issue=MPECLIPSE-38Jar overrides are now
properly supported./action
/release
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPECLIPSE-47) Add resources directories and test resources directories to .classpath
Message: The following issue has been closed. Resolver: Emmanuel Venisse Date: Thu, 14 Oct 2004 11:37 AM Done. - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-47 Here is an overview of the issue: - Key: MPECLIPSE-47 Summary: Add resources directories and test resources directories to .classpath Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Fix Fors: 1.9 Versions: 1.9 Assignee: Reporter: Emmanuel Venisse Created: Tue, 12 Oct 2004 12:33 PM Updated: Thu, 14 Oct 2004 11:37 AM Description: - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1235) Performance problem with Maven reactor on Solaris
The following issue has been updated: Updater: Eric Lapierre (mailto:[EMAIL PROTECTED]) Date: Thu, 14 Oct 2004 12:25 PM Comment: This is an example that replicates our project structure, the dependencies between the projects, as well as 3rd party jar dependencies. This takes forever on Solaris 9. Changes: Attachment changed to with_3rd_party_dependencies.zip - For a full history of the issue, see: http://jira.codehaus.org/browse/MAVEN-1235?page=history - View the issue: http://jira.codehaus.org/browse/MAVEN-1235 Here is an overview of the issue: - Key: MAVEN-1235 Summary: Performance problem with Maven reactor on Solaris Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Versions: 1.0-beta-10 1.0-rc3 1.0-rc1 1.0-rc2 Assignee: Reporter: Vincent Massol Created: Wed, 14 Apr 2004 5:01 AM Updated: Thu, 14 Oct 2004 12:25 PM Description: Context: We have about 58 Maven projects. Each project has about 85 dependencies. About 50 of these are dependencies to external jars. The rest are inter-project dependencies. Problem: When running the Maven reactor on windows machine. The reactor correctly and relatively quickly (30-40 seconds) finds out the ordered list of projects to run. However, on Solaris, it takes about 215 minutes (almost 4 hours!) to find out the ordered list of projects. Analysis: It seems the problem is somewhere in the werkz code. When using a profiling tool, 100% of the time is spent in the Goal.addPrecusor method (which takes as an average about 1 minute per project per dependency to run). I don't see how the problem could be in werkz. But still the profiling tool points there. Could it be the checkForCycle which is somehow having recursivity problems on Solaris? Any idea? Thanks - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cvs commit: maven-plugins/eclipse/xdocs changes.xml
Thanks! I was just thinking of tackling this one!
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 14, 2004 4:25 PM
To: [EMAIL PROTECTED]
Subject: cvs commit: maven-plugins/eclipse/xdocs changes.xml
evenisse2004/10/14 08:24:51
Modified:eclipse/src/plugin-resources/templates classpath.jelly
eclipse/xdocs changes.xml
Log:
MPECLIPSE-47. Add resources directories and test resources
directories to .classpath.
Revision ChangesPath
1.23 +28 -0
maven-plugins/eclipse/src/plugin-resources/templates/classpath.jelly
Index: classpath.jelly
===
RCS file:
/home/cvs/maven-plugins/eclipse/src/plugin-resources/templates/cla
sspath.jelly,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- classpath.jelly 8 Oct 2004 15:46:48 - 1.22
+++ classpath.jelly 14 Oct 2004 15:24:51 - 1.23
@@ -54,6 +54,19 @@
/j:if
/j:forEach
classpathentry kind=src path=${srcDir}
excluding=${excluding} /
+
+j:if test=${!pom.build.resources.isEmpty()}
+ j:forEach var=resource items=${pom.build.resources}
+j:new var=file className=java.io.File
+ j:arg value=${basedir}/
+/j:new
+j:invokeStatic var=resourceDirectory
className=org.apache.maven.MavenUtils method=makeRelativePath
+ j:arg value=${file}/
+ j:arg value=${resource.directory}/
+/j:invokeStatic
+classpathentry kind=src path=${resourceDirectory}/
+ /j:forEach
+/j:if
/j:if
!-- Add the list of additional directories for the
classpath from ${maven.eclipse.classpath.include}--
@@ -108,6 +121,21 @@
j:if test=${depVersion != 'none'}
j:set var=ignoreJUnit value=true /
classpathentry kind=var
path=MAVEN_REPO/junit/jars/junit-${depVersion}.jar/
+/j:if
+
+j:if test=${pom.build.unitTest != null}
+ j:if test=${!pom.build.unitTest.resources.isEmpty()}
+j:forEach var=resource
items=${pom.build.unitTest.resources}
+ j:new var=file className=java.io.File
+j:arg value=${basedir}/
+ /j:new
+ j:invokeStatic var=resourceDirectory
className=org.apache.maven.MavenUtils method=makeRelativePath
+j:arg value=${file}/
+j:arg value=${resource.directory}/
+ /j:invokeStatic
+ classpathentry kind=src
path=${resourceDirectory} output=${testOutputDir}/
+/j:forEach
+ /j:if
/j:if
/j:if
1.32 +1 -0 maven-plugins/eclipse/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/eclipse/xdocs/changes.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- changes.xml 8 Oct 2004 15:46:48 - 1.31
+++ changes.xml 14 Oct 2004 15:24:51 - 1.32
@@ -25,6 +25,7 @@
/properties
body
release version=1.9 date=in cvs
+ action dev=evenisse type=fix
issue=MPECLIPSE-47Add resources directories and test resources
directories to .classpath./action
action dev=epugh type=fix issue=MPECLIPSE-46
due-to=Archimedes TrajanoOverriden jar that resides outside
maven repo doesn't get resolved properly./action
action dev=epugh type=fix issue=MPECLIPSE-38Jar
overrides are now properly supported./action
/release
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPGUMP-3) Place nag onto module not (just) project
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPGUMP-3 Here is an overview of the issue: - Key: MPGUMP-3 Summary: Place nag onto module not (just) project Type: Improvement Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-gump-plugin Assignee: Brett Porter Reporter: Adam Jack Created: Thu, 14 Oct 2004 12:51 PM Updated: Thu, 14 Oct 2004 12:51 PM Description: Would you mind moving the nag element out if projects and up onto the module? That way if we get a CVS|SVN error folks would be notified. If this isn't right (although I think a POM only has one project) then perhaps add something to the module, and also override (or duplicate) on the project, whatever is easier. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven snapshot does not compile
Hi
Problem to compile maven snapshot on a linux fedora 2 machine.
Snapshot comes from :
http://cvs.apache.org/snapshots/maven/maven_20041013104550.tar.gz
And I get this error :
Plugin 'maven-deploy-plugin' in project 'Maven' is not available
Any help welcome
Andre Legendre
Complete error log is :
{orion:rcs} maven
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0
Attempting to download maven-jelly-tags-1.1-SNAPSHOT.jar.
Attempting to download maven-model-1.1-SNAPSHOT.jar.
Plugin 'maven-deploy-plugin' in project 'Maven' is not available
build:start:
java:prepare-filesystem:
java:compile:
[echo] Compiling to
/home/rcs/Master/extern/java/jakarta/maven/target/classes
[javac] Compiling 65 source files to
/home/rcs/Master/extern/java/jakarta/maven/target/classes
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:38:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.Credentials;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:39:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.Header;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:40:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.HostConfiguration;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:41:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.HttpClient;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:42:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.HttpRecoverableException;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:43:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.NTCredentials;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:44:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.UsernamePasswordCredentials;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:45:
package org.apache.commons.httpclient.methods does not exist
import org.apache.commons.httpclient.methods.GetMethod;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:46:
package org.apache.commons.httpclient.util does not exist
import org.apache.commons.httpclient.util.DateParser;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:47:
package org.apache.commons.httpclient.util does not exist
import org.apache.commons.httpclient.util.DateParseException;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:438:
cannot resolve symbol
symbol : class HttpClient
location: class org.apache.maven.util.HttpUtils
private static String retrieveArtifact(HttpClient client, URL
source, File destinationFile, long timestamp, DownloadMeter
downloadMeter ) throws FileNotFoundException, IOException,
HttpRecoverableException {
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:438:
cannot resolve symbol
symbol : class HttpRecoverableException
location: class org.apache.maven.util.HttpUtils
private static String retrieveArtifact(HttpClient client, URL
source, File destinationFile, long timestamp, DownloadMeter
downloadMeter ) throws FileNotFoundException, IOException,
HttpRecoverableException {
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:346:
cannot resolve symbol
symbol : class Credentials
location: class org.apache.maven.util.HttpUtils
Credentials creds = null;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:348:
cannot resolve symbol
symbol : class NTCredentials
location: class org.apache.maven.util.HttpUtils
creds = new NTCredentials(proxyUserName, proxyPassword,
loginHost, loginDomain);
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:351:
cannot resolve symbol
symbol : class UsernamePasswordCredentials
location: class org.apache.maven.util.HttpUtils
[jira] Commented: (MPWAR-33) Plugin generates multiple Class-Path entries in the manifest file
The following comment has been added to this issue:
Author: Felipe Leme
Created: Thu, 14 Oct 2004 2:10 PM
Body:
Joran,
Could you please write a simple test-case for this issue (i.e., a simple project.xml
whose consecutive calls to maven war:war generates the invalid war)? I've tried to
reproduce it, but the error didn't happens...
Anyway, I think the fix is essy, it's just a matter of removing the 'update=true'
attribute from ant:jar:
ant:jar
destfile=${maven.war.build.dir}/${maven.war.final.name}
basedir=${maven.war.webapp.dir}
update=true
index=${maven.war.index}
-- Felipe
-
View this comment:
http://jira.codehaus.org/browse/MPWAR-33?page=comments#action_25375
-
View the issue:
http://jira.codehaus.org/browse/MPWAR-33
Here is an overview of the issue:
-
Key: MPWAR-33
Summary: Plugin generates multiple Class-Path entries in the manifest file
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-war-plugin
Versions:
1.6
Assignee: Felipe Leme
Reporter: Jöran Stark
Created: Wed, 22 Sep 2004 1:38 PM
Updated: Thu, 14 Oct 2004 2:10 PM
Description:
Hi,
Running war:war (maven-war-plugin-1.6) the first time generates a manifest file with a
single Class-Path entry (correctly including the
dependencies), but running war:war a second time (with no clean-up done) generates
multiple Class-Path entries.
This problem does not occure when building the EJB's (maven-ejb-plugin-1.4). When I
compared theese two I noticed that the war-plugin does an update while the ejb-plugin
does not. By removing the update attribute the war-plugin works fine, for me anyway ;-)
I have the same problem with 1.7-SNAPSHOT from CVS-HEAD.
Since my project includes other developers and users I would like to avoid making
(local) changes in the plugin. Currently the solution is to do a clean-up in the
pre-goal to war:war.
Cheers
Joran
[manifest after first run]
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.5.3
Created-By: 1.4.2_05-b04 (Sun Microsystems Inc.)
Class-Path: jakarta-oro-jena-2.0.jar icu4j.jar antlr.jar
Built-By: Joran
Name: foo.bar
Specification-Title: foo-web
Specification-Version: 1.0
Specification-Vendor: Apache Software Foundation
Implementation-Title: foo.bar
Implementation-Version: 1.0
Implementation-Vendor: Apache Software Foundation
[manifest after second run]
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.5.3
Created-By: 1.4.2_05-b04 (Sun Microsystems Inc.)
Class-Path: jakarta-oro-jena-2.0.jar icu4j.jar antlr.jar
Class-Path: jakarta-oro-jena-2.0.jar icu4j.jar antlr.jar
Class-Path: jakarta-oro-jena-2.0.jar icu4j.jar antlr.jar
Built-By: Joran
Name: foo.bar
Specification-Title: foo-web
Specification-Version: 1.0
Specification-Vendor: Apache Software Foundation
Implementation-Title: foo.bar
Implementation-Version: 1.0
Implementation-Vendor: Apache Software Foundation
[a snippet from project.xml]
dependency
groupIdjena/groupId
artifactIdicu4j/artifactId
jaricu4j.jar/jar
properties
war.manifest.classpathtrue/war.manifest.classpath
/properties
/dependency
-
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPWAR-2) Include dependency as manifest-classpath
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MPWAR-2 Here is an overview of the issue: - Key: MPWAR-2 Summary: Include dependency as manifest-classpath Type: Improvement Status: Closed Priority: Minor Resolution: DUPLICATE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-war-plugin Fix Fors: 1.6 Assignee: Reporter: Anders Engstr?m Created: Sat, 20 Sep 2003 5:52 AM Updated: Thu, 14 Oct 2004 2:16 PM Description: One nice feature for the war plugin would be to make it possible to specify that a dependency should be included in the manifest classpath of the war. Is is this something that is considered? The jelly-code is in the ejb-plugin, so I suppose it would be pretty easy to implement (I'd be happy to write a patch). The reason is that when you have an ejb module and one or many web-modules in a J2EE-project (as we have) you often have common dependencies between these modules. Let's say you need commons-logging in all modules then you'd probably want to include commons-logging-x.x.x.jar in the EAR-file, and reference it from all other modules as manifest classpath entries. In the project.xml of a webapplication you would thus have: !-- This is a dependency shared by many modules -- dependency groupIdcommons-logging/groupId artifactIdcommons-logging/groupId version1.0.3/version properties war.manifest.classpathtrue/war.manifest.classpath /properties /dependency !-- This is a webapp dependency only -- dependency groupIdwebwork/groupId artifactIdwebwork/artifactId version1.3/version properties war.bundletrue/war.bundle /properties /dependency - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPPDF-16) Maven PDF fails
The following issue has been updated: Updater: Arnaud HERITIER (mailto:[EMAIL PROTECTED]) Date: Thu, 14 Oct 2004 3:09 PM Changes: Version changed to 2.2 Version changed to 2.0 Fix Version changed to 2.3 - For a full history of the issue, see: http://jira.codehaus.org/browse/MPPDF-16?page=history - View the issue: http://jira.codehaus.org/browse/MPPDF-16 Here is an overview of the issue: - Key: MPPDF-16 Summary: Maven PDF fails Type: Bug Status: Open Priority: Blocker Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-pdf-plugin Fix Fors: 2.3 Versions: 2.0 2.1 2.2 Assignee: Arnaud HERITIER Reporter: bflorat Created: Fri, 8 Oct 2004 3:36 PM Updated: Thu, 14 Oct 2004 3:09 PM Environment: Maven 1.0, Linux. Description: maven pdf __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 Plugin cache will be regenerated build:start: xdoc:init: pdf:init: pdf:prepare: [copy] Copying 14 files to /data/projects/jajuk/maven_rep/target/pdf fo:fo: [echo] Generating /data/projects/jajuk/maven_rep/target/docs/project.fo ... [style] Processing /data/projects/jajuk/maven_rep/xdocs/navigation.xml to /data/projects/jajuk/maven_rep/target/pdf/project.fo [style] Loading stylesheet /home/bflorat/.maven/cache/maven-pdf-plugin-2.1/plugin-resources/project2fo.xslt BUILD FAILED File.. /home/bflorat/.maven/cache/maven-pdf-plugin-2.1/plugin.jelly Element... style Line.. 70 Column 113 Provider org.apache.xalan.processor.TransformerFactoryImpl not found Total time: 14 seconds Finished at: Fri Oct 08 21:17:20 CEST 2004 - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPECLIPSE-49) duplicate build path added if resouce directory is the same as java source dir
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-49 Here is an overview of the issue: - Key: MPECLIPSE-49 Summary: duplicate build path added if resouce directory is the same as java source dir Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Versions: 1.9 Assignee: Reporter: fabrizio giustina Created: Thu, 14 Oct 2004 3:35 PM Updated: Thu, 14 Oct 2004 3:35 PM Description: This is a problem in MPECLIPSE-47, committed a few hours ago: if your pom declares the same directory both in sourceDirectory and in resources (common for .properties files) build sourceDirectorysrc/java/sourceDirectory resources resource directorysrc/java/directory includes include**/*.properties/include /includes filteringfalse/filtering /resource /resources /build the resulting .classpath file has duplicate entries and eclipse complains about it. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPPDF-16) Maven PDF fails
Message: The following issue has been closed. Resolver: Arnaud HERITIER Date: Thu, 14 Oct 2004 4:04 PM Thanks Archimedes. A snapshot is available here : http://cvs.apache.org/repository/maven/plugins/ - View the issue: http://jira.codehaus.org/browse/MPPDF-16 Here is an overview of the issue: - Key: MPPDF-16 Summary: Maven PDF fails Type: Bug Status: Closed Priority: Blocker Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-pdf-plugin Fix Fors: 2.3 Versions: 2.0 2.1 2.2 Assignee: Arnaud HERITIER Reporter: bflorat Created: Fri, 8 Oct 2004 3:36 PM Updated: Thu, 14 Oct 2004 4:04 PM Environment: Maven 1.0, Linux. Description: maven pdf __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 Plugin cache will be regenerated build:start: xdoc:init: pdf:init: pdf:prepare: [copy] Copying 14 files to /data/projects/jajuk/maven_rep/target/pdf fo:fo: [echo] Generating /data/projects/jajuk/maven_rep/target/docs/project.fo ... [style] Processing /data/projects/jajuk/maven_rep/xdocs/navigation.xml to /data/projects/jajuk/maven_rep/target/pdf/project.fo [style] Loading stylesheet /home/bflorat/.maven/cache/maven-pdf-plugin-2.1/plugin-resources/project2fo.xslt BUILD FAILED File.. /home/bflorat/.maven/cache/maven-pdf-plugin-2.1/plugin.jelly Element... style Line.. 70 Column 113 Provider org.apache.xalan.processor.TransformerFactoryImpl not found Total time: 14 seconds Finished at: Fri Oct 08 21:17:20 CEST 2004 - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/pdf/xdocs changes.xml
aheritier2004/10/14 13:05:21
Modified:pdf plugin.jelly project.xml
pdf/xdocs changes.xml
Log:
MPPDF-16 : JDK 5.0 incompatibility. XSLT is now called from Jelly.
Revision ChangesPath
1.22 +92 -25maven-plugins/pdf/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/pdf/plugin.jelly,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- plugin.jelly 22 Sep 2004 21:39:30 - 1.21
+++ plugin.jelly 14 Oct 2004 20:05:21 - 1.22
@@ -115,34 +115,101 @@
prereqs=pdf:prepare
description=Generates an fo xml document from the ${maven.pdf.navigationFile}
file supplied as part of the documentation.
-echoGenerating ${maven.xdoc.dest}/project.fo from
${maven.pdf.navigationFilePath}/${maven.pdf.navigationFile} .../echo
+echoGenerating ${internal_pdf_workingDir}/project.fo from
${maven.pdf.navigationFilePath}/${maven.pdf.navigationFile} .../echo
available file=${maven.pdf.navigationFilePath}/${maven.pdf.navigationFile}
property=maven.fo.navigation.available/
fail
message=PDF generation cannot complete as
${maven.pdf.navigationFilePath}/${maven.pdf.navigationFile} is missing
unless=maven.fo.navigation.available/
-!-- 'Major hack.' Stolen from the Latka plugin.jelly. All of this could be
avoided by putting
- xalan into $MAVEN_HOME/lib/endorsed directory in the distribution, but never
mind --
-
${systemScope.setProperty('javax.xml.transform.TransformerFactory','org.apache.xalan.processor.TransformerFactoryImpl')}
-style
- in=${maven.pdf.navigationFilePath}/${maven.pdf.navigationFile}
- out=${internal_pdf_workingDir}/project.fo
- style=${plugin.resources}/project2fo.xslt
- force=true
- param name=basePath expression=${internal_pdf_workingDir}/
- param name=confidential expression=${maven.pdf.confidential}/
- param name=paperType expression=${maven.pdf.paperType}/
- param name=companyIncName expression=${maven.pdf.companyIncName}/
- param name=publicationYear expression=${maven.pdf.copyrightYear}/
- param name=coverProjectCompany
expression=${maven.pdf.cover.projectCompany}/
- param name=coverProjectName expression=${maven.pdf.cover.projectName}/
- param name=coverType expression=${maven.pdf.cover.type}/
- param name=coverVersion expression=${maven.pdf.cover.version}/
- param name=coverDate expression=${maven.pdf.cover.date}/
- param name=companyLogo expression=${maven.pdf.companyLogo}/
- param name=projectLogo expression=${maven.pdf.projectLogo}/
- param name=imageDpi expression=${maven.pdf.imageDpi}/
- param name=debug expression=${maven.pdf.debug}/
-/style
+
+j:scope
+ j:new className=java.io.File var=styleFile
+j:arg value=${plugin.resources}/project2fo.xslt /
+ /j:new
+ j:new className=javax.xml.transform.stream.StreamSource var=style
+j:arg value=${styleFile} /
+ /j:new
+
+ j:new className=org.apache.xalan.processor.TransformerFactoryImpl
var=transformerFactory /
+ j:invoke on=${transformerFactory} method=newTransformer
var=transformer
+j:arg value=${style} /
+ /j:invoke
+ j:invoke on=${transformer} method=setParameter
+j:arg value=basePath /
+j:arg value=${internal_pdf_workingDir}/
+ /j:invoke
+ j:invoke on=${transformer} method=setParameter
+j:arg value=confidential /
+j:arg value=${maven.pdf.confidential}/
+ /j:invoke
+ j:invoke on=${transformer} method=setParameter
+j:arg value=paperType /
+j:arg value=${maven.pdf.paperType}/
+ /j:invoke
+ j:invoke on=${transformer} method=setParameter
+j:arg value=companyIncName /
+j:arg value=${maven.pdf.companyIncName}/
+ /j:invoke
+ j:invoke on=${transformer} method=setParameter
+j:arg value=publicationYear /
+j:arg value=${maven.pdf.copyrightYear}/
+ /j:invoke
+ j:invoke on=${transformer} method=setParameter
+j:arg value=coverProjectCompany /
+j:arg value=${maven.pdf.cover.projectCompany}/
+ /j:invoke
+ j:invoke on=${transformer} method=setParameter
+j:arg value=coverProjectName /
+j:arg value=${maven.pdf.cover.projectName}/
+ /j:invoke
+ j:invoke on=${transformer} method=setParameter
+j:arg value=coverType /
+j:arg value=${maven.pdf.cover.type}/
+ /j:invoke
+ j:invoke on=${transformer} method=setParameter
+j:arg value=coverVersion /
+j:arg value=${maven.pdf.cover.version}/
+ /j:invoke
+ j:invoke on=${transformer} method=setParameter
+
Re: Maven snapshot does not compile
I've never tried those snapshots, but regardless you need to bootstrap.
ant -f build-bootstrap.xml
Refer to the build instructions on the web site.
Regards,
Brett
A Leg wrote:
Hi
Problem to compile maven snapshot on a linux fedora 2 machine.
Snapshot comes from :
http://cvs.apache.org/snapshots/maven/maven_20041013104550.tar.gz
And I get this error :
Plugin 'maven-deploy-plugin' in project 'Maven' is not available
Any help welcome
Andre Legendre
Complete error log is :
{orion:rcs} maven
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0
Attempting to download maven-jelly-tags-1.1-SNAPSHOT.jar.
Attempting to download maven-model-1.1-SNAPSHOT.jar.
Plugin 'maven-deploy-plugin' in project 'Maven' is not available
build:start:
java:prepare-filesystem:
java:compile:
[echo] Compiling to
/home/rcs/Master/extern/java/jakarta/maven/target/classes
[javac] Compiling 65 source files to
/home/rcs/Master/extern/java/jakarta/maven/target/classes
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:38:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.Credentials;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:39:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.Header;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:40:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.HostConfiguration;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:41:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.HttpClient;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:42:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.HttpRecoverableException;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:43:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.NTCredentials;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:44:
package org.apache.commons.httpclient does not exist
import org.apache.commons.httpclient.UsernamePasswordCredentials;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:45:
package org.apache.commons.httpclient.methods does not exist
import org.apache.commons.httpclient.methods.GetMethod;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:46:
package org.apache.commons.httpclient.util does not exist
import org.apache.commons.httpclient.util.DateParser;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:47:
package org.apache.commons.httpclient.util does not exist
import org.apache.commons.httpclient.util.DateParseException;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:438:
cannot resolve symbol
symbol : class HttpClient
location: class org.apache.maven.util.HttpUtils
private static String retrieveArtifact(HttpClient client, URL
source, File destinationFile, long timestamp, DownloadMeter
downloadMeter ) throws FileNotFoundException, IOException,
HttpRecoverableException {
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:438:
cannot resolve symbol
symbol : class HttpRecoverableException
location: class org.apache.maven.util.HttpUtils
private static String retrieveArtifact(HttpClient client, URL
source, File destinationFile, long timestamp, DownloadMeter
downloadMeter ) throws FileNotFoundException, IOException,
HttpRecoverableException {
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:346:
cannot resolve symbol
symbol : class Credentials
location: class org.apache.maven.util.HttpUtils
Credentials creds = null;
^
/home/rcs/Master/extern/java/jakarta/maven/src/java/org/apache/maven/util/HttpUtils.java:348:
cannot resolve symbol
symbol : class NTCredentials
location: class org.apache.maven.util.HttpUtils
creds = new NTCredentials(proxyUserName,
proxyPassword, loginHost, loginDomain);
^
Re: JellySwt : problem running demo
Looks like it is trying to link a win32 native library.
Commons-user will need to help you out with how to set up the JellySWT
build to pick up a linux version.
Cheers,
Brett
A Leg wrote:
Hi
I am interested to use jelly swt for our project.
http://compiere-mfgscm.sourceforge.net
I when I try to run jelly swt demo on Linux fedora 2 I get this :
I already sent this mail to common-users but may be it is better here ?
Any help welcome.
Thank's for any reply
Andre Legendre
{orion:rcs} maven demo
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0
build:start:
java:prepare-filesystem:
java:compile:
[echo] Compiling to
/home/rcs/Master/extern/java/jakarta/jakarta-commons/jelly/jelly-tags/swt/target/classes
java:jar-resources:
test:prepare-filesystem:
test:test-resources:
test:compile:
create-classpath:
demo:
[java] Exception in thread main java.lang.UnsatisfiedLinkError: no
swt-win32-2128 in java.library.path
[java] at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1491)
[java] at java.lang.Runtime.loadLibrary0(Runtime.java:788)
[java] at org.eclipse.swt.internal.win32.OS.clinit(OS.java:42)
[java] at
org.eclipse.swt.internal.win32.TCHAR.clinit(TCHAR.java:26)
[java] at org.eclipse.swt.widgets.Widget.clinit(Widget.java:79)
[java] at java.lang.Class.forName0(Native Method)
[java] at java.lang.Class.forName(Class.java:141)
[java] at
org.apache.commons.jelly.tags.swt.SwtTagLibrary.class$(SwtTagLibrary.java:84)
[java] at
org.apache.commons.jelly.tags.swt.SwtTagLibrary.init(SwtTagLibrary.java:94)
[java] at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[java] at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[java] at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[java] at
java.lang.reflect.Constructor.newInstance(Constructor.java:274)
[java] at java.lang.Class.newInstance0(Class.java:308)
[java] at java.lang.Class.newInstance(Class.java:261)
[java] at
org.apache.commons.jelly.JellyContext.getTagLibrary(JellyContext.java:454)
[java] at
org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java:979)
[java] at
org.apache.commons.jelly.parser.XMLParser.startElement(XMLParser.java:593)
[java] at
org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:446)
[java] at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:306)
[java] at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1568)
[java] at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:355)
[java] at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:539)
[java] at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:595)
[java] at
org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
[java] at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1125)
[java] at
org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:238)
[java] at
org.apache.commons.jelly.Jelly.compileScript(Jelly.java:125)
[java] at
org.apache.commons.jelly.util.CommandLineParser.invokeCommandLineJelly(CommandLineParser.java:98)
[java] at org.apache.commons.jelly.Jelly.main(Jelly.java:92)
[java] [ERROR] Java Result: 1
BUILD SUCCESSFUL
Total time: 5 seconds
Finished at: Thu Oct 14 11:30:44 EEST 2004
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven snapshot does not compile
Additionally, your downloaded copy of httpclient may be corrupt - check the size of ~/.maven/repository/httpclient/jars/httpclient-2.0.jar Brett Porter wrote: I've never tried those snapshots, but regardless you need to bootstrap. ant -f build-bootstrap.xml Refer to the build instructions on the web site. Regards, Brett A Leg wrote: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPECLIPSE-48) handling source attachments (patch)
The following issue has been updated: Updater: fabrizio giustina (mailto:[EMAIL PROTECTED]) Date: Thu, 14 Oct 2004 5:13 PM Comment: this is an updated version of the patch. Updated after the MPECLIPSE-47 commit, fixes an error in the previous patch, and contains the fix for MPECLIPSE-49 too Changes: Attachment changed to MPECLIPSE-48_updated.diff - For a full history of the issue, see: http://jira.codehaus.org/browse/MPECLIPSE-48?page=history - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-48 Here is an overview of the issue: - Key: MPECLIPSE-48 Summary: handling source attachments (patch) Type: Improvement Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Versions: 1.9 Assignee: Reporter: fabrizio giustina Created: Tue, 12 Oct 2004 4:36 PM Updated: Thu, 14 Oct 2004 5:13 PM Description: Actually maven repository doesn't contain source artifacts, however it would be nice if eclipse users could have a way to handle source for jars and have them added to eclipse .classpath (needed for debug and javadocs). The attached path let users store sources in the local maven repository in the same way other artifacts are managed. Through the modification of the jar path the plugin will look for the sources file and, if existing, it will add them to the .classpath file. The position of src files is controlled by 2 plugin properties: maven.eclipse.src.dir (directory for source artifact type) and maven.eclipse.src.extension (extension for files). These are temporarely managed as eclipse plugin properties till there is a standard maven default for them. As an example, using the default values for these properties: MAVEN_REPO/eclipse/jars/eclipse-ui-3.0.0.jar will be mapped to MAVEN_REPO/eclipse/src/eclipse-ui-3.0.0.zip If the source zip is not available, it will not be added to the classpath file, so it will not cause any problem to users who don't have sources in their local repository. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1466) install_repo.bat can require inconsistent quoting on the command line
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1466 Here is an overview of the issue: - Key: MAVEN-1466 Summary: install_repo.bat can require inconsistent quoting on the command line Type: Bug Status: Unassigned Priority: Minor Original Estimate: 1 hour Time Spent: Unknown Remaining: 1 hour Project: maven Components: documentation Versions: 1.0 Assignee: Reporter: Albert Davidson Chou Created: Thu, 14 Oct 2004 6:13 PM Updated: Thu, 14 Oct 2004 6:13 PM Environment: Windows XP Professional SP 1 Description: The install_repo.bat script in version 1.0 builds up its argument word by word and then puts double quotes around the value thereby built up wherever it is used. However, this implementation makes using the script kind of weird. On Windows I have to quote the command anyway if it contains spaces, e.g., %MAVEN_HOME%\bin\install_repo.bat and I would expect to have to quote its argument for similar reasons. But as it stands now, install_repo.bat _requires_ the following quoting syntax if both MAVEN_HOME and HOME (or HOMEPATH) contain spaces: %MAVEN_HOME%\bin\install_repo.bat %HOME%\.maven\repository Note the inconsistency in quoting. The Windows batch language doesn't treat quotes the way most shells do; the quotes are literally part of the string rather than just a meta-character that signifies that contained whitespace is literal rather than a command or argument separator. The syntax %~1 can be used to produce a non-quoted and fully-path-expanced version of whatever argument %1 was, at least in more recent versions of Windows (2000, XP, 2003). No guarantees that this feature is present in Windows 9x - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1467) maven:get/set doesn't appear to correctly initialise plugin in some cases
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1467
Here is an overview of the issue:
-
Key: MAVEN-1467
Summary: maven:get/set doesn't appear to correctly initialise plugin in some cases
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
plugin manager
Fix Fors:
1.0.1
Versions:
1.0
Assignee: Brett Porter
Reporter: Brett Porter
Created: Thu, 14 Oct 2004 7:53 PM
Updated: Thu, 14 Oct 2004 7:53 PM
Description:
ref: maven-user.
I'm pretty sure this will come up empty:
project
goal name=foo
maven:get plugin=maven-war-plugin var=foo property=maven.war.src /
echo${foo}/echo
/goal
/project
-
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/ear/src/plugin-test project.xml
felipeal2004/10/14 22:01:55 Modified:ear/src/plugin-test project.xml Log: updated version of maven-j2ee-plugin dependency Revision ChangesPath 1.10 +1 -1 maven-plugins/ear/src/plugin-test/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/ear/src/plugin-test/project.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- project.xml 15 Mar 2004 10:54:10 - 1.9 +++ project.xml 15 Oct 2004 05:01:54 - 1.10 @@ -79,7 +79,7 @@ dependency groupIdmaven/groupId artifactIdmaven-j2ee-plugin/artifactId - version1.3/version + version1.4/version typeplugin/type /dependency /dependencies - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/ear project.xml
felipeal2004/10/14 22:02:05 Modified:ear project.xml Log: added myself as developer Revision ChangesPath 1.35 +10 -0 maven-plugins/ear/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/ear/project.xml,v retrieving revision 1.34 retrieving revision 1.35 diff -u -r1.34 -r1.35 --- project.xml 14 Jul 2004 23:19:14 - 1.34 +++ project.xml 15 Oct 2004 05:02:05 - 1.35 @@ -81,6 +81,16 @@ roleJava Developer/role /roles /developer +developer + nameFelipe Leme/name + idfelipeal/id + email[EMAIL PROTECTED]/email + organizationFalcon Informatica/organization + roles +roleJava Developer/role +roleJelly Developer/role + /roles +/developer /developers dependencies dependency - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/ear/xdocs changes.xml properties.xml
felipeal2004/10/14 22:07:35
Modified:ear plugin.jelly plugin.properties
ear/xdocs changes.xml properties.xml
Log:
MPEAR-21: added property maven.ear.appxml.encoding
Revision ChangesPath
1.21 +2 -2 maven-plugins/ear/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/ear/plugin.jelly,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- plugin.jelly 21 Jul 2004 08:03:22 - 1.20
+++ plugin.jelly 15 Oct 2004 05:07:35 - 1.21
@@ -133,12 +133,12 @@
!--==--
goal name=ear:generate-ear-descriptor description=Generates the ear
descriptor
- ant:echoGenerating appxml file:${maven.ear.appxml} version
${maven.ear.appxml.version}/ant:echo
+ ant:echoGenerating appxml file:${maven.ear.appxml} version
${maven.ear.appxml.version} encoding: ${maven.ear.appxml.encoding}/ant:echo
j:file name=${maven.ear.appxml}
outputMode=xml
prettyPrint=true
- encoding=UTF-8
+ encoding=${maven.ear.appxml.encoding}
j:switch on=${maven.ear.appxml.version}
1.7 +2 -1 maven-plugins/ear/plugin.properties
Index: plugin.properties
===
RCS file: /home/cvs/maven-plugins/ear/plugin.properties,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- plugin.properties 15 Mar 2004 10:54:10 - 1.6
+++ plugin.properties 15 Oct 2004 05:07:35 - 1.7
@@ -30,4 +30,5 @@
maven.ear.appxml.generate=false
maven.ear.displayname=${pom.id}
maven.ear.appxml.version=1.3
-maven.ear.resources=${maven.build.dir}/ear
\ No newline at end of file
+maven.ear.resources=${maven.build.dir}/ear
+maven.ear.appxml.encoding=UTF-8
\ No newline at end of file
1.22 +1 -0 maven-plugins/ear/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/ear/xdocs/changes.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- changes.xml 21 Jul 2004 08:03:22 - 1.21
+++ changes.xml 15 Oct 2004 05:07:35 - 1.22
@@ -25,6 +25,7 @@
/properties
body
release version=1.6-SNAPSHOT date=in CVS
+ action dev=felipeal type=add issue=MPEAR-21Added property
codemaven.ear.appxml.encoding/code./action
action dev=vmassol type=update issue=MPEAR-19
The plugin now displays the version of the bundled artifacts on the
console.
1.14 +18 -8 maven-plugins/ear/xdocs/properties.xml
Index: properties.xml
===
RCS file: /home/cvs/maven-plugins/ear/xdocs/properties.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- properties.xml12 Apr 2004 22:53:01 - 1.13
+++ properties.xml15 Oct 2004 05:07:35 - 1.14
@@ -25,7 +25,7 @@
/properties
body
-section name=ejb jar settings
+section name=ear settings
table
trthProperty/ththOptional?/ththDescription/ththDefault/th/tr
tr
@@ -42,7 +42,7 @@
tdmaven.ear.appxml/td
tdYes/td
td
-Location of the application.xml file
+Location of the codeapplication.xml/code file
to be used within the ear file.
/td
td
@@ -53,7 +53,7 @@
tdmaven.ear.appxml.generate/td
tdYes/td
td
-Indicates if application.xml files should
+Indicates if codeapplication.xml/code files should
be autogenerated
/td
td
@@ -64,10 +64,10 @@
tdmaven.ear.appxml.version/td
tdYes/td
td
-Inserts the doctype header depending on the specified version. Default
is 1.3
+Inserts the doctype header depending on the specified version.
/td
td
-false
+1.3
/td
/tr
tr
@@ -75,7 +75,7 @@
tdYes/td
td
Display name of the application to be used
-when application.xml file is autogenerated
+when codeapplication.xml/code file is autogenerated
/td
td
${pom.id}
@@ -101,6 +101,16 @@
${maven.src.dir}/application
/td
/tr
+tr
+ tdmaven.ear.appxml.encoding/td
+ tdYes/td
+ td
+
cvs commit: maven-plugins/ear project.xml
felipeal2004/10/14 22:09:31 Modified:ear project.xml Log: fixed URL for Jelly util taglib Revision ChangesPath 1.36 +1 -1 maven-plugins/ear/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/ear/project.xml,v retrieving revision 1.35 retrieving revision 1.36 diff -u -r1.35 -r1.36 --- project.xml 15 Oct 2004 05:02:05 - 1.35 +++ project.xml 15 Oct 2004 05:09:31 - 1.36 @@ -103,7 +103,7 @@ groupIdcommons-jelly/groupId artifactIdcommons-jelly-tags-util/artifactId version20030211.141939/version - urlhttp://jakarta.apache.org/commons/jelly/tags/util//url + urlhttp://jakarta.apache.org/commons/jelly/libs/util/index.html/url /dependency /dependencies /project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPEAR-21) application.xml is always generated with UTF-8
Message: The following issue has been closed. Resolver: Felipe Leme Date: Fri, 15 Oct 2004 1:10 AM Fixed, by adding property maven.ear.appxml.encoding. - View the issue: http://jira.codehaus.org/browse/MPEAR-21 Here is an overview of the issue: - Key: MPEAR-21 Summary: application.xml is always generated with UTF-8 Type: Improvement Status: Closed Priority: Major Resolution: FIXED Original Estimate: 30 minutes Time Spent: Unknown Remaining: 30 minutes Project: maven-ear-plugin Fix Fors: 1.6 Versions: 1.5 Assignee: Felipe Leme Reporter: Felipe Leme Created: Thu, 7 Oct 2004 3:53 PM Updated: Fri, 15 Oct 2004 1:10 AM Description: application.xml is always generated with UTF-8, which is bad. I will modify it to use the value defined by a property (like maven.ear.appxml.encoding). - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPEAR-25) Create property maven.ear.final.name
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPEAR-25 Here is an overview of the issue: - Key: MPEAR-25 Summary: Create property maven.ear.final.name Type: Improvement Status: Open Priority: Minor Original Estimate: 30 minutes Time Spent: Unknown Remaining: 30 minutes Project: maven-ear-plugin Fix Fors: 1.6 Versions: 1.5 Assignee: Felipe Leme Reporter: Felipe Leme Created: Fri, 15 Oct 2004 1:29 AM Updated: Fri, 15 Oct 2004 1:29 AM Description: See MPJAVA-8 for more details. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPJAR-38) Create property maven.jar.final.name
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPJAR-38 Here is an overview of the issue: - Key: MPJAR-38 Summary: Create property maven.jar.final.name Type: Improvement Status: Open Priority: Minor Original Estimate: 30 minutes Time Spent: Unknown Remaining: 30 minutes Project: maven-jar-plugin Fix Fors: 1.7 Versions: 1.6 Assignee: Felipe Leme Reporter: Felipe Leme Created: Fri, 15 Oct 2004 1:31 AM Updated: Fri, 15 Oct 2004 1:31 AM Description: See MPJAVA-8 for more details. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPRAR-2) Create property maven.ear.final.name
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPRAR-2 Here is an overview of the issue: - Key: MPRAR-2 Summary: Create property maven.ear.final.name Type: Improvement Status: Open Priority: Minor Original Estimate: 30 minutes Time Spent: Unknown Remaining: 30 minutes Project: maven-rar-plugin Fix Fors: 1.1 Versions: 1.0 Assignee: Felipe Leme Reporter: Felipe Leme Created: Fri, 15 Oct 2004 1:32 AM Updated: Fri, 15 Oct 2004 1:32 AM Description: See MPJAVA-8 for more details. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJAVA-8) Consistent properties for jar, war, ejb and ear
Message:
The following issue has been closed.
Resolver: Felipe Leme
Date: Fri, 15 Oct 2004 1:34 AM
I created 3 new issues, one for each plugin (jar, ear and rar).
-
View the issue:
http://jira.codehaus.org/browse/MPJAVA-8
Here is an overview of the issue:
-
Key: MPJAVA-8
Summary: Consistent properties for jar, war, ejb and ear
Type: Improvement
Status: Closed
Priority: Major
Resolution: DUPLICATE
Original Estimate: Unknown
Time Spent: 30 minutes
Remaining: 0 minutes
Project: maven-java-plugin
Assignee: Felipe Leme
Reporter: Aslak Hellesoy
Created: Tue, 25 Mar 2003 5:11 AM
Updated: Fri, 15 Oct 2004 1:34 AM
Description:
The current naming conventions for properties defining the names of jar, ejb, war and
ear are somewhat inconsistent.
This patch introduces 4 new properties:
# defined in the java plugin's plugin.properties
maven.jar.final.name = ${maven.final.name}.jar
# defined in the war plugin's plugin.properties
maven.war.final.name = ${maven.final.name}.war
# defined in the ejb plugin's plugin.properties
maven.ejb.final.name = ${maven.final.name}.jar
# defined in the ear plugin's plugin.properties
maven.ear.final.name = ${maven.final.name}.ear
This patch solves the following problems:
1) It removes the risk of name clashes for projects that produce both plain
jar files and ejb jar files, since the maven.ejb.final.name property can be overridden.
2) When packaging wars and ejbs inside ears, it is sometimes desirable to have
different names for ejbs and wars, like foo-ejb-1.0.jar and foo-war-1.0.war. This is
necessary when the contents of an ear file is to be deployed on different weblogic
servers with weblogic.deploy. This can now be achieved by overriding
maven.ejb.final.name and/or maven.war.final.name.
This patch should not change any of the current functionality, and the documentation
has been updated too.
-
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven snapshot does not compile
Hi Brett Your advice should be good : I don't have ~/.maven/repository/httpclient/jars/httpclient-2.0.jar nor ~/.maven/repository/httpclient/ I have a ~/.maven/repository/ with many subdirectories. Where can I download httpclient-2.0.jar ? For any reason maven does not try to do it. Thank's for your help Andre Brett Porter wrote: Additionally, your downloaded copy of httpclient may be corrupt - check the size of ~/.maven/repository/httpclient/jars/httpclient-2.0.jar Brett Porter wrote: I've never tried those snapshots, but regardless you need to bootstrap. ant -f build-bootstrap.xml Refer to the build instructions on the web site. Regards, Brett A Leg wrote: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
