[JBoss JIRA] (FORGE-747) ForgePlugin list-plugins ignores GREP
by George Gastaldi (JIRA)
George Gastaldi created FORGE-747:
-------------------------------------
Summary: ForgePlugin list-plugins ignores GREP
Key: FORGE-747
URL: https://issues.jboss.org/browse/FORGE-747
Project: Forge
Issue Type: Bug
Components: Builtin Plugins
Affects Versions: 1.1.3.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Fix For: 1.2.0.Final
The grep command is ignored when used with the list-plugins command in ForgePlugin Eg:
{code}
forge list-plugins | grep arquillian
{code}
The list-plugins also should allow filtering values.
--
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
13 years, 3 months
[JBoss JIRA] (FORGE-604) Add support for Java EE 6 Full Profile
by Christopher Volk (JIRA)
[ https://issues.jboss.org/browse/FORGE-604?page=com.atlassian.jira.plugin.... ]
Christopher Volk edited comment on FORGE-604 at 1/12/13 9:49 PM:
-----------------------------------------------------------------
Additional info based on running *Forge 1.1.3.Final* against a new multi-module maven project created in Idea (using JBoss BOMs), and ear packaging.
Things are looking much better based on all the following, very-positive info.
Can start forge in either root or module dir and it sees it as a project
>From root project level:*
- Can build at base project level and sub module level
- Can add a repo
- Can add a dependency
- Can add a managed dependency
*Dependencies and plugins:*
In module dir:
??[myapp] myapp $ cd myapp-web??
- "project add-dependency" will successfully find managed dependencies in parent pom and ask if we want to use it (sweet!)
- listing facets is properly module aware
- "primefaces setup" works if you cd into web module, complains about war vs pom types if run from root proj dir (not bad)
- "persistence setup" works if cd'd into ejb module
*Main thoughts:*
We'd probably need something like:
- EAR module support for things like new-project and --type
- Add multi-module maven support with appropriate sub module setups/poms
- EAR packaging support
- Make "CLI scoping" more module aware
- Should better handle (prevent? auto-cd?) running module-specific (e.g. JSF) plugins/commands at parent pom level
I hope this helps a bit. I'll try to attach a project to play with.
was (Author: cvolk):
Additional info based on running *Forge 1.1.3.Final* against a new multi-module maven project created in Idea (using JBoss BOMs), and ear packaging.
Things are looking much better based on all the following, very-positive info.
Can start forge in either root or module dir and it sees it as a project
>From root project level:*
- Can build at base project level and sub module level
- Can add a repo
- Can add a dependency
- Can add a managed dependency
*Dependencies and plugins:*
In module dir:
$ cd myapp-web
- "project add-dependency" will successfully find managed dependencies in parent pom and ask if we want to use it (sweet!)
- listing facets is properly module aware
- "primefaces setup" works if you cd into web module, complains about war vs pom types if run from root proj dir (not bad)
- "persistence setup" works if cd'd into ejb module
*Main thoughts:*
We'd probably need something like:
- EAR module support for things like new-project and --type
- Add multi-module maven support with appropriate sub module setups/poms
- EAR packaging support
- Make "CLI scoping" more module aware
- Should better handle (prevent? auto-cd?) running module-specific (e.g. JSF) plugins/commands at parent pom level
I hope this helps a bit. I'll try to attach a project to play with.
> Add support for Java EE 6 Full Profile
> --------------------------------------
>
> Key: FORGE-604
> URL: https://issues.jboss.org/browse/FORGE-604
> Project: Forge
> Issue Type: Task
> Components: Java EE APIs
> Affects Versions: 1.0.5.Final
> Environment: All
> Reporter: Christopher Volk
> Fix For: 1.2.0.Final
>
>
> Add support for Java EE 6 Full profile, including multi-module support (cli/maven/ear) and EAR packaging.
> The EAR packaging should be fairly "easy" to implement. The maven side of multi-module should be similarly "easy". CLI multi-module support is something I would expect to take up most of this effort.
> I believe this to be a critical feature - serious enterprise software requires Full Profile, and Forge would be even more useful for bootstrapping and developing against the Full Profile than even the Web Profile. I know that almost all the apps I work on professionally require Full Profile.
> This would be a real home run, IMHO, especially in the wake of JBoss AS7.1's Full Profile Compliance :-)
--
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
13 years, 3 months
[JBoss JIRA] (FORGE-604) Add support for Java EE 6 Full Profile
by Christopher Volk (JIRA)
[ https://issues.jboss.org/browse/FORGE-604?page=com.atlassian.jira.plugin.... ]
Christopher Volk commented on FORGE-604:
----------------------------------------
Additional info based on running *Forge 1.1.3.Final* against a new multi-module maven project created in Idea (using JBoss BOMs), and ear packaging.
Things are looking much better based on all the following, very-positive info.
Can start forge in either root or module dir and it sees it as a project
>From root project level:*
- Can build at base project level and sub module level
- Can add a repo
- Can add a dependency
- Can add a managed dependency
*Dependencies and plugins:*
In module dir:
$ cd myapp-web
- "project add-dependency" will successfully find managed dependencies in parent pom and ask if we want to use it (sweet!)
- listing facets is properly module aware
- "primefaces setup" works if you cd into web module, complains about war vs pom types if run from root proj dir (not bad)
- "persistence setup" works if cd'd into ejb module
*Main thoughts:*
We'd probably need something like:
- EAR module support for things like new-project and --type
- Add multi-module maven support with appropriate sub module setups/poms
- EAR packaging support
- Make "CLI scoping" more module aware
- Should better handle (prevent? auto-cd?) running module-specific (e.g. JSF) plugins/commands at parent pom level
I hope this helps a bit. I'll try to attach a project to play with.
> Add support for Java EE 6 Full Profile
> --------------------------------------
>
> Key: FORGE-604
> URL: https://issues.jboss.org/browse/FORGE-604
> Project: Forge
> Issue Type: Task
> Components: Java EE APIs
> Affects Versions: 1.0.5.Final
> Environment: All
> Reporter: Christopher Volk
> Fix For: 1.2.0.Final
>
>
> Add support for Java EE 6 Full profile, including multi-module support (cli/maven/ear) and EAR packaging.
> The EAR packaging should be fairly "easy" to implement. The maven side of multi-module should be similarly "easy". CLI multi-module support is something I would expect to take up most of this effort.
> I believe this to be a critical feature - serious enterprise software requires Full Profile, and Forge would be even more useful for bootstrapping and developing against the Full Profile than even the Web Profile. I know that almost all the apps I work on professionally require Full Profile.
> This would be a real home run, IMHO, especially in the wake of JBoss AS7.1's Full Profile Compliance :-)
--
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
13 years, 3 months
[JBoss JIRA] (FORGE-745) Can not use Java Parser in war deployment on AS7
by Craig Schwarzwald (JIRA)
Craig Schwarzwald created FORGE-745:
---------------------------------------
Summary: Can not use Java Parser in war deployment on AS7
Key: FORGE-745
URL: https://issues.jboss.org/browse/FORGE-745
Project: Forge
Issue Type: Bug
Components: Parsers / File Manipulation
Affects Versions: 1.1.3.Final
Environment: Ubuntu, AS7
Reporter: Craig Schwarzwald
{code}
package org.ocpsoft.keywords;
import static org.junit.Assert.assertTrue;
import java.io.File;
import java.io.FileOutputStream;
import java.io.PrintStream;
import java.net.URL;
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.drone.api.annotation.Drone;
import org.jboss.arquillian.junit.Arquillian;
import org.jboss.arquillian.test.api.ArquillianResource;
import org.jboss.forge.parser.JavaParser;
import org.jboss.forge.parser.java.JavaClass;
import org.jboss.forge.parser.java.Visibility;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.asset.EmptyAsset;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.jboss.shrinkwrap.resolver.api.DependencyResolvers;
import org.jboss.shrinkwrap.resolver.api.maven.MavenDependencyResolver;
import org.junit.Test;
import org.junit.runner.RunWith;
import com.ocpsoft.constants.InputConstants;
import com.thoughtworks.selenium.DefaultSelenium;
@RunWith(Arquillian.class)
public class ParserExampleTest
{
@Deployment // testable = false to run as a client
public static WebArchive createDeployment() {
MavenDependencyResolver resolver = DependencyResolvers.use(
MavenDependencyResolver.class).loadMetadataFromPom("pom.xml");
return ShrinkWrap.create(WebArchive.class)
.addAsResource("META-INF/persistence.xml")
.addAsLibraries(resolver.artifacts("org.jboss.forge:parser-java-impl")
.resolveAsFiles())
.addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml");
}
@Test
public void testParser() throws InterruptedException {
String className = "ParseTest";
removeClassFile(InputConstants.FILE_LOCATION + className + ".java");
createTestClassViaParser(InputConstants.FILE_LOCATION + className + ".java", className);
}
private void createTestClassViaParser(String testPath, String className) {
JavaClass testClass = JavaParser.create(JavaClass.class);
testClass
.setName(className)
.setPackage("com.example.domain")
.addAnnotation(RunWith.class).setLiteralValue(Arquillian.class.getSimpleName() + ".class")
.getOrigin().addImport(Arquillian.class);
testClass
.addField().setPrivate().setStatic(true).setFinal(true).setType(String.class).setName("WEBAPP_SRC").setLiteralInitializer("\"src/main/webapp\"");
testClass.addMethod()
.setName("getDeployment")
.setStatic(true)
.setVisibility(Visibility.PUBLIC)
.setReturnType(WebArchive.class)
.setBody("return ShrinkWrap.create(WebArchive.class, \"FBTutorialDemo.war\")\n" +
"\t.addAsResource(\"META-INF/persistence.xml\")\n" +
"\t.addAsWebResource(new File(WEBAPP_SRC, \"index.html\"))\n" +
"\t.addAsWebResource(new File(WEBAPP_SRC, \"index2.html\"))\n" +
"\t.addAsWebResource(new File(WEBAPP_SRC, \"myInfo.html\"))\n" +
"\t.addAsWebResource(new File(WEBAPP_SRC, \"friendsInfo.html\"))\n" +
"\t.addAsWebInfResource(EmptyAsset.INSTANCE, \"beans.xml\");")
.addAnnotation(Deployment.class)
.getOrigin().addImport(File.class);
testClass.addImport(WebArchive.class);
testClass.addImport(ShrinkWrap.class);
testClass.addImport(EmptyAsset.class);
testClass
.addField().setType(DefaultSelenium.class)
.setName("browser").addAnnotation(Drone.class)
.getOrigin().addImport(DefaultSelenium.class);
testClass.addImport(Drone.class);
testClass
.addField().setType(URL.class)
.setName("deploymentURL").addAnnotation(ArquillianResource.class)
.getOrigin().addImport(URL.class);
testClass.addImport(ArquillianResource.class);
try{
PrintStream writetoTest = new PrintStream(
new FileOutputStream(testPath));
writetoTest.print(testClass.toString());
writetoTest.close();
}
catch (Exception e) {
System.err.println("Failure in createTestClassViaParser: " + e);
}
}
public void removeClassFile(String filePath){
File classFile = new File(filePath);
try{
if(!classFile.exists()){
System.out.println(filePath + " does NOT exist. Nothing to Remove");
}
else{
if(classFile.delete()){
System.out.println(classFile.getName() + " is deleted!");
}else{
System.out.println("Delete operation is failed.");
assertTrue(false);
}
}
}catch(Exception e){
e.printStackTrace();
}
}
}
{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
13 years, 3 months