September 2013 - forge-issues - Jboss List Archives

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-896?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reassigned FORGE-896: ---------------------------------------- Assignee: (was: Lincoln Baxter III) > 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: Build Tools - Maven > Affects Versions: 2.0.0.Alpha3 > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha10 > > > 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

10 years, 8 months

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 Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-894?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reassigned FORGE-894: ---------------------------------------- Assignee: (was: Lincoln Baxter III) > 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: Feature Request > Components: Build Tools - Maven > Affects Versions: 2.0.0.Alpha3 > Reporter: Lincoln Baxter III > Labels: difficult > 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

10 years, 8 months

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 Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-894?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-894: ------------------------------------- Issue Type: Feature Request (was: Bug) > 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: Feature Request > Components: Build Tools - Maven > 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

10 years, 8 months

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 Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-894?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-894: ------------------------------------- Labels: difficult (was: ) > 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: Feature Request > Components: Build Tools - Maven > Affects Versions: 2.0.0.Alpha3 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Labels: difficult > 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1160) Support UIInputMany for InputType.FILE_PICKER and DIRECTORY_PICKER

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1160: -------------------------------------- Summary: Support UIInputMany for InputType.FILE_PICKER and DIRECTORY_PICKER Key: FORGE-1160 URL: https://issues.jboss.org/browse/FORGE-1160 Project: Forge Issue Type: Feature Request Components: UI - Eclipse Affects Versions: 2.0.0.Alpha11 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.0.0.Alpha12 -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1159) CLAC fails to resolve indirect interfaces

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1159?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1159. ------------------------------------- Fix Version/s: 2.0.0.Alpha12 (was: 2.x Future) Resolution: Done Done. > CLAC fails to resolve indirect interfaces > ----------------------------------------- > > Key: FORGE-1159 > URL: https://issues.jboss.org/browse/FORGE-1159 > Project: Forge > Issue Type: Bug > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha11 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha12 > > > Given > {code} > public interface ScaffoldSetupWizard extends UIWizard > {code} > and > {code} > public class ScaffoldSetupWizardImpl extends AbstractUICommand implements ScaffoldSetupWizard > {code} > the following test fails: > {code} > Assert.assertTrue(wizard instanceof UIWizard); > {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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1159) CLAC fails to resolve indirect interfaces

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1159?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1159: ----------------------------------------- Assignee: Lincoln Baxter III > CLAC fails to resolve indirect interfaces > ----------------------------------------- > > Key: FORGE-1159 > URL: https://issues.jboss.org/browse/FORGE-1159 > Project: Forge > Issue Type: Bug > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha11 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > Given > {code} > public interface ScaffoldSetupWizard extends UIWizard > {code} > and > {code} > public class ScaffoldSetupWizardImpl extends AbstractUICommand implements ScaffoldSetupWizard > {code} > the following test fails: > {code} > Assert.assertTrue(wizard instanceof UIWizard); > {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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1159) CLAC fails to resolve indirect interfaces

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1159: -------------------------------------- Summary: CLAC fails to resolve indirect interfaces Key: FORGE-1159 URL: https://issues.jboss.org/browse/FORGE-1159 Project: Forge Issue Type: Bug Components: Furnace (Container) Affects Versions: 2.0.0.Alpha11 Reporter: George Gastaldi Fix For: 2.x Future Given {code} public interface ScaffoldSetupWizard extends UIWizard {code} and {code} public class ScaffoldSetupWizardImpl extends AbstractUICommand implements ScaffoldSetupWizard {code} the following test fails: {code} Assert.assertTrue(wizard instanceof UIWizard); {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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1158) Review the MavenFacet for exporting problems like model issues and dependency resolution failures to consumers

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1158?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1158: ----------------------------------- Summary: Review the MavenFacet for exporting problems like model issues and dependency resolution failures to consumers (was: Review the MavenCoreFacet for exporting problems like model issues and dependency resolution failures to consumers) > Review the MavenFacet for exporting problems like model issues and dependency resolution failures to consumers > -------------------------------------------------------------------------------------------------------------- > > Key: FORGE-1158 > URL: https://issues.jboss.org/browse/FORGE-1158 > Project: Forge > Issue Type: Task > Components: Build Tools - Maven > Affects Versions: 1.4.1.Final > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > From FORGE-1133, FORGE-1134 and FORGE-1136, it became imperative to ensure that consumers of the Maven Core facet (or it's equivalent) in Forge 2 should have access to any problems encountered in dependency resolution. > The list of problem includes any problems found in the project's model (like an incorrectly structured POM), but also includes dependency collection and resolution failures. > Not all of the above described problems should necessarily result in exceptions being thrown to consumers of the API. We could change the design of the Facet to do this as part of this task, but that may not be necessary and may not be optimal. > Consumers may also want to access the problems encountered via another API so that they may be better equipped to deal with the failure after inspecting it further. > Discuss (and create sub-tasks). -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1158) Review the MavenCoreFacet for exporting problems like model issues and dependency resolution failures to consumers

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1158: -------------------------------------- Summary: Review the MavenCoreFacet for exporting problems like model issues and dependency resolution failures to consumers Key: FORGE-1158 URL: https://issues.jboss.org/browse/FORGE-1158 Project: Forge Issue Type: Task Components: Build Tools - Maven Affects Versions: 1.4.1.Final Reporter: Vineet Reynolds Fix For: 2.x Future >From FORGE-1133, FORGE-1134 and FORGE-1136, it became imperative to ensure that consumers of the Maven Core facet (or it's equivalent) in Forge 2 should have access to any problems encountered in dependency resolution. The list of problem includes any problems found in the project's model (like an incorrectly structured POM), but also includes dependency collection and resolution failures. Not all of the above described problems should necessarily result in exceptions being thrown to consumers of the API. We could change the design of the Facet to do this as part of this task, but that may not be necessary and may not be optimal. Consumers may also want to access the problems encountered via another API so that they may be better equipped to deal with the failure after inspecting it further. Discuss (and create sub-tasks). -- 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

10 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2013