Re: Welcome Robert Scholte to the Apache Maven team!

[Vincent Siveton]

Welcome Robert

Vincent

2011/7/6 Mark Struberg :
> Hi Maven folks!
>
> The Apache Maven PMC is glad to welcome Robert Scholte as new Apache Maven 
> Committer!
> Most of us know Robert already from his dedicated work on lots of Maven 
> plugins over at codehaus-mojo, so I guess I don't have to add much ;)
>
> Robert, congratulations and happy hacking!
>
> LieGrue,
> strub
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Fwd: Travel Assistance applications now open for ApacheCon NA 2011

[Vincent Siveton]

FYI

-- Forwarded message --
From: Gavin McDonald 
Date: 2011/6/6
Subject: Travel Assistance applications now open for ApacheCon NA 2011
To: committ...@apache.org


The Apache Software Foundation (ASF)'s Travel Assistance Committee (TAC) is
now accepting applications for ApacheCon North America 2011, 7-11 November
in Vancouver BC, Canada.

The TAC is seeking individuals from the Apache community at-large --users,
developers, educators, students, Committers, and Members-- who would like to
attend ApacheCon, but need some financial support in order to be able to get
there. There are limited places available, and all applicants will be scored
on their individual merit.

Financial assistance is available to cover flights/trains, accommodation and
entrance fees either in part or in full, depending on circumstances.
However, the support available for those attending only the BarCamp (7-8
November) is less than that for those attending the entire event (Conference
+ BarCamp 7-11 November). The Travel Assistance Committee aims to support
all official ASF events, including cross-project activities; as such, it may
be prudent for those in Asia and Europe to wait for an event geographically
closer to them.

More information can be found at http://www.apache.org/travel/index.html
including a link to the online application and detailed instructions for
submitting.

Applications will close on 8 July 2011 at 22:00 BST (UTC/GMT +1).

We wish good luck to all those who will apply, and thank you in advance for
tweeting, blogging, and otherwise spreading the word.

Regards,
The Travel Assistance Committee

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Doap Plugin 1.1 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Doap
Plugin, version 1.1

The DOAP Plugin is used to generate compliant Description of a Project
(DOAP) file from a POM. The main goal is to be able to provide DOAP
files for Semantic Web systems that use them as primary input but that
would also alleviate the burden of maintaining two sets of metadata.

http://maven.apache.org/plugins/maven-doap-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-doap-plugin
  1.1


Release Notes - Maven 2.x DOAP Plugin - Version 1.1

** Bug
* [MDOAP-22] - Documentation regarding site-integration hrefs wrong file
* [MDOAP-23] - Plugin assumes that both  and
 are always specified
* [MDOAP-24] - programing-language, os and name properties should
be an RDF literals, not a RDF resources.
* [MDOAP-25] - foaf:Organization usage doesn't comply with DoaP/FoaF specs.
* [MDOAP-26] - minimal pom IT is failing with Maven 3
* [MDOAP-27] - Generated files aren't useable with Jena
* [MDOAP-31] - Generated DOAP Mailing lists are too stricts

** Improvement
* [MDOAP-28] - Remove developers/contributors having role 'emeritus'
* [MDOAP-32] - Generate a DOAP file for another Maven Project
* [MDOAP-33] - Add more DOAP options like blog, audience, plateform...
* [MDOAP-34] - Add a way to add dynamically namespace

** New Feature
* [MDOAP-15] - Please add german localization
* [MDOAP-29] - Detect Apache projects
* [MDOAP-35] - Fetch file-release url

** Task
* [MDOAP-30] - Update requirement to Maven 2.2 and Java 5

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 2.3.1 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Project
Info Reports Plugin, version 2.3.1

This plugin is used to generate reports information about the project.
http://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-project-info-reports-plugin
 2.3.1


Release Notes - Maven 2.x Project Info Reports Plugin - Version 2.3.1

** Bug
* [MPIR-201] - The project info module report produces incorrect links
* [MPIR-209] - Wrong links in modules overview page if module
artifactId does not match directory structure
* [MPIR-210] - Project Summary Download link points to
distributionManagement (upload) url
* [MPIR-211] - NPE with custom text bundle
* [MPIR-212] - src/main/java does not exist for non-jar project

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 2.3 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Project
Info Reports Plugin, version 2.3

This plugin is used to generate reports information about the project.

http://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  2.3



Release Notes - Maven 2.x Project Info Reports Plugin - Version 2.3


** Bug
* [MPIR-128] - Add a link to a repository location in Project Summary
* [MPIR-158] - Artifact ## has no file error.
* [MPIR-180] - Repositories which require authentication get blacklisted
* [MPIR-198] - introduction does not allow HTML markup
* [MPIR-199] - ProjectInfoReportUtils.java : Avoid using blocking
call [ url.openStream() ] while opening stream from an URL

** Improvement
* [MPIR-171] - support "TimeZones" as a timezone
* [MPIR-194] - [WARNING] Deprecated API called
* [MPIR-202] - Typo
* [MPIR-204] - License report should not try to include pdf
content as plain text
* [MPIR-206] - Generalize configuration for text reports

** New Feature
* [MPIR-80] - Add Java requirements to the Dependency Report
* [MPIR-205] - Add the license information for each dependency
* [MPIR-207] - Add a distribution management report

** Task
* [MPIR-200] - update requirement to Maven 2.2 and Java 5

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven PDF Plugin 1.1 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven PDF
Plugin, version 1.1

This plug-in allows you to generate a PDF version of your project's
documentation.

http://maven.apache.org/plugins/maven-pdf-plugin/

You should specify the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-pdf-plugin
 1.1


Release Notes - Maven 2.x PDF Plugin - Version 1.1

** Bug
* [MPDF-17] - Test fails with JDK 1.5+ if base directory has a
space in its path
* [MPDF-28] - When specifying output dir, copy only the generated pdf
* [MPDF-31] - LinkageError using JDK6

** Improvement
* [MPDF-23] - Definition Lists are not formatted correctly
* [MPDF-26] - Add report generation in PDF
* [MPDF-27] - Support Doxia files generated by Maven plugins
* [MPDF-30] - Add a parameter to include or not the TOC

** New Feature
* [MPDF-24] - Support Velocity files

** Wish
* [MPDF-16] - Add German translation

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Doxia and Doxia Site Tools 1.1.2 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Doxia
and Doxia Site Tools version 1.1.2

Doxia is a content generation framework which aims to provide its
users with powerful techniques for generating static and dynamic
content: Doxia can be used in web-based publishing context to generate
static sites, in addition to being incorporated into dynamic content
generation systems like blogs, wikis and content management systems.

Doxia supports markup languages with simple syntaxes. Lightweight
markup languages are used by people who might be expected to read the
document source as well as the rendered output.

http://maven.apache.org/doxia

You should specify the version in your project's plugin configuration:

Release Notes - Maven Doxia - Version 1.1.2

** Bug
* [DOXIA-338] - Section numbering and links
* [DOXIA-343] - FO: links broken if link target contains dot
* [DOXIA-353] - IText sink: Definition Lists are not formatted correctly
* [DOXIA-357] - FO: NoSuchElementException with a table caption
* [DOXIA-359] - Xdoc parser doesnt make the difference for 
* [DOXIA-360] - Unable to specify table cell/row alignment
* [DOXIA-362] - Entities in attribute values are not escaped
* [DOXIA-363] - FO: Nested tables are not allowed
* [DOXIA-364] - Guarantee the state of sinks and parsers impl
* [DOXIA-366] - Wrong TOC when styles

** Improvement
* [DOXIA-358] - avoid to store in memory the full generated FO
document when only table content is needed


Release Notes - Maven Doxia Sitetools - Version 1.1.2

** Bug
* [DOXIASITETOOLS-29] - PathUtils.getRelativePath returns
different results on Windows and Linux
* [DOXIASITETOOLS-35] - wrong model inheritance for text-only
banners (without image)

** Improvement
* [DOXIASITETOOLS-21] - Add Velocity support to DocRenderer
* [DOXIASITETOOLS-33] - Add an option to include or not the TOC
* [DOXIASITETOOLS-36] - add lastModification to DecorationModel to
track last modification time of site.xml

** New Feature
* [DOXIASITETOOLS-7] - site.xml  attribute no more working
* [DOXIASITETOOLS-31] - Allow images in the menu items of the site.xml

** Task
* [DOXIASITETOOLS-32] - Deployed decoration-1.0.1.xsd

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Support for ditaa diagrams in APT

[Vincent Siveton]

Not scheduled and I dont think we will make efforts to.
You could always provide a module for it and create an issue.

Cheers,

Vincent

2009/11/17 Lóránt Pintér :
> Hi,
>
> Are there any plans to support ditaa ( http://ditaa.sourceforge.net/ ) in
> the future? It would be a nice addition to the APT format.
>
> Lóránt
>

[ANN] Maven Reporting Impl 2.0.4.3 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven
Reporting Impl, version 2.0.4.3.

This shared component contains abstract classes to manage report generation..

http://maven.apache.org/shared/maven-reporting-impl/

Release Notes - Maven Shared Components - Version maven-reporting-impl 2.0.4.3

** Bug
* [MSHARED-120] - No single report generated with latest
maven-reporting-impl

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Javadoc Plugin 2.6.1 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Javadoc
Plugin, version 2.6.1

This plugin uses the javadoc tool for generating javadocs for the
specified project.

http://maven.apache.org/plugins/maven-javadoc-plugin/

You should specify the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-javadoc-plugin
 2.6.1



Release Notes - Maven 2.x Javadoc Plugin - Version 2.6.1

** Bug
* [MJAVADOC-244] - Javadoc plugin: java files under
src/main/javadoc and doc-files directory are being compiled
* [MJAVADOC-246] - ExceptionInInitializerError with
maven-site-plugin:2.1-SNAPSHOT and mvn > 2.1
* [MJAVADOC-251] - Configuration of javadoc:javadoc fails with NPE
upon disadvantageous order of config injection
* [MJAVADOC-252] - javadoc link : nonproxyhosts not used
* [MJAVADOC-257] - maven-javadoc-plugin 2.5, 2.6 and mojo: Error
extracting plugin descriptor
* [MJAVADOC-259] - Resource copying from javadoc dir is incomplete
* [MJAVADOC-262] - Parameters like sourcepath depend on system
path separator (colon/semicolon)
* [MJAVADOC-268] - performance problem in
AbstractJavadocMojo.getModulesLinks()

** Improvement
* [MJAVADOC-258] - Grouping example could show multiple packages per group
* [MJAVADOC-266] - META-INF directory copied from resource artifacts
* [MJAVADOC-267] - Allow changing the reportOutputDirectory from
the commandline


** Task
* [MJAVADOC-248] - Site 'Usage' page references 2.5 version of m-javadoc-p

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Javadoc Plugin 2.6 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Javadoc
Plugin, version 2.6.

The Maven Javadoc Plugin is a plugin that uses the javadoc tool for
generating javadocs for the specified project.

http://maven.apache.org/plugins/maven-javadoc-plugin/

You should specify the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-javadoc-plugin
 2.6


Release Notes - Maven 2.x Javadoc Plugin - Version 2.6

** Sub-task
* [MJAVADOC-239] - Helpfile loaded from classpath

** Bug
* [MJAVADOC-181] - Javadoc report not generated for multi-module
project if run from parent level.
* [MJAVADOC-215] - warning proxyHost' is deprecated since 2.4
* [MJAVADOC-219] - skip parameter is ignored in aggregate goal
* [MJAVADOC-220] - ArrayIndexOutOfBoundsException in
JavadocUtil.getIncludedFiles
* [MJAVADOC-230] - aggregate report requires to have
aggregate=true configuration parameter
* [MJAVADOC-231] - tagletpath does not seem to work
* [MJAVADOC-232] - copied doc-files folder contains svn meta files
* [MJAVADOC-238] - No timeout set for URLConnection which can
cause build to get stuck

** Improvement
* [MJAVADOC-216] - Stylesheet file loaded from classpath
* [MJAVADOC-222] - Documentation Issues
* [MJAVADOC-225] - The plugin should be able to generate a jar of
the aggregated javadoc
* [MJAVADOC-226] - Add a new goal to fix Javadoc tags
* [MJAVADOC-240] - Add default Javadoc link depending the values
of maven-compiler-plugin configuration

** New Feature
* [MJAVADOC-97] - enable internal/external dependency references as links

** Task
* [MJAVADOC-217] - Update "Aggregating Javadocs" example

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Fwd: Application Period for Travel Assistance to ApacheCon US 2009 Opens Soon

[Vincent Siveton]

The Travel Assistance Committee is taking in applications for those wanting
to attend ApacheCon US 2009 (Oakland) which takes place between the 2nd and
6th November 2009.

The Travel Assistance Committee is looking for people who would like to be
able to attend ApacheCon US 2009 who may need some financial support in
order to get there. There are limited places available, and all applications
will be scored on their individual merit. Applications are open to all open
source developers who feel that their attendance would benefit themselves,
their project(s), the ASF and open source in general.

Financial assistance is available for flights, accommodation, subsistence
and Conference fees either in full or in part, depending on circumstances.
It is intended that all our ApacheCon events are covered, so it may be
prudent for those in Europe and/or Asia to wait until an event closer to
them comes up - you are all welcome to apply for ApacheCon US of course, but
there should be compelling reasons for you to attend an event further away
that your home location for your application to be considered above those
closer to the event location.

More information can be found on the main Apache website at
http://www.apache.org/travel/index.html - where you will also find a link to
the online application and details for submitting.

Applications for applying for travel assistance will open on 27th July 2009
and close of the 17th August 2009.

Good luck to all those that will apply.

Regards,

The Travel Assistance Committee

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Fwd: [GSoC 2009] Apache is officially participating in Google Summer of Code 2009

[Vincent Siveton]

FYI

-- Forwarded message --
From: Luciano Resende 
Date: 2009/3/19
Subject: [GSoC 2009] Apache is officially participating in Google
Summer of Code 2009
To: p...@apache.org


Dear PMC,

It's now official, Google has announced that The Apache Software
Foundation was selected as one of the participating organization in
the GSoC 2009 program. This is an excellent opportunity for Apache, as
it allows projects to build/increase its community, it also help
students to learn about open source, about Apache Software Foundation
and how to do things the "Apache Way".

Please start advertising the program and discussing project ideas with
your project community. Then add your project ideas to the ASF GSoC
2009 Official Project Ideas page [1], as this is going to be the most
visible place for students. Per GSoC 2009 timeline, Students should
officially start applying for these ideas on March 23.

ASF Members and committers can volunteer to be mentors in the GSoC
2009 program (see [2] for more details about being a mentor). We
invite all mentors and GSoC interested parties to subscribe to the
code-awa...@a.o mailing list [3] to coordinate work between mentors,
ask questions and get updates related to GSoC 2009 program.

Please, feel free to forward this announce to any appropriate dev@ or
users@ lists so your larger community can hear about the GSoC 2009
program.

[1] http://wiki.apache.org/general/SummerOfCode2009
[2] http://wiki.apache.org/general/SummerOfCodeMentor
[3] mailto:code-awards-subscr...@apache.org


--
Luciano Resende
http://people.apache.org/~lresende
http://lresende.blogspot.com/

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Doxia 1.1 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Doxia,
Doxia Sitetools, version 1.1 and Maven Doxia Tools, version 1.0.

Doxia is a content generation framework which aims to provide its
users with powerful techniques for generating static and dynamic
content: Doxia can be used in web-based publishing context to generate
static sites, in addition to being incorporated into dynamic content
generation systems like blogs, wikis and content management systems.

http://maven.apache.org/doxia/

Release Notes - Maven Doxia - Version 1.1

** Bug
* [DOXIA-51] - RtfSink supports only ".ppm" image type in figureGraphics()
* [DOXIA-59] - Doxia creates files with inconsistent new lines
* [DOXIA-99] - Figures require extension in APT and they should not
* [DOXIA-127] - Twiki module cannot parse two forced links in the
same paragraph
* [DOXIA-148] - FmlParser emits HTML specific events
* [DOXIA-152] - Xdoc parser shouldn't insert anchors for section titles
* [DOXIA-156] - XhtmlSink#tableCell( boolean headerRow, String
width ) uses a COLSPAN attribute instead of WIDTH attribute
* [DOXIA-157] - Doxia Book doesn't work with xdoc source files
* [DOXIA-160] - Book output in doc-book format is not well formed
* [DOXIA-161] - filename with dot have a false output name
* [DOXIA-162] - Failure to parse paragraph line with an EOL
* [DOXIA-166] - Book output ignores book, chapter and section titles
* [DOXIA-168] - Confluence module does not allow nested formatting
- e.g. a bullet cannot contain *bold* text or a [link]
* [DOXIA-169] - Confluence module does not recognize line breaks (\\)
* [DOXIA-171] - Confluence "quote" macro not recognised
* [DOXIA-173] - Support for Confluence anchor macro
* [DOXIA-175] - Confluence module does not recognise backslash as
escape character
* [DOXIA-176] - Confluence parser doesn't strip leading space for
section titles
* [DOXIA-177] - Invalid XHTML because of wrong position of table caption
* [DOXIA-178] - Confluence: nested wiki formats (e.g. bold italic)
do not work
* [DOXIA-180] - Confluence module should remove leading '#' from anchor link
* [DOXIA-181] - Confluence ParagraphBlockParser does not offer
lines to other parsers
* [DOXIA-182] - Confluence support for img macro
* [DOXIA-183] - Remove xhtml specific events from xdoc parser
* [DOXIA-189] - newline added after every closing tag
* [DOXIA-190] - text like (=something=) is parsed incorrectly
* [DOXIA-193] - forced url links where parsed as WikiWords links
* [DOXIA-201] -  tags are always parsed as macro parameters
* [DOXIA-212] - There is no way to include images using relative urls
* [DOXIA-215] - Trailing spaces after table definition causes exception
* [DOXIA-216] - Linkcheck broken
* [DOXIA-221] - Fix ArrayIndexOutOfBoundsException in XhtmlBaseSink
* [DOXIA-222] - XhtmlBaseParser swallows significant whitespace
* [DOXIA-225] - DocBookParser swallows significant whitespace
* [DOXIA-227] - [regression] attributes stripped from img tags
* [DOXIA-230] - Review Doxia generation for Apt and Docbook
* [DOXIA-235] - Confluence parser doesn't strip leading spaces for
list items
* [DOXIA-240] - NPE when building documentation
* [DOXIA-241] - Xdoc/XhtmlBaseParser doesn't close sections properly
* [DOXIA-242] - Echo macro outputs internal params
* [DOXIA-246] - TOC macro: higher entries are ignored
* [DOXIA-247] - unable to parse document when the last character is '}'
* [DOXIA-250] - Xml parser should handle entities defined in doctype
* [DOXIA-251] - The AbstractXmlParser should take care of EOL
* [DOXIA-257] - APT local anchor / link doesn't work when there is
a whitespace in the anchor name
* [DOXIA-259] - Source code snippets are not indented automatically
* [DOXIA-261] - The Twiki noautolink is not used at all
* [DOXIA-270] - Review doxia-converter artefact to respect ASF rules
* [DOXIA-273] - Broken link in External Resources page
* [DOXIA-274] - Broken link in "What is Doxia?" page
* [DOXIA-291] - Wrong classid in SwfMacro
* [DOXIA-292] - Be sure to call tableRows(int[], boolean) to be
backward compatible with Doxia 1.0

