June 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-803) Promote usage of ShrinkWrap Resolver instead of using Aether directly

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-803?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-803: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Promote usage of ShrinkWrap Resolver instead of using Aether directly > --------------------------------------------------------------------- > > Key: FORGE-803 > URL: https://issues.jboss.org/browse/FORGE-803 > Project: Forge > Issue Type: Enhancement > Components: Maven Integration > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > Fix For: 2.x Future > > > The MavenDependencyResolver should use ShrinkWrap Resolver APIs instead of using the Aether APIs directly. > This is believed to bring some performance enhancements also, due to internal improvements in the latest version of SWR. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-846) Create a template processor addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-846?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-846: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Create a template processor addon > --------------------------------- > > Key: FORGE-846 > URL: https://issues.jboss.org/browse/FORGE-846 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha2 > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > We need an addon to manipulate templates. This addon will be used in the New Project addon and in the scaffold in a first moment. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-876) Cannot @Inject UIInput<FileResource<?>> input; Deployment exception results.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-876?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-876: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Cannot @Inject UIInput<FileResource<?>> input; Deployment exception results. > ---------------------------------------------------------------------------- > > Key: FORGE-876 > URL: https://issues.jboss.org/browse/FORGE-876 > Project: Forge > Issue Type: Bug > Components: Container, Plugin API > Affects Versions: 2.0.0.Alpha2 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > {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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-886) Should be able to re-install an existing Addon if it is a SNAPSHOT

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-886?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-886: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Should be able to re-install an existing Addon if it is a SNAPSHOT > ------------------------------------------------------------------ > > Key: FORGE-886 > URL: https://issues.jboss.org/browse/FORGE-886 > Project: Forge > Issue Type: Feature Request > Components: Container, Plugin Repository > Affects Versions: 2.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > Currently re-installing Addons is not supported, because there is no way to tell Forge to stop using the existing deployed files without giving it time to detect the change and re-deploy the addon. > In order to implement this, the Forge registry file probably needs to use some kind of marker files. > {code} > .dodeploy > .deployed > .undeployed > {code} > So that it knows how to respond when changes are made faster than timestamps can detect. This would (hopefully) also in theory be a step toward multi JVM (multiple running forge / concurrent modification instance) support. > This has been partially implemented, but only naively. The files are actually re-written on UNIX based OS's, and will be re-loaded next time the addon is disabled/re-enabled, but this will not work on Windows. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-894) Forge DependencyFacet cannot resolve dependencies in reactor projects without first installing necessary dependencies in the local Repository

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-894?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-894: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Forge DependencyFacet cannot resolve dependencies in reactor projects without first installing necessary dependencies in the local Repository > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-894 > URL: https://issues.jboss.org/browse/FORGE-894 > Project: Forge > Issue Type: Bug > Components: Maven Integration > Affects Versions: 2.0.0.Alpha3 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > As the title states, maven project building requests do not resolv reactor project dependencies. > {code} > parent/ > - addon --> spi > - api > - impl > - spi > - tests --> addon > {code} > the tests/ module dependency resolution result does not contain a transitive dependency to the spi/ module, however, when building from maven cli, it clearly should and does have this dependency - so this is a pure tooling issue due to the fact that the addon/ sub-module actually cannot be resolved. > This can be reproduced in the branch: https://github.com/forge/core/tree/FORGE-894 > Running the test: > {code} > Failed tests: testCreateAddonProject(org.jboss.forge.addons.AddonProjectConfiguratorTest): SPI module is not present in the TESTS module > {code} > Relevant code (where the resolution is performed) is here: https://github.com/forge/core/blob/FORGE-894/maven/impl-projects/src/main... -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-922) Forge JavaParser does not support Wildcard Imports "org.jboss.forge.*"

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-922?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-922: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Forge JavaParser does not support Wildcard Imports "org.jboss.forge.*" > ---------------------------------------------------------------------- > > Key: FORGE-922 > URL: https://issues.jboss.org/browse/FORGE-922 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > The JavaParser Annotation.getQualifiedName() will return "Column" instead of "javax.persistence.Column" for the following example class scenario. It should be able to understand the wildcard, given the proper metadata: > {code}package demo.entities; > import javax.persistence.*; > @Entity > public class Contact implements java.io.Serializable { > @Id > private @GeneratedValue(strategy = GenerationType.AUTO) > @Column(name = "id", updatable = false, nullable = false) > Long id = null; > @Version > private @Column(name = "version") > int version = 0; > public Long getId() { > return this.id; > } > public void setId(final Long id) { > this.id = id; > } > public int getVersion() { > return this.version; > } > public void setVersion(final int version) { > this.version = version; > } > @Override > public boolean equals(Object that) { > if (this == that) { > return true; > } > if (that == null) { > return false; > } > if (getClass() != that.getClass()) { > return false; > } > if (id != null) { > return id.equals(((Contact) that).id); > } > return super.equals(that); > } > @Override > public int hashCode() { > if (id != null) { > return id.hashCode(); > } > return super.hashCode(); > } > private String name; > public String getName() { > return this.name; > } > public void setName(final String name) { > this.name = name; > } > public String toString() { > return "" + name; > } > }{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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-896) Different Facets for main and test sources/resources

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-896?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-896: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Different Facets for main and test sources/resources > ---------------------------------------------------- > > Key: FORGE-896 > URL: https://issues.jboss.org/browse/FORGE-896 > Project: Forge > Issue Type: Enhancement > Components: Maven Integration > Affects Versions: 2.0.0.Alpha3 > Reporter: George Gastaldi > Fix For: 2.x Future > > > It should be possible to have a facet to create the src/main/* structure and another facet for src/test/*. > JavaSourceFacet and ResourceFacet should be split into two different interfaces to allow that -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-898) "Install an Addon" command should allow quick-selection of "org.jboss.forge" core addons.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-898?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-898: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > "Install an Addon" command should allow quick-selection of "org.jboss.forge" core addons. > ----------------------------------------------------------------------------------------- > > Key: FORGE-898 > URL: https://issues.jboss.org/browse/FORGE-898 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins, Usability > Affects Versions: 2.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-954) JAVA_PACKAGE_PICKER should enable auto-completion from the project sources directory

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-954?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-954. --------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Alpha5 (was: 2.x Future) Resolution: Done Implemented in Eclipse > JAVA_PACKAGE_PICKER should enable auto-completion from the project sources directory > ------------------------------------------------------------------------------------ > > Key: FORGE-954 > URL: https://issues.jboss.org/browse/FORGE-954 > Project: Forge > Issue Type: Enhancement > Components: UI - Eclipse, UI - IntelliJ IDEA, UI - Shell > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha5 > > > It would be nice if the UIInput with type = JAVA_PACKAGE_PICKER enabled auto-completion from the project sources directory -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-955) Enable package auto-complete in Eclipse for JAVA_PACKAGE_PICKER

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-955?page=com.atlassian.jira.plugin.... ] George Gastaldi deleted FORGE-955: ---------------------------------- > Enable package auto-complete in Eclipse for JAVA_PACKAGE_PICKER > --------------------------------------------------------------- > > Key: FORGE-955 > URL: https://issues.jboss.org/browse/FORGE-955 > Project: Forge > Issue Type: Sub-task > Reporter: George Gastaldi > -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2013