February 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2220) IntelliJIdea plugin: UX issues

by Vaclav Tunka (JIRA)

[ https://issues.jboss.org/browse/FORGE-2220?page=com.atlassian.jira.plugin... ] Vaclav Tunka updated FORGE-2220: -------------------------------- Description: When you use latest forge in latest IDEA, there are bad focuses on forms. For example, when I create Enum using Forge, the focus is not on Enum's name, but on some other field. Also if I hit enter to create the Enum, the default action is to cancel the form. So I need to shift the focus to Create button manualy using tab or mouse and then hit Space, as Enter is always bound to Cancel button. Could you please have a look at other dialogs as well and fix the default focus? (was: When you use latest forge in latest IDEA, there are bad focuses on forms. For example, when I create Enum using Forge, the focus is not on Enum's name, but on some other field. Also if I hit enter to create the Enum, the default action is to cancel the form. So I need to shift the focus to Create button manualy using tab or mouse. Could you please have a look at other dialogs as well and fix the default focus?) > IntelliJIdea plugin: UX issues > ------------------------------ > > Key: FORGE-2220 > URL: https://issues.jboss.org/browse/FORGE-2220 > Project: Forge > Issue Type: Bug > Components: UI - IntelliJ IDEA > Reporter: Vaclav Tunka > > When you use latest forge in latest IDEA, there are bad focuses on forms. For example, when I create Enum using Forge, the focus is not on Enum's name, but on some other field. Also if I hit enter to create the Enum, the default action is to cancel the form. So I need to shift the focus to Create button manualy using tab or mouse and then hit Space, as Enter is always bound to Cancel button. Could you please have a look at other dialogs as well and fix the default focus? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2220) IntelliJIdea plugin: UX issues

by Vaclav Tunka (JIRA)

Vaclav Tunka created FORGE-2220: ----------------------------------- Summary: IntelliJIdea plugin: UX issues Key: FORGE-2220 URL: https://issues.jboss.org/browse/FORGE-2220 Project: Forge Issue Type: Bug Components: UI - IntelliJ IDEA Reporter: Vaclav Tunka When you use latest forge in latest IDEA, there are bad focuses on forms. For example, when I create Enum using Forge, the focus is not on Enum's name, but on some other field. Also if I hit enter to create the Enum, the default action is to cancel the form. So I need to shift the focus to Create button manualy using tab or mouse. Could you please have a look at other dialogs as well and fix the default focus? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2219) Problem with NonSnapshotDependencyFilter activation criteria

by ludovic Bertin (JIRA)

ludovic Bertin created FORGE-2219: ------------------------------------- Summary: Problem with NonSnapshotDependencyFilter activation criteria Key: FORGE-2219 URL: https://issues.jboss.org/browse/FORGE-2219 Project: Forge Issue Type: Bug Components: Dependencies Affects Versions: 2.14.0.Final Environment: All Reporter: ludovic Bertin Priority: Minor Use case DependencyBuilder lastOfficialParent = DependencyBuilder.create("myGroupId:myArtifact:::pom"); List foundParentVersions = dependencyFacet.resolveAvailableVersions(lastOfficialParent); Results Only released versions are returned, because NonSnapshotDependencyFilter activation is checking nullity of version and not empty String -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2217) Migrate from Aether to Maven public API

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2217?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2217: ---------------------------------------- See FORGE-2218 for a solution > Migrate from Aether to Maven public API > --------------------------------------- > > Key: FORGE-2217 > URL: https://issues.jboss.org/browse/FORGE-2217 > Project: Forge > Issue Type: Component Upgrade > Components: Build Tools - Maven > Affects Versions: 2.14.0.Final > Reporter: Lincoln Baxter III > Fix For: 2.14.1.Final > > > See: https://github.com/jboss-switchyard/tools/pull/377/files > Related to FORGE-2184 > [~fbricon] - Do you have any information about how we might do this? Can Forge even replace the following code with this higher level Maven API? Does it allow us to customize the resolution process? > Our custom stuff is here: > https://github.com/forge/furnace/blob/master/manager/resolver/maven/src/m... > And here: > https://github.com/forge/core/blob/master/maven/impl/src/main/java/org/jb... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2218) Mojos should run in an isolated classloader

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2218: -------------------------------------- Summary: Mojos should run in an isolated classloader Key: FORGE-2218 URL: https://issues.jboss.org/browse/FORGE-2218 Project: Forge Issue Type: Enhancement Components: Build Tools - Maven, Furnace (Container) Affects Versions: 2.14.0.Final Reporter: George Gastaldi Fix For: 2.x Future The AddonInstallMojo runs in the same classloader as Maven. The problem lies when the Maven version used to run the plugin uses a different API version than Furnace, for example Aether 0.9.0 and Aether 1.0. Since Classworlds (the mechanism using in Maven to "isolate" classes in mojos) does not load Aether classes, the code should be compatible with the running Maven version, otherwise class structure errors will be thrown and the execution will fail. One solution is to start Furnace, deploy the addon-manager addon and lookup services instead of instantiating {{AddonManagerImpl}}. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2217) Migrate from Aether to Maven public API

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2217?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-2217. ------------------------------------- Resolution: Won't Fix While this would fix the problem, given that the Maven APis don't appear to support the functionality we need, we will need to solve it another way (if possible, in the Mojo itself, by avoiding the API conflict situation entirely. Not ideal, but... not much choice.) > Migrate from Aether to Maven public API > --------------------------------------- > > Key: FORGE-2217 > URL: https://issues.jboss.org/browse/FORGE-2217 > Project: Forge > Issue Type: Component Upgrade > Components: Build Tools - Maven > Affects Versions: 2.14.0.Final > Reporter: Lincoln Baxter III > Fix For: 2.14.1.Final > > > See: https://github.com/jboss-switchyard/tools/pull/377/files > Related to FORGE-2184 > [~fbricon] - Do you have any information about how we might do this? Can Forge even replace the following code with this higher level Maven API? Does it allow us to customize the resolution process? > Our custom stuff is here: > https://github.com/forge/furnace/blob/master/manager/resolver/maven/src/m... > And here: > https://github.com/forge/core/blob/master/maven/impl/src/main/java/org/jb... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2217) Migrate from Aether to Maven public API

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2217?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-2217: ------------------------------------------- What we are doing is basically this: Collect all dependencies and transitive dependencies of a Coordinate classified by "forge-addon". Do not collect dependency subtrees of the primary artifact that start with an artifact classified as "forge-addon". > Migrate from Aether to Maven public API > --------------------------------------- > > Key: FORGE-2217 > URL: https://issues.jboss.org/browse/FORGE-2217 > Project: Forge > Issue Type: Component Upgrade > Components: Build Tools - Maven > Affects Versions: 2.14.0.Final > Reporter: Lincoln Baxter III > Fix For: 2.14.1.Final > > > See: https://github.com/jboss-switchyard/tools/pull/377/files > Related to FORGE-2184 > [~fbricon] - Do you have any information about how we might do this? Can Forge even replace the following code with this higher level Maven API? Does it allow us to customize the resolution process? > Our custom stuff is here: > https://github.com/forge/furnace/blob/master/manager/resolver/maven/src/m... > And here: > https://github.com/forge/core/blob/master/maven/impl/src/main/java/org/jb... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2217) Migrate from Aether to Maven public API

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2217?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2217: ---------------------------------------- And here: https://github.com/forge/furnace/blob/master/manager/resolver/maven/src/m... > Migrate from Aether to Maven public API > --------------------------------------- > > Key: FORGE-2217 > URL: https://issues.jboss.org/browse/FORGE-2217 > Project: Forge > Issue Type: Component Upgrade > Components: Build Tools - Maven > Affects Versions: 2.14.0.Final > Reporter: Lincoln Baxter III > Fix For: 2.14.1.Final > > > See: https://github.com/jboss-switchyard/tools/pull/377/files > Related to FORGE-2184 > [~fbricon] - Do you have any information about how we might do this? Can Forge even replace the following code with this higher level Maven API? Does it allow us to customize the resolution process? > Our custom stuff is here: > https://github.com/forge/furnace/blob/master/manager/resolver/maven/src/m... > And here: > https://github.com/forge/core/blob/master/maven/impl/src/main/java/org/jb... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2217) Migrate from Aether to Maven public API

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-2217: ----------------------------------------- Summary: Migrate from Aether to Maven public API Key: FORGE-2217 URL: https://issues.jboss.org/browse/FORGE-2217 Project: Forge Issue Type: Component Upgrade Components: Build Tools - Maven Affects Versions: 2.14.0.Final Reporter: Lincoln Baxter III Fix For: 2.14.1.Final See: https://github.com/jboss-switchyard/tools/pull/377/files Related to FORGE-2184 [~fbricon] - Do you have any information about how we might do this? Can Forge even replace the following code with this higher level Maven API? Does it allow us to customize the resolution process? Our custom stuff is here: https://github.com/forge/furnace/blob/master/manager/resolver/maven/src/m... And here: https://github.com/forge/core/blob/master/maven/impl/src/main/java/org/jb... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2216) Forge Tests: WARN if _DEFAULT_ addon contains duplicate classes which are in dependencies, or duplicated classes in dependencies.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2216?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2216: ---------------------------------------- I am a bit unsure if just warning should be the correct approach here. This seems like a programming error and an exception should be thrown instead > Forge Tests: WARN if _DEFAULT_ addon contains duplicate classes which are in dependencies, or duplicated classes in dependencies. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-2216 > URL: https://issues.jboss.org/browse/FORGE-2216 > Project: Forge > Issue Type: Enhancement > Components: Furnace (Container), Test Harness > Affects Versions: 2.14.0.Final > Reporter: Ondrej Zizka > Assignee: George Gastaldi > > If the _DEFAULT_ addon (created by ForgeArchive getDeployment()) contains classes which duplicate those in dependencies (which is very easy to achieve), then various negative side effect may occur - e.g. querying for an @Annotation, or querying a Map with classes as keys, etc etc. > Typically solving these errors is hard work. > Forge, resp. Furnace, should WARN about duplicated classes. Maybe optionally if that would mean scanning all addons (but I assume that is being done anyway). > In other words: > 1) Scan whole _DEFAULT_ addon and for each class, try loading that class by FQCN from each dependency. If found, then WARN about it. > 2) Scan all dependency addons and warn if duplicated FQCN is found. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2015