** Improvement
* [DOXIA-78] - Doxia XDOC parser and XHTML renderer ignore
"rowspan" and "colspan" attributes for tables
* [DOXIA-137] - Add comments to sink API
* [DOXIA-142] - Allow snippet macro contents to be output as-is,
instead of verbatim
* [DOXIA-144] - Review signature methods
* [DOXIA-153] - HTML tags in twiki not rendered correctly
* [DOXIA-154] - Xdoc parser should recognize 

Re: Error getting reports from plugin:'org.apache.maven.plugins:maven-project-info-reports-plugin'

[Vincent Siveton]

Hi,

2009/3/4 Krishnamurthi, Venkat :
> Thanks for the response. I resolved this issue by disabling access to the 
> maven central plugin repo (http://repo1.maven.org/maven2/) and allowing my 
> local repo to use a older version of the plugin like 2.0.  Also, I'm 
> currently using maven 2.0.7. Is this issue resolved for higher versions?

AFAIK it is not an issue for 2.1 or 2.1.1

Cheers,

Vincent

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Error getting reports from plugin:'org.apache.maven.plugins:maven-project-info-reports-plugin'

[Vincent Siveton]

Hi

Weird issue... maven-reporting-impl is defined in the pom!

Several ideas:
- rerun with maven 2.0.10
- run mvn -up
- remove your local repo
- be sure that the pom/jar in your repo managers are valids.

Cheers,

Vincent

2009/3/4, Krishnamurthi, Venkat :
> Thanks for the response. This is the output with -e switch:
>
>  [INFO] Trace
>  org.apache.maven.lifecycle.LifecycleExecutionException: Error getting 
> reports from the plugin 
> 'org.apache.maven.plugins:maven-project-info-reports-plugin': Unable to find 
> the mojo 
> 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license' in 
> the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin'
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:694)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:642)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:517)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>  Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find 
> the mojo 
> 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license' in 
> the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin'
> at 
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:571)
> at 
> org.apache.maven.plugin.DefaultPluginManager.getReport(DefaultPluginManager.java:495)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:683)
> ... 18 more
>  Caused by: 
> org.codehaus.plexus.component.repository.exception.ComponentLookupException: 
> Unable to lookup component 
> 'org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license',
>  it could not be created
> at 
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335)
> at 
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
> at 
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:562)
> ... 20 more
>  Caused by: 
> org.codehaus.plexus.component.factory.ComponentInstantiationException: Could 
> not instanciate component: role: 'null', implementation: 
> 'org.apache.maven.report.projectinfo.LicenseReport'
> at 
> org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77)
> at 
> org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62)
> at 
> org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464)
> at 
> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93)
> at 
> org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:48)
> at 
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
> ... 22 more
>  Caused by: java.lang.NoClassDefFoundError: 
> org/apache/maven/reporting/AbstractMavenReport
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
> at 
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
> at java.net.URLClassLoader.defineCla

[ANN] Maven Project Info Reports Plugin 2.1.1 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Project
Info Reports Plugin, version 2.1.1.
This is a maintenance release due to MPIR-146.

This plugin is used to generate reports information about the project.

http://maven.apache.org/plugins/maven-project-info-reports-plugin

You should specify the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-project-info-reports-pluginn
 2.1.1


Release Notes - Maven 2.x Project Info Reports Plugin - Version 2.1.1

** Bug
* [MPIR-127] - Image close.gif not copy when performing site:stage
* [MPIR-131] - NPE in printArtifactsLocations() for blacklisted repo
* [MPIR-135] - NPE if license URL is not defined
* [MPIR-146] -
org.apache.maven.report.projectinfo.dependencies.Dependencies.mapArtifactFiles(DependencyNode,
Map) wreaks havoc upon artifacts file names

** Improvement
* [MPIR-140] - Add anchors to sections to be able to link them directly
* [MPIR-141] - "Release" french translation


Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Stylus Skin 1.1 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Site
Skin, version 1.1
http://maven.apache.org/skins/maven-stylus-skin

You should specify the version in your site.xml:


  ...
  
org.apache.maven.skins
maven-stylus-skin
1.1
  
  ...


Release Notes - Maven Skins - Version stylus-1.1

** Task
* [MSKINS-5] - Adds a privacy policy link as required by the board

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Recommendation for best format for Maven Documentation

[Vincent Siveton]

Hi Ahana,

- which Wiki? Doxia supports TWiki and confluence out-of-box.
- who are writing doc? APT/xdoc are meanly for dev (btw we have an
editor in m2e eclipse plugin).
- You could easily convert wiki+html to apt or xdoc via doxia-converter [1]
- if header/footer are on your all pages, you need to remove them first.

Cheers,

Vincent

[1] 
http://svn.apache.org/repos/asf/maven/doxia/doxia-tools/trunk/doxia-converter

2008/12/29, Ahana :
>
>  Hello Folks,
>
>  I need to move documentation from various formats like Wiki and HTML and
>  move it to Maven and generate a site as well as a book. Key requirements are
>  ease of use, cross-referencing, images, headers & footers. Could someone
>  with experience building something similar recommend the best format and
>  editing tools to do this?
>
>  Thanks,
>  A
>
> --
>  View this message in context: 
> http://www.nabble.com/Recommendation-for-best-format-for-Maven-Documentation-tp21199191p21199191.html
>  Sent from the Doxia - Users mailing list archive at Nabble.com.
>
>

Re: Custom Macro Problem

[Vincent Siveton]

try with maven-site-plugin

2008/12/22, dhallammail-apa...@yahoo.com :
> Hi Vincent,
>
>  It's added as a /project/dependencies/dependency.
>
>  I haven't got a plugin specified in my pom for any site work.  Just things 
> like maven-compiler-plugin.
>
>  I'm assuming what you are getting at is that I need to add the dependency to 
> the plugin.  Do you know which plugin?
>
>  Regards,
>
>  Dave
>
>
>
>
>  
>  From: Vincent Siveton 
>  To: doxia-us...@maven.apache.org
>  Sent: Monday, 22 December, 2008 14:39:02
>  Subject: Re: Custom Macro Problem
>
>
>  Did you add your macro dependency as an extension or a plugin
>  dependency in your pom?
>
>  Cheers,
>
>  Vincent
>
>  2008/12/22, dhallammail-apa...@yahoo.com :
>  > Hi,
>  >
>  >  I have a custom Macro that is bundled as part of a Maven jar build.  It 
> creates a jar file with the /META-INF/plexus/components.xml file in it and 
> all looks good.  The macro class javadoc has @plexus.component 
> role="org.apache.maven.doxia.macro.Macro" role-hint="source" in it.
>  >
>  >  I have another Maven project that needs to use that macro in some xdoc.  
> I have had the built-in snippet macro working but can't get my custom one to 
> work.
>  >
>  >  I have added the jar containing the components.xml and macro as a 
> dependency to the other project but in site:site I'm just getting the trace 
> below.
>  >
>  >  Any ideas - I'm sure it's really simple.
>  >
>  >  Many thanks,
>  >
>  >  Dave
>  >
>  >  [ERROR] Error parsing xx\logging\src\site\xdoc\doc.xml: line [-1] 
> Macro execution failed: Macro not found: source
>  >  org.apache.maven.doxia.parser.ParseException: Macro execution failed: 
> Macro not found: source
>  > at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:61)
>  > at 
> org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:99)
>  > at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:59)
>  > at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:342)
>  > at 
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:46)
>  > at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
>  > at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
>  > at 
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129)
>  > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
>  > at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
>  > at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
>  > at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
>  > at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
>  > at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
>  > at 
> org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
>  > at 
> org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
>  > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
>  > at 
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
>  > at 
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
>  > at 
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
>  > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
>  > at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
>  > at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
>  >  Caused by: org.apache.maven.doxia.macro.MacroExecutionException: Macro 
> not found: source
>  > at 
> org.apache.maven.doxia.module.xdoc.XdocParser.handleEndTag(XdocParser.java:481)
>  > at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:92)
>  > at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:53)
>  > ... 22 more
>  >  Caused by: org.apache.maven.doxia.macro.manager.MacroNotFoundException: 
> Cannot find macro with id = source
>  > at 
> org.apache.maven.doxia.macro.manager.DefaultMacroManager.getMacro(DefaultMacroManager.java:48)
>  > at 
> org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:69)
>  > at 
> org.apache.maven.doxia.module.xdoc.XdocParser.handleEndTag(XdocParser.java:477)
>  >
>  >
>  >
>  >
>
>
>
>

Re: Custom Macro Problem

[Vincent Siveton]

Did you add your macro dependency as an extension or a plugin
dependency in your pom?

Cheers,

Vincent

2008/12/22, dhallammail-apa...@yahoo.com :
> Hi,
>
>  I have a custom Macro that is bundled as part of a Maven jar build.  It 
> creates a jar file with the /META-INF/plexus/components.xml file in it and 
> all looks good.  The macro class javadoc has @plexus.component 
> role="org.apache.maven.doxia.macro.Macro" role-hint="source" in it.
>
>  I have another Maven project that needs to use that macro in some xdoc.  I 
> have had the built-in snippet macro working but can't get my custom one to 
> work.
>
>  I have added the jar containing the components.xml and macro as a dependency 
> to the other project but in site:site I'm just getting the trace below.
>
>  Any ideas - I'm sure it's really simple.
>
>  Many thanks,
>
>  Dave
>
>  [ERROR] Error parsing xx\logging\src\site\xdoc\doc.xml: line [-1] Macro 
> execution failed: Macro not found: source
>  org.apache.maven.doxia.parser.ParseException: Macro execution failed: Macro 
> not found: source
> at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:61)
> at org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:99)
> at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:59)
> at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:342)
> at 
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:46)
> at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
> at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
> at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
> at 
> org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
> at 
> org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
> at 
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
> at 
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
> at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
>  Caused by: org.apache.maven.doxia.macro.MacroExecutionException: Macro not 
> found: source
> at 
> org.apache.maven.doxia.module.xdoc.XdocParser.handleEndTag(XdocParser.java:481)
> at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:92)
> at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:53)
> ... 22 more
>  Caused by: org.apache.maven.doxia.macro.manager.MacroNotFoundException: 
> Cannot find macro with id = source
> at 
> org.apache.maven.doxia.macro.manager.DefaultMacroManager.getMacro(DefaultMacroManager.java:48)
> at 
> org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:69)
> at 
> org.apache.maven.doxia.module.xdoc.XdocParser.handleEndTag(XdocParser.java:477)
>
>
>
>

New namespaces for Maven Settings and Profiles XSD

[Vincent Siveton]

FYI, the Maven team fixed the namespaces for settings and profiles XSD
(due to MNG-2636 and MNG-3907).
So, for instance, you need to use the following:
http://maven.apache.org/SETTINGS/1.0.0";
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
  http://maven.apache.org/xsd/settings-1.0.0.xsd";>
  ...


Have a glance to this url for other xsd:
http://maven.apache.org/xsd

Thanks,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Help Plugin 2.1 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Help
Plugin, version 2.1

The Maven Help plugin provides goals aimed at helping to make sense
out of the build environment. It includes the ability to view the
effective POM and settings files, after inheritance and active
profiles have been applied, as well as a describe a particular plugin
goal to give usage information.

http://maven.apache.org/plugins/maven-help-plugin/

You should specify the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-help-plugin
 2.1



Release Notes - Maven 2.x Help Plugin - Version 2.1

** Bug
* [MPH-42] - Active profiles recursively growing
* [MPH-49] - help:describe no-arg error doesn't mention "cmd"
* [MPH-50] - "mvn help:describe -Dcmd=compiler:compile" describes
entire plugin, not the specific mojo
* [MPH-51] - "help:help -Ddetail" looks better than "help:describe
-Dplugin=help -Dfull"
* [MPH-52] - help:describe never shows "Default Value"

** Improvement
* [MPH-15] - help:describe should accept plugin prefix or prefix:goal
* [MPH-26] - New goal help:help to provide help on how to use
helper plugins in maven
* [MPH-29] - help:describe should be way more helpful when no
arguments are provided
* [MPH-32] - "medium" mode should be the default for help:describe
* [MPH-33] - Help plugin should refer to "goal" not "mojo"
* [MPH-35] - Make -Dfull more discoverable by suggesting it
* [MPH-37] - help:effective-pom - sort the properties list
* [MPH-40] - help:effective-pom emits invalid XML to output file
* [MPH-44] - Hide passwords for effective-settings
* [MPH-46] - Improve the output of help:describe
* [MPH-54] - -Dhelp:describe -Ddetail should not show component requirements

** New Feature
* [MPH-4] - add mojo to projecthelp to describe supported plugin
parameter expressions
* [MPH-12] - Create a Mojo to list all Profiles for a Project
(even those loaded from an external profiles.xml)
* [MPH-28] - New goal to list platform details
* [MPH-30] - help:describe should accept "cmd" argument
* [MPH-47] - Add a new goal to evaluate Maven expressions given by a user

** Task
* [MPH-43] - Create an abstract Help Mojo with output  parameter
* [MPH-48] - Review dependencies

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: dependency tree but for build/reporting plugins

[Vincent Siveton]

Hi

2008/8/27 Giovanni Azua <[EMAIL PROTECTED]>:
> Hi Dennis,
>
> I swept my local repo first and then ran the build as you recommended using
> the -X option.
>
> These are all the doxia versions that end up being downloaded into my local
> repo:
> 1.0-alpha-7

maven-reporting-api-2.0.5 uses doxia-api 1.0-alpha-7

> 1.0-alpha-8

given from findbugs-maven-plugin

> 1.0-alpha-9

from maven-changes-plugin

> 1.0-alpha-10
> 1.0-alpha-11

from site plugin

HTH

Vincent

> But from the build log alone I can't figure out why the e.g. 1.0-alpha-10
> gets pulled. I added the build.log output file for this last build tentative
> and would appreciate enormously if you could have a look at it to see why
> the non 11 doxia versions get downloaded and further how to fix this:
>  ld.log>
>
> My parent pom is under:
>  .xml?view=markup>
>
> TIA,
> Regards,
> Giovanni
>
>
>> -Original Message-
>> From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
>> Sent: Sunday, August 24, 2008 8:17 PM
>> To: Maven Users List
>> Subject: Re: dependency tree but for build/reporting plugins
>>
>> Run Maven with the -X command line switch to reveal all dependencies and
>> how they are pulled in.
>>
>
>
>
>
> -
> 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: [ANN] Maven Javadoc Plugin 2.5 Released

[Vincent Siveton]

Hi Peter,

Verify that you defined the correct javadoc plugin version in your poms.
http://maven.apache.org/plugins/maven-javadoc-plugin/plugin-info.html

You could also run
mvn help:effective-pom

HTH

Cheers,

Vincent

2008/8/28 Peter Horlock <[EMAIL PROTECTED]>:
> Unfortunately, 2.5 doesn't work for me.
>
> Eventhough I can find it when I manually browse the Central Repo,
> my Maven 2 version can't find it. I assume that someone forgot to update
> those additional xml files telling with versions are hosted by the server. I
> manually downloaded the javadoc 2.5 jar, but then Maven complains about a
> Plexus version missing, and so on...
>
> Peter
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANN] Maven Javadoc Plugin 2.5 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Javadoc
Plugin, version 2.5

The Maven Javadoc Plugin is a plugin that uses the javadoc tool for
generating javadocs for the specified project.

http://maven.apache.org/plugins/maven-javadoc-plugin/

You should specify the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-javadoc-plugin
 2.5


Release Notes - Maven 2.x Javadoc Plugin - Version 2.5

** Bug
* [MJAVADOC-138] - javadoc:test-javadoc failed if target/classes
not already created
* [MJAVADOC-144] - Cannot generate Javadoc on Mac OS X if path
contains space characters
* [MJAVADOC-162] - javadocExecutable unusable
* [MJAVADOC-168] - Regression: 2.4-SNAPSHOT does not generate docs
for generates sources if run outside a build
* [MJAVADOC-178] - Transitive Dependencies to Taglet Artifacts are
not resolved nor added to the classpath
* [MJAVADOC-180] - aggregation doesn't work for test-javadoc goal
* [MJAVADOC-183] - Aggregate javadoc does not process the
src/main/javadoc directories
* [MJAVADOC-187] - Javadoc jar manifest should contain
Specification and Implementation details
* [MJAVADOC-188] - -top command line argument is passed even when
java version is <1.6, generating a warning
* [MJAVADOC-190] - Javadoc tool -excludedocfilessubdir has no effect
* [MJAVADOC-194] - javadoc 2.4 does not [build-helper:add-source
{execution: add-source}] when aggregating a javadoc for a project
* [MJAVADOC-198] - AbstractJavadocMojo#getClasspath(..) should use
subProject's managedVersionMap
* [MJAVADOC-201] - Links parameter should handle relative links
* [MJAVADOC-210] - Unit tests fail on OS X
* [MJAVADOC-212] -
AggregatorJavadocReport/AggregatorTestJavadocReport are used by
default in aggregator and no reports are generated

** Improvement
* [MJAVADOC-78] - Add a flag to provide standard doclet parameters
to custom ones too
* [MJAVADOC-182] - use ${project.build.sourceEncoding} as default
value for "encoding" parameter
* [MJAVADOC-189] - Allow skipping of javadoc generation
* [MJAVADOC-192] - Bump to a new release of Doxia
* [MJAVADOC-193] - Bump plexus-utils to 1.5.1
* [MJAVADOC-196] - Create AggregatorJavadocMojo similar to
AggregatorSourceJarMojo
* [MJAVADOC-197] - Provide flag to ignore errors
* [MJAVADOC-202] - Links ../apidocs from javadoc:javadoc to
javadoc:test-javadoc
* [MJAVADOC-203] - Test report should have its own config

