[jira] (MEAR-146) Expose parameter to not write library-directory element in application.xml
[ https://jira.codehaus.org/browse/MEAR-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301799#comment-301799 ] Alex Halovanic commented on MEAR-146: - Stéphane, in light of Oracle confirming this being intentional behavior for the foreseeable future, do you still think it makes sense to modify this to have a specific WebLogic section for this option? I feel like introducing a PlexusConfiguration just to nest a parameter is going to make invoking this option unnecessarily complex. For example, the ear:ear goal documentation is not going to list this flag if it's nested under a Configuration class. Also, unlike the JBoss options, this does not modify a separate file, but has consequences for application.xml. > Expose parameter to not write library-directory element in application.xml > -- > > Key: MEAR-146 > URL: https://jira.codehaus.org/browse/MEAR-146 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.8 > Environment: Oracle WebLogic >Reporter: Alex Halovanic >Priority: Minor > Attachments: ear-remove-librarydirectory-IT.patch, > ear-remove-librarydirectory.patch > > > The current handling of defaultLibBundleDir leads to some issues on Oracle > Weblogic 10+. The Ear plugin currently sets library-directory to the value > of defaultLibBundleDir in the application.xml for EARs v5+. Some of Oracle's > classloading features break (specifically "Generic File Loading") when this > element is set. defaultLibBundleDir has to be set to APP-INF/lib since this > is the magic library folder for WebLogic. > The patch adds a parameter to prevent setting library-directory for cases > like this. -- 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] (MPLUGIN-216) default dependency resolution set to RUNTIME
[ https://jira.codehaus.org/browse/MPLUGIN-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPLUGIN-216. - Resolution: Fixed Fix Version/s: 3.1 Assignee: Herve Boutemy done in [r1353331|http://svn.apache.org/viewvc?rev=1353331&view=rev] > default dependency resolution set to RUNTIME > > > Key: MPLUGIN-216 > URL: https://jira.codehaus.org/browse/MPLUGIN-216 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Components: maven-plugin-tools-annotations >Affects Versions: 3.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 3.1 > > > as reported on > [mavendev|http://mail-archives.apache.org/mod_mbox/maven-dev/201206.mbox/%3Cop.wgcyfqiskdkhrr%40columbia%3E], > java 5 annotations generate descriptor with RUNTIME default resolution scope > instead of no resolution with javadoc tags -- 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] (MPLUGIN-216) default dependency resolution set to RUNTIME
Herve Boutemy created MPLUGIN-216: - Summary: default dependency resolution set to RUNTIME Key: MPLUGIN-216 URL: https://jira.codehaus.org/browse/MPLUGIN-216 Project: Maven 2.x Plugin Tools Issue Type: Bug Components: maven-plugin-tools-annotations Affects Versions: 3.0 Reporter: Herve Boutemy as reported on [mavendev|http://mail-archives.apache.org/mod_mbox/maven-dev/201206.mbox/%3Cop.wgcyfqiskdkhrr%40columbia%3E], java 5 annotations generate descriptor with RUNTIME default resolution scope instead of no resolution with javadoc tags -- 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] (MPLUGIN-215) role-hint and configuration generated with empty values
[ https://jira.codehaus.org/browse/MPLUGIN-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPLUGIN-215: -- Description: as reported on [mavendev|http://mail-archives.apache.org/mod_mbox/maven-dev/201206.mbox/%3Cop.wgcyfqiskdkhrr%40columbia%3E], descriptor generated from java 5 annotations is different from descriptor generated from javadoc tags: - phase is always added without value - elements within have an explicit closing tag if there's no content (was a compressed tag like ) - role-hint-tag with empty content is added if there's no role-hint (wasn't there, IIRC this could be an issue) this is probably due to the fact that annotations are defined with empty String default value where javadoc tags have no default value then null was: as reported on [mavendev|], descriptor generated from java 5 annotations is different from descriptor generated from javadoc tags: - phase is always added without value - elements within have an explicit closing tag if there's no content (was a compressed tag like ) - role-hint-tag with empty content is added if there's no role-hint (wasn't there, IIRC this could be an issue) this is probably due to the fact that annotations are defined with empty String default value where javadoc tags have no default value then null > role-hint and configuration generated with empty values > --- > > Key: MPLUGIN-215 > URL: https://jira.codehaus.org/browse/MPLUGIN-215 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Components: maven-plugin-tools-annotations >Affects Versions: 3.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 3.1 > > > as reported on > [mavendev|http://mail-archives.apache.org/mod_mbox/maven-dev/201206.mbox/%3Cop.wgcyfqiskdkhrr%40columbia%3E], > descriptor generated from java 5 annotations is different from descriptor > generated from javadoc tags: > - phase is always added without value > - elements within have an explicit closing tag if there's no > content (was a compressed tag like ) > - role-hint-tag with empty content is added if there's no role-hint (wasn't > there, IIRC this could be an issue) > this is probably due to the fact that annotations are defined with empty > String default value where javadoc tags have no default value then null -- 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] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11
[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold reopened SUREFIRE-827: - > Surefire 2.12 cannot run a single test, regression from 2.11 > > > Key: SUREFIRE-827 > URL: https://jira.codehaus.org/browse/SUREFIRE-827 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.12 > Environment: Ubuntu 11.10 >Reporter: Andrew Gaul >Assignee: Kristian Rosenvold > Fix For: 2.13 > > Attachments: BUG-827.zip > > > # Surefire 2.11 > $ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile > ... > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > # Surefire 2.12 > mvn test -Dtest=DataTest#testDataServerGetNonExistentFile > ... > Tests run: 9, Failures: 0, Errors: 0, Skipped: 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-54) Upgrade to bootstrap-2.0.4
[
https://jira.codehaus.org/browse/MSKINS-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301789#comment-301789
]
Robert Scholte commented on MSKINS-54:
--
Replacing the {{js}} and {{css}} has some side effects, it ruins the searchbox
for instance.
> Upgrade to bootstrap-2.0.4
> --
>
> Key: MSKINS-54
> URL: https://jira.codehaus.org/browse/MSKINS-54
> Project: Maven Skins
> Issue Type: Improvement
> Components: Fluido Skin
>Affects Versions: fluido-1.2.1
>Reporter: Robert Scholte
>
--
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] (MPLUGIN-215) role-hint and configuration generated with empty values
[ https://jira.codehaus.org/browse/MPLUGIN-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPLUGIN-215. - Resolution: Fixed Fix Version/s: 3.1 Assignee: Herve Boutemy done in [r1353251|http://svn.apache.org/viewvc?rev=1353251&view=rev] > role-hint and configuration generated with empty values > --- > > Key: MPLUGIN-215 > URL: https://jira.codehaus.org/browse/MPLUGIN-215 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Components: maven-plugin-tools-annotations >Affects Versions: 3.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 3.1 > > > as reported on [mavendev|], descriptor generated from java 5 annotations is > different from descriptor generated from javadoc tags: > - phase is always added without value > - elements within have an explicit closing tag if there's no > content (was a compressed tag like ) > - role-hint-tag with empty content is added if there's no role-hint (wasn't > there, IIRC this could be an issue) > this is probably due to the fact that annotations are defined with empty > String default value where javadoc tags have no default value then null -- 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] (MPLUGIN-215) role-hint and configuration generated with empty values
Herve Boutemy created MPLUGIN-215: - Summary: role-hint and configuration generated with empty values Key: MPLUGIN-215 URL: https://jira.codehaus.org/browse/MPLUGIN-215 Project: Maven 2.x Plugin Tools Issue Type: Bug Components: maven-plugin-tools-annotations Affects Versions: 3.0 Reporter: Herve Boutemy as reported on [mavendev|], descriptor generated from java 5 annotations is different from descriptor generated from javadoc tags: - phase is always added without value - elements within have an explicit closing tag if there's no content (was a compressed tag like ) - role-hint-tag with empty content is added if there's no role-hint (wasn't there, IIRC this could be an issue) this is probably due to the fact that annotations are defined with empty String default value where javadoc tags have no default value then null -- 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] (MPLUGIN-214) generated descriptor for Maven object components is not like previous versions
[ https://jira.codehaus.org/browse/MPLUGIN-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPLUGIN-214. - Resolution: Fixed Fix Version/s: 3.1 Assignee: Herve Boutemy fixed in [r1353231|http://svn.apache.org/viewvc?rev=1353231&view=rev] > generated descriptor for Maven object components is not like previous versions > -- > > Key: MPLUGIN-214 > URL: https://jira.codehaus.org/browse/MPLUGIN-214 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Components: maven-plugin-tools-annotations >Affects Versions: 3.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Trivial > Fix For: 3.1 > > > as reported in > [mavendev|http://mail-archives.apache.org/mod_mbox/maven-dev/201206.mbox/%3Cop.wgcyfqiskdkhrr%40columbia%3E], > project, session and settings have an implementation and required is false > (was true) > this doesn't have any impact since these objects are injected by Maven core, > not by Plexus, but making sure the same description is generated will help > users confidence -- 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] (MPLUGIN-214) generated descriptor for Maven object components is not like previous versions
Herve Boutemy created MPLUGIN-214: - Summary: generated descriptor for Maven object components is not like previous versions Key: MPLUGIN-214 URL: https://jira.codehaus.org/browse/MPLUGIN-214 Project: Maven 2.x Plugin Tools Issue Type: Bug Components: maven-plugin-tools-annotations Affects Versions: 3.0 Reporter: Herve Boutemy Priority: Trivial as reported in [mavendev|http://mail-archives.apache.org/mod_mbox/maven-dev/201206.mbox/%3Cop.wgcyfqiskdkhrr%40columbia%3E], project, session and settings have an implementation and required is false (was true) this doesn't have any impact since these objects are injected by Maven core, not by Plexus, but making sure the same description is generated will help users confidence -- 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
