[jira] (DOXIA-503) Plexus components cannot be abstract classes
[ https://jira.codehaus.org/browse/DOXIA-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed DOXIA-503. --- Resolution: Fixed Fix Version/s: 1.6 Assignee: Herve Boutemy done in [r1604367|http://svn.apache.org/r1604367] thank you > Plexus components cannot be abstract classes > > > Key: DOXIA-503 > URL: https://jira.codehaus.org/browse/DOXIA-503 > Project: Maven Doxia > Issue Type: Bug > Components: Core >Reporter: Mikolaj Izdebski >Assignee: Herve Boutemy > Fix For: 1.6 > > Attachments: doxia-plexus-component.patch > > > Abstract class cannot be a component. Plexus may try to instantiate (and it > will certainly fail to do so). -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-4506) Split site deployment URLs into release vs. snapshot, just like artifacts
[ https://jira.codehaus.org/browse/MNG-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MNG-4506: Component/s: FDPFC > Split site deployment URLs into release vs. snapshot, just like artifacts > - > > Key: MNG-4506 > URL: https://jira.codehaus.org/browse/MNG-4506 > Project: Maven > Issue Type: Improvement > Components: FDPFC, POM >Reporter: Matthew Beermann > Fix For: Issues to be reviewed for 4.x > > > (This is for Maven 2.1. My apologies if it's a duplicate, but I couldn't find > this issue reported elsewhere.) > One of the things we've always considered to be a major design oversight in > Maven is that the artifact repositories (in the > section) are split up into releases vs. snapshots, but the site repository > isn't. This practice significantly conflicts with the way that we (and many > others) use Maven: there's a centralized, locked-down release artifact > repository, there are many, loosely secured snapshot artifact repositories > for each team, /and there's a corresponding site repository for each/. > This organization doesn't seem especially radical, but the way the POM is > organized makes it difficult to achieve. Either we have to (hope to) remember > to update the site deployment URL just before a release, or else override it > from the command line during the release. Would it be possible to split these > two apart by enhancing the POM schema in Maven 2.1? -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-2216) Add default encodings section to POM
[
https://jira.codehaus.org/browse/MNG-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MNG-2216:
Component/s: FDPFC
> Add default encodings section to POM
>
>
> Key: MNG-2216
> URL: https://jira.codehaus.org/browse/MNG-2216
> Project: Maven
> Issue Type: Improvement
> Components: FDPFC, POM::Encoding
>Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.3
>Reporter: Trustin Lee
> Fix For: Issues to be reviewed for 4.x
>
> Attachments: example-pom.xml
>
>
> Look at the attached example POM.
> Do you see many duplicate configuration properties ('UTF-8') in it? and the
> names of properties are very inconsistent.
> It would be great if:
> 1) Add a global section which specifies default encodings:
> {code:xml}
>
> UTF-8
>
> UTF-8
> {code}
> 2) Make encoding properties in all plugins to be consistent and deprecate old
> properties. The default values could be:
> {noformat}inputEncoding = ${pom.encoding.input}
> outputEncoding = ${pom.encoding.output}{noformat}
> so users can override the default settings easily.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-2478) add filtered resource directories to super POM
[ https://jira.codehaus.org/browse/MNG-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MNG-2478: Component/s: FDPFC > add filtered resource directories to super POM > -- > > Key: MNG-2478 > URL: https://jira.codehaus.org/browse/MNG-2478 > Project: Maven > Issue Type: New Feature > Components: FDPFC, POM >Affects Versions: 2.0.4 > Environment: any >Reporter: Jörg Hohwiller > Fix For: Issues to be reviewed for 4.x > > > The super POM contains default folders for resources that are NOT filtered > (src/main/resources and src/test/resources). If one (additionally) needs a > filtered resources folder, it needs to override the default and therefore has > to add all default folders if he does NOT want to "loose" the defaults. > To make this easier my suggestion is to add filtered resource folders to the > super POM. This should also fit to the philosophy of maven that aims to have > defaults and only declare as little custom configuration as needed. > My personal favorite for the foldernames would be "templates" but to make > things more obvious to the user maybe "filtered-resources" would be better. > Actually I do not care to much about the name... > So the resources in the super POM should look like this: > > > src/main/resources > > > > src/main/filtered-resources > true > > > > > > src/test/resources > > > > src/test/filtered-resources > true > > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-177) supersedes/obsoletes
[ https://jira.codehaus.org/browse/MNG-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MNG-177: --- Component/s: FDPFC > supersedes/obsoletes > > > Key: MNG-177 > URL: https://jira.codehaus.org/browse/MNG-177 > Project: Maven > Issue Type: Improvement > Components: FDPFC, POM >Reporter: Brett Porter > Fix For: Issues to be reviewed for 4.x > > > Ability to map superseded ids. > eg plexus-container-default supersedes plexus-container-api -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5517) Supporting semver like syntax for tag
[ https://jira.codehaus.org/browse/MNG-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MNG-5517: Component/s: FDPFC > Supporting semver like syntax for tag > --- > > Key: MNG-5517 > URL: https://jira.codehaus.org/browse/MNG-5517 > Project: Maven > Issue Type: Improvement > Components: Dependencies, FDPFC, POM >Reporter: Vijay Dharap >Priority: Minor > Fix For: Issues to be reviewed for 4.x > > > node js and its corresponding package manager - npm - follows semvar notation > to depict the dependencies. > The supported syntax variations for version specification can be seen here. > https://github.com/isaacs/node-semver#ranges > I find their syntax to be much more intuitive and subsequently user friendly > than what is followed in current maven dependency tag > (http://books.sonatype.com/mvnref-book/reference/pom-relationships-sect-project-dependencies.html#pom-relationships-sect-version-ranges). > Hope we can make the pom xml little more user friendly by adapting similar > version specification syntax. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (DOXIATOOLS-47) remove encoding parameters from site descriptor methods
Herve Boutemy created DOXIATOOLS-47: --- Summary: remove encoding parameters from site descriptor methods Key: DOXIATOOLS-47 URL: https://jira.codehaus.org/browse/DOXIATOOLS-47 Project: Maven Doxia Tools Issue Type: Wish Components: Doxia Integration Tools Affects Versions: doxia-integration-tools-1.5 Reporter: Herve Boutemy site descriptor is an XML file: encoding is built into XML input and output encodings don't have any meaning in this -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (DOXIATOOLS-47) remove encoding parameters from site descriptor methods
[ https://jira.codehaus.org/browse/DOXIATOOLS-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed DOXIATOOLS-47. --- Resolution: Fixed Fix Version/s: doxia-integration-tools-1.6 Assignee: Herve Boutemy done in [r1604423|http://svn.apache.org/r1604423]: didn't deprecate the old method but simply removed the parameters and assuming breaking compatibility > remove encoding parameters from site descriptor methods > --- > > Key: DOXIATOOLS-47 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-47 > Project: Maven Doxia Tools > Issue Type: Wish > Components: Doxia Integration Tools >Affects Versions: doxia-integration-tools-1.5 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: doxia-integration-tools-1.6 > > > site descriptor is an XML file: encoding is built into XML > input and output encodings don't have any meaning in this -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (DOXIATOOLS-48) don't read parent site.xml if inheritance not expected
Herve Boutemy created DOXIATOOLS-48: --- Summary: don't read parent site.xml if inheritance not expected Key: DOXIATOOLS-48 URL: https://jira.codehaus.org/browse/DOXIATOOLS-48 Project: Maven Doxia Tools Issue Type: Improvement Components: Doxia Integration Tools Affects Versions: doxia-integration-tools-1.5 Reporter: Herve Boutemy Priority: Minor DOXIASITETOOLS-90 added inheritance control optimization: in case of inheritance disabled, no need to get parent site.xml -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (DOXIATOOLS-48) don't read parent site.xml if inheritance not expected
[ https://jira.codehaus.org/browse/DOXIATOOLS-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed DOXIATOOLS-48. --- Resolution: Fixed Fix Version/s: doxia-integration-tools-1.6 Assignee: Herve Boutemy done in [r1604424|http://svn.apache.org/r1604424] > don't read parent site.xml if inheritance not expected > -- > > Key: DOXIATOOLS-48 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-48 > Project: Maven Doxia Tools > Issue Type: Improvement > Components: Doxia Integration Tools >Affects Versions: doxia-integration-tools-1.5 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Minor > Fix For: doxia-integration-tools-1.6 > > > DOXIASITETOOLS-90 added inheritance control > optimization: in case of inheritance disabled, no need to get parent site.xml -- This message was sent by Atlassian JIRA (v6.1.6#6162)