** New Feature
* [MJAVADOC-191] - Add a new Mojo for test-jar
* [MJAVADOC-204] - Have a way to auto detect tagletClass from a
given tagletArtifact
* [MJAVADOC-206] - use ${project.reporting.outputEncoding} as
default value for "docencoding" and "charset" parameter and default to
UTF-8
* [MJAVADOC-208] - Added bootclasspath javadoc option
* [MJAVADOC-209] - Exclude debug files for javadoc:jar goal

** Task
* [MJAVADOC-199] - Upgrade to plexus-utils:1.5.5


** Wish
* [MJAVADOC-126] - Add the ability to load the stylesheet from a
jar (resource)
* [MJAVADOC-185] - Revert MJAVADOC-165 and default to platform encoding

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANN] Maven Plugin Tools 2.4.3 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Plugin
Tools, version 2.4.3

The Maven Plugin Tools contains the necessary tools to be able to
produce Maven Plugins in a variety of languages.

http://maven.apache.org/plugin-tools
http://maven.apache.org/plugins/maven-plugin-plugin

Release Notes - Maven 2.x Plugin Tools - Version 2.4.3

** Sub-task
* [MPLUGIN-134] - Review the support of Mojo's annotations

** Bug
* [MPLUGIN-26] - Parsing issue due to qdox regression
* [MPLUGIN-126] - Report mojo outputs XDoc into wrong directory if
outputDirectory parameter is overriden with a relative path
* [MPLUGIN-130] - PluginDescriptorGenerator doesn't write
deprecated tag for a mojo
* [MPLUGIN-131] - PluginXdocGenerator doesn't handle correctly the
Resource bundles and make typo in some languages
* [MPLUGIN-133] - JavaMojoDescriptorExtractor doesn't handle @requiresReport

** Improvement
* [MPLUGIN-125] - Add deprecation messages to output of help mojo
* [MPLUGIN-128] - Add a line break before writing default value in
description field
* [MPLUGIN-129] - Avoid generation of emtpy plugin report for POM projects
* [MPLUGIN-132] - Don't encourage users to use "mvn -up" to update plugins

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANN] Maven DOAP Plugin 1.0 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven DOAP
Plugin, version 1.0.

This plugin generates a Description of a Project (DOAP) file from
information in a POM.

http://maven.apache.org/plugins/maven-doap-plugin/

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-doap-plugin
 1.0


Release Notes - Maven 2.x DOAP Plugin - Version 1.0

** Bug
* [MDOAP-6] - Support more repositories
* [MDOAP-13] - 'Examples' section on 'Introduction' page contains
a broken link.

** Improvement
* [MDOAP-1] - DOAP Plugin should support setting of shortdesc and
pmc and the about default should be
http://${project.artifactId}.rdf.apache.org
* [MDOAP-8] - ASF namespace is always include
* [MDOAP-9] - Support more DOAP resource like wikis
* [MDOAP-10] - Supports more DOAP roles for developers/contributors
* [MDOAP-12] - Take care of the xml:lang

** New Feature
* [MDOAP-4] - Handle versions

** Task
* [MDOAP-7] - Add test code
* [MDOAP-14] - Review and update site documentation

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANN] Maven Project Info Reports Plugin 2.1 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Project
Info Reports Plugin, version 2.1

This plugin generates standard reports for the specified project.

http://maven.apache.org/plugins/maven-project-info-reports-plugin/

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-project-info-reports-plugin
 2.1


Release Notes - Maven 2.x Project Info Reports Plugin - Version 2.1

** Sub-task
* [MPIR-126] - Move PluginManagementRenderer in an inner class of
PluginManagementReport

** Bug
* [MPIR-48] - Internal html references are not generated in the
team-list.html
* [MPIR-49] - team-list.html is not correctly generated when table
is to large
* [MPIR-52] - Wrong text on scm page for svn protocol
* [MPIR-53] - there is no info about project-info-reports:summary
in documentation
* [MPIR-57] - URLs only link if they are FQDNs
* [MPIR-59] - Site generation exception for french language, error
with simple quote in  translation "S'inscrire" for mailing list
* [MPIR-60] - Current head throws NPE when generating reports
* [MPIR-65] - Direct report generation breaks on skin version even
though it is specified
* [MPIR-66] - When run standalone, project metadata is missing
* [MPIR-70] - NullPointerException when generating Dependencies report
* [MPIR-75] - Typing mistake in properties file
* [MPIR-76] - Dependencies report is incorrect
* [MPIR-79] - Add explicit resource bundle for English
* [MPIR-81] - DependenciesRenderer logs Exception when it can't
find the artifact being built!!!
* [MPIR-84] - StringIndexOutOfBoundsException when ML archive dont
finish with a /
* [MPIR-89] - Bad spelling in Project Information => Overview =>
Dependencies
* [MPIR-90] - Bad style in text "Access from behind a firewall"
* [MPIR-91] - Bad spelling in text "Access through a proxy"
* [MPIR-92] - Wrong encoding in german properties
* [MPIR-96] - Switched link text and target in license report
* [MPIR-98] - Team list does not contain anchors on user ids
* [MPIR-99] - Strange warnings when generating Plugin Management report
* [MPIR-104] - Regression in 2.1-SNAPSHOT: SVN is no more recognized
* [MPIR-106] - Regression in 2.1-SNAPSHOT, the  Project
Dependencies and the Project Transitive Dependencies are the same
* [MPIR-109] - Wrong description of in source repository overview
* [MPIR-119] - Dependency Repository Locations in Dependency
Report doesn't allow snapshot artifacts url from the snapshot
repositories
* [MPIR-122] - Brazilian Portuguese language bundle - encoding
problems and improvements
* [MPIR-123] - Hungarian language bundle - encoding problems and
improvements
* [MPIR-124] - License report is empty in offline
* [MPIR-129] - Duplicate entries of the same artifact in Licenses
section of Dependencies report
* [MPIR-130] - No mark or link to SNAPSHOT artifacts in Dependency
Repository Locations section of Dependencies report

** Improvement
* [MPIR-28] - improve convergence report
* [MPIR-46] - Sample reports are out of date
* [MPIR-47] - Dependency Report does not show origin of transitive
dependency
* [MPIR-54] - Team list table improvement
* [MPIR-56] - Refactor the dependencies report
* [MPIR-58] - The sandbox component Jar has been renamed to JarAnalyzer
* [MPIR-61] - [PATCH] Updated CI Systems
* [MPIR-62] - [PATCH] Dependency File Details : set right
justification for numeric columns
* [MPIR-64] - Korean translation resource file
* [MPIR-67] - Please update the german localization.
* [MPIR-69] - add anchors for developers
* [MPIR-72] - Upgrade to doxia 1.0-alpha-9
* [MPIR-82] - Clarify usage of outputDirectory parameter
* [MPIR-87] - Show repositories an artifact is deployed to as a report
* [MPIR-94] - Change optional label in dependencies site
* [MPIR-108] - Add validation of SCM urls
* [MPIR-110] - Update code due to deprecated classes in
maven-dependency-tree:1.1
* [MPIR-111] - Make Classifier and Optional column in dependencies
report "optional" in the renderer
* [MPIR-112] - Dependency Listings is too big: replace it by
toogle entries in the dependency tree
* [MPIR-113] - Dependency Tree lists all dependencies: needs to
reduce to dependencies used by the project
* [MPIR-115] - Make the Sealed column optional in dependencies report
* [MPIR-116] - Make the classifier column optional in dependencies
management report
* [MPIR-117] - Replaced the table caption in the CI report
* [MPIR-118] - Equalize links to project web site for artifactId
* [MPIR-125] - Create a plugin report

** New Feature
* [MPIR-26] - Could the Dependencies report show the size of the jars/etc...
* [MPIR-55] - Detailed Artifact Information & Repository Location
for each Dependency.
* [MPIR-63] - 

[ANN] Maven Plugin Testing 1.2 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Plugin
Testing, version 1.2

The Maven Plugin Testing contains the necessary modules to be able to
test Maven Plugins.

http://maven.apache.org/plugin-testing/

Note: This release changes the groupId for the artifacts.

You can specify the version in your project's dependency
configuration, for instance:


  org.apache.maven.plugin-testing
  maven-plugin-testing-harness
  1.2
  test


Enjoy,

-The Maven team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Conficuring dependency for com.sun.javadoc and com.sun.tools.doclet

[Vincent Siveton]

Please, don't send twice.

http://maven.apache.org/users/getting-help.html
Specifically, read the references

Cheers,

Vincent

2008/6/4, Niranjan Deshpande <[EMAIL PROTECTED]>:
> My application needs the Tag and Taglets class when it is compiled.
>  These classes are provided in JDKs tools.jar file.
>
>  Since this has not been configured in my POM, I am getting this error:
>
>  package com.sun.tools.doclets does not exist
>
>  How do i add this dependecny to the POM? AS per my understanding this is a
>  provided dependency (a dependency that is used to compile the application
>  but will not be deployed. This scope provided is used for a dependency when
>  we expect the JDK or the application server to provide the JAR)
>
>  Please help.
>
>
>
>  --
>  Regards,
>  Niranjan Deshpande
>
>  "Shut yourself from the world and create the reality you want"
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANN] Maven Ant Plugin 2.1 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Ant
Plugin, version 2.1

This plugin generates Ant  build files for Ant 1.6.2 or above.

http://maven.apache.org/plugins/maven-ant-plugin/

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-ant-plugin
 2.1


Release Notes - Maven 2.x Ant Plugin - Version 2.1

** Bug
* [MANT-4] - Generated ANT contains hardcoded "get" tasks that
look at the "C:\" drive etc... when using a local repository
* [MANT-30] - classcast exception when running ant:ant on
tagtraum.com's gcviewer project
* [MANT-32] - java.lang.ClassCastException when packaging jeuclid-3.0.1
* [MANT-34] - The generated maven-build.xml and
maven-build.properties contains absolute path to local repository
* [MANT-35] - The generated maven-build.xml has paths that contain
\ characters on Windows
* [MANT-36] - Use correct file encoding when writing build files
* [MANT-37] - Wrong path to test resources in maven-build.xml
* [MANT-39] - Always specify source/target options for javac

** Improvement
* [MANT-6] - "test" targets should fail if junit.jar not present
* [MANT-7] - "test" target should support running a single test -
just like mvn test does
* [MANT-22] - Make it possible to run the package target without tests
* [MANT-38] - Use reporting output directory configured in POM
* [MANT-40] - Use includes/excludes configured for Surefire when
running tests

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANN] Maven Doxia Integration Tools 1.0 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Doxia
Integration Tools, version 1.0. It is a collection of tools to help
the integration of Doxia in Maven plugins.

http://maven.apache.org/shared/maven-doxia-tools

You can specify the version in your project's dependency configuration:


  org.apache.maven.shared
  maven-doxia-tools
  1.0


Enjoy,

-The Maven team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven pde rcp to build

[Vincent Siveton]

Hi,

Have a look on Carlos's blog
http://www.jroller.com/carlossg/entry/slides_from_eclipsecon

Cheers,

Vincent

2008/4/21  <[EMAIL PROTECTED]>:
> I have been looking for a while for this solution.
>
>  Has anyone been able to run this tutorial to complete?
>
>  http://mojo.codehaus.org/pde-maven-plugin/examples/simple_product.html
>
>  I have looked through many emails just to get the project to build in maven
>  with Eclipse 3.3.2 as target.
>
>  Now I am at a point where it builds with 0 errors. I had to change the
>  pom.xml packaging setting from ZIP to  JAR.
>
>  So I tried to run it from the dos with:  *java -jar
>  simple_application-1.0-SNAPSHOT.jar
>  *
>  I get nothing. No errors, no failure,. nothing!
>
>  Here is my pom.xml;
>  http://maven.apache.org/POM/4.0.0";
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>  http://maven.apache.org/maven-v4_0_0.xsd";>
>   4.0.0
>   test.pde_maven_plugin
>   simple_application
>   jar
>   Simple Plugin PDE Example
>   1.0-SNAPSHOT
>   A Simple Plugin PDE Example
>   
> 
>   
> org.codehaus.mojo
> pde-maven-plugin
> true
> 
>   C:\Program
>  Files\JavaWorkEnv\eclipse
>   simple_product.product
>   3.3.2.v20071019
> 
>   
> 
>   
>  
>
>
>  Any leads to get this to run from dos as jar or how to get the zip packaging
>  setting to build?
>
>  Here is the error if I have zip as packaging setting.
>
>  >mvn install
>  [INFO] Scanning for projects...
>  [INFO]
>  
>  [INFO] Building Simple Plugin PDE Example
>  [INFO]task-segment: [install]
>  [INFO]
>  
>  [INFO] [pde:ext]
>  [INFO]
>  
>  [ERROR] BUILD ERROR
>  [INFO]
>  
>  [INFO] C:\Program Files\JavaWorkEnv\eclipse\startup.jar not found.  Have you
>  set up your -DeclipseInstall?
>  [INFO]
>  
>  [INFO] For more information, run Maven with the -e switch
>  [INFO]
>  
>  [INFO] Total time: 2 seconds
>  [INFO] Finished at: Mon Apr 21 12:12:30 CDT 2008
>  [INFO] Final Memory: 3M/8M
>  [INFO]
>  
>
>  Thanks
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANN] Maven Plugin Tools 2.4 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Plugin
Tools, version 2.4

The Maven Plugin Tools contains the necessary tools to be able to
produce Maven Plugins in a variety of languages.

Maven Plugin:
http://maven.apache.org/plugins/maven-plugin-plugin/

Maven Plugin Tools:
http://maven.apache.org/plugin-tools/maven-plugin-tools-ant/
http://maven.apache.org/plugin-tools/maven-plugin-tools-api/
http://maven.apache.org/plugin-tools/maven-plugin-tools-beanshell/
http://maven.apache.org/plugin-tools/maven-plugin-tools-java/
http://maven.apache.org/plugin-tools/maven-plugin-tools-javadoc/
http://maven.apache.org/plugin-tools/maven-plugin-tools-model/

Note: the groupId of tools becomes org.apache.maven.plugin-tools.

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:
http://maven.apache.org/plugins/maven-plugin-plugin/plugin-info.html

Release Notes - Maven 2.x Plugin Tools - Version 2.4

** Sub-task
* [MPLUGIN-66] - Add unit test

** Bug
* [MPLUGIN-28] - Error of goal value in Plugin documentation generation
* [MPLUGIN-30] - dependency:analyze shows errors
* [MPLUGIN-35] - Generated documentation for @phase is misleading
* [MPLUGIN-43] - Adding validation in PluginXdocGenerator class?
* [MPLUGIN-45] - Plugin dependencies are not put in generated plugin.xml
* [MPLUGIN-46] - [maven-plugin-testing-harness-1.0-beta-1]
AbstractMojoTestCase.extractPluginConfiguration expects plugin
configuration directly under plugin (configuration under
executions/execution doesn't work)
* [MPLUGIN-58] - File Parameter Evaluation
* [MPLUGIN-59] - [maven-plugin-testing-harness] Clean the code
* [MPLUGIN-60] - MavenProjectStub uses immutable collections for
modifiable data
* [MPLUGIN-62] - Exclude read-only components from plugin goal documentation
* [MPLUGIN-65] - [PATCH] NPE in PluginXDocGenerator while creating
plugin site
* [MPLUGIN-71] - Make JavaMojoDescriptorExtractor extract
class-level deprecated tag
* [MPLUGIN-73] - PluginXdocGenerator fails to decode javadoc inline tags
* [MPLUGIN-76] - Fixed file encoding employed by PluginXDocGenerator
* [MPLUGIN-78] - Fix german localization
* [MPLUGIN-79] - Fix detection of JDK requirement
* [MPLUGIN-80] - Detection of report goals always fails due to
class loader separation
* [MPLUGIN-83] - POM snippet for plugin usage via pluginManagement
is missing  container
* [MPLUGIN-85] - Add missing whitespace between words on mojo
description page
* [MPLUGIN-86] - Test for empty mojo description in XDoc generator
does not cover empty string
* [MPLUGIN-88] - Fix punctuation for description of mojo attributes
* [MPLUGIN-91] - misleading icon on list of goals

** Improvement
* [MPLUGIN-11] - add an introduction to plugin configuration in
plugin report
* [MPLUGIN-13] - Provide Automated Documentation for a Plugin That
Provides a Report
* [MPLUGIN-38] - Upgrade to doxia 1.0-alpha-9
* [MPLUGIN-53] - Plugin descriptor extractor crashes on certain
types of Java source files
* [MPLUGIN-63] - Add since column in the parameters table
* [MPLUGIN-64] - Beanshell extractor does not handle parameter default value
* [MPLUGIN-67] - Document somewhere the minimum version of maven
required by the plugin
* [MPLUGIN-68] - Make generated mojo description valid XHTML
* [MPLUGIN-70] - Make plugin highlight deprecated goals in the
plugin overview
* [MPLUGIN-72] - Add german translation
* [MPLUGIN-75] - Internationalize PluginXdocGenerator
* [MPLUGIN-77] - Add german translation
* [MPLUGIN-87] - Replace "None" with something that is better
understandable without context
* [MPLUGIN-90] - Refactor makeValidHtml into PluginUtils for better reusage

** New Feature
* [MPLUGIN-40] - All plugins should by default have an
auto-generated goal 'help'
* [MPLUGIN-81] - Handle Mojo annotations as Javadoc taglets to
make better javadoc

** Task
* [MPLUGIN-69] - Be consistent about physical/logical formatting tags
* [MPLUGIN-74] - Explicitly control layout of tables generated for
parameters of mojo description
* [MPLUGIN-82] - Fix test for javadoc tools
* [MPLUGIN-84] - Update to Plexus Utils 1.5+
* [MPLUGIN-89] - Restore compat with Java 1.4

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven-javadoc-plugin 2.4 missing

[Vincent Siveton]

Hi

The release process started yesterday on [EMAIL PROTECTED] Just waiting for.

Cheers,

Vincent

2008/3/10, Julien Graglia <[EMAIL PROTECTED]>:
> The project summary (1) announce version 2.4, the SVN tag is present,
>  but I can't find the plugin in ibiblio (2) or repo1 (3).
>
>  This version is quite young : site generated march 08, svn tag created
>  38 hours ago.
>  Is it too early for v2.4?
>
>  1 :
>  http://maven.apache.org/plugins/maven-javadoc-plugin/project-summary.html
>  2 :
>  
> http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/maven/plugins/maven-javadoc-plugin/
>  3 :
>  http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-javadoc-plugin/
>
>
>  --
>  Julien Graglia
>
>
>
>  -
>  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: OutOfMemoryError when running javadoc:javadoc

[Vincent Siveton]

Hi Ryan

My guess is that you need to increase the memory.

Cheers,

Vincent

2008/1/29, Ryan H. <[EMAIL PROTECTED]>:
> Hello,
>
> I'm getting OutOfMeoryError when running javadoc:javadoc to generate an
> aggregated javadoc for multiple projects, even given with these options. Any
> solution to this problem?
>
> 512
>
> 1024
>
> Thanks
>
> Ryan
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Javadoc:jar error: Not executing Javadoc as the project is not a Java classpath-capable package

[Vincent Siveton]

Hi Ryan,

What is your packaging type of your project (or subprojects)? It seems
it is not a java one.

Cheers,

Vincent

2008/1/29, Ryan H. <[EMAIL PROTECTED]>:
> Hello,
>
> Anyone knows what this javadoc:jar complains about? I'm able to run
> javadoc:javadoc in "aggregate" mode (ie. generate only one report for
> all multiple projects). However, when I run javadoc:jar, it starts
> complaining it ...
>
> [INFO] [javadoc:jar]
> [INFO] Not executing Javadoc as the project is not a Java classpath-capable
> package
>
> Thanks
> Ryan
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Copyright Symbol broken in Javadoc

[Vincent Siveton]

Hi Jochen,

The bottom uses © for the copyright. So I guess UTF-8 is used in
command line.

Cheers,

Vincent

2008/1/19, Jochen Wiedmann <[EMAIL PROTECTED]>:
> Hi,
>
> if you have a look at
>
> 
> http://people.apache.org/~jochen/commons-fileupload/site/apidocs/index.html
>
> then you'll find that the copyright symbol at the page bottom is
> broken. Does anyone have an explanation for that? I did not do any
> configuration on the javadoc plugin, apart from specifying 2.3.
>
> Jochen
>
>
> --
> Look, that's why there's rules, understand? So that you think before
> you break 'em.
>
> -- (Terry Pratchett, Thief of Time)
>
> -
> 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: [ANN] Maven PMD Plugin 2.3 Released

[Vincent Siveton]

hehe :)

