[JBoss JIRA] (FORGE-876) Cannot @Inject UIInput<FileResource<?>> input; Deployment exception results.
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-876?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III commented on FORGE-876:
------------------------------------------
The origin/FORGE-876 branch reproduces this bug.
Or the following test-case:
{code}
/*
* Copyright 2012 Red Hat, Inc. and/or its affiliates.
*
* Licensed under the Eclipse Public License version 1.0, available at
* http://www.eclipse.org/legal/epl-v10.html
*/
package org.jboss.forge.ui.impl;
import javax.inject.Inject;
…
[View More]
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit.Arquillian;
import org.jboss.forge.arquillian.Addon;
import org.jboss.forge.arquillian.Dependencies;
import org.jboss.forge.arquillian.archive.ForgeArchive;
import org.jboss.forge.container.addons.AddonId;
import org.jboss.forge.container.repositories.AddonDependencyEntry;
import org.jboss.forge.resource.FileResource;
import org.jboss.forge.ui.input.UIInput;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.junit.Assert;
import org.junit.Test;
import org.junit.runner.RunWith;
@RunWith(Arquillian.class)
public class UIInputResourceInjectionTest
{
@Deployment
@Dependencies({ @Addon(name = "org.jboss.forge:ui", version = "2.0.0-SNAPSHOT"),
@Addon(name = "org.jboss.forge:resources", version = "2.0.0-SNAPSHOT") })
public static ForgeArchive getDeployment()
{
ForgeArchive archive = ShrinkWrap
.create(ForgeArchive.class)
.addBeansXML()
.addAsAddonDependencies(
AddonDependencyEntry.create(AddonId.from("org.jboss.forge:ui", "2.0.0-SNAPSHOT")),
AddonDependencyEntry.create(AddonId.from("org.jboss.forge:resources", "2.0.0-SNAPSHOT")));
return archive;
}
@Inject
UIInput<FileResource<?>> firstName;
@Test
public void testInjectionNotNull()
{
Assert.assertNotNull(firstName);
}
@Test
public void testInputValues()
{
Assert.assertEquals("firstName", firstName.getName());
Assert.assertEquals(FileResource.class, firstName.getValueType());
}
}
{code}
> Cannot @Inject UIInput<FileResource<?>> input; Deployment exception results.
> ----------------------------------------------------------------------------
>
> Key: FORGE-876
> URL: https://issues.jboss.org/browse/FORGE-876
> Project: Forge
> Issue Type: Story
> Components: Container, Plugin API
> Affects Versions: 2.0.0.Alpha2
> Reporter: Lincoln Baxter III
> Fix For: 2.0.0.Alpha4
>
>
> {code}
> org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [UIInput<FileResource<Object>>] with qualifiers [@Service] at injection point [[BackedAnnotatedField] @Inject org.jboss.forge.ui.impl.UIInputResourceInjectionTest.firstName]
> at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:403)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:325)
> at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:177)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:208)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:519)
> at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:505)
> at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:480)
> at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:536)
> at org.jboss.weld.bootstrap.api.helpers.ForwardingBootstrap.validateBeans(ForwardingBootstrap.java:75)
> at org.jboss.weld.environment.se.Weld.initialize(Weld.java:138)
> at org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup.call(AddonRunnable.java:171)
> at org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup.call(AddonRunnable.java:133)
> at org.jboss.forge.container.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.container.impl.AddonRunnable$3.call(AddonRunnable.java:106)
> at org.jboss.forge.container.impl.AddonRunnable$3.call(AddonRunnable.java:98)
> at org.jboss.forge.container.LockManagerImpl.performLocked(LockManagerImpl.java:48)
> at org.jboss.forge.container.impl.AddonRunnable.run(AddonRunnable.java:97)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:680)
> {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
[View Less]
11 years, 11 months
[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ]
George Gastaldi commented on FORGE-877:
---------------------------------------
As from [~fbricon]:
{quote}
<fbricon> gastaldi: there's an eclipse (not m2e) limitation that says if a project is located directly in the workspace folder, then the project name must match the project folder name
{quote}
If you create the structure outside the workspace, all projects are successfully imported
…
[View More]
> Addon sub-module is not imported into eclipse workspace
> -------------------------------------------------------
>
> Key: FORGE-877
> URL: https://issues.jboss.org/browse/FORGE-877
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.0.0.Alpha3
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 2.0.0.Alpha4
>
>
> When a new forge addon is created using the "New Project" addon, and the option "Split project" is chosen, the addon submodule is not imported
--
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
[View Less]
11 years, 11 months
[JBoss JIRA] (FORGE-253) Forge should provide development profiles API for datasources and other configs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-253?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-253:
----------------------------------
Fix Version/s: 2.0.0.Alpha4
(was: 2.0.0.Alpha3)
> Forge should provide development profiles API for datasources and other configs
> -------------------------------------------------------------------------------
>
> Key: FORGE-253
> URL: https://issues.jboss.org/…
[View More]browse/FORGE-253
> Project: Forge
> Issue Type: Feature Request
> Components: Plugin API
> Affects Versions: 1.0.0.Alpha3
> Reporter: Lincoln Baxter III
> Fix For: 2.0.0.Alpha4
>
>
> lincolnthree
> It gives you what is in persistence.xml
> 11:22
> maxandersen
> it wasn't there a jbossworld
> 11:22
> lincolnthree
> that's been there from the beginning
> 11:22
> maxandersen
> yes - persistence.xml says datasources
> nothing about the actual connection info
> 11:23
> lincolnthree
> oh right
> well
> connection info is stored on the server
> forge doesn't know that
> unless it's in the persistence.xml
> 11:23
> maxandersen
> lincolnthree: exaactly - but it has to know that eventually.
> 11:23
> lincolnthree
> as properties
> 11:23
> maxandersen
> lincolnthree: it wont be
> lincolnthree: this is why tools like rails, hibernate tools and others have notion of "profiles" or simply just property overrides for use at design time and for use at runtime
--
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
[View Less]
11 years, 11 months
[JBoss JIRA] (FORGE-186) Allow decoration/interception of Plugin output
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-186?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-186:
----------------------------------
Fix Version/s: 2.0.0.Alpha4
(was: 2.0.0.Alpha3)
> Allow decoration/interception of Plugin output
> ----------------------------------------------
>
> Key: FORGE-186
> URL: https://issues.jboss.org/browse/FORGE-186
> Project: Forge
> Issue …
[View More]Type: Feature Request
> Components: Plugin API, Usability
> Affects Versions: 1.0.6.Final
> Reporter: Jonathan Fuerth
> Priority: Minor
> Fix For: 2.0.0.Alpha4
>
>
> The Java syntax highlighting in cat & less output is wonderful. As much as we all (don't) love XML, there's still a lot of it to deal with in Java EE projects. Syntax highlighting can help.
> Allowing decoration of plugin output would be a major win for extensibility and modularity here. Allowing individual plugins to separate concerns based on runtime conditions. (E.g, what type of resource is in scope.)
--
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
[View Less]
11 years, 11 months
[JBoss JIRA] (FORGE-212) Classload dependencies of current project when performing certain operations
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-212?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-212:
----------------------------------
Fix Version/s: 2.0.0.Alpha4
(was: 2.0.0.Alpha3)
> Classload dependencies of current project when performing certain operations
> -----------------------------------------------------------------------------
>
> Key: FORGE-212
> URL: https://issues.jboss.org/browse/…
[View More]FORGE-212
> Project: Forge
> Issue Type: Feature Request
> Components: Maven Integration, Parsers / File Manipulation, Plugin API
> Affects Versions: 1.0.0.Alpha3
> Reporter: wiktorowski maximilien
> Priority: Minor
> Fix For: 2.0.0.Alpha4
>
>
> "Generating crud views for entities located into an external jar is a use case i'd like to see implemented in forge.
> In my case i have a model.jar containing my entities and an admin.war generated with seam forge. I'd like to use from-entity to generate scaffolding views in admin.war for the entities located in model.jar"
> This means that Forge will need to classload dependencies of the target project in order to perform reflection-based generation. This may also require a reflection-based meta-model such as what was done with Errai/GWT.
--
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
[View Less]
11 years, 11 months