September 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-559) Add support for listing or navigating the contents of a jar file

by Dan Allen (JIRA)

Dan Allen created FORGE-559: ------------------------------- Summary: Add support for listing or navigating the contents of a jar file Key: FORGE-559 URL: https://issues.jboss.org/browse/FORGE-559 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 1.0.3.Final Reporter: Dan Allen Priority: Minor Currently it's possible to step into a jar file. {code} [project] project $ cd sample.jar [project] sample.jar $ {code} However, an attempt to use ls to list the contents results in this error: {code} ***ERROR*** [ls] Plugin is not usable in current scope or project. {code} I would expect it to list the contents of the jar file: {code} META-INF/ META-INF/MANIFEST.MF org/ org/arquillian/ org/arquillian/example/ org/arquillian/example/MySimpleBean.class META-INF/forge.xml META-INF/beans.xml {code} If ls should only list the top-level files and directory, then I would expect find to display the contents recursively. If neither of those make sense, then the command "list" may be appropriate. I would expect that I can continue to navigate and cat files inside the jar file as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
7
0 / 0

[JBoss JIRA] (FORGE-583) Include Forge JavaDoc in Distribution download.

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-583: ---------------------------------------- Summary: Include Forge JavaDoc in Distribution download. Key: FORGE-583 URL: https://issues.jboss.org/browse/FORGE-583 Project: Forge Issue Type: Task Components: Documentation, Forge Build Affects Versions: 1.0.5.Final Reporter: Lincoln Baxter III The Forge API JavaDocs should be included in the Forge Distribution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
14
0 / 0

[JBoss JIRA] (FORGE-575) Upgrade Maven Integration APIs to 3.0.4

by George Gastaldi (JIRA)

George Gastaldi created FORGE-575: ------------------------------------- Summary: Upgrade Maven Integration APIs to 3.0.4 Key: FORGE-575 URL: https://issues.jboss.org/browse/FORGE-575 Project: Forge Issue Type: Library Upgrade Reporter: George Gastaldi Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
3
0 / 0

[JBoss JIRA] (FORGE-630) Remove Solder from Forge

by George Gastaldi (JIRA)

George Gastaldi created FORGE-630: ------------------------------------- Summary: Remove Solder from Forge Key: FORGE-630 URL: https://issues.jboss.org/browse/FORGE-630 Project: Forge Issue Type: Patch Reporter: George Gastaldi Solder features should be integrated in Forge and the dependency should be removed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
4
0 / 0

[JBoss JIRA] (FORGE-534) Separate forge core from built in plugins - resulting in a basic shell

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-534: ---------------------------------------- Summary: Separate forge core from built in plugins - resulting in a basic shell Key: FORGE-534 URL: https://issues.jboss.org/browse/FORGE-534 Project: Forge Issue Type: Feature Request Components: Shell Reporter: Lincoln Baxter III Fix For: 2.0.0.Alpha1 Forge should be completely de-coupled from the built-in plugins, and runnable as a standalone shell with plugin support. This means that the "Current Project" construct will need to be moved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] (FORGE-364) Allow Plugins to Reference Facets from other Plugins

by Lincoln Baxter III (Created) (JIRA)

Allow Plugins to Reference Facets from other Plugins ---------------------------------------------------- Key: FORGE-364 URL: https://issues.jboss.org/browse/FORGE-364 Project: Forge Issue Type: Enhancement Components: Shell Affects Versions: 1.0.0.Beta3 Reporter: Lincoln Baxter III Assignee: Lincoln Baxter III Currently, it is impossible to reference Facets defined in a separate plugin, due to Modularity constraints. We need a way to expose this information between plugins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-289) Scan plugins for potential problematic dependencies

by Paul Bakker (JIRA)

Scan plugins for potential problematic dependencies --------------------------------------------------- Key: SEAMFORGE-289 URL: https://issues.jboss.org/browse/SEAMFORGE-289 Project: Seam Forge Issue Type: Enhancement Components: Plugin API Reporter: Paul Bakker Due to JBM some dependencies can brake Forge. Most problems have to do with the way Weld currently works. If a class is reimported that is used by the core Weld sees two classes for a injection point. If the cdi api is imported as a compile scoped dependency, this will brake injection in the plugin all together. Forge should scan for these kind of dependencies. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
2
0 / 0

[JBoss JIRA] (FORGE-542) Create service provider plugin

by George Gastaldi (JIRA)

George Gastaldi created FORGE-542: ------------------------------------- Summary: Create service provider plugin Key: FORGE-542 URL: https://issues.jboss.org/browse/FORGE-542 Project: Forge Issue Type: Feature Request Reporter: George Gastaldi Create a plugin to create a new ServiceLoader service registration in META-INF/services, based on an interface and class implementation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
4
0 / 0

[JBoss JIRA] (FORGE-604) Add support for Java EE 6 Full Profile

by Christopher Volk (JIRA)

Christopher Volk created FORGE-604: -------------------------------------- Summary: Add support for Java EE 6 Full Profile Key: FORGE-604 URL: https://issues.jboss.org/browse/FORGE-604 Project: Forge Issue Type: Task Components: Java EE APIs Affects Versions: 1.0.5.Final Environment: All Reporter: Christopher Volk Fix For: Future Add support for Java EE 6 Full profile, including multi-module support (cli/maven/ear) and EAR packaging. The EAR packaging should be fairly "easy" to implement. The maven side of multi-module should be similarly "easy". CLI multi-module support is something I would expect to take up most of this effort. I believe this to be a critical feature - serious enterprise software requires Full Profile, and Forge would be even more useful for bootstrapping and developing against the Full Profile than even the Web Profile. I know that almost all the apps I work on professionally require Full Profile. This would be a real home run, IMHO, especially in the wake of JBoss AS7.1's Full Profile Compliance :-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] (FORGE-564) Allow multiple @Alias for a plugin

by George Gastaldi (JIRA)

George Gastaldi created FORGE-564: ------------------------------------- Summary: Allow multiple @Alias for a plugin Key: FORGE-564 URL: https://issues.jboss.org/browse/FORGE-564 Project: Forge Issue Type: Enhancement Reporter: George Gastaldi A plugin could have multiple alias. For example, the Help plugin could be invoked by "help" or "?". This issue may be solved by: - Changing the @Alias value() method to return a String[]; - As Dan suggested,introduce an @Aliases annotation that accepts a collection of @Alias annotations. this reads nicer and leaves the door open for per-alias customizations if we should need them. The second approach looks nicer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2012