You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Stuart Bell (JIRA)" <ji...@apache.org> on 2007/02/05 17:50:05 UTC
[jira] Reopened: (AXIS2-2072) Code generator Eclipse plug-in not
working when building from source
[ https://issues.apache.org/jira/browse/AXIS2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart Bell reopened AXIS2-2072:
--------------------------------
Although I am able to build the source and create what looks like the appropriate plug-in content, I am still getting the following error when trying to use the code generator (File->New->Other):
The selected wizard could not be started.
Reason:
Plug-in Axis2_Codegen_Wizard was unablet o load class org.apache.axis2.tool.codegen.eclipse.CodeGenWizard
------------
Under the <<Details button the following class was listed:
org/apache/axis2/util/CommandLinOptionConstants$Java2WSDLConstants
-------------
Searching for this class, it was found in axis2-kernel-1.1.1.jar, which is referenced in the plugin.xml file for the plug-in.
Any thoughts on what is causing this? I am using Eclipse 3.2.1.
Thanks,
Stuart
> Code generator Eclipse plug-in not working when building from source
> --------------------------------------------------------------------
>
> Key: AXIS2-2072
> URL: https://issues.apache.org/jira/browse/AXIS2-2072
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.1.1
> Environment: Windows XP, Eclipse 3.2.1, JDK 1.4.2
> Reporter: Stuart Bell
> Assigned To: Lahiru Sandakith
>
> Attempted to follow the installation instructions here: http://ws.apache.org/axis2/tools/1_1/eclipse/wsdl2java-plugin.html
> I've never had such a difficult experience with other Eclipse plug-ins. I've had to go down the route of building the plug-in from the source. The create-project.xml for codegen seems to be broken as it is attempting to reference an axis2-1.1.1.jar which no longer exists. It seems that the Axis libraries have been broken up into multiple JARs. This seems to have happened changed with retrospectively updating the build script.
> Also, the installation guide for the plugin is very obscure. I am aware of Maven, but I have never used it. Do I really have to spend days figuring out Maven just to re-build a plugin??
> Was the plugin never developed to be just dropped into the plugins directory in Eclipse?
> Regards,
> Stuart Bell
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org