[JBoss JIRA] Created: (JBIDE-7755) Portlet wizard allows creating portlets with same name
by Snjezana Peco (JIRA)
Portlet wizard allows creating portlets with same name
------------------------------------------------------
Key: JBIDE-7755
URL: https://jira.jboss.org/browse/JBIDE-7755
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Portal/GateIn
Affects Versions: 3.2.0.Beta1
Reporter: Snjezana Peco
Assignee: Snjezana Peco
Steps to reproduce:
- create a Dynamic Web project with the JBoss Portlet Core facet
- create a Java Portlet with the Test name (page 3 of the New Java Portlet wizard)
- create another project with the same name
The wizard will allow creating portlets with the same name. The created portlet.xml file will contain an error. The problem can also be reproduced when creating JSF/Seam portlet.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBDS-1268) Request: Complete Automated Install using XML
by Will Dinyes (JIRA)
Request: Complete Automated Install using XML
---------------------------------------------
Key: JBDS-1268
URL: https://jira.jboss.org/browse/JBDS-1268
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: installer
Affects Versions: 3.0.0.GA
Environment: Java 1.6 (Sun), RHEL 5.5
Reporter: Will Dinyes
Currently, the install process outputs an InstallConfigRecord.xml file, which for a general IzPack install, would contain all the information needed to repeat the install in exactly the same way, but without prompts.
However, the output file does not currently contain all the required info. The only sections included are the install path, and JBDS short cut panel. When using this file to perform an automated install via:
java -jar jbdevstudio-3.0.0.GA.jar InstallConfigRecord.xml
The install goes to the right directory, but the short cut does not appear to be created.
It would be great if this file could be used to automate an installation. In my particular case, the reason is that we will have instructors and students doing weekly installs of the software, and if we could streamline that process, it would free up more time for learning how to use the dev tools (which are great, by the way).
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-8128) [JBossTools Runtimes] Allow user to select what runtime types to be added
by Libor Zoubek (JIRA)
[JBossTools Runtimes] Allow user to select what runtime types to be added
--------------------------------------------------------------------------
Key: JBIDE-8128
URL: https://issues.jboss.org/browse/JBIDE-8128
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS, integration
Affects Versions: 3.2.0.CR1
Reporter: Libor Zoubek
Assignee: Rob Stryker
If user searches for a runtime(s) he adds folder wich contains typically EAP or SOA. But EAP or SOA contains several runtimes, which are added if user decides to add the runtime as whole. Runtimes that will be added are printed in description section.
User shlould have the right to decide what runtimes will be added. I suggest to display found runtime as tree with checkboxes.
For example SOA runtime should look like:
- /opt/soa-5.0
|- Server runtime 5.0
|- Drools 5.1
|- Seam 2.2
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[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
14 years, 11 months