March 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (ROASTER-67) Update the built in eclipse code formatter style to latest eclipse

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-67?page=com.atlassian.jira.plugin... ] George Gastaldi closed ROASTER-67. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.13.1.Final Resolution: Done > Update the built in eclipse code formatter style to latest eclipse > ------------------------------------------------------------------ > > Key: ROASTER-67 > URL: https://issues.jboss.org/browse/ROASTER-67 > Project: Roaster > Issue Type: Enhancement > Components: Formatter > Affects Versions: 2.13.0.Final > Reporter: Claus Ibsen > Assignee: George Gastaldi > Fix For: 2.13.1.Final > > Attachments: Screen Shot 2015-03-23 at 4.49.00 PM.png > > > Using roaster its really annoying that it uses a not common java convention for code style. > eg all the braces are on new lines, which nobody uses. > If you use Eclipse or JBDS then its out of the box settings is on same line. > See attached screenshot -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-35) PostStartup event is not fired for every deployed addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-35?page=com.atlassian.jira.plugin... ] George Gastaldi updated FURNACE-35: ----------------------------------- Fix Version/s: 2.x Future Affects Version/s: 2.15.3.Final Component/s: Container - CDI Runtime > PostStartup event is not fired for every deployed addon > ------------------------------------------------------- > > Key: FURNACE-35 > URL: https://issues.jboss.org/browse/FURNACE-35 > Project: Forge: Furnace > Issue Type: Bug > Components: Container - CDI, Runtime > Affects Versions: 2.15.3.Final > Reporter: Matej Briskar > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-35) PostStartup event is not fired for every deployed addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-35?page=com.atlassian.jira.plugin... ] George Gastaldi moved FORGE-2294 to FURNACE-35: ----------------------------------------------- Project: Forge: Furnace (was: Forge) Key: FURNACE-35 (was: FORGE-2294) > PostStartup event is not fired for every deployed addon > ------------------------------------------------------- > > Key: FURNACE-35 > URL: https://issues.jboss.org/browse/FURNACE-35 > Project: Forge: Furnace > Issue Type: Bug > Reporter: Matej Briskar > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2294) PostStartup event is not fired for every deployed addon

by Matej Briskar (JIRA)

Matej Briskar created FORGE-2294: ------------------------------------ Summary: PostStartup event is not fired for every deployed addon Key: FORGE-2294 URL: https://issues.jboss.org/browse/FORGE-2294 Project: Forge Issue Type: Bug Reporter: Matej Briskar -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2292) ResourcesFacet - A Resource should have API to get the project FQN name