Vincent

2008/1/8, Dan Tran <[EMAIL PROTECTED]>:
> Good work Dennis,
>
> what is next? javadoc plugin? :-)
>
>
>
> On Jan 8, 2008 12:55 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> > The Maven team is pleased to announce the release of Maven PMD
> > Plugin, version 2.3.
> >
> > http://maven.apache.org/plugins/maven-pmd-plugin/
> >
> > You can run 'mvn -up' to get the latest version of the plugin, or
> > specify the version in your project's plugin configuration:
> >
> > 
> >  org.apache.maven.plugins
> >  maven-pmd-plugin
> >  2.3
> > 
> >
> > Release Notes - Maven 2.x PMD Plugin - Version 2.3
> >
> > ** Bug
> > * [MPMD-55] - The Xml pmd file isn't encode to UTF8 charset counter
> > the charset declaration in the file header
> > * [MPMD-56] - targetJdk support for jdk 1.6
> > * [MPMD-57] - cpd: wrong symlink detection if relative source path
> > is used
> > * [MPMD-58] - sourceEncoding honoured with pmd but not cpd
> > * [MPMD-60] - @SuppressWarnings causes maven PMD plugin to fail on
> > building report
> > * [MPMD-66] - Support for jdk1.4 using new pmd-jdk14 artifact
> > * [MPMD-67] - Using JDK 1.6 causes ParseException: Can't use
> > generics unless running in JDK 1.5 mode!
> > * [MPMD-69] - line number is not displayed in pmd check report
> >
> > ** Improvement
> > * [MPMD-65] - Better error handling for PMDException
> >
> >
> > ** Task
> > * [MPMD-59] - Upgrade to PMD 4.1
> >
> >
> > Enjoy!
> >
> > - The Maven Team
> >
> >
> > -
> > 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]

[ANN] Maven Clean Plugin 2.2 for Maven 2 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Clean
Plugin, version 2.2.

http://maven.apache.org/plugins/maven-clean-plugin/

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-clean-plugin
 2.2


Release Notes - Maven 2.x Clean Plugin - Version 2.2

** Bug
* [MCLEAN-21] - Plugin Docu's index.html
* [MCLEAN-26] - Long pathnames on windows platforms cannot be deleted

** Improvement
* [MCLEAN-8] - conversion of the existing unit tests to use the
AbstractMojoTestCase from the plugin testing harness
* [MCLEAN-22] - Possibility to ignore deletion failures
* [MCLEAN-23] - Disable Clean plugin execution
* [MCLEAN-24] - Disable plugin execution
* [MCLEAN-27] - fileset directory does not work as expected when
cleaning "modules" in sub-directories

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: test timeout

[Vincent Siveton]

Hi Nico,

Try surefire.timeout from the snapshot (SUREFIRE-320)

Cheers,

Vincent

2007/12/3, nicolas de loof <[EMAIL PROTECTED]>:
> Is there any way to configure surefire plugin to stop the test JVM (in
> forkmode "once") after some timeout ?
>
> maven1 has the maven.junit.timeout, but I can't find in m2 doc some similar
> feature.
>
> Nico.
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Translation for Chinese Users

[Vincent Siveton]

Hi

Thanks for your help. Here is a first step that could help you
http://maven.apache.org/plugins/maven-site-plugin/i18n.html

Cheers,

Vincent

2007/11/23, Juven Xu <[EMAIL PROTECTED]>:
> Hi, guys:
>
>   I'm a maven user from China and I do the build work for my company which
> is in Shanghai.
>   Now I find that I've already been attracted by this powerful project
> management tool and I really want to do something to contribute.
>   So, how about letting me do some translation work for Chinese users?
> Anyone agree with me?
>   Thanks.
>
> Juven
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ISO-8859-1 -> "Invalid byte 2 of 3-byte UTF-8 sequence" error with Doxia (maven plugin)

[Vincent Siveton]

Hi Serge,

It is a known limitation in the iText plugin. The implementation uses
the deprecated itext xml and the xml encoding is hardcoded to utf-8

Cheers,

Vincent

[1] http://www.lowagie.com/iText/tutorial/ch07.html

2007/11/9, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>
> Hello,
> I'm trying to use the Doxia Maven plugin to automatically render .pdf from
> APT and i'm encountering this problem, does any of you have an idea about
> this ?
> The .apt files are encoded in ISO-8859-1 and contain various french
> characters (like accentued characters).
>
> I got the "Invalid byte 2 of 3-byte UTF-8 sequence." error and i really
> don't know how to deal with ISO-8859-1 with this plugin, what should I add
> and where ?
> I've tried to add in my pom.xml the  and 
> lines but the behaviour is just the same with or without.
>
> My Doxia "example.xml" file doesn't contain at this time any special
> characters.
> If i set the book configuration to point to plain .apt without any special
> characters only, everything works fine, but as soon as I have french
> national characters in the apt files, i get this error.
>
> I'm using (as far as i know) the last version of the plugin
> ("1.0-alpha-10").
>
> My POM looks like that :
> 
>   org.apache.maven.doxia
>   doxia-maven-plugin
>   1.0-alpha-10
>   
> 
>   pre-site
>   
> render-books
>   
> 
>   
>   
> iso-8859-1   
> iso-8859-1  
> 
>   
> site/
> pdf/example.xml
> 
>   
> pdf
>   
> 
>   
> 
>   
> 
>
> Result stacktrace :
>
> [INFO]
> 
> [ERROR] FATAL ERROR
> [INFO]
> 
> [INFO] Invalid byte 2 of 3-byte UTF-8 sequence.
> [INFO]
> 
> [INFO] Trace
> ExceptionConverter: org.xml.sax.SAXParseException: Invalid byte 2 of 3-byte
> UTF-8 sequence.
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1810)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
> at com.lowagie.text.xml.XmlParser.go(Unknown Source)
> at com.lowagie.text.xml.XmlParser.parse(Unknown Source)
> at com.lowagie.text.xml.XmlToXXX.parse(Unknown Source)
> at
> org.apache.maven.doxia.module.itext.ITextUtil.writePdf(ITextUtil.java:118)
> at
> org.apache.maven.doxia.book.services.renderer.PdfBookRenderer.renderXML(PdfBookRenderer.java:50)
> at
> org.apache.maven.doxia.book.services.renderer.AbstractITextBookRenderer.renderBook(AbstractITextBookRenderer.java:162)
> at
> org.apache.maven.doxia.book.DefaultBookDoxia.renderBook(DefaultBookDoxia.java:126)
> at
> org.apache.maven.doxia.plugin.DoxiaRenderBooksMojo.execute(DoxiaRenderBooksMojo.java:214)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lif

Re: [ANN] Maven NSIS Plugin 2.0 for Maven 1.x released

[Vincent Siveton]

Hi,

I already did it in the past :)
http://jira.codehaus.org/browse/MASSEMBLY-32

Cheers,

Vincent

2007/10/29, Arnaud HERITIER <[EMAIL PROTECTED]>:
> it should be something provided within the assembly plugin or an extension
> of it.
> I never had the time to rewrite it for maven 2 but it shouldn't be very
> difficult.
>
> Arnaud
>
> On 10/28/07, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> >
> >
> > If this is a frequent question then I have to review my message filter!
> > ;) I can't remember NSIS mentioned on a maven list since a long time.
> >
> > Anyway, I am not aware of any m2 plugin, but I am certainly not the
> > right person to ask since even for the m1 plugin, I only did one release
> > once but I never maintained it.
> >
> > Anyone else?
> >
> > -Lukas
> >
> >
> > Stefano Fornari wrote:
> > > Hi Lukas,
> > > maybe this is a frequent question, forgive me if it is such case (but
> > > I could not find any reference searching the list archive).
> > >
> > > Is there any work or plan for a NSIS plug-in for Maven2?
> > >
> > > Thanks in advance,
> > > Stefano
> > >
> > > On 7/28/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> > >
> > >>We are pleased to announce the Maven NSIS Plugin 2.0 release!
> > >>
> > >>http://maven.apache.org/maven-1.x/plugins/nsis/
> > >>
> > >>A plugin to generate Win32 installer programs using NSIS
> > >>
> >
> > >>===
> > >>
> > >>Changes in this version include:
> > >>
> > >>  New Features:
> > >>
> > >>o Add faq Thanks to Geoffrey.
> > >>
> > >>  Fixed bugs:
> > >>
> > >>o Use maven.nsis.build.dir instead of maven.dist.assembly.dir. Fixes
> > >>  MPNSIS-9. Thanks to Matthias Kerkhoff.
> > >>o Fail when makensis fails. Fixes MPNSIS-8. Thanks to Matthias Kerkhoff.
> > >>o Check maven.nsis.exe exists before using it. Thanks to Geoffrey.
> > >>
> > >>  Changes:
> > >>
> > >>o Rename ORGANIZATIONconstant to PROJECT_ORGANIZATION.
> > >>o Add back license to project.xml after the scm plugin removed it.
> > >>
> >
> > >>===
> > >>
> > >>
> > >>To automatically install the plugin, type the following on a single
> > line:
> > >>
> > >>maven plugin:download
> > >>  -Dmaven.repo.remote=http://www.ibiblio.org/maven,
> > http://people.apache.org/repo/m1-snapshot-repository/
> > >>  -DgroupId=maven
> > >>  -DartifactId=maven-nsis-plugin
> > >>  -Dversion=2.0
> > >>
> > >>For a manual installation, you can download the plugin here:
> > >>
> > http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-nsis-plugin-2.0.jar
> > >>
> > >>
> > >>Have fun!
> > >>-The Maven NSIS Plugin development team
> > >>
> > >>-
> > >>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]
> >
> >
>
>
> --
> ..
> Arnaud HERITIER
> ..
> OCTO Technology - aheritier AT octo DOT com
> www.octo.com | blog.octo.com
> ..
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problems using a customized javadoc plugin from custom repository

[Vincent Siveton]

Hi,

Try to remove your repo, specially:
${user.home}/.m2/repository/org/apache/maven/plugins/maven-javadoc-plugin

Cheers,

Vincent

2007/10/24, Dirk Olmes <[EMAIL PROTECTED]>:
> Hi,
>
> I'm trying to work around http://jira.codehaus.org/browse/MJAVADOC-157
> so I have checked out the maven-javadoc-plugin sources and tweaked it so
> it works for building my site. I have added the necessary into to deploy
> my patched m-j-p to my custom repo and deployed it.
>
> The site runs on our CI server which must be able to download the
> patched m-j-p from our custom repo. This works fine but when I run the
> site, I get the following error message:
>
> [INFO]
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Error getting reports from the plugin
> 'org.apache.maven.plugins:maven-javadoc-plugin': Unable to find the mojo
> 'org.apache.maven.plugins:maven-javadoc-plugin:2.4-MULE-586296:javadoc'
> in the plugin 'org.apache.maven.plugins:maven-javadoc-plugin'
> org/apache/maven/doxia/siterenderer/RendererException
>
> No, running with -X -e does not come up with any more helpful info either.
>
> I have searched the archive and found various threads with "unable to
> find the mojo" which generally seems to be solved by removing the plugin
> in question from the local repo. I did this and I even ran the build
> with a fresh local repo: the error remains the same.
>
> Any idea what could be wrong here?
>
> -dirk
>
> -
> 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: Java doc generation

[Vincent Siveton]

Hi Jerome,

Done right now.

Cheers,

Vincent

2007/10/22, Jerome Lacoste <[EMAIL PROTECTED]>:
> On 10/20/07, Vincent Siveton <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > The problems should be fixed in svn. Could you try again with a
> > SNAPSHOT version?
>
> Vincent,
>
> did you release a new snapshot after making those changes ?
>
> The last since to be from the 11th of Octover:
>
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-javadoc-plugin/2.4-SNAPSHOT/
>
> (and I am now seeing MJAVADOC-156 on my projects)
>
> Cheers,
>
> jerome
>
> -
> 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: Please release wagon-ftp

[Vincent Siveton]

Hi Julien,

Ask it on dev@

Thanks,

Vincent

2007/10/11, Julien HENRY <[EMAIL PROTECTED]>:
> Hi,
>
> Could you please release a new version of wagon-ftp. I
> really need WAGONFTP-7 for deploying site.
>
> Thanks
>
> Julien
>
>
>   
> _
> Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail
>
> -
> 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: Java doc generation

[Vincent Siveton]

Hi,

The problems should be fixed in svn. Could you try again with a
SNAPSHOT version?

Cheers,

Vincent

2007/10/17, Sinduria,Anuradha <[EMAIL PROTECTED]>:
> Hi,
>
> Thanks for your reply, actually I did not able to understand what you want
> to convey, If possible please elaborate how to resolve this.
>
> I now added javadoc version inside configuration, but it is still giving the
> same error.
>
> 
> org.apache.maven.plugins
> maven-javadoc-plugin
> 
>  
>  1.5
> 
>
>
>
>
> Thanks and Regards,
> Anuradha Sinduria
>
>
> -Original Message-
> From: Tim Kettler [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 16, 2007 6:55 PM
> To: Maven Users List
> Subject: Re: Java doc generation
>
> The plugin executes 'javadoc -J-fullversion' to retrieve the version of
> the javadoc tool and expects output like this:
>
>   java full version "1.5.0_11-b03"
>
>
> See here for reference [1]. Can you try if your javadoc prints the
> version information in some other format.
>
> -Tim
>
> [1]
> https://svn.apache.org/repos/asf/maven/plugins/tags/maven-javadoc-plugin-2.3
> /src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
>
> Sinduria,Anuradha schrieb:
> > I created a symbolic link, java doc generation started but it got stuck
> and
> > generated this error
> >
> >
> > [INFO] Generate "JavaDocs" report.
> > [INFO]
> > 
> > [ERROR] FATAL ERROR
> > [INFO]
> > 
> > [INFO] For input string: "dial"
> > [INFO]
> > 
> > [INFO] Trace
> > java.lang.NumberFormatException: For input string: "dial"
> > at
> > sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1224)
> > at java.lang.Float.parseFloat(Float.java:394)
> > at
> >
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.getJavadocVersion(Abstra
> > ctJavadocMojo.java:2966)
> > at
> >
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJa
> > vadocMojo.java:1085)
> > at
> >
> org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:13
> > 1)
> > at
> >
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDo
> > cumentRenderer.java:67)
> > at
> >
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Default
> > SiteRenderer.java:239)
> > at
> >
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRe
> > nderer.java:115)
> > at
> > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124)
> > at
> org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
> > at
> >
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage
> > r.java:443)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
> > cycleExecutor.java:539)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> > (DefaultLifecycleExecutor.java:480)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec
> > ycleExecutor.java:459)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
> > ures(DefaultLifecycleExecutor.java:311)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa
> > ultLifecycleExecutor.java:278)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
> > Executor.java:143)
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> > )
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> > .java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at
> > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> > at
> > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> > at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> > [INFO]
> > 
> >
> > Thanks and Regards,
> > Anuradha Sinduria
> >
> >
> > -Original Message-
> > From: Tim Kettler [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, October 16, 2007 1:47 PM
> > To: Maven Users List
> > Subject: Re: Java doc generation
> >
> > Hi,
> >
> > this is 

Re: Japanese speaking users?

[Vincent Siveton]

Hi,

Naoki Nose did it for the site plugin in the past.
Maybe he could contribute again. I cc him.

Cheers,

Vincent

2007/10/17, Brian E. Fox <[EMAIL PROTECTED]>:
> Is there anyone out there who can review the patch for Japanese
> resources?
>
>
>
> http://jira.codehaus.org/browse/MNG-428
>
>
>
> Thanks,
>
> Brian
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Looking for UML Diagram Plugin

[Vincent Siveton]

Hi,

Also, in the sandbok, we have a project [1] which an Ant UmlDocTask
which uses javadoc and graphviz to generate UML diagram. HTH.

Cheers,

Vincent

[1] 
https://svn.apache.org/repos/asf/maven/sandbox/trunk/jxr/maven-jxr/maven-jxr-java

https://svn.apache.org/repos/asf/maven/sandbox/trunk/jxr/maven-jxr/maven-jxr-java

2007/10/19, Wendy Smoak <[EMAIL PROTECTED]>:
> On 10/19/07, Mac-Systems <[EMAIL PROTECTED]> wrote:
>
> > i searched a bit the www for an UML Generator Plugin.
> > Anyone can point me whats good for Maven 2 ?
> > Generation should run unter Linux Maschine, as i read
> > about http://wiki.wsmoak.net/cgi-bin/wiki.pl?UMLGraph
> > which seems to run only on Windows...
>
> I was using Windows when I wrote up the example.  I just did it on OS
> X, haven't tried it on Linux but I imagine it should work.  Here's the
> GraphViz download page:  http://www.graphviz.org/Download..php
>
> You can take the example from the Continuum pom:
> http://svn.apache.org/repos/asf/maven/continuum/trunk/pom.xml
>
> And here's an example of aggregated Javadocs with UML diagrams at the
> package and class level:
> http://maven.apache.org/continuum/ref/latest/apidocs/org/apache/maven/continuum/project/builder/AbstractContinuumProjectBuilder.html
> (Click 'FRAMES' at the top to wander around more.)
>
> HTH,
> --
> Wendy
>
> -
> 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]

