geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lin Sun (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-4346) c-m-p doesn't update plugin catalog when desp is added/updated to a plugin's pom.xml file
Date Fri, 10 Oct 2008 03:26:47 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638469#action_12638469
] 

Lin Sun commented on GERONIMO-4346:
-----------------------------------

There are two probs here -

1. when some information of plugin is changed (such as license, category, name, url, etc.),
we keep the plugin in the plugin catalog but remove the associated pluginArtifact and add
the new plugin into the catalog.   This would result invalid plugin in the catalog, as pluginArtifact
is required.

2. when description of a plugin is updated, we treat the old plugin and new plugin key unchanged,
thus we would only update the pluginartifact.

> c-m-p doesn't update plugin catalog when desp is added/updated to a plugin's pom.xml
file
> -----------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4346
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4346
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: car-maven-plugin
>    Affects Versions: 2.2
>            Reporter: Lin Sun
>            Assignee: Lin Sun
>            Priority: Minor
>
> when I made changes (http://svn.apache.org/viewvc?rev=703224&view=rev) and build
locally at trunk/plugins/console, I found out the local m2's geronimo-plugins.xml isn't updated
with the new description I added.  This is likely a c-m-p issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message