by Claus Ibsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-2292?page=com.atlassian.jira.plugin... ] Claus Ibsen commented on FORGE-2292: ------------------------------------ I was able to strip the absolute prefix and compute the path relative from the resource directory with this code {code} // we only want the relative dir name from the resource directory, eg META-INF/spring/foo.xml String baseDir = facet.getResourceDirectory().getFullyQualifiedName(); String fqn = resource.getFullyQualifiedName(); if (fqn.startsWith(baseDir)) { fqn = fqn.substring(baseDir.length() + 1); } {code} And I have the xml file in META-INF/spring dir. And the completer now works {code} [foo]$ camel-setup^C [foo]$ ls src/main/resources/META-INF/spring foo.xml [foo]$ camel-add-endpoint-xml --xml META-INF/spring/foo.xml {code} > ResourcesFacet - A Resource should have API to get the project FQN name > ----------------------------------------------------------------------- > > Key: FORGE-2292 > URL: https://issues.jboss.org/browse/FORGE-2292 > Project: Forge > Issue Type: Feature Request > Affects Versions: 2.15.2.Final > Reporter: Claus Ibsen > Priority: Minor > > Using the following code to find all Camel xml files in my project > {code} > public XmlFileCompleter(ResourcesFacet facet) { > // find package names in the source code > facet.visitResources(new ResourceVisitor() { > @Override > public void visit(VisitContext context, Resource<?> resource) { > String name = resource.getName(); > if (name.endsWith(".xml")) { > // must contain <camelContext... > boolean camel = resource.getContents().contains("<camelContext"); > if (camel) { > files.add(resource.getName()); > } > } > } > }); > } > {code} > The problem is that I cannot get the FQN package name of the resource. > getName returns the name without any parents - that is okay and would be expected. > getFullyQualifiedName() returns the absolute path on my computer, so its > /opt/jboss-forge/foo/src/main/resources/spring/foo.xml > eg the project is stored in /opt/jboss-forge/foo. So I need an api to give me the java package name of the resource - which in this case would be spring/foo.xml. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-54) Plugin to Database Migration Framework

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-54?page=com.atlassian.jira.p... ] George Gastaldi edited comment on FORGEPLUGINS-54 at 3/23/15 5:07 PM: ---------------------------------------------------------------------- Potential tools/libraries that already work through database upgrades: Liquibase - http://www.liquibase.org/, strongest, mature available tool (based on my research). JPA or integration effort unknown. Used in Grails database migration plugin. Flyway - http://flywaydb.org/, comparatively new, but gaining lot of traction. Used in Spring Roo as add-on (http://code.google.com/p/spring-roo-addon-flyway/) There are others, however these two seem to be the strongest candidate given they already have been used in similar plugin approaches. Personally I have had good experience with liquibase as a standalone database change tool, but never used it tightly coupled with a programming language for domain<->db change management. flyway to liquibase comparison: http://stackoverflow.com/questions/8418814/db-migration-tool-liquibase-or... was (Author: dhartford): Potential tools/libraries that already work through database upgrades: Liquibase - http://www.liquibase.org/, strongest, mature available tool (based on my research). JPA or integration effort unknown. Used in Grails database migration plugin. Flyway - http://code.google.com/p/flyway/, comparatively new, but gaining lot of traction. Used in Spring Roo as add-on (http://code.google.com/p/spring-roo-addon-flyway/) There are others, however these two seem to be the strongest candidate given they already have been used in similar plugin approaches. Personally I have had good experience with liquibase as a standalone database change tool, but never used it tightly coupled with a programming language for domain<->db change management. flyway to liquibase comparison: http://stackoverflow.com/questions/8418814/db-migration-tool-liquibase-or... > Plugin to Database Migration Framework > -------------------------------------- > > Key: FORGEPLUGINS-54 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-54 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Reporter: Mauro Silva > > Recommend idea for adding a database change plugin. The Grails plugin for database changes (http://grails.org/plugin/database-migration) may be good for inspiration, however the Forge version may not necessarily have the tightly coupled support as the Grails/Groovy domain models have, but something that supports JPA would be fabulous. > Although a generic plugin for Liquibase or other database change management support could be useful, it would be left 'up to the developer' on how to use it which seems counter-intuitive to a more RAD-style development environment, per the specific of JPA-based data access (potentially OGM-based JPA as well). > Usecase is for solving how to deploy database structure changes in an automated fashion to ensure the database schema does not go out of sync with the application. > A Plugin like spring-roo-addon-flyway (http://code.google.com/p/spring-roo-addon-flyway/). > Could be other Database Migration API that works better on Jboss ecosystem (I dont know if that is one). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-2) seam-persistence fails with opaque ERROR ArrayIndexOutOfBoundsException when dependency resolution fails

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-2?page=com.atlassian.jira.pl... ] George Gastaldi closed FORGEPLUGINS-2. -------------------------------------- Resolution: Out of Date > seam-persistence fails with opaque ERROR ArrayIndexOutOfBoundsException when dependency resolution fails > -------------------------------------------------------------------------------------------------------- > > Key: FORGEPLUGINS-2 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-2 > Project: Forge Plugins/Addons > Issue Type: Bug > Environment: Seam Forge 1.0.0-SNAPSHOT > Reporter: Thomas Frühbeck > Priority: Minor > > [einsatz] einsatz $ seam-persistence setup > ***ERROR*** [seam-persistence setup] -1 > ??? > [einsatz] einsatz $ set VERBOSE true > [einsatz] einsatz $ seam-persistence setup > ***ERROR*** [seam-persistence setup] -1 > Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 > at java.util.ArrayList.elementData(ArrayList.java:338) > at java.util.ArrayList.get(ArrayList.java:351) > at org.jboss.forge.seam.persistence.SeamPersistencePlugin.installDependencies(SeamPersistencePlugin.java:192) > at org.jboss.forge.seam.persistence.SeamPersistencePlugin.install(SeamPersistencePlugin.java:63) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-1) cannot generate entities from Mysql db using Hibernate Tools plugin

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-1?page=com.atlassian.jira.pl... ] George Gastaldi closed FORGEPLUGINS-1. -------------------------------------- Resolution: Out of Date > cannot generate entities from Mysql db using Hibernate Tools plugin > ------------------------------------------------------------------- > > Key: FORGEPLUGINS-1 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-1 > Project: Forge Plugins/Addons > Issue Type: Bug > Environment: Forge 1.0.0-SNAPSHOT, hibernate tools plugin > Reporter: Tomas Remes > Assignee: Koen Aers > > I am using latest Forge 1.0.0-SNAPSHOT and I am not able to run "generate-entities --dialect org.hibernate.dialect.MySQLDialect --driver com.mysql.jdbc.Driver". Even though I have my mysql connector jar in $FORGE_HOME/lib, it gives me: > Driver class: com.mysql.jdbc.Driver could not be loaded. Check that the driver jar(s) are in $FORGE_HOME/lib. > ***ERROR*** [generate-entities] JDBC Driver class not found: com.mysql.jdbc.Driver -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-11) Package to generate entities into should match <groupId>.model

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-11?page=com.atlassian.jira.p... ] George Gastaldi closed FORGEPLUGINS-11. --------------------------------------- Assignee: George Gastaldi (was: Koen Aers) Resolution: Done This is fixed in Forge 2 > Package to generate entities into should match <groupId>.model > -------------------------------------------------------------- > > Key: FORGEPLUGINS-11 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-11 > Project: Forge Plugins/Addons > Issue Type: Bug > Reporter: Pete Muir > Assignee: George Gastaldi > > By default, this should be the package offered up as a default -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-26) Openshift plugin should allow specification of operation timeout to support other localities

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-26?page=com.atlassian.jira.p... ] George Gastaldi closed FORGEPLUGINS-26. --------------------------------------- Resolution: Won't Fix The Openshift plugin is no longer maintained. See FORGEPLUGINS-148 for more details > Openshift plugin should allow specification of operation timeout to support other localities > --------------------------------------------------------------------------------------------- > > Key: FORGEPLUGINS-26 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-26 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Reporter: Lincoln Baxter III > Assignee: William DeCoste > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2015