[JBoss JIRA] (JBIDE-18508) EAR Maven project loses lib/ artifacts deployed to EAP broken after closing/reopening
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18508?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18508:
----------------------------------------
Labels: f2f2014 (was: )
> EAR Maven project loses lib/ artifacts deployed to EAP broken after closing/reopening
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18508
> URL: https://issues.jboss.org/browse/JBIDE-18508
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.1.2.Final
> Reporter: Marek Schmidt
> Assignee: Fred Bricon
> Labels: f2f2014
> Fix For: 4.3.0.Alpha1
>
> Attachments: seam-restbay-src.zip
>
>
> EAR Maven project loses lib/ artifacts deployed to EAP after closing/reopening
> 0. setup the redhat techpreview/all maven repository
> 1. Import the (attached) project as Maven project
> 2. Deploy the restbay-ear project to EAP 6.2 (or 6.3)
> 3. Close all 4 subprojects of the restbay project
> 4. reopen all the restbay projects
> 5. now the application will automatically redeploy
> 6. this redeployment will result in a failure.
> If you compare the deployment folders before/after the closing/reopening of the project, you will notice some of the restbay-ear.ear/lib/ libraries are missing.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18513) Servers still require access to remote runtime even when no runtime needed
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18513?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-18513:
---------------------------------------
It turns out the solution in JBIDE-17164 was not ideal.
I wasn't aware of it, but Max says FTP remote server worked fine for deployment in the past. So the solution to avoiding the NPE when starting it is not to hide such server but to disable the start/stop operation on such server (or have a special warning when user tries to start such a server).
> Servers still require access to remote runtime even when no runtime needed
> --------------------------------------------------------------------------
>
> Key: JBIDE-18513
> URL: https://issues.jboss.org/browse/JBIDE-18513
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Max Rydahl Andersen
>
> We removed the need for having access to local runtime when using a remote server but we still require additional access to the remote runtime (via ssh or similar) even though our server should be able to deploy to a server that is running in management mode + externally managed.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18419) CordovaSim can't handle cordova-3.6.3
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18419?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-18419.
-------------------------------
Verified with JBT 4.2.0.CR2-v20141005-0541-B267
> CordovaSim can't handle cordova-3.6.3
> -------------------------------------
>
> Key: JBIDE-18419
> URL: https://issues.jboss.org/browse/JBIDE-18419
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.CR1
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Priority: Blocker
> Fix For: 4.2.0.CR2
>
>
> No errors when running against *cordova-3.5.0*. However with *cordova-3.6.3* getting the error with the following stack trace:
> {code}
> 2014-09-23 13:40:23.731:INFO:oejs.Server:jetty-8.1.14.v20131031
> 2014-09-23 13:40:23.781:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:54262
> !JavaScript ERROR: TypeError: 'undefined' is not a function (evaluating 'exec.init()') on line 1483 for http://localhost:54243/cordova.js
> !JavaScript LOG: deviceready has not fired after 5 seconds.
> !JavaScript LOG: Channel not fired: onNativeReady
> !JavaScript LOG: Channel not fired: onPluginsReady
> !JavaScript LOG: Channel not fired: onCordovaReady
> {code}
> the upstream issue for apache ripple - https://issues.apache.org/jira/browse/RIPPLE-69
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18513) Servers still require access to remote runtime even when no runtime needed
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-18513:
-------------------------------------------
Summary: Servers still require access to remote runtime even when no runtime needed
Key: JBIDE-18513
URL: https://issues.jboss.org/browse/JBIDE-18513
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: server
Reporter: Max Rydahl Andersen
We removed the need for having access to local runtime when using a remote server but we still require additional access to the remote runtime (via ssh or similar) even though our server should be able to deploy to a server that is running in management mode + externally managed.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18508) EAR Maven project loses lib/ artifacts deployed to EAP broken after closing/reopening
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18508?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-18508:
-------------------------------------
It's just than I didn't plan on releasing anything for SR2. yet.
I haven't planned on making any breaking API changes so I reckon m2e 1.2.0 might be a good candidate for a fix release for SR2. We can discuss the matter on next F2F.
> EAR Maven project loses lib/ artifacts deployed to EAP broken after closing/reopening
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18508
> URL: https://issues.jboss.org/browse/JBIDE-18508
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.1.2.Final
> Reporter: Marek Schmidt
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha1
>
> Attachments: seam-restbay-src.zip
>
>
> EAR Maven project loses lib/ artifacts deployed to EAP after closing/reopening
> 0. setup the redhat techpreview/all maven repository
> 1. Import the (attached) project as Maven project
> 2. Deploy the restbay-ear project to EAP 6.2 (or 6.3)
> 3. Close all 4 subprojects of the restbay project
> 4. reopen all the restbay projects
> 5. now the application will automatically redeploy
> 6. this redeployment will result in a failure.
> If you compare the deployment folders before/after the closing/reopening of the project, you will notice some of the restbay-ear.ear/lib/ libraries are missing.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months