[JBoss JIRA] (FORGE-1381) Being able to clear parts of the generated code (or all the project)
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1381?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1381:
-------------------------------------
Summary: Being able to clear parts of the generated code (or all the project) (was: Being able to clear parts or all project)
> Being able to clear parts of the generated code (or all the project)
> --------------------------------------------------------------------
>
> Key: FORGE-1381
> URL: https://issues.jboss.org/browse/FORGE-1381
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta3
> Reporter: Antonio Goncalves
>
> When prototyping using a Forge script, sometimes I would like to have a command that would delete parts of a project (or everything) from dependencies in the {{pom.xml}} to source code. Something like :
> {code}
> jpa-clear # deletes the code of the entities and the JPA dependencies
> jsf-clear # deletes the backing bean and pages
> ...
> project-clear # deletes everything (source code, and pom dependencies) leaving empty directories and artifactId and groupId
> {code}
> And then I would be able to start again from scratch without leaving the CLI.
--
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
[JBoss JIRA] (FORGE-1382) MavenPluginFacet does not get plugin dependencies
by Max Barkley (JIRA)
[ https://issues.jboss.org/browse/FORGE-1382?page=com.atlassian.jira.plugin... ]
Max Barkley commented on FORGE-1382:
------------------------------------
Hi George,
I've fixed the errors in the reproducer so that it compiles and runs. I hope that helps!
Cheers.
> MavenPluginFacet does not get plugin dependencies
> -------------------------------------------------
>
> Key: FORGE-1382
> URL: https://issues.jboss.org/browse/FORGE-1382
> Project: Forge
> Issue Type: Bug
> Components: Plugin API
> Affects Versions: 1.4.3.Final
> Reporter: Max Barkley
> Priority: Minor
>
> The constructor {{MavenPluginAdapter(org.apache.maven.model.Plugin)}} does not copy dependencies from its argument. Consequently, calling {{MavenPluginFacet.getPlugin(org.jboss.forge.project.dependencies.Dependency)}} retrieves a plugin with no dependencies regardless of the actual pom configuration.
--
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
[JBoss JIRA] (FORGE-1382) MavenPluginFacet does not get plugin dependencies
by Max Barkley (JIRA)
[ https://issues.jboss.org/browse/FORGE-1382?page=com.atlassian.jira.plugin... ]
Max Barkley updated FORGE-1382:
-------------------------------
Steps to Reproduce:
Running this with junit should reproduce the problem:
{code}
import static org.junit.Assert.*;
import org.jboss.forge.maven.MavenPluginFacet;
import org.jboss.forge.maven.plugins.MavenPluginBuilder;
import org.jboss.forge.project.Project;
import org.jboss.forge.project.dependencies.Dependency;
import org.jboss.forge.project.dependencies.DependencyBuilder;
import org.jboss.forge.test.AbstractShellTest;
import org.junit.Test;
public class Reproducer extends AbstractShellTest {
@Test
public void testPluginDependencyRetrieval() throws Exception {
// Setup
Project project = initializeJavaProject();
MavenPluginFacet pluginFacet = project.getFacet(MavenPluginFacet.class);
Dependency pluginArtifact = DependencyBuilder.create("maven-compiler-plugin");
Dependency dependency = DependencyBuilder.create("org.jboss.errai:errai-common:2.4.3.Final");
// Add plugin
pluginFacet.addPlugin(MavenPluginBuilder.create().setDependency(DependencyBuilder.create(pluginArtifact)).addPluginDependency(dependency));
// This will fail
assertFalse(pluginFacet.getPlugin(pluginArtifact).getDirectDependencies().isEmpty());
}
}
{code}
was:
Running this with junit should reproduce the problem:
{code}
public class Reproducer extends AbstractShellTest {
@Test
public void testPluginDependencyRetrieval() throws Exception {
// Setup
Project project = initializeJavaProject();
MavenPluginFacet pluginFacet = project.getFacet(MavenPluginFacet.class);
Dependency pluginArtifact = DependencyBuilder.create("maven-compiler-plugin");
Dependency dependency = DependencyBuilder.create("org.jboss.errai:errai-common:2.4.3.Final");
// Add plugin
pluginFacet.addPlugin(PluginBuilder.create(pluginArtifact).addPluginDependency(dependency));
// This will fail
assertFalse(pluginFacet.getPlugin(pluginArtifact).getDirectDependencies().isEmpty());
}
}
{code}
> MavenPluginFacet does not get plugin dependencies
> -------------------------------------------------
>
> Key: FORGE-1382
> URL: https://issues.jboss.org/browse/FORGE-1382
> Project: Forge
> Issue Type: Bug
> Components: Plugin API
> Affects Versions: 1.4.3.Final
> Reporter: Max Barkley
> Priority: Minor
>
> The constructor {{MavenPluginAdapter(org.apache.maven.model.Plugin)}} does not copy dependencies from its argument. Consequently, calling {{MavenPluginFacet.getPlugin(org.jboss.forge.project.dependencies.Dependency)}} retrieves a plugin with no dependencies regardless of the actual pom configuration.
--
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
[JBoss JIRA] (FORGE-1384) forge2: add description text & example panels to "Forge Run Command" dialog
by Gavin Flower (JIRA)
Gavin Flower created FORGE-1384:
-----------------------------------
Summary: forge2: add description text & example panels to "Forge Run Command" dialog
Key: FORGE-1384
URL: https://issues.jboss.org/browse/FORGE-1384
Project: Forge
Issue Type: Feature Request
Components: UI - Eclipse
Affects Versions: 2.0.0.Beta3
Environment: Linux
Reporter: Gavin Flower
There is currently a tooltip, but it does not add really add much to what could be gained from the command name!
It might be a good idea to have a variable sized scrollable text panel in the bottom half to give a more detailed explanation. As a suitable explanation might range from a single sentence to several paragraphs (in the later case, the first para should be short summary that might be enough to more experienced people). It is important to explain why & when you would want to use the command, as well as what it does. Probably a good idea to say what files it creates and/or modifies...
Plus a second panel for examples, the examples may be in a tree structure, when there is more than one available. Each example would have:
(1) short descriptive name
(2) brief description of what it sets out to achieve and how
(3) the example code itself, along with appropriate comments
An unexpanded leaf will have (1) & as much of (2) as can fit on the rest of the line. When a leaf is expanded then the full detail will be available. In rare cases you might need several levels to group related examples together.
The target audience will consist of people who are totally new to Forge and to JEE, to those people with considerable related experience, as well as experienced developers from other areas (For example I started with FORTRAN & COBOL over 40 years ago, and have been doing Java for over 10 years, but relatively inexperienced in JEE).
--
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
[JBoss JIRA] (FORGEPLUGINS-113) Create an Apache Cordova plugin
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGEPLUGINS-113?page=com.atlassian.jira.... ]
Vineet Reynolds commented on FORGEPLUGINS-113:
----------------------------------------------
APK packaging type support is no longer needed. With the Hybrid Mobile project (Cordova) tooling in JBDS 7.1, this is no longer needed. Also Cordova 3 moved to a unified project structure, to align with the W3C Packaged Webapps specification (http://www.w3.org/TR/widgets/), and thus APK project support can no longer be treated as a dependency.
We however need to introduce a "Nothing" buildsystem in Forge 2, and provide a Cordova addon.
> Create an Apache Cordova plugin
> -------------------------------
>
> Key: FORGEPLUGINS-113
> URL: https://issues.jboss.org/browse/FORGEPLUGINS-113
> Project: Forge Plugins
> Issue Type: Feature Request
> Reporter: Vineet Reynolds
>
> This is to create an Apache Cordova/PhoneGap plugin.
> Special consideration needs to be given to integration with the build system, since Forge projects are Maven projects. Also, location of the artifacts like the 'www' assets need to be considered as well.
--
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
[JBoss JIRA] (FORGE-1382) MavenPluginFacet does not get plugin dependencies
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1382?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1382:
----------------------------------------
Hi Max,
The above test does not compile . I suppose you meant MavenPluginBuilder instead of PluginBuilder? If so, could you please fix the test case? Pull requests are greatly appreciated too. :)
Thanks
> MavenPluginFacet does not get plugin dependencies
> -------------------------------------------------
>
> Key: FORGE-1382
> URL: https://issues.jboss.org/browse/FORGE-1382
> Project: Forge
> Issue Type: Bug
> Components: Plugin API
> Affects Versions: 1.4.3.Final
> Reporter: Max Barkley
> Priority: Minor
>
> The constructor {{MavenPluginAdapter(org.apache.maven.model.Plugin)}} does not copy dependencies from its argument. Consequently, calling {{MavenPluginFacet.getPlugin(org.jboss.forge.project.dependencies.Dependency)}} retrieves a plugin with no dependencies regardless of the actual pom configuration.
--
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