The following issue has been updated:
Updater: Vincent Massol (mailto:[EMAIL PROTECTED])
Date: Sat, 17 Apr 2004 8:28 AM
Changes:
assignee changed from Cactus Developers Mailing List to Vincent Massol
description changed from The version number in the
org.apache.cactus.eclipse.runner_20030722 plugin is
not numeric and Eclipse will not load the plugin as a result. Under
configuration information one can find error messages of the ilk:
!SUBENTRY 1 org.eclipse.core.runtime 2 1 Jul 25, 2003 14:41:04.244
!MESSAGE Error while processing "file:G:/Program
Files/eclipse/plugins/org.apache.cactus.eclipse.runner_20030713/plugin.xml:
assertion failed: The major (1st) component of plug-in version identifier,
"${project.version.plugin}", must be numeric.".
!SUBENTRY 1 org.eclipse.core.runtime 2 1 Jul 25, 2003 14:41:04.244
!MESSAGE Error while processing "file:G:/Program
Files/eclipse/plugins/org.apache.cactus.eclipse.runner_20030715/plugin.xml:
assertion failed: The major (1st) component of plug-in version identifier,
"${project.version.plugin}", must be numeric.".
Changing the version number in the plugin.xml to the same value as in the webapp
plugin fixes the problem. It looks like something in the build process is not
working properly.
Chris Marshall to The version number in the org.apache.cactus.eclipse.runner_20030722
plugin is
not numeric and Eclipse will not load the plugin as a result. Under
configuration information one can find error messages of the ilk:
!SUBENTRY 1 org.eclipse.core.runtime 2 1 Jul 25, 2003 14:41:04.244
!MESSAGE Error while processing "file:G:/Program
Files/eclipse/plugins/org.apache.cactus.eclipse.runner_20030713/plugin.xml:
assertion failed: The major (1st) component of plug-in version identifier,
"${project.version.plugin}", must be numeric.".
!SUBENTRY 1 org.eclipse.core.runtime 2 1 Jul 25, 2003 14:41:04.244
!MESSAGE Error while processing "file:G:/Program
Files/eclipse/plugins/org.apache.cactus.eclipse.runner_20030715/plugin.xml:
assertion failed: The major (1st) component of plug-in version identifier,
"${project.version.plugin}", must be numeric.".
Changing the version number in the plugin.xml to the same value as in the webapp
plugin fixes the problem. It looks like something in the build process is not
working properly.
Chris Marshall
environment changed from Operating System: All
Platform: All to Operating System: All
Platform: All
priority changed to Blocker
Fix Version changed to 1.5-rc1
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/CACTUS-47?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/CACTUS-47
Here is an overview of the issue:
---------------------------------------------------------------------
Key: CACTUS-47
Summary: version number in plugin.xml is not numeric
Type: Bug
Status: Resolved
Priority: Blocker
Resolution: FIXED
Project: Cactus
Components:
Eclipse Integration
Fix Fors:
1.5-rc1
Versions:
1.5-beta1
Assignee: Vincent Massol
Reporter: Christopher Marshall
Created: Fri, 25 Jul 2003 6:58 PM
Updated: Sat, 17 Apr 2004 8:28 AM
Environment: Operating System: All
Platform: All
Description:
The version number in the org.apache.cactus.eclipse.runner_20030722 plugin is
not numeric and Eclipse will not load the plugin as a result. Under
configuration information one can find error messages of the ilk:
!SUBENTRY 1 org.eclipse.core.runtime 2 1 Jul 25, 2003 14:41:04.244
!MESSAGE Error while processing "file:G:/Program
Files/eclipse/plugins/org.apache.cactus.eclipse.runner_20030713/plugin.xml:
assertion failed: The major (1st) component of plug-in version identifier,
"${project.version.plugin}", must be numeric.".
!SUBENTRY 1 org.eclipse.core.runtime 2 1 Jul 25, 2003 14:41:04.244
!MESSAGE Error while processing "file:G:/Program
Files/eclipse/plugins/org.apache.cactus.eclipse.runner_20030715/plugin.xml:
assertion failed: The major (1st) component of plug-in version identifier,
"${project.version.plugin}", must be numeric.".
Changing the version number in the plugin.xml to the same value as in the webapp
plugin fixes the problem. It looks like something in the build process is not
working properly.
Chris Marshall
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
