[jira] (MSKINS-64) Social buttons are not aligned when rendered in the sidebar
Simone Tripodi created MSKINS-64: Summary: Social buttons are not aligned when rendered in the sidebar Key: MSKINS-64 URL: https://jira.codehaus.org/browse/MSKINS-64 Project: Maven Skins Issue Type: Bug Components: Fluido Skin Affects Versions: fluido-1.3.0 Reporter: Simone Tripodi As shown in the [Fluido Homepage|http://maven.apache.org/skins/maven-fluido-skin/], buttons for social network integration are not aligned when rendered in the sidebar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-64) Social buttons are not aligned when rendered in the sidebar
[ https://jira.codehaus.org/browse/MSKINS-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi closed MSKINS-64. Resolution: Fixed Fix Version/s: fluido-1.3.0 Assignee: Simone Tripodi Fixed on trunk, see r1377280 > Social buttons are not aligned when rendered in the sidebar > > > Key: MSKINS-64 > URL: https://jira.codehaus.org/browse/MSKINS-64 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.3.0 >Reporter: Simone Tripodi >Assignee: Simone Tripodi > Fix For: fluido-1.3.0 > > > As shown in the [Fluido > Homepage|http://maven.apache.org/skins/maven-fluido-skin/], buttons for > social network integration are not aligned when rendered in the sidebar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-63) Improve the sidebar layout
[ https://jira.codehaus.org/browse/MSKINS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MSKINS-63. -- Resolution: Fixed use icon-chevron now > Improve the sidebar layout > -- > > Key: MSKINS-63 > URL: https://jira.codehaus.org/browse/MSKINS-63 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.3.0 >Reporter: Simone Tripodi >Assignee: Olivier Lamy > Fix For: fluido-1.3.0 > > Attachments: MSKINS-63-2.patch, MSKINS-63-icon-chevron.patch, > MSKINS-63.patch, Screen Shot 2012-08-22 at 2.49.25 PM.png, Screen Shot > 2012-08-23 at 2.38.06 PM.png, Screen Shot 2012-08-23 at 2.40.06 PM.png, > Screen Shot 2012-08-23 at 2.40.17 PM.png > > > After upgrading Bootstrap to v2.1.0, sidebar back to look bad again, see the > attached screenshot :S > It could be improved starting, for example, from the Bootstrap > [Sample|http://twitter.github.com/bootstrap/examples/fluid.html] (which is > called _fluid_!!! :D) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-370) Use native bunzip2 when in the path
Benson Margulies created MDEP-370: - Summary: Use native bunzip2 when in the path Key: MDEP-370 URL: https://jira.codehaus.org/browse/MDEP-370 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: unpack-dependencies Affects Versions: 2.5 Reporter: Benson Margulies The java unpacker of bunzip2 is spectacularly slow. Given that the dependency plugin is already in the business of using command lines in some cases, I suggest trying to operate bunzip2 this way, as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-251) Artifact ###### has no file error regression.
[
https://jira.codehaus.org/browse/MPIR-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=307075#comment-307075
]
Herve Boutemy commented on MPIR-251:
IIUC, you have an artifact in your repository that has no file, then the
message would be consistent for this one
but thze problem here would be that when one artifact is foudn without any
file, every artifact is reported as having no file
I'll try to reproduce such conditions
> Artifact ## has no file error regression.
> -
>
> Key: MPIR-251
> URL: https://jira.codehaus.org/browse/MPIR-251
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.5
>Reporter: Ian Brandt
>Priority: Minor
> Attachments: pom.xml
>
>
> It appears that MPIR-158 has regressed. I'm seeing the same exact issue in
> 2.5 with Maven 3.0.4:
> {noformat}
> [INFO] Generating "Dependencies" report---
> maven-project-info-reports-plugin:2.5
> [ERROR] Artifact: com.sun:tools:jar:1.5.0 has no file.
> [ERROR] Artifact: com.thoughtworks.xstream:xstream:jar:1.3 has no file.
> [ERROR] Artifact: commons-beanutils:commons-beanutils:jar:1.8.0 has no file.
> [ERROR] Artifact: commons-cli:commons-cli:jar:1.1 has no file.
> [ERROR] Artifact: commons-codec:commons-codec:jar:1.3 has no file.
> [ERROR] Artifact: commons-collections:commons-collections:jar:3.2.1 has no
> file.
> [ERROR] Artifact: commons-digester:commons-digester:jar:2.0 has no file.
> [ERROR] Artifact: commons-fileupload:commons-fileupload:jar:1.2.2 has no file.
> ...{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-251) Artifact ###### has no file error regression.
[
https://jira.codehaus.org/browse/MPIR-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=307075#comment-307075
]
Herve Boutemy edited comment on MPIR-251 at 8/25/12 9:29 AM:
-
IIUC, you have an artifact in your repository that has no file, then the
message would be consistent for this one
but the problem would be that when one artifact is found without any file,
every artifact is reported as having no file
I'll try to reproduce such conditions
was (Author: hboutemy):
IIUC, you have an artifact in your repository that has no file, then the
message would be consistent for this one
but thze problem here would be that when one artifact is foudn without any
file, every artifact is reported as having no file
I'll try to reproduce such conditions
> Artifact ## has no file error regression.
> -
>
> Key: MPIR-251
> URL: https://jira.codehaus.org/browse/MPIR-251
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.5
>Reporter: Ian Brandt
>Priority: Minor
> Attachments: pom.xml
>
>
> It appears that MPIR-158 has regressed. I'm seeing the same exact issue in
> 2.5 with Maven 3.0.4:
> {noformat}
> [INFO] Generating "Dependencies" report---
> maven-project-info-reports-plugin:2.5
> [ERROR] Artifact: com.sun:tools:jar:1.5.0 has no file.
> [ERROR] Artifact: com.thoughtworks.xstream:xstream:jar:1.3 has no file.
> [ERROR] Artifact: commons-beanutils:commons-beanutils:jar:1.8.0 has no file.
> [ERROR] Artifact: commons-cli:commons-cli:jar:1.1 has no file.
> [ERROR] Artifact: commons-codec:commons-codec:jar:1.3 has no file.
> [ERROR] Artifact: commons-collections:commons-collections:jar:3.2.1 has no
> file.
> [ERROR] Artifact: commons-digester:commons-digester:jar:2.0 has no file.
> [ERROR] Artifact: commons-fileupload:commons-fileupload:jar:1.2.2 has no file.
> ...{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5336) Descriptor Reference for settings.xml is incorrect
Jan Hänsli created MNG-5336: --- Summary: Descriptor Reference for settings.xml is incorrect Key: MNG-5336 URL: https://jira.codehaus.org/browse/MNG-5336 Project: Maven 2 & 3 Issue Type: Bug Components: Settings Affects Versions: 3.0.4 Reporter: Jan Hänsli The example settings.xml found here (http://maven.apache.org/ref/3.0.4/maven-settings/settings.html) is not valid! 65: 66: value 67: bad line 67: correct line 67: Steps to reproduce: - Copy & Paste the document into your IDE or XML editor. - Start the xml validator and try to validate the document against http://maven.apache.org/xsd/settings-1.1.0.xsd -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-65) When topbar enabled, it hides the GitHub ribbon
Simone Tripodi created MSKINS-65: Summary: When topbar enabled, it hides the GitHub ribbon Key: MSKINS-65 URL: https://jira.codehaus.org/browse/MSKINS-65 Project: Maven Skins Issue Type: Bug Components: Fluido Skin Affects Versions: fluido-1.3.0 Reporter: Simone Tripodi As per subject, when both topbar and GitHub ribbon are enabled, the topbar hides the GitHub ribbon due to z-index -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-65) When topbar enabled, it hides the GitHub ribbon
[ https://jira.codehaus.org/browse/MSKINS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi closed MSKINS-65. Resolution: Fixed Assignee: Simone Tripodi fixed on trunk, see r1377309 > When topbar enabled, it hides the GitHub ribbon > --- > > Key: MSKINS-65 > URL: https://jira.codehaus.org/browse/MSKINS-65 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.3.0 >Reporter: Simone Tripodi >Assignee: Simone Tripodi > > As per subject, when both topbar and GitHub ribbon are enabled, the topbar > hides the GitHub ribbon due to z-index -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-59) Submenu support on dropdowns
[ https://jira.codehaus.org/browse/MSKINS-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated MSKINS-59: - Issue Type: Improvement (was: Bug) > Submenu support on dropdowns > > > Key: MSKINS-59 > URL: https://jira.codehaus.org/browse/MSKINS-59 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: fluido-1.3.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-58) upgrade to bootstrap 2.1.0
[ https://jira.codehaus.org/browse/MSKINS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated MSKINS-58: - Issue Type: Task (was: Bug) > upgrade to bootstrap 2.1.0 > -- > > Key: MSKINS-58 > URL: https://jira.codehaus.org/browse/MSKINS-58 > Project: Maven Skins > Issue Type: Task > Components: Fluido Skin >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: fluido-1.3.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-251) Artifact ###### has no file error regression.
[
https://jira.codehaus.org/browse/MPIR-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=307080#comment-307080
]
Herve Boutemy commented on MPIR-251:
I tried but cannot reproduce the issue
sorry, can't help...
> Artifact ## has no file error regression.
> -
>
> Key: MPIR-251
> URL: https://jira.codehaus.org/browse/MPIR-251
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.5
>Reporter: Ian Brandt
>Priority: Minor
> Attachments: pom.xml
>
>
> It appears that MPIR-158 has regressed. I'm seeing the same exact issue in
> 2.5 with Maven 3.0.4:
> {noformat}
> [INFO] Generating "Dependencies" report---
> maven-project-info-reports-plugin:2.5
> [ERROR] Artifact: com.sun:tools:jar:1.5.0 has no file.
> [ERROR] Artifact: com.thoughtworks.xstream:xstream:jar:1.3 has no file.
> [ERROR] Artifact: commons-beanutils:commons-beanutils:jar:1.8.0 has no file.
> [ERROR] Artifact: commons-cli:commons-cli:jar:1.1 has no file.
> [ERROR] Artifact: commons-codec:commons-codec:jar:1.3 has no file.
> [ERROR] Artifact: commons-collections:commons-collections:jar:3.2.1 has no
> file.
> [ERROR] Artifact: commons-digester:commons-digester:jar:2.0 has no file.
> [ERROR] Artifact: commons-fileupload:commons-fileupload:jar:1.2.2 has no file.
> ...{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-789) Automatic Major/Minor/Patch version number increment
Johannes bannhofer created MRELEASE-789:
---
Summary: Automatic Major/Minor/Patch version number increment
Key: MRELEASE-789
URL: https://jira.codehaus.org/browse/MRELEASE-789
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Components: prepare
Affects Versions: 2.4
Environment: Windows 7 / MAC OS X 10.5
Reporter: Johannes bannhofer
Attachments: mrelease_2.4_semantic versioning.patch
Hi,
i just added a feature for generating the next version number in batch mode.
Currently only the last number (either the last number of the digits array or
the annotation revision is increased. With this batch the digit group to
increase can be specified. Additionally I added an option for either keeping or
deleting trailing zeros after a major/minor version change.
I added tests for checking the versioning, the old behaviour is still the same,
all unit tests are working.
EXECUTION:
mvn release:prepare -B -DbatchIncGroup=1 -DbatchKeepTrailingZeros=true
CHANGES:
added two fields to modello model:
- batchKeepTrailingZeros
- batchIncGroup
Added an overloaded method of DefaultVersionInfo.getNextVersion
Added Testcases
Added loading/merging of the two new properties
Examples from DefaultVersionInfoTest:
public void testNextVersionMajor() throws Exception {
checkNextVersion("1", "2", 1, true);
checkNextVersion("1.2", "2.0", 1, true);
checkNextVersion("1.2.3", "2.0.0", 1, true);
checkNextVersion("11.22.33.44", "12.0.0.0", 1, true);
checkNextVersion("1.2", "2", 1, false);
checkNextVersion("1", "2", 1, false);
}
public void testNextVersionMinor() throws Exception {
checkNextVersion("1.2.3", "1.3.0", 2, true);
checkNextVersion("1.2.345.678", "1.3.0.0", 2, true);
checkNextVersion("1.2.3", "1.3", 2, false);
checkNextVersion("1", "1.1", 2, false);
}
public void testNextVersionPatch() throws Exception {
checkNextVersion("1.2.3", "1.2.4", 3, true);
checkNextVersion("1.2.3", "1.2.4", 3, false);
checkNextVersion("1", "1.0.1", 3, false);
checkNextVersion("1-SNAPSHOT", "1.0.1-SNAPSHOT", 3, false);
checkNextVersion("1.1", "1.1.1", 3, false);
checkNextVersion("1.1.1", "1.1.2", 3, false);
checkNextVersion("1", "1.0.0.0.1", 5, false);
}
I hope that helps, I would check it in myself but I think it is a longer way to
become a commiter :)
I do not have any ASF code style guide/formatter, where can I find one?
cheers joe
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-789) Automatic Major/Minor/Patch version number increment
[
https://jira.codehaus.org/browse/MRELEASE-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-789.
---
Resolution: Fixed
Closing this one as duplicate. There are several equivalent issues, although it
is good to know this one has a patch+test.
About the extra fields; everything behind the second dot is considered one
field for Maven. In general, if this can't be converted to a number, then it is
handled as a String, making 2 bigger then 11.
About your other question: the
[guide-helping|http://maven.apache.org/guides/development/guide-helping.html]
page should answer those questions.
> Automatic Major/Minor/Patch version number increment
>
>
> Key: MRELEASE-789
> URL: https://jira.codehaus.org/browse/MRELEASE-789
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
>Affects Versions: 2.4
> Environment: Windows 7 / MAC OS X 10.5
>Reporter: Johannes bannhofer
> Attachments: mrelease_2.4_semantic versioning.patch
>
>
> Hi,
> i just added a feature for generating the next version number in batch mode.
> Currently only the last number (either the last number of the digits array or
> the annotation revision is increased. With this batch the digit group to
> increase can be specified. Additionally I added an option for either keeping
> or deleting trailing zeros after a major/minor version change.
> I added tests for checking the versioning, the old behaviour is still the
> same, all unit tests are working.
> EXECUTION:
> mvn release:prepare -B -DbatchIncGroup=1 -DbatchKeepTrailingZeros=true
> CHANGES:
> added two fields to modello model:
> - batchKeepTrailingZeros
> - batchIncGroup
> Added an overloaded method of DefaultVersionInfo.getNextVersion
> Added Testcases
> Added loading/merging of the two new properties
> Examples from DefaultVersionInfoTest:
> public void testNextVersionMajor() throws Exception {
> checkNextVersion("1", "2", 1, true);
> checkNextVersion("1.2", "2.0", 1, true);
> checkNextVersion("1.2.3", "2.0.0", 1, true);
> checkNextVersion("11.22.33.44", "12.0.0.0", 1, true);
> checkNextVersion("1.2", "2", 1, false);
> checkNextVersion("1", "2", 1, false);
> }
> public void testNextVersionMinor() throws Exception {
> checkNextVersion("1.2.3", "1.3.0", 2, true);
> checkNextVersion("1.2.345.678", "1.3.0.0", 2, true);
> checkNextVersion("1.2.3", "1.3", 2, false);
> checkNextVersion("1", "1.1", 2, false);
> }
> public void testNextVersionPatch() throws Exception {
> checkNextVersion("1.2.3", "1.2.4", 3, true);
> checkNextVersion("1.2.3", "1.2.4", 3, false);
> checkNextVersion("1", "1.0.1", 3, false);
> checkNextVersion("1-SNAPSHOT", "1.0.1-SNAPSHOT", 3, false);
> checkNextVersion("1.1", "1.1.1", 3, false);
> checkNextVersion("1.1.1", "1.1.2", 3, false);
> checkNextVersion("1", "1.0.0.0.1", 5, false);
> }
> I hope that helps, I would check it in myself but I think it is a longer way
> to become a commiter :)
> I do not have any ASF code style guide/formatter, where can I find one?
> cheers joe
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5336) Descriptor Reference for settings.xml is incorrect
[ https://jira.codehaus.org/browse/MNG-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=307090#comment-307090 ] Dennis Lundberg commented on MNG-5336: -- I've created a pull request for modello@github with a fix. It seems I do not have commit access to sonatype/modello, so I need the help of someone that has commit access. Hervé? > Descriptor Reference for settings.xml is incorrect > -- > > Key: MNG-5336 > URL: https://jira.codehaus.org/browse/MNG-5336 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Settings >Affects Versions: 3.0.4 >Reporter: Jan Hänsli > > The example settings.xml found here > (http://maven.apache.org/ref/3.0.4/maven-settings/settings.html) is not valid! > 65: > 66: value > 67: > bad line 67: > correct line 67: > Steps to reproduce: > - Copy & Paste the document into your IDE or XML editor. > - Start the xml validator and try to validate the document against > http://maven.apache.org/xsd/settings-1.1.0.xsd -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
