[JBoss JIRA] Created: (JBDS-1008) Create Shortcuts fails on 64-bit Vista
by Burr Sutter (JIRA)
Create Shortcuts fails on 64-bit Vista
--------------------------------------
Key: JBDS-1008
URL: https://jira.jboss.org/jira/browse/JBDS-1008
Project: JBoss Developer Studio
Issue Type: Bug
Components: installer
Affects Versions: 3.0.0.CR1
Reporter: Burr Sutter
Attachments: Shortcuts.jpg
Click the Next button produces the following stack trace on the console. The workaround is to just hit Finish instead of next (screenshot provided)
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at com.izforge.izpack.panels.ShortcutPanel.isValidated(ShortcutPanel.jav
a:580)
at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFra
me.java:1453)
at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFra
me.java:1444)
at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionP
erformed(InstallerFrame.java:1529)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:19
95)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.jav
a:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel
.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242
)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonL
istener.java:236)
at java.awt.Component.processMouseEvent(Component.java:6216)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3265)
at java.awt.Component.processEvent(Component.java:5981)
at java.awt.Container.processEvent(Container.java:2041)
at java.awt.Component.dispatchEventImpl(Component.java:4583)
at java.awt.Container.dispatchEventImpl(Container.java:2099)
at java.awt.Component.dispatchEvent(Component.java:4413)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4556
)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4220)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4150)
at java.awt.Container.dispatchEventImpl(Container.java:2085)
at java.awt.Window.dispatchEventImpl(Window.java:2475)
at java.awt.Component.dispatchEvent(Component.java:4413)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThre
ad.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.
java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre
ad.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-1965) display links from tiles definitions on stuts diagram (like from jsp pages)
by Alex Titov (JIRA)
display links from tiles definitions on stuts diagram (like from jsp pages)
---------------------------------------------------------------------------
Key: JBIDE-1965
URL: http://jira.jboss.com/jira/browse/JBIDE-1965
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: struts/shale
Affects Versions: 2.0.1
Reporter: Alex Titov
Priority: Minor
Stuts plugin can display links from jsp page to actions and other jsp pages on diagram. That is grate! But if you use tiles plugin you don't work with jsp pages directly. Instead you work with tiles definition. For example
<definition name="..." path="/WEB-INF/jsp/template.jsp">
<put name="content" value="/WEB-INF/graph.jsp"></put>
</definition>
Both template.jsp and graph.jsp are jsp pages and have links but struts plugin does not understand this. So links from these pages are not displayed in struts diagram.
Also it would be nice if there were way to select jsp page for "value" attribute in "put" element in tiles editor (like for "path" attribute in "definition" element).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-4601) JBoss Profiler throws NPE when Profile > Profile Configurations... dialog is launched for a Main class
by Nick Boldt (JIRA)
JBoss Profiler throws NPE when Profile > Profile Configurations... dialog is launched for a Main class
------------------------------------------------------------------------------------------------------
Key: JBIDE-4601
URL: https://jira.jboss.org/jira/browse/JBIDE-4601
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M2
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Steps to repro:
a) install Eclipse 3.5
b) install JBoss Profiler feature from update site http://download.jboss.org/jbosstools/updates/nightly/3.1.0.M2/
c) restart Eclipse
d) create a Java project, eg., foobar
e) create a Main class in that project, eg., foo.bar.Main
f) put this in Main.java:
package foo.bar;
public class Main {
/**
* @param args
*/
public static void main(String[] args) {
System.out.println("Hello, Foo!");
}
}
f) debug the class: right-click in the file and Debug As > Java Application
g) add a breakpoint on the println() line
h) debug again, this time switching to the Debug perspective when prompted
i) right-click in class file, Debug As > Debug Configurations...
j) note the new JBoss Profiler tab for your Java Application > Main launch configuration. Close the dialog.
k) right-click in class file, Profile As > Profile Configurations...
l) note three error dialogs.
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
by Sean Flanigan (JIRA)
Externalise English strings (move them from source code into .properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Much of the English text in JBoss Tools is already externalised into .properties files, but my pseudolocalisation testing [1] shows that there is still some hard-coded English text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java source.
Any such English text needs to be moved out of the source code into .properties files, and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings" wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating another one for each package in the bundle. (More bundles create more work for translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-4044) Review unused strings from Messages classes as reported by UCDetector
by Sean Flanigan (JIRA)
Review unused strings from Messages classes as reported by UCDetector
---------------------------------------------------------------------
Key: JBIDE-4044
URL: https://jira.jboss.org/jira/browse/JBIDE-4044
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Cleanup
Affects Versions: 3.1.0
Reporter: Sean Flanigan
I've run UCDetector [1] against the codebase, and it has found 294
fields in *Messages classes which have 0 references. I've attached a
list (views well in oocalc). I'd like to remove them, along with their
corresponding resourcebundle properties, to reduce the number of
translatable strings before localisation begins.
I think it should be safe to remove these fields, since any direct usage will be caught by the compiler as soon as we try to remove it (and wouldn't have been listed by UCDetector anyway, unless it is completely broken), and it would be extremely unlikely for anyone to access a Messages field by reflection.
If you want to run UCDetector yourself, select one or more plugin projects (not features, not non-Java projects), select UCDetector/Detect unnecessary code, and wait. I recommend configuring Eclipse's Problems view to show problems of type "UCDetector Marker (References)" whose description contains 'Field "'. The relevant problems are of the form 'Field SomethingMessages.SOME_KEY" has 0 references'.
[1] http://ucdetector.sourceforge.net/
--
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, 10 months
[JBoss JIRA] Created: (JBDS-706) Add option to create a JBoss Portal project
by Joao Paulo Viragine (JIRA)
Add option to create a JBoss Portal project
-------------------------------------------
Key: JBDS-706
URL: https://jira.jboss.org/jira/browse/JBDS-706
Project: Developer Studio
Issue Type: Feature Request
Environment: JBDS 2.0.0.GA
Reporter: Joao Paulo Viragine
It would be nice if we could create a portal in JBoss Portal directly from JBDS/Tools.
We could have an option named: 'Create JBoss Portal Project', which included facets like JBoss Portlet and Seam (among others)
and created: portlet.xml, portlet-instances.xml and default-object.xml.
This option could prompt for a portal name, so we don't need to even define/create the portal in JBoss Portal Admin console. Everything would be done directly from JBDS/Tools.
Note that option would be slight different from an existing 'JBoss JSF/Seam Portlet' option that doesn't create a portal, only a portal page in an existing portal.
--
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, 10 months
[jbosside-issues] [JBoss JIRA] Created: (JBIDE-428) Add new features to Feemarker Plugin
by ZERR Angelo (JIRA)
Add new features to Feemarker Plugin
------------------------------------
Key: JBIDE-428
URL: http://jira.jboss.com/jira/browse/JBIDE-428
Project: JBoss IDE
Issue Type: Patch
Components: FreeMarker plugin
Reporter: ZERR Angelo
Assigned To: Joe Hudson
Attachments: FreemarkerIDE.zip
I have updated Freemarker Plugin to :
1) have template completion capability : (ex : type list in your ftl template, and CRTL+SPACE => <#list ....><#list> will be generate.
You can customize your template with menu Window/Preferences/Freemarker Editor/Templates
2) add XML context capabilty. You can choose XML file and have completion with element and attribute of your XML.
3) add String context. I beleive it will be better to have Java Type context (Boolea, String,...)
3) add Preview Tab to see the result of the merge of your template and your model. It works ONLY with XML context. It's not available dor Class context.
To use Preview Tab with Class, I believe it will good to have a class wich return getter of your Class.
Ex : if you have class MyForm, user will have to add getMyForm in the context class for the preview.
MyForm getMyForm() {
MyForm form = new MyForm
form.setId("MyId")
return form;
}
If user have the ftl template ${myForm.id}, when you click to th epreview tab, you will have MyId displayed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-1388) support remote hosts/external started AS adapter
by Max Andersen (JIRA)
support remote hosts/external started AS adapter
------------------------------------------------
Key: JBIDE-1388
URL: http://jira.jboss.com/jira/browse/JBIDE-1388
Project: JBoss Tools
Issue Type: Feature Request
Components: JBossAS
Reporter: Max Andersen
Fix For: 2.1
people like to start there server manually and just hook up to it via remote debugging - we should make that easy (its trivial via eclipse support for remote debugging)
should be an option on the servers, doesnt require new server/runtime type if local server.
Only catch is that the server might not even be accessible via filesystem - how should we handle deploy and runtime lib situation ? (my best bet is just that these would be unspecified and not provide those features)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 12 months
[JBoss JIRA] Created: (JBDS-1016) Usability issue with Seam Web Project Wizard
by Joshua Wulf (JIRA)
Usability issue with Seam Web Project Wizard
--------------------------------------------
Key: JBDS-1016
URL: https://jira.jboss.org/jira/browse/JBDS-1016
Project: JBoss Developer Studio
Issue Type: Bug
Affects Versions: 3.0.0.M4
Environment: Mac OS X 10.4.11 32 bit PPC
Reporter: Joshua Wulf
The Seam Web Project Wizard changes the Configuration when the Target runtime is changed. Although it starts out with "Dynamic Web Application for Seam 2.0" selected by default, if the Target runtime is changed the Configuration selection is changed to match the Target Runtime. This results in an error "Seam facet must be enabled."
Changing the Target Runtime back to the original one does not remove the error. There are two ways to remove the error message. One is to manually change the Configuration back to "Dynamic Web Application for Seam 2.x". Since it is not possible to move forward from this page without enabling the Seam facet, the configuration should not automatically change to one that does not have Seam facet enabled.
The situation is more complicated, and worse, however, because the other way to remove the error message is to manually modify the Configuration using the "Modify" button. If the user does this, and enables JavaServer Faces and Seam, the error message will disappear and they will be able to move forward.
However, when it comes time to select the Seam runtime the user will run into a problem. In the Modify Configuration screen where the user enabled the Seam facet, the unique option there was fixed at version 2.2. If the Seam runtime the user wishes to use is not 2.2 then they will get an error that the Seam runtime is an incompatible version. They will be unable to select any other version in the version drop-down box.
So there are three problems:
1. The Configuration changes automatically to one incompatible with a Seam Web Project if the Target runtime is changed.
2 . Although a user may try to clear the resultant error message by changing the runtime back to the original one, the error message will remain, as the dialog will change the configuration to another incompatible one. If the user did not notice the original default configuration (which they may well not if they are moving from top to the bottom of the wizard, which will be the usual case), they have no way of knowing how to clear the error message.
3. If the user clicks on the tempting "Modify" button and manually enables Seam they can run into a problem several screens later (error message saying Seam version is incompatible and only 2.2 in the version drop-down box) with no obvious way to resolve it.
The workaround is to document this quirk, but that defeats the purpose of an intuitive in-IDE wizard that guides you through setting up the project.
I would recommend making the configuration stay on the default, even when the Target runtime is changed. If the user sees an incompatible version of Seam there when they scan down, they are likely to click it to see if a compatible version of Seam is there. If they see "Default configuration for X runtime" with a description saying "A good starting point... Additional facets can later be installed to add new functionality to the project" and an error message saying "Seam facet must be enabled", then their likely response will be to modify the configuration to "add new functionality" to the "good starting point" that the wizard has selected for them.
--
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, 12 months
[JBoss JIRA] Created: (JBIDE-5535) New Web Service
by Burr Sutter (JIRA)
New Web Service
---------------
Key: JBIDE-5535
URL: https://jira.jboss.org/jira/browse/JBIDE-5535
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Burr Sutter
Attachments: New_WebService_Wizard.jpg, New_Wizard.jpg
There should be a New Web Service Project wizard (the same as New Dynamic Web Project) and a New Web Service component wizard.
The New Web Service Project wizard creates the exact same thing as New Dynamic Web Project but with HelloWorldWS.java containing the following:
package com.jboss.lab;
import javax.jws.WebMethod;
import javax.jws.WebService;
@WebService
public class MyWebService {
@WebMethod
public String sayHello(String name) {
return "Hello2 " + name + "!";
}
}
And the appropriate entries in the web.xml.
<servlet>
<servlet-name>MyWebServiceServlet</servlet-name>
<servlet-class>com.jboss.lab.MyWebService</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>MyWebServiceServlet</servlet-name>
<url-pattern>/MyWebService</url-pattern>
</servlet-mapping>
See screenshots for current functionality.
This suggestion is based on how Visual Studio handles this scenario. For a New Web Service or New Web Service project, it drops in the annotated mywebservice.asmx automatically. You can deploy the project/component immediately without further editing.
--
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
15 years
[JBoss JIRA] Created: (JBIDE-1608) Hibernate Configuration view should display all database
by Vitali Yemialyanchyk (JIRA)
Hibernate Configuration view should display all database
---------------------------------------------------------
Key: JBIDE-1608
URL: http://jira.jboss.com/jira/browse/JBIDE-1608
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Vitali Yemialyanchyk
Assigned To: Vitali Yemialyanchyk
Priority: Minor
Fix For: LATER
Look at the attached file hibernate.cfg.xml - if <property name="hibernate.connection.url">jdbc:mysql://localhost:3306/mysql</property>
Hibernate Configuration view -> ... -> Database display correctly mysql database - but if
<property name="hibernate.connection.url">jdbc:mysql://localhost:3306</property>
look like this
Hibernate Configuration view -> ... -> Database display nothing and the user can't understand what is wrong - I provide 2 screenshots
the same if
<property name="hibernate.connection.url">jdbc:mysql://localhost:3306/mysql1</property>
mysql1 - there is no such DB
as I think in first case Hibernate Configuration should display all mysql DBs and in the second case the user should get message -
something like "Can't find shuch DB"
Other thing - then I press right mouse button on Hibernate Configuration view -> ... -> Database - I expect to get possibility to configure
DB URL and may be some other properties - the best thing here if I'll get some dialog - or at least possibility to open hibernate.cfg.xml for edit.
For this I'll create other new issue...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBIDE-4082) Can't change starting state node from graphical editor
by Hedley Proctor (JIRA)
Can't change starting state node from graphical editor
------------------------------------------------------
Key: JBIDE-4082
URL: https://jira.jboss.org/jira/browse/JBIDE-4082
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0
Environment: Windows xp
Eclipse 3.3.2, build M20080221-1800
JBoss jBPM Eclipse plugin v3.1.3 SP2
Reporter: Hedley Proctor
Fix For: 3.1.0
It doesn't seem possible to change the a starting state node to a normal state node, or vice versa. e.g. if you have a starting state with transitions to a number of states, but you want to insert a new starting state before it and convert the present node to a normal "State" node, it looks like you have to
- delete your current starting state node
- create a new state node with the same name, transitions, actions etc
- add your new starting state node
Since state and starting states are very similar, perhaps we could have an option to convert a starting state node to a normal state? e.g. in the properties tab at the bottom perhaps? Then you could just click this button or change the option to convert the node type, without any deleting and recreating.
--
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
15 years, 1 month
[JBoss JIRA] Created: (JBIDE-4039) Drools Runtime version checks during Drools project creation.
by Aliaksey Nis (JIRA)
Drools Runtime version checks during Drools project creation.
-------------------------------------------------------------
Key: JBIDE-4039
URL: https://jira.jboss.org/jira/browse/JBIDE-4039
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Affects Versions: 3.0.0.GA
Environment: WindowsXP SP2
JBoss Developer Studio
Version: 2.0.0.GA
Build id: jbdevstudio-eap-win32-2.0.0.GA-R200903141247-H4
JRE 1.5_08
Reporter: Aliaksey Nis
Attachments: DroolsExc1.txt, DroolsExc2.txt
EXECUTE: Install studio, during installation add jboss-soa-p.4.3.0 server.
ASSERT: Studio created drools runtime - Drools - jboss-soa-p.4.3.0.
EXECUTE: New project > Drools Project.
EXECUTE: Input name, press Next 2 times.
FAILURE: In step 3 enabled default checkbox with "Drools - jboss-soa-p.4.3.0" runtime(4.x drools runtime). And selected code compatibility with drools 5.x. No sights of warning about wrong Drools version.
EXECUTE: Press Finish.
ASSERT: Project created with error multiply markers(because wrong drools runtime used).
EXECUTE: Go to Preferences > Drools > Drools Runtimes. Create new Drools 5.x runtime.
EXECUTE: Right click on Drools project. Select Properties > Drools.
EXECUTE: Enable Settings checkbox, select Drools 5.x runtime. Press Ok.
FAILURE: Exception thrown in error log(DroolsExc1.txt).
EXECUTE: Right click on Drools project. Select Properties > Drools.
EXECUTE: Disable Settings checkbox. Press Ok.
FAILURE: Each time you press Ok button - exception thrown in error log(DroolsExc21.txt). It's imposible to disable Project specific settings now.
--
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
15 years, 2 months
[JBoss JIRA] Created: (JBDS-894) Drools Gudided Editor creates incorrect XML for BRMS Manager to consume
by Graham Gear (JIRA)
Drools Gudided Editor creates incorrect XML for BRMS Manager to consume
-----------------------------------------------------------------------
Key: JBDS-894
URL: https://jira.jboss.org/jira/browse/JBDS-894
Project: JBoss Developer Studio
Issue Type: Bug
Affects Versions: 2.1.0
Environment: BRMS Manager 5.0.1
Reporter: Graham Gear
Priority: Minor
When rules created with the Dev Studio 2.1 Drools Guided Editor are uploaded to the BRMS Manager 5.0.1, literal values are not displayed correctly. BRL authored from Dev Studio has a feild nature of 0, where as BRMS authored BRL has a nature 1. Eg
Dev Studio Drools Guided Editor BRL:
<rhs>
<setField>
<fieldValues>
<fieldValue>
<field>review</field>
<value>Rule 6764: Review: Large Monthly Income</value>
<nature>0</nature>
<type>String</type>
</fieldValue>
</fieldValues>
<variable>applicationResult</variable>
</setField>
</rhs>
BRMS Manager Guided Editor BRL:
<rhs>
<setField>
<fieldValues>
<fieldValue>
<field>review</field>
<value>Rule 6764: Review: Large Monthly Income</value>
<nature>1</nature>
<type>String</type>
</fieldValue>
</fieldValues>
<variable>applicationResult</variable>
</setField>
</rhs>
If this is manually changed to 1 and uploaded to the BRMS Manager it all seems to work.
Previous versions of the Drools Plugin under Dev Studio 2.0 did not generated the nature tag at all and worked with BRMS Manager 5.0.0.
I have not tested interopability of Dev Studio 2.1 and BRMS Manager 5.0.0
--
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
15 years, 2 months