[JBoss JIRA] (FORGEPLUGINS-203) Spring Boot setup command
by Ivan St. Ivanov (JIRA)
Ivan St. Ivanov created FORGEPLUGINS-203:
--------------------------------------------
Summary: Spring Boot setup command
Key: FORGEPLUGINS-203
URL: https://issues.jboss.org/browse/FORGEPLUGINS-203
Project: Forge Plugins/Addons
Issue Type: Sub-task
Reporter: Ivan St. Ivanov
Develop a command for setting up Spring Boot. It should install the Spring Boot facet. Upon its installation, the latter should add the needed dependencies in the pom.xml (or build.gradle), create the Spring Boot Application main class and the application.properties.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (FORGEPLUGINS-202) Enable JPA facet in Spring Boot projects
by Ivan St. Ivanov (JIRA)
[ https://issues.jboss.org/browse/FORGEPLUGINS-202?page=com.atlassian.jira.... ]
Ivan St. Ivanov reassigned FORGEPLUGINS-202:
--------------------------------------------
Assignee: Ivan St. Ivanov
> Enable JPA facet in Spring Boot projects
> ----------------------------------------
>
> Key: FORGEPLUGINS-202
> URL: https://issues.jboss.org/browse/FORGEPLUGINS-202
> Project: Forge Plugins/Addons
> Issue Type: Sub-task
> Reporter: Ivan St. Ivanov
> Assignee: Ivan St. Ivanov
>
> Spring Boot supports JPA. However instead of configuring it in the Java EE way with persistence.xml, in it uses a properties file for that (and for all their configuration). The current JPA facet implementations however are developed with presistence.xml in mind. The JPA setup wizard itself is also bound somehow to presistence.xml - it picks the facet to install based on that file.
> All the Forge commands for JPA should not be rewritten just because of the fact above. It should be possible in a Spring Boot project to create new entities with Forge even without having persistence.xml.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (FORGEPLUGINS-202) Enable JPA facet in Spring Boot projects
by Ivan St. Ivanov (JIRA)
Ivan St. Ivanov created FORGEPLUGINS-202:
--------------------------------------------
Summary: Enable JPA facet in Spring Boot projects
Key: FORGEPLUGINS-202
URL: https://issues.jboss.org/browse/FORGEPLUGINS-202
Project: Forge Plugins/Addons
Issue Type: Sub-task
Reporter: Ivan St. Ivanov
Spring Boot supports JPA. However instead of configuring it in the Java EE way with persistence.xml, in it uses a properties file for that (and for all their configuration). The current JPA facet implementations however are developed with presistence.xml in mind. The JPA setup wizard itself is also bound somehow to presistence.xml - it picks the facet to install based on that file.
All the Forge commands for JPA should not be rewritten just because of the fact above. It should be possible in a Spring Boot project to create new entities with Forge even without having persistence.xml.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (FORGEPLUGINS-201) Create Spring Boot Addon
by Ivan St. Ivanov (JIRA)
Ivan St. Ivanov created FORGEPLUGINS-201:
--------------------------------------------
Summary: Create Spring Boot Addon
Key: FORGEPLUGINS-201
URL: https://issues.jboss.org/browse/FORGEPLUGINS-201
Project: Forge Plugins/Addons
Issue Type: Feature Request
Reporter: Ivan St. Ivanov
Create an addon that will setup a Spring Boot project and will have commands for adding various functionalities like Spring MVC scaffolding, Spring Security, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (FORGE-2419) Refactoring the JSF Commands
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-2419:
----------------------------------------
Summary: Refactoring the JSF Commands
Key: FORGE-2419
URL: https://issues.jboss.org/browse/FORGE-2419
Project: Forge
Issue Type: Sub-task
Components: Java EE
Affects Versions: 2.17.0.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
Today the JSF methods {{FacesNewBeanCommand}}, {{FacesNewConverterCommand}} and {{FacesNewValidatorCommand}} use templating.
For the little amount of code that is generated, it would be better to use Roaster instead. And in the refactoring process, add some tests.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months