[JBoss JIRA] Created: (JBIDE-6731) cannot create bottom-up ws with ws-cxf
by Martin Malina (JIRA)
cannot create bottom-up ws with ws-cxf
--------------------------------------
Key: JBIDE-6731
URL: https://jira.jboss.org/browse/JBIDE-6731
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.1.0.GA
Environment: jbdevstudio-macosx-cocoa-3.0.1.v201006010437R-H98-GA.jar
jboss-eap-5.0.1.CR1.zip with jbossws-cxf-3.1.2.SP6-installer.zip installed
Mac OS X Snow Leopard
Reporter: Martin Malina
Assignee: Brian Fitzpatrick
I get an error when trying to created a web service:
Failed to Generate Web Service code, please check the log for more details.
The details show:
Failed to Generate Web Service code, please check the log for more details
...
java2ws - Apache CXF 2.2.6
/Users/rasp/jbossqa/workspace-eap/TestWSProject/src/test/ws/jaxws/Echo.java:23: cannot find symbol
symbol : class Person
location: package test
private test.Person arg0;
^
/Users/rasp/jbossqa/workspace-eap/TestWSProject/src/test/ws/jaxws/Echo.java:25: cannot find symbol
symbol : class Person
location: package test
public test.Person getArg0() {
^
...
This only happens when the selected runtime has ws-cxf installed. See the steps to reproduce.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-7050) Cannot change Server runtime when creating web service
by Libor Zoubek (JIRA)
Cannot change Server runtime when creating web service
------------------------------------------------------
Key: JBIDE-7050
URL: https://jira.jboss.org/browse/JBIDE-7050
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.M2
Reporter: Libor Zoubek
Assignee: Brian Fitzpatrick
When creating bottom-up web service, I am not able to change server runtime.
Add more than 1 server runtimes (I used EAP 5 and EAP 5.1)
1. run 'Web Service' wizard
2.Click 'Server Runtime' link
3. Select a runtime other than it was selected before
4. Click OK
5. Back in wizard page no changes are populated
Note that this does not seem to be WTP bug, I've tested it on helios-jee (used runtimes JBoss AS 4.2 and 5.0) without any problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8778) Can't build the parent & target platform poms.
by Alexey Kazakov (JIRA)
Can't build the parent & target platform poms.
----------------------------------------------
Key: JBIDE-8778
URL: https://issues.jboss.org/browse/JBIDE-8778
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Alexey Kazakov
Assignee: Nick Boldt
I'm doing the a) step from http://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3 and get the following exception:
igels@alexey-desktop:~/Projects/jbt-3.3/trunk$ mvn clean install -f build/parent/pom.xml -Dmaven.repo.local=.repository
[INFO] Scanning for projects...
[WARNING] No explicit target runtime environment configuration. Build is platform dependent.
[ERROR] Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools:org.jboss.tools.target.platform:target:unified:0.0.3-SNAPSHOT -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools:org.jboss.tools.target.platform:target:unified:0.0.3-SNAPSHOT
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools:org.jboss.tools.target.platform:target:unified:0.0.3-SNAPSHOT
at org.codehaus.tycho.resolver.DefaultTargetPlatformConfigurationReader.getTarget(DefaultTargetPlatformConfigurationReader.java:196)
at org.codehaus.tycho.resolver.DefaultTargetPlatformConfigurationReader.getTargetPlatformConfiguration(DefaultTargetPlatformConfigurationReader.java:53)
at org.codehaus.tycho.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:57)
at org.codehaus.tycho.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:94)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:273)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
... 11 more
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8754) JMX provider not found; regression due to separation of JMX integration
by Rob Stryker (JIRA)
JMX provider not found; regression due to separation of JMX integration
-----------------------------------------------------------------------
Key: JBIDE-8754
URL: https://issues.jboss.org/browse/JBIDE-8754
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.M1
During the separation of JMX integration into its own plugin, a typo led to the jmx provider not being found. Patch is as follows in class org.jboss.ide.eclipse.as.core.ExtensionManager:
- IConfigurationElement[] cf = registry.getConfigurationElementsFor(JBossServerCorePlugin.PLUGIN_ID, "pollers"); //$NON-NLS-1$
+ IConfigurationElement[] cf = registry.getConfigurationElementsFor(JBossServerCorePlugin.PLUGIN_ID, "jmxRunner"); //$NON-NLS-1$
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8556) Compilation failure for 3.3.indigo branch :: AS
by Nick Boldt (JIRA)
Compilation failure for 3.3.indigo branch :: AS
-----------------------------------------------
Key: JBIDE-8556
URL: https://issues.jboss.org/browse/JBIDE-8556
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_3.3.indigo.continuou...
[ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-compiler-plugin:0.10.0:compile (default-compile) on project org.jboss.tools.common: Compilation failure: Compilation failure:
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_3.3.indigo.continuous/sources/common/plugins/org.jboss.tools.common/src/org/jboss/tools/common/reporting/ProblemBuffer.java (at line 19):[-1,-1]
[ERROR] import org.eclipse.core.runtime.adaptor.EclipseLog;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.core.runtime.adaptor.EclipseLog cannot be resolved
[ERROR]
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_3.3.indigo.continuous/sources/common/plugins/org.jboss.tools.common/src/org/jboss/tools/common/reporting/ProblemBuffer.java (at line 110):[-1,-1]
[ERROR] log = new EclipseLog(getLogFile());
[ERROR] ^^^^^^^^^^
[ERROR] EclipseLog cannot be resolved to a type
[ERROR]
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_3.3.indigo.continuous/sources/common/plugins/org.jboss.tools.common/src/org/jboss/tools/common/reporting/ProblemBuffer.java (at line 111):[-1,-1]
[ERROR] writer = new PlatformLogWriter(log);
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The constructor PlatformLogWriter(FrameworkLog) is undefined
[ERROR]
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_3.3.indigo.continuous/sources/common/plugins/org.jboss.tools.common/src/org/jboss/tools/common/reporting/ProblemBuffer.java (at line 111):[-1,-1]
[ERROR] writer = new PlatformLogWriter(log);
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] Type mismatch: cannot convert from PlatformLogWriter to ILogListener
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8485) RSEZippedJSTPublisher cannot be resolved to a type; The type RSEZippedFolderPublisher is already defined
by Nick Boldt (JIRA)
RSEZippedJSTPublisher cannot be resolved to a type; The type RSEZippedFolderPublisher is already defined
--------------------------------------------------------------------------------------------------------
Key: JBIDE-8485
URL: https://issues.jboss.org/browse/JBIDE-8485
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Rob Stryker
[ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-compiler-plugin:0.10.0:compile (default-compile) on project org.jboss.ide.eclipse.as.rse.core: Compilation failure: Compilation failure:
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.2_trunk.component--as/sources/plugins/org.jboss.ide.eclipse.as.rse.core/src/org/jboss/ide/eclipse/as/rse/core/archives/RSEZippedJSTPublisher.java (at line 27):[-1,-1]
[ERROR] public class RSEZippedFolderPublisher extends RSEZippedJSTPublisher {
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The public type RSEZippedFolderPublisher must be defined in its own file
[ERROR]
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.2_trunk.component--as/sources/plugins/org.jboss.ide.eclipse.as.rse.core/src/org/jboss/ide/eclipse/as/rse/core/archives/RSEZippedJSTPublisher.java (at line 27):[-1,-1]
[ERROR] public class RSEZippedFolderPublisher extends RSEZippedJSTPublisher {
[ERROR] ^^^^^^^^^^^^^^^^^^^^^
[ERROR] RSEZippedJSTPublisher cannot be resolved to a type
[ERROR]
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.2_trunk.component--as/sources/plugins/org.jboss.ide.eclipse.as.rse.core/src/org/jboss/ide/eclipse/as/rse/core/archives/RSEZippedFolderPublisher.java (at line 27):[-1,-1]
[ERROR] public class RSEZippedFolderPublisher extends RSEZippedJSTPublisher {
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The type RSEZippedFolderPublisher is already defined
Broken since Feb 22, build #149:
http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.2...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months