[JBoss JIRA] (JBIDE-16518) Unable to deploy Richfaces project example
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16518?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-16518:
-----------------------------------
Assignee: Snjezana Peco (was: Fred Bricon)
Assigning to Snjeza while I'm away.
> Unable to deploy Richfaces project example
> ------------------------------------------
>
> Key: JBIDE-16518
> URL: https://issues.jboss.org/browse/JBIDE-16518
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> 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: Radim Hopp
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.2.0.Beta1
>
>
> 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, 4 months
[JBoss JIRA] (JBIDE-16257) Cordova Plug-in Discovery wizard should have option to show already installed plug-ins as disabled
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16257?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-16257:
---------------------------------
Fix Version/s: 4.2.0.Beta1
> Cordova Plug-in Discovery wizard should have option to show already installed plug-ins as disabled
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16257
> URL: https://issues.jboss.org/browse/JBIDE-16257
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Assignee: Gorkem Ercan
> Fix For: 4.2.0.Beta1
>
>
> In JBoss Central Software/Updates tab, can select 'show installed' check box and already installed components are shown as disabled (greyed out).
> A similar feature should be added to Cordova plug-in Discovery wizard. As at the moment if you have installed a plug-in and then search for it in discovery wizard, the wizard shows nothing to inform you why is isn't listed - user has to make an assumption that it's because they have already installed it rather than say typed the wrong text in the search field.
--
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, 4 months
[JBoss JIRA] (JBIDE-16257) Cordova Plug-in Discovery wizard should have option to show already installed plug-ins as disabled
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16257?page=com.atlassian.jira.plugi... ]
Gorkem Ercan reassigned JBIDE-16257:
------------------------------------
Assignee: Gorkem Ercan
> Cordova Plug-in Discovery wizard should have option to show already installed plug-ins as disabled
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16257
> URL: https://issues.jboss.org/browse/JBIDE-16257
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Assignee: Gorkem Ercan
>
> In JBoss Central Software/Updates tab, can select 'show installed' check box and already installed components are shown as disabled (greyed out).
> A similar feature should be added to Cordova plug-in Discovery wizard. As at the moment if you have installed a plug-in and then search for it in discovery wizard, the wizard shows nothing to inform you why is isn't listed - user has to make an assumption that it's because they have already installed it rather than say typed the wrong text in the search field.
--
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, 4 months
[JBoss JIRA] (JBIDE-16591) Remove remote JBoss Archetype catalog - CLONE
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16591?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-16591.
---------------------------------
Resolution: Done
Fixed in master
> Remove remote JBoss Archetype catalog - CLONE
> ---------------------------------------------
>
> Key: JBIDE-16591
> URL: https://issues.jboss.org/browse/JBIDE-16591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.2.0.Beta1
>
>
> The JBoss remote archetype catalog was added with JBIDE-12094 to mitigate the loss of functionality caused by the removal of the JBoss nexus index (which caused JBIDE-12066)
> Problem is, m2e tries to check the origin of a given archetype several (3 minimum) times during the creation process. It tries to lookup any selected archetype in all remote repositories in order to get the matching remote url if possible.
> Problem is, JBoss Nexus is super super slow. Each lookup takes between 5 and 10 seconds (or more!). Given most archetypes come from Maven central this is a waste of time. When removed, creating any project from either JBoss Central or the Maven Wizard becomes much, much, *much* faster.
> I have some work in progress to fix the dubious lookup logic in m2e but that won't be available before next june.
> I believe even switchyard archetypes are now synch'ed to Maven central so the JBoss Archetype Catalog is not relevant anymore. I propose we remove it from the JBoss Maven Integration plugin. [~rcernich] WDYT?
--
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, 4 months
[JBoss JIRA] (JBIDE-16591) Remove remote JBoss Archetype catalog - CLONE
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16591?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16591:
--------------------------------
Fix Version/s: 4.2.0.Beta1
(was: 4.1.2.CR1)
> Remove remote JBoss Archetype catalog - CLONE
> ---------------------------------------------
>
> Key: JBIDE-16591
> URL: https://issues.jboss.org/browse/JBIDE-16591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.2.0.Beta1
>
>
> The JBoss remote archetype catalog was added with JBIDE-12094 to mitigate the loss of functionality caused by the removal of the JBoss nexus index (which caused JBIDE-12066)
> Problem is, m2e tries to check the origin of a given archetype several (3 minimum) times during the creation process. It tries to lookup any selected archetype in all remote repositories in order to get the matching remote url if possible.
> Problem is, JBoss Nexus is super super slow. Each lookup takes between 5 and 10 seconds (or more!). Given most archetypes come from Maven central this is a waste of time. When removed, creating any project from either JBoss Central or the Maven Wizard becomes much, much, *much* faster.
> I have some work in progress to fix the dubious lookup logic in m2e but that won't be available before next june.
> I believe even switchyard archetypes are now synch'ed to Maven central so the JBoss Archetype Catalog is not relevant anymore. I propose we remove it from the JBoss Maven Integration plugin. [~rcernich] WDYT?
--
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, 4 months
[JBoss JIRA] (JBIDE-16591) Remove remote JBoss Archetype catalog - CLONE
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16591?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16591:
--------------------------------
Git Pull Request: (was: https://github.com/jbosstools/jbosstools-central/pull/212)
> Remove remote JBoss Archetype catalog - CLONE
> ---------------------------------------------
>
> Key: JBIDE-16591
> URL: https://issues.jboss.org/browse/JBIDE-16591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.2.0.Beta1
>
>
> The JBoss remote archetype catalog was added with JBIDE-12094 to mitigate the loss of functionality caused by the removal of the JBoss nexus index (which caused JBIDE-12066)
> Problem is, m2e tries to check the origin of a given archetype several (3 minimum) times during the creation process. It tries to lookup any selected archetype in all remote repositories in order to get the matching remote url if possible.
> Problem is, JBoss Nexus is super super slow. Each lookup takes between 5 and 10 seconds (or more!). Given most archetypes come from Maven central this is a waste of time. When removed, creating any project from either JBoss Central or the Maven Wizard becomes much, much, *much* faster.
> I have some work in progress to fix the dubious lookup logic in m2e but that won't be available before next june.
> I believe even switchyard archetypes are now synch'ed to Maven central so the JBoss Archetype Catalog is not relevant anymore. I propose we remove it from the JBoss Maven Integration plugin. [~rcernich] WDYT?
--
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, 4 months
[JBoss JIRA] (JBIDE-16591) Remove remote JBoss Archetype catalog - CLONE
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-16591:
-----------------------------------
Summary: Remove remote JBoss Archetype catalog - CLONE
Key: JBIDE-16591
URL: https://issues.jboss.org/browse/JBIDE-16591
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.1.1.Final
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 4.1.2.CR1
The JBoss remote archetype catalog was added with JBIDE-12094 to mitigate the loss of functionality caused by the removal of the JBoss nexus index (which caused JBIDE-12066)
Problem is, m2e tries to check the origin of a given archetype several (3 minimum) times during the creation process. It tries to lookup any selected archetype in all remote repositories in order to get the matching remote url if possible.
Problem is, JBoss Nexus is super super slow. Each lookup takes between 5 and 10 seconds (or more!). Given most archetypes come from Maven central this is a waste of time. When removed, creating any project from either JBoss Central or the Maven Wizard becomes much, much, *much* faster.
I have some work in progress to fix the dubious lookup logic in m2e but that won't be available before next june.
I believe even switchyard archetypes are now synch'ed to Maven central so the JBoss Archetype Catalog is not relevant anymore. I propose we remove it from the JBoss Maven Integration plugin. [~rcernich] WDYT?
--
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, 4 months
[JBoss JIRA] (JBIDE-14744) Allow users to choose from quickstarts/templates when creatingApplication wizard: new application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14744?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14744:
-------------------------------------
Priority: Blocker (was: Major)
> Allow users to choose from quickstarts/templates when creatingApplication wizard: new application
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14744
> URL: https://issues.jboss.org/browse/JBIDE-14744
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.2.0.Beta1
>
> Attachments: 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.png, alternative-cartridges.png, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.png, openshift-quickstart.png
>
>
> The web ui offers a large set of quickstarts/templates:
> !openshift-quickstart.png!
> in a mail from clayton on the 4th of june:
> {quote}
> For QuickStarts, brokers may choose to
> a) enable community quickstarts
> (the URL you saw below, set by COMMUNITY_QUICKSTART_URL being a URL in /etc/openshift/broker.conf)
> b) enable their own list of quickstarts
> (a different url, /broker/rest/quickstarts, configured from /etc/openshift/quickstarts.json)
> c) disable the quickstarts link
> (delete /etc/openshift/quickstarts.json)
> To correctly fetch the quickstarts for a server, retrieve the API document
> /broker/rest/api
> and look for the LIST_QUICKSTARTS link. If it is present, you may retrieve quickstarts. If it is absent, you should assume there are no quickstarts.
> Retrieving the list of quickstarts, unlike other REST API feed calls, is very specific:
> * API versioning is not supported
> * Only JSON is supported
> * The body of the response is slightly different than standard REST API feed results
> * If you encounter a parse error or an unexpected data value you are required to handle it gracefully by omitting the entry - the API may change without warning (although hopefully not)
> The format of the JSON response (in either a) or b) above) is:
> {quote}
> {code}
> {
> data: [
> quickstart: {
> id: "<string id>",
> href: "<absolute URL to a display URL for the quickstart>",
> name: "<name>",
> updated: "<last update date in seconds from the epoch>",
> summary: "<brief HTML body of the item>",
> body: "<full HTML body of the item>",
> cartridges: "<cartridge spec>",
> website: "<URL of metadata about the source of the quickstart or the technology>",
> tags: "<comma delimited list of tags>",
> language: "<display name of the type of quickstart>",
> initial_git_url: "<absolute URL or Git reference to source>",
> provider: "openshift|reviewed|partner|community", # default is community
> },
> ]
> }
> {code}
> {quote}
> You should assume that arbitrary content could be injected into any of these fields and defend yourself against XSS appropriately. You should also assume that the structure could be changed at any time.
> Cartridge spec:
> The cartridge spec is defined as either:
> a) a comma delimited list of cartridge name search conditions
> b) a string containing a JSON array
> If the leading character of the cartridge spec is '[', you must convert the cartridge spec to JSON and submit the value provided to the server on creation as the "cartridges" field.
> Otherwise,
> 1) split the string by "," into "segments"
> 2) trim whitespace from each segment
> 3) split each segment by "|" into "matches" - these represent logical ORs
> 4) strip leading and trailing "*" characters
> 5) For each segment, return all cartridges that have a case-insensitive substring match on any of the "matches" in that segment for the user to select.
> See https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea...
> and https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea...
> {quote}
--
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, 4 months