April 2013 - forge-issues - Jboss List Archives

[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 started 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

[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 updated FORGE-847: -------------------------------- Description: 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. was: 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:jave} 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. > 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 James Perkins (JIRA)

James Perkins created FORGE-847: ----------------------------------- Summary: 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:jave} 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-846) Create a template processor addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-846?page=com.atlassian.jira.plugin.... ] George Gastaldi reassigned FORGE-846: ------------------------------------- Assignee: Vineet Reynolds Repository and initial structure created in: https://github.com/forge/templates-addon Notes about design and thoughts: http://forge.etherpad.corp.redhat.com/2 > 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.0.0.Alpha3 > > > 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, 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 edited comment on FORGE-842 at 4/5/13 11:44 AM: --------------------------------------------------------------- What about the plugin "resolution" : {code:xml} <build> <pluginManagement> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>2.0.2</version> <configuration> <source>1.6</source> <target>1.6</target> </configuration> </plugin> </plugins> </pluginManagement> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> </plugin> </plugins> </build> {code} Should the {code:java}mavenPluginFacet.getPlugin(DependencyBuilder.create("org.apache.maven.plugins:maven-compiler-plugin")).getVersion(){code} returns "2.0.2" (currently returns "null"). Or maybe we could implement a getResolvedPlugin() ?? was (Author: charless): What about the plugin "resolution" : {code:xml} <build> <pluginManagement> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>2.0.2</version> <configuration> <source>1.6</source> <target>1.6</target> </configuration> </plugin> </plugins> </pluginManagement> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> </plugin> > 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-846) Create a template processor addon

by George Gastaldi (JIRA)

George Gastaldi created FORGE-846: ------------------------------------- Summary: 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 Fix For: 2.0.0.Alpha3 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, 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 commented on FORGE-842: -------------------------------------- What about the plugin "resolution" : {code:xml} <build> <pluginManagement> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>2.0.2</version> <configuration> <source>1.6</source> <target>1.6</target> </configuration> </plugin> </plugins> </pluginManagement> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> </plugin> > 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-845) Forge 2.0.0.Alpha[12] freezes at banner on Mac OS X

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-845?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-845. --------------------------------- Assignee: George Gastaldi Resolution: Cannot Reproduce Bug The bug never existed. It was a configuration issue by not having aesh installed > Forge 2.0.0.Alpha[12] freezes at banner on Mac OS X > --------------------------------------------------- > > Key: FORGE-845 > URL: https://issues.jboss.org/browse/FORGE-845 > Project: Forge > Issue Type: Bug > Affects Versions: 2.0.0.Alpha2 > Reporter: Tom Cunningham > Assignee: George Gastaldi > Attachments: threaddumps.log > > > Forge seems to freeze at the banner screen on Mac OS X if I use either jdk 1.7.0_09 or jdk 1.6.0_43. > I don't have any similar problems with forge 1.2.2.Final or below, and I've tried removing my .forge directory and I have tried doing it in a directory with no forge projects (empty directory), and I still see a freeze. > bananastand:~ tcunning$ forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 2.0.0.Alpha2 ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] > Attaching a thread dump. -- 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-845) Forge 2.0.0.Alpha[12] freezes at banner on Mac OS X

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-845?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-845: --------------------------------------- Try adding the jboss nexus repo in your settings.xml and enabling it by default. Although the jar should be in the maven central already. > Forge 2.0.0.Alpha[12] freezes at banner on Mac OS X > --------------------------------------------------- > > Key: FORGE-845 > URL: https://issues.jboss.org/browse/FORGE-845 > Project: Forge > Issue Type: Bug > Affects Versions: 2.0.0.Alpha2 > Reporter: Tom Cunningham > Attachments: threaddumps.log > > > Forge seems to freeze at the banner screen on Mac OS X if I use either jdk 1.7.0_09 or jdk 1.6.0_43. > I don't have any similar problems with forge 1.2.2.Final or below, and I've tried removing my .forge directory and I have tried doing it in a directory with no forge projects (empty directory), and I still see a freeze. > bananastand:~ tcunning$ forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 2.0.0.Alpha2 ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] > Attaching a thread dump. -- 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-845) Forge 2.0.0.Alpha[12] freezes at banner on Mac OS X

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/FORGE-845?page=com.atlassian.jira.plugin.... ] Tom Cunningham commented on FORGE-845: -------------------------------------- If I do forge --install aesh, here's what I see : bananastand:~ tcunning$ forge --install aesh java.lang.IllegalArgumentException: No Artifact version found for org.jboss.forge:aesh::: at org.jboss.forge.bootstrap.Bootstrap.install(Bootstrap.java:191) at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:136) at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:91) > Forge 2.0.0.Alpha[12] freezes at banner on Mac OS X > --------------------------------------------------- > > Key: FORGE-845 > URL: https://issues.jboss.org/browse/FORGE-845 > Project: Forge > Issue Type: Bug > Affects Versions: 2.0.0.Alpha2 > Reporter: Tom Cunningham > Attachments: threaddumps.log > > > Forge seems to freeze at the banner screen on Mac OS X if I use either jdk 1.7.0_09 or jdk 1.6.0_43. > I don't have any similar problems with forge 1.2.2.Final or below, and I've tried removing my .forge directory and I have tried doing it in a directory with no forge projects (empty directory), and I still see a freeze. > bananastand:~ tcunning$ forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 2.0.0.Alpha2 ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] > Attaching a thread dump. -- 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