[JBoss JIRA] (FORGE-884) EntityWidgetBuilderTest is failing
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-884?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-884.
---------------------------------
> EntityWidgetBuilderTest is failing
> ----------------------------------
>
> Key: FORGE-884
> URL: https://issues.jboss.org/browse/FORGE-884
> Project: Forge
> Issue Type: Bug
> Components: Scaffold
> Reporter: George Gastaldi
> Assignee: Vineet Reynolds
> Priority: Blocker
> Fix For: 1.2.4.Final
>
>
> The following test fails:
> {code:java}
> org.jboss.forge.scaffold.faces.metawidget.widgetbuilder.EntityWidgetBuilderTest
> testExpandOneToOne(org.jboss.forge.scaffold.faces.metawidget.widgetbuilder.EntityWidgetBuilderTest)
> junit.framework.ComparisonFailure: null expected:<...:outputText id="item[Name" value="#{_item.name}"/></h:link></h:column><h:column><f:facet name="header"><h:outputText value="Description"/></f:facet><h:link outcome="/entityWidgetBuilderTest$FooOneToOne/view"><f:param name="id" value="#{_item.id}"/><h:outputText id="itemDescription" value="#{_item.description}]"/></h:link></h:colu...> but was:<...:outputText id="item[BarName" value="_item.bar.name"/></h:link></h:column><h:column><f:facet name="header"><h:outputText value="Description"/></f:facet><h:link outcome="/entityWidgetBuilderTest$FooOneToOne/view"><f:param name="id" value="#{_item.id}"/><h:outputText id="itemBarDescription" value="_item.bar.description]"/></h:link></h:colu...>
> at junit.framework.Assert.assertEquals(Assert.java:81)
> at junit.framework.Assert.assertEquals(Assert.java:87)
> at org.jboss.forge.scaffold.faces.metawidget.widgetbuilder.EntityWidgetBuilderTest.testExpandOneToOne(EntityWidgetBuilderTest.java:431)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:232)
> at junit.framework.TestSuite.run(TestSuite.java:227)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> {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, 11 months
[JBoss JIRA] (FORGE-884) EntityWidgetBuilderTest is failing
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-884?page=com.atlassian.jira.plugin.... ]
Vineet Reynolds resolved FORGE-884.
-----------------------------------
Resolution: Done
Pushed upstream https://github.com/forge/core/commit/d582898ff
And tested manually as well, to ensure that FORGE-872 is not broken. This bunch of tests needs to be revised IMHO.
> EntityWidgetBuilderTest is failing
> ----------------------------------
>
> Key: FORGE-884
> URL: https://issues.jboss.org/browse/FORGE-884
> Project: Forge
> Issue Type: Bug
> Components: Scaffold
> Reporter: George Gastaldi
> Assignee: Vineet Reynolds
> Priority: Blocker
> Fix For: 1.2.4.Final
>
>
> The following test fails:
> {code:java}
> org.jboss.forge.scaffold.faces.metawidget.widgetbuilder.EntityWidgetBuilderTest
> testExpandOneToOne(org.jboss.forge.scaffold.faces.metawidget.widgetbuilder.EntityWidgetBuilderTest)
> junit.framework.ComparisonFailure: null expected:<...:outputText id="item[Name" value="#{_item.name}"/></h:link></h:column><h:column><f:facet name="header"><h:outputText value="Description"/></f:facet><h:link outcome="/entityWidgetBuilderTest$FooOneToOne/view"><f:param name="id" value="#{_item.id}"/><h:outputText id="itemDescription" value="#{_item.description}]"/></h:link></h:colu...> but was:<...:outputText id="item[BarName" value="_item.bar.name"/></h:link></h:column><h:column><f:facet name="header"><h:outputText value="Description"/></f:facet><h:link outcome="/entityWidgetBuilderTest$FooOneToOne/view"><f:param name="id" value="#{_item.id}"/><h:outputText id="itemBarDescription" value="_item.bar.description]"/></h:link></h:colu...>
> at junit.framework.Assert.assertEquals(Assert.java:81)
> at junit.framework.Assert.assertEquals(Assert.java:87)
> at org.jboss.forge.scaffold.faces.metawidget.widgetbuilder.EntityWidgetBuilderTest.testExpandOneToOne(EntityWidgetBuilderTest.java:431)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:232)
> at junit.framework.TestSuite.run(TestSuite.java:227)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> {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, 11 months
[JBoss JIRA] (FORGE-565) Persistence plugin needs to better guide users through a custom database configuration
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-565?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III commented on FORGE-565:
------------------------------------------
I dunno. Some folks recently had confusion about it in the Forums. We could probably still improve. Also warning people when the persistence.xml needs further configuration.
> Persistence plugin needs to better guide users through a custom database configuration
> --------------------------------------------------------------------------------------
>
> Key: FORGE-565
> URL: https://issues.jboss.org/browse/FORGE-565
> Project: Forge
> Issue Type: Enhancement
> Components: Builtin Plugins
> Affects Versions: 1.0.4.Final
> Reporter: Lincoln Baxter III
> Priority: Minor
> Labels: Starter
> Fix For: 1.2.4.Final
>
>
> In order to use the PostgreSQL (or any custom) database, you'll need to skip the --container JBOSS_AS7 parameter; otherwise, this will override the data-source configuration as seen in the INFO messages:
> {code}***INFO*** Setting transaction-type="JTA"
> ***INFO*** Using example data source [java:jboss/datasources/ExampleDS]{code}
> We should probably make this more clear, or perhaps create a warning or error scenario instead of INFO. When you remove the --container parameter.
> It should be much clearer that you may need to use some of the extended parameters like --jndiName and so forth.
> This can probably be done by updating the PersistencePlugin and related classes:
> https://github.com/forge/core/blob/master/javaee-impl/src/main/java/org/j...
--
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, 11 months
[JBoss JIRA] (FORGE-565) Persistence plugin needs to better guide users through a custom database configuration
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-565?page=com.atlassian.jira.plugin.... ]
George Gastaldi commented on FORGE-565:
---------------------------------------
Isn't this issue already fixed ?
> Persistence plugin needs to better guide users through a custom database configuration
> --------------------------------------------------------------------------------------
>
> Key: FORGE-565
> URL: https://issues.jboss.org/browse/FORGE-565
> Project: Forge
> Issue Type: Enhancement
> Components: Builtin Plugins
> Affects Versions: 1.0.4.Final
> Reporter: Lincoln Baxter III
> Priority: Minor
> Labels: Starter
> Fix For: 1.2.4.Final
>
>
> In order to use the PostgreSQL (or any custom) database, you'll need to skip the --container JBOSS_AS7 parameter; otherwise, this will override the data-source configuration as seen in the INFO messages:
> {code}***INFO*** Setting transaction-type="JTA"
> ***INFO*** Using example data source [java:jboss/datasources/ExampleDS]{code}
> We should probably make this more clear, or perhaps create a warning or error scenario instead of INFO. When you remove the --container parameter.
> It should be much clearer that you may need to use some of the extended parameters like --jndiName and so forth.
> This can probably be done by updating the PersistencePlugin and related classes:
> https://github.com/forge/core/blob/master/javaee-impl/src/main/java/org/j...
--
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, 11 months
[JBoss JIRA] (FORGE-167) Add support for ProfileBuilder in MavenCoreFacet (or create MavenProfileFacet)
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-167?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-167.
---------------------------------
Fix Version/s: (was: 1.2.4.Final)
Resolution: Won't Fix
Not needed, as the Maven model already provides this feature (as illustrated by the code in the description)
> Add support for ProfileBuilder in MavenCoreFacet (or create MavenProfileFacet)
> ------------------------------------------------------------------------------
>
> Key: FORGE-167
> URL: https://issues.jboss.org/browse/FORGE-167
> Project: Forge
> Issue Type: Enhancement
> Components: Maven Integration
> Affects Versions: 1.0.0.Beta2
> Reporter: Lincoln Baxter III
> Assignee: Paul Bakker
> Priority: Minor
> Labels: Starter
>
> {code} MavenPluginFacet mavenPluginFacet = getProject().getFacet(MavenPluginFacet.class);
> int nrOfPlugins = getNumberOfPlugins();
> MavenPluginBuilder plugin = MavenPluginBuilder.create()
> .setDependency(
> DependencyBuilder.create()
> .setGroupId("org.apache.maven.plugins")
> .setArtifactId("maven-site-plugin")
> .setVersion("3.0")
> );
> MavenPluginAdapter mvnPlugin = new MavenPluginAdapter(plugin);
> MavenCoreFacet facet = project.getFacet(MavenCoreFacet.class);
> Profile profile = new Profile();
> profile.setId(profileId);
> profile.getBuild().addPlugin(theplugin);
>
> Model pom = facet.getPOM();
> pom.addProfile(profile);
>
> facet.setPOM(pom);
> {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, 11 months