Maven Publisher Plugin

maven-publisher: artifact pom installed in local repository has a "-plugin" suffix

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Labels:
    None
  • Environment:
    Grails 1.3.4
    maven-publisher 0.7.5

Description

I created an empty grails plug-in called 'admin-scaffold', and installed in my local maven repository with the maven-publisher plugin. It is packaged and installed in my local repository. The generated pom filename is

~/.m2/repository/org/grails/plugins/admin-scaffold/0.1/admin-scaffold-0.1-plugin.xml

The problem is that when I issue a grails plugin-info admin-scaffold grails will look for

~/.m2/repository/org/grails/plugins/admin-scaffold/0.1/admin-scaffold-0.1.xml

I attached the full output I get.

  1. Text File
    _GrailsMaven.groovy.patch
    14/Feb/11 10:50 AM
    0.5 kB
    Alessandro Mecca
  2. Text File
    plugin-info.log
    14/Feb/11 6:47 AM
    2 kB
    Alessandro Mecca
  3. Text File
    plugin-install.log
    14/Feb/11 6:47 AM
    2 kB
    Alessandro Mecca

Issue Links

depends on

Bug - A problem which impairs or prevents the functions of the product. GRAILS-6147 Maven classifier not working for deps

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Alessandro Mecca added a comment -

Renaming the admin-scaffold-0.1-plugin.xml file to admin-scaffold-0.1.xml makes grails plugin-info happy.

Show
Alessandro Mecca added a comment - Renaming the admin-scaffold-0.1-plugin.xml file to admin-scaffold-0.1.xml makes grails plugin-info happy.
Hide
Permalink
Alessandro Mecca added a comment -

The patch removes the line responsable for adding the "-plugin" suffix. With this the plugin is deployed as grails install-plugin expects to find it.

Show
Alessandro Mecca added a comment - The patch removes the line responsable for adding the "-plugin" suffix. With this the plugin is deployed as grails install-plugin expects to find it.
Hide
Permalink
Peter Ledbrook added a comment -

Sorry, but I don't think that's the appropriate fix. I'm trying to find out why Grails/Ivy is even looking for that .xml file. I'm pretty sure it's not after the *-plugin.xml.

Show
Peter Ledbrook added a comment - Sorry, but I don't think that's the appropriate fix. I'm trying to find out why Grails/Ivy is even looking for that .xml file. I'm pretty sure it's not after the *-plugin.xml .
Hide
Permalink
Peter Ledbrook added a comment -

This is actually a problem in Grails core in that it ignores the 'classifier' part of dependencies.

Show
Peter Ledbrook added a comment - This is actually a problem in Grails core in that it ignores the 'classifier' part of dependencies.
Hide
Permalink
Luke Daley added a comment -

@Peter: I think this is a different problem.

When the dependency artifact is created in Grails, the classifier is not pushed down to it.

https://github.com/grails/grails-core/blob/master/grails-bootstrap/src/main/groovy/org/codehaus/groovy/grails/resolve/AbstractIvyDependencyManager.java#L492

Show
Luke Daley added a comment - @Peter: I think this is a different problem. When the dependency artifact is created in Grails, the classifier is not pushed down to it. https://github.com/grails/grails-core/blob/master/grails-bootstrap/src/main/groovy/org/codehaus/groovy/grails/resolve/AbstractIvyDependencyManager.java#L492
Hide
Permalink
Luke Daley added a comment -

Should be fixed by https://github.com/grails/grails-core/commit/b009969179529d5e59233bf4d2484491bdba0877

Show
Luke Daley added a comment - Should be fixed by https://github.com/grails/grails-core/commit/b009969179529d5e59233bf4d2484491bdba0877

People

  • Assignee:
    Peter Ledbrook
    Reporter:
    Alessandro Mecca
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: