jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2.x SHITTY Plugin
  • MSHITTY-10

install must fix the plugin descriptor version before installing the jar

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: 1.0-alpha-1
  • Fix Version/s: 1.0-alpha-4
  • Component/s: Install
  • Labels:
    None

Description

The install goal seems only to be taking the already built jar and installing it with the "testing" version into the repo. The plugins contain metadata that has the version. If this version is not also updated to "testing" then bad things can happen. Specifically the plugin isn't found and default phases aren't used when running tests under 2.1.

We had a similar problem with the plugin-testing-harness that corrupted the default artifact with "test" and thus screwed people up at runtime. More info is here: MECLIPSE-239

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Text File
    MSHITTY-10.patch
    06/Apr/10 10:20 PM
    15 kB
    Richard Vowles

Issue Links

is depended upon by

Bug - A problem which impairs or prevents the functions of the product. MRPM-80 Integration tests fail using maven 2.2.1

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MSHITTY-33 Maven SHITTY Plugin fails when used with Maven 2.1.0 (Needs to update internal plugin metadata)

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.
is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-3284 Cached plugins are used, even when the specifically declared

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

Bug - A problem which impairs or prevents the functions of the product. MNG-1323 Plugin extensions (dependencies) not resolved in reactor build

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. MOJO-1359 -Pintegration-tests doesn't work on mvn 2.1.0

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Jason Dillon added a comment - 14/Aug/08 9:55 AM

This is actually causing gmaven release:prepare builds to fail... so need to sort this out soon.

Show
Jason Dillon added a comment - 14/Aug/08 9:55 AM This is actually causing gmaven release:prepare builds to fail... so need to sort this out soon.
Hide
Permalink
Richard Vowles added a comment - 06/Apr/10 10:20 PM

This patch fixes this problem. It causes the pom.xml to be re-written (if it has a version) and the jar to be extracted and the plugin.xml and pom.xml to be re-written.

The only thing it doesn't watch for is parent-POMs, but they don't seem to matter.

Show
Richard Vowles added a comment - 06/Apr/10 10:20 PM This patch fixes this problem. It causes the pom.xml to be re-written (if it has a version) and the jar to be extracted and the plugin.xml and pom.xml to be re-written. The only thing it doesn't watch for is parent-POMs, but they don't seem to matter.
Hide
Permalink
pkernevez added a comment - 07/May/10 8:22 AM

Hi,

We need this fix and I see that there isn't any release for 3 years.
Is any active developers on this plugin ? Or do I do a release myself ?

Show
pkernevez added a comment - 07/May/10 8:22 AM Hi, We need this fix and I see that there isn't any release for 3 years. Is any active developers on this plugin ? Or do I do a release myself ?
Hide
Permalink
Wim Deblauwe added a comment - 12/Jul/10 3:50 AM

This also affects the RPM maven plugin, see MRPM-80. I would link them, but I don't have the rights to do so it seems.

Show
Wim Deblauwe added a comment - 12/Jul/10 3:50 AM This also affects the RPM maven plugin, see MRPM-80. I would link them, but I don't have the rights to do so it seems.
Hide
Permalink
Brett Okken added a comment - 12/Jul/10 7:12 AM

I created the link to MRPM-80.

pkernevez, it would be great if you could do a release.

Show
Brett Okken added a comment - 12/Jul/10 7:12 AM I created the link to MRPM-80. pkernevez, it would be great if you could do a release.
Hide
Permalink
kristian meier added a comment - 12/Jul/10 12:08 PM

I also would appreciate a release fixing the bug. I have a workaround in place using the same version as the artifact which get tested (can be configured for shitty:install) instead of using the version 'testing'. but I have to update this version manually since the release plugin does not do this and there are quite some places to udpate.

Show
kristian meier added a comment - 12/Jul/10 12:08 PM I also would appreciate a release fixing the bug. I have a workaround in place using the same version as the artifact which get tested (can be configured for shitty:install) instead of using the version 'testing'. but I have to update this version manually since the release plugin does not do this and there are quite some places to udpate.

People

  • Assignee:
    Jason Dillon
    Reporter:
    Brian Fox
Vote (7)
Watch (9)

Dates

  • Created:
    10/Feb/08 12:13 PM
    Updated:
    12/Jul/10 12:08 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.