[JBoss JIRA] (JBIDE-16628) Wildfly server adapter is labeled experimental
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-16628:
----------------------------------
Summary: Wildfly server adapter is labeled experimental
Key: JBIDE-16628
URL: https://issues.jboss.org/browse/JBIDE-16628
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Alpha2
Reporter: Pavol Srna
Fix For: 4.2.0.Beta1
Attachments: wildfly-label.png
Released version of Wildfly is 8.0.0.Final and I assume we should change the server adapter label and remove the "(Experimental)" string.
--
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, 2 months
[JBoss JIRA] (JBIDE-16574) File->Maven->Checkout Maven Project from SCM - results in error unless scm URL has "scm:null:" prefix
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16574?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16574:
---------------------------------------------
I tried this "checkout maven project from scm" and yeah its rather crappy.
There are no options in the combo thus you have no good idea what it is about.
When I click "find more connectors" it shows everything not just scm AND when typing in git nothing shows up. I have to type "egit' to get the installer and then you get this error:
Operation details
Cannot complete the install because one or more required items could not be found.
Software being installed: Maven SCM Handler for EGit 0.14.0.201207041402 (org.sonatype.m2e.egit.feature.feature.group 0.14.0.201207041402)
Missing requirement: Maven SCM Handler for EGit 0.14.0.201207041402 (org.sonatype.m2e.egit 0.14.0.201207041402) requires 'bundle org.eclipse.egit.core [1.0.0,3.0.0)' but it could not be found
Cannot satisfy dependency:
From: Maven SCM Handler for EGit 0.14.0.201207041402 (org.sonatype.m2e.egit.feature.feature.group 0.14.0.201207041402)
To: org.sonatype.m2e.egit [0.14.0.201207041402]
So yeah, this situation should get fixed.
> File->Maven->Checkout Maven Project from SCM - results in error unless scm URL has "scm:null:" prefix
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16574
> URL: https://issues.jboss.org/browse/JBIDE-16574
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.Alpha2
> Environment: RHEL6
> OpenJDK 1.7
> JBT 4.2.0.alpha2.respin-a
> Reporter: Len DiMaggio
> Fix For: 4.2.0.Beta1
>
> Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot-3.png, Screenshot.png
>
>
> See attached screenshots - if a user attempts to import TicketMonster with this URL:
> git://github.com/jboss-jdf/ticket-monster.git
> This error is raised: "Select SCM type and URL"
> Using this URL clears the error condition:
> scm:null:git://github.com/jboss-jdf/ticket-monster.git
--
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, 2 months
[JBoss JIRA] (JBDS-2851) Team Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2851:
-------------------------------------------
Please be aware of JBIDE-13703 which discuss most of this from dev perspective and have related Eclipse platform issues linked in.
> Team Usability
> --------------
>
> Key: JBDS-2851
> URL: https://issues.jboss.org/browse/JBDS-2851
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Priority: Critical
> Labels: QE_JBDS80_needinfo
>
> It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as
> - how to integrate with CVS, SVN, Git
> - how to "import" a Maven-based project from SCM
> "Check out Maven Projects from SCM" has misfired for some users
> - how to "checkin" changes back to the SCM
> To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things.
> For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically.
--
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, 2 months
[JBoss JIRA] (JBIDE-16620) [Check] Unable to deploy Richfaces project example
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16620?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-16620.
---------------------------------
Resolution: Cannot Reproduce Bug
Not replicatable
> [Check] Unable to deploy Richfaces project example
> --------------------------------------------------
>
> Key: JBIDE-16620
> URL: https://issues.jboss.org/browse/JBIDE-16620
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Alpha2
> Environment: JBT 4.2.0.Alpha2 installed on top of Eclipse Luna M5.
> Fedora 18, OpenJDK 1.7.0 64b
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.1.2.CR1
>
>
> I'm unable to deploy Richfaces project created from Central using standard Run as->Run on server.
> I've tried to deploy it to JBoss AS 7.1.1 and EAP 6.2, both with no success.
> {noformat:title=Server console output}
> 5:10:45,978 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
> 15:10:46,202 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
> 15:10:46,251 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
> 15:10:47,043 INFO [org.xnio] XNIO Version 3.0.3.GA
> 15:10:47,045 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
> 15:10:47,053 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
> 15:10:47,060 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
> 15:10:47,076 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
> 15:10:47,079 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
> 15:10:47,090 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
> 15:10:47,143 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
> 15:10:47,147 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
> 15:10:47,165 INFO [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
> 15:10:47,171 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
> 15:10:47,176 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 15:10:47,193 INFO [org.jboss.as.security] (MSC service thread 1-8) JBAS013100: Current PicketBox version=4.0.7.Final
> 15:10:47,217 INFO [org.jboss.as.naming] (MSC service thread 1-6) JBAS011802: Starting Naming Service
> 15:10:47,225 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
> 15:10:47,233 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default]
> 15:10:47,397 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-5) JBoss Web Services - Stack CXF Server 4.0.2.GA
> 15:10:47,451 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
> 15:10:47,806 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 15:10:47,871 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost/127.0.0.1:4447
> 15:10:47,871 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:9999
> 15:10:47,879 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory /home/rax/Runtimes/jboss-as-7.1.1.Final/standalone/deployments
> 15:10:47,888 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jboss-as-kitchensink-rf.war in deployment directory. To trigger deployment create a file called jboss-as-kitchensink-rf.war.dodeploy
> 15:10:47,993 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "jboss-as-kitchensink-rf.war"
> 15:10:48,907 INFO [org.jboss.as.jpa] (MSC service thread 1-4) JBAS011401: Read persistence.xml for primary
> 15:10:49,278 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment jboss-as-kitchensink-rf.war
> 15:10:49,285 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named MemberRegistration in deployment unit deployment "jboss-as-kitchensink-rf.war" are as follows:
> java:global/jboss-as-kitchensink-rf/MemberRegistration!org.jboss.tools.example.richfaces.service.MemberRegistration
> java:app/jboss-as-kitchensink-rf/MemberRegistration!org.jboss.tools.example.richfaces.service.MemberRegistration
> java:module/MemberRegistration!org.jboss.tools.example.richfaces.service.MemberRegistration
> java:global/jboss-as-kitchensink-rf/MemberRegistration
> java:app/jboss-as-kitchensink-rf/MemberRegistration
> java:module/MemberRegistration
> 15:10:49,439 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: jboss-as-kitchensink-rf.war
> 15:10:49,464 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900 1.1.5 (AS71)
> 15:10:49,508 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [jboss/datasources/KitchensinkrfQuickstartDS]
> 15:10:49,509 INFO [org.jboss.as.jpa] (MSC service thread 1-6) JBAS011402: Starting Persistence Unit Service 'jboss-as-kitchensink-rf.war#primary'
> 15:10:49,589 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-6) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
> 15:10:49,593 INFO [org.hibernate.Version] (MSC service thread 1-6) HHH000412: Hibernate Core {4.0.1.Final}
> 15:10:49,595 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-6) HHH000206: hibernate.properties not found
> 15:10:49,598 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-6) HHH000021: Bytecode provider name : javassist
> 15:10:49,612 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-6) HHH000204: Processing PersistenceUnitInfo [
> name: primary
> ...]
> 15:10:49,619 WARN [org.jboss.modules] (MSC service thread 1-6) Failed to define class org.jboss.tools.example.richfaces.util.RewriteConfigurationProvider in Module "deployment.jboss-as-kitchensink-rf.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link org/jboss/tools/example/richfaces/util/RewriteConfigurationProvider (Module "deployment.jboss-as-kitchensink-rf.war:main" from Service Module Loader)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:396)
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:243)
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:73)
> at org.jboss.modules.Module.loadModuleClass(Module.java:517)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
> at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:171)
> at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:489) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
> at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:851) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
> at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:596) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
> at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: java.lang.NoClassDefFoundError: org/ocpsoft/rewrite/servlet/config/HttpConfigurationProvider
> at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.7.0_45]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:800) [rt.jar:1.7.0_45]
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) [rt.jar:1.7.0_45]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:327)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:391)
> ... 20 more
> Caused by: java.lang.ClassNotFoundException: org.ocpsoft.rewrite.servlet.config.HttpConfigurationProvider from [Module "deployment.jboss-as-kitchensink-rf.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
> ... 25 more
> 15:10:49,629 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.persistenceunit."jboss-as-kitchensink-rf.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-as-kitchensink-rf.war#primary": Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: java.lang.RuntimeException: error trying to scan <jar-file>: vfs:/home/rax/Runtimes/jboss-as-7.1.1.Final/standalone/deployments/jboss-as-kitchensink-rf.war/WEB-INF/classes/
> at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:854)
> at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:596)
> at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> ... 3 more
> Caused by: java.lang.RuntimeException: JBAS011431: Could not load entity class 'org.jboss.tools.example.richfaces.util.RewriteConfigurationProvider' with PersistenceUnitInfo.getClassLoader()
> at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:175)
> at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:489)
> at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:851)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.tools.example.richfaces.util.RewriteConfigurationProvider from [Module "deployment.jboss-as-kitchensink-rf.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
> at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:171)
> ... 11 more
> 15:10:49,640 INFO [org.jboss.as] (MSC service thread 1-8) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 15:10:49,641 ERROR [org.jboss.as] (MSC service thread 1-8) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 4039ms - Started 185 of 291 services (29 services failed or missing dependencies, 76 services are passive or on-demand)
> 15:10:49,842 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jboss-as-kitchensink-rf.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-as-kitchensink-rf.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-as-kitchensink-rf.war#primary\": Failed to start service"}}
> 15:10:49,854 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010409: Unbound data source [jboss/datasources/KitchensinkrfQuickstartDS]
> 15:10:49,865 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment jboss-as-kitchensink-rf.war in 23ms
> 15:10:49,866 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.persistenceunit."jboss-as-kitchensink-rf.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-as-kitchensink-rf.war#primary": Failed to start service
> 15:10:49,868 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-as-kitchensink-rf.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-as-kitchensink-rf.war#primary\": Failed to start service"}}}}
> {noformat}
> Note, that deploying via maven goal jboss-as:deploy as described in readme.md works fine.
--
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, 2 months
[JBoss JIRA] (JBIDE-16626) OpenShift Server Adapter: Binary deployment
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16626?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16626:
----------------------------------
Assignee: Andre Dietisheim
> OpenShift Server Adapter: Binary deployment
> -------------------------------------------
>
> Key: JBIDE-16626
> URL: https://issues.jboss.org/browse/JBIDE-16626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Final, 4.2.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
>
> At first, I am not sure whether this is bug or desired behaviour (in that case this issue is Enhancement). There is a problem with binary deployment.
> Current workflow is following:
> PRESTEPS:
> 1. Create OpenShift application (e.g. EAP through OpenShift explorer, context menu, new application)
> 2. Open Project Explorer, select application and open context menu OpenShift - Configure Markers...
> 3. Select disable maven build marker. You can select also Hot deploy to improve deploying speed (no need to restart cartridge).
> 4. Open Navigator - .openshift - markers and select new markers and add them to Index (context menu - Team - Add to Index)
> 5. Push application to OpenShift (e.g. context menu of application - Team - Commit...)
> BINARY DEPLOYMENT
> 1. Now imagine, you want to binary deploy. Let's say, user change something in index.html (for example title).
> 2. Then it's required to locally build application (context menu of application - Run as - Maven build and set goal "clean package -Popenshift"). Result - application is build in deployment folder as ROOT.war.
> 3. Add ROOT.war to git index (context menu - Team - Add to index)
> 4. Drag and drop application from Project Explorer to Servers view adapter onto the given OpenShift adapter.
> 5. Confirm push.
> My idea of binary deployment is:
> 1. User change something in application
> 2. Drag and drop application from Project Explorer to Servers view onto OpenShift adapter - this step build application, add ROOT.war to index.
> 3. Confirm to push.
--
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, 2 months
[JBoss JIRA] (JBIDE-16626) OpenShift Server Adapter: Binary deployment
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-16626:
-------------------------------------
Summary: OpenShift Server Adapter: Binary deployment
Key: JBIDE-16626
URL: https://issues.jboss.org/browse/JBIDE-16626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.Final, 4.2.0.Alpha2
Reporter: Marián Labuda
At first, I am not sure whether this is bug or desired behaviour (in that case this issue is Enhancement). There is a problem with binary deployment.
Current workflow is following:
PRESTEPS:
1. Create OpenShift application (e.g. EAP through OpenShift explorer, context menu, new application)
2. Open Project Explorer, select application and open context menu OpenShift - Configure Markers...
3. Select disable maven build marker. You can select also Hot deploy to improve deploying speed (no need to restart cartridge).
4. Open Navigator - .openshift - markers and select new markers and add them to Index (context menu - Team - Add to Index)
5. Push application to OpenShift (e.g. context menu of application - Team - Commit...)
BINARY DEPLOYMENT
1. Now imagine, you want to binary deploy. Let's say, user change something in index.html (for example title).
2. Then it's required to locally build application (context menu of application - Run as - Maven build and set goal "clean package -Popenshift"). Result - application is build in deployment folder as ROOT.war.
3. Add ROOT.war to git index (context menu - Team - Add to index)
4. Drag and drop application from Project Explorer to Servers view adapter onto the given OpenShift adapter.
5. Confirm push.
My idea of binary deployment is:
1. User change something in application
2. Drag and drop application from Project Explorer to Servers view onto OpenShift adapter - this step build application, add ROOT.war to index.
3. Confirm to push.
--
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, 2 months