[
https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin....
]
Aurélien Pupier commented on JBDS-4105:
---------------------------------------
[~chirino] Do we have already some maven goal/phase that can be used to produced the
Source to be deployed?
What is the time required to generate it? it is to know if we can imagine it on
Incremental build on on a full build only.
[~jeffmaury] [~rob.stryker] apart from the service/pod issue, how Eclipse OpenShift
Tooling knows which folder/files it needs to redeploy using the s2i binary way? (it is
using the s2i binary right?)
And by writing this question, i realize that we have the service/pod fix as requirements
so we might be forced to provide just an "ignore" m2e connector for this plugin
for the first release? the implication that I see is no leverage of the Eclipse OpenShift
Tooling:
- will require manual rebuild
- no hot-deploy
- what else?
Provide m2e connector for io.fabric8:fabric8-maven-plugin
---------------------------------------------------------
Key: JBDS-4105
URL:
https://issues.jboss.org/browse/JBDS-4105
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Feature Request
Components: maven
Reporter: Aurélien Pupier
iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e
connector to have a better integration.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)