[JBoss JIRA] (FORGE-840) Provide a dependency information repository for the current project
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-840?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-840.
---------------------------------
Resolution: Duplicate Issue
Duplicate of FORGE-563
> Provide a dependency information repository for the current project
> -------------------------------------------------------------------
>
> Key: FORGE-840
> URL: https://issues.jboss.org/browse/FORGE-840
> Project: Forge
> Issue Type: Feature Request
> Components: Usability
> Affects Versions: 1.2.2.Final, 2.0.0.Alpha1
> Reporter: George Gastaldi
> Assignee: George Gastaldi
>
> It would be nice if Forge could provide a query-able mechanism for a project so it would be possible to retrieve information like:
> - All available @Entity mapped classes;
> - Classes that implement a specific interface;
> - Is a specific class present in the configured pom.xml?
> That would enrich user experience and also allow the writing of smarter plugins.
--
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
11 years, 8 months
[JBoss JIRA] (FORGE-840) Provide a dependency information repository for the current project
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-840?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-840:
----------------------------------
Fix Version/s: (was: 2.0.0.Alpha2)
(was: 1.2.3.Final)
> Provide a dependency information repository for the current project
> -------------------------------------------------------------------
>
> Key: FORGE-840
> URL: https://issues.jboss.org/browse/FORGE-840
> Project: Forge
> Issue Type: Feature Request
> Components: Usability
> Affects Versions: 1.2.2.Final, 2.0.0.Alpha1
> Reporter: George Gastaldi
> Assignee: George Gastaldi
>
> It would be nice if Forge could provide a query-able mechanism for a project so it would be possible to retrieve information like:
> - All available @Entity mapped classes;
> - Classes that implement a specific interface;
> - Is a specific class present in the configured pom.xml?
> That would enrich user experience and also allow the writing of smarter plugins.
--
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
11 years, 8 months
[JBoss JIRA] (FORGE-840) Provide a dependency information repository for the current project
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-840?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-840.
---------------------------------
Resolution: Duplicate Issue
Duplicate of FORGE-563
> Provide a dependency information repository for the current project
> -------------------------------------------------------------------
>
> Key: FORGE-840
> URL: https://issues.jboss.org/browse/FORGE-840
> Project: Forge
> Issue Type: Feature Request
> Components: Usability
> Affects Versions: 1.2.2.Final, 2.0.0.Alpha1
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 1.2.3.Final, 2.0.0.Alpha2
>
>
> It would be nice if Forge could provide a query-able mechanism for a project so it would be possible to retrieve information like:
> - All available @Entity mapped classes;
> - Classes that implement a specific interface;
> - Is a specific class present in the configured pom.xml?
> That would enrich user experience and also allow the writing of smarter plugins.
--
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
11 years, 8 months
[JBoss JIRA] (FORGE-840) Provide a dependency information repository for the current project
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-840?page=com.atlassian.jira.plugin.... ]
George Gastaldi reopened FORGE-840:
-----------------------------------
> Provide a dependency information repository for the current project
> -------------------------------------------------------------------
>
> Key: FORGE-840
> URL: https://issues.jboss.org/browse/FORGE-840
> Project: Forge
> Issue Type: Feature Request
> Components: Usability
> Affects Versions: 1.2.2.Final, 2.0.0.Alpha1
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 1.2.3.Final, 2.0.0.Alpha2
>
>
> It would be nice if Forge could provide a query-able mechanism for a project so it would be possible to retrieve information like:
> - All available @Entity mapped classes;
> - Classes that implement a specific interface;
> - Is a specific class present in the configured pom.xml?
> That would enrich user experience and also allow the writing of smarter plugins.
--
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
11 years, 8 months
[JBoss JIRA] (FORGE-835) Forge field plugin doesn't support lobs / byte arrays
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-835?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-835:
----------------------------------
Status: Closed (was: Pull Request Sent)
Resolution: Done
Merged, good job ivan !
> Forge field plugin doesn't support lobs / byte arrays
> -----------------------------------------------------
>
> Key: FORGE-835
> URL: https://issues.jboss.org/browse/FORGE-835
> Project: Forge
> Issue Type: Feature Request
> Components: Builtin Plugins
> Affects Versions: 1.2.2.Final
> Reporter: Ivan St. Ivanov
> Assignee: Ivan St. Ivanov
> Fix For: 1.2.3.Final
>
>
> Right now Forge's field plugin supports most of the common Java/JPA types as commands (string, number, date, etc.). It also supports JPA relationships (one-to-many, etc.). However, a very common scenario for a Java EE developer is to store an image or other binary object into the database.
> In such situations the JPA best practices say that it should be declared as byte array field and annotated with @Lob.
> Forge should be able to generate such fields when the command:
> {code:java}
> field lob --named <field-name>
> {code}
> is issued
> The exact name of the command (lob or bytearray or anything) is subject to discussion.
--
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
11 years, 8 months
[JBoss JIRA] (FORGE-835) Forge field plugin doesn't support lobs / byte arrays
by Ivan St. Ivanov (JIRA)
[ https://issues.jboss.org/browse/FORGE-835?page=com.atlassian.jira.plugin.... ]
Ivan St. Ivanov updated FORGE-835:
----------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/forge/core/pull/305
> Forge field plugin doesn't support lobs / byte arrays
> -----------------------------------------------------
>
> Key: FORGE-835
> URL: https://issues.jboss.org/browse/FORGE-835
> Project: Forge
> Issue Type: Feature Request
> Components: Builtin Plugins
> Affects Versions: 1.2.2.Final
> Reporter: Ivan St. Ivanov
> Assignee: Ivan St. Ivanov
> Fix For: 1.2.3.Final
>
>
> Right now Forge's field plugin supports most of the common Java/JPA types as commands (string, number, date, etc.). It also supports JPA relationships (one-to-many, etc.). However, a very common scenario for a Java EE developer is to store an image or other binary object into the database.
> In such situations the JPA best practices say that it should be declared as byte array field and annotated with @Lob.
> Forge should be able to generate such fields when the command:
> {code:java}
> field lob --named <field-name>
> {code}
> is issued
> The exact name of the command (lob or bytearray or anything) is subject to discussion.
--
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
11 years, 8 months
[JBoss JIRA] (FORGE-842) Add managed plugin support to MavenPluginFacet
by charles SALMON (JIRA)
charles SALMON created FORGE-842:
------------------------------------
Summary: Add managed plugin support to MavenPluginFacet
Key: FORGE-842
URL: https://issues.jboss.org/browse/FORGE-842
Project: Forge
Issue Type: Story
Components: Maven Integration
Reporter: charles SALMON
Assignee: charles SALMON
Maven offers a way to handle plugins by using the "pluginManagement" feature (similar to the "dependencyManagement" one).
The idea here is to enhance the MavenPluginFacet with the following methods:
{code:java}
List<MavenPlugin> listConfiguredManagedPlugins();
boolean hasManagedPlugin(Dependency dependency);
MavenPlugin getManagedPlugin(Dependency dependency);
void addManagedPlugin(MavenPlugin plugin);
void removeManagedPlugin(Dependency dependency);
void updateManagedPlugin(final MavenPlugin plugin);
{code}
--
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
11 years, 8 months