July 2011 - forge-dev - Jboss List Archives

by Lincoln Baxter, III

Hey Paul, It seems like we have two orthogonal plugin repositories. I'd like to start using GitHub (have already started) to host the repository for easy adds/updates/etc. Do you think your plugin groups can be incorporated into what we've got going on here? https://raw.github.com/forge/plugin-repository/master/repository.yaml This is where the code lives for the search and installation (you've probably already seen it.) https://github.com/forge/core/blob/master/shell/src/main/java/org/jboss/f... -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

12 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-188) Deploying to OpenShift from Forge

by Lincoln Baxter III (JIRA)

Deploying to OpenShift from Forge --------------------------------- Key: SEAMFORGE-188 URL: https://issues.jboss.org/browse/SEAMFORGE-188 Project: Seam Forge Issue Type: Feature Request Components: Blessed Plugins Affects Versions: 1.0.0.Alpha3 Reporter: Lincoln Baxter III Priority: Minor I think it makes a lot of sense to be able to deploy applications from the very tool with which they were created. This will be a compelling argument to get your foot in the door with both Forge and OpenShift. I'd like to start by deploying a Java EE 6 web-application. We can build out more 'rhq' commands from there. * Register for OpenShift, get a Flex account. * Download Forge, build an app. * Deploy to OpenShift. * Done in 10 minutes. This would provide an OS-agnostic way to interact with OpenShift. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
12
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-258) Deploying to OpenShift Express from Forge

by Max Rydahl Andersen (JIRA)

Deploying to OpenShift Express from Forge ----------------------------------------- Key: SEAMFORGE-258 URL: https://issues.jboss.org/browse/SEAMFORGE-258 Project: Seam Forge Issue Type: Feature Request Reporter: Max Rydahl Andersen similar to the Flex, creating apps and deploy for Express would be useful - actually more interesting since Express is much more about development than Flex is currently. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-241) Need jenkins jobs for blessed plugins on github

by Lincoln Baxter III (JIRA)

Need jenkins jobs for blessed plugins on github ----------------------------------------------- Key: SEAMFORGE-241 URL: https://issues.jboss.org/browse/SEAMFORGE-241 Project: Seam Forge Issue Type: Task Components: Blessed Plugins Reporter: Lincoln Baxter III https://github.com/forge/plugin-* Need hudson jobs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-257) Add ability to alias commands (like bash)

by Lincoln Baxter III (JIRA)

Add ability to alias commands (like bash) ----------------------------------------- Key: SEAMFORGE-257 URL: https://issues.jboss.org/browse/SEAMFORGE-257 Project: Seam Forge Issue Type: Feature Request Components: Shell Affects Versions: 1.0.0.Alpha4 Reporter: Lincoln Baxter III It should be possible to create aliases: {code}$ alias foo="echo bar"{code} Alias by itself should print a list of aliases: {code}$ alias $ foo="echo bar"{code} Aliases should simply be literal translations via regex on the front of any command, should we support embedded aliases? For modifying any part of a command? {code}$ alias foo="bar" $ echo foo bar{code} Etc... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-253) Provide a way for external processes to communicate with Forge

by Koen Aers (JIRA)

Provide a way for external processes to communicate with Forge --------------------------------------------------------------- Key: SEAMFORGE-253 URL: https://issues.jboss.org/browse/SEAMFORGE-253 Project: Seam Forge Issue Type: Feature Request Reporter: Koen Aers For the Eclipse Forge Tools I need to be able to do the following: - ask Forge for the list of available commands in the current context - ask Forge for the plugin/command/option metadata Ideally this should be done by sending Forge a 'meta' command that doesn't get executed but triggers a user provided listener (pretty much like a Forge plugin) that can build and send back the response. I have experimented with a Forge plugin providing this behaviour but of course then this plugin shows up in the list of available commands which I don't want. This plugin had an alias that started with the ansi escape sequence so that its echo was easily detected and handled appropriately. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-256) AS7 deploy plugin should have dist as dependency to prevent requirement for JBOSS_HOME

