[JBoss JIRA] (FORGE-1182) Addons generated by NewProjectWizard should contain a sample README.asciidoc
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1182?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1182.
----------------------------------
Resolution: Done
> Addons generated by NewProjectWizard should contain a sample README.asciidoc
> ----------------------------------------------------------------------------
>
> Key: FORGE-1182
> URL: https://issues.jboss.org/browse/FORGE-1182
> Project: Forge
> Issue Type: Feature Request
> Components: Documentation
> Affects Versions: 2.0.0.Alpha11
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 2.0.0.Alpha12
>
>
> Asciidoc Template:
> {code}
> == ADDON_NAME
> :idprefix: id_
> (choose one, do not modify, then add a second sentence with a brief description, starting with - "The ADDON_NAME addon enables blah blah...)
> This addon provides *standalone* functionality, and *exports services* for use in other addons.
> This addon provides *standalone* functionality.
> This addon *exports services* for use in other addons.
> This addon *provides classes* for use in other addons.
> This addon is a 'Furnace container' that provides *lifecycle* and *service registry* support for dependent addons.
>
> === Dependencies: None (or)
> === Depends on
> [options="header"]
> |===
> |Addon |Exported |Optional
> |DEP1
> |yes
> |no
> |DEP2
> |yes
> |yes
> |===
> == Setup
> This Addon requires the following installation steps.
> === Add configuration to pom.xml
> To use this addon, you must add it as a dependency in the *pom.xml* of your `forge-addon` classified artifact:
> (Make sure the dependency is put all the way to the left, and uses 3 spaces for indentation of GAV)
> [source,xml]
> ----
> <dependency>
> <groupId>ADDON_GROUP_ID</groupId>
> <artifactId>ADDON_ARTIFACT_ID</artifactId>
> <classifier>forge-addon</classifier>
> <version>${version}</version>
> </dependency>
> ----
> == Features
> ABCFactory for simple ABC blah::
> Allows for blah blah
> +
> [source,java]
> ----
> @Inject private ABCFactory factory;
> ABC abc = factory.createABC();
> ----
> +
> [TIP]
> ====
> If your addon uses a container that does not support "@Inject" annotations, services such as the `ABCFactory` may also be
> accessed via the `AddonRegistry`:
> ----
> Imported<ABCFactory> imported = addonRegistry.getServices(ABCFactory.class);
> ABCFactory factory = imported.get();
> ----
> ====
> Creating a new XYZ instance::
> Causes XYZ to occur
> +
> [source,java]
> ----
> XYZ xyz = factory.createXYZ();
> ----
> {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
12 years, 10 months
[JBoss JIRA] (FORGE-1181) Inherited injection points are not be resolved
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1181?page=com.atlassian.jira.plugin... ]
George Gastaldi deleted FORGE-1181:
-----------------------------------
> Inherited injection points are not be resolved
> ----------------------------------------------
>
> Key: FORGE-1181
> URL: https://issues.jboss.org/browse/FORGE-1181
> Project: Forge
> Issue Type: Bug
> Reporter: George Gastaldi
>
> if you create a class in the projects-api module
> {code}
> public abstract class AbstractProjectCommand extends AbstractUICommand
> {
> @Inject
> protected ProjectFactory projectFactory;
> }
> {code}
> And create a class in the javaee-impl module that extends it, the following error is thrown:
> {code}
> WELD-001408 Unsatisfied dependencies for type [ProjectFactory] with qualifiers [@Default] at injection point [[BackedAnnotatedField] @Inject protected org.jboss.forge.addon.projects.ui.AbstractProjectCommand.projectFactory]
> {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
12 years, 10 months
[JBoss JIRA] (FORGE-1182) Addons generated by NewProjectWizard should contain a sample README.asciidoc
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1182?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1182:
-----------------------------------
Description:
Asciidoc Template:
{code}
== ADDON_NAME
:idprefix: id_
(choose one, do not modify, then add a second sentence with a brief description, starting with - "The ADDON_NAME addon enables blah blah...)
This addon provides *standalone* functionality, and *exports services* for use in other addons.
This addon provides *standalone* functionality.
This addon *exports services* for use in other addons.
This addon *provides classes* for use in other addons.
This addon is a 'Furnace container' that provides *lifecycle* and *service registry* support for dependent addons.
=== Dependencies: None (or)
=== Depends on
[options="header"]
|===
|Addon |Exported |Optional
|DEP1
|yes
|no
|DEP2
|yes
|yes
|===
== Setup
This Addon requires the following installation steps.
=== Add configuration to pom.xml
To use this addon, you must add it as a dependency in the *pom.xml* of your `forge-addon` classified artifact:
(Make sure the dependency is put all the way to the left, and uses 3 spaces for indentation of GAV)
[source,xml]
----
<dependency>
<groupId>ADDON_GROUP_ID</groupId>
<artifactId>ADDON_ARTIFACT_ID</artifactId>
<classifier>forge-addon</classifier>
<version>${version}</version>
</dependency>
----
== Features
ABCFactory for simple ABC blah::
Allows for blah blah
+
[source,java]
----
@Inject private ABCFactory factory;
ABC abc = factory.createABC();
----
+
[TIP]
====
If your addon uses a container that does not support "@Inject" annotations, services such as the `ABCFactory` may also be
accessed via the `AddonRegistry`:
----
Imported<ABCFactory> imported = addonRegistry.getServices(ABCFactory.class);
ABCFactory factory = imported.get();
----
====
Creating a new XYZ instance::
Causes XYZ to occur
+
[source,java]
----
XYZ xyz = factory.createXYZ();
----
{code}
was:
Asciidoc Template:
{code}
== ADDON_NAME
:idprefix: id_
(choose one, do not modify, then add a second sentence with a brief description, starting with - "The ADDON_NAME addon enables blah blah...)
This addon provides *standalone* functionality, and *exports services* for use in other addons.
This addon provides *standalone* functionality.
This addon *exports services* for use in other addons.
This addon *provides classes* for use in other addons.
This addon is a 'Furnace container' that provides *lifecycle* and *service registry* support for dependent addons.
=== Dependencies: None (or)
=== Depends on
[options="header"]
|===
|Addon |Exported |Optional
|DEP1
|yes
|no
|DEP2
|yes
|yes
|===
[TBD - Depends on FORGE-869 - image of the addon dependency graph - linked from /addon/dependencies.dot]
== Setup
This Addon requires the following installation steps.
=== Add configuration to pom.xml
To use this addon, you must add it as a dependency in the *pom.xml* of your `forge-addon` classified artifact:
(Make sure the dependency is put all the way to the left, and uses 3 spaces for indentation of GAV)
[source,xml]
----
<dependency>
<groupId>ADDON_GROUP_ID</groupId>
<artifactId>ADDON_ARTIFACT_ID</artifactId>
<classifier>forge-addon</classifier>
<version>${version}</version>
</dependency>
----
== Features
ABCFactory for simple ABC blah::
Allows for blah blah
+
[source,java]
----
@Inject private ABCFactory factory;
ABC abc = factory.createABC();
----
+
[TIP]
====
If your addon uses a container that does not support "@Inject" annotations, services such as the `ABCFactory` may also be
accessed via the `AddonRegistry`:
----
Imported<ABCFactory> imported = addonRegistry.getServices(ABCFactory.class);
ABCFactory factory = imported.get();
----
====
Creating a new XYZ instance::
Causes XYZ to occur
+
[source,java]
----
XYZ xyz = factory.createXYZ();
----
{code}
> Addons generated by NewProjectWizard should contain a sample README.asciidoc
> ----------------------------------------------------------------------------
>
> Key: FORGE-1182
> URL: https://issues.jboss.org/browse/FORGE-1182
> Project: Forge
> Issue Type: Feature Request
> Components: Documentation
> Affects Versions: 2.0.0.Alpha11
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 2.0.0.Alpha12
>
>
> Asciidoc Template:
> {code}
> == ADDON_NAME
> :idprefix: id_
> (choose one, do not modify, then add a second sentence with a brief description, starting with - "The ADDON_NAME addon enables blah blah...)
> This addon provides *standalone* functionality, and *exports services* for use in other addons.
> This addon provides *standalone* functionality.
> This addon *exports services* for use in other addons.
> This addon *provides classes* for use in other addons.
> This addon is a 'Furnace container' that provides *lifecycle* and *service registry* support for dependent addons.
>
> === Dependencies: None (or)
> === Depends on
> [options="header"]
> |===
> |Addon |Exported |Optional
> |DEP1
> |yes
> |no
> |DEP2
> |yes
> |yes
> |===
> == Setup
> This Addon requires the following installation steps.
> === Add configuration to pom.xml
> To use this addon, you must add it as a dependency in the *pom.xml* of your `forge-addon` classified artifact:
> (Make sure the dependency is put all the way to the left, and uses 3 spaces for indentation of GAV)
> [source,xml]
> ----
> <dependency>
> <groupId>ADDON_GROUP_ID</groupId>
> <artifactId>ADDON_ARTIFACT_ID</artifactId>
> <classifier>forge-addon</classifier>
> <version>${version}</version>
> </dependency>
> ----
> == Features
> ABCFactory for simple ABC blah::
> Allows for blah blah
> +
> [source,java]
> ----
> @Inject private ABCFactory factory;
> ABC abc = factory.createABC();
> ----
> +
> [TIP]
> ====
> If your addon uses a container that does not support "@Inject" annotations, services such as the `ABCFactory` may also be
> accessed via the `AddonRegistry`:
> ----
> Imported<ABCFactory> imported = addonRegistry.getServices(ABCFactory.class);
> ABCFactory factory = imported.get();
> ----
> ====
> Creating a new XYZ instance::
> Causes XYZ to occur
> +
> [source,java]
> ----
> XYZ xyz = factory.createXYZ();
> ----
> {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
12 years, 10 months
[JBoss JIRA] (FORGE-1182) Addons generated by NewProjectWizard should contain a sample README.asciidoc
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1182:
--------------------------------------
Summary: Addons generated by NewProjectWizard should contain a sample README.asciidoc
Key: FORGE-1182
URL: https://issues.jboss.org/browse/FORGE-1182
Project: Forge
Issue Type: Feature Request
Components: Documentation
Affects Versions: 2.0.0.Alpha11
Reporter: George Gastaldi
Assignee: George Gastaldi
Fix For: 2.0.0.Alpha12
Asciidoc Template:
{code}
== ADDON_NAME
:idprefix: id_
(choose one, do not modify, then add a second sentence with a brief description, starting with - "The ADDON_NAME addon enables blah blah...)
This addon provides *standalone* functionality, and *exports services* for use in other addons.
This addon provides *standalone* functionality.
This addon *exports services* for use in other addons.
This addon *provides classes* for use in other addons.
This addon is a 'Furnace container' that provides *lifecycle* and *service registry* support for dependent addons.
=== Dependencies: None (or)
=== Depends on
[options="header"]
|===
|Addon |Exported |Optional
|DEP1
|yes
|no
|DEP2
|yes
|yes
|===
[TBD - Depends on FORGE-869 - image of the addon dependency graph - linked from /addon/dependencies.dot]
== Setup
This Addon requires the following installation steps.
=== Add configuration to pom.xml
To use this addon, you must add it as a dependency in the *pom.xml* of your `forge-addon` classified artifact:
(Make sure the dependency is put all the way to the left, and uses 3 spaces for indentation of GAV)
[source,xml]
----
<dependency>
<groupId>ADDON_GROUP_ID</groupId>
<artifactId>ADDON_ARTIFACT_ID</artifactId>
<classifier>forge-addon</classifier>
<version>${version}</version>
</dependency>
----
== Features
ABCFactory for simple ABC blah::
Allows for blah blah
+
[source,java]
----
@Inject private ABCFactory factory;
ABC abc = factory.createABC();
----
+
[TIP]
====
If your addon uses a container that does not support "@Inject" annotations, services such as the `ABCFactory` may also be
accessed via the `AddonRegistry`:
----
Imported<ABCFactory> imported = addonRegistry.getServices(ABCFactory.class);
ABCFactory factory = imported.get();
----
====
Creating a new XYZ instance::
Causes XYZ to occur
+
[source,java]
----
XYZ xyz = factory.createXYZ();
----
{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
12 years, 10 months
[JBoss JIRA] (FORGE-1181) Inherited injection points are not be resolved
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1181:
--------------------------------------
Summary: Inherited injection points are not be resolved
Key: FORGE-1181
URL: https://issues.jboss.org/browse/FORGE-1181
Project: Forge
Issue Type: Bug
Components: Furnace (Container)
Affects Versions: 2.0.0.Alpha11
Reporter: George Gastaldi
Fix For: 2.x Future
if you create a class in the projects-api module
public abstract class AbstractProjectCommand extends AbstractUICommand
{
@Inject
protected ProjectFactory projectFactory;
}
And create a class in the javaee-impl module that extends it, the following error is thrown:
{code}
WELD-001408 Unsatisfied dependencies for type [ProjectFactory] with qualifiers [@Default] at injection point [[BackedAnnotatedField] @Inject protected org.jboss.forge.addon.projects.ui.AbstractProjectCommand.projectFactory]
{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
12 years, 10 months
[JBoss JIRA] (FORGE-1181) Inherited injection points are not be resolved
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1181?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1181:
-----------------------------------
Description:
if you create a class in the projects-api module
{code}
public abstract class AbstractProjectCommand extends AbstractUICommand
{
@Inject
protected ProjectFactory projectFactory;
}
{code}
And create a class in the javaee-impl module that extends it, the following error is thrown:
{code}
WELD-001408 Unsatisfied dependencies for type [ProjectFactory] with qualifiers [@Default] at injection point [[BackedAnnotatedField] @Inject protected org.jboss.forge.addon.projects.ui.AbstractProjectCommand.projectFactory]
{code}
was:
if you create a class in the projects-api module
public abstract class AbstractProjectCommand extends AbstractUICommand
{
@Inject
protected ProjectFactory projectFactory;
}
And create a class in the javaee-impl module that extends it, the following error is thrown:
{code}
WELD-001408 Unsatisfied dependencies for type [ProjectFactory] with qualifiers [@Default] at injection point [[BackedAnnotatedField] @Inject protected org.jboss.forge.addon.projects.ui.AbstractProjectCommand.projectFactory]
{code}
> Inherited injection points are not be resolved
> ----------------------------------------------
>
> Key: FORGE-1181
> URL: https://issues.jboss.org/browse/FORGE-1181
> Project: Forge
> Issue Type: Bug
> Components: Furnace (Container)
> Affects Versions: 2.0.0.Alpha11
> Reporter: George Gastaldi
> Fix For: 2.x Future
>
>
> if you create a class in the projects-api module
> {code}
> public abstract class AbstractProjectCommand extends AbstractUICommand
> {
> @Inject
> protected ProjectFactory projectFactory;
> }
> {code}
> And create a class in the javaee-impl module that extends it, the following error is thrown:
> {code}
> WELD-001408 Unsatisfied dependencies for type [ProjectFactory] with qualifiers [@Default] at injection point [[BackedAnnotatedField] @Inject protected org.jboss.forge.addon.projects.ui.AbstractProjectCommand.projectFactory]
> {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
12 years, 10 months
[JBoss JIRA] (FORGE-1180) Warn when duplicate classes are found in dependencies from separate addons
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1180:
--------------------------------------
Summary: Warn when duplicate classes are found in dependencies from separate addons
Key: FORGE-1180
URL: https://issues.jboss.org/browse/FORGE-1180
Project: Forge
Issue Type: Feature Request
Components: Furnace (Container)
Affects Versions: 2.0.0.Alpha11
Reporter: George Gastaldi
Fix For: 2.x Future
{quote}
<lincolnthree> gastaldi: the APIs will probably conflict if both are used in the same addon. in that case, a classloading-only addon containing the shared APIs must be created
<lincolnthree> gastaldi: this is the only downside of a modular system
<lincolnthree> gastaldi: one of the few downsides :)
<gastaldi> hum
<gastaldi> we need to have some way to query if a class exists in an addon
<lincolnthree> gastaldi: why?
<gastaldi> so we avoid adding duplicate classes in different addons?
<lincolnthree> gastaldi: duplicate classes in addons is not a bug, per-say
<gastaldi> aka: how the heck would I know that one need to create a shared API for the bean-validation?
<lincolnthree> gastaldi: what we could do is possibly some runtime analysis of the code and warn when duplicate classes are found in dependencies from separate addons
<lincolnthree> gastaldi: and we could also run this as a service on the forge website
<gastaldi> lincolnthree, so this shared API is just a enhancement, not requirement?
<lincolnthree> gastaldi: correct
{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, 10 months
[JBoss JIRA] (FORGE-1164) `project remove-managed-dependency` does not remove managed dependency
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1164?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1164:
-------------------------------------------
I was wrong about the parsing. Will have to dig.
> `project remove-managed-dependency` does not remove managed dependency
> ----------------------------------------------------------------------
>
> Key: FORGE-1164
> URL: https://issues.jboss.org/browse/FORGE-1164
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.4.0.Final
> Reporter: Antonio Goncalves
> Fix For: 1.x Future
>
>
> I want to turn a Forge project from being Java EE 6 to Java EE 7 centric. One of these tasks is to change the dependencies in the {{pom.xml}}. So I add the {{javax:javaee-api:7.0}} to the pom and list the managed dependencies :
> {code}
> $ project list-managed-dependencies
> org.jboss.spec : jboss-javaee-6.0 : 3.0.2.Final : pom : import
> org.hibernate : hibernate-validator : 5.1.0.Alpha1 : jar : provided
> javax : javaee-api : 7.0 : jar : provided
> {code}
> If I remove the added {{javax:javaee-api:7.0}}, it works. But if I want to remove the {{org.jboss.spec:jboss-javaee-6.0}}, the console says it doesn't exist :
> {code}
> $ project remove-managed-dependency org.jboss.spec:jboss-javaee-6.0
> Managed dependency [org.jboss.spec:jboss-javaee-6.0:::] not found in project...
> {code}
> I even tried adding version, scope and so on, but it doesn't work :
> {code}
> $ project remove-managed-dependency
> ? [[ groupId :artifactId {:version :scope :packaging} ] (of type org.jboss.forge.project.dependencies.Dependency)]: org.jboss.spec:jboss-javaee-6.0:3.0.2.Final:pom:import
> Managed dependency [org.jboss.spec:jboss-javaee-6.0:import::3.0.2.Final] not found in project...
> {code}
> PS : same occur in Forge 1.3.3-Final
--
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, 10 months
[JBoss JIRA] (FORGE-1164) `project remove-managed-dependency` does not remove managed dependency
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1164?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III updated FORGE-1164:
--------------------------------------
Fix Version/s: 1.x Future
> `project remove-managed-dependency` does not remove managed dependency
> ----------------------------------------------------------------------
>
> Key: FORGE-1164
> URL: https://issues.jboss.org/browse/FORGE-1164
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.4.0.Final
> Reporter: Antonio Goncalves
> Fix For: 1.x Future
>
>
> I want to turn a Forge project from being Java EE 6 to Java EE 7 centric. One of these tasks is to change the dependencies in the {{pom.xml}}. So I add the {{javax:javaee-api:7.0}} to the pom and list the managed dependencies :
> {code}
> $ project list-managed-dependencies
> org.jboss.spec : jboss-javaee-6.0 : 3.0.2.Final : pom : import
> org.hibernate : hibernate-validator : 5.1.0.Alpha1 : jar : provided
> javax : javaee-api : 7.0 : jar : provided
> {code}
> If I remove the added {{javax:javaee-api:7.0}}, it works. But if I want to remove the {{org.jboss.spec:jboss-javaee-6.0}}, the console says it doesn't exist :
> {code}
> $ project remove-managed-dependency org.jboss.spec:jboss-javaee-6.0
> Managed dependency [org.jboss.spec:jboss-javaee-6.0:::] not found in project...
> {code}
> I even tried adding version, scope and so on, but it doesn't work :
> {code}
> $ project remove-managed-dependency
> ? [[ groupId :artifactId {:version :scope :packaging} ] (of type org.jboss.forge.project.dependencies.Dependency)]: org.jboss.spec:jboss-javaee-6.0:3.0.2.Final:pom:import
> Managed dependency [org.jboss.spec:jboss-javaee-6.0:import::3.0.2.Final] not found in project...
> {code}
> PS : same occur in Forge 1.3.3-Final
--
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, 10 months