July 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2384) JPAFacet.isInstalled() should only check for descriptor's existence

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2384?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2384. ---------------------------------- Resolution: Done > JPAFacet.isInstalled() should only check for descriptor's existence > ------------------------------------------------------------------- > > Key: FORGE-2384 > URL: https://issues.jboss.org/browse/FORGE-2384 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 2.16.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.17.0.Final > > > The JPAFacet implementations depend on certain libraries to be installed to be enabled. > However, if a project already has EclipseLink JARs or even OpenJPA JARs, the JPA Facet is not recognized as installed. Therefore, it would be much better if the JPAFacet logic for installation ({{isInstalled()}}) would just check for persistence descriptor existence and the version attribute. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2385) JPA facet should return the JPA provider

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2385?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2385: ---------------------------------------- It would be also nice to have a setPersistenceProvider, so when the following code is executed, the EclipseLink JARs are installed instead of the JavaEE/Hibernate ones: {code:java} FacetFactory facetFactory = ... EclipseLinkProvider provider = ... Project project = ... JPAFacet_2_0 facet = facetFactory.create(project, JPAFacet_2_0.class); facet.setPersistenceProvider(provider); // Install the JPA 2.0 facet facetFactory.install(project,facet); {code} > JPA facet should return the JPA provider > ---------------------------------------- > > Key: FORGE-2385 > URL: https://issues.jboss.org/browse/FORGE-2385 > Project: Forge > Issue Type: Feature Request > Components: Facets, Java EE > Affects Versions: 2.17.0.Final > Reporter: Ivan St. Ivanov > Assignee: Ivan St. Ivanov > > At the moment when JPA facet is installed, the user enters the selected JPA provider (Hibernate JPA, Eclipselink, Open JPA, Java EE). But afterwards in later stages in the project, they are not able to obtain the information about that setting. > The JPA facet should have a method with the following signature: > PersistenceProvider getPersistenceProvider(); > Its implementation should not count on any data stored by Forge on previous step and should work both on projects where JPA was setup by Forge and where the dependencies and persistence.xml were configured by the user with other means. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2384) JPAFacet.isInstalled() should only check for descriptor's existence

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2384?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2384: ----------------------------------- Description: The JPAFacet implementations depend on certain libraries to be installed to be enabled. However, if a project already has EclipseLink JARs or even OpenJPA JARs, the JPA Facet is not recognized as installed. Therefore, it would be much better if the JPAFacet logic for installation ({{isInstalled()}}) would just check for persistence descriptor existence and the version attribute. was: The JPAFacet implementations depend on certain libraries to be installed to be enabled. However, if a project already has EclipseLink JARs, the JPA Facet is not recognized as installed. Therefore, it would be much better if the JPAFacet logic for installation ({{isInstalled()}}) would just check for persistence descriptor existence and the version attribute. Component/s: Java EE Forum Reference: http://lists.jboss.org/pipermail/forge-dev/2015-July/004289.html > JPAFacet.isInstalled() should only check for descriptor's existence > ------------------------------------------------------------------- > > Key: FORGE-2384 > URL: https://issues.jboss.org/browse/FORGE-2384 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 2.16.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.17.0.Final > > > The JPAFacet implementations depend on certain libraries to be installed to be enabled. > However, if a project already has EclipseLink JARs or even OpenJPA JARs, the JPA Facet is not recognized as installed. Therefore, it would be much better if the JPAFacet logic for installation ({{isInstalled()}}) would just check for persistence descriptor existence and the version attribute. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2385) JPA facet should return the JPA provider

by Ivan St. Ivanov (JIRA)

Ivan St. Ivanov created FORGE-2385: -------------------------------------- Summary: JPA facet should return the JPA provider Key: FORGE-2385 URL: https://issues.jboss.org/browse/FORGE-2385 Project: Forge Issue Type: Feature Request Components: Facets, Java EE Affects Versions: 2.17.0.Final Reporter: Ivan St. Ivanov At the moment when JPA facet is installed, the user enters the selected JPA provider (Hibernate JPA, Eclipselink, Open JPA, Java EE). But afterwards in later stages in the project, they are not able to obtain the information about that setting. The JPA facet should have a method with the following signature: PersistenceProvider getPersistenceProvider(); Its implementation should not count on any data stored by Forge on previous step and should work both on projects where JPA was setup by Forge and where the dependencies and persistence.xml were configured by the user with other means. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2385) JPA facet should return the JPA provider

by Ivan St. Ivanov (JIRA)