by Ken Finnigan (JIRA)

AS7 deploy plugin should have dist as dependency to prevent requirement for JBOSS_HOME -------------------------------------------------------------------------------------- Key: SEAMFORGE-256 URL: https://issues.jboss.org/browse/SEAMFORGE-256 Project: Seam Forge Issue Type: Enhancement Components: Blessed Plugins Affects Versions: 1.0.0.Alpha4 Reporter: Ken Finnigan To remove the need for users to specify JBOSS_HOME when running the AS7 deploy plugin on forge you could add the following Maven plugin: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <executions> <execution> <id>unpack-as7</id> <phase>process-test-classes</phase>  <goals> <goal>unpack</goal> </goals> <configuration> <artifactItems> <artifactItem> <groupId>org.jboss.as</groupId> <artifactId>jboss-as-dist</artifactId> <version>7.0.0.Final</version> <type>zip</type> <overWrite>false</overWrite> <outputDirectory>${project.build.directory}</outputDirectory> </artifactItem> </artifactItems> </configuration> </execution> </executions> </plugin> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
3
0 / 0

This is VERY nicely done! I like it :)

by Lincoln Baxter, III

http://vimeo.com/26562733 How do you think we should resolve the JBOSS_HOME requirement issue? Forge config to override system environment? -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

12 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-254) Links on project homepage are out of date

by Fernando Correia (JIRA)

Links on project homepage are out of date ----------------------------------------- Key: SEAMFORGE-254 URL: https://issues.jboss.org/browse/SEAMFORGE-254 Project: Seam Forge Issue Type: Task Components: Documentation Environment: web browser Reporter: Fernando Correia Priority: Minor Many of the links at http://seamframework.org/Documentation/SeamForge are broken. For instance: * Downloads & Releases: Downloads (http://repository.jboss.org/nexus/content/groups/public/org/jboss/forge/) * Snapshots (Maven): Downloads (http://repository.jboss.org/nexus/content/groups/public/org/jboss/forge/) * User's guide (In Progress): (https://docs.jboss.org/author/display/SEAMFORGE/Reference+Guide) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

Re: [forge-dev] Consolidating the Plugin Repositories

by Lincoln Baxter, III

Hey Paul, We already have plugin search capabilities in the forge plugin. Basically I don't think we really need the XML repo because it's so close in functionality to what's already there. I do want to keep the idea of plugin-groups, but maybe tags is the answer there. Just let people provide tags that are searchable along with name and description. Try this out in Forge and you will see what I mean: (You may want to update and build a new snapshot.) $ forge find-plugin * $ forge find-plugin seam :) Thoughts? ~Lincoln On Mon, Jul 18, 2011 at 4:31 PM, Paul Bakker <paul.bakker.nl(a)gmail.com>wrote: > Hi Lincoln, > > Yes that would be a good improvement. > I think it's also good if we put the plugin browsing functionallity in the > forge plugin because now it feels a bit out of place (not sure if you wanted > to do that too). I will rewrite the code in the plugin-repo to use this. > > What library do we use for yaml parsing? > > Paul > > > > On Jul 18, 2011, at 10:11 PM, Lincoln Baxter, III wrote: > > Hey Paul, > > It seems like we have two orthogonal plugin repositories. I'd like to start > using GitHub (have already started) to host the repository for easy > adds/updates/etc. > > Do you think your plugin groups can be incorporated into what we've got > going on here? > https://raw.github.com/forge/plugin-repository/master/repository.yaml > > This is where the code lives for the search and installation (you've > probably already seen it.) > > https://github.com/forge/core/blob/master/shell/src/main/java/org/jboss/f... > > -- > Lincoln Baxter, III > http://ocpsoft.com > http://scrumshark.com > "Keep it Simple" > > > -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

12 years, 9 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-dev July 2011