[
https://issues.jboss.org/browse/JBIDE-9085?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-9085:
------------------------------------
I thought we had discussed removing all sorts of UI elements that simply were cluttering
things. For example, we had discussed that for as7 we should remove pollers and just make
the default two work... or we should remove the JMX login and password situation since
that doesn't matter... or we should remove the custom deployment locations since it
was confusing to the user and as7 had a clean deployments folder, thus removing the
necessity of us having metadata or custom options.
So....... what we have here is a clear problem of the usecases not being clear, and of
conflicting specifications. If we are removing all these UI elements, they will result in
a loss of functionality for the user. If we NEED to KEEP all of the UI elements, then we
had absolutely no reason to duplicate all the classes and try a clean break, when the
use-cases are almost entirely the same.
AS7 does not allow users to set custom deploy folder
----------------------------------------------------
Key: JBIDE-9085
URL:
https://issues.jboss.org/browse/JBIDE-9085
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.M2
AS 7 has no option for controlling where deployment goes.
As long as Deploy Only server does not support AS7 marker files this is crucial to
have for deployments that does not live inside AS7 standard location (i.e. openshift
express)
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira