April 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGEPLUGINS-105) Clean up prompts and plugin in general

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-105?page=com.atlassian.jira.... ] James Perkins updated FORGEPLUGINS-105: --------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/plugin-jboss-as/pull/8 > Clean up prompts and plugin in general > -------------------------------------- > > Key: FORGEPLUGINS-105 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-105 > Project: Forge Plugins > Issue Type: Enhancement > Components: JBoss AS Plugin > Reporter: James Perkins > Assignee: James Perkins > > Most of the prompts are rather confusing and at times reprompt for information that shouldn't be needed. > Think about changing the deploy goals to use the maven plugin and only use the Forge shell for executing commands, starting, stopping, etc. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-847) Add an option to the DependencyResolver to resolve a single artifact (no version range)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-847?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-847: ---------------------------------- Fix Version/s: 1.2.3.Final > Add an option to the DependencyResolver to resolve a single artifact (no version range) > --------------------------------------------------------------------------------------- > > Key: FORGE-847 > URL: https://issues.jboss.org/browse/FORGE-847 > Project: Forge > Issue Type: Feature Request > Components: Maven Integration > Affects Versions: 1.2.2.Final > Reporter: James Perkins > Fix For: 1.2.3.Final > > > Currently {{org.jboss.forge.project.dependencies.DependencyResolver}} only has a option to return a list of dependencies. This results in version range query which requires the repository to have a {{maven-metadata.xml}} file. It would be useful to have something like: > {code:java} > public DependencyResource resolveArtifact(Dependency dependency) > {code} > This would allow for a specific version to be looked up. It also would have better performance when a dependency version is defined. > Currently using a repository that does not have metadata files does not work. For example http://maven.repository.redhat.com/earlyaccess/all/ cannot be used due to this issue. Which means no EAP dependencies cannot be downloaded from a Forge plugin. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-847) Add an option to the DependencyResolver to resolve a single artifact (no version range)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-847?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-847: ---------------------------------- Affects Version/s: 1.2.2.Final > Add an option to the DependencyResolver to resolve a single artifact (no version range) > --------------------------------------------------------------------------------------- > > Key: FORGE-847 > URL: https://issues.jboss.org/browse/FORGE-847 > Project: Forge > Issue Type: Feature Request > Components: Maven Integration > Affects Versions: 1.2.2.Final > Reporter: James Perkins > > Currently {{org.jboss.forge.project.dependencies.DependencyResolver}} only has a option to return a list of dependencies. This results in version range query which requires the repository to have a {{maven-metadata.xml}} file. It would be useful to have something like: > {code:java} > public DependencyResource resolveArtifact(Dependency dependency) > {code} > This would allow for a specific version to be looked up. It also would have better performance when a dependency version is defined. > Currently using a repository that does not have metadata files does not work. For example http://maven.repository.redhat.com/earlyaccess/all/ cannot be used due to this issue. Which means no EAP dependencies cannot be downloaded from a Forge plugin. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-842) Add managed plugin support to MavenPluginFacet

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-842?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-842. --------------------------------- > Add managed plugin support to MavenPluginFacet > ---------------------------------------------- > > Key: FORGE-842 > URL: https://issues.jboss.org/browse/FORGE-842 > Project: Forge > Issue Type: Enhancement > Components: Maven Integration > Affects Versions: 1.2.2.Final > Reporter: charles SALMON > Assignee: charles SALMON > Fix For: 1.2.3.Final > > > Maven offers a way to handle plugins by using the "pluginManagement" feature (similar to the "dependencyManagement" one). > The idea here is to enhance the MavenPluginFacet with the following methods: > {code:java} > List<MavenPlugin> listConfiguredManagedPlugins(); > boolean hasManagedPlugin(Dependency dependency); > MavenPlugin getManagedPlugin(Dependency dependency); > void addManagedPlugin(MavenPlugin plugin); > void removeManagedPlugin(Dependency dependency); > void updateManagedPlugin(final MavenPlugin plugin); > {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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-842) Add managed plugin support to MavenPluginFacet

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-842?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-842: ---------------------------------- Fix Version/s: 1.2.3.Final Affects Version/s: 1.2.2.Final > Add managed plugin support to MavenPluginFacet > ---------------------------------------------- > > Key: FORGE-842 > URL: https://issues.jboss.org/browse/FORGE-842 > Project: Forge > Issue Type: Enhancement > Components: Maven Integration > Affects Versions: 1.2.2.Final > Reporter: charles SALMON > Assignee: charles SALMON > Fix For: 1.2.3.Final > > > Maven offers a way to handle plugins by using the "pluginManagement" feature (similar to the "dependencyManagement" one). > The idea here is to enhance the MavenPluginFacet with the following methods: > {code:java} > List<MavenPlugin> listConfiguredManagedPlugins(); > boolean hasManagedPlugin(Dependency dependency); > MavenPlugin getManagedPlugin(Dependency dependency); > void addManagedPlugin(MavenPlugin plugin); > void removeManagedPlugin(Dependency dependency); > void updateManagedPlugin(final MavenPlugin plugin); > {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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-842) Add managed plugin support to MavenPluginFacet

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-842?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-842: ---------------------------------- Issue Type: Enhancement (was: Story) Workflow: GIT Pull Request workflow (was: jira) Git Pull Request: https://github.com/forge/core/pull/306 > Add managed plugin support to MavenPluginFacet > ---------------------------------------------- > > Key: FORGE-842 > URL: https://issues.jboss.org/browse/FORGE-842 > Project: Forge > Issue Type: Enhancement > Components: Maven Integration > Reporter: charles SALMON > Assignee: charles SALMON > > Maven offers a way to handle plugins by using the "pluginManagement" feature (similar to the "dependencyManagement" one). > The idea here is to enhance the MavenPluginFacet with the following methods: > {code:java} > List<MavenPlugin> listConfiguredManagedPlugins(); > boolean hasManagedPlugin(Dependency dependency); > MavenPlugin getManagedPlugin(Dependency dependency); > void addManagedPlugin(MavenPlugin plugin); > void removeManagedPlugin(Dependency dependency); > void updateManagedPlugin(final MavenPlugin plugin); > {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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-847) Add an option to the DependencyResolver to resolve a single artifact (no version range)

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/FORGE-847?page=com.atlassian.jira.plugin.... ] James Perkins commented on FORGE-847: ------------------------------------- If I can find the time I definitely will. If someone beats me to it that would be great too :-) > Add an option to the DependencyResolver to resolve a single artifact (no version range) > --------------------------------------------------------------------------------------- > > Key: FORGE-847 > URL: https://issues.jboss.org/browse/FORGE-847 > Project: Forge > Issue Type: Feature Request > Components: Maven Integration > Reporter: James Perkins > > Currently {{org.jboss.forge.project.dependencies.DependencyResolver}} only has a option to return a list of dependencies. This results in version range query which requires the repository to have a {{maven-metadata.xml}} file. It would be useful to have something like: > {code:java} > public DependencyResource resolveArtifact(Dependency dependency) > {code} > This would allow for a specific version to be looked up. It also would have better performance when a dependency version is defined. > Currently using a repository that does not have metadata files does not work. For example http://maven.repository.redhat.com/earlyaccess/all/ cannot be used due to this issue. Which means no EAP dependencies cannot be downloaded from a Forge plugin. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-847) Add an option to the DependencyResolver to resolve a single artifact (no version range)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-847?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-847: ------------------------------------------ Good idea. This shouldn't be so hard to do. Feel like taking a shot at it, actually? > Add an option to the DependencyResolver to resolve a single artifact (no version range) > --------------------------------------------------------------------------------------- > > Key: FORGE-847 > URL: https://issues.jboss.org/browse/FORGE-847 > Project: Forge > Issue Type: Feature Request > Components: Maven Integration > Reporter: James Perkins > > Currently {{org.jboss.forge.project.dependencies.DependencyResolver}} only has a option to return a list of dependencies. This results in version range query which requires the repository to have a {{maven-metadata.xml}} file. It would be useful to have something like: > {code:java} > public DependencyResource resolveArtifact(Dependency dependency) > {code} > This would allow for a specific version to be looked up. It also would have better performance when a dependency version is defined. > Currently using a repository that does not have metadata files does not work. For example http://maven.repository.redhat.com/earlyaccess/all/ cannot be used due to this issue. Which means no EAP dependencies cannot be downloaded from a Forge plugin. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-842) Add managed plugin support to MavenPluginFacet

by charles SALMON (JIRA)

[ https://issues.jboss.org/browse/FORGE-842?page=com.atlassian.jira.plugin.... ] charles SALMON resolved FORGE-842. ---------------------------------- Resolution: Done > Add managed plugin support to MavenPluginFacet > ---------------------------------------------- > > Key: FORGE-842 > URL: https://issues.jboss.org/browse/FORGE-842 > Project: Forge > Issue Type: Story > Components: Maven Integration > Reporter: charles SALMON > Assignee: charles SALMON > > Maven offers a way to handle plugins by using the "pluginManagement" feature (similar to the "dependencyManagement" one). > The idea here is to enhance the MavenPluginFacet with the following methods: > {code:java} > List<MavenPlugin> listConfiguredManagedPlugins(); > boolean hasManagedPlugin(Dependency dependency); > MavenPlugin getManagedPlugin(Dependency dependency); > void addManagedPlugin(MavenPlugin plugin); > void removeManagedPlugin(Dependency dependency); > void updateManagedPlugin(final MavenPlugin plugin); > {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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-842) Add managed plugin support to MavenPluginFacet

by charles SALMON (JIRA)

[ https://issues.jboss.org/browse/FORGE-842?page=com.atlassian.jira.plugin.... ] Work on FORGE-842 stopped by charles SALMON. > Add managed plugin support to MavenPluginFacet > ---------------------------------------------- > > Key: FORGE-842 > URL: https://issues.jboss.org/browse/FORGE-842 > Project: Forge > Issue Type: Story > Components: Maven Integration > Reporter: charles SALMON > Assignee: charles SALMON > > Maven offers a way to handle plugins by using the "pluginManagement" feature (similar to the "dependencyManagement" one). > The idea here is to enhance the MavenPluginFacet with the following methods: > {code:java} > List<MavenPlugin> listConfiguredManagedPlugins(); > boolean hasManagedPlugin(Dependency dependency); > MavenPlugin getManagedPlugin(Dependency dependency); > void addManagedPlugin(MavenPlugin plugin); > void removeManagedPlugin(Dependency dependency); > void updateManagedPlugin(final MavenPlugin plugin); > {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, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013