[
https://issues.jboss.org/browse/FORGE-728?page=com.atlassian.jira.plugin....
]
Robert Dalgleish commented on FORGE-728:
----------------------------------------
I googled the value for the persistence provider. I entered an incorrect value for the
container ("JBOSS") and it prompted me for one of several JBOSS instances. The
TAB technique I also found mentioned in a google result.
I had started with Forge 1.1.1, and that may have been the problem. I upgraded to 1.1.3
with no success. Removing ~/.forge directory seems to have fixed the problem. Thank you.
No proxy.
I despair at software that is completely missing documentation, meaning that google is my
only recourse. Try doing "help persistence" and see what I mean.
I am only trying out the software because in a year, I have to consider how to upgrade a
Seam 2 project to run in a JBoss AS7/Seam 3/JBoss Forge world. So far, my trepidations
have not been allayed.
Documentation for Getting Started omits crucial details
-------------------------------------------------------
Key: FORGE-728
URL:
https://issues.jboss.org/browse/FORGE-728
Project: Forge
Issue Type: Bug
Components: Documentation
Reporter: Robert Dalgleish
The documentation in
http://forge.jboss.org/docs/using/basic-javaee-app.html omits
critical details.
1) In section "Set up persistence (JPA)", useful values for "{your JPA
implementation}" and "{your container}" are not provided. From slopping
around, I found that "HIBERNATE" and "JBOSS" worked.
2) While trying to follow section "Deploy/undeploy to AS7", issuing the command
"forge install-plugin jboss-as-7" yields the error:
***ERROR*** Exception encountered: no default repository set: (to set, type: set
DEFAULT_PLUGIN_REPO <repository>) (type "set VERBOSE true" to enable stack
traces)
At one point in the documentation, I founnd what the value of <repository> should
be, namely
https://raw.github.com/forge/plugin-repository/master/repository.yaml --
however, I don't think this is the correct value, as the command then proceeded to
mangle the value, changing the .yaml to yaml.yaml
--
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