[ANN] Maven Antlr Plugin Moved

[Vincent Siveton]

The Maven Team announces that the Maven Antlr Plugin is now hosted by
the Mojo project at Codehaus.

The new website is: http://mojo.codehaus.org/antlr-maven-plugin/

- The Maven Team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANN] Maven Javadoc Plugin 2.3 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of Maven Javadoc Plugin,
version 2.3.

http://maven.apache.org/plugins/maven-javadoc-plugin/

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:


org.apache.maven.plugins
maven-javadoc-plugin
2.3



Release Notes - Maven 2.x Javadoc Plugin - Version 2.3


** Bug
   * [MJAVADOC-74] - Unavailable package-list prevents deploy & release
   * [MJAVADOC-83] - Aggregated javadoc page stays empty when site is
generated with the destination option active
   * [MJAVADOC-87] - doc-files ignored if they reside in the
resources directory
   * [MJAVADOC-94] - The javadoc option "-sourcetab" should be passed
as "-linksourcetab"
   * [MJAVADOC-101] - Embedded error: Error rendering Maven report
   * [MJAVADOC-104] - Javadoc of generated sources is not generated
when aggregate=true
   * [MJAVADOC-105] - Excluded package is generated (should not)
because of wrong file separator.
   * [MJAVADOC-110] - sourcepath element is not working
   * [MJAVADOC-113] - docletPath not working in 2.2 - Cannot find
doclet class ydoc.doclets.YStandard
   * [MJAVADOC-115] - getDocletPath does not return correct path
   * [MJAVADOC-117] - sourcepath and aggregate don"t work to generate
javaodc of test classes
   * [MJAVADOC-118] - src/main/javadoc of sub modules ignored for
generation of aggregated javadoc
   * [MJAVADOC-123] - Encoding Error When Getting project.name For
JavaDoc -doctitle
   * [MJAVADOC-124] - Can't find resource for bundle
com.sun.tools.doclets.formats.html.resources.standard, key
doclet.malformed_html_link_tag
   * [MJAVADOC-125] - Dont generate javadoc report if project has pom
packaging and src/main exists
   * [MJAVADOC-127] - Tests fail on MacOS X
   * [MJAVADOC-128] - Plugin does not accept URL to an offlineLink's location
   * [MJAVADOC-129] - javadocDirectory config parameter is ignored
and default doesn't work either.
   * [MJAVADOC-130] - Inproper Handling of Tag Definitions
   * [MJAVADOC-133] - Javadoc fails if footer contains newlines

** Improvement
   * [MJAVADOC-75] - Document how to deploy javadoc jars
   * [MJAVADOC-112] - How to use packages should be documented
   * [MJAVADOC-114] - Less output
   * [MJAVADOC-120] - Better handling of Javadoc resources:
overview.html, doc-files
   * [MJAVADOC-131] - file configuration should use File type instead of String

** New Feature
   * [MJAVADOC-98] - Add support for Javadoc version different from JAVA_HOME
   * [MJAVADOC-100] - Allow JavaDocs to generate for Test Code
   * [MJAVADOC-109] - Able to point to different JVM, rather then
just using what is set in JAVA_HOME
   * [MJAVADOC-121] - Add a new parameter to handle additional -J options



** Wish
   * [MJAVADOC-95] - Confusing  and
 configuration options
   * [MJAVADOC-122] - configuration documentation


Enjoy,

-The Maven team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Same jar, different version

[Vincent Siveton]

Hi,

Seems to be a problem inside appfuse. Ask it on [EMAIL PROTECTED]
http://appfuse.org/display/APF/Mailing+Lists

Cheers,

Vincent

2007/7/14, Frederick N. Brier <[EMAIL PROTECTED]>:

I am learning AppFuse and Maven2 at the same time.  Things are going
well, but I have a number of .jar(s) included in the target .war's
WEB-INF/lib that are the same, but different versions.  There are
currently 4.

commons-digester-1.7.jar
commons-digester-1.8.jar

commons-lang-2.0.jar
commons-lang-2.3.jar

commons-logging-1.0.4.jar
commons-logging-1.1.jar

struts2-spring-plugin-2.0.6.jar
struts2-spring-plugin-2.0.8.jar

Why might this occur?  If it is a bug, what is the workaround.  I saw
 elements within a  element and
was wondering whether if I found the place where the files were getting
included, I could issue an exclude.

Right now, I am manually deleting the duplicate .jars out of the .war.
Otherwise, a deployment error is generated at startup because the
struts-default.xml cannot be found.  Thank you for you help.

Fred


-
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 site plugin "Doxia" issue ..

[Vincent Siveton]

Hi,

You need to install it from svn:
http://svn.apache.org/viewvc/velocity/site/tools/velocity-site-doxia-renderer/

Ask [EMAIL PROTECTED] to provide it on the Apache Snapshot Repository.

Cheers,

Vincent

2007/7/12, Giovanni Azua <[EMAIL PROTECTED]>:

Hi all,

I have spent quite a bit trying to have doxia installed and running.

Basically I need couple of features only available with doxia:

1-. Ability to customize my index.html to something like e.g. maven 2
site does using the index.xml.vm velocity template.

2-. Use the snippet macro during site generation.

The problem is that I am not able to get the doxia snapshot anywhere ...

Any examples of a working setup?

I have in my pom.xml the settings bellow but I get all kind of errors
Like e.g. mismatch of site plugin version with doxia version, missing
plugin version etc etc.

TIA,
Regards,
Giovanni



org.apache.maven.plugins
maven-site-plugin
2.0-SNAPSHOT


org.apache.velocity.site

velocity-site-doxia-renderer
1.2-SNAPSHOT




org.apache.velocity.site
velocity-site-doxia-renderer
1.0-SNAPSHOT







pre-site






  
Codehaus Snapshots
http://snapshots.repository.codehaus.org/
   
   
 Apache Snapshot Repository
 http://people.apache.org/repo/m2-snapshot-repository/
   




-
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: Source XREF generation puzzle !

[Vincent Siveton]

Hi again,

http://jira.codehaus.org/browse/JXR
With a patch it is always better :)

Cheers,

Vincent

2007/7/11, Mick Knutson <[EMAIL PROTECTED]>:

where do I go to do that?

On 7/11/07, Vincent Siveton <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> sourceDirs is a readonly param so you cannot use jxr to include
> generated-sources dir.
> Samething for test-jxr goal.
>
> Please open an issue.
>
> Cheers,
>
> Vincent
>
> 2007/7/11, Mick Knutson <[EMAIL PROTECTED]>:
> > I just added this to my project and have only 1 issue. My
> generated-sources
> > does not get included
> >
> > 
> > org.apache.maven.plugins
> > maven-jxr-plugin
> >
> > 
> > 
> > com
> > 
> > 
> > org/**/*.java
> > com/**/*.java
> > 
> > 
> >
> > com/company/test/**/*.java
> > 
> > 
> > 
> > jxr
> > 
> > 
> > 
> >
> > 
> >
> >
> > How can I include both :
> > ./src/main/java
> >
> > and
> >
> > ./src/main/generated-sources
> >
> >
> >
> >
> >
> > On 7/11/07, Jerome Thibaud <[EMAIL PROTECTED]> wrote:
> > >
> > > oh! oh! oh! I think I've seen a typo...
> > > As usual, it's after you click the send button that it hits you!
> > >
> > > the second
> > >
> > >  jxr
> > >
> > >
> > > should have been
> > >
> > >  test-jxr
> > >
> > >
> > > I guess that's this part which makes the link between a configuration
> and
> > > a
> > > goal.
> > >
> > > Thus said it still doesn't work!
> > >
> > > Exclusion/Inclusion works fine when applied to the plugin level.
> > > But no effect when applied in the reportSet...
> > >
> > > [DEBUG]   (f) excludes = []
> > > [DEBUG]   (f) includes = []
> > >
> > >
> > >
> > > Help greatly appreciated!
> > >
> > >
> > > Jerome
> > >
> >
> >
> >
> > --
> > ---
> > Thanks,
> > Mick Knutson
> >
> > http://www.baselogic.com
> > http://www.blincmagazine.com
> > http://www.djmick.com
> > http://www.myspace.com/mickknutson
> > http://www.myspace.com/djmick_dot_com
> > http://www.myspace.com/sexybeotches
> > http://www.thumpradio.com
> > ---
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
---
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Source XREF generation puzzle !

[Vincent Siveton]

Hi,

sourceDirs is a readonly param so you cannot use jxr to include
generated-sources dir.
Samething for test-jxr goal.

Please open an issue.

Cheers,

Vincent

2007/7/11, Mick Knutson <[EMAIL PROTECTED]>:

I just added this to my project and have only 1 issue. My generated-sources
does not get included


org.apache.maven.plugins
maven-jxr-plugin



com


org/**/*.java
com/**/*.java



com/company/test/**/*.java



jxr







How can I include both :
./src/main/java

and

./src/main/generated-sources





On 7/11/07, Jerome Thibaud <[EMAIL PROTECTED]> wrote:
>
> oh! oh! oh! I think I've seen a typo...
> As usual, it's after you click the send button that it hits you!
>
> the second
>
>  jxr
>
>
> should have been
>
>  test-jxr
>
>
> I guess that's this part which makes the link between a configuration and
> a
> goal.
>
> Thus said it still doesn't work!
>
> Exclusion/Inclusion works fine when applied to the plugin level.
> But no effect when applied in the reportSet...
>
> [DEBUG]   (f) excludes = []
> [DEBUG]   (f) includes = []
>
>
>
> Help greatly appreciated!
>
>
> Jerome
>



--
---
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: next javadoc plugin release?

[Vincent Siveton]

Hi Mark,

The release could be done quickly, hope this month.

Cheers,

Vincent

2007/7/9, Mark Proctor <[EMAIL PROTECTED]>:

Any update when the javadoc plugin will be released?

Mark
Mark Proctor wrote:
> The Javadoc plugin is currently broken for doclet usage. I fixed the
> bug and carlos applied my patch,
> http://jira.codehaus.org/browse/MJAVADOC-115 - vincent is taking time
> to work on xwiki so won't be doing any plugin maintenance. Any idea
> when this will be released, who can do this now with vincent awol?
> It's not an enhancement, but a pretty serious bug fix, so hoping that
> it will get prioritised. I've got a release coming up soon and really
> want to have doclets working in maven, without having to maintain my
> own INTERNAL fork of the plugin, which is a real pain for open source
> projects.
>
> Mark
>


-
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: Source XREF generation puzzle !

[Vincent Siveton]

Hi Jerome,

Unsupported feature outofbox.

An easy workaround is to use reportset, something like this following:

 
   
 
   org.apache.maven.plugins
   maven-jxr-plugin
   
 
   com
   
 ...
   
   
 jxr
   
 
 
   test
   
 ...
   
   
 jxr
   
 
   
 
   
 

Cheers,

Vincent

2007/7/10, Jerome Thibaud <[EMAIL PROTECTED]>:

Hi,

I got a legacy project where tests and application sources are under the
same directory

/src/com/...
  /test/...


Enters maven-jxr-plugin. Which is called twice during site generation, once
for the (app) sources and once for the tests.

And I want to filter out src/test during the (app) sources Xref generation
and to filter out src/com during the tests Xref generation.

So I see a filter configuration


  ...
  
**/include/*.java
  
  ...


 Makes me feel like I'm almost there, but, considering the absence of more
settings,
I suppose this applies to both jxr:jxr and jxr:test-jxr.

Hence my question, how do I specify 2 configurations, one for the execution
of jxr:jxr and the other for jxr-test-jxr?

Thanks in advance

Jerome Thibaud



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [ANN] Maven Stylus Skin 1.0.1 Released

[Vincent Siveton]

No website but you could do a co from
http://svn.apache.org/repos/asf/maven/skins/trunk

Cheers,

Vincent

2007/7/10, Srepfler Srgjan <[EMAIL PROTECTED]>:

Dennis Lundberg wrote:
> Wim Deblauwe wrote:
>> url of the website or the groupId/artifactId would be useful...
>
> There is no website for this skin.
>
> groupId:artifactId
> org.apache.maven.skins:maven-stylus-skin
>
> If you are using this skin you already have this configured in your
> site.xml file.
>
>>
>> regards,
>>
>> Wim
>>
>> 2007/5/31, Dennis Lundberg <[EMAIL PROTECTED]>:
>>>
>>>
>>> The Maven team is pleased to announce the release of Maven Stylus Skin,
>>> version 1.0.1.
>>>
>>>
>>> Release Notes - Maven Skins - Version stylus-1.0.1
>>>
>>> ** Bug
>>>  * [MSKINS-1] - Images are missing that are referenced in
>>> maven-theme.css
>>>
>>>
>>> - The Maven Team
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>
>
I don't use is but I'd like to check it out, where can I find the homepage?
Srgjan

-
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: [m205] JDeveloper support, and best

[Vincent Siveton]

Hi Mick,

You could use the maven2 jdev plugin
http://wiki.apache.org/myfaces/Trinidad_Plugins
http://people.apache.org/repo/m2-snapshot-repository/org/apache/myfaces/trinidadbuild/maven-jdev-plugin/

Cheers,

Vincent

2007/5/16, Mick Knutson <[EMAIL PROTECTED]>:

I am having real issues trying to understand how to migrate my eclipse based
multi-module Maven 2 project to JDeveloper.
Can someone please help me understand the steps I am going to need to do to
accomplish this?



---
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: generating site for multiproject

[Vincent Siveton]

Hi Marco,

You could use the stage goal
mvn site:stage -DstagingDirectory=C:\fullsite

http://maven.apache.org/plugins/maven-site-plugin/howto.html

Cheers,

Vincent

2007/5/18, Marco Mistroni <[EMAIL PROTECTED]>:

hi all,
 how can i generate only one site for my multiproject?
i want to avoid to put 'hardcoded' references to point to sites of my
subprojects, i was wondering if maven could do an
'all in one' site..

any help?

thanks in advance and regards
 marco



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: SWF within Maven documentation

[Vincent Siveton]

Hi Steve,

2007/5/17, Steve Motola <[EMAIL PROTECTED]>:

Thank you - using APT.  I was able to successfully create a macro with
Doxia, easy once you see a working example.  There could be a little
more documentation...

Q:  Do you know of a location to get other third party macros?



No



Syntax:

  %{swf|src=swf/Example1/Example1|id=Example1|width=268|height=172}



Create an issue in jira for this. We will add it.

Cheers,

Vincent


Downloaded Doxia src.  Looked at Echo example in:


/doxia-1.0-alpha-8/doxia-core/src/main/java/org/apache/maven/doxia/macro

added Swf class, used maven to compile ;) and put in local repo.


Is still a little rough, simple but functional:


package org.apache.maven.doxia.macro;

/*
 * Copyright 2004-2006 The Apache Software Foundation.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *  http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

import org.apache.maven.doxia.sink.Sink;

import java.util.Iterator;

/**
 * Macro for embedding Flash (SWF) within Maven documentation.
 *
 * @plexus.component role="org.apache.maven.doxia.macro.Macro"
 * role-hint="swf"
 */