[ https://issues.jboss.org/browse/FORGE-2385?page=com.atlassian.jira.plugin... ] Ivan St. Ivanov reassigned FORGE-2385: -------------------------------------- Assignee: Ivan St. Ivanov > JPA facet should return the JPA provider > ---------------------------------------- > > Key: FORGE-2385 > URL: https://issues.jboss.org/browse/FORGE-2385 > Project: Forge > Issue Type: Feature Request > Components: Facets, Java EE > Affects Versions: 2.17.0.Final > Reporter: Ivan St. Ivanov > Assignee: Ivan St. Ivanov > > At the moment when JPA facet is installed, the user enters the selected JPA provider (Hibernate JPA, Eclipselink, Open JPA, Java EE). But afterwards in later stages in the project, they are not able to obtain the information about that setting. > The JPA facet should have a method with the following signature: > PersistenceProvider getPersistenceProvider(); > Its implementation should not count on any data stored by Forge on previous step and should work both on projects where JPA was setup by Forge and where the dependencies and persistence.xml were configured by the user with other means. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2384) JPAFacet.isInstalled() should only check for descriptor's existence

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2384: -------------------------------------- Summary: JPAFacet.isInstalled() should only check for descriptor's existence Key: FORGE-2384 URL: https://issues.jboss.org/browse/FORGE-2384 Project: Forge Issue Type: Enhancement Affects Versions: 2.16.2.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.17.0.Final The JPAFacet implementations depend on certain libraries to be installed to be enabled. However, if a project already has EclipseLink JARs, the JPA Facet is not recognized as installed. Therefore, it would be much better if the JPAFacet logic for installation ({{isInstalled()}}) would just check for persistence descriptor existence and the version attribute. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-74) It's better for precise operation that the source code writer retains original spaces

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-74?page=com.atlassian.jira.plugin... ] George Gastaldi closed ROASTER-74. ---------------------------------- Assignee: Shoji Kuzukami Fix Version/s: 2.14.1.Final Resolution: Done > It's better for precise operation that the source code writer retains original spaces > -------------------------------------------------------------------------------------- > > Key: ROASTER-74 > URL: https://issues.jboss.org/browse/ROASTER-74 > Project: Roaster > Issue Type: Enhancement > Components: JDT > Affects Versions: 2.x Future > Environment: Win 8.1 Pro 64bit, Eclipse Mars 64bit, Java 8 > Reporter: Shoji Kuzukami > Assignee: Shoji Kuzukami > Fix For: 2.14.1.Final > > > I want to verify a source code modified by the 'roast' by using a diff based utility because the modification can unexpectedly break the semantics of original source code by any bugs of the library. > But the code writer #toString() in roaster writes a 'formatted' source code removing some white spaces in the original. So the diff utility cannot be simply applied. > It's better that the source code writer emits such a code that the original code is minimally operated as well as it can, because the roaster formatter can be used independently by calling Formatter.format(String). > Although this is a design-concept issue of this project, it's happy for me that the pull-request following is accepted. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2383) Upgrade to Furnace 2.19.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2383?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2383. ---------------------------------- Resolution: Done > Upgrade to Furnace 2.19.0.Final > ------------------------------- > > Key: FORGE-2383 > URL: https://issues.jboss.org/browse/FORGE-2383 > Project: Forge > Issue Type: Component Upgrade > Components: Furnace (Container) > Affects Versions: 2.16.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.17.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2383) Upgrade to Furnace 2.19.0.Final

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2383: -------------------------------------- Summary: Upgrade to Furnace 2.19.0.Final Key: FORGE-2383 URL: https://issues.jboss.org/browse/FORGE-2383 Project: Forge Issue Type: Component Upgrade Components: Furnace (Container) Affects Versions: 2.16.2.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.17.0.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2382) Add a isSerializable parameter to the cdi-new-bean command

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2382?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-2382: ------------------------------------------ Yes. I think the naming of some commands should be homogeinized. Sometimes we use {{not-nullable}} (in JPA for nullable = false) or {{withNamed}} (for a bean with @Named). > Add a isSerializable parameter to the cdi-new-bean command > ---------------------------------------------------------- > > Key: FORGE-2382 > URL: https://issues.jboss.org/browse/FORGE-2382 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.16.2.Final > Reporter: Antonio Goncalves > Labels: starter > Fix For: 2.x Future > > > Sometimes it's useful/mandatory to have CDI beans that are serializable. At the moment the {{cdi-new-bean}} command doesn't allow us to do that easily (except using scopes that are not always needed). A simple boolean {{isSerializable}} could do : > {code} > cdi-new-bean --named LoggerProducer --isSerializable > {code} > This would generate : > {code} > public class LoggerProducer implements Serializable > { > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2015