[JBoss JIRA] (FORGE-1599) Introduce a cache addon
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1599:
--------------------------------------
Summary: Introduce a cache addon
Key: FORGE-1599
URL: https://issues.jboss.org/browse/FORGE-1599
Project: Forge
Issue Type: Feature Request
Components: Blessed Plugins
Reporter: George Gastaldi
Fix For: 2.x Future
This would allow other addons to cache state. It should allow individual configurations of each cache.
There should also have a CacheFactory, to allow creation of caches on-demand.
--
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, 1 month
[JBoss JIRA] (FORGE-1597) Optional facets are preventing installation of facets
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1597?page=com.atlassian.jira.plugin... ]
George Gastaldi reassigned FORGE-1597:
--------------------------------------
Assignee: George Gastaldi
> Optional facets are preventing installation of facets
> -----------------------------------------------------
>
> Key: FORGE-1597
> URL: https://issues.jboss.org/browse/FORGE-1597
> Project: Forge
> Issue Type: Bug
> Components: Plugin API
> Affects Versions: 2.0.0.Final
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Priority: Blocker
> Fix For: 2.0.1.Final
>
>
> FacesFacet declares an optional constraint on ServletFacet. FacetFactoryImpl checks if the optional constraint is satisfied in https://github.com/forge/core/blob/master/facets/impl/src/main/java/org/j... , hence not registering the candidate facet.
> This test summarizes the problem (in
> {{org.jboss.forge.addon.javaee.faces.FacesFacetTest}}):
> {code}
> @Test
> public void testFacesFacetInstalledAfterProjectIsEvictedFromCache()
> {
> Project project = projectFactory.createTempProject();
> facetFactory.install(project, FacesFacet_2_2.class);
> Assert.assertTrue("Should have FacesFacet", project.hasFacet(FacesFacet.class));
> Assert.assertTrue("Should have FacesFacet_2_2", project.hasFacet(FacesFacet_2_2.class));
> projectFactory.invalidateCaches();
> project = projectFactory.findProject(project.getRootDirectory());
> Assert.assertTrue("Should have FacesFacet", project.hasFacet(FacesFacet.class));
> Assert.assertTrue("Should have FacesFacet_2_2", project.hasFacet(FacesFacet_2_2.class));
> }
> {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, 1 month
[JBoss JIRA] (FORGE-1597) Optional facets are preventing installation of facets
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1597?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1597:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/forge/core/pull/390
> Optional facets are preventing installation of facets
> -----------------------------------------------------
>
> Key: FORGE-1597
> URL: https://issues.jboss.org/browse/FORGE-1597
> Project: Forge
> Issue Type: Bug
> Components: Plugin API
> Affects Versions: 2.0.0.Final
> Reporter: George Gastaldi
> Priority: Blocker
> Fix For: 2.0.1.Final
>
>
> FacesFacet declares an optional constraint on ServletFacet. FacetFactoryImpl checks if the optional constraint is satisfied in https://github.com/forge/core/blob/master/facets/impl/src/main/java/org/j... , hence not registering the candidate facet.
> This test summarizes the problem (in
> {{org.jboss.forge.addon.javaee.faces.FacesFacetTest}}):
> {code}
> @Test
> public void testFacesFacetInstalledAfterProjectIsEvictedFromCache()
> {
> Project project = projectFactory.createTempProject();
> facetFactory.install(project, FacesFacet_2_2.class);
> Assert.assertTrue("Should have FacesFacet", project.hasFacet(FacesFacet.class));
> Assert.assertTrue("Should have FacesFacet_2_2", project.hasFacet(FacesFacet_2_2.class));
> projectFactory.invalidateCaches();
> project = projectFactory.findProject(project.getRootDirectory());
> Assert.assertTrue("Should have FacesFacet", project.hasFacet(FacesFacet.class));
> Assert.assertTrue("Should have FacesFacet_2_2", project.hasFacet(FacesFacet_2_2.class));
> }
> {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, 1 month
[JBoss JIRA] (FORGE-1598) MavenFacetImpl retains stale building results
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1598:
--------------------------------------
Summary: MavenFacetImpl retains stale building results
Key: FORGE-1598
URL: https://issues.jboss.org/browse/FORGE-1598
Project: Forge
Issue Type: Bug
Components: Build Tools - Maven
Affects Versions: 2.0.0.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Fix For: 2.0.1.Final
The state should be managed by another object, and shared across multiple MavenFacetImpl instances
--
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, 1 month
[JBoss JIRA] (FORGE-1597) Optional facets are preventing installation of facets
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1597:
--------------------------------------
Summary: Optional facets are preventing installation of facets
Key: FORGE-1597
URL: https://issues.jboss.org/browse/FORGE-1597
Project: Forge
Issue Type: Bug
Components: Plugin API
Affects Versions: 2.0.0.Final
Reporter: George Gastaldi
Priority: Blocker
Fix For: 2.0.1.Final
FacesFacet declares an optional constraint on ServletFacet. FacetFactoryImpl checks if the optional constraint is satisfied in https://github.com/forge/core/blob/master/facets/impl/src/main/java/org/j... , hence not registering the candidate facet.
This test summarizes the problem (in
{{org.jboss.forge.addon.javaee.faces.FacesFacetTest}}):
{code}
@Test
public void testFacesFacetInstalledAfterProjectIsEvictedFromCache()
{
Project project = projectFactory.createTempProject();
facetFactory.install(project, FacesFacet_2_2.class);
Assert.assertTrue("Should have FacesFacet", project.hasFacet(FacesFacet.class));
Assert.assertTrue("Should have FacesFacet_2_2", project.hasFacet(FacesFacet_2_2.class));
projectFactory.invalidateCaches();
project = projectFactory.findProject(project.getRootDirectory());
Assert.assertTrue("Should have FacesFacet", project.hasFacet(FacesFacet.class));
Assert.assertTrue("Should have FacesFacet_2_2", project.hasFacet(FacesFacet_2_2.class));
}
{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, 1 month
[JBoss JIRA] (FORGE-1596) Forge doesn't discover JVM properly on OS X
by Tair Sabirgaliev (JIRA)
[ https://issues.jboss.org/browse/FORGE-1596?page=com.atlassian.jira.plugin... ]
Tair Sabirgaliev updated FORGE-1596:
------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/forge/core/pull/389
> Forge doesn't discover JVM properly on OS X
> -------------------------------------------
>
> Key: FORGE-1596
> URL: https://issues.jboss.org/browse/FORGE-1596
> Project: Forge
> Issue Type: Enhancement
> Components: UI - Shell
> Affects Versions: 2.0.0.Final
> Environment: OS X / Mavericks, with both java 1.6 and 1.7 installed
> Reporter: Tair Sabirgaliev
> Priority: Trivial
>
> When running a fresh Forge 2.0.0.Final CLI, I observer this:
> {code}
> $ forge
> Using Forge at /Users/tair/forge-distribution-2.0.0.Final
> Error: a Java 1.7 or higher JRE is required to run Forge; found [/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/java -version == java version "1.6.0_65"
> Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
> Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)].
> {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, 1 month
[JBoss JIRA] (FORGE-1596) Forge doesn't discover JVM properly on OS X
by Tair Sabirgaliev (JIRA)
Tair Sabirgaliev created FORGE-1596:
---------------------------------------
Summary: Forge doesn't discover JVM properly on OS X
Key: FORGE-1596
URL: https://issues.jboss.org/browse/FORGE-1596
Project: Forge
Issue Type: Enhancement
Components: UI - Shell
Affects Versions: 2.0.0.Final
Environment: OS X / Mavericks, with both java 1.6 and 1.7 installed
Reporter: Tair Sabirgaliev
Priority: Trivial
When running a fresh Forge 2.0.0.Final CLI, I observer this:
{code}
$ forge
Using Forge at /Users/tair/forge-distribution-2.0.0.Final
Error: a Java 1.7 or higher JRE is required to run Forge; found [/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/java -version == java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)].
{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, 1 month