[jira] Closed: (MNG-2564) J2EE is now called Java EE
[ http://jira.codehaus.org/browse/MNG-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2564. Assignee: Vincent Siveton Resolution: Won't Fix > J2EE is now called Java EE > -- > > Key: MNG-2564 > URL: http://jira.codehaus.org/browse/MNG-2564 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: Guides >Affects Versions: 2.0.4 > Environment: Maven 2 Web Site >Reporter: Markus KARG >Assignee: Vincent Siveton >Priority: Trivial > Fix For: Documentation Deficit > > > The Maven 2 Web Site contains tips on naming Sun's technologies: > http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html > It contains the following line: > J2EE javax.j2ee j2ee > Actually Sun's Bill SHANNON (= Spec Lead of Java EE 5) told me that "they" (= > Reference Implementation team aka "Glassfish" team) are working on publishing > a javaee.jar (= open sourced APIs) as a Maven 2 project. In that context he > said, that the abbreviation "J2EE" is obsolete and the often seen "JEE" > abbreviation in fact is disliked (or let's say: forbidden). Since the > official release of "Java Enterprise Edition v5", the official abbreviation > is "Jave EE". > So I want to suggest that the above-mentioned document gets changed to > contain the following line from now on: > JavaEE javax.javaee javaee -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2540) M2 website : move content of "Examples" link to "Guides" link.
[ http://jira.codehaus.org/browse/MNG-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2540. Assignee: Vincent Siveton Resolution: Fixed added in the "Plugin Developers Centre" > M2 website : move content of "Examples" link to "Guides" link. > -- > > Key: MNG-2540 > URL: http://jira.codehaus.org/browse/MNG-2540 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: General >Reporter: Davy Toch >Assignee: Vincent Siveton >Priority: Minor > Fix For: Documentation Deficit > > > On http://maven.apache.org/examples/index.html there is only one example > "Injecting POM properties via settings.xml", which could be put on : > http://maven.apache.org/guides/index.html > This would allow the 'examples' link in the left menu to be deleted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-1582) Add how to convert pregoals and postgoals to lifecycle to the m1-m2 guide
[ http://jira.codehaus.org/browse/MNG-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-1582. Assignee: Vincent Siveton Resolution: Fixed added this link > Add how to convert pregoals and postgoals to lifecycle to the m1-m2 guide > - > > Key: MNG-1582 > URL: http://jira.codehaus.org/browse/MNG-1582 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: Guides >Affects Versions: 2.0 >Reporter: Carlos Sanchez >Assignee: Vincent Siveton > Fix For: Documentation Deficit > > > guide to convert pregoals and postgoals to lifecycle > give a pointer to the integration test that covers lifecycle as a example -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1304) Create a standard versioning document
[ http://jira.codehaus.org/browse/MNG-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119436 ] Vincent Siveton commented on MNG-1304: -- Here are some links: http://apr.apache.org/versioning.html http://xstream.codehaus.org/versioning.html http://commons.apache.org/releases/versioning.html http://docs.codehaus.org/display/MAVEN/Versioning > Create a standard versioning document > - > > Key: MNG-1304 > URL: http://jira.codehaus.org/browse/MNG-1304 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: General >Reporter: Jason van Zyl > Fix For: Documentation Deficit > > > We need to document how SNAPSHOTs work and how we move from one version to > another. There are the starts of decent documents in the xstream project and > the commons project at Apache. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2469) Refactor and refine the getting started guide so that you could do it 10 min
[ http://jira.codehaus.org/browse/MNG-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2469. Assignee: Vincent Siveton Resolution: Won't Fix we already have "Getting Started in 30 Minutes", http://maven.apache.org/guides/getting-started/index.html > Refactor and refine the getting started guide so that you could do it 10 min > > > Key: MNG-2469 > URL: http://jira.codehaus.org/browse/MNG-2469 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: Guides >Reporter: Marvin King >Assignee: Vincent Siveton > Fix For: Documentation Deficit > > > "chop up the getting started guide so it is again something you could do in > 10 minutes to get a feel for Maven (perhaps go back to the level of the > original guide). Maybe rename to something else? I used to call it "the 10 > minute test" on Maven 1." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2165) Provide links to release notes on download page, navigation, and README.txt in binaries
[ http://jira.codehaus.org/browse/MNG-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2165. Assignee: Vincent Siveton Resolution: Fixed fixed in r610775 > Provide links to release notes on download page, navigation, and README.txt > in binaries > --- > > Key: MNG-2165 > URL: http://jira.codehaus.org/browse/MNG-2165 > Project: Maven 2 > Issue Type: Task > Components: Documentation: General >Reporter: Anuerin Diaz >Assignee: Vincent Siveton >Priority: Minor > Fix For: Documentation Deficit > > > The downlodable binary distribution of Maven does not include any release > notes which is helpful to people who needs to analyze what exactly has > changed in each version (contrary to the latest and the greatest mindset). It > might be possible to get a list using JIRA but it would be convenient if each > (fix) distribution can include a file listing the major enhancements and bug > fixes similar to the following format: > ver 2.0.2 >- change 1 >- bugfix for bleh > ver 2.0.1 >- enhancement 1 >- new feature > even a listing of the JIRA numbers (and some summary) of the included fixes > and enhancement would be useful in this regard. > Thank you. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-1306) Document the use of https for transport in m2 (wagon)
[ http://jira.codehaus.org/browse/MNG-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-1306. Assignee: Vincent Siveton Resolution: Won't Fix Should be fixed by MNG-1560 > Document the use of https for transport in m2 (wagon) > - > > Key: MNG-1306 > URL: http://jira.codehaus.org/browse/MNG-1306 > Project: Maven 2 > Issue Type: Task > Components: Documentation: General >Reporter: Jason van Zyl >Assignee: Vincent Siveton > Fix For: Documentation Deficit > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-1887) Guide to transforming a maven.xml goal into a plugin
[ http://jira.codehaus.org/browse/MNG-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-1887. Assignee: Vincent Siveton Resolution: Won't Fix just add related links > Guide to transforming a maven.xml goal into a plugin > > > Key: MNG-1887 > URL: http://jira.codehaus.org/browse/MNG-1887 > Project: Maven 2 > Issue Type: New Feature > Components: Documentation: Guides >Affects Versions: 2.0.1 >Reporter: Geoffrey De Smet >Assignee: Vincent Siveton > Fix For: Documentation Deficit > > > Many users coming from maven 1 have large maven.xml files and don't really > know how to start migrating those. > Usually these maven.xml do simple things like copy some files or run an ant > task. > 3 use cases should be shown: > 1) old custom assembly script can now be done by the assembly plugin > 2) some ant task can be done with the antrun plugin > 3) some custom script can be turned into a plugin > You probably don't like solution 2) and it's indeed not the best solution, > like use maven.xml in maven 1 was also not the best solution, > despite that people are doing it to do things quick & dirty or as proofs of > concepts, > so they should be guided (and also be told that 3) is better) > This could become a part of "Guide to Moving from Maven 1.x to Maven 2.x": > http://maven.apache.org/guides/mini/guide-m1-m2.html > But seeing the length of that one, some sort of index would be usefull (like > in FAQ's). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2337) XSLT for converting Maven1 project.xml to Maven2 pom.xml
[ http://jira.codehaus.org/browse/MNG-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2337. Assignee: Vincent Siveton Resolution: Fixed Added in our sandbok https://svn.apache.org/repos/asf/maven/sandbox/trunk/other/m1-m2 > XSLT for converting Maven1 project.xml to Maven2 pom.xml > > > Key: MNG-2337 > URL: http://jira.codehaus.org/browse/MNG-2337 > Project: Maven 2 > Issue Type: Task > Components: Documentation: Guides >Affects Versions: 2.0.4 >Reporter: David Smiley >Assignee: Vincent Siveton >Priority: Minor > Fix For: Documentation Deficit > > Attachments: maven1 project to maven2 pom.xsl > > > Attached is an XSLT script that converts a Maven 1 project.xml to Maven 2 > pom.xml. Please update this page: > http://maven.apache.org/guides/mini/guide-m1-m2.html > to offer this useful script. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNGSITE-11) review and link to POMstrap
[ http://jira.codehaus.org/browse/MNGSITE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119389 ] Vincent Siveton commented on MNGSITE-11: I suggested to add a related software link > review and link to POMstrap > --- > > Key: MNGSITE-11 > URL: http://jira.codehaus.org/browse/MNGSITE-11 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Brett Porter > > http://pomstrap.tigris.org/ > Heard about this a while back - it seems to have matured a bit. Let's you > execute your project from a POM. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNGSITE-1) http://maven.apache.org/pom.html is out of date and broken
[ http://jira.codehaus.org/browse/MNGSITE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNGSITE-1. - Assignee: Vincent Siveton Resolution: Cannot Reproduce already fixed > http://maven.apache.org/pom.html is out of date and broken > -- > > Key: MNGSITE-1 > URL: http://jira.codehaus.org/browse/MNGSITE-1 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Henri Yandell >Assignee: Vincent Siveton > > The links at the top don't work, and the information is dated. For example it > lacks info on dependency->classifier. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNGSITE-9) set up a plugin developer centre
[ http://jira.codehaus.org/browse/MNGSITE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNGSITE-9. - Assignee: Vincent Siveton Resolution: Duplicate > set up a plugin developer centre > > > Key: MNGSITE-9 > URL: http://jira.codehaus.org/browse/MNGSITE-9 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Brett Porter >Assignee: Vincent Siveton > > we should have a specific subsection of the site that deals with issues that > plugin developers would encounter (both at Maven and those who develop them > independantly). Incorporating the cookbook format by slurping in the wiki > would also be particularly helpful here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNGSITE-5) Create a Developers centre
[ http://jira.codehaus.org/browse/MNGSITE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNGSITE-5. - Assignee: Vincent Siveton Resolution: Fixed applied > Create a Developers centre > --- > > Key: MNGSITE-5 > URL: http://jira.codehaus.org/browse/MNGSITE-5 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Vincent Siveton >Assignee: Vincent Siveton > > Already discuss on the dev list by brett and myself -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNGSITE-25) Guide to Mirror Settings - repository size is out of date
[ http://jira.codehaus.org/browse/MNGSITE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNGSITE-25. -- Assignee: Vincent Siveton Resolution: Fixed applied > Guide to Mirror Settings - repository size is out of date > - > > Key: MNGSITE-25 > URL: http://jira.codehaus.org/browse/MNGSITE-25 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Tom Cort >Assignee: Vincent Siveton >Priority: Trivial > Attachments: guide-mirror-settings.apt-repo-size.patch > > > Page: http://maven.apache.org/guides/mini/guide-mirror-settings.html > In the "Creating your own mirror" section at the bottom, it says that a > mirror requires about 10GB of disk space. That number is out of date; it's up > to 16GB now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNGSITE-28) Add a link to Artifactory to the "Introduction to Repositories" guide
[ http://jira.codehaus.org/browse/MNGSITE-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNGSITE-28. -- Assignee: Vincent Siveton Resolution: Fixed done > Add a link to Artifactory to the "Introduction to Repositories" guide > - > > Key: MNGSITE-28 > URL: http://jira.codehaus.org/browse/MNGSITE-28 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Yoav Landman >Assignee: Vincent Siveton > > Could you please add Artifactory (http://artifactory.sourceforge.net/) to the > list of solutions under the "Setting up the Internal Repository" section? > Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2575) republish all plugin documentation using the improved format
[ http://jira.codehaus.org/browse/MNG-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2575. Assignee: Vincent Siveton Resolution: Cannot Reproduce All plugins have been redeployed after November 2006 > republish all plugin documentation using the improved format > > > Key: MNG-2575 > URL: http://jira.codehaus.org/browse/MNG-2575 > Project: Maven 2 > Issue Type: Task > Components: Documentation: General >Reporter: Brett Porter >Assignee: Vincent Siveton > Fix For: Documentation Deficit > > > regardless of whether they have been released, we should get all plugin sites > generated using the corrected version in maven 2.0.5-snapshot to fix the > index page and the format of the plugin documentation and republish them -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2655) Revise Introduction to the Build Lifecycle
[ http://jira.codehaus.org/browse/MNG-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2655. Assignee: Vincent Siveton Resolution: Fixed Applied. Thanks! > Revise Introduction to the Build Lifecycle > -- > > Key: MNG-2655 > URL: http://jira.codehaus.org/browse/MNG-2655 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: Introductions >Reporter: Franz Allan Valencia See >Assignee: Vincent Siveton >Priority: Minor > Fix For: Documentation Deficit > > Attachments: MNG-2655-maven-site.patch > > > * Provide a Table of Contents (the page is too long). > * Enumerate the available lifecycles (default, clean, site). > * Provide references to the list of phases for those lifecycles lifecycles . > * Explain goals and how they relate to the build phases. > * Provide references to the default goal bindings on the build phases. > * Explain what plugins are and how they relate to goals > * Transfer the "...For developers" section to Guide to Java Plugin > Development. Users don't need to know tihs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2954) Docu incomplete: "Guide to uploading artifacts to the Central Repository": Jira project not specified, Attachment usage unclear
[ http://jira.codehaus.org/browse/MNG-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2954. Assignee: Vincent Siveton Resolution: Fixed Fixed in r610625 > Docu incomplete: "Guide to uploading artifacts to the Central Repository": > Jira project not specified, Attachment usage unclear > > > Key: MNG-2954 > URL: http://jira.codehaus.org/browse/MNG-2954 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: Guides >Reporter: Stefan Prange >Assignee: Vincent Siveton >Priority: Minor > Fix For: Documentation Deficit > > > Hi, > 1) the "Guide to uploading artifacts to the Central Repository" > (http://maven.apache.org/guides/mini/guide-central-repository-upload.html) > says, that upload requests have to be made as Jira issues using the URL > http://jira.codehaus.org/secure/CreateIssue.jspa?pid=10367&issuetype=3. > Under this URL one has to choose a Project and an Issue Type. It would be > great if the guide could say which project and issue type to choose. > I suppose that project is "maven-upload-requests" and issue type is wish, but > I'm not sure. > 2) the guide says that new bundles have to be downloadable via a URL which > has to be entered into the Jira issue. > But Jira also offers the possibility to add an attachment to the issue (up to > 10MB). It would be nice, if the guide could clarify on this possibilty, > either that using attachments is equal to download urls (then the url doesn't > have to be a mandatory field any more) or that attachments added to the issue > will be ignored. > Kind regards, Stefan Prange -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2769) Use of POM namespace is confused and confusing in both the code and the documentation
[ http://jira.codehaus.org/browse/MNG-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2769. Assignee: Vincent Siveton Resolution: Fixed Fixed this page in r610540 > Use of POM namespace is confused and confusing in both the code and the > documentation > - > > Key: MNG-2769 > URL: http://jira.codehaus.org/browse/MNG-2769 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Documentation: Guides, > General, POM >Affects Versions: 2.0.4 >Reporter: Nigel Magnay >Assignee: Vincent Siveton >Priority: Minor > Fix For: Documentation Deficit > > > Looking at the (very good) documentation on the POM at > http://maven.apache.org/pom.html, the very first link is to the POM XSD, the > schema definition for the XML. This XSD explicitly places POMs into the > namespace targetNamespace="http://maven.apache.org/POM/4.0.0";. > However, the immediately following examples of POMs do not place their > examples inside this namespace (there should be an > xmlns="http://maven.apache.org/POM/4.0.0"; at the root element). > Taking a look through my local repository, it's all a bit hit-and-miss as to > whether the defined POM is in the correct namespace or not. > This is really annoying, because any tools I write that wish to use standard > XML parsers to consume the POM need, in effect, to pass a namespace manager > around, because if I wish to XPath to 'dependencies', I have to say 'is this > //pom:dependencies, or is it a "defective" POM, where it's just > //dependencies. This is bad if I'm using XSLT too (as one might to display a > 'prettyprinted' POM). > * The documentation should use the namespace > * Maven should probably warn when it meets a POM that it's compiling from > contains information in an invalid namespace. > * Maven should re-namespace POMs to be in the 'right' namespace when copying > to repositories (or perhaps modify any POM.xml that it sees which is > incorrect automatically). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-41) best practices: site management
[ http://jira.codehaus.org/browse/MNG-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119320 ] Vincent Siveton commented on MNG-41: >From dev@ http://www.nabble.com/Publishing-Plugin-Sites-(was:-Re:-Plugins-sandbox-site)-td13044546s177.html > best practices: site management > --- > > Key: MNG-41 > URL: http://jira.codehaus.org/browse/MNG-41 > Project: Maven 2 > Issue Type: Task > Components: Design, Patterns & Best Practices >Reporter: Jason van Zyl >Priority: Trivial > Fix For: Documentation Deficit > > > * How to deal with multiple versions of the site > * How to deal with staging directories for the site (will require a change to > the POM) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2170) Packaged Maven Documentation for Download
[ http://jira.codehaus.org/browse/MNG-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2170. Assignee: Vincent Siveton Resolution: Fixed fixed in r610492 Need to redeploy the website. > Packaged Maven Documentation for Download > - > > Key: MNG-2170 > URL: http://jira.codehaus.org/browse/MNG-2170 > Project: Maven 2 > Issue Type: Wish > Components: Documentation: General > Environment: all environments >Reporter: Hans Baier >Assignee: Vincent Siveton > Fix For: Documentation Deficit > > > Hello, > I am sorely missing packaged maven documentation for download > on the maven project site. > Every time I want to look something up, > I have to go online. > Thank you for the great software! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2556) downloadable docs
[ http://jira.codehaus.org/browse/MNG-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2556. Assignee: Vincent Siveton Resolution: Duplicate > downloadable docs > - > > Key: MNG-2556 > URL: http://jira.codehaus.org/browse/MNG-2556 > Project: Maven 2 > Issue Type: Wish > Components: Documentation: General >Reporter: Michael Stevens >Assignee: Vincent Siveton >Priority: Minor > Fix For: Documentation Deficit > > > A downloadable package of maven documentation would be nice. > This is obviously total wishlist :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2594) faq links
[ http://jira.codehaus.org/browse/MNG-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2594. Assignee: Vincent Siveton Resolution: Cannot Reproduce Cannot reproduce > faq links > - > > Key: MNG-2594 > URL: http://jira.codehaus.org/browse/MNG-2594 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: Faqs >Reporter: Luis Parravicini >Assignee: Vincent Siveton >Priority: Minor > Fix For: Documentation Deficit > > > The links in http://maven.apache.org/faq.html are displayed as "[text|url]" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2392) document
[ http://jira.codehaus.org/browse/MNG-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2392. Assignee: Vincent Siveton Resolution: Fixed Already fixed with r372499 > document > > > Key: MNG-2392 > URL: http://jira.codehaus.org/browse/MNG-2392 > Project: Maven 2 > Issue Type: Task > Components: Documentation: General >Reporter: Brett Porter >Assignee: Vincent Siveton > Fix For: Documentation Deficit > > > see: http://mail-archives.apache.org/mod_mbox/maven-users/200511.mbox/[EMAIL > PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2519) Need samples and more extensive documentation conserning settings and pom files
[ http://jira.codehaus.org/browse/MNG-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2519. Assignee: Vincent Siveton Resolution: Won't Fix These files are only references, not documentation. > Need samples and more extensive documentation conserning settings and pom > files > --- > > Key: MNG-2519 > URL: http://jira.codehaus.org/browse/MNG-2519 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: General, POM, Settings >Reporter: Ronny Naess >Assignee: Vincent Siveton > Fix For: Documentation Deficit > > > I think maven is a nice tool, but the documentation lacks many places. I have > worked a lot with ANT from earlier and I must say that one of the best parts > about Ant is the documentation. Each Ant task is very well documentet. Each > attribute is documentet with a description and required field. In addition to > being followed by one or more samples. You can in most cases just copy and > paste the tasks right out of the documentation and in to your build.xml with > little or no modification. > Compare Ants http://ant.apache.org/manual/coretasklist.html with > http://maven.apache.org/ref/2.0.4/maven-model/maven.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2143) Proposition of documentation
[ http://jira.codehaus.org/browse/MNG-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2143. Assignee: Vincent Siveton Resolution: Won't Fix seems to be out of date > Proposition of documentation > > > Key: MNG-2143 > URL: http://jira.codehaus.org/browse/MNG-2143 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: General >Reporter: Raphaël Piéroni >Assignee: Vincent Siveton > Fix For: Documentation Deficit > > Attachments: AdvancedDocumentation.apt, Categories.txt, MainPage.apt > > > Here attached are 2 apt file that describe a first attempt to refactor the > maven documentation site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-1500) document the running of a single test or group of tests using the -Dtest=FooTest option
[ http://jira.codehaus.org/browse/MNG-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-1500. Assignee: Vincent Siveton (was: Jason van Zyl) Resolution: Fixed patch applied. Thanks! > document the running of a single test or group of tests using the > -Dtest=FooTest option > --- > > Key: MNG-1500 > URL: http://jira.codehaus.org/browse/MNG-1500 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: Guides >Reporter: Jason van Zyl >Assignee: Vincent Siveton > Fix For: Documentation Deficit > > Attachments: general.fml.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1582) Add how to convert pregoals and postgoals to lifecycle to the m1-m2 guide
[ http://jira.codehaus.org/browse/MNG-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119223 ] Vincent Siveton commented on MNG-1582: -- http://www.nabble.com/using-preGoal-and-postGoal-in-m2--td1151533s177.html > Add how to convert pregoals and postgoals to lifecycle to the m1-m2 guide > - > > Key: MNG-1582 > URL: http://jira.codehaus.org/browse/MNG-1582 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: Guides >Affects Versions: 2.0 >Reporter: Carlos Sanchez > Fix For: Documentation Deficit > > > guide to convert pregoals and postgoals to lifecycle > give a pointer to the integration test that covers lifecycle as a example -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MRELEASE-312) CVS examples in guide to using release plugin
[ http://jira.codehaus.org/browse/MRELEASE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-1871 to MRELEASE-312: --- Fix Version/s: (was: Documentation Deficit) Component/s: (was: Documentation: Guides) scm Key: MRELEASE-312 (was: MNG-1871) Project: Maven 2.x Release Plugin (was: Maven 2) > CVS examples in guide to using release plugin > - > > Key: MRELEASE-312 > URL: http://jira.codehaus.org/browse/MRELEASE-312 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: scm >Reporter: Miguel Griffa > > Guide to using release plugin should include examples for CVS as well as SVN -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2710) Consider adding id element under Contributor
[ http://jira.codehaus.org/browse/MNG-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MNG-2710: - Fix Version/s: (was: Documentation Deficit) 2.1-alpha-1 Component/s: (was: Documentation: General) POM Need to review it for 2.1 > Consider adding id element under Contributor > > > Key: MNG-2710 > URL: http://jira.codehaus.org/browse/MNG-2710 > Project: Maven 2 > Issue Type: New Feature > Components: POM > Environment: >ver > Microsoft Windows XP [Version 5.1.2600] > >mvn -v > Maven version: 2.0.4 > >java -version > java version "1.6.0" > Java(TM) SE Runtime Environment (build 1.6.0-b105) > Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing) >Reporter: Reshat Sabiq >Priority: Minor > Fix For: 2.1-alpha-1 > > > In my case, i just don't want to put name under code i didn't write, though i > did have an ID. > Could also be an apache committer contributing to a different project, so > pretty fair idea. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2783) Maven Guide to EARs describes WAR projects
[ http://jira.codehaus.org/browse/MNG-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2783. Assignee: Vincent Siveton Resolution: Fixed Deleted the file http://maven.apache.org/guides/mini/guide-ear.html > Maven Guide to EARs describes WAR projects > -- > > Key: MNG-2783 > URL: http://jira.codehaus.org/browse/MNG-2783 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: Guides >Reporter: Shelley Baker >Assignee: Vincent Siveton >Priority: Minor > Fix For: Documentation Deficit > > > The "Maven - Guide to EARs" [1] describes creation of an EAR project using a > non-existent "maven-archetype-ear" and further describes the output of the > ear archetype creation as a WAR. It appears that the "Guide to EARs" is > nearly an exact copy of the "Guide to Webapps" [2]. > [1] http://maven.apache.org/guides/mini/guide-ear.html > [2] http://maven.apache.org/guides/mini/guide-webapp.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2808) Anchors on maven.apache.org are broken
[ http://jira.codehaus.org/browse/MNG-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2808. Assignee: Vincent Siveton Resolution: Cannot Reproduce cannot reproduce > Anchors on maven.apache.org are broken > -- > > Key: MNG-2808 > URL: http://jira.codehaus.org/browse/MNG-2808 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting > Environment: Both Firefox 2 and IE 7.0 >Reporter: Alexander Dotor >Assignee: Vincent Siveton >Priority: Minor > Fix For: Reviewed Pending Version Assignment > > > The anchors for on-page-navigation on maven.apache.org are broken. The > href-attrivbute contains uppercase letters at the beginning and blanks > between words. The name-Attribute of the appropriate anchors is in lowercase > and containts underscores instead of blanks. > This makes it extremly difficult to navigate the POM-Reference for example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2809) Can't activate a profile by checking for the presence of a file in ${user.home}
[
http://jira.codehaus.org/browse/MNG-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNG-2809.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.1-alpha-1
2.0.9
Fixed with r609976
> Can't activate a profile by checking for the presence of a file in
> ${user.home}
> ---
>
> Key: MNG-2809
> URL: http://jira.codehaus.org/browse/MNG-2809
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.0.4
>Reporter: Mark Proctor
>Assignee: Vincent Siveton
> Fix For: 2.0.9, 2.1-alpha-1
>
>
> The following won't activate. If I move it to a path without a space it
> works. This is for windows xp.
> ${user.home}/.m2/ydoc/lib/ydoc.jar
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2814) OS name is only detected if lower cased
[
http://jira.codehaus.org/browse/MNG-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNG-2814.
Assignee: Vincent Siveton
Resolution: Cannot Reproduce
Already fixed by PLXUTILS-3 for Maven >= 2.0.6
> OS name is only detected if lower cased
> ---
>
> Key: MNG-2814
> URL: http://jira.codehaus.org/browse/MNG-2814
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.0.4
>Reporter: Graham Leggett
>Assignee: Vincent Siveton
> Fix For: Reviewed Pending Version Assignment
>
>
> The following profile does not activate on MacosX:
>
> activate-mac
>
>
> Mac OS X
>
>
>
> "Mac OS X" matches the value returned when querying ${os.name}.
> If you lowercase the name, the profile is activated:
>
> activate-mac
>
>
> mac os x
>
>
>
> This is counter intuitive, as one would expect the exact cut and pasted
> (capitalised) ${os.name} value to work as an OS name in a profile.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2848) Environment variables in profile activation not working
[
http://jira.codehaus.org/browse/MNG-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNG-2848.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.1-alpha-1
2.0.9
Patch applied in r609944. Thanks!
> Environment variables in profile activation not working
> ---
>
> Key: MNG-2848
> URL: http://jira.codehaus.org/browse/MNG-2848
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.0.4, 2.0.5
> Environment: Windows XP Professional, JDK 1.5
>Reporter: Muhammad Alsebaey
>Assignee: Vincent Siveton
> Fix For: 2.0.9, 2.1-alpha-1
>
> Attachments: MNG-2848.patch
>
>
> When using an environment variable as a profile activation variable, it
> doesnt work, using either env.X or ${env.X} doesnt work.
> I found the same issue on the forums unresolved.
> http://www.nabble.com/profile-activation-based-on-environment-variables-tf2585492s177.html#a7208580
> Basically, the following doesnt work, where FOO is a windows environment
> variable (like PATH for example) :
> {code:xml}
>
> haroon-workstation
>
>
> env.FOO
> foo
>
>
> ...
>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2849) nonProxyHosts element's value separator
[ http://jira.codehaus.org/browse/MNG-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2849. Assignee: Vincent Siveton Resolution: Cannot Reproduce Already fixed by r426263 and r426268 http://maven.apache.org/ref/current/maven-settings/settings.html#class_proxy > nonProxyHosts element's value separator > > > Key: MNG-2849 > URL: http://jira.codehaus.org/browse/MNG-2849 > Project: Maven 2 > Issue Type: Wish > Components: Sites & Reporting >Affects Versions: 2.0.5 >Reporter: Sang-Jea Shin >Assignee: Vincent Siveton >Priority: Trivial > Fix For: Reviewed Pending Version Assignment > > > According to this article proxy separator is "|". > http://maven.apache.org/guides/mini/guide-proxies.html > But according to this article, separator is ",". > http://maven.apache.org/ref/2.0.4/maven-settings/settings.html > Which one is correct? > Or both works? > I wish to correct these description. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-286) [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
[ http://jira.codehaus.org/browse/MSITE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MSITE-286. - Assignee: Vincent Siveton Resolution: Duplicate Duplicate MSITE-170 Fixed in maven-site-plugin:2.0-beta-6 > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > > > Key: MSITE-286 > URL: http://jira.codehaus.org/browse/MSITE-286 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: christian-Luc Houze >Assignee: Vincent Siveton >Priority: Minor > Fix For: 2.0-beta-6 > > > I always get the error below: > [INFO] Velocimacro : initialization starting. > [INFO] Velocimacro : adding VMs from VM library template : > VM_global_library.vm > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > [INFO] Velocimacro : error using VM library template VM_global_library.vm : > org.apache.velocity.exception.ResourceNotFoundException: Unable to find > resource 'VM_global_library.vm' > [INFO] Velocimacro : VM library template macro registration complete. > this does not seem to affectr my builds or sites generation > is this normal/abnormal. > what should i do so that i get rid of this, and that my manager does not feel > bad about a product that throws errors even if final result seems ok :-) > thanks, > Christian-Luc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MSITE-286) [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
[ http://jira.codehaus.org/browse/MSITE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-2910 to MSITE-286: Affects Version/s: (was: 2.0.4) 2.0-beta-5 Fix Version/s: (was: Reviewed Pending Version Assignment) 2.0-beta-6 Component/s: (was: Errors) Key: MSITE-286 (was: MNG-2910) Project: Maven 2.x Site Plugin (was: Maven 2) > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > > > Key: MSITE-286 > URL: http://jira.codehaus.org/browse/MSITE-286 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: christian-Luc Houze >Priority: Minor > Fix For: 2.0-beta-6 > > > I always get the error below: > [INFO] Velocimacro : initialization starting. > [INFO] Velocimacro : adding VMs from VM library template : > VM_global_library.vm > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > [INFO] Velocimacro : error using VM library template VM_global_library.vm : > org.apache.velocity.exception.ResourceNotFoundException: Unable to find > resource 'VM_global_library.vm' > [INFO] Velocimacro : VM library template macro registration complete. > this does not seem to affectr my builds or sites generation > is this normal/abnormal. > what should i do so that i get rid of this, and that my manager does not feel > bad about a product that throws errors even if final result seems ok :-) > thanks, > Christian-Luc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3135) Enable skipping clean:clean goal in verifier
[ http://jira.codehaus.org/browse/MNG-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3135. Assignee: Vincent Siveton Resolution: Fixed applied with the Maven code style (609582) > Enable skipping clean:clean goal in verifier > > > Key: MNG-3135 > URL: http://jira.codehaus.org/browse/MNG-3135 > Project: Maven 2 > Issue Type: Improvement > Components: integration tests >Affects Versions: Shared Components >Reporter: Arnaud Bailly >Assignee: Vincent Siveton >Priority: Trivial > Fix For: Shared Components > > Attachments: autoclean.patch > > > WHen using maven-verifier, clean:clean goal is automatically added at the > start of the execution of the plugin. The attached patch simply adds an > autoclean property to the verifier that is 'true' by default but may be unset. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3145) StringIndexOutOfBoundsException in AbstractMavenReportRenderer
[
http://jira.codehaus.org/browse/MNG-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNG-3145.
Assignee: Vincent Siveton
Resolution: Fixed
Fixed in r609579
For the next time, please provide us a patch.
http://maven.apache.org/guides/development/guide-m2-development.html#Creating_and_submitting_a_patch
> StringIndexOutOfBoundsException in AbstractMavenReportRenderer
> --
>
> Key: MNG-3145
> URL: http://jira.codehaus.org/browse/MNG-3145
> Project: Maven 2
> Issue Type: Bug
> Components: Sites & Reporting
>Affects Versions: 2.0.6
>Reporter: Thomas Krammer
>Assignee: Vincent Siveton
> Fix For: Shared Components
>
>
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1768)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.applyPattern(AbstractMavenReportRenderer.java:598)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.linkPatternedText(AbstractMavenReportRenderer.java:353)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.tableCell(AbstractMavenReportRenderer.java:213)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.tableCell(AbstractMavenReportRenderer.java:193)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.tableRow(AbstractMavenReportRenderer.java:225)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderDependenciesForScope(DependenciesReport.java:318)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderBody(DependenciesReport.java:228)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:97)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:67)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:239)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.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(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> 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: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)
> When you look at the code it seems like a copy/paste error:
> String subString = text.substring(
> lastOffset, i );
> lastOffset = i + 1;
> int lastComma = subString.lastIndexOf( "," );
> if ( lastComma != -1 )
> {
> segments.put( subString.substring( 0,
> lastComma ).trim(),
> subString.substring(
> lastComma + 1 ).trim() );
> }
> else
> {
> segments.put( subString.substring( 0,
> lastComma ).trim(), null );
> }
> I guess the last
[jira] Closed: (MNG-2925) NullPointerException in PluginDescriptor.getMojo() if there's no mojo in pom.xml
[
http://jira.codehaus.org/browse/MNG-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNG-2925.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.1-alpha-1
2.0.9
Applied in r609576
For the next time, please provide us a patch.
http://maven.apache.org/guides/development/guide-m2-development.html#Creating_and_submitting_a_patch
> NullPointerException in PluginDescriptor.getMojo() if there's no mojo in
> pom.xml
>
>
> Key: MNG-2925
> URL: http://jira.codehaus.org/browse/MNG-2925
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API
>Affects Versions: 2.0.5
>Reporter: Kohsuke Kawaguchi
>Assignee: Vincent Siveton
> Fix For: 2.0.9, 2.1-alpha-1
>
>
> The getMojo method fails with NPE because getMojos() method returns null.
> This happens when there's no mojo in the plugin.
> The code should be modified to check for this situation, like this:
> {code}
> public MojoDescriptor getMojo( String goal )
> {
> List mojos = getMojos();
> if(mojos==null) return null; // no mojo in this POM
> MojoDescriptor mojoDescriptor = null;
> for ( Iterator i = mojos.iterator(); i.hasNext() && mojoDescriptor ==
> null; )
> {
> MojoDescriptor desc = (MojoDescriptor) i.next();
> if ( goal.equals( desc.getGoal() ) )
> {
> mojoDescriptor = desc;
> }
> }
> return mojoDescriptor;
> }
> {/code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2953) Wrong link on http://docs.codehaus.org/display/MAVEN/How+To+Help
[ http://jira.codehaus.org/browse/MNG-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2953. Assignee: Vincent Siveton Resolution: Fixed Fixed > Wrong link on http://docs.codehaus.org/display/MAVEN/How+To+Help > - > > Key: MNG-2953 > URL: http://jira.codehaus.org/browse/MNG-2953 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: Guides >Reporter: Mario Hochreiter >Assignee: Vincent Siveton >Priority: Minor > Fix For: Documentation Deficit > > > There is an incorrect link on the > http://docs.codehaus.org/display/MAVEN/How+To+Help wiki site to > http://maven.apache.org/maven2/development/development-guide.html which > seems no longer to exist. > I think the correct link should be: > http://maven.apache.org/guides/development/guide-m2-development.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2964) Need documentation about Maven2 logging
[ http://jira.codehaus.org/browse/MNG-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2964. Assignee: Vincent Siveton Resolution: Fixed added a new FAQ entry in r609355 > Need documentation about Maven2 logging > --- > > Key: MNG-2964 > URL: http://jira.codehaus.org/browse/MNG-2964 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: Faqs >Affects Versions: 2.0.5 >Reporter: Tano Dzhinski >Assignee: Vincent Siveton > Fix For: Documentation Deficit > > > How to set message level for maven2 output? (it always shows INFO level > messages) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2983) Wrong anchors on guide web pages
[ http://jira.codehaus.org/browse/MNG-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2983. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: (was: Reviewed Pending Version Assignment) Documentation Deficit Already fixed at least with r609137 > Wrong anchors on guide web pages > > > Key: MNG-2983 > URL: http://jira.codehaus.org/browse/MNG-2983 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Reporter: David Balaic >Assignee: Vincent Siveton >Priority: Minor > Fix For: Documentation Deficit > > > The web pages, like http://maven.apache.org/guides/getting-started/index.html > have all the anchors wrong. > Example, the link "What is Maven?" has the value > http://maven.apache.org/guides/getting-started/index.html#What%20is%20Maven? > while the anchor is named "what_is_maven" so the correct link would be > http://maven.apache.org/guides/getting-started/index.html#what_is_maven > It is the same with all links on that page and also on other pages, like : > http://maven.apache.org/run-maven/index.html > http://maven.apache.org/settings.html > etc (I guess all of them) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3120) Documentation how to use org.apache.maven.monitor.logging.Log
[
http://jira.codehaus.org/browse/MNG-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNG-3120.
Resolution: Won't Fix
Fix Version/s: (was: 2.0.x)
reopen to fix as wont fix
> Documentation how to use org.apache.maven.monitor.logging.Log
> -
>
> Key: MNG-3120
> URL: http://jira.codehaus.org/browse/MNG-3120
> Project: Maven 2
> Issue Type: Wish
>Reporter: Tano Dzhinski
>Assignee: Vincent Siveton
>
> private Log log = this.getLog();
>
> public void execute() throws MojoExecutionException {
> log.info("message");
> log.debug("message");
> log.warn("message");
> log.error("message");
> ...
> This code always shows all four messages
> How can I define the loggig level?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MNG-3120) Documentation how to use org.apache.maven.monitor.logging.Log
[
http://jira.codehaus.org/browse/MNG-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton reopened MNG-3120:
--
> Documentation how to use org.apache.maven.monitor.logging.Log
> -
>
> Key: MNG-3120
> URL: http://jira.codehaus.org/browse/MNG-3120
> Project: Maven 2
> Issue Type: Wish
>Reporter: Tano Dzhinski
>Assignee: Vincent Siveton
>
> private Log log = this.getLog();
>
> public void execute() throws MojoExecutionException {
> log.info("message");
> log.debug("message");
> log.warn("message");
> log.error("message");
> ...
> This code always shows all four messages
> How can I define the loggig level?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3120) Documentation how to use org.apache.maven.monitor.logging.Log
[
http://jira.codehaus.org/browse/MNG-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNG-3120.
Assignee: Vincent Siveton
Resolution: Fixed
It is a pitfall. Have a glance to the doc or MNG-3273
> Documentation how to use org.apache.maven.monitor.logging.Log
> -
>
> Key: MNG-3120
> URL: http://jira.codehaus.org/browse/MNG-3120
> Project: Maven 2
> Issue Type: Wish
>Reporter: Tano Dzhinski
>Assignee: Vincent Siveton
> Fix For: 2.0.x
>
>
> private Log log = this.getLog();
>
> public void execute() throws MojoExecutionException {
> log.info("message");
> log.debug("message");
> log.warn("message");
> log.error("message");
> ...
> This code always shows all four messages
> How can I define the loggig level?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3156) NullPointerException with mvn dependency:sources
[ http://jira.codehaus.org/browse/MNG-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3156. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: (was: 2.0.x) 2.1-alpha-1 2.0.9 The fix is already present on branch and trunk (r609337) > NullPointerException with mvn dependency:sources > > > Key: MNG-3156 > URL: http://jira.codehaus.org/browse/MNG-3156 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.7 >Reporter: Sam Imari >Assignee: Vincent Siveton > Fix For: 2.0.9, 2.1-alpha-1 > > Attachments: pom.xml > > > I got a NPE when I use mvn dependency:sources to download all the sources for > my appfuse M5 project: > $ mvn -e -U dependency:sources > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'dependency'. > [INFO] org.apache.maven.plugins: checking for updates from appfuse > [INFO] org.apache.maven.plugins: checking for updates from central > [INFO] org.codehaus.mojo: checking for updates from appfuse > [INFO] org.codehaus.mojo: checking for updates from central > [INFO] artifact org.apache.maven.plugins:maven-dependency-plugin: checking > for updates from appfuse > [INFO] artifact org.apache.maven.plugins:maven-dependency-plugin: checking > for updates from central > [INFO] > > [INFO] Building AppFuse Struts 2 Application > [INFO]task-segment: [dependency:sources] > [INFO] > > Downloading: > http://repo1.maven.org/maven2/org/codehaus/xfire/bcprov-jdk15/133/bcprov-jdk15-133.pom > Downloading: > http://static.appfuse.org/repository/org/codehaus/xfire/bcprov-jdk15/133/bcprov-jdk15-133.pom > Downloading: > http://repo1.maven.org/maven2/xml-security/xmlsec/1.3.0/xmlsec-1.3.0.pom > Downloading: > http://static.appfuse.org/repository/xml-security/xmlsec/1.3.0/xmlsec-1.3.0.pom > Downloading: http://repo1.maven.org/maven2/wss4j/wss4j/1.5.1/wss4j-1.5.1.pom > Downloading: > http://static.appfuse.org/repository/wss4j/wss4j/1.5.1/wss4j-1.5.1.pom > Downloading: > http://repo1.maven.org/maven2/xfire/saaj-impl/1.3/saaj-impl-1.3.pom > Downloading: > http://static.appfuse.org/repository/xfire/saaj-impl/1.3/saaj-impl-1.3.pom > [INFO] [dependency:sources] > Downloading: http://repo1.maven.org/maven2/ant/ant/1.5/ant-1.5-sources.jar > Downloading: > http://static.appfuse.org/repository/ant/ant/1.5/ant-1.5-sources.jar > Downloading: http://repo1.maven.org/maven2/asm/asm/1.5.3/asm-1.5.3-sources.jar > Downloading: > http://static.appfuse.org/repository/asm/asm/1.5.3/asm-1.5.3-sources.jar > Downloading: > http://repo1.maven.org/maven2/asm/asm-attrs/1.5.3/asm-attrs-1.5.3-sources.jar > Downloading: > http://static.appfuse.org/repository/asm/asm-attrs/1.5.3/asm-attrs-1.5.3-sources.jar > Downloading: > http://repo1.maven.org/maven2/aspectj/aspectjweaver/1.5.3/aspectjweaver-1.5.3-sources.jar > Downloading: > http://static.appfuse.org/repository/aspectj/aspectjweaver/1.5.3/aspectjweaver-1.5.3-sources.jar > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:92) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:73) > at > org.apache.maven.plugin.dependency.utils.resolvers.DefaultArtifactsResolver.resolve(DefaultArtifactsResolver.java:81) > at > org.apache.maven.plugin.dependency.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies(AbstractDependencyFilterMojo.java:308) > at > org.apache.maven.plugin.dependency.AbstractDependencyFilterMojo.getDependencySets(AbstractDependencyFilterMojo.java:265) > at > org.apache.maven.plugin.dependency.resolvers.ResolveDependencySourcesMojo.execute(ResolveDependencySourcesMojo.java:69) > 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(Defau
[jira] Closed: (MNG-3213) Please update to plexus-utils 1.4.3 or later for PLXUTILS-36
[ http://jira.codehaus.org/browse/MNG-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3213. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: (was: 2.0.x) 2.0.8 Already fixed in mvn 2.0.8 with plexus-utils:1.4.6 If a given maven project doesn't use it yet, please open another issue for the given project. > Please update to plexus-utils 1.4.3 or later for PLXUTILS-36 > > > Key: MNG-3213 > URL: http://jira.codehaus.org/browse/MNG-3213 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Max Bowsher >Assignee: Vincent Siveton > Fix For: 2.0.8 > > > Please update to plexus-utils 1.4.3 or later to get the fix for PLXUTILS-36. > This is a fairly minor bug, but the failure mode is extremely puzzling and > quite difficult to debug if you have not seen it before. > The problem is that, if an envvar with a single-character name is defined, > then plexus-utils will mangle another envvar at random (depending on the > random sort order of the environment block). For three developers in my > office, it has impacted the SSH_AUTH_SOCK envvar, causing Subversion > operations and Maven scpexe deployments to fail with mysterious-seeming > authentication failures. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3214) Coping with SUN JARs
[ http://jira.codehaus.org/browse/MNG-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3214. Assignee: Vincent Siveton Resolution: Fixed Added the true Maven 2 repo: http://download.java.net/maven/2/ > Coping with SUN JARs > > > Key: MNG-3214 > URL: http://jira.codehaus.org/browse/MNG-3214 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: Guides >Reporter: Marvin Froeder >Assignee: Vincent Siveton >Priority: Trivial > Fix For: Documentation Deficit > > > Add a link reference to the sun repository with jars. > https://maven-repository.dev.java.net/repository/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-267) Add a window and a document title plus a document description (like made in javadoc and jxr plugin)
[ http://jira.codehaus.org/browse/SUREFIRE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118903 ] Vincent Siveton commented on SUREFIRE-267: -- Benjamin, I am not really in favour on this i18n approach. Let s discuss it on the wiki or on dev@ FYI we have an I18N proposal here: http://docs.codehaus.org/display/MAVEN/I18N+Plugin+Description > Add a window and a document title plus a document description (like made in > javadoc and jxr plugin) > --- > > Key: SUREFIRE-267 > URL: http://jira.codehaus.org/browse/SUREFIRE-267 > Project: Maven Surefire > Issue Type: New Feature > Components: report plugin >Affects Versions: 2.0 Report Plugin > Environment: WinXp, Java5 >Reporter: Martin Zeltner > Fix For: 2.x > > Attachments: > patch_maven-surefire-report-plugin_add-window-and-doc-title-plus-doc-description.patch > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > Add a window and a document title plus a document description (like made in > javadoc and jxr plugin). By default the windowTitle, docTitle and > docDescription are taken from the resource bundle but if one likes to use a > specific (like made in javadoc and jxr plugin) these three parameters can be > personalized. See appended patch. > Cheers, > Martin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MJAVADOC-164) Javadoc 1.4 fails due to missing directory in linkoffline option
[
http://jira.codehaus.org/browse/MJAVADOC-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-164.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.4
Added a test on linkoffline location
> Javadoc 1.4 fails due to missing directory in linkoffline option
>
>
> Key: MJAVADOC-164
> URL: http://jira.codehaus.org/browse/MJAVADOC-164
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.3
> Environment: j2sdk1.4.2_15, maven 2.0.8
>Reporter: Vincent Siveton
>Assignee: Vincent Siveton
> Fix For: 2.4
>
>
> On trunk, r609309, calling:
> {noformat}
> mvn clean site -Preporting -Ddebug=true
> {noformat}
> The error is:
> {noformat}
> Embedded error: Error rendering Maven report: Exit code: 1 - javadoc: Error
> reading file:
> D:/java/apache.org/maven/src/trunks/maven-2.0.x/maven-repository-metadata/target/site/testapidocs/package-list
> {noformat}
> And the option file contains:
> {noformat}
> ...
> -linkoffline
> 'http://maven.apache.org/maven-artifact/apidocs'
> 'D:/java/apache.org/maven/src/trunks/maven-2.0.x/maven-artifact/target/site/testapidocs'
> -linkoffline
> 'http://maven.apache.org/maven-repository-metadata/apidocs'
> 'D:/java/apache.org/maven/src/trunks/maven-2.0.x/maven-repository-metadata/target/site/testapidocs'
> ...
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MJAVADOC-164) Javadoc 1.4 fails due to missing directory in linkoffline option
Javadoc 1.4 fails due to missing directory in linkoffline option
Key: MJAVADOC-164
URL: http://jira.codehaus.org/browse/MJAVADOC-164
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.3
Environment: j2sdk1.4.2_15, maven 2.0.8
Reporter: Vincent Siveton
On trunk, r609309, calling:
{noformat}
mvn clean site -Preporting -Ddebug=true
{noformat}
The error is:
{noformat}
Embedded error: Error rendering Maven report: Exit code: 1 - javadoc: Error
reading file:
D:/java/apache.org/maven/src/trunks/maven-2.0.x/maven-repository-metadata/target/site/testapidocs/package-list
{noformat}
And the option file contains:
{noformat}
...
-linkoffline
'http://maven.apache.org/maven-artifact/apidocs'
'D:/java/apache.org/maven/src/trunks/maven-2.0.x/maven-artifact/target/site/testapidocs'
-linkoffline
'http://maven.apache.org/maven-repository-metadata/apidocs'
'D:/java/apache.org/maven/src/trunks/maven-2.0.x/maven-repository-metadata/target/site/testapidocs'
...
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3219) Create a CLIRR/JarDiff setup for 2.0.x and 2.1.x
[ http://jira.codehaus.org/browse/MNG-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118899 ] Vincent Siveton commented on MNG-3219: -- added clirr report in the maven-parent (r609317) > Create a CLIRR/JarDiff setup for 2.0.x and 2.1.x > > > Key: MNG-3219 > URL: http://jira.codehaus.org/browse/MNG-3219 > Project: Maven 2 > Issue Type: New Feature > Components: Bootstrap & Build >Reporter: Jason van Zyl > Fix For: 2.0.9 > > > It may not only be for the core but also the plugin tools that have been > separated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3273) Point out known pitfalls when developing plugins
[
http://jira.codehaus.org/browse/MNG-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNG-3273.
Resolution: Fixed
patch applied in r609305. Thanks!
> Point out known pitfalls when developing plugins
>
>
> Key: MNG-3273
> URL: http://jira.codehaus.org/browse/MNG-3273
> Project: Maven 2
> Issue Type: Improvement
> Components: Documentation: Guides
>Reporter: Benjamin Bentmann
>Assignee: Vincent Siveton
>Priority: Minor
> Attachments: pitfalls.patch
>
>
> Writing a simple Maven plugin is quite easy but getting it wrong is also
> quite easy. I am just a novice but have so far noticed two subtle
> anti-patterns that plugin developers should avoid. I would expect that the
> Maven core team knows some more aspects about mojo programming that plugin
> developers should be aware of to fight bugs right from the beginning. All
> those pitfalls would fit nicely into [Plugin
> Development|http://maven.apache.org/guides/plugin/guide-java-plugin-development.html].
> Some examples: It is a bad idea to code something like
> {code:java}
> public MyMojo {
> private Log log = getLog();
> public void execute() throws MojoExecutionException {
> log.debug("...");
> }
> }
> {code}
> Getting the logger this way will retrieve some default logger instead of the
> logger that is injected into the mojo (by the plexus container?). This is
> easily noticed by the different output styles of the log messages and the
> fact that one gets [debug] message without having "-X" enabled.
> Not bad but rather dangerous is something like
> {code:java}
> public MyMojo {
> /**
> * This parameter will take a file path (file paths are
> platform-dependent...)
> * @parameter
> */
> private String outputDirectory;
> public void execute() throws MojoExecutionException {
> File outputDir = new File(outputDirectory).getAbsoluteFile();
> outputDir.mkdirs();
> }
> }
> {code}
> java.io.File resolves relative paths like "target/something" that users might
> provide in the plugin configuration against the current directory which needs
> not be the project base directory. Therefore, path parameters should be
> declared of type java.io.File rather than simple strings as Maven seems to
> automatically push in properly resolved paths into the mojo. If one really
> needs the parameter to be of type String (i.e. to try resource lookup from
> class path), the best practice to properly get an absolute path should be
> documented.
> How to get a plugin ready for reactor builds might also be worth some warning
> words. What does one need to know about aggregator-style execution, execution
> project, forking ... ?
> A further improvement might be links to recommended libraries like
> plexus-utils or plexus-components. This would point peoply to existing code
> and prevent to error-prone reinvention of the wheel (only a few things on
> earth are that simple that people get them reliably right...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3255) Documentation for checking out and build should warn abour long path names on Windows
[ http://jira.codehaus.org/browse/MNG-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3255. Assignee: Vincent Siveton Resolution: Fixed Added a Windows note (r609303) > Documentation for checking out and build should warn abour long path names on > Windows > - > > Key: MNG-3255 > URL: http://jira.codehaus.org/browse/MNG-3255 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: Guides >Reporter: Dale King >Assignee: Vincent Siveton > Fix For: Documentation Deficit > > > I tried checking out the 2.1 maven code and build to see if a problem I was > seeing with maven eclipse integration was localized to the that integration > or was caused by the new maven embedder in 2.1 that they use. > I was checking out into a directory on my desktop under windows. The checkout > did not complete and had a message: > svn: Can't open file > 'maven-components\maven-core\src\test\resources\org\apache\ > maven\extension\test-extension-repo\org\apache\maven\core\test\test-lifecycle-an > d-artifactHandler\1\.svn\tmp\text-base\test-lifecycle-and-artifactHandler-1.pom. > md5.svn-base': The system cannot find the path specified. > The problem is that while windows allows filenames up to 256 characters the > maximum path length it allows is 260 characters. When you add that path to > the path to the desktop directory it was too long. > I was able to check it out to the root directory without problem. > The guide to building maven should probably mention that for Windows users in > the part about checking out the source. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3242) It's not possible to get a property with unescaped & sign for urls
[
http://jira.codehaus.org/browse/MNG-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118825
]
Vincent Siveton commented on MNG-3242:
--
Could you provide us your pom?
The following should work:
{noformat}
...
jdbc:mysql://localhost/mydb?user=myuser&password=mypass&useUnicode=true&characterEncoding=utf-8
OR
...
{noformat}
> It's not possible to get a property with unescaped & sign for urls
> --
>
> Key: MNG-3242
> URL: http://jira.codehaus.org/browse/MNG-3242
> Project: Maven 2
> Issue Type: Bug
> Components: General
>Affects Versions: 2.0.6
>Reporter: Nils Eckert
> Fix For: 2.0.x
>
>
> I found no way to create a property with a not escaped ampersand (&-sign).
> This is needed for a MySQL jdbc-connection String with some connection
> variabled and should be filtered in a properties file during compile phase.
> It tried to escape it with & This leeds to following error: Project build
> error Cannot read project model from interpolating filter of serialized
> version.
> It is no option to use a double escaping with &. Here I get a &
> in my connection url.
> I also tried to use a <[CDATA[ ... ]]> with the same problems. It's not
> possible to use & sign. And if I use & this escaped tag appears in my
> properties file after filtering.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3255) Documentation for checking out and build should warn abour long path names on Windows
[ http://jira.codehaus.org/browse/MNG-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3255. Resolution: Won't Fix It is a SVN issue not a Maven one > Documentation for checking out and build should warn abour long path names on > Windows > - > > Key: MNG-3255 > URL: http://jira.codehaus.org/browse/MNG-3255 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: Guides >Reporter: Dale King > Fix For: Documentation Deficit > > > I tried checking out the 2.1 maven code and build to see if a problem I was > seeing with maven eclipse integration was localized to the that integration > or was caused by the new maven embedder in 2.1 that they use. > I was checking out into a directory on my desktop under windows. The checkout > did not complete and had a message: > svn: Can't open file > 'maven-components\maven-core\src\test\resources\org\apache\ > maven\extension\test-extension-repo\org\apache\maven\core\test\test-lifecycle-an > d-artifactHandler\1\.svn\tmp\text-base\test-lifecycle-and-artifactHandler-1.pom. > md5.svn-base': The system cannot find the path specified. > The problem is that while windows allows filenames up to 256 characters the > maximum path length it allows is 260 characters. When you add that path to > the path to the desktop directory it was too long. > I was able to check it out to the root directory without problem. > The guide to building maven should probably mention that for Windows users in > the part about checking out the source. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3257) Intro to the POM Example 3 - nonsense explanation
[ http://jira.codehaus.org/browse/MNG-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3257. Assignee: Vincent Siveton Resolution: Fixed Applied. Next time, please provide directly a patch. See http://maven.apache.org/guides/development/guide-helping.html > Intro to the POM Example 3 - nonsense explanation > - > > Key: MNG-3257 > URL: http://jira.codehaus.org/browse/MNG-3257 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: Introductions >Affects Versions: Documentation Deficit >Reporter: Gary Morgan >Assignee: Vincent Siveton >Priority: Minor > Fix For: Documentation Deficit > > > The solution explanation for Example 3 contains a number of errors. > 1) "we have the element /module/ my-module///module/." > should probably read "we have the element my-module." > 2) "The value of /module/// is the " > should probably read "The value of is the " > 3) "relative path from the com.mycompany.app:my-module:1 to > com.mycompany.app:my-module:1's POM" > should probably read "relative path from the com.mycompany.app:my-app:1 to > com.mycompany.app:my-module:1's POM" > 4) "Now, whenever a maven command processes com.mycompany.app:my-module:1" > should probably read "Now, whenever a maven command processes > com.mycompany.app:my-app:1" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3265) maven-model Extension.equals causes NPE when any field is uninitialized
[ http://jira.codehaus.org/browse/MNG-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MNG-3265: - Summary: maven-model Extension.equals causes NPE when any field is uninitialized (was: maven-model Repository.equals causes NPE when any field is uninitialized) > maven-model Extension.equals causes NPE when any field is uninitialized > --- > > Key: MNG-3265 > URL: http://jira.codehaus.org/browse/MNG-3265 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Jared Roberts > Attachments: MNG-3265-maven-model.patch > > > The equals(Object) method of Extension does not check for null values before > calling String.equals(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3273) Point out known pitfalls when developing plugins
[
http://jira.codehaus.org/browse/MNG-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNG-3273.
Assignee: Vincent Siveton
Resolution: Fixed
Added your pitfalls proposal in r609135
> Point out known pitfalls when developing plugins
>
>
> Key: MNG-3273
> URL: http://jira.codehaus.org/browse/MNG-3273
> Project: Maven 2
> Issue Type: Improvement
> Components: Documentation: Guides
>Reporter: Benjamin Bentmann
>Assignee: Vincent Siveton
>Priority: Minor
>
> Writing a simple Maven plugin is quite easy but getting it wrong is also
> quite easy. I am just a novice but have so far noticed two subtle
> anti-patterns that plugin developers should avoid. I would expect that the
> Maven core team knows some more aspects about mojo programming that plugin
> developers should be aware of to fight bugs right from the beginning. All
> those pitfalls would fit nicely into [Plugin
> Development|http://maven.apache.org/guides/plugin/guide-java-plugin-development.html].
> Some examples: It is a bad idea to code something like
> {code:java}
> public MyMojo {
> private Log log = getLog();
> public void execute() throws MojoExecutionException {
> log.debug("...");
> }
> }
> {code}
> Getting the logger this way will retrieve some default logger instead of the
> logger that is injected into the mojo (by the plexus container?). This is
> easily noticed by the different output styles of the log messages and the
> fact that one gets [debug] message without having "-X" enabled.
> Not bad but rather dangerous is something like
> {code:java}
> public MyMojo {
> /**
> * This parameter will take a file path (file paths are
> platform-dependent...)
> * @parameter
> */
> private String outputDirectory;
> public void execute() throws MojoExecutionException {
> File outputDir = new File(outputDirectory).getAbsoluteFile();
> outputDir.mkdirs();
> }
> }
> {code}
> java.io.File resolves relative paths like "target/something" that users might
> provide in the plugin configuration against the current directory which needs
> not be the project base directory. Therefore, path parameters should be
> declared of type java.io.File rather than simple strings as Maven seems to
> automatically push in properly resolved paths into the mojo. If one really
> needs the parameter to be of type String (i.e. to try resource lookup from
> class path), the best practice to properly get an absolute path should be
> documented.
> How to get a plugin ready for reactor builds might also be worth some warning
> words. What does one need to know about aggregator-style execution, execution
> project, forking ... ?
> A further improvement might be links to recommended libraries like
> plexus-utils or plexus-components. This would point peoply to existing code
> and prevent to error-prone reinvention of the wheel (only a few things on
> earth are that simple that people get them reliably right...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3275) Maven 2.0.6 pom missing from ibiblio
[ http://jira.codehaus.org/browse/MNG-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3275. Resolution: Cannot Reproduce Pom is present in the central [1]. FYI this description is not really helpful. Have a glance on [2] to submit an helpful report. [1] http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom [2] http://maven.apache.org/users/getting-help.html > Maven 2.0.6 pom missing from ibiblio > > > Key: MNG-3275 > URL: http://jira.codehaus.org/browse/MNG-3275 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Reporter: Yuri Schimke > > I'm using Archiva as a mirror for central. But I think I'm getting some bad > ibiblio file mirror. > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > GroupId: org.apache.maven > ArtifactId: maven > Version: 2.0.6 > Reason: Unable to download the artifact from any repository > org.apache.maven:maven:pom:2.0.6 > ftp://ibiblio.org/pub/packages/maven2/org/apache/maven/maven/ > Current directory is /pub/packages/maven2/org/apache/maven/maven/ > [DIRECTORY] Parent Directory > [DIRECTORY] 2.0. . . . . . . . . . . . . . . . . . .[May 7 2006] > [DIRECTORY] 2.0-alpha-1. . . . . . . . . . . . . . .[May 7 2006] > [DIRECTORY] 2.0-alpha-2. . . . . . . . . . . . . . .[May 7 2006] > [DIRECTORY] 2.0-alpha-3. . . . . . . . . . . . . . .[May 7 2006] > [DIRECTORY] 2.0-beta-1 . . . . . . . . . . . . . . .[May 7 2006] > [DIRECTORY] 2.0-beta-2 . . . . . . . . . . . . . . .[May 7 2006] > [DIRECTORY] 2.0-beta-3 . . . . . . . . . . . . . . .[May 7 2006] > [DIRECTORY] 2.0.1. . . . . . . . . . . . . . . . . .[May 7 2006] > [DIRECTORY] 2.0.2. . . . . . . . . . . . . . . . . .[May 7 2006] > [DIRECTORY] 2.0.3. . . . . . . . . . . . . . . . . .[May 7 2006] > [DIRECTORY] 2.0.4. . . . . . . . . . . . . . . . . .[May 7 2006] > [FILE] maven-metadata.xml . . . . . . . . . . .[May 7 2006] > 512B > [FILE] maven-metadata.xml.asc . . . . . . . . .[Jun 27 2006] > 187B > [FILE] maven-metadata.xml.md5 . . . . . . . . .[May 7 2006] > 32B > [FILE] maven-metadata.xml.sha1. . . . . . . . .[May 7 2006] > 40B > http://repo1.maven.org/maven2/org/apache/maven/maven/ > Index of /maven2/org/apache/maven/maven > Icon Name Last modified Size Description[DIR] > Parent Directory - > [DIR] 2.0-alpha-1/ 07-May-2006 17:31- > [DIR] 2.0-alpha-2/ 07-May-2006 17:31- > [DIR] 2.0-alpha-3/ 07-May-2006 17:31- > [DIR] 2.0-beta-1/ 07-May-2006 17:31- > [DIR] 2.0-beta-2/ 07-May-2006 17:31- > [DIR] 2.0-beta-3/ 07-May-2006 17:31- > [DIR] 2.0.1/07-May-2006 17:31- > [DIR] 2.0.2/07-May-2006 17:31- > [DIR] 2.0.3/07-May-2006 17:31- > [DIR] 2.0.4/07-May-2006 17:31- > [DIR] 2.0.5/14-Feb-2007 11:11- > [DIR] 2.0.6/31-Mar-2007 20:55- > [DIR] 2.0.7/21-Jun-2007 00:31- > [DIR] 2.0/ 07-May-2006 17:31- > [TXT] maven-metadata.xml21-Jun-2007 00:30 605 > [TXT] maven-metadata.xml.asc27-Jun-2006 08:00 187 > [TXT] maven-metadata.xml.md521-Jun-2007 00:30 32 > [TXT] maven-metadata.xml.sha1 21-Jun-2007 00:30 40 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3279) Support Exception Chaining for MojoFailureException
[ http://jira.codehaus.org/browse/MNG-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3279. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.0.9 Patch applied. Thanks! > Support Exception Chaining for MojoFailureException > --- > > Key: MNG-3279 > URL: http://jira.codehaus.org/browse/MNG-3279 > Project: Maven 2 > Issue Type: Improvement > Components: Plugin API >Affects Versions: 2.0.7 >Reporter: Benjamin Bentmann >Assignee: Vincent Siveton >Priority: Trivial > Fix For: 2.0.9 > > Attachments: exception-chaining.patch > > > It would be helpful if MojoFailureException provides constructors to supply > an inner exception, just like MojoExecutionException does already. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3288) Invalid systemPath allows build to continue--failing in later phase.
[
http://jira.codehaus.org/browse/MNG-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNG-3288.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.0.9
verify that the system-scoped artifact is a file: fixed in r60896
> Invalid systemPath allows build to continue--failing in later phase.
>
>
> Key: MNG-3288
> URL: http://jira.codehaus.org/browse/MNG-3288
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.0.7
>Reporter: David Siefert
>Assignee: Vincent Siveton
>Priority: Minor
> Fix For: 2.0.9
>
> Attachments: systempath-issue.zip
>
>
> When the system scoped dependency is specified as follows:
>
> junit
> junit
> 3.8.1
> system
>
> ${env.USERPROFILE}/.m2/repository/junit/junit/3.8.1/junit-3.8.2.jar
>
> Maven fails and complains correctly (junit-3.8.2.jar is incorrect, and should
> be junit-3.8.1.jar).
> However, when the following is used:
>
> junit
> junit
> 3.8.1
> system
> ${env.USERPROFILE}/.m2/repository/junit/junit
>
> Maven DOES NOT COMPLAIN, the build process proceeds and fails later in the
> compile/testCompile build phases since the dependency is not available. You
> can see attached minimal project.
> FYI-This was tested on a Windows XP system, I have not yet tried to replicate
> this issue on *nix.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3335) Improvement to "resource" / "targetPath" element in pom.xml
[
http://jira.codehaus.org/browse/MNG-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNG-3335.
Assignee: Vincent Siveton
Resolution: Fixed
fixed with r608896
> Improvement to "resource" / "targetPath" element in pom.xml
> ---
>
> Key: MNG-3335
> URL: http://jira.codehaus.org/browse/MNG-3335
> Project: Maven 2
> Issue Type: Improvement
> Components: Documentation: General
>Affects Versions: Documentation Deficit
>Reporter: Daniel Harvey
>Assignee: Vincent Siveton
>
> The documentation for the "resource" / "targetPath" element in pom.xml here
> (http://maven.apache.org/ref/current/maven-model/maven.html#class_resource)
> is a little unclear about the location being relative to the target/classes
> directory.
> Specifically, I suggest adding: "The path is relative to the target/classes
> directory (${project.build.outputDirectory})."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3337) Downloading plugins for an inhouse repository problem
[
http://jira.codehaus.org/browse/MNG-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118729
]
Vincent Siveton commented on MNG-3337:
--
Did you overrided the central repo? Something like the following in your
settings:
{noformat}
central
...
{noformat}
Also, try to add the central repo (http://repo1.maven.org/maven2/ ) in your
settings.
> Downloading plugins for an inhouse repository problem
> -
>
> Key: MNG-3337
> URL: http://jira.codehaus.org/browse/MNG-3337
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Reporter: sedatcorbaci
>Priority: Blocker
>
> For an inhouse maven repository we can't find a way to download the plugins
> to local repo.
> When we try to execute an initial archetype:create command encountered maven
> couldn't find the archetype plugin error. To deal with this we just copies
> org.apache folder to local repo and then everything fine. But again if i need
> any plugin that is not in copied to local repo manually maven couldn't
> download it from internal repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3344) Provide new POM element to configure site directory (e.g. "src/site")
[
http://jira.codehaus.org/browse/MNG-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton updated MNG-3344:
-
Fix Version/s: 2.1-alpha-1
Sounds acceptable feature for 2.1
> Provide new POM element to configure site directory (e.g. "src/site")
> -
>
> Key: MNG-3344
> URL: http://jira.codehaus.org/browse/MNG-3344
> Project: Maven 2
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.8
>Reporter: Benjamin Bentmann
> Fix For: 2.1-alpha-1
>
>
> As requested in MSITE-91 and its various duplicates, the input location for
> the site generation should be configurable. Currently, this is realized by a
> configuration parameter (siteDirectory) for the maven-site-plugin itself but
> I argue that this is not sufficient/robust for all cases. The problem is that
> the plugin cannot access its configuration in ancestor POMs and hence can
> only guess.
> For example, take the following multi-module scenario:
> project-parent/
> doc/
> site.xml
> project-module/
> src/
> site/
> site.xml
> Let us ignore the fact that such is layout is unusual, weird, bad-practice or
> whatever you would like to call it. The point is, it should be possible. The
> important aspect of the example is that both POMs will need to use a
> different configuration of the maven-site-plugin to find the site descriptor
> (and related files). The parent POM will have siteDirectory=doc while the
> module POM will have siteDirectory=src/site.
> Now consider the plugin's steps when building the site for project-module.
> From the plugin configuration in "project-module/pom.xml", it knows to search
> the site descriptor for the sub project in "src/site". To apply inheritance,
> the plugin then needs to locate the site descriptor of the parent project.
> Ups. The plugin cannot access the corresponding plugin configuration in
> "project-parent/pom.xml". So it can only assume that the parent uses the same
> directory layout for the site as the current sub module.
> Having a dedicated POM element for the site files, e.g.
> ${project.reporting.siteDirectory}, would allow the maven-site-plugin to
> properly determine the location of the site descriptor of any ancestor
> project. The super POM can default this element to "src/site" to get the
> usual behavior.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3308) SNAPSHOT plugin not found after successfully downloaded
[ http://jira.codehaus.org/browse/MNG-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3308. Resolution: Cannot Reproduce It sounds like more a Plexus error or a plugin conf error than a Maven issue. BTW I am able to run mvn jdepend:generate on my projects > SNAPSHOT plugin not found after successfully downloaded > > > Key: MNG-3308 > URL: http://jira.codehaus.org/browse/MNG-3308 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.8 >Reporter: Jörg Hohwiller > > Sometimes Maven is really hard to understand: > It successfully downloads a plugin and then is NOT able to find what it just > downloaded. I looked at the POM of that plugin but can NOT see anything wrong. > Any ideas? > [INFO] snapshot org.codehaus.mojo:jdepend-maven-plugin:2.0-SNAPSHOT: checking > for updates from Codehaus Snapshots > Downloading: > http://snapshots.repository.codehaus.org/org/codehaus/mojo/jdepend-maven-plugin/2.0-SNAPSHOT/jdepend-maven-plugin-2.0-20070110.102957-1.pom > 1K downloaded > Downloading: > http://snapshots.repository.codehaus.org/org/codehaus/mojo/jdepend-maven-plugin/2.0-SNAPSHOT/jdepend-maven-plugin-2.0-20070110.102957-1.jar > 18K downloaded > 22:32:45,390 INFO org.hibernate.cfg.Environment - Hibernate 3.2.0 > 22:32:45,421 INFO org.hibernate.cfg.Environment - hibernate.properties not > found > 22:32:45,437 INFO org.hibernate.cfg.Environment - Bytecode provider name : > cglib > 22:32:45,437 INFO org.hibernate.cfg.Environment - using JDK 1.4 > java.sql.Timestamp handling > url = > jar:file:/C:/WINDOWS/Profiles/hohwille/.m2/repository/org/codehaus/mojo/dashboard-maven-plugin/1.0-SNAPSHOT/dashboard-maven-plugin-1.0-SNAPSHOT.jar!/hibernate.cfg.xml > 22:32:45,531 INFO org.hibernate.cfg.Configuration - configuring from url: > jar:file:/C:/WINDOWS/Profiles/hohwille/.m2/repository/org/codehaus/mojo/dashboard-maven-plugin/1.0-SNAPSHOT/dashboard-maven-plugin-1.0-SNAPSHOT.jar!/hibernate.cfg.xml > 22:32:45,703 INFO org.hibernate.cfg.Configuration - Reading mappings from > resource: dashboard.hbm.xml > 22:32:45,906 INFO org.hibernate.cfg.HbmBinder - Mapping class: > org.codehaus.mojo.dashboard.report.plugin.beans.DashBoardMavenProject -> > MavenProject > 22:32:45,937 INFO org.hibernate.cfg.HbmBinder - Mapping class: > org.codehaus.mojo.dashboard.report.plugin.beans.AbstractReportBean -> > AbstractReportBean > 22:32:46,171 INFO org.hibernate.cfg.HbmBinder - Mapping union-subclass: > org.codehaus.mojo.dashboard.report.plugin.beans.CheckstyleReportBean -> > CheckstyleReportBean > 22:32:46,171 INFO org.hibernate.cfg.HbmBinder - Mapping union-subclass: > org.codehaus.mojo.dashboard.report.plugin.beans.CoberturaReportBean -> > CoberturaReportBean > 22:32:46,187 INFO org.hibernate.cfg.HbmBinder - Mapping union-subclass: > org.codehaus.mojo.dashboard.report.plugin.beans.CloverReportBean -> > CloverReportBean > 22:32:46,187 INFO org.hibernate.cfg.HbmBinder - Mapping union-subclass: > org.codehaus.mojo.dashboard.report.plugin.beans.CpdReportBean -> CpdReportBean > 22:32:46,187 INFO org.hibernate.cfg.HbmBinder - Mapping union-subclass: > org.codehaus.mojo.dashboard.report.plugin.beans.PmdReportBean -> PmdReportBean > 22:32:46,187 INFO org.hibernate.cfg.HbmBinder - Mapping union-subclass: > org.codehaus.mojo.dashboard.report.plugin.beans.SurefireReportBean -> > SurefireReportBean > 22:32:46,187 INFO org.hibernate.cfg.HbmBinder - Mapping union-subclass: > org.codehaus.mojo.dashboard.report.plugin.beans.FindBugsReportBean -> > FindBugsReportBean > 22:32:46,187 INFO org.hibernate.cfg.Configuration - Configured > SessionFactory: null > [INFO] artifact org.codehaus.mojo:jdepend-maven-plugin: checking for updates > from central > Downloading: > http://repo1.maven.org/maven2/org/codehaus/mojo/jdepend-maven-plugin/2.0-beta-1/jdepend-maven-plugin-2.0-beta-1.pom > 1K downloaded > Downloading: > http://repo1.maven.org/maven2/org/codehaus/mojo/jdepend-maven-plugin/2.0-beta-1/jdepend-maven-plugin-2.0-beta-1.jar > 17K downloaded > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error getting reports from the plugin > 'org.codehaus.mojo:jdepend-maven-plugin': Unable to find the mojo > 'org.codehaus.mojo:jdepend-maven-plugin:2.0-SNAPSHOT:generate' in the plugin > 'org.codehaus.mojo:jdepend-maven-plugin' > Component descriptor cannot be found in the component repository: > org.apache.maven.plugin.Mojoorg.codehaus.mojo:jdepend-maven-plugin:2.0-SNAPSHOT:generate. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > --
[jira] Commented: (MNG-3301) is there any problems with proxy i tried every thing with settings.xml i dont why it happening like this we have to fix this issue
[ http://jira.codehaus.org/browse/MNG-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118707 ] Vincent Siveton commented on MNG-3301: -- Could you tell us more about your configuration like settings.xml > is there any problems with proxy i tried every thing with settings.xml i dont > why it happening like this we have to fix this issue > -- > > Key: MNG-3301 > URL: http://jira.codehaus.org/browse/MNG-3301 > Project: Maven 2 > Issue Type: Task > Components: Command Line >Affects Versions: 2.0.7 >Reporter: vamsikrishna > > org.apache.maven.lifecycle.LifecycleExecutionException: Missing: > -- > 1) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.maven.wagon > -DartifactId=wagon-webdav \ > -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file there: > mvn deploy:deploy-file -DgroupId=org.apache.maven.wagon > -DartifactId=wagon-webdav \ > -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \ >-Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) com.intralinks.qa:qc-super-pom:pom:1.2-SNAPSHOT > 2) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MCLEAN-29) Maven clean plugin doesn't filter resources from exclude list
[ http://jira.codehaus.org/browse/MCLEAN-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-3302 to MCLEAN-29: Affects Version/s: (was: 2.0.7) Component/s: (was: Plugins and Lifecycle) Key: MCLEAN-29 (was: MNG-3302) Project: Maven 2.x Clean Plugin (was: Maven 2) > Maven clean plugin doesn't filter resources from exclude list > - > > Key: MCLEAN-29 > URL: http://jira.codehaus.org/browse/MCLEAN-29 > Project: Maven 2.x Clean Plugin > Issue Type: Bug >Reporter: Vladimir Sosnin > > For example you want to delete content of folder but want to keep folder > itself and it's SCM (e.g. SVN) information. Following configuration for > "maven-maven-clean" plugin deletes all plain files under ".svn" directory and > simply keeps empty subdirs. Thus, making update command impossible. > > ... > > > maven-clean-plugin > >true > > > logic/src/test/generated/resources > > > > .svn/**/* > > > > **/* > > > false > > > > > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3310) JAVACMD set incorrectly when JAVA_HOME is not set
[ http://jira.codehaus.org/browse/MNG-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3310. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.0.9 Patch applied. Thanks! > JAVACMD set incorrectly when JAVA_HOME is not set > - > > Key: MNG-3310 > URL: http://jira.codehaus.org/browse/MNG-3310 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.8 >Reporter: Matthijs Wensveen >Assignee: Vincent Siveton > Fix For: 2.0.9 > > Attachments: mvn.patch > > > In the mvn shell script, when the JAVA_HOME environment variable is not set, > the script sets JAVACMD to java, probably as a best effort, hoping it is on > the user's PATH. 4 lines beneath that, the JAVACMD is tested for > executability, but since it is not a path to the java executable, but just > the java command, this fails. > The relevant part of the script (lines 122-139): > 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 > Line 131 should be changed to: > JAVACMD="`which java`" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3313) NetBeans projects, more than ant project, more than free form project.
[ http://jira.codehaus.org/browse/MNG-3313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118702 ] Vincent Siveton commented on MNG-3313: -- Did you check these plugins in the mojo land? http://mojo.codehaus.org/nbm-maven-plugin/ http://mojo.codehaus.org/netbeans-freeform-maven-plugin/ > NetBeans projects, more than ant project, more than free form project. > --- > > Key: MNG-3313 > URL: http://jira.codehaus.org/browse/MNG-3313 > Project: Maven 2 > Issue Type: New Feature > Components: Dependencies, Design, Patterns & Best Practices, IDEs, > POM >Reporter: Imre Tabur >Priority: Critical > > Is better to have maven (plugin) that generates correct NetBeans project, not > only ANT free form project: > 1)Including information about what type project it is - ear, war, jar > 2)Correct Source/Binary format by POM - right now it desn't generate correct > source level! > 3)Recursively resolved dependencies packages for project for compile, build, > test > 4)maven source tree > layout(http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html) > must accept also other source layouts like default NetBeans layout or any > other what users/developers do . Maven can't be dominant at this point, > because people cant always remake theirs projects by maven needs. If we > compare rpm/yum, deb/apt systems with maven, then maven tries to be dominant > - all things must be done this way how maven accept it, but deb/rpm > conception says: "We accept developers(users) packages and we can build users > sources, we don't need special layout for that!". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3317) i want to use filter option one of my txt file has multiple option like qa,prod,dev/
[ http://jira.codehaus.org/browse/MNG-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3317. Assignee: Vincent Siveton Resolution: Incomplete Next time, please ask your questions on Maven User List ([EMAIL PROTECTED]) not in Jira However, I guess you want profiles. Have a glance on the doc. http://maven.apache.org/guides/mini/guide-building-for-different-environments.html http://www.sonatype.com/book/j2ee.html#use_profiles_for_dev_test_prod > i want to use filter option one of my txt file has multiple option like > qa,prod,dev/ > > > Key: MNG-3317 > URL: http://jira.codehaus.org/browse/MNG-3317 > Project: Maven 2 > Issue Type: Task > Components: Dependencies >Affects Versions: 2.0.8 >Reporter: parlepoint >Assignee: Vincent Siveton > > hi guys, > i have properties file having multiple option for qa,prd,dev. > i would like to filtered with my option of qa /prd or dev. > did anybody know how to apply filter in properties file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3318) ActiveProjectArtifact should have appropriate equals and hashCode methods
[ http://jira.codehaus.org/browse/MNG-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3318. Assignee: Vincent Siveton Resolution: Fixed fixed with r608815 > ActiveProjectArtifact should have appropriate equals and hashCode methods > - > > Key: MNG-3318 > URL: http://jira.codehaus.org/browse/MNG-3318 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Carolin Koehler >Assignee: Vincent Siveton > Fix For: 2.0.9 > > > ActiveProjectArtifact should have appropriate equals and hashCode method like > the DefaultArtifact, to be comparable and to be usable with hash based > collections. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3318) ActiveProjectArtifact should have appropriate equals and hashCode methods
[ http://jira.codehaus.org/browse/MNG-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MNG-3318: - Affects Version/s: 2.0.8 Fix Version/s: 2.0.9 > ActiveProjectArtifact should have appropriate equals and hashCode methods > - > > Key: MNG-3318 > URL: http://jira.codehaus.org/browse/MNG-3318 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Carolin Koehler > Fix For: 2.0.9 > > > ActiveProjectArtifact should have appropriate equals and hashCode method like > the DefaultArtifact, to be comparable and to be usable with hash based > collections. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3325) unable to delete surefire reports on windows xp meachine
[ http://jira.codehaus.org/browse/MNG-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3325. Assignee: Vincent Siveton Resolution: Incomplete The descripton of this issue is totally incomplete. Next time, please read the "Submit an issue" part in [1] However, it sounds like a clean-plugin issue. Maybe, have a look on the clean FAQ [2] or try to use the failOnError parameter [3]. [1] http://maven.apache.org/users/getting-help.html [2] http://maven.apache.org/plugins/maven-clean-plugin/faq.html [3] http://maven.apache.org/plugins/maven-clean-plugin/examples/ignoring-errors.html > unable to delete surefire reports on windows xp meachine > > > Key: MNG-3325 > URL: http://jira.codehaus.org/browse/MNG-3325 > Project: Maven 2 > Issue Type: Bug >Reporter: vamsikrishna >Assignee: Vincent Siveton > > unable to delete surefire reports on windows xp meachine -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3327) Deploy site of SNAPSHOT to a different location than site of release version
[ http://jira.codehaus.org/browse/MNG-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118681 ] Vincent Siveton commented on MNG-3327: -- see thread on dev@ http://www.nabble.com/Publishing-Plugin-Sites-%28was%3A-Re%3A-Plugins-sandbox-site%29-td13044546s177.html#a13044546 > Deploy site of SNAPSHOT to a different location than site of release version > > > Key: MNG-3327 > URL: http://jira.codehaus.org/browse/MNG-3327 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: General >Reporter: Benjamin Bentmann > > This issue is not directly targetted at the Maven core but something general > the Maven developers should consider since Maven is about best practices: > It is a bad practice to deploy sites of SNAPSHOTs to the same location as the > final release version. The ordinary user who runs Maven simply using release > versions of the plugins should be able to read the corresponding > documentation, not documentation for a different plugin version. For example, > take > http://maven.apache.org/plugins/maven-antrun-plugin/examples/tasksAttributes.html > which describes a feature of the upcoming release which is not yet > available. It may take users a while to realize that this documentation is > for the SNAPSHOT version of the AntRun plugin and hence not usable in a > production build. > Therefore, I would suggest to deploy release sites to something like > maven.apche.org/plugins/maven-X-plugin > (as now) and the SNAPSHOT site to > maven.apche.org/plugins/maven-X-plugin/snapshot > or similar. This should be easy using a profile. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3219) Create a CLIRR/JarDiff setup for 2.0.x and 2.1.x
[ http://jira.codehaus.org/browse/MNG-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118677 ] Vincent Siveton commented on MNG-3219: -- In mojo land, we have both plugins but only clirr-maven-plugin was released, the other one is in the sandbox. I propose to configure only the clirr report in the maven-parent: this report will be available here [1]. WDYT? [1] http://maven.apache.org/ref/current > Create a CLIRR/JarDiff setup for 2.0.x and 2.1.x > > > Key: MNG-3219 > URL: http://jira.codehaus.org/browse/MNG-3219 > Project: Maven 2 > Issue Type: New Feature > Components: Bootstrap & Build >Reporter: Jason van Zyl > Fix For: 2.0.9 > > > It may not only be for the core but also the plugin tools that have been > separated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3011) Generating API differences between 2.0.x and 2.1
[ http://jira.codehaus.org/browse/MNG-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3011. Resolution: Duplicate Fix Version/s: (was: Reviewed Pending Version Assignment) > Generating API differences between 2.0.x and 2.1 > > > Key: MNG-3011 > URL: http://jira.codehaus.org/browse/MNG-3011 > Project: Maven 2 > Issue Type: Task > Components: General >Affects Versions: 2.1 >Reporter: Vincent Siveton >Priority: Minor > > I think it could be useful for developers > http://www.osjava.org/jardiff/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MANT-33) ClassCastException when calling mvn ant:ant
[ http://jira.codehaus.org/browse/MANT-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MANTLR-25 to MANT-33: --- Key: MANT-33 (was: MANTLR-25) Project: Maven 2.x Ant Plugin (was: Maven 2.x Antlr Plugin) > ClassCastException when calling mvn ant:ant > --- > > Key: MANT-33 > URL: http://jira.codehaus.org/browse/MANT-33 > Project: Maven 2.x Ant Plugin > Issue Type: Bug > Environment: java-config -L > The following VMs are available for generation-2: > 1) Blackdown JDK 1.4.2.03 [blackdown-jdk-1.4.2] > 2) Sun 32bit JRE 1.6.0.03 [emul-linux-x86-java-1.6] > *) Sun JDK 1.5.0.13 [sun-jdk-1.5] > 4) Sun JDK 1.6.0.03 [sun-jdk-1.6] > * Active vm > emerge --info > Portage 2.1.4_rc11 (default-linux/amd64/2006.1/desktop, gcc-4.2.2, > glibc-2.7-r1, 2.6.23-gentoo x86_64) > = > System uname: 2.6.23-gentoo x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor > 6000+ > Timestamp of tree: Unknown > app-shells/bash: 3.2_p17-r1 > dev-java/java-config: 1.3.7, 2.1.3 > dev-lang/python: 2.5.1-r4 > sys-apps/baselayout: 1.12.10-r5 > sys-apps/sandbox:1.2.18.1-r2 > sys-devel/autoconf: 2.13, 2.61-r1 > sys-devel/automake: 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 > sys-devel/binutils: 2.18-r1 > sys-devel/gcc-config: 1.4.0-r4 > sys-devel/libtool: 1.5.24 > virtual/os-headers: 2.6.23-r2 > ACCEPT_KEYWORDS="amd64 ~amd64" > CBUILD="x86_64-pc-linux-gnu" > CFLAGS="-march=k8 -O2 -pipe" > CHOST="x86_64-pc-linux-gnu" > CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config > /usr/kde/3.5/shutdown /usr/share/config /var/lib/hsqldb" > CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf > /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ > /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/splash /etc/terminfo > /etc/texmf/web2c /etc/udev/rules.d" > CXXFLAGS="-march=k8 -O2 -pipe" > DISTDIR="/usr/portage/distfiles" > FEATURES="cvs distlocks metadata-transfer nostrip parallel-fetch sfperms > strict unmerge-orphans userfetch userpriv usersandbox" > GENTOO_MIRRORS="http://distfiles.gentoo.org > http://distro.ibiblio.org/pub/linux/distributions/gentoo"; > LANG="en_NZ" > LC_ALL="en_NZ.utf8" > LINGUAS="en en_GB en_NZ" > MAKEOPTS="-j3" > PKGDIR="/usr/portage/packages" > PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times > --compress --force --whole-file --delete --delete-after --stats --timeout=180 > --exclude=/distfiles --exclude=/local --exclude=/packages > --filter=H_**/files/digest-*" > PORTAGE_TMPDIR="/var/tmp" > PORTDIR="/home/alistair/gentoo/cvs/gentoo-x86" > PORTDIR_OVERLAY="/home/alistair/gentoo/overlays/java-overlay > /home/alistair/gentoo/overlays/java-experimental" > SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" > USE="X a52 aac acpi alsa amd64 apache2 berkdb bitmap-fonts cairo cdr > clearcase cli cracklib crypt ctype cups cvs dbus doc dri dvd dvdr dvdread eds > emboss encode esd fam firefox fortran gd gdbm gif glitz gpm gtk2 hal iconv > ipv6 isdnlog java java5 javamail jpeg jpeg2k kde ldap lm_sensors mad midi > mikmod mp3 mpeg mplayer mudflap mysql mysqli ncurses nls nptl nptlonly > nsplugin offensive ogg opengl openmp pam pcre pdf perl png ppds pppd python > qt3 qt4 quicktime readline reflection ruby sdl session source spell spl sql > sqlite ssl subversion svg tcpd theora threads tiff tomcat truetype > truetype-fonts type1-fonts unicode utempter vorbis xcomposite xine xml xorg > xulrunner xv xvid xvmc zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem > bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel > intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" > ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file > hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate > route share shm softvol" APACHE2_MODULES="actions alias auth_basic > authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm > authz_default authz_groupfile authz_host authz_owner authz_user autoindex > cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter > file_cache filter headers include info log_config logio mem_cache mime > mime_magic negotiation rewrite setenvif speling status unique_id userdir > usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" > KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 > mtxorb ncurses text" LINGUAS="en en_GB en_NZ" USERLAND="GNU" > VIDEO_CARDS="nvidia" > Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, > PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS >Reporter: Alistair Bush > Attachments: mvnDebug.txt > > >
[jira] Commented: (MPIR-34) Update the i18n properties file with these new additions
[ http://jira.codehaus.org/browse/MPIR-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115573 ] Vincent Siveton commented on MPIR-34: - Applied Juven's file in r599988 Juven, next time, please submit patch instead of file (see http://maven.apache.org/guides/development/guide-helping.html ) > Update the i18n properties file with these new additions > > > Key: MPIR-34 > URL: http://jira.codehaus.org/browse/MPIR-34 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Task >Reporter: Edwin Punzalan >Assignee: Dennis Lundberg > Attachments: MNG-MPIR-34-maven-project-info-reports-plugin.patch, > project-info-report_zh_CN.properties > > > These have been added: > report.dependencies.graph.title=Project Dependency Graph > report.dependencies.graph.tree.title=Dependency Tree > report.dependencies.graph.tables.title=Dependency Listings > report.dependencies.graph.tables.column.groupid=GroupId > report.dependencies.graph.tables.column.artifactid=ArtifactId > report.dependencies.graph.tables.column.version=Version > report.dependencies.graph.tables.column.comments=Comments > report.dependencies.graph.tables.attached=Attached > report.dependencies.graph.tables.notAttached=Not attached > report.summary.title=Project Summary > report.summary.name=Project Summary > report.summary.description=This document lists other related information of > this project > report.summary.field=Field > report.summary.value=Value > report.summary.general.title=Project Information > report.summary.general.name=Name > report.summary.general.description=Description > report.summary.general.homepage=Homepage > report.summary.build.title=Build Information > report.summary.build.groupid=GroupId > report.summary.build.artifactid=ArtifactId > report.summary.build.version=Version > report.summary.build.type=Type > report.summary.organization.title=Project Organization > report.summary.organization.name=Name > report.summary.organization.url=URL -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-34) Update the i18n properties file with these new additions
[ http://jira.codehaus.org/browse/MPIR-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115571 ] Vincent Siveton commented on MPIR-34: - Updated the French bundle in r599987 > Update the i18n properties file with these new additions > > > Key: MPIR-34 > URL: http://jira.codehaus.org/browse/MPIR-34 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Task >Reporter: Edwin Punzalan >Assignee: Dennis Lundberg > Attachments: MNG-MPIR-34-maven-project-info-reports-plugin.patch, > project-info-report_zh_CN.properties > > > These have been added: > report.dependencies.graph.title=Project Dependency Graph > report.dependencies.graph.tree.title=Dependency Tree > report.dependencies.graph.tables.title=Dependency Listings > report.dependencies.graph.tables.column.groupid=GroupId > report.dependencies.graph.tables.column.artifactid=ArtifactId > report.dependencies.graph.tables.column.version=Version > report.dependencies.graph.tables.column.comments=Comments > report.dependencies.graph.tables.attached=Attached > report.dependencies.graph.tables.notAttached=Not attached > report.summary.title=Project Summary > report.summary.name=Project Summary > report.summary.description=This document lists other related information of > this project > report.summary.field=Field > report.summary.value=Value > report.summary.general.title=Project Information > report.summary.general.name=Name > report.summary.general.description=Description > report.summary.general.homepage=Homepage > report.summary.build.title=Build Information > report.summary.build.groupid=GroupId > report.summary.build.artifactid=ArtifactId > report.summary.build.version=Version > report.summary.build.type=Type > report.summary.organization.title=Project Organization > report.summary.organization.name=Name > report.summary.organization.url=URL -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-273) Wrong url in banner left url when page has more 2 sub directories
Wrong url in banner left url when page has more 2 sub directories - Key: MSITE-273 URL: http://jira.codehaus.org/browse/MSITE-273 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-6 Environment: svn rev 599447 Reporter: Vincent Siveton Follow the following steps: 1. go to http://maven.apache.org/repository/index.html or http://maven.apache.org/developers/committer-environment.html 2. and click on the Maven logo (top left) 3. the page is http://maven.apache.org/ which is the correct behaviour But try to reproduce the same with 2 sub directories in the url, like http://maven.apache.org/guides/mini/guide-central-repository-upload.html The url is http://maven.apache.org/guides/ instead of http://maven.apache.org/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-34) Using security manager in a fork mode causes an AccessControlException
[ http://jira.codehaus.org/browse/SUREFIRE-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114771 ] Vincent Siveton commented on SUREFIRE-34: - Dont know about Ashcroft and agree with your comment. But the use case was defining a security manager without any policy. We need to handle this. WDYT? > Using security manager in a fork mode causes an AccessControlException > -- > > Key: SUREFIRE-34 > URL: http://jira.codehaus.org/browse/SUREFIRE-34 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 1.5.3 (2.1.3 plugin) >Reporter: Vincent Siveton >Priority: Critical > Fix For: 2.4 > > Attachments: SUREFIRE-34.diff > > > Using securityManager in a forkmode causes > java.security.AccessControlException in the createClassLoader() method > Same things with setSystemProperties() > Example: > > org.apache.maven.plugins > maven-surefire-plugin > > pertest > -Djava.security.manager > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-299) Add SCM informations in the manifest
Add SCM informations in the manifest Key: MRELEASE-299 URL: http://jira.codehaus.org/browse/MRELEASE-299 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-7 Reporter: Vincent Siveton It should be great if some SCM informations like url and revision could be put in the MANIFEST.MF -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3294) [file-management] Add a parameter to throw or not IOException in delete( FileSet fileSet )
[ http://jira.codehaus.org/browse/MNG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3294. Assignee: Vincent Siveton Resolution: Fixed done in r596648 > [file-management] Add a parameter to throw or not IOException in delete( > FileSet fileSet ) > -- > > Key: MNG-3294 > URL: http://jira.codehaus.org/browse/MNG-3294 > Project: Maven 2 > Issue Type: Improvement > Components: Shared >Reporter: Vincent Siveton >Assignee: Vincent Siveton > > Add a parameter in delete( FileSet fileSet ) to throw IOException when errors > have occurred by deleting files or directories. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3294) [file-management] Add a parameter to throw or not IOException in delete( FileSet fileSet )
[file-management] Add a parameter to throw or not IOException in delete( FileSet fileSet ) -- Key: MNG-3294 URL: http://jira.codehaus.org/browse/MNG-3294 Project: Maven 2 Issue Type: Improvement Components: Shared Reporter: Vincent Siveton Add a parameter in delete( FileSet fileSet ) to throw IOException when errors have occurred by deleting files or directories. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPLUGIN-62) Exclude read-only components from plugin goal documentation
[
http://jira.codehaus.org/browse/MPLUGIN-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPLUGIN-62.
--
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.4
Patch applied. Thanks!
> Exclude read-only components from plugin goal documentation
> ---
>
> Key: MPLUGIN-62
> URL: http://jira.codehaus.org/browse/MPLUGIN-62
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Java Plugins
> Environment: Maven 2.0.7
>Reporter: Benjamin Bentmann
>Assignee: Vincent Siveton
>Priority: Trivial
> Fix For: 2.4
>
> Attachments: readonly-component.patch
>
>
> Currently, a mojo field declared like
> {code:java}
> /**
> * @component
> * @readonly
> */
> private MavenProjectHelper projectHelper;
> {code}
> will make it into the site documentation for the goal (i.e.
> mymojo-mojo.html), causing confusion for users of the plugin.
> This problem seems to arise from
> JavaMojoDescriptorExtractor.extractParameters() which does not mark
> @component fields as read-only. This in turn, will make
> PluginXdocGeneratorMojo.filterParameters() keep the field for documentation.
> The attached patch shows two possible solutions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPLUGIN-63) Add since column in the parameters table
[ http://jira.codehaus.org/browse/MPLUGIN-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPLUGIN-63. -- Resolution: Fixed added > Add since column in the parameters table > > > Key: MPLUGIN-63 > URL: http://jira.codehaus.org/browse/MPLUGIN-63 > Project: Maven 2.x Plugin Tools > Issue Type: Improvement > Components: Java Plugins >Affects Versions: 2.3 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.4 > > > The since column will improve the learning curve of new features -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPLUGIN-63) Add since column in the parameters table
[ http://jira.codehaus.org/browse/MPLUGIN-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MPLUGIN-63: --- Affects Version/s: 2.3 > Add since column in the parameters table > > > Key: MPLUGIN-63 > URL: http://jira.codehaus.org/browse/MPLUGIN-63 > Project: Maven 2.x Plugin Tools > Issue Type: Improvement > Components: Java Plugins >Affects Versions: 2.3 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.4 > > > The since column will improve the learning curve of new features -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPLUGIN-63) Add since column in the parameters table
Add since column in the parameters table Key: MPLUGIN-63 URL: http://jira.codehaus.org/browse/MPLUGIN-63 Project: Maven 2.x Plugin Tools Issue Type: Improvement Components: Java Plugins Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: 2.4 The since column will improve the learning curve of new features -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-63) Add CSS style class to XHTML tags
[ http://jira.codehaus.org/browse/DOXIA-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114031 ] Vincent Siveton commented on DOXIA-63: -- Is it reasonable to use CSS in a document like pdf? > Add CSS style class to XHTML tags > - > > Key: DOXIA-63 > URL: http://jira.codehaus.org/browse/DOXIA-63 > Project: Maven Doxia > Issue Type: Improvement > Components: Core >Affects Versions: 1.0-alpha-8 >Reporter: Vance Karimi >Priority: Minor > Fix For: 1.0-beta-1 > > Attachments: doxia-1.0-alpha-8-core-patch.txt, > doxia-1.0-alpha-8-sink-api-patch.txt > > > Add support for CSS style formatting with a class property on tags. > Previously filed http://jira.codehaus.org/browse/MNG-545. > Patches for core and sink-api for doxia-1.0-alpha-8 attached. > It provides the following fixes: > 1. class property on list and numbered list tag > 2. class property on paragraph tag > 3. class property on link tag > 4. target property on link tag > 5. class property on table cells > 6. class property on table header cells > 7. class property on anchors > Is this an acceptable request or have people achieved CSS style differently > when generating XHTML using Doxia? > Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCLEAN-8) conversion of the existing unit tests to use the AbstractMojoTestCase from the plugin testing harness
[ http://jira.codehaus.org/browse/MCLEAN-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MCLEAN-8. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.2 apply with several updates > conversion of the existing unit tests to use the AbstractMojoTestCase from > the plugin testing harness > - > > Key: MCLEAN-8 > URL: http://jira.codehaus.org/browse/MCLEAN-8 > Project: Maven 2.x Clean Plugin > Issue Type: Improvement >Reporter: Jesse McConnell >Assignee: Vincent Siveton > Fix For: 2.2 > > Attachments: maven-clean-harness-2.patch, maven-clean-harness.patch > > > This is the patch for that I am hoping are best practices in using the plugin > testing harness as mentioned in MNG-32 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLEAN-25) Optionally don't delete the 'target ' directory
[ http://jira.codehaus.org/browse/MCLEAN-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113823 ] Vincent Siveton commented on MCLEAN-25: --- You could also use ignoreErrors parameter (see MCLEAN-22 ) > Optionally don't delete the 'target ' directory > > > Key: MCLEAN-25 > URL: http://jira.codehaus.org/browse/MCLEAN-25 > Project: Maven 2.x Clean Plugin > Issue Type: New Feature >Reporter: Joern Huxhorn >Assignee: Vincent Siveton > Fix For: 2.2 > > Attachments: clean-patch.patch > > > Would it be possible to add an option to the clean-plugin so only the content > of the target folder(s) are deleted but not the directory itself? > This would help developers using windoze quite a lot since: > - clean fails if you happen to have opened a command line with target as the > current dir. > - windoze closes explorer windows pointing to deleted directories, so you > have to reopen the windows after a clean install > Those problems would both be solved by an option like deleteRoot=false or > something. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCLEAN-27) fileset directory does not work as expected when cleaning "modules" in sub-directories
[
http://jira.codehaus.org/browse/MCLEAN-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MCLEAN-27.
-
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.2
o handle subproject dir
> fileset directory does not work as expected when cleaning "modules" in
> sub-directories
> --
>
> Key: MCLEAN-27
> URL: http://jira.codehaus.org/browse/MCLEAN-27
> Project: Maven 2.x Clean Plugin
> Issue Type: Improvement
>Affects Versions: 2.1.1
>Reporter: Jacob Robertson
>Assignee: Vincent Siveton
> Fix For: 2.2
>
>
> Following the example given on the plugin site, I used a fileset with a
> directory like so.
> {code}
>
> maven-clean-plugin
>
>
>
>
> src/main/application
>
>
> *.jar
>
>
>
>
>
> {code}
> I did this, or a variation on it, to several projects. I then created a
> parent pom in the directory above those projects, added them as modules in
> that pom, and ran "mvn clean" expecting to have those specified directories
> cleaned for me (of all jar files). However, it did not work. To get it to
> work, I had to prefix my directories with ${basedir}, for example
> "${basedir}/src/main/application".
> If this is the desired behavior, I recommend adding one sentence to the
> documentation to explain this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCLEAN-22) Possibility to ignore deletion failures
[ http://jira.codehaus.org/browse/MCLEAN-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MCLEAN-22. - Assignee: Vincent Siveton Resolution: Fixed added ignoreErrors parameter > Possibility to ignore deletion failures > --- > > Key: MCLEAN-22 > URL: http://jira.codehaus.org/browse/MCLEAN-22 > Project: Maven 2.x Clean Plugin > Issue Type: Improvement >Affects Versions: 2.1, 2.1.1 > Environment: WinXP SP2 >Reporter: Bugittaa Pahasti >Assignee: Vincent Siveton > Fix For: 2.2 > > > If deletion of the output directories during clean fails, the build will > fail. It would be good to have a configuration option, so that the plugin > would just print a warning and continue cleaning with the rest of the > directories. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCLEAN-24) Disable plugin execution
[ http://jira.codehaus.org/browse/MCLEAN-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MCLEAN-24. - Assignee: Vincent Siveton Resolution: Fixed added a skip parameter > Disable plugin execution > > > Key: MCLEAN-24 > URL: http://jira.codehaus.org/browse/MCLEAN-24 > Project: Maven 2.x Clean Plugin > Issue Type: Improvement >Affects Versions: 2.1, 2.1.1 >Reporter: Daniel Takai >Assignee: Vincent Siveton > Fix For: 2.2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > It is sometimes favorable not to execute the clean plugin for some profile > (for instance in a multi-project where you wouldn't want the the integration > test setup to be cleaned since it takes 45 minutes to set it up). > It would be nice if plugin execution could be turned off via > false -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCLEAN-25) Optionally don't delete the 'target ' directory
[ http://jira.codehaus.org/browse/MCLEAN-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MCLEAN-25. - Assignee: Vincent Siveton Resolution: Won't Fix Fix Version/s: 2.2 This patch doesnt fix all other Windows handler pb. I add a faq entry and you could download ProcessExplorer to close some handler. http://www.microsoft.com/technet/sysinternals/Utilities/ProcessExplorer.mspx > Optionally don't delete the 'target ' directory > > > Key: MCLEAN-25 > URL: http://jira.codehaus.org/browse/MCLEAN-25 > Project: Maven 2.x Clean Plugin > Issue Type: New Feature >Reporter: Joern Huxhorn >Assignee: Vincent Siveton > Fix For: 2.2 > > Attachments: clean-patch.patch > > > Would it be possible to add an option to the clean-plugin so only the content > of the target folder(s) are deleted but not the directory itself? > This would help developers using windoze quite a lot since: > - clean fails if you happen to have opened a command line with target as the > current dir. > - windoze closes explorer windows pointing to deleted directories, so you > have to reopen the windows after a clean install > Those problems would both be solved by an option like deleteRoot=false or > something. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-185) Add encoding support
Add encoding support Key: DOXIA-185 URL: http://jira.codehaus.org/browse/DOXIA-185 Project: Maven Doxia Issue Type: Improvement Components: Sink API Affects Versions: 1.0-alpha-10 Reporter: Vincent Siveton -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-74) Move logic inside AbstractProjectInfoReport to maven-reporting-impl
[
http://jira.codehaus.org/browse/MPIR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113012
]
Vincent Siveton commented on MPIR-74:
-
The main pb is not in the MPIR (works fine) but in all report pending plugins.
We need to extract this logic somewhere to avoid copy/paste.
Just try to create a new report plugin with doxia:1.0-alpha-9 and specify the
following content
{noformat}
getSink().head();
getSink().text( "REPORT NAME" );
getSink().head_();
{noformat}
> Move logic inside AbstractProjectInfoReport to maven-reporting-impl
> ---
>
> Key: MPIR-74
> URL: http://jira.codehaus.org/browse/MPIR-74
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Vincent Siveton
>Priority: Blocker
> Fix For: 2.1
>
>
> Due to doxia:1.0-alpha-9, the following methods need to be a part of
> maven-reporting-impl:
> private File getSkinArtifactFile();
> public void execute();
> So, it should be more easy to create a new report plugin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
