[JBoss JIRA] Created: (JBIDE-9135) AS RSE gives null pointer when using AS 7 local RSE
by Max Rydahl Andersen (JIRA)
AS RSE gives null pointer when using AS 7 local RSE
---------------------------------------------------
Key: JBIDE-9135
URL: https://issues.jboss.org/browse/JBIDE-9135
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M2
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
java.lang.NullPointerException
at org.eclipse.rse.internal.services.local.shells.LocalShellThread.init(LocalShellThread.java:188)
at org.eclipse.rse.internal.services.local.shells.LocalShellThread.<init>(LocalShellThread.java:95)
at org.eclipse.rse.internal.services.local.shells.LocalHostShell.<init>(LocalHostShell.java:39)
at org.eclipse.rse.internal.services.local.shells.LocalShellService.runCommand(LocalShellService.java:62)
at org.eclipse.rse.services.shells.AbstractShellService.runCommand(AbstractShellService.java:53)
at org.jboss.ide.eclipse.as.rse.core.RSEHostShellModel$ServerShellModel.createStartupShell(RSEHostShellModel.java:80)
at org.jboss.ide.eclipse.as.rse.core.RSELaunchDelegate.actualLaunch(RSELaunchDelegate.java:77)
at org.jboss.ide.eclipse.as.core.server.internal.launch.JBossServerStartupLaunchConfiguration.actualLaunch(JBossServerStartupLaunchConfiguration.java:113)
at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossLaunchConfigType.launch(AbstractJBossLaunchConfigType.java:77)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3404)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3342)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:363)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
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-5914) M2eclipse is registering bad menu or Seam component view has bad menu id
by Max Rydahl Andersen (JIRA)
M2eclipse is registering bad menu or Seam component view has bad menu id
------------------------------------------------------------------------
Key: JBIDE-5914
URL: https://jira.jboss.org/jira/browse/JBIDE-5914
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven, Seam
Affects Versions: 3.1.0.CR2
Reporter: Max Rydahl Andersen
Fix For: 3.1.1
What steps will reproduce the problem?
1. Open Seam components view
2. Right Click on project
3. Error log shows up with
"Plug-in 'org.maven.ide.eclipse.refactoring' contributed an invalid Menu Extension (Path: 'org.eclipse.jdt.ui.refactoring.menu' is invalid): org.maven.ide.eclipse.editor.RenameProjectAction"
Which is rather annoying.
I assume either is m2eclipse registreing their menu wrongly or our seam component view (common navigator) is doing something wrong since it works in Project Explorer.
-- Error Details --
Date: Tue Feb 23 19:00:35 CET 2010
Message: Plug-in 'org.maven.ide.eclipse.refactoring' contributed an invalid Menu Extension (Path: 'org.eclipse.jdt.ui.refactoring.menu' is invalid): org.maven.ide.eclipse.editor.RenameProjectAction
Severity: Error
Product: Eclipse 1.2.1.20090812-1036 (org.eclipse.epp.package.jee.product)
Plugin: org.eclipse.ui
Session Data:
eclipse.buildId=M20090917-0800
java.version=1.6.0_14
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=da_DK
Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product -data C:\Users\max\workspace-testy -product org.eclipse.epp.package.jee.product
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips
by Max Andersen (JIRA)
Add NOT_DROPINS + readme or similar into our updatesite zips
------------------------------------------------------------
Key: JBIDE-6985
URL: https://jira.jboss.org/browse/JBIDE-6985
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Affects Versions: 3.2.x
Reporter: Max Andersen
Assignee: Nick Boldt
Fix For: 3.2.x
Just an idea that occurred to that since updatesite zips and our old dropin compatible zips has same layout users keep trying to put them into dropins folder.
Could would add a "NOT_FOR_DROPINS" with text explaining this an updatesite and (or at least) a readme or instructions file outlining:
"This file is an Eclipse update zip to be used from within an Eclipse installations update manager.
Do *not* unzip this zip into Eclipse directly nor into its dropins folder - it will *not* work.
Use the Eclipse P2 Update Manager UI to perform the installation."
Just a thought after seeing multiple users asking why their installation does not work anymore.
--
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-9255) Duplicate java elements in CDI validation problem message
by Alexey Kazakov (JIRA)
Duplicate java elements in CDI validation problem message
---------------------------------------------------------
Key: JBIDE-9255
URL: https://issues.jboss.org/browse/JBIDE-9255
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.3.0.M3
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.0.M3
EXECUTE: Create any CDI project with Seam Solder module.
EXECUTE: Create a few types:
{code}
@Retention(RUNTIME)
@GenericType(MessageSystemConfiguration.class)
@interface ACMEQueue {
String name();
}
{code}
{code}
public class MyMessageQueues {
@Produces
@ACMEQueue("defaultQueue")
@Named("aaa")
MessageSystemConfiguration defaultQueue = new MessageSystemConfiguration(null);
@Produces
@Durable
@ACMEQueue("defaultQueue")
@Named("aaa")
MessageSystemConfiguration defaultQueue1 = new MessageSystemConfiguration(null);
}
{code}
{code}
@GenericConfiguration(ACMEQueue.class)
class MessageManager {
@Inject
@Generic
MessageQueue queue;
@Produces
@ApplyScope
MessageDispatcher messageDispatcherProducer() {
return queue.createMessageDispatcher();
}
@Produces
DispatcherPolicy getPolicy() {
return queue.getDispatcherPolicy();
}
}
{code}
{code}
@GenericConfiguration(ACMEQueue.class)
@ApplyScope
public class QueueManager implements Serializable {
@Produces
@ApplyScope
public MessageQueue messageQueueProducer() {
// return factory.createMessageQueue(config.name());
return null;
}
}
{code}
{code}
public interface MessageQueue {}
{code}
EXECUTE: Save the files.
ASSERT: Both @Named("aaa") marked as duplicate EL names: "A few beans (QueueManager.messageQueueProducer(), MyMessageQueues.defaultQueue1, MyMessageQueues.defaultQueue) have the same EL name and the name is not resolvable [JSR-299 §5.3.1]
FAILURE: Both @Named("aaa") marked as duplicate EL names: "A few beans (QueueManager.messageQueueProducer(), MyMessageQueues.defaultQueue1, MyMessageQueues.defaultQueue, QueueManager.messageQueueProducer()) have the same EL name and the name is not resolvable [JSR-299 §5.3.1] <-- QueueManager.messageQueueProducer() mentioned twice!
--
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-9266) Replace/Extend latestBuild.html with a latest symbolic link
by Max Rydahl Andersen (JIRA)
Replace/Extend latestBuild.html with a latest symbolic link
-----------------------------------------------------------
Key: JBIDE-9266
URL: https://issues.jboss.org/browse/JBIDE-9266
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
I see we have more and more latestBuild.html present all over and I'm suggestion we replace those with "latest" symbolic links instead.
Here is how to automate that on downloads.jboss.org at least:
echo -e "rm latest\nln 2011-06-27_10-25-32-H2980 latest" | sftp tools@filemgmt.jboss.org:/downloads_htdocs/tools/builds/nightly/trunk
The actual paths should of course be replaced with proper variable replacements.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months