[JBoss JIRA] (JBIDE-12631) merge Flow component into jBPM3 component in SVN?
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-12631:
----------------------------------
Summary: merge Flow component into jBPM3 component in SVN?
Key: JBIDE-12631
URL: https://issues.jboss.org/browse/JBIDE-12631
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.3.0.Final-SOA
Reporter: Nick Boldt
Assignee: Koen Aers
Fix For: 4.0.0.Alpha1-SOA
Koen:
Is there any reason to keep the Flow component separated from the jbpm3/4 component in SVN?
If we merge them we can build them in ONE step instead of TWO, saving time and resources.
Actually, is Flow even still needed? Or was that a sidetrack for jbpm4 only, and thus can be deprecated/removed?
My feeling is that we can purge everything in Flow and all the jbpm4 stuff from SVN, leaving only these IUs:
{code}
org.jbpm.gd.jpdl.feature
org.jboss.tools.jbpm3.feature
org.jboss.tools.jbpm3.test.feature
org.jboss.tools.jbpm.convert.feature
org.jboss.tools.jbpm.common.feature
org.jboss.tools.jbpm.common
org.jboss.tools.jbpm.convert
org.jbpm.gd.jpdl
org.jboss.tools.jbpm.common.test
org.jboss.tools.jbpm.convert.test
org.jbpm.gd.jpdl.test
org.jboss.tools.jbpm.ui.bot.test
{code}
Is that correct?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-12458) Removal of deltacloud from trunk
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-12458:
-----------------------------------
Summary: Removal of deltacloud from trunk
Key: JBIDE-12458
URL: https://issues.jboss.org/browse/JBIDE-12458
Project: Tools (JBoss Tools)
Issue Type: Task
Components: deltacloud
Affects Versions: 3.4.0.M1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.4.0.M1
Deltacloud is outdated and no longer belongs in trunk. I'm opening this jira to track it's removal. This topic is still open for discussion, but for now it leans heavily towards removal. Anyone with concerns are invited to express them here.
I would suggest that for removal to be approved, this jira needs a +1 from the component lead, a +1 from build, and a +1 from JBT lead, as well as no -1's from any JBoss Tools committers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] Created: (JBIDE-8062) Cannot properly edit value of <f:selectItem> tag via Visual Editor
by Vlado Pakan (JIRA)
Cannot properly edit value of <f:selectItem> tag via Visual Editor
------------------------------------------------------------------
Key: JBIDE-8062
URL: https://issues.jboss.org/browse/JBIDE-8062
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor Templates
Affects Versions: 3.2.0.CR1
Environment: Linux 32bit, JBDS 4.0.0.v201012161657N-H584-CR1
Reporter: Vlado Pakan
Assignee: Maxim Areshkau
When user wants to edit value of <f:selectItem> via Visual Editor he has to click on <f:selectItem> text tree times to select only item text not to select item text together with item button symbol. Whole item text gets selected. When user starts to type item text is deselected and first two characters of item text are replaced with typed characters. The rest of item text stays unchanged.
It works like this only for <f:selectItem> tag placed in <h:selectOneRadio> tag. It's not possible to edit <f:selectItem> value at all when it's placed in <h:selectManyCheckbox> tag.
When <f:selectItem> text is selected in Visual Editor cursor is put to this text and arrow keys are moving him but it's not possible to edit item text.
Test page is attached to this Jira: https://issues.jboss.org/browse/JBIDE-3860
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-12613) non-api uses of astools code need to be cleaned or made API
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-12613:
-----------------------------------
Summary: non-api uses of astools code need to be cleaned or made API
Key: JBIDE-12613
URL: https://issues.jboss.org/browse/JBIDE-12613
Project: Tools (JBoss Tools)
Issue Type: Task
Components: JBossAS/Servers
Affects Versions: 4.0.0.Alpha1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha2
The following are what I consider "bad uses" of astools code. Not all are the fault of the consuming component. Some may be the fault of inadequate API on the part of astools.
Either way, here's the list:
ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/AbstractJBossWSGenerationTest.java:import org.jboss.ide.eclipse.as.core.server.internal.JBossServer;
seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/Seam23FacetInstallDelegate.java:import org.jboss.ide.eclipse.as.core.modules.SingleDeployableFactory;
seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/ResourceDeployer.java:import org.jboss.ide.eclipse.as.core.modules.SingleDeployableFactory;
bpel/plugins/org.jboss.tools.bpel.runtimes/src/org/jboss/tools/bpel/runtimes/module/JBTBPELPublisher.java:import org.jboss.ide.eclipse.as.core.publishers.PublishUtil;
bpel/plugins/org.jboss.tools.bpel.runtimes/src/org/jboss/tools/bpel/runtimes/module/JBTBPELPublisher.java:import org.jboss.ide.eclipse.as.core.server.xpl.LocalCopyCallback;
bpel/plugins/org.jboss.tools.bpel.runtimes/src/org/jboss/tools/bpel/runtimes/module/JBTBPELPublisher.java:import org.jboss.ide.eclipse.as.core.server.xpl.PublishCopyUtil;
esb/tests/org.jboss.tools.esb.project.core.test/src/org/jboss/tools/esb/project/core/test/ESBProjectDeploymentTest.java:import org.jboss.ide.eclipse.as.core.server.internal.DeployableServer;
examples/plugins/org.jboss.tools.project.examples.cheatsheet/src/org/jboss/tools/project/examples/cheatsheet/actions/RunOnServer.java:import org.jboss.ide.eclipse.as.core.modules.SingleDeployableFactory;
maven/plugins/org.jboss.tools.maven.sourcelookup.ui/src/org/jboss/tools/maven/sourcelookup/ui/browsers/JBossSourceContainerDialog.java:import org.jboss.ide.eclipse.as.core.server.internal.JBossServer;
maven/plugins/org.jboss.tools.maven.sourcelookup.core/src/org/jboss/tools/maven/sourcelookup/containers/JBossSourceContainer.java:import org.jboss.ide.eclipse.as.core.server.bean.JBossServerType;
maven/plugins/org.jboss.tools.maven.sourcelookup.core/src/org/jboss/tools/maven/sourcelookup/containers/JBossSourceContainer.java:import org.jboss.ide.eclipse.as.core.server.bean.ServerBean;
maven/plugins/org.jboss.tools.maven.sourcelookup.core/src/org/jboss/tools/maven/sourcelookup/containers/JBossSourceContainer.java:import org.jboss.ide.eclipse.as.core.server.bean.ServerBeanLoader;
maven/plugins/org.jboss.tools.maven.sourcelookup.core/src/org/jboss/tools/maven/sourcelookup/containers/JBossSourceContainer.java:import org.jboss.ide.eclipse.as.core.server.internal.JBossServer;
Suggested fixes are as follows:
1) Make a JBossServer interface IJBossServer
2) Make serverbean official API
3) Make publish utils official API and try to separate htem from internal impl (difficult)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-12638) externalize strings
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-12638:
----------------------------------------
Summary: externalize strings
Key: JBIDE-12638
URL: https://issues.jboss.org/browse/JBIDE-12638
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.0.0.Alpha1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Minor
Fix For: 4.0.x
Messages and other texts are currently still embedded in the code. We should externalize them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months