[jira] (MWAR-248) Plugin warns about missing webxml attribute even if one exists
[ https://jira.codehaus.org/browse/MWAR-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289239#comment-289239 ] Kristian Rosenvold commented on MWAR-248: - We'll have to go to plexus-archiver 2.1 for this one before releasing. 2.0.2 contains a file-mode bug that hits linux systems when unzipping archives with unspecified file permissions. I can push war-release together with archiver "tomorrow". > Plugin warns about missing webxml attribute even if one exists > -- > > Key: MWAR-248 > URL: https://jira.codehaus.org/browse/MWAR-248 > Project: Maven 2.x WAR Plugin > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: Gili >Assignee: Dennis Lundberg > Fix For: 2.1.2 > > Attachments: debug.log > > > I am attaching a debug log that clearly demonstrates how the WAR plugin warns > about a missing webxml attribute which exists. I am attempting to let the > plugin know that the web.xml file it is encountering is the same one > specified by the webxml attribute. > My pom file contains: > > org.apache.maven.plugins > maven-war-plugin > 2.1.1 > > true > src/main/webapp/WEB-INF/web.xml > > -- 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] (MWAR-273) Add Maven version used to Created-By entry in manifest
[ https://jira.codehaus.org/browse/MWAR-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289238#comment-289238 ] Anders Hammar commented on MWAR-273: @Dennis: Yes, the Maven version is only included in the Manifest when building with 3.0.4+. Older version will only state "Apache Maven" (the same as currently). > Add Maven version used to Created-By entry in manifest > -- > > Key: MWAR-273 > URL: https://jira.codehaus.org/browse/MWAR-273 > Project: Maven 2.x WAR Plugin > Issue Type: Improvement >Affects Versions: 2.1.1 > Environment: n/a >Reporter: Anders Hammar > Attachments: MWAR-273.patch > > > Upgrade the dependency to org.apache.maven:maven-archiver to newer version > (when released) to get the version of Maven Core used for building included > in the Created-By manifest entry. The call to MavenArchiver also needs to be > slightly updated to pass along the MavenSession. -- 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] (MSHARED-134) Using ${artifcactId}-Extention-Name in MANIFEST file can create invalid MANIFEST files
[
https://jira.codehaus.org/browse/MSHARED-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated MSHARED-134:
---
Component/s: maven-archiver
> Using ${artifcactId}-Extention-Name in MANIFEST file can create invalid
> MANIFEST files
> --
>
> Key: MSHARED-134
> URL: https://jira.codehaus.org/browse/MSHARED-134
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: maven-archiver-2.4
> Environment: Java HotSpot(TM) Client VM (build 1.5.0_13-121)
>Reporter: Todd Caine
> Attachments: MavenArchiver.java-Patch.txt, nautilus-debug-log.txt
>
>
> If you have a maven dependency on an something with an artifactId that
> contains a '.' in it, it creates an illegal manifest file when trying to
> create an executable jar file (java -jar foo.jar).
> {noformat}
> Exception in thread "main" java.io.IOException: invalid header field name:
> geronimo-jms_1.1_spec-Extension-Name
> at java.util.jar.Attributes.read(Attributes.java:409)
> at java.util.jar.Manifest.read(Manifest.java:167)
> at java.util.jar.Manifest.(Manifest.java:52)
> at java.util.jar.JarFile.getManifestFromReference(JarFile.java:158)
> at java.util.jar.JarFile.getManifest(JarFile.java:145)
> {noformat}
> Here's my configuration:
> {code:xml}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
>
> my.class.Test
> true
> true
> ./lib/
>
>
>
>
> {code}
> I added the following dependency:
> {code:xml}
>
> org.apache.geronimo.specs
> geronimo-jms_1.1_spec
>
> {code}
> When the maven-archiver tries to create a manifest file with the JARs
> dependencies it adds the following to the META-INF/MANIFEST.MF file:
> {noformat}
> geronimo-jms_1.1_spec-Extension-Name: geronimo-jms_1.1_spec
> geronimo-jms_1.1_spec-Implementation-Version: 1.0
> {noformat}
> After digging around a bit it turns out that '.' is an illegal character in
> the "Extension-Name" and "Implementaion-Version" header fields, which leads
> to the following exception when I try to run "java -jar Test.jar"
> java.io.IOException: invalid header field name:
> geronimo-jms_1.1_spec-Extension-Name
--
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] (SCM-659) gitexe SCM: Configurability of SCM info method
[ https://jira.codehaus.org/browse/SCM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289217#comment-289217 ] Paul Hicks commented on SCM-659: Oops, this should be a minor. Don't have permission to edit it. Sorry. > gitexe SCM: Configurability of SCM info method > --- > > Key: SCM-659 > URL: https://jira.codehaus.org/browse/SCM-659 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-git >Affects Versions: 1.6 >Reporter: Paul Hicks > > I need to use the output of "git describe" with the buildnumber plugin. The > newest versions of gitexe scm are using "git rev-parse --verify HEAD" which > is a sensible choice, but won't work for me. Is there a way to configure how > the info method works? I can't find a definition of the API. > I'd be happy to develop this and submit a patch. I just need to know how > individual methods in the SCM plugin are configured. I'm not having any luck > with http://maven.apache.org/scm/maven-scm-api/ -- 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] (SCM-659) gitexe SCM: Configurability of SCM info method
Paul Hicks created SCM-659: -- Summary: gitexe SCM: Configurability of SCM info method Key: SCM-659 URL: https://jira.codehaus.org/browse/SCM-659 Project: Maven SCM Issue Type: Improvement Components: maven-scm-provider-git Affects Versions: 1.6 Reporter: Paul Hicks I need to use the output of "git describe" with the buildnumber plugin. The newest versions of gitexe scm are using "git rev-parse --verify HEAD" which is a sensible choice, but won't work for me. Is there a way to configure how the info method works? I can't find a definition of the API. I'd be happy to develop this and submit a patch. I just need to know how individual methods in the SCM plugin are configured. I'm not having any luck with http://maven.apache.org/scm/maven-scm-api/ -- 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] (MWAR-273) Add Maven version used to Created-By entry in manifest
[ https://jira.codehaus.org/browse/MWAR-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289205#comment-289205 ] Dennis Lundberg commented on MWAR-273: -- Patch applied in [r1235053|http://svn.apache.org/viewvc?view=revision&revision=1235053] with minor modifications. > Add Maven version used to Created-By entry in manifest > -- > > Key: MWAR-273 > URL: https://jira.codehaus.org/browse/MWAR-273 > Project: Maven 2.x WAR Plugin > Issue Type: Improvement >Affects Versions: 2.1.1 > Environment: n/a >Reporter: Anders Hammar > Attachments: MWAR-273.patch > > > Upgrade the dependency to org.apache.maven:maven-archiver to newer version > (when released) to get the version of Maven Core used for building included > in the Created-By manifest entry. The call to MavenArchiver also needs to be > slightly updated to pass along the MavenSession. -- 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] (MWAR-273) Add Maven version used to Created-By entry in manifest
[ https://jira.codehaus.org/browse/MWAR-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289204#comment-289204 ] Dennis Lundberg commented on MWAR-273: -- Hi Anders, Do I understand correctly that this will only work for Maven 3.0.4+ ? > Add Maven version used to Created-By entry in manifest > -- > > Key: MWAR-273 > URL: https://jira.codehaus.org/browse/MWAR-273 > Project: Maven 2.x WAR Plugin > Issue Type: Improvement >Affects Versions: 2.1.1 > Environment: n/a >Reporter: Anders Hammar > Attachments: MWAR-273.patch > > > Upgrade the dependency to org.apache.maven:maven-archiver to newer version > (when released) to get the version of Maven Core used for building included > in the Created-By manifest entry. The call to MavenArchiver also needs to be > slightly updated to pass along the MavenSession. -- 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] (MWAR-248) Plugin warns about missing webxml attribute even if one exists
[ https://jira.codehaus.org/browse/MWAR-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MWAR-248. Resolution: Fixed Assignee: Dennis Lundberg Fixed by upgrading plexus-archiver to version 2.0.2. > Plugin warns about missing webxml attribute even if one exists > -- > > Key: MWAR-248 > URL: https://jira.codehaus.org/browse/MWAR-248 > Project: Maven 2.x WAR Plugin > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: Gili >Assignee: Dennis Lundberg > Fix For: 2.1.2 > > Attachments: debug.log > > > I am attaching a debug log that clearly demonstrates how the WAR plugin warns > about a missing webxml attribute which exists. I am attempting to let the > plugin know that the web.xml file it is encountering is the same one > specified by the webxml attribute. > My pom file contains: > > org.apache.maven.plugins > maven-war-plugin > 2.1.1 > > true > src/main/webapp/WEB-INF/web.xml > > -- 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] (ARCHETYPE-397) Required property default value is not displayed correctly if a Velocity expression
[
https://jira.codehaus.org/browse/ARCHETYPE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Hugonnet updated ARCHETYPE-397:
Attachment: fix_archetype_397.patch
Patch to fix this problem : creating a VelocityContext to display defaultValue
correctly
> Required property default value is not displayed correctly if a Velocity
> expression
> ---
>
> Key: ARCHETYPE-397
> URL: https://jira.codehaus.org/browse/ARCHETYPE-397
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator
>Affects Versions: 2.2
>Reporter: Nicolas Dupont
> Attachments: fix_archetype_397.patch
>
>
> If you use a Velocity expression to define a default value in your archetype
> descriptor, it is not displayed correctly when you generate a project.
> Let's say we have, in our descriptor :
> ${groupId}.${artifactId}
> When you generate a project from the archetype, you type com.company as a
> groupId and my-project as an artifactId. Then you'll be prompted for the
> package and default value will be displayed as "com.company.my-project".
> Now, if we have in our descriptor :
> {{ key="package">${groupId}.${artifactId.replace('-','')}}}
> When you generate a project in the same way, the default value for package
> will be displayed as ${groupId}.${artifactId.replace('-','')} instead of
> com.company.myproject.
> Note that if you leave the value as it is, the generation will do resolve the
> expression (package property will be resolve correctly). It's just confusing
> when the default value is showed at the prompt step.
--
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-5234) Error : Cannot override read-only parameter: classesDirectory in goal: war:manifest
Kavi created MNG-5234: - Summary: Error : Cannot override read-only parameter: classesDirectory in goal: war:manifest Key: MNG-5234 URL: https://jira.codehaus.org/browse/MNG-5234 Project: Maven 2 & 3 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.2.1 Environment: Redhat Linux Reporter: Kavi Priority: Critical Attachments: maven_error.jpg Hi, While executing maven with any of the code coverage reporting plugins (cobertura, jacoco, clover), I get the following error: [ERROR] BUILD ERROR [INFO] [INFO] Error configuring: org.apache.maven.plugins:maven-war-plugin. Reason: ERROR: Cannot override read-only parameter: classesDirectory in goal: war:manifest Though the classes directory is not read-only on the system, I am unable to figure out the issue. The following maven goals were executed: 'clean install cobertura:cobertura -Pdev' or 'clean install jacoco:report -Pdev' oe 'clean install clover:clover -Pdev'. They build and pass the instrumentation steps, however, after the stages of war:manifest, war:war, the above error is thrown and the Build fails. Could you please help fix the same so that Sonar can be configured to read the code coverage statistics and display them on the dashboard ? The versions used are: Maven: 2.2.1 Sonar: 2.12 Jenkins: 1.447 Sonar Plugin: 1.7.2 Jenkins Cobertura Plugin: 1.3 Please note: This issue was also reported as http://jira.codehaus.org/browse/MRM-636 and http://jira.codehaus.org/browse/SONAR-855 Thanks. -- 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-342) maven-dependency-plugin goal build-classpath is not written in correct order.
[ https://jira.codehaus.org/browse/MDEP-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Lindgren updated MDEP-342: - Attachment: classpathorderproblem.zip mvn dependency:build-classpath is not producing the classpath in the same order as mvn dependency:tree > maven-dependency-plugin goal build-classpath is not written in correct order. > - > > Key: MDEP-342 > URL: https://jira.codehaus.org/browse/MDEP-342 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: build-classpath >Affects Versions: 2.4 >Reporter: Anders Lindgren > Attachments: classpathorderproblem.zip > > > When running the goal build-classpath, the order of the dependencies in the > output is not the same as in the pom. > The dependency:tree is however producing output in correct order. > Also, when producing an executable jar using the maven-jar-plugin with > addClasspath set to true, the result is correct. -- 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-342) maven-dependency-plugin goal build-classpath is not written in correct order.
Anders Lindgren created MDEP-342: Summary: maven-dependency-plugin goal build-classpath is not written in correct order. Key: MDEP-342 URL: https://jira.codehaus.org/browse/MDEP-342 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: build-classpath Affects Versions: 2.4 Reporter: Anders Lindgren When running the goal build-classpath, the order of the dependencies in the output is not the same as in the pom. The dependency:tree is however producing output in correct order. Also, when producing an executable jar using the maven-jar-plugin with addClasspath set to true, the result is correct. -- 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] (MNGSITE-150) Installation guide creates unnecessary M2 variable
SebbASF created MNGSITE-150: --- Summary: Installation guide creates unnecessary M2 variable Key: MNGSITE-150 URL: https://jira.codehaus.org/browse/MNGSITE-150 Project: Maven Project Web Site Issue Type: Bug Environment: http://maven.apache.org/download.html#Installation Reporter: SebbASF Priority: Minor The installation guide says one needs to create an "M2" environment variable. However, M2 only appears to be used for updating the PATH; it does not appear to be used by the Maven scripts. If it's not necessary - only a convenience - then this should be stated, and / or the instructions reworded to avoid using it. -- 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-24) Add the Twitter follow button support
[
https://jira.codehaus.org/browse/MSKINS-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289138#comment-289138
]
Lars Francke commented on MSKINS-24:
I tried, yeah and it does not work locally. I now tried to actually deploy a
site and then the JS seems to be working. The _Using Javascript_ section
actually has multiple different snippets and some actually do include the
{{http:}} scheme. Don't know why it's missing in some of them and is there in
others.
Sorry for the confusion but I didn't want to deploy the site with the button
not working...but turns out I should have just done it ;-)
> Add the Twitter follow button support
> -
>
> Key: MSKINS-24
> URL: https://jira.codehaus.org/browse/MSKINS-24
> Project: Maven Skins
> Issue Type: New Feature
> Components: Fluido Skin
>Affects Versions: fluido-1.1
>Reporter: Simone Tripodi
>Assignee: Simone Tripodi
> Fix For: fluido-1.1
>
>
> With few configuration parameters in the {{custom.fluidoSkin}} section in
> {{site.xml}} it is possible to add [Twitter follow
> button|https://dev.twitter.com/docs/follow-button] support
--
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-24) Add the Twitter follow button support
[
https://jira.codehaus.org/browse/MSKINS-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289137#comment-289137
]
Simone Tripodi commented on MSKINS-24:
--
did you try it? It is currently working, see the related
[IT|http://maven.apache.org/skins/maven-fluido-skin/mskins-24_topbar/index.html]
Have a look at the Twitter's [Follow
Button|https://dev.twitter.com/docs/follow-button] documentation, read the
section _Using Javascript_ to see why it is missing ;)
> Add the Twitter follow button support
> -
>
> Key: MSKINS-24
> URL: https://jira.codehaus.org/browse/MSKINS-24
> Project: Maven Skins
> Issue Type: New Feature
> Components: Fluido Skin
>Affects Versions: fluido-1.1
>Reporter: Simone Tripodi
>Assignee: Simone Tripodi
> Fix For: fluido-1.1
>
>
> With few configuration parameters in the {{custom.fluidoSkin}} section in
> {{site.xml}} it is possible to add [Twitter follow
> button|https://dev.twitter.com/docs/follow-button] support
--
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-24) Add the Twitter follow button support
[
https://jira.codehaus.org/browse/MSKINS-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289136#comment-289136
]
Lars Francke commented on MSKINS-24:
Looks like there's a "http:" missing.
It only produces
{code}js.src = "//platform.twitter.com/widgets.js";{code}
instead of
{code}js.src = "http://platform.twitter.com/widgets.js";{code}
> Add the Twitter follow button support
> -
>
> Key: MSKINS-24
> URL: https://jira.codehaus.org/browse/MSKINS-24
> Project: Maven Skins
> Issue Type: New Feature
> Components: Fluido Skin
>Affects Versions: fluido-1.1
>Reporter: Simone Tripodi
>Assignee: Simone Tripodi
> Fix For: fluido-1.1
>
>
> With few configuration parameters in the {{custom.fluidoSkin}} section in
> {{site.xml}} it is possible to add [Twitter follow
> button|https://dev.twitter.com/docs/follow-button] support
--
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] (DOXIATOOLS-16) NullPointerException when site URL is being generated
Marc Claessens created DOXIATOOLS-16: Summary: NullPointerException when site URL is being generated Key: DOXIATOOLS-16 URL: https://jira.codehaus.org/browse/DOXIATOOLS-16 Project: Maven Doxia Tools Issue Type: Bug Environment: environment independent Reporter: Marc Claessens We have a parent POM where the site url is generated via the Maven Groovy plugin, unless it is explicitly defined in the child POM i.e. project-sites Our project Nexus server Site ... org.codehaus.groovy.maven gmaven-plugin pre-site execute } This leads to a NullPointerException in DefaultSiteTool.java: at java.io.File.(File.java:222) at org.apache.maven.doxia.tools.DefaultSiteTool.urlEncode(DefaultSiteTool.java:1478) at org.apache.maven.doxia.tools.DefaultSiteTool.getDistMgmntSiteUrl(DefaultSiteTool.java:1451) The if statement in getDistMgntSiteUrl (for both methods) should test for null on project.getDistributionManagement().getSite().getUrl() -- 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-5233) ArtifactMetadataRetrievalException from org.apache.maven.artifact.metadata is not anymore binary compatible.
[
https://jira.codehaus.org/browse/MNG-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MNG-5233.
-
Resolution: Fixed
fixed r1234715
> ArtifactMetadataRetrievalException from org.apache.maven.artifact.metadata is
> not anymore binary compatible.
>
>
> Key: MNG-5233
> URL: https://jira.codehaus.org/browse/MNG-5233
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0, 3.0.1, 3.0.4
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
> Fix For: 3.0.5
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:features-maven-plugin:2.2.5:generate-features-file
> (validate) on project feature.protocol: Execution validate of goal
> org.apache.karaf.tooling:features-maven-plugin:2.2.5:generate-features-file
> failed: An API incompatibility was encountered while executing
> org.apache.karaf.tooling:features-maven-plugin:2.2.5:generate-features-file:
> java.lang.NoSuchMethodError:
> org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: method
> (Ljava/lang/String;)V not found
> {code}
--
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-5233) ArtifactMetadataRetrievalException from org.apache.maven.artifact.metadata is not anymore binary compatible.
[
https://jira.codehaus.org/browse/MNG-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MNG-5233:
--
Description:
{code}
[ERROR] Failed to execute goal
org.apache.karaf.tooling:features-maven-plugin:2.2.5:generate-features-file
(validate) on project feature.protocol: Execution validate of goal
org.apache.karaf.tooling:features-maven-plugin:2.2.5:generate-features-file
failed: An API incompatibility was encountered while executing
org.apache.karaf.tooling:features-maven-plugin:2.2.5:generate-features-file:
java.lang.NoSuchMethodError:
org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: method
(Ljava/lang/String;)V not found
{code}
Affects Version/s: 3.0.4
Fix Version/s: 3.0.5
Assignee: Olivier Lamy
> ArtifactMetadataRetrievalException from org.apache.maven.artifact.metadata is
> not anymore binary compatible.
>
>
> Key: MNG-5233
> URL: https://jira.codehaus.org/browse/MNG-5233
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0, 3.0.1, 3.0.4
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
> Fix For: 3.0.5
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:features-maven-plugin:2.2.5:generate-features-file
> (validate) on project feature.protocol: Execution validate of goal
> org.apache.karaf.tooling:features-maven-plugin:2.2.5:generate-features-file
> failed: An API incompatibility was encountered while executing
> org.apache.karaf.tooling:features-maven-plugin:2.2.5:generate-features-file:
> java.lang.NoSuchMethodError:
> org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: method
> (Ljava/lang/String;)V not found
> {code}
--
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-5233) ArtifactMetadataRetrievalException from org.apache.maven.artifact.metadata is not anymore binary compatible.
Olivier Lamy created MNG-5233: - Summary: ArtifactMetadataRetrievalException from org.apache.maven.artifact.metadata is not anymore binary compatible. Key: MNG-5233 URL: https://jira.codehaus.org/browse/MNG-5233 Project: Maven 2 & 3 Issue Type: Bug Affects Versions: 3.0.1, 3.0 Reporter: Olivier Lamy -- 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] (SCM-658) HgChangeLogCommand doesn't implement method executeChangeLogCommand()
Vladimir Kralik created SCM-658: --- Summary: HgChangeLogCommand doesn't implement method executeChangeLogCommand() Key: SCM-658 URL: https://jira.codehaus.org/browse/SCM-658 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-mercurial (hg) Affects Versions: 1.6 Environment: maven 2.2.1, 3.0.3 Reporter: Vladimir Kralik Priority: Blocker Class org.apache.maven.scm.provider.hg.command.changelog.HgChangeLogCommand doesn't implement method of abstract parent class org.apache.maven.scm.command.changelog.AbstractChangeLogCommand protected ChangeLogScmResult executeChangeLogCommand( ScmProviderRepository repository, ScmFileSet fileSet, ScmVersion startVersion, ScmVersion endVersion, String datePattern ) I think, that this is the main reason of SONARPLUGINS-1157 ( http://jira.codehaus.org/browse/SONARPLUGINS-1157 ). -- 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
