[JBoss JIRA] (FORGE-801) Support for Transactional Resources
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-801?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-801.
---------------------------------
Fix Version/s: 2.0.0.Alpha13
(was: 2.x Future)
Resolution: Done
Implemented using XADisk
> Support for Transactional Resources
> ------------------------------------
>
> Key: FORGE-801
> URL: https://issues.jboss.org/browse/FORGE-801
> Project: Forge
> Issue Type: Feature Request
> Components: Resources API
> Affects Versions: 1.2.1.Final
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 2.0.0.Alpha13
>
> Attachments: IMG_20130225_215814.jpg, UserGuide_TXFileInJava_v1.0.pdf
>
>
> FileResources should be transactional, that is, allow modification of resources for displaying purposes and allow commit or rollback of changes.
> The implementation could copy the modified file to a temporary folder and when commit is invoked, copy back the contents to the original folder.
> It may be necessary to provide a pointer back to the original file (Properties file next to changed file maybe?).
--
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, 1 month
[JBoss JIRA] (FORGE-385) Current directory is poor default for new-project location when existing project is detected
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-385?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III closed FORGE-385.
------------------------------------
Fix Version/s: 2.0.0.Alpha5
(was: 1.x Future)
Resolution: Done
Fixed in Forge 2. An empty or new directory must now be selected, or overwrite must be specified.
> Current directory is poor default for new-project location when existing project is detected
> --------------------------------------------------------------------------------------------
>
> Key: FORGE-385
> URL: https://issues.jboss.org/browse/FORGE-385
> Project: Forge
> Issue Type: Enhancement
> Components: Builtin Plugins
> Affects Versions: 1.0.0.Beta3
> Reporter: Dan Allen
> Assignee: Lincoln Baxter III
> Priority: Minor
> Labels: Starter
> Fix For: 2.0.0.Alpha5
>
>
> When creating a new project using the new-project command, forge will offer the current directory as the target location if a project with the same name is found.
> {code}
> $ new-project --named example --topLevelPackage org.example
> ***ERROR*** [/home/dallen/example] already contains a project; please use a different folder.
> Where would you like to create the project? [Press ENTER to use the current directory: dallen]
> {code}
> This default is a recipe for disaster. If there is a project in the way, then using the current directory puts that project *in* the project being created. Additionally, if the current directory is $HOME, then the project will get overlaid in a directory which has many other files and directories.
> A better default is to append a number to the end of the project name. For example:
> {code}
> $ new-project --named example --topLevelPackage org.example
> ***ERROR*** [/home/dallen/example] already contains a project; please use a different folder.
> Where would you like to create the project? [Press ENTER to use an alternative directory: example2]
> {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, 1 month
[JBoss JIRA] (FORGE-385) Current directory is poor default for new-project location when existing project is detected
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-385?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III reassigned FORGE-385:
----------------------------------------
Assignee: Lincoln Baxter III
> Current directory is poor default for new-project location when existing project is detected
> --------------------------------------------------------------------------------------------
>
> Key: FORGE-385
> URL: https://issues.jboss.org/browse/FORGE-385
> Project: Forge
> Issue Type: Enhancement
> Components: Builtin Plugins
> Affects Versions: 1.0.0.Beta3
> Reporter: Dan Allen
> Assignee: Lincoln Baxter III
> Priority: Minor
> Labels: Starter
> Fix For: 1.x Future
>
>
> When creating a new project using the new-project command, forge will offer the current directory as the target location if a project with the same name is found.
> {code}
> $ new-project --named example --topLevelPackage org.example
> ***ERROR*** [/home/dallen/example] already contains a project; please use a different folder.
> Where would you like to create the project? [Press ENTER to use the current directory: dallen]
> {code}
> This default is a recipe for disaster. If there is a project in the way, then using the current directory puts that project *in* the project being created. Additionally, if the current directory is $HOME, then the project will get overlaid in a directory which has many other files and directories.
> A better default is to append a number to the end of the project name. For example:
> {code}
> $ new-project --named example --topLevelPackage org.example
> ***ERROR*** [/home/dallen/example] already contains a project; please use a different folder.
> Where would you like to create the project? [Press ENTER to use an alternative directory: example2]
> {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, 1 month
[JBoss JIRA] (FORGEPLUGINS-138) Switchyard service promotion issues
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGEPLUGINS-138?page=com.atlassian.jira.... ]
Lincoln Baxter III moved FORGE-1215 to FORGEPLUGINS-138:
--------------------------------------------------------
Project: Forge Plugins (was: Forge)
Key: FORGEPLUGINS-138 (was: FORGE-1215)
Affects Version/s: (was: 2.0.0.Alpha12)
Component/s: Switchyard Plugin
(was: Plugin API)
> Switchyard service promotion issues
> -----------------------------------
>
> Key: FORGEPLUGINS-138
> URL: https://issues.jboss.org/browse/FORGEPLUGINS-138
> Project: Forge Plugins
> Issue Type: Bug
> Components: Switchyard Plugin
> Environment: Fedora 16
> java 1.7.0
> maven 3.1.0
> Reporter: R Searls
> Attachments: service-promotion_Alpha12.zip
>
>
> This issue is in the plugin-switchyard code.
> A created service can not be promoted until the service classes are compiled.
> The underlying code does not see the service until it is compile. There is
> code in the generated switchyard maven project pom.xml to introspect class files.
> The generated XML in the switchyard.xml file of a promoted service is not
> correct. A service element as a direct child of composite element is required,
> but is not generated.
> ------- switchyard.xml contents that is generated for a promoted service -----------
> <?xml version="1.0" encoding="UTF-8"?>
> <switchyard xmlns="urn:switchyard-config:switchyard:1.0">
> <composite xmlns="http://docs.oasis-open.org/ns/opencsa/sca/200912"
> name="myProject"
> targetNamespace="urn:switchyard:application:myProject">
> <component name="SimpleListener">
> <implementation.bean xmlns="urn:switchyard-component-bean:config:1.0"
> class="jbossesb.services.service.SimpleListenerBean"/>
> <service name="SimpleListener">
> <interface.java interface="jbossesb.services.service.SimpleListener"/>
> </service>
> </component>
> </composite>
> </switchyard>
> ------- switchyard.xml contents that is needed for a promoted service --------------
> <?xml version="1.0" encoding="UTF-8"?>
> <switchyard xmlns="urn:switchyard-config:switchyard:1.0">
> <composite xmlns="http://docs.oasis-open.org/ns/opencsa/sca/200912"
> name="myProject"
> targetNamespace="urn:switchyard:application:myProject">
> <service name="SimpleListener" promote="SimpleListener">
> <binding.sca/>
> </service>
> <component name="SimpleListener">
> <implementation.bean xmlns="urn:switchyard-component-bean:config:1.0"
> class="jbossesb.services.service.SimpleListenerBean"/>
> <service name="SimpleListener">
> <interface.java interface="jbossesb.services.service.SimpleListener"/>
> </service>
> </component>
> </composite>
> </switchyard>
--
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, 1 month
[JBoss JIRA] (FORGE-286) Forge needs a de-centralized plugin distribution and repository system
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-286?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III closed FORGE-286.
------------------------------------
Fix Version/s: 2.0.0.Alpha1
(was: 1.x Future)
Resolution: Done
This has been solved via Furnace Manager. The Repository will be implemented as part of the Forge 2 website launch.
> Forge needs a de-centralized plugin distribution and repository system
> ----------------------------------------------------------------------
>
> Key: FORGE-286
> URL: https://issues.jboss.org/browse/FORGE-286
> Project: Forge
> Issue Type: Feature Request
> Components: Brainstorming, Plugin API
> Affects Versions: 1.0.0.Alpha1
> Environment: All
> Reporter: Lincoln Baxter III
> Assignee: Lincoln Baxter III
> Priority: Critical
> Labels: Maven
> Fix For: 2.0.0.Alpha1
>
>
> There is no disputing the value of this type of feature, as has been shown with App-stores of all kinds. This would be relatively simple to implement as a Maven-based system, delegating all of the artifact resolution and dependency management to Maven.
> Features Forge would need to provide:
> 1) Built-in plugins and native APIs to search/install/remove/update plug-ins (easy using forge Resource APIs + Aether to add/remove JARs.) This internal plugin/commands could be called "forge" for simplicity
> ------------------------------------------------------------------------------------------
> $ forge plugin-find prettyfaces
> Forge found the following plugins in specified repositories: <--- notice the 'forgeplugin' classifier used to identify forge plugins from other artifacts.
> * http://ocpsoft.com/repository ...... [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:[... 3.1.0, 3.2.0, 3.2.1]
> * http://repo1.maven.org/ .............. [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:3.1.0
> $ forge plugin-install prettyfaces --version 3.1.0
> ***SUCCESS*** [prettyfaces] plugin was successfully installed. You will need to restart forge to see these changes.
> $ forge plugin-list
> Listing installed plugins:
> * prettyfaces [3.1.0]
> * forge-scaffold [1.0.0.Alpha1]
> * forge-javaee6 [1.0.0.Alpha1]
> * home-control [1.0.0.Alpha1]
> $ forge plugin-remove prettyfaces
> Are you sure you you want to remove the plugin(s) [prettyfaces] [Y,n]? Y
> ***SUCCESS*** [prettyfaces] plugin was successfully removed. You will need to restart forge to see these changes.
> ------------------------------------------------------------------------------------------
> 2) Plugin repository management (add/remove/edit/list current plugin repository targets.)
> ------------------------------------------------------------------------------------------
> $ forge repo-list
> Currently using the following plugin repositories:
> * 1. https://repository.jboss.org/nexus/content/groups/public/
> * 2. http://ocpsoft.com/repository
> * 3. http://example.com/forge/plugin-repository
> $ forge repo-add http://jboss.org/forge/repository/ <-- These two will be KEY, we NEED THESE to happen
> $ forge repo-add http://javaee.org/forge/repository/
> $ forge repo-list
> Currently using the following plugin repositories:
> * 1. https://repository.jboss.org/nexus/content/groups/public/
> * 2. http://ocpsoft.com/repository
> * 3. http://example.com/forge/plugin-repository
> * 4. http://jboss.org/forge/repository/
> * 5. http://javaee.org/forge/repository/
> $ forge repo-del 5
> ***SUCCESS*** removed repository [http://javaee.org/forge/repository/]. Plugins installed from this repository will no longer be auto-updated, and can be removed using [forge plugin-remove {plugin-id}]
> ------------------------------------------------------------------------------------------
> 3) Auto-update functionality
> Periodically search for updates to existing plugins (or search on request) - ask users if they would like to see a list of updates or perform an automated update / update individual plugins.
> 4) A meta-data system of identifying compatible versions of plugins w/running version of forge.
> Possibly need to create a maven packaging type and build plugin in order to facilitate this type of additional metadata and artifact resolution. (Or could require a <classifier>forgeplugin</classifier>. We already have the maven GAV (GroupId : ArtifactId : Version) information. Supplemented with this classifier, we could easily identify forge plugins from other artifacts in maven.
--
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, 1 month
[JBoss JIRA] (FORGE-286) Forge needs a de-centralized plugin distribution and repository system
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-286?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III reassigned FORGE-286:
----------------------------------------
Assignee: Lincoln Baxter III
> Forge needs a de-centralized plugin distribution and repository system
> ----------------------------------------------------------------------
>
> Key: FORGE-286
> URL: https://issues.jboss.org/browse/FORGE-286
> Project: Forge
> Issue Type: Feature Request
> Components: Brainstorming, Plugin API
> Affects Versions: 1.0.0.Alpha1
> Environment: All
> Reporter: Lincoln Baxter III
> Assignee: Lincoln Baxter III
> Priority: Critical
> Labels: Maven
> Fix For: 1.x Future
>
>
> There is no disputing the value of this type of feature, as has been shown with App-stores of all kinds. This would be relatively simple to implement as a Maven-based system, delegating all of the artifact resolution and dependency management to Maven.
> Features Forge would need to provide:
> 1) Built-in plugins and native APIs to search/install/remove/update plug-ins (easy using forge Resource APIs + Aether to add/remove JARs.) This internal plugin/commands could be called "forge" for simplicity
> ------------------------------------------------------------------------------------------
> $ forge plugin-find prettyfaces
> Forge found the following plugins in specified repositories: <--- notice the 'forgeplugin' classifier used to identify forge plugins from other artifacts.
> * http://ocpsoft.com/repository ...... [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:[... 3.1.0, 3.2.0, 3.2.1]
> * http://repo1.maven.org/ .............. [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:3.1.0
> $ forge plugin-install prettyfaces --version 3.1.0
> ***SUCCESS*** [prettyfaces] plugin was successfully installed. You will need to restart forge to see these changes.
> $ forge plugin-list
> Listing installed plugins:
> * prettyfaces [3.1.0]
> * forge-scaffold [1.0.0.Alpha1]
> * forge-javaee6 [1.0.0.Alpha1]
> * home-control [1.0.0.Alpha1]
> $ forge plugin-remove prettyfaces
> Are you sure you you want to remove the plugin(s) [prettyfaces] [Y,n]? Y
> ***SUCCESS*** [prettyfaces] plugin was successfully removed. You will need to restart forge to see these changes.
> ------------------------------------------------------------------------------------------
> 2) Plugin repository management (add/remove/edit/list current plugin repository targets.)
> ------------------------------------------------------------------------------------------
> $ forge repo-list
> Currently using the following plugin repositories:
> * 1. https://repository.jboss.org/nexus/content/groups/public/
> * 2. http://ocpsoft.com/repository
> * 3. http://example.com/forge/plugin-repository
> $ forge repo-add http://jboss.org/forge/repository/ <-- These two will be KEY, we NEED THESE to happen
> $ forge repo-add http://javaee.org/forge/repository/
> $ forge repo-list
> Currently using the following plugin repositories:
> * 1. https://repository.jboss.org/nexus/content/groups/public/
> * 2. http://ocpsoft.com/repository
> * 3. http://example.com/forge/plugin-repository
> * 4. http://jboss.org/forge/repository/
> * 5. http://javaee.org/forge/repository/
> $ forge repo-del 5
> ***SUCCESS*** removed repository [http://javaee.org/forge/repository/]. Plugins installed from this repository will no longer be auto-updated, and can be removed using [forge plugin-remove {plugin-id}]
> ------------------------------------------------------------------------------------------
> 3) Auto-update functionality
> Periodically search for updates to existing plugins (or search on request) - ask users if they would like to see a list of updates or perform an automated update / update individual plugins.
> 4) A meta-data system of identifying compatible versions of plugins w/running version of forge.
> Possibly need to create a maven packaging type and build plugin in order to facilitate this type of additional metadata and artifact resolution. (Or could require a <classifier>forgeplugin</classifier>. We already have the maven GAV (GroupId : ArtifactId : Version) information. Supplemented with this classifier, we could easily identify forge plugins from other artifacts in maven.
--
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, 1 month
[JBoss JIRA] (FORGE-1238) Unable to build plugins - unable to find org/eclipse/osgi/3.6.0.v20100517/osgi-3.6.0.v20100517.pom
by David Beer (JIRA)
[ https://issues.jboss.org/browse/FORGE-1238?page=com.atlassian.jira.plugin... ]
David Beer commented on FORGE-1238:
-----------------------------------
It seems that there is something odd about using artifactory, a clean install on localhost and point maven to that and it insists on trying to download the osgi-3.6 artifact however if I use the maven repo everything builds and installs fine. It is almost as if artifactory is trying to download all versions. I also wonder if it is bintray repository that artifactory now adds.
> Unable to build plugins - unable to find org/eclipse/osgi/3.6.0.v20100517/osgi-3.6.0.v20100517.pom
> --------------------------------------------------------------------------------------------------
>
> Key: FORGE-1238
> URL: https://issues.jboss.org/browse/FORGE-1238
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.4.1.Final
> Environment: Linux, based system.
> Reporter: David Beer
> Assignee: Lincoln Baxter III
>
> Maven is unable to resolve the following artifact org/eclipse/osgi/3.6.0.v20100517/osgi-3.6.0.v20100517.pom
> on further investigation it seems the groupid which declares the artifact is wrong. It is declared as org.eclipse yet should be org.eclipse.osgi.
> This means I can't download and build any plugins.
--
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, 1 month