You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Kenney Westerhof (JIRA)" <ji...@codehaus.org> on 2005/07/15 12:49:57 UTC
[jira] Created: (MNG-592) [maven-plugin-mapping] error retrieving mappings when custom PluginRepository specified
[maven-plugin-mapping] error retrieving mappings when custom PluginRepository specified
---------------------------------------------------------------------------------------
Key: MNG-592
URL: http://jira.codehaus.org/browse/MNG-592
Project: Maven 2
Type: Bug
Versions: 2.0-beta-1
Reporter: Kenney Westerhof
Priority: Critical
When a custom PluginRepository is specified in the pom (or a parent pom),
m2 can't load the plugins.xml. When the repository is removed, it can find it again.
It checks both repositories, and fails at the second repo, invalidating/forgetting the plugins.xml from
the first repo.
This is a major problem since now ejb/war builds don't produce the correct artifacts,
even when the plugin is specified in the pom. It seems it's not bound to the lifecycle.
[INFO] ----------------------------------------------------------------------------
[INFO] Retrieving plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins'
[INFO] Retrieving plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins'
[INFO] Cannot find plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins' in remote repository - Using local copy.
[WARNING] Cannot resolve plugin-mapping metadata for groupId: org.apache.maven.plugins - IGNORING.
[ERROR] Nonexistent component: org.apache.maven.lifecycle.mapping.LifecycleMappingejb
[WARNING] Lifecycle mappings not found for packaging: 'ejb'. Using defaults.
[snip]
[INFO] maven-archiver: using locally installed snapshot
[INFO] [jar:jar]
[INFO] Building jar: [snip]...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-592) [maven-plugin-mapping] error retrieving mappings when custom PluginRepository specified
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-592?page=all ]
John Casey closed MNG-592:
--------------------------
Resolution: Fixed
should work now, refer to it2000 for testing.
> [maven-plugin-mapping] error retrieving mappings when custom PluginRepository specified
> ---------------------------------------------------------------------------------------
>
> Key: MNG-592
> URL: http://jira.codehaus.org/browse/MNG-592
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Reporter: Kenney Westerhof
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> When a custom PluginRepository is specified in the pom (or a parent pom),
> m2 can't load the plugins.xml. When the repository is removed, it can find it again.
> It checks both repositories, and fails at the second repo, invalidating/forgetting the plugins.xml from
> the first repo.
> This is a major problem since now ejb/war builds don't produce the correct artifacts,
> even when the plugin is specified in the pom. It seems it's not bound to the lifecycle.
> [INFO] ----------------------------------------------------------------------------
> [INFO] Retrieving plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins'
> [INFO] Retrieving plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins'
> [INFO] Cannot find plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins' in remote repository - Using local copy.
> [WARNING] Cannot resolve plugin-mapping metadata for groupId: org.apache.maven.plugins - IGNORING.
> [ERROR] Nonexistent component: org.apache.maven.lifecycle.mapping.LifecycleMappingejb
> [WARNING] Lifecycle mappings not found for packaging: 'ejb'. Using defaults.
> [snip]
> [INFO] maven-archiver: using locally installed snapshot
> [INFO] [jar:jar]
> [INFO] Building jar: [snip]...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-592) [maven-plugin-mapping] error retrieving mappings when custom PluginRepository specified
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-592?page=all ]
Brett Porter updated MNG-592:
-----------------------------
Fix Version: 2.0-beta-1
> [maven-plugin-mapping] error retrieving mappings when custom PluginRepository specified
> ---------------------------------------------------------------------------------------
>
> Key: MNG-592
> URL: http://jira.codehaus.org/browse/MNG-592
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Reporter: Kenney Westerhof
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> When a custom PluginRepository is specified in the pom (or a parent pom),
> m2 can't load the plugins.xml. When the repository is removed, it can find it again.
> It checks both repositories, and fails at the second repo, invalidating/forgetting the plugins.xml from
> the first repo.
> This is a major problem since now ejb/war builds don't produce the correct artifacts,
> even when the plugin is specified in the pom. It seems it's not bound to the lifecycle.
> [INFO] ----------------------------------------------------------------------------
> [INFO] Retrieving plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins'
> [INFO] Retrieving plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins'
> [INFO] Cannot find plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins' in remote repository - Using local copy.
> [WARNING] Cannot resolve plugin-mapping metadata for groupId: org.apache.maven.plugins - IGNORING.
> [ERROR] Nonexistent component: org.apache.maven.lifecycle.mapping.LifecycleMappingejb
> [WARNING] Lifecycle mappings not found for packaging: 'ejb'. Using defaults.
> [snip]
> [INFO] maven-archiver: using locally installed snapshot
> [INFO] [jar:jar]
> [INFO] Building jar: [snip]...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-592) [maven-plugin-mapping] error retrieving mappings when custom PluginRepository specified
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-592?page=comments#action_44154 ]
John Casey commented on MNG-592:
--------------------------------
this should no longer impact the lifecycle-mapping stuff, but I'll verify that the other bit has been fixed.
> [maven-plugin-mapping] error retrieving mappings when custom PluginRepository specified
> ---------------------------------------------------------------------------------------
>
> Key: MNG-592
> URL: http://jira.codehaus.org/browse/MNG-592
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Reporter: Kenney Westerhof
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> When a custom PluginRepository is specified in the pom (or a parent pom),
> m2 can't load the plugins.xml. When the repository is removed, it can find it again.
> It checks both repositories, and fails at the second repo, invalidating/forgetting the plugins.xml from
> the first repo.
> This is a major problem since now ejb/war builds don't produce the correct artifacts,
> even when the plugin is specified in the pom. It seems it's not bound to the lifecycle.
> [INFO] ----------------------------------------------------------------------------
> [INFO] Retrieving plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins'
> [INFO] Retrieving plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins'
> [INFO] Cannot find plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins' in remote repository - Using local copy.
> [WARNING] Cannot resolve plugin-mapping metadata for groupId: org.apache.maven.plugins - IGNORING.
> [ERROR] Nonexistent component: org.apache.maven.lifecycle.mapping.LifecycleMappingejb
> [WARNING] Lifecycle mappings not found for packaging: 'ejb'. Using defaults.
> [snip]
> [INFO] maven-archiver: using locally installed snapshot
> [INFO] [jar:jar]
> [INFO] Building jar: [snip]...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org