public class SwfMacro
extends AbstractMacro
{
private static final String EOL = System.getProperty(
"line.separator" );

public void execute( Sink sink, MacroRequest request )
{

// TODO: at what point to throw exceptions if some required
information
//   is not provided?

// parameter defaults
String src = "";
String id = "swf";
String width = "400";
String height = "400";
String quality = "high";
String menu = "false";
String loop = "0";
String play = "true";
String version = "9,0,45,0";
String allowScript = "sameDomain";

// assign parameters
for ( Iterator i = request.getParameters().keySet().iterator();
i.hasNext(); )
{
String str = "";
String key = (String) i.next();
if(key.equals("src")) {
str = (String) request.getParameter(key);
if(str != "") {
src = str;
}
}
if(key.equals("id")) {
str = (String) request.getParameter(key);
if(str != "") {
id = str;
}
}
if(key.equals("width")) {
width = (String) request.getParameter(key);
if(str != "") {
width = str;
}
}
if(key.equals("height")) {
str = (String) request.getParameter(key);
if(str != "") {
height = str;
}
}
if(key.equals("quality")) {
str = (String) request.getParameter(key);
if(str != "") {
quality = str;
}
}
if(key.equals("menu")) {
str = (String) request.getParameter(key);
if(str != "") {
menu = str;
}
}
if(key.equals("loop")) {
str = (String) request.getParameter(key);
if(str != "") {
loop = str;
}
}
if(key.equals("play")) {
str = (String) request.getParameter(key);
if(str != "") {
play = str;
}
}
if(key.equals("version")) {
str = (String) request.getParameter(key);
// enable version shorthand
// TODO: put in other shorthand versions
if(str.equals("6")) {
version = "6,0,29,0";
} else {
if(str.equals("9")) {
version = "9,0,45,0";
} else {
if(str != "") {
version = str;
} } }
}
if(key.equals("allowScript")) {
str = (String) request.getParameter(key);
if(str != "") {
allowScript = str;
}
}
}

String content = "" +
"" +
"" +
"" +
"" +
"" +
"" +
"" +
"" +
"" +
"";

sink.rawText

Re: next javadoc plugin release?

[Vincent Siveton]

Hi Mark,

We dont schedule a specific date for the release. I will have a glance
this week.
I am very *busy* actually so ping me if I dont.

Cheers,

Vincent

2007/4/30, Mark Proctor <[EMAIL PROTECTED]>:

The Javadoc plugin is currently broken for doclet usage. I fixed the bug
and carlos applied my patch,
http://jira.codehaus.org/browse/MJAVADOC-115 - vincent is taking time to
work on xwiki so won't be doing any plugin maintenance. Any idea when
this will be released, who can do this now with vincent awol? It's not
an enhancement, but a pretty serious bug fix, so hoping that it will get
prioritised. I've got a release coming up soon and really want to have
doclets working in maven, without having to maintain my own INTERNAL
fork of the plugin, which is a real pain for open source projects.

Mark

-
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: Status of maven dependency analysis mojo?

[Vincent Siveton]

Hi Steinar,

Moved to 
https://svn.apache.org/repos/asf//maven/sandbox/trunk/shared/maven-dependency-analyzer/
and the plugin was merged into maven-dependency-plugin

Cheers,

Vincent

2007/3/7, Steinar Bang <[EMAIL PROTECTED]>:

Does anyone know the current status for the dependency analysis mojo?
Specifically: is there still work going on it, or is it dead?  Where
can I get it from?  How do I run it? (ie. what goals do I give on the
command line?)

I googled today for something to help me clean up the dependencies of
our hierarchical maven project, and I ran into the
maven-dependency-analyzer:
http://jira.codehaus.org/browse/MNG-2676
which seems to be exactly what I was looking for.

However, the SVN URLs in the above bug report don't work.  I was able
to check out the maven-dependency-analyzer by inserting a "/trunk"
after "/shared".

But I wasn't able to find the maven-dependency-analyzer-plugin.

So any information about the status of this tool, or of alternative
tools, is welcome.

Thanx!


- Steinar



-
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: [m2.0.5] Javadoc generation for older code

[Vincent Siveton]

Hi Thorsten,

2007/2/26, Thorsten Heit <[EMAIL PROTECTED]>:

Hi Vincent,


> > Until the corresponding classes are updated or refactored, how can I let
> Javadoc generate the API documentation?
>
> Add -Ddebug=true
> 
http://maven.apache.org/plugins/maven-javadoc-plugin/faq.html#How%20to%20know%20exactly%20the%20Javadoc%20command%20line

The parameters listed there are basically the same that I already tried on the 
command line but that also doesn't work:

%> javadoc -source 1.4 -sourcepath src/ -d target/site/apidocs/ 

Loading source files for package ukv.lrkern...
d:\workspaces\sukv-maven\CAccess\src\ukv\lrkern\LRKern.java:10948: as of 
release 5, 'enum' is a keyword, and may not be used as an identifier
(use -source 1.4 or lower to use 'enum' as an identifier)
Enumeration enum = map.keys();
^
etc.

Isn't there a trick to force the Javadoc command to ignore JDK >= 1.5 keywords?


No AFAIK




Regards

Thorsten


PS: I'm using JDK 6 as default JDK on my machine (Windows XP).


Sounds like http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6507179

Cheers,

Vincent


-
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: 2 modello questions

[Vincent Siveton]

2007/2/26, Jörg Schaible <[EMAIL PROTECTED]>:

Hi Jo,

Jo Vandermeeren wrote on Monday, February 26, 2007 9:52 AM:

> Hi Tim,
>
> I have no experience with the modello plugin, but you could always
> contact one of the developers directly..
> http://dcabasson.developpez.com/maven/modello-maven-plugin/tea
> m-list.html

No, it is *awlays* a very bad idea to contact the devs directly, especially if 
the project clearly states, that it has a mailing list:
http://dcabasson.developpez.com/maven/modello-maven-plugin/mail-lists.html



Agree!

Cheers,

Vincent


[snip]

- Jörg

-
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: 2 modello questions

[Vincent Siveton]

2007/2/24, Tim Moloney <[EMAIL PROTECTED]>:

1) How do you write a .mdo file to implement the following XML?

  
element text
  

To get the attributes, you have to define a .  However, a class
appears to only support attributes and child elements.


yes



2) Is it possible to add something to a .mdo file to have "implements
Comparable" added to a generated class definition?


Yes by using 

Cheers,

Vincent


Thanks,
  Tim


-
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: [m2.0.5] Javadoc generation for older code

[Vincent Siveton]

Hi Thorsten,

2007/2/26, Thorsten Heit <[EMAIL PROTECTED]>:

Hi,

we're developing using JDK 1.4, and unfortunately someone uses "enum" as a variable name 
somewhere in one of his source files. Since "enum" is a reserved keyword for Java 5 and 
higher, executing javadoc results in a couple of errors:

(...)
Loading source files for package ukv.lrkern...
d:\workspaces\sukv-maven\CAccess\src\ukv\lrkern\LRKern.java:10948: as of 
release 5, 'enum' is a keyword, and may not be used as an identifier
(use -source 1.4 or lower to use 'enum' as an identifier)
Enumeration enum = map.keys();

etc.

In the reportings section in my pom.xml I added


org.apache.maven.plugins
maven-javadoc-plugin
2.2

1.4



but that didn't help. When I execute Javadoc in the command line using the "-source 
1.4" parameter, the errors remain (although the program tells me to add this 
parameter...).

Until the corresponding classes are updated or refactored, how can I let 
Javadoc generate the API documentation?


Add -Ddebug=true
http://maven.apache.org/plugins/maven-javadoc-plugin/faq.html#How%20to%20know%20exactly%20the%20Javadoc%20command%20line

Cheers,

Vincent





Regards

Thorsten

-
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: APT Images With URL

[Vincent Siveton]

Hi,

2007/1/18, Subhash Chandran <[EMAIL PROTECTED]>:

The APT format guide here:

http://maven.apache.org/guides/mini/guide-apt-format.html

speaks only of image display. This is done like: [path/to/image.ext]

Is there any possibility of having a link on the image?


Not actually see DOXIA-71 but contributions are always welcome.

Cheers,

Vincent



Is there a possibility of somehow having HTML code rendered from
inside APT? This would ease most of my frustrations with APT.

--
Regards,
Subhash Chandran S

http://wizcrypt.wiztools.org/

-
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: cannot find images in APT files

[Vincent Siveton]

Hi Martin,

2007/1/9, Martin Goldhahn <[EMAIL PROTECTED]>:

Hi!
I want to render an APT file that I use in my site as a PDF file.
Maven's site plugin finds the image because it is located in
src/site/resources. It seams that this path is not added to doxia's
classpath. Thus it cannot find the image.

How do I tell the doxia-maven-plugin that it should search the resources
folder as well?


It seems to be a limitation. Please open an issue.

Cheers,

Vincent



Martin

REMINDER - Vincent Massol & Jason van Zyl - Conférence gratuite / Free Conference - Montréal, Canada

[Vincent Siveton]

Hi all,

Feel free to contact Carmen Robert ([EMAIL PROTECTED]) to
register: it is free.

Cheers,

Vincent


-Original Message-
From: Carmen Robert [mailto:[EMAIL PROTECTED]
Sent: Monday, November 27, 2006 8:49 AM
To: Carmen Robert
Subject: RAPPEL : Vincent Massol & Jason van Zyl - Conférence gratuite /
Free Conference
Importance: High

(English version follows)

L'HEURE DU CRIM
CONFÉRENCE DE VINCENT MASSOL ET JASON VAN ZYL
Vendredi le 1er décembre 2006
De 10 h 00 à 12 h 00
(Présentation donnée en anglais)

Titre : Assurer la qualité du produit avec Maven et utiliser efficacement
Maven avec des équipes

Conférenciers : Vincent Massol, directeur technique, Pivolis, Paris et
Jason van Zyl, chef, Mergere, Marina Del Rey, Californie.

Lieu :

*   Montréal : Maison des hautes technologies de Montréal, 550, rue
Sherbrooke Ouest, Bureau 100, Salle A
*   Québec : CRIM Québec, Place de la Cité - Tour de la Cité, 2600,
boul. Laurier, bur. 625, salle C

Inscription gratuite - Réservation :

*   Montréal : (514) 840-7992 / [EMAIL PROTECTED]
*   Québec : (418) 648-8080 / [EMAIL PROTECTED]


RÉSUMÉ : Assurer la qualité du produit avec Maven : La première partie de
cette présentation démontrera comment utiliser les "plugins" de Maven pour
garantir une bonne qualité du code. Plus spécifiquement, nous couvrirons
les thèmes suivants :

• Les bonnes pratiques d'utilisation des "plugins" Checkstyle,
PMD et Findbugs

• Couverture de code avec les "plugins" Clover et Cobertura

• Vérification de compatibilité binaire en utilisant le
"plugin" Clirr

• Automatisation des tests fonctionnels avec Cargo et Maven.



Utiliser efficacement Maven avec des équipes : La deuxième partie de cette
présentation est pour ceux et celles qui veulent influencer la
collaboration dans les équipes au moyen de Maven et de ses outils reliés
comme Continuum, le gestionnaire de "repository". Il y aura aussi une
discussion sur les défis que les équipes doivent relever lors du
développement d'un logiciel et comment Maven peut aider à surmonter ces
défis. Les techniques de gestion de site Web fournies par Maven aident les
équipes à fournir de la visibilité nécessaire aux projets et aident les
membres de l'équipe à connaître la documentation à jour lors de la
génération de site Web. Les techniques d'intégration continue seront
présentées et le logiciel Continuum sera utilisé pour démontrer comment
suivre un projet avec un minimum d'effort. La gestion des "releases", qui
peut être souvent difficile, sera également discutée et les outils de
gestion de "release" fournis par Maven seront employés pour démontrer
comment alléger la complexité et le fardeau de faire des "releases"
fréquemment, sûrs et reproductibles.


BIOGRAPHIES :


Vincent Massol : Vincent est un participant actif de la communauté Maven
en tant que committer et que membre du Project Management Committee (PMC),
depuis les débuts de Maven en 2002. En plus de son travail sur Maven, il a
fondé le projet Jakarta Cactus de la fondation ASF, qui est un simple
"framework" pour tester le code Java côté serveur, et le projet Cargo de
la fondation Codehaus, une API Java unifiant la manipulation des
conteneurs Java. Récemment, Vincent a participé comme committer au projet
Xwiki, un wiki Open Source de deuxième génération. Vincent est le co-
auteur de trois livres : « JUnit in Action » publié par Manning en 2003, «
Maven: A Developer's Notebook » publié par O'Reilly en 2005 et « Better
Builds with Maven » publié par Mergere en 2006.



Jason van Zyl : Jason Van Zyl a plus de dix ans d'expérience en
développement de logiciel pour des entreprises du Fortune 500. Il est le
fondateur des projets Maven d'Apache, du "framework" Plexus de Codehaus,
et du projet Velocity de Jakarta, et est actuellement le président du PMC
de Maven. Jason est un fanatique d'Open Source, il est impliqué dans
Apache depuis plus de six ans, il a participé à la création de la
fondation Codehaus et quand il ne travaille pas sur des projets Open
Source, il s'endort en rêvant à eux !

L'Heure du CRIM est une série de séminaires scientifiques donnés par des
experts de renommée internationale et organisés par la R-D du CRIM (Centre
de recherche informatique de Montréal). Contact : Carmen Robert, 514-840-
7992 / [EMAIL PROTECTED]  Veuillez nous excuser si vous recevez cette
annonce en plusieurs exemplaires.  Merci de bien vouloir faire circuler ce
message autour de vous.



L'HEURE DU CRIM
CONFERENCE WITH VINCENT MASSOL AND JASON VAN ZYL
Friday December 1st, 2006
From 10:00 a.m. to 12:00 p.m.
Presentation given in English

Title : Ensuring quality with Maven and using Maven effectively with teams

Speakers : Vincent Massol, Technical Director, Pivolis, Paris, and Jason
van Zyl, Chief, Mergere, Marina Del Rey, California.

Location :

*   MontrEal : Maison des hautes technologies de Montréal, 550
Sherbrooke West, Suite 100, Room A
*   

Re: javadoc plugin failures and recent behaviour change

[Vincent Siveton]

Hi Kelvin,

I did mvn javadoc:javadoc (with 2.1) on tuscany trunk:
https://svn.apache.org/repos/asf/incubator/tuscany/java

No error here. Are you sure that commonj is correctly included as dependency?

Cheers,

Vincent

2006/11/9, kelvin goodson <[EMAIL PROTECTED]>:

I have a build failure that's happening when creating javadoc and it seems
to be due to a change in the javadoc plugin behaviour.

Here is a mvn execution log that exhibits the problem
https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/kgoodson/javadocProblems/fresh.log

Here are the logic steps that lead me to the conclusion that this is a
plugin behaviour change

1) Building in my trunk started failing like this a few days ago
2) so I tried buiding an old unaltered release source tree which used to
build fine, against my local repo and it failed in the same way
3) so I tried an offline build of the same release source on a different
machine which had an old repository state, and it succeeded
4) so I zipped up the old repository from the 2nd machine and transferred it
to the machine where the failures had started and did offline builds of both
the release and of the trunk,  which both succeeded  --- at which point I
could assert that it was the repository state that was at fault (see
https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/kgoodson/javadocProblems/dt_used_on_lt.log
)
5) so I completely removed my repository and did and online build of the
trunk from fresh,  which failed in the same way that I had seen in step 1 --
at which point I could assert that the problems were introduced by an
artifact which had been freshly downloaded to my repository

I see from the difference in the logs, that right at the start of the
javadoc:javadoc phase there is behaviour difference,  the one that succeeds

begins in this way
===
[INFO] [javadoc:javadoc]
Loading source files for package org.apache.tuscany.sdo...
Loading source files for package org.apache.tuscany.sdo.codegen...
Loading source files for package org.apache.tuscany.sdo.helper...
Loading source files for package org.apache.tuscany.sdo.impl...
Loading source files for package org.apache.tuscany.sdo.model...
Loading source files for package org.apache.tuscany.sdo.model.impl...
Loading source files for package org.apache.tuscany.sdo.model.java.impl...
Loading source files for package org.apache.tuscany.sdo.model.java...
Loading source files for package org.apache.tuscany.sdo.util...
Loading source files for package org.apache.tuscany.sdo.util.metadata.impl..
.
Loading source files for package org.apache.tuscany.sdo.util.metadata...
Loading source files for package org.apache.tuscany.sdo.util.resource...
Loading source files for package org.apache.tuscany.sdo.generate.adapter...
Loading source files for package org.apache.tuscany.sdo.generate...
Loading source files for package
org.apache.tuscany.sdo.generate.templates.model...
Loading source files for package org.apache.tuscany.sdo.generate.util...
Loading source files for package org.eclipse.jdt.core.formatter...
Loading source files for package org.apache.tuscany.sdo.plugin...


whereas the one that fails begins in this way ...
[INFO] [javadoc:javadoc]
Loading source file
C:/Development/Tortoise/distroTest3/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/AnyTypeDataObject.java...
Loading source file
C:/Development/Tortoise/distroTest3/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/codegen/BytecodeInterfaceGenerator.java...
Loading source file
C:/Development/Tortoise/distroTest3/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/codegen/GenerationException.java...
Loading source file
C:/Development/Tortoise/distroTest3/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/codegen/JavaInterfaceGenerator.java...
Loading source file
C:/Development/Tortoise/distroTest3/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/codegen/NoJavaImplementationException.java...
Loading source file
C:/Development/Tortoise/distroTest3/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/helper/CopyHelperImpl.java...
Loading source file
C:/Development/Tortoise/distroTest3/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/helper/CrossScopeCopyHelperImpl.java...
Loading source file
C:/Development/Tortoise/distroTest3/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/helper/DataFactoryImpl.java...
Loading source file
C:/Development/Tortoise/distroTest3/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/helper/DataHelperImpl.java...
Loading source file
C:/Development/Tortoise/distroTest3/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/helper/EqualityHelperImpl.java...
Loading source file
C:/Development/Tortoise/distroTest3/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/helper/HelperProviderImpl.java...


==

FYI, the poart of the log whe

[ANN] Maven Javadoc Plugin 2.1 for Maven 2 Released

[Vincent Siveton]

The Maven team is pleased to announce the release of the Maven Javadoc
Plugin, version 2.1

http://maven.apache.org/plugins/maven-javadoc-plugin/

You can run mvn -U to get the latest version of the plugin, or specify
the version in your project's plugin configuration:


org.apache.maven.plugins
maven-javadoc-plugin
2.1



Release Notes - Maven 2.x Javadoc Plugin - Version 2.1

** Bug
   * [MJAVADOC-62] - javadoc:javadoc needs access to generated sources
   * [MJAVADOC-64] - No way to output javadoc warnings
   * [MJAVADOC-65] - The javadoc plugin seems to ignore package-info.java
   * [MJAVADOC-72] - Aggregating javadocs doesn't work
   * [MJAVADOC-81] - Additional doclets do not run.
   * [MJAVADOC-82] - 'sourcepath' should not be mandatory when using
'subpackages' configuration
   * [MJAVADOC-84] - destDir not used when generating a site
   * [MJAVADOC-85] -  allow only one taglet
   * [MJAVADOC-86] - Coma in  are replaced by -group
   * [MJAVADOC-87] - doc-files ignored if they reside in the
resources directory
   * [MJAVADOC-88] - Copyright null if no organization name was specified
   * [MJAVADOC-90] - Missing standard doclet options
   * [MJAVADOC-92] - Cant find javadoc.exe on windows in specific cases
   * [MJAVADOC-93] - Allow commas in text arguments doctitle,
windowtitle, header, footer, and bottom [PATCH ATTACHED]

** Improvement
   * [MJAVADOC-73] - provide javadoc warnings
   * [MJAVADOC-89] - Improve the plugin debugger

** New Feature
   * [MJAVADOC-61] - Adding custom source paths to javadoc

** Task
   * [MJAVADOC-71] - Update plugin documentation
   * [MJAVADOC-79] - Review plugin documentation

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Retrieving root directory in maven 2

[Vincent Siveton]

${project.parent} parent project
${project.parent.basedir} for the parent basedir

For all expressions, checks appendix A from "Better builds with maven" ebook.

Cheers,

Vincent

2006/8/9, Rohnny Moland <[EMAIL PROTECTED]>:

Hi there,

