[JBoss JIRA] (FORGE-583) Include Forge JavaDoc in Distribution download.
by Ivan St. Ivanov (JIRA)
[ https://issues.jboss.org/browse/FORGE-583?page=com.atlassian.jira.plugin.... ]
Ivan St. Ivanov updated FORGE-583:
----------------------------------
Status: Pull Request Sent (was: Pull Request Sent)
Git Pull Request: https://github.com/forge/core/pull/235, https://github.com/forge/core/pull/240, https://github.com/forge/core/pull/282, https://github.com/forge/core/pull/304, https://github.com/forge/core/pull/322 (was: https://github.com/forge/core/pull/235, https://github.com/forge/core/pull/240, https://github.com/forge/core/pull/282, https://github.com/forge/core/pull/304)
> 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
> Assignee: Ivan St. Ivanov
> Labels: starter
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (FORGE-811) MavenPlugin: Add maven plugin
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-811?page=com.atlassian.jira.plugin.... ]
George Gastaldi commented on FORGE-811:
---------------------------------------
Be sure to use the org.jboss.forge.maven.plugins.MavenPluginInstaller class, as described in FORGE-862
> MavenPlugin: Add maven plugin
> -----------------------------
>
> Key: FORGE-811
> URL: https://issues.jboss.org/browse/FORGE-811
> Project: Forge
> Issue Type: Feature Request
> Components: Maven Integration
> Affects Versions: 1.2.1.Final
> Reporter: George Gastaldi
> Labels: starter
>
> The MavenPlugin could have a command to add Maven plugins to the current project's pom.xml
> Syntax could be something like:
> {code}
> maven add-plugin groupId:artifactId:version
> {code}
> version is optional and may be prompted if not specified.
--
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
12 years, 10 months
[JBoss JIRA] (FORGE-811) MavenPlugin: Add maven plugin
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-811?page=com.atlassian.jira.plugin.... ]
George Gastaldi commented on FORGE-811:
---------------------------------------
Here are the skeleton methods to be added to MavenPlugin:
{code}
@Command("add-plugin")
public void addPlugin(
@Option(description = "dependency identifier of plugin, ex: \"org.jboss.forge:forge-maven-plugin:1.0.0.Final\"",
required = true) final Dependency gav,
final PipeOut out)
{
}
@Command("add-managed-plugin")
public void addManagedPlugin(
@Option(description = "dependency identifier of plugin, ex: \"org.jboss.forge:forge-maven-plugin:1.0.0.Final\"",
required = true) final Dependency gav,
final PipeOut out)
{
}
{code}
> MavenPlugin: Add maven plugin
> -----------------------------
>
> Key: FORGE-811
> URL: https://issues.jboss.org/browse/FORGE-811
> Project: Forge
> Issue Type: Feature Request
> Components: Maven Integration
> Affects Versions: 1.2.1.Final
> Reporter: George Gastaldi
> Labels: starter
>
> The MavenPlugin could have a command to add Maven plugins to the current project's pom.xml
> Syntax could be something like:
> {code}
> maven add-plugin groupId:artifactId:version
> {code}
> version is optional and may be prompted if not specified.
--
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
12 years, 10 months
[JBoss JIRA] (FORGE-924) It is not possible to set default values for incoming prompts or respond for prompts automatically in forge scripts.
by Ãbner Oliveira (JIRA)
Ãbner Oliveira created FORGE-924:
-------------------------------------
Summary: It is not possible to set default values for incoming prompts or respond for prompts automatically in forge scripts.
Key: FORGE-924
URL: https://issues.jboss.org/browse/FORGE-924
Project: Forge
Issue Type: Feature Request
Components: Forge Scripting Language
Affects Versions: 1.3.0.Final
Reporter: Ãbner Oliveira
I'm writing a script to server as a start point to a trainning session in my company. I had some problems because some plugins hava prompts for select versions and there is no way to automatize the process.
I asked for solution in the #forge channel and one solution was expose the queueInputLines in some way.
The simplest solution is change the plugins to expose arguments in the commands to allow set the default value for incoming prompts.
--
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
12 years, 10 months
[JBoss JIRA] (FORGE-920) Enhancements for JPA setup + new entity
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-920?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-920.
---------------------------------
Resolution: Partially Completed
Now JPA Setup is shown only when a project is in context
> Enhancements for JPA setup + new entity
> ---------------------------------------
>
> Key: FORGE-920
> URL: https://issues.jboss.org/browse/FORGE-920
> Project: Forge
> Issue Type: Enhancement
> Affects Versions: 2.0.0.Alpha4
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 2.0.0.Alpha5
>
>
> {quote}
> <lincolnthree> the command should create a completely valid (with package declaration) java class, but it should be created directly in the target folder
> ...
> <lincolnthree> gastaldi: precisely, but if you are working on a project, does it default the value of targetDir to the full path of where the source will be created?
> <lincolnthree> e.g: src/main/java/org/example/
> <gastaldi> it should be
> <lincolnthree> ok trying
> <lincolnthree> 1 sec
> <lincolnthree> it doesn't
> <gastaldi> it defaults to the selection you made before running the Wizard
> <gastaldi> no ?
> <gastaldi> let me see
> <lincolnthree> it defaults to the selection, yes
> <lincolnthree> but if you are selected in a project
> <lincolnthree> it should use the FULL path to the correct location of the class
> <lincolnthree> using the project JavaSourceFacet to get the proper location
> ...
> <lincolnthree> just use context.getInitialSelection() to find the nearest project in the hierarchy
> <lincolnthree> also, make sure the command is disabled in the menu isEnabled() == false if no project is found
> <lincolnthree> i think that will be enough for now
> {quote}
--
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
12 years, 10 months