[JBoss JIRA] (JBIDE-14549) Deploying archive via drag&drop triggers server start
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14549?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-14549.
------------------------------------
verified in JBDS 7.1.0 Alpha2-v20131002-0939-B431
> Deploying archive via drag&drop triggers server start
> -----------------------------------------------------
>
> Key: JBIDE-14549
> URL: https://issues.jboss.org/browse/JBIDE-14549
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: archives, upstream
> Affects Versions: 4.1.0.Beta1
> Reporter: Jaroslav Jankovič
> Assignee: Rob Stryker
> Fix For: 4.1.1.Alpha2
>
>
> If archive is deployed with Publish dialog, server is (correctly) not started. However, drag&drop archive under server in servers view cause server starting.
> STEP: create a simple java project
> STEP: create an archive in it (via explorer/view)
> STEP: in Project Explorer view, expand Project Archives explorer, select the created archive and drag & drop into server in server's view
> ASSERT: archive is deployed on the server
> FAIL: server start is initiated but I think it should be not, because archive deploy via Publish Archive dialog doesn't trigger server's start
> There is another bug. When user wants to drag&drop whole project into the server, server's starting process is also initiated, but should be not.
> STEP: create a simple java project
> STEP: open Project Explorer view and drag & drop the project into a server
> ASSERT: project is deployed
> ASSERT: server is not started
> STEP: undeploy the project from a server
> STEP: create an archive in the project
> STEP: drag & drop the project into a server
> ASSERT: project is deployed
> FAIL: server's start is triggered
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15398) CDI Builder is sloooow
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-15398.
------------------------------------
verified in JBDS 7.1.0 Alpha2-v20131002-0939-B431
> CDI Builder is sloooow
> ----------------------
>
> Key: JBIDE-15398
> URL: https://issues.jboss.org/browse/JBIDE-15398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.0.Final
> Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
> Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png, MemoryUsedWithNewMaven.png, MemoryUsedWithNewMavenAfterBuild.png
>
>
> After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator.
> 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar.
> If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the bulk of JBT), import+build complete in ~12/13 min
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15665) Wrong output directory in new Tomcat 7 applications
by Jorge Yagüe París (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15665?page=com.atlassian.jira.plugi... ]
Jorge Yagüe París updated JBIDE-15665:
--------------------------------------
Description:
I created a new Tomcat 7 Openshift application with the new project wizard, using an existing Maven project. The wizard adds the Openshift profile in pom.xml but outputDirectory is set as *deployments* instead of *webapps*, so when the application is pushed to the server it doesn't work.
Changing deployments to webapps in the Maven plugin makes it work.
was:
I created a new Tomcat 7 Openshift application with the new project wizard, using an existing Maven project. The wizard adds the Openshift profile in pom.xml but outputDirectory is set as *deployments* instead of *webapps*, so when the application is pushed to the server it doesn't work.
Changing deployments for webapps in the Maven plugin makes it work.
> Wrong output directory in new Tomcat 7 applications
> ---------------------------------------------------
>
> Key: JBIDE-15665
> URL: https://issues.jboss.org/browse/JBIDE-15665
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.1.Final
> Environment: Eclipse Kepler, Mac OS X 10.8.4
> Reporter: Jorge Yagüe París
> Priority: Minor
> Labels: maven, tomcat7
>
> I created a new Tomcat 7 Openshift application with the new project wizard, using an existing Maven project. The wizard adds the Openshift profile in pom.xml but outputDirectory is set as *deployments* instead of *webapps*, so when the application is pushed to the server it doesn't work.
> Changing deployments to webapps in the Maven plugin makes it work.
--
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
12 years, 6 months
[JBoss JIRA] (JBTIS-188) remove drools JBTIS TP dependencies added for Fuse
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-188:
--------------------------------
Summary: remove drools JBTIS TP dependencies added for Fuse
Key: JBTIS-188
URL: https://issues.jboss.org/browse/JBTIS-188
Project: JBoss Tools Integration Stack
Issue Type: Task
Security Level: Public (Everyone can see)
Components: target-platform
Affects Versions: 4.1.3
Reporter: Paul Leacu
Assignee: Paul Leacu
Drools components were added to the JBTIS TP for Fuse. SInce Drools components change frequently - these dependecnies should be moved back to the Fuse TP which is already separate.
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15665) Wrong output directory in new Tomcat 7 applications
by Jorge Yagüe París (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15665?page=com.atlassian.jira.plugi... ]
Jorge Yagüe París updated JBIDE-15665:
--------------------------------------
Environment: Eclipse Kepler, Mac OS X 10.8.4 (was: Eclipse, Mac OS X 10.8.4)
> Wrong output directory in new Tomcat 7 applications
> ---------------------------------------------------
>
> Key: JBIDE-15665
> URL: https://issues.jboss.org/browse/JBIDE-15665
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.1.Final
> Environment: Eclipse Kepler, Mac OS X 10.8.4
> Reporter: Jorge Yagüe París
> Priority: Minor
> Labels: maven, tomcat7
>
> I created a new Tomcat 7 Openshift application with the new project wizard, using an existing Maven project. The wizard adds the Openshift profile in pom.xml but outputDirectory is set as *deployments* instead of *webapps*, so when the application is pushed to the server it doesn't work.
> Changing deployments for webapps in the Maven plugin makes it work.
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15665) Wrong output directory in new Tomcat 7 applications
by Jorge Yagüe París (JIRA)
Jorge Yagüe París created JBIDE-15665:
-----------------------------------------
Summary: Wrong output directory in new Tomcat 7 applications
Key: JBIDE-15665
URL: https://issues.jboss.org/browse/JBIDE-15665
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.1.Final
Environment: Eclipse, Mac OS X 10.8.4
Reporter: Jorge Yagüe París
Priority: Minor
I created a new Tomcat 7 Openshift application with the new project wizard, using an existing Maven project. The wizard adds the Openshift profile in pom.xml but outputDirectory is set as *deployments* instead of *webapps*, so when the application is pushed to the server it doesn't work.
Changing deployments for webapps in the Maven plugin makes it work.
--
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
12 years, 6 months