How can I retrieve the root directory in maven 2 from the pom?
${basedir} was the closest I found, but then I get the path from where
maven is running, so this seems to be the module path. I would guess
its a simple ${..} I can use..

BTW: Where can I find an overview over all the references I can use from a pom?


Thanks in advance,
Rohnny

-
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: Customize site Project Reports menu labels

[Vincent Siveton]

It is not possible yet. See:
http://jira.codehaus.org/browse/MPIR-35

Cheers,

Vincent

2006/8/9, lore <[EMAIL PROTECTED]>:


Hi!
I need to customize the labels of the Project Reports menu entries in the
Maven2 site.
How can I do?

Thanks,
   Lorenzo
--
View this message in context: 
http://www.nabble.com/Customize-site-Project-Reports-menu-labels-tf2077958.html#a5723454
Sent from the Maven - Users forum at Nabble.com.


-
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: Offline documentation

[Vincent Siveton]

Calling mvn site is the only option:
Maven Web Site
svn co http://svn.apache.org/repos/asf/maven/site/trunk
Plugins
svn co https://svn.apache.org/repos/asf/maven/plugins/trunk

Cheers,

Vincent

2006/8/7, Chris Hilton <[EMAIL PROTECTED]>:

You can probably check out the entire core Maven project and then run
"mvn site" in the root directory to generate documentation for all of
the core plugins.

Chris Hilton

> -Original Message-
> From: Paul Michael Reilly [mailto:[EMAIL PROTECTED]
> Sent: Monday, 07 August, 2006 12:24
> To: users@maven.apache.org
> Subject: Offline documentation
>
> As near as I can tell, all Maven2 reference documentation is
> on-line accessible.  I find myself on vacation now with rare
> and low quality on-line access.  Is there some way I can
> easily download documentation for the Maven2 core and
> plugins?  I am about to go get the Mergere book (pdf) but I
> was wondering if there is some other options?
>
> Thanks,
>
> -pmr
>
> -
> 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: Maven2 PDF plugin

[Vincent Siveton]

Hi,

This is a maven1 plugin.

For Maven2, you could create PDF (and more) using doxia-book. Actually
the implementation uses the itext framework.
http://maven.apache.org/doxia/book/

The website is not uptodate. Check out from svn to learn more.

Cheers,

Vincent

2006/8/6, Andreas Koop <[EMAIL PROTECTED]>:

Hi maven-users,

Does anybody know if there is a working PDF plugin for maven2? I would
like to generate a PDF from my whole project site as it is possible with
maven1. Trying version 2.2.1 from
http://www.ibiblio.org/maven2/maven/maven-pdf-plugin/ I get the following
Exception. The plugin seems not to work:-( Can someone give me a hint
what's going wrong?

Thanks a lot,

Andreas.

C:\temp\myapp>mvn maven:maven-pdf-plugin:2.2.1:pdf
[INFO] Scanning for projects...
[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] null
[INFO]

[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginM
anager.java:292)
at
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(De
faultPluginManager.java:198)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlug
inManager.java:163)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa
ultLifecycleExecutor.java:1252)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor
(DefaultLifecycleExecutor.java:1517)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListBy
AggregationNeeds(DefaultLifecycleExecutor.java:381)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:135)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]

[INFO] Total time: < 1 second
[INFO] Finished at: Mon Aug 07 00:35:37 CEST 2006
[INFO] Final Memory: 1M/2M
[INFO]


C:\temp\myapp>

-
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: The mvn script errors out when JAVA_HOME is not defined

[Vincent Siveton]

JAVA_HOME is a requirement
http://maven.apache.org/download.html#installation

Cheers,

Vincent

2006/8/7, Weiqi Gao <[EMAIL PROTECTED]>:

Hi,

I'm learning Maven 2.0.4 and encountered an error when invoking the
mvn script.  The following piece of script seems to be the cause of my
error message:


if [ -z "$JAVACMD" ] ; then
 if [ -n "$JAVA_HOME"  ] ; then
   if [ -x "$JAVA_HOME/jre/sh/java" ] ; then
 # IBM's JDK on AIX uses strange locations for the executables
 JAVACMD="$JAVA_HOME/jre/sh/java"
   else
 JAVACMD="$JAVA_HOME/bin/java"
   fi
 else
   JAVACMD=java
 fi
fi

if [ ! -x "$JAVACMD" ] ; then
 echo "Error: JAVA_HOME is not defined correctly."
 echo "  We cannot execute $JAVACMD"
 exit 1
fi


I don't have my JAVA_HOME set, so my JAVACMD has the value of "java"
when the [ -x "$JAVACMD" ] check is done.  Naturally it failed because
the file "java" doesn't exist in the current directory.

It would make more sense to do the [ -x "$JAVACMD" ] check in the [ -n
"JAVA_HOME" ] branch of the if statement in the previous block (when
$JAVACMD is built up).

Thanks,
--
Weiqi Gao (高为奇)
[EMAIL PROTECTED]
http://www.weiqigao.com/blog/

Re: per-user db settings in maven

[Vincent Siveton]

Use the settings.xml

For sql statements, check:
http://mojo.codehaus.org/sql-maven-plugin/

Cheers,

Vincent

2006/7/26, Denis McCarthy <[EMAIL PROTECTED]>:

Hi,
I'm moving from an ant build process to maven. I'm currently trying to
replace an ant target that rebuilt our database. In the ant target each
developer had an individual local.properties file that defined their own
username/password/tnsname for the database. I'm writing a simple plugin
to rebuild the db at the moment. Where do non-shareable properties fit
in in maven?

I can't really have these properties directly in a  tag
in the pom, because the pom is committed to source control and will be
shared by all developers. I'd like to import properties from a file that
is not committed to subversion
Thanks
Denis

-
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: Consulting

[Vincent Siveton]

Hi JF,

As Emmanuel and Carlos wrote, Mergere is the best option with European
based consultants and developers.

In Belgium, I know Peopleware (http://peopleware.be/) which presents
Maven training.

Cheers,

Vincent

PS: Not Mergere or Peopleware associate!

2006/6/15, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:


First of all, I would like to apologize if this list is not the
appropriate medium for such question, but I have no idea where I could
go elsewhere.

I would like to know if anyone could recommend companies/individuals
providing consulting services around Maven 2.

It would be a limited mission, for Belgium, ideally in french
(although english is fine)

Regards,

J-F



-
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: [doxia] rendering xdoc separatly

[Vincent Siveton]

Arnaud,

You are right,  very poor documentation. See the doxia-site project.
The developers need to check the sources, and the tests.

Cheers,

Vincent

2006/3/22, Arnaud HERITIER <[EMAIL PROTECTED]>:
> Vincent,
>
> There's no documentation actually about doxia (except the javadoc and the
> tests) ?
>
> Arnaud
>
> On 3/22/06, Vincent Siveton <[EMAIL PROTECTED]> wrote:
> >
> > Hi Dominique,
> >
> > Have a look to test cases in the doxia-core
> >
> > http://svn.apache.org/repos/asf/maven/doxia/trunk/doxia-core/src/test/java/o
> > rg/apache/maven/doxia/module/xdoc
> >
> > HTH
> >
> > Vincent
> >
> > > -Original Message-
> > > From: Dominique JOCAL [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, March 22, 2006 4:55 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: [doxia] rendering xdoc separatly
> > >
> > > Hi all,
> > >
> > > i would like to write some technical documentation in xdoc format and
> > > render it for an existing web site, out of a maven context.
> > >
> > > Is it possible to call some code from Doxia to render xdoc files
> > separatly
> > > ? We'd like to render it "online", is there already some servlet for
> > doing
> > > this ?
> > >
> > > I'm conscious web site integration issues have to be handled : support
> > of
> > > the site banner and/or menu, support of the site CSS... There is some
> > work
> > > to do even if this Doxia code could generate style-less XHTML.
> > >
> > > Thank you for your reading and your solutions or advises,
> > >
> > > Dominique.
> >
> >
>
>

RE: [doxia] rendering xdoc separatly

[Vincent Siveton]

Hi Dominique,

Have a look to test cases in the doxia-core
http://svn.apache.org/repos/asf/maven/doxia/trunk/doxia-core/src/test/java/o
rg/apache/maven/doxia/module/xdoc

HTH

Vincent

> -Original Message-
> From: Dominique JOCAL [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 22, 2006 4:55 AM
> To: [EMAIL PROTECTED]
> Subject: [doxia] rendering xdoc separatly
> 
> Hi all,
> 
> i would like to write some technical documentation in xdoc format and
> render it for an existing web site, out of a maven context.
> 
> Is it possible to call some code from Doxia to render xdoc files separatly
> ? We'd like to render it "online", is there already some servlet for doing
> this ?
> 
> I'm conscious web site integration issues have to be handled : support of
> the site banner and/or menu, support of the site CSS... There is some work
> to do even if this Doxia code could generate style-less XHTML.
> 
> Thank you for your reading and your solutions or advises,
> 
> Dominique.

Re: [M2] site.xml schema

[Vincent Siveton]

AFAIK not yet

Cheers,

Vincent

2006/2/1, Thomas Van de Velde <[EMAIL PROTECTED]>:
> Hi,
>
> I am having an error in the generation of my site.
>
> [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0
> [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
> [ERROR] RHS of #set statement is null. Context will not be modified.
> org/apache/
> maven/plugins/site/maven-site.vm [line 2, column 1]
> [ERROR] Method calculateLink threw exception for reference $PathTool in
> template
>  org/apache/maven/plugins/site/maven-site.vm at  [3,29]
> [INFO]
> -
> ---
> [ERROR] BUILD ERROR
>
> Is there any schema I can use to validate my site.xml?
>
> Thomas
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] NPE in "mvn site" using maven from SVN

[Vincent Siveton]

Hi Arik,

It is a normal issue because maven-skins is not released yet.

Try to add the Apache Development Repository as mirror:
http://cvs.apache.org/maven-snapshot-repository/

I will add a request on the dev list.

Cheers,

Vincent

2005/12/23, Arik Kfir <[EMAIL PROTECTED]>:
> Hi,
>
> I've received the following exception while running "mvn site" on a
> multi-module project (using maven from SVN):
> java.lang.NullPointerException
>at 
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.getParentPrefix(DefaultDecorationModelInheritanceAssembler.java:255)
>at 
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:46)
>at 
> org.apache.maven.plugins.site.SiteMojo.getDecorationModel(SiteMojo.java:557)
>at 
> org.apache.maven.plugins.site.SiteMojo.getDecorationModel(SiteMojo.java:472)
>at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:348)
>at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:414)
>at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
>at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
>at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451)
>at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303)
>at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
>at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:585)
>at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>
> I know you guys don't like us "commoners" using maven from SVN (wink)
> but I couldn't wait, seeing the JIRAs about making the site plugin
> reactor-aware closed...
>  ;-)
>
> Regards,
>_
>Arik Kfir[EMAIL PROTECTED]
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Info Requested: About Maven nightly build binaries

[Vincent Siveton]

Hi Venkat,

> I am using Maven Version 2.
> I am getting issues here and there and most of them were already fixed based
> on the information in user group.
>  I like to know where can  I get the latest version (nightly build) of
> Maven.  The Apache Maven site binaries looks like provide downloads for only
> the stable releases.

All our builds are here
http://maven.zones.apache.org/~maven/builds/
BUT it is only for Maven itself, not for plugins

> Also I am getting little confusion every time about the Maven distributed
> internet site structures. Apache, JIRA , Codehaus, Nabble, Ibiblio,
> Soucrforge (is there something else? I do not know). I understand somehow
> but not quietly properly.

Quickly, Maven is an ASF top level project so we need the Apache
infrastructure ;)
JIRA is our issue tracking and project management application
Codehaus is our wiki
ibiblio is a Maven repository
nabble is a mail archive (the official is from ASF mail-archives.apache.org)

> If I need information what is the right place to look in. Can some one help
> me to understand how it is organized and what is the right place to look for
> information about Maven-2.

http://maven.apache.org/guides/index.html
http://maven.apache.org/guides/getting-started/index.html

HTH

Cheers,

Vincent

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: disable maven i18n output message

[Vincent Siveton]

Hi Ken

Look at this:
http://www.mail-archive.com/dev@maven.apache.org/msg25571.html

HTH

Cheers,

Vincent

2005/12/6, Ken Perl <[EMAIL PROTECTED]>:
> Hi,
> I have trouble to view the maven 's i18n message in my computer, it
> displays many questions mark ??? in its output.
> How could disable the i18n output message and view English output only?
> I am using maven 1.1-beta-2.
>
> --
> perl -e 'print unpack(u,"62V5N\"FME;G\!E ")'
>
> -
> 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: maven2 question

[Vincent Siveton]

Marco,

xdoclet
http://mojo.codehaus.org/xdoclet-maven-plugin/

Hibernate
https://svn.codehaus.org/mojo/trunk/mojo/hibernate2-maven-plugin

HTH

Cheers,

Vincent

2005/12/8, Marco Mistroni <[EMAIL PROTECTED]>:
> hello all,
>   i am currently using maven 1.0 together with XDoclet plugin and hibernate
> plugin for generating hbm.xml files etc
> i woud like to move to maven 2, is anyone aware of any plugins that can be
> used in maven2 with xdoclet and
> hibernate?
>
> thanks and regards
>  marco
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] Missing breadcrumb text

[Vincent Siveton]

Hi Kristian,

> a) A bug, as indicated by JIRA issue MNG-1706

Closed

> b) A change that requires me to update site.xml etc.?

You could add in your site.xml:

  ...
  
  ...


The position could be: left, right, navigation-top, navigation-bottom, bottom.
See http://jira.codehaus.org/browse/MNG-990

> Maven 1.x also had the option to display the versionnumber in the
> breadcrumb-section.
> Is this feature planned for 2.0 as well?

You could vote for MNG-991
Contributions are welcome ;)

Cheers,

Vincent

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wher is site.xml DTD ?

[Vincent Siveton]

Hi Jean-Charles,

No DTD but XSD.
http://maven.apache.org/maven-navigation-1.0.xsd

AFAIK, it is for Maven1. Arnaud, could you confirme that?

Cheers,

Vincent

2005/12/8, Jean-Charles Giardina <[EMAIL PROTECTED]>:
> Hi folk,
>
> Eclipse XML plugin doesn't like site.xml format (I think because it
> think is an eclipse file)
>
> So, I want to add DOCTYPE in my site.xml to stop borring warning.
>
> Where I can find site.xml DTD ?
>
> Tks
>
> -
> 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: [m2] Howto Hack JavadocReport.java

[Vincent Siveton]

I think that the best way for you is to build everything with the bootstrap
http://maven.apache.org/guides/development/guide-building-m2.html

HTH

Cheers,

Vincent

> -Original Message-
> From: Pilgrim, Peter [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 16, 2005 7:03 AM
> To: 'Maven Users List'
> Subject: RE: [m2] Howto Hack JavadocReport.java
> 
> > -----Original Message-
> > From: Vincent Siveton [mailto:[EMAIL PROTECTED]
> ====
> >
> > > Thanks for the information. I just apply the patch and
> > > ran `mvn compile install'. I get these errors.
> >
> > Best call for the build:
> > $mvn clean install
> >
> > Install phase will compile, test, package and install into your local
> > repository.
> >
> > > Is this normal behaviours for re-installing maven 2 plug-ins?
> >
> > My feeling is that you need to install the snapshot for
> > maven-plugin-parent,
> > eg from the trunk:
> > components/maven-plugins
> > $mvn clean install
> >
> > Cheers,
> >
> > Vincent
> >
> ====
> 
> The link for ``Build from Source is broken''
> http://maven.apache.org/developers/building.html
> 
> Vincent
> 
> I did exactly as you suggested, but I got an a different
> build exception.
> 
> 
> 
> C:\Projects\maven-site\maven-plugins>mvn clean install
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO]   Maven Plugins
> [INFO]   Maven PLUGIN Plugin
> [INFO]   Maven Ant Plugin
> [INFO]   Maven AntRun Plugin
> [INFO]   Maven Assembly Plugin
> [INFO]   Maven Checkstyle Plugin
> [INFO]   Maven Clean Plugin
> [INFO]   Maven Clover Plugin
> [INFO]   Maven Compiler Plugin
> [INFO]   Maven Deploy Plugin
> [INFO]   Maven Surefire Plugin
> [INFO]   Maven Eclipse Plugin
> [INFO]   Maven Ear plugin
> [INFO]   Maven EJB Plugin
> [INFO]   Maven Help Plugin
> [INFO]   Maven IDEA Plugin
> [INFO]   Maven Install Plugin
> [INFO]   Maven Jar Plugin
> [INFO]   Maven Javadoc Plugin
> [INFO]   Maven PMD Plugin
> [INFO]   Maven Site plugin
> [INFO]   Maven Project Info Reports Plugin
> [INFO]   Maven Rar plugin
> [INFO]   Maven Release plugin
> [INFO]   Maven Repository Plugin
> [INFO]   Maven Resources Plugin
> [INFO]   Maven Source Plug-In
> [INFO]   Maven War Plugin
> [INFO]   Maven Verifier Plugin
> [INFO] ---
> --
> ---
> [INFO] Building Maven Plugins
> [INFO]task-segment: [clean, install]
> [INFO] ---
> --
> ---
> [INFO] [clean:clean]
> [INFO] [install:install]
> [INFO] Installing C:\Projects\maven-site\maven-plugins\pom.xml to
> C:\Documents a
> nd Settings\ppilgrim\.m2\repository\org\apache\maven\plugins\maven-plugin-
> parent
> \2.0.1-SNAPSHOT\maven-plugin-parent-2.0.1-SNAPSHOT.pom
> [INFO] ---
> --
> ---
> [INFO] Building Maven PLUGIN Plugin
> [INFO]task-segment: [clean, install]
> [INFO] ---
> --
> ---
> [INFO] [clean:clean]
> [INFO] Deleting directory C:\Projects\maven-site\maven-plugins\maven-
> plugin-plug
> in\target
> [INFO] [plugin:descriptor]
> [INFO] [resources:resources]
> [WARNING]
> Artifact junit:junit:jar:3.8.1 retains local scope 'test'
> overriding bro
> ader scope 'compile'
> given by a dependency. If this is not intended, modify or remove
> the loc
> al scope.
> 
> Downloading:
> http://snapshots.maven.codehaus.org/maven2/org/apache/maven/maven-p
> lugin-tools-java/2.0.1-SNAPSHOT/maven-plugin-tools-java-2.0.1-SNAPSHOT.pom
> [WARNING] Unable to get resource from repository snapshots
> (http://snapshots.mav
> en.codehaus.org/maven2)
> Downloading:
> http://snapshots.maven.codehaus.org/maven2/org/apache/maven/maven-p
> lugin-tools-api/2.0.1-SNAPSHOT/maven-plugin-tools-api-2.0.1-SNAPSHOT.pom
> [WARNING] Unable to get resource from repository snapshots
> (http://snapshots.mav
> en.codehaus.org/maven2)
> Downloading:
> http://snapshots.maven.codehaus.org/maven2/org/apache/maven/maven-p
> lugin-tools-beanshell/2.0.1-SNAPSHOT/maven-plugin-tools-beanshell-2.0.1-
> SNAPSHOT
> .pom
> [WARNING] Unable to get resource from repository snapshots
> (http://snapshots.mav
> en.codehaus.org/maven2)
> Downloading:
> http://snapshots.maven.codehaus.org/maven2/org/apache/maven/maven-p
> roject/2.0.1-SNAPSHOT/maven-project-2.0.1-SNAPSHOT.pom
> [WARNING] Unable to get resource from 

RE: [m2] Howto Hack JavadocReport.java

[Vincent Siveton]

Hi again,

> Thanks for the information. I just apply the patch and
> ran `mvn compile install'. I get these errors.

Best call for the build:
$mvn clean install

Install phase will compile, test, package and install into your local
repository.

> Is this normal behaviours for re-installing maven 2 plug-ins?

My feeling is that you need to install the snapshot for maven-plugin-parent,
eg from the trunk:
components/maven-plugins
$mvn clean install

Cheers,

Vincent

> 
> [INFO] ---
> --
> ---
> [ERROR] BUILD ERROR
> [INFO] ---
> --
> ---
> [INFO] Failed to resolve artifact.
> 
> GroupId: org.apache.maven.plugins
> ArtifactId: maven-plugin-parent
> Version: 2.0.1-SNAPSHOT
> 
> Reason: Unable to download the artifact from any repository
>   org.apache.maven.plugins:maven-plugin-parent:2.0.1-SNAPSHOT:pom
> 
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   snapshots (http://snapshots.maven.codehaus.org/maven2)
> 
> 
> [INFO] ---
> --
> ---
> [INFO] For more information, run Maven with the -e switch
> [INFO] ---
> --
> 
> 
> Looks like the local POM bug again to me. Instinct says ignore it, then.
> Am I right?
> 
> > -Original Message-
> > From: Vincent Siveton [mailto:[EMAIL PROTECTED]
> > Sent: 16 November 2005 10:55
> > To: 'Maven Users List'
> > Subject: RE: [m2] Howto Hack JavadocReport.java
> >
> >
> > Hi Peter,
> >
> > The best way is to uncomment the following line:
> > optionsFile.deleteOnExit();
> > So you will know exactly the command line.
> >
> 
> 
> 
> > BTW, here is a patch.
> >
> > --- src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java
> > (révision 344975)
> > +++ src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java
> > (copie de travail)
> > @@ -822,7 +822,7 @@
> >  addArgIfNotEmpty( arguments, "-doctitle", quotedArgument(
> > doctitle ) );
> >  addArgIfNotEmpty( arguments, "-excludedocfilessubdir",
> > quotedPathArgument( excludedocfilessubdir ), 1.4f );
> >  addArgIfNotEmpty( arguments, "-footer",
> > quotedArgument( footer
> > ) );
> > -addArgIfNotEmpty( arguments, "-group",
> > quotedArgument( group ),
> > true );
> > +addArgIfNotEmpty( arguments, "-group", group, true );
> >  addArgIfNotEmpty( arguments, "-header",
> > quotedArgument( header
> > ) );
> >  addArgIfNotEmpty( arguments, "-helpfile",
> > quotedPathArgument(
> > helpfile ) );
> >
> > You could test it with the test project:
> > maven-javadoc-plugin\src\test\projects\javadoc-plugin-test1
> >
> > You need to add quote on your group element, eg:
> > "Unit Tests" "com.csfb.foo.test*:com.csfb.bar.test*"
> >
> > I think it is a regression bug. What is the JIRA issue id?
> >
> > Cheers,
> >
> > Vincent
> >
> >
> > > -Original Message-
> > > From: Pilgrim, Peter [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, November 16, 2005 5:26 AM
> > > To: Maven Users List (E-mail)
> > > Subject: [m2] Howto Hack JavadocReport.java
> > >
> > >
> > > Hi
> > >
> > > I have got the source code for maven 2 now, and I am trying
> > to debug the -
> > > group property
> > > of the maven-javadoc-plugin.
> > >
> > > I understand to compile the plugin, I ran ``mvn install'' from
> > > C:\Projects\maven-site\maven-plugins\maven-javadoc-plugin
> > >
> > > WHen I tried to run the mvn javadoc:javadoc I still get the error
> > > because of the group XML element.
> > >
> > >
> > >Unit Tests, com.csfb.foo.test*:com.csfb.bar.test*
> > >
> > >
> > > I dont know the correct syntax. How do I hack ``JavadocReport.java''
> > > to find out what is going on?
> > >
> > > addArgIfNotEmpty( arguments, "-taglet",
> > quotedArgument( taglet
> > > ), 1.4f );
> > > addArgIfNotEmpty( arguments, "-tagletpath",
> > > quotedPathArgument( tag

RE: [m2] Howto Hack JavadocReport.java

[Vincent Siveton]

Hi Peter,

The best way is to uncomment the following line:
optionsFile.deleteOnExit();
So you will know exactly the command line.

BTW, here is a patch.

--- src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java
(révision 344975)
+++ src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java
(copie de travail)
@@ -822,7 +822,7 @@
 addArgIfNotEmpty( arguments, "-doctitle", quotedArgument(
doctitle ) );
 addArgIfNotEmpty( arguments, "-excludedocfilessubdir",
quotedPathArgument( excludedocfilessubdir ), 1.4f );
 addArgIfNotEmpty( arguments, "-footer", quotedArgument( footer
) );
-addArgIfNotEmpty( arguments, "-group", quotedArgument( group ),
true );
+addArgIfNotEmpty( arguments, "-group", group, true );
 addArgIfNotEmpty( arguments, "-header", quotedArgument( header
) );
 addArgIfNotEmpty( arguments, "-helpfile", quotedPathArgument(
helpfile ) );

You could test it with the test project:
maven-javadoc-plugin\src\test\projects\javadoc-plugin-test1

You need to add quote on your group element, eg:
"Unit Tests" "com.csfb.foo.test*:com.csfb.bar.test*"

I think it is a regression bug. What is the JIRA issue id?

Cheers,

Vincent


> -Original Message-
> From: Pilgrim, Peter [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 16, 2005 5:26 AM
> To: Maven Users List (E-mail)
> Subject: [m2] Howto Hack JavadocReport.java
> 
> 
> Hi
> 
> I have got the source code for maven 2 now, and I am trying to debug the -
> group property
> of the maven-javadoc-plugin.
> 
> I understand to compile the plugin, I ran ``mvn install'' from
> C:\Projects\maven-site\maven-plugins\maven-javadoc-plugin
> 
> WHen I tried to run the mvn javadoc:javadoc I still get the error
> because of the group XML element.
> 
>
>Unit Tests, com.csfb.foo.test*:com.csfb.bar.test*
>
> 
> I dont know the correct syntax. How do I hack ``JavadocReport.java''
> to find out what is going on?
> 
> addArgIfNotEmpty( arguments, "-taglet", quotedArgument( taglet
> ), 1.4f );
> addArgIfNotEmpty( arguments, "-tagletpath",
> quotedPathArgument( tagletpath ), 1.4f );
> addArgIf( arguments, use, "-use" );
> addArgIf( arguments, version, "-version" );
> addArgIfNotEmpty( arguments, "-windowtitle", quotedArgument(
> windowtitle ) );
> }
>   System.out.println("JAVADOC PLUGIN options are
> "+arguments.toString() );
> 
> 
> 1 error
> [INFO] ---
> --
> ---
> [ERROR] BUILD ERROR
> [INFO] ---
> --
> ---
> [INFO] An error has occurred in JavaDocs report generation.
> 
> Embedded error: Exit code: 1 - javadoc: Illegal package name:
> "C:/Projects/bridg
> etown/core/target/javadoc/apidocs/stylesheet.css"
> 
> [INFO] ---
> --
> ---
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An error has
> occurred in
>  JavaDocs report generation.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:544)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
> Goal(DefaultLifecycleExecutor.java:482)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:452)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> 
> --
> Peter Pilgrim :: J2EE Software Development
> Operations/IT - Credit Suisse First Boston,
> Floor 15, 5 Canada Square, London E14 4QJ, United Kingdom
> Tel: +44-(0)207-883-4497
> 
> 
> ==
> 
> Please access the attached hyperlink for an important electronic
> communications disclaimer:
> 
> http://www.csfb.com/legal_terms/disclaimer_external_email.shtml
> 
> ==
> 
> 
> 
> -
> 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: First Release of Maven?

[Vincent Siveton]

Hi Bernd,

Maven 2: 19 Oct 2005
Maven 1: 13 Jul 2004

Regards,

Vincent

> -Original Message-
> From: Bernd Mau [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 08, 2005 5:51 AM
> To: users@maven.apache.org
> Subject: First Release of Maven?
> 
> Hi,
> 
> can anybody tell when the first public and stable version of Maven has
> been released?
> 
> Bernd
> 
> 
> -
> 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: [M2] dependency license management

[Vincent Siveton]

Hi

> The information is there (the POM can add it), and its a requirement
> on new POMs added to the repository by manual upload, though I'm sure

+1 for this feature

> there are quite a few gaps in the repository which we'd need to fill
> once this is analysed.
> 
> At present, this is something we are interested in working on, but
> don't have any immediate plans to implement. It would be fairly
> similar to the dependencies report.

IMHO it could be a first step to add a License column in the Project
Dependencies report.

Cheers,

Vincent



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [m2] Updating *.properties files according to environment

[Vincent Siveton]

Hi Samuel,

The Maven1 environment files (build.properties and project.properties) have
been replaced with a settings.xml file in Maven2.

You could also define profiles to have customized builds.
http://maven.apache.org/guides/introduction/introduction-to-profiles.html

Cheers,

Vincent

> -Original Message-
> From: Samuel Le Berrigaud [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 03, 2005 6:38 AM
> To: Maven Users List
> Subject: [m2] Updating *.properties files according to environment
> 
> Hi,
> 
> here is what I would like to do. I have some properties files for
> which values depends on the environement (development, test, live...)
> or per developer.
> 
> Here is a basic example:
> 
> [EMAIL PROTECTED]@
> [EMAIL PROTECTED]@
> [EMAIL PROTECTED]@
> [EMAIL PROTECTED]@
> 
> 
> What I would like is that, according to the environment, the variables
> of these files could be populated with right value (may be stored in
> pom.xml or settins.xml), and as far as possible keep a constant
> directory structure...
> 
> I have seen the "profile" managment that m2 provides, but it look like
> that for what I do, I would have to have different directories for the
> different environments (profiles)...
> 
> Is that possible using m2 ?
> 
> Please tell me if I'm not clear enough...
> 
> Thank you,
> 
> --
> Samuel Le Berrigaud


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] How to add Javadoc Report(s) ?

[Vincent Siveton]

Hi Peter,

> Running mvn javadoc:javadoc
>
> [INFO] [javadoc:javadoc]
> [INFO] C:\opt\j2sdk1.4.2_04\jre\..\bin\javadoc.exe @options @files
> usage: javadoc [options] [packagenames] [sourcefiles] [classnames] [EMAIL 
> PROTECTED]
> -overview   Read overview documentation from HTML file
> -public   Show only public classes and members
> -protectedShow protected/public classes and members (default)
>
> ====
>
> 1 error
> [INFO] 
> -
> ---
> [ERROR] BUILD ERROR
> [INFO] 
> -
> ---
> [INFO] An error has occurred in JavaDocs report generation.
>
> Embedded error: Exit code: 1 - javadoc: invalid flag: -J-Xmx512m


Works for me.
Try to install the latest javadoc plugin from SVN.

> BTW: How do specify the  information in the configuration element.
>
> Is the format like this?
>
>
>org.apache.maven.plugins
>maven-javadoc-plugin
>
>128m
>512m
>true
>
>Data Access Objects,
>com.csfb.asds.server.dao:
>com.csfb.asds.ejb.dao:
>com.csfb.asds.client.dao:
>
>
>


The following test worked in the past.
http://svn.apache.org/repos/asf/maven/components/trunk/maven-plugins/maven-javadoc-plugin/src/test/projects/javadoc-plugin-test1/pom.xml
So, sounds like a bug around the line 825 ;)
Could you file it in JIRA?

Cheers,

Vincent

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] Maven project descriptor documentation is wrong

[Vincent Siveton]

Hi

That sounds like the MNG-523 issue
http://jira.codehaus.org/browse/MNG-523

Cheers,

Vincent

2005/10/20, Craig S. Cottingham <[EMAIL PROTECTED]>:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to ,
> the testResources element contains resource elements. According to the
> XSD, they're testResource elements.
>
> Should I file a bug in JIRA? If so, under what?
>
> - --
> Craig S. Cottingham
> [EMAIL PROTECTED]
> OpenPGP key available from:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7977F79C
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.4 (Darwin)
>
> iD8DBQFDV7khEJLQ3Hl395wRAgwmAJ45yEXJWLxdydwPrOW0uUV/fFoUJwCaA7Yc
> Wjm7+wMQycZMr8ecWbkCEIM=
> =i/yx
> -END PGP SIGNATURE-
>
>
> -
> 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: Problems with maven-project-info-reports-plugin

[Vincent Siveton]

Hi,

It is a known bug
http://jira.codehaus.org/browse/MNG-1216
http://jira.codehaus.org/browse/MNG-1239

Corrected in SVN

Cheers,

Vincent

> -Original Message-
> From: Jørgen Solberg [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 20, 2005 7:03 AM
> To: users@maven.apache.org
> Subject: Problems with maven-project-info-reports-plugin
> 
> Seems like it's still a problem with the plugin.
>   [ERROR] FATAL ERROR
> [INFO]
> -
> ---
> [INFO] Can't find bundle for base name project-info-report, locale no_NO
> [INFO]
> -
> ---
> [INFO] Trace
> java.util.MissingResourceException: Can't find bundle for base name
> project-info
> -report, locale no_NO
> at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle
> .java:804)
> at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:773)
> at java.util.ResourceBundle.getBundle(ResourceBundle.java:661)
> at org.apache.maven.report.projectinfo.CimReport.getBundle(CimReport.jav
> a:260)
> at org.apache.maven.report.projectinfo.CimReport.getName(CimReport.java:
> 80)
> at org.apache.maven.plugins.site.ReportComparator.compare(ReportComparat
> or.java:40)
> at java.util.Arrays.mergeSort(Arrays.java:1278)
> at java.util.Arrays.mergeSort(Arrays.java:1289)
> at java.util.Arrays.sort(Arrays.java:1219)
> at java.util.Collections.sort(Collections.java:155)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:239)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:399)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:519)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:469)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:448)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:301)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:268)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:137)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> 
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> -
> ---
> [INFO] Total time: 9 seconds
> [INFO] Finished at: Thu Oct 20 12:45:00 CEST 2005
> [INFO] Final Memory: 6M/12M
> [INFO]
> -
> ---


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [m2] Help! Getting started with plugins

[Vincent Siveton]

Hi Kevin,

> OK, following the instructions I got it built and deployed to my local
> repository. However, the only way I could get it to run was to type:
> 
>   m2 sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi
> or
>   m2 sample.plugin:maven-hello-plugin:sayhi
> 
> I tried updating my settings.xml (~/.m2/settings.xml I presume)

You right.

> 
>   
> sample.plugin
>   
> 
> 
> but I could not get
>   m2 hello:sayhi
> to work

Works for me. Try the following:
#m2 clean install hello:sayhi

HTH

Cheers,

Vincent


> 
> 
> maven-hello-plugin> m2 hello:sayhi
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'hello'.
> [INFO]
> --
> --
> [ERROR] BUILD ERROR
> [INFO]
> --
> --
> [INFO] The plugin 'org.apache.maven.plugins:maven-hello-plugin' does not
> exist or no valid version could be found
> [INFO]
> --
> --
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> --
> --
> [INFO] Total time: 1 second
> [INFO] Finished at: Mon Oct 17 14:19:49 MEST 2005
> [INFO] Final Memory: 1M/4M
> [INFO]
> --
> --
> 
> 
> Any help appreciated,
> Kevin
> 
> 
> PS. Is this the only way to write plugins? Is Marmalade dead?
> 
> 
> 
> 
> -Original Message-
> From: Vincent Siveton [mailto:[EMAIL PROTECTED]
> Sent: 17 October 2005 13:01
> To: 'Maven Users List'
> Subject: RE: [m2] Help! Getting started with plugins
> 
> Hi Kevin,
> 
> Have a look on this following:
> http://www.codehaus.org/~jvanzyl/maven2/guides/plugin/guide-java-plugin-
> deve
> lopment.html
> Thanks Jason to work on m2 documentation.
> 
> HTH
> 
> Cheers,
> 
> Vincent
> 
> > -Original Message-
> > From: Kevin McNamee [mailto:[EMAIL PROTECTED]
> > Sent: Monday, October 17, 2005 6:39 AM
> > To: 'Maven Users List'
> > Subject: [m2] Help! Getting started with plugins
> >
> > Hi,
> >
> >
> >
> > I have been trying to create a plugin for Maven 2 without much success.
> >
> >
> >
> > I have looked at the following links for help:
> >
> > http://www.onjava.com/pub/a/onjava/2004/03/17/maven.html?page=1   (Maven
> > 1)
> >
> > http://maven.apache.org/maven2/developers/plugin-development-guide.html
> > (Maven 2 - empty)
> >
> > http://maven.apache.org/maven2/developers/developing-plugins-with-
> > marmalade.
> > html  (Marmalade - doesn't seem to work)
> >
> >
> >
> > All I need is a working "Hello World" example that preferably does not
> > involve writing Java.
> >
> > My goal is to encapsulate some of our Ant functionality with a plugin.
> >
> >
> >
> > Much appreciated,
> >
> > Kevin
> >
> >
> 
> 
> 
> 
> -
> 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]