[JBoss JIRA] (FORGE-1876) Addon services should be exposed through @Produces methods
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1876?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1876.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.6.1.Final
(was: 2.x Future)
Resolution: Done
> Addon services should be exposed through @Produces methods
> -----------------------------------------------------------
>
> Key: FORGE-1876
> URL: https://issues.jboss.org/browse/FORGE-1876
> Project: Forge
> Issue Type: Enhancement
> Components: Furnace CDI
> Affects Versions: 2.6.0.Final
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 2.6.1.Final
>
>
> Having an addon that depends on the furnace-cdi container and declares the following class:
> {code}
> import javax.enterprise.inject.Produces;
> import javax.ws.rs.client.Client;
> import javax.ws.rs.client.ClientBuilder;
> public class RestClientProducer
> {
> @Produces
> public ClientBuilder createClientBuilder()
> {
> ClientBuilder builder = ClientBuilder.newBuilder();
> return builder;
> }
> @Produces
> public Client createClient(ClientBuilder builder)
> {
> return builder.build();
> }
> }
> {code}
> Then:
> - {{WeldServiceRegistry.hasService(javax.ws.rs.client.Client.class)}} should return true
> - {{AddonRegistry.getServices(javax.ws.rs.client.Client.class).get()}} should call the producer method and return the requested service
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (FORGE-1876) Addon services should be exposed through @Produces methods
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1876?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1876:
-----------------------------------
Description:
Having an addon that depends on the furnace-cdi container and declares the following class:
{code}
import javax.enterprise.inject.Produces;
import javax.ws.rs.client.Client;
import javax.ws.rs.client.ClientBuilder;
public class RestClientProducer
{
@Produces
public ClientBuilder createClientBuilder()
{
ClientBuilder builder = ClientBuilder.newBuilder();
return builder;
}
@Produces
public Client createClient(ClientBuilder builder)
{
return builder.build();
}
}
{code}
Then:
- {{WeldServiceRegistry.hasService(javax.ws.rs.client.Client.class)}} should return true
- {{AddonRegistry.getServices(javax.ws.rs.client.Client.class).get()}} should call the producer method and return the requested service
was:
Having an addon that depends on the furnace-cdi container and declares the following class:
{code}
import javax.enterprise.inject.Produces;
import javax.ws.rs.client.Client;
import javax.ws.rs.client.ClientBuilder;
public class RestClientProducer
{
@Produces
public ClientBuilder createClientBuilder()
{
ClientBuilder builder = ClientBuilder.newBuilder();
return builder;
}
@Produces
public Client createClient(ClientBuilder builder)
{
return builder.build();
}
}
{code}
Then:
- {{AddonRegistry.hasService(javax.ws.rs.client.Client.class)}} should return true
- {{AddonRegistry.getServices(javax.ws.rs.client.Client.class).get()}} should call the producer method and return the requested service
> Addon services should be exposed through @Produces methods
> -----------------------------------------------------------
>
> Key: FORGE-1876
> URL: https://issues.jboss.org/browse/FORGE-1876
> Project: Forge
> Issue Type: Enhancement
> Components: Furnace CDI
> Affects Versions: 2.6.0.Final
> Reporter: George Gastaldi
> Fix For: 2.x Future
>
>
> Having an addon that depends on the furnace-cdi container and declares the following class:
> {code}
> import javax.enterprise.inject.Produces;
> import javax.ws.rs.client.Client;
> import javax.ws.rs.client.ClientBuilder;
> public class RestClientProducer
> {
> @Produces
> public ClientBuilder createClientBuilder()
> {
> ClientBuilder builder = ClientBuilder.newBuilder();
> return builder;
> }
> @Produces
> public Client createClient(ClientBuilder builder)
> {
> return builder.build();
> }
> }
> {code}
> Then:
> - {{WeldServiceRegistry.hasService(javax.ws.rs.client.Client.class)}} should return true
> - {{AddonRegistry.getServices(javax.ws.rs.client.Client.class).get()}} should call the producer method and return the requested service
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (FORGE-1876) Addon services should be exposed through @Produces methods
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1876?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1876:
-----------------------------------
Description:
Having an addon that depends on the furnace-cdi container and declares the following class:
{code}
import javax.enterprise.inject.Produces;
import javax.ws.rs.client.Client;
import javax.ws.rs.client.ClientBuilder;
public class RestClientProducer
{
@Produces
public ClientBuilder createClientBuilder()
{
ClientBuilder builder = ClientBuilder.newBuilder();
return builder;
}
@Produces
public Client createClient(ClientBuilder builder)
{
return builder.build();
}
}
{code}
Then:
- {{AddonRegistry.hasService(javax.ws.rs.client.Client.class)}} should return true
- {{AddonRegistry.getServices(javax.ws.rs.client.Client.class).get()}} should call the producer method and return the requested service
was:
Having an addon that depends on the furnace-cdi container and declares the following class:
{code}
import javax.enterprise.inject.Produces;
import javax.ws.rs.client.Client;
import javax.ws.rs.client.ClientBuilder;
public class RestClientProducer
{
@Produces
public ClientBuilder createClientBuilder()
{
ClientBuilder builder = ClientBuilder.newBuilder();
return builder;
}
@Produces
public Client createClient(ClientBuilder builder)
{
return builder.build();
}
}
{code}
{{AddonRegistry.getServices(javax.ws.rs.client.Client.class).get()}} should call the producer method and return the requested service
> Addon services should be exposed through @Produces methods
> -----------------------------------------------------------
>
> Key: FORGE-1876
> URL: https://issues.jboss.org/browse/FORGE-1876
> Project: Forge
> Issue Type: Enhancement
> Components: Furnace CDI
> Affects Versions: 2.6.0.Final
> Reporter: George Gastaldi
> Fix For: 2.x Future
>
>
> Having an addon that depends on the furnace-cdi container and declares the following class:
> {code}
> import javax.enterprise.inject.Produces;
> import javax.ws.rs.client.Client;
> import javax.ws.rs.client.ClientBuilder;
> public class RestClientProducer
> {
> @Produces
> public ClientBuilder createClientBuilder()
> {
> ClientBuilder builder = ClientBuilder.newBuilder();
> return builder;
> }
> @Produces
> public Client createClient(ClientBuilder builder)
> {
> return builder.build();
> }
> }
> {code}
> Then:
> - {{AddonRegistry.hasService(javax.ws.rs.client.Client.class)}} should return true
> - {{AddonRegistry.getServices(javax.ws.rs.client.Client.class).get()}} should call the producer method and return the requested service
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (FORGE-1876) Addon services should be exposed through @Produces methods
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1876:
--------------------------------------
Summary: Addon services should be exposed through @Produces methods
Key: FORGE-1876
URL: https://issues.jboss.org/browse/FORGE-1876
Project: Forge
Issue Type: Enhancement
Components: Furnace CDI
Affects Versions: 2.6.0.Final
Reporter: George Gastaldi
Fix For: 2.x Future
Having an addon that depends on the furnace-cdi container and declares the following class:
{code}
import javax.enterprise.inject.Produces;
import javax.ws.rs.client.Client;
import javax.ws.rs.client.ClientBuilder;
public class RestClientProducer
{
@Produces
public ClientBuilder createClientBuilder()
{
ClientBuilder builder = ClientBuilder.newBuilder();
return builder;
}
@Produces
public Client createClient(ClientBuilder builder)
{
return builder.build();
}
}
{code}
{{AddonRegistry.getServices(javax.ws.rs.client.Client.class).get()}} should call the producer method and return the requested service
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (FORGE-1875) Console hangs during auto-complete
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-1875?page=com.atlassian.jira.plugin... ]
Vineet Reynolds updated FORGE-1875:
-----------------------------------
Description:
When I TAB out for auto-complete options for JPA entities during scaffold generation, like so:
{noformat}
scaffold-generate --provider AngularJS --targets <TAB> com.redhat.sessions.model.
{noformat}
then the console hangs after displaying the initial package selection i.e. {{com.redhat.sessions.model.}}.
The following stacktrace is reported:
{noformat}
!ENTRY org.jboss.tools.forge.aesh.core 4 1 2014-06-09 20:44:52.663
!MESSAGE Error logged from Aesh Core Plugin:
!STACK 0
java.lang.Throwable: Unimplemented command: DEVICE_STATUS_REPORT
at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:11)
at org.jboss.tools.aesh.core.internal.io.DocumentHandler.handleCommand(DocumentHandler.java:35)
at org.jboss.tools.aesh.core.internal.io.CommandFilter.filterOutput(CommandFilter.java:34)
at org.jboss.tools.aesh.core.internal.io.AeshOutputStream.write(AeshOutputStream.java:21)
at java.io.PrintStream.write(PrintStream.java:480)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
at java.io.PrintStream.write(PrintStream.java:527)
at java.io.PrintStream.print(PrintStream.java:669)
at org.jboss.aesh.console.Console$ConsoleShell.getCursor(Console.java:935)
at org.jboss.aesh.console.AeshConsoleBuffer.redrawMultipleLines(AeshConsoleBuffer.java:156)
at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:125)
at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:114)
at org.jboss.aesh.console.AeshCompletionHandler.displayCompletion(AeshCompletionHandler.java:218)
at org.jboss.aesh.console.AeshCompletionHandler.complete(AeshCompletionHandler.java:162)
at org.jboss.aesh.console.AeshInputProcessor.complete(AeshInputProcessor.java:381)
at org.jboss.aesh.console.AeshInputProcessor.parseOperation(AeshInputProcessor.java:149)
at org.jboss.aesh.console.Console.processInternalOperation(Console.java:596)
at org.jboss.aesh.console.Console.execute(Console.java:586)
at org.jboss.aesh.console.Console.access$700(Console.java:60)
at org.jboss.aesh.console.Console$6.run(Console.java:503)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}
was:
When I TAB out for auto-complete options for JPA entities during scaffold generation, like so:
{noformat}
scaffold-generate --provider AngularJS --targets <TAB> com.redhat.sessions.model.
{noformat}
tnen the console hangs after displaying the initial package selection i.e. {{com.redhat.sessions.model.}}.
The following stacktrace is reported:
{noformat}
!ENTRY org.jboss.tools.forge.aesh.core 4 1 2014-06-09 20:44:52.663
!MESSAGE Error logged from Aesh Core Plugin:
!STACK 0
java.lang.Throwable: Unimplemented command: DEVICE_STATUS_REPORT
at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:11)
at org.jboss.tools.aesh.core.internal.io.DocumentHandler.handleCommand(DocumentHandler.java:35)
at org.jboss.tools.aesh.core.internal.io.CommandFilter.filterOutput(CommandFilter.java:34)
at org.jboss.tools.aesh.core.internal.io.AeshOutputStream.write(AeshOutputStream.java:21)
at java.io.PrintStream.write(PrintStream.java:480)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
at java.io.PrintStream.write(PrintStream.java:527)
at java.io.PrintStream.print(PrintStream.java:669)
at org.jboss.aesh.console.Console$ConsoleShell.getCursor(Console.java:935)
at org.jboss.aesh.console.AeshConsoleBuffer.redrawMultipleLines(AeshConsoleBuffer.java:156)
at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:125)
at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:114)
at org.jboss.aesh.console.AeshCompletionHandler.displayCompletion(AeshCompletionHandler.java:218)
at org.jboss.aesh.console.AeshCompletionHandler.complete(AeshCompletionHandler.java:162)
at org.jboss.aesh.console.AeshInputProcessor.complete(AeshInputProcessor.java:381)
at org.jboss.aesh.console.AeshInputProcessor.parseOperation(AeshInputProcessor.java:149)
at org.jboss.aesh.console.Console.processInternalOperation(Console.java:596)
at org.jboss.aesh.console.Console.execute(Console.java:586)
at org.jboss.aesh.console.Console.access$700(Console.java:60)
at org.jboss.aesh.console.Console$6.run(Console.java:503)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}
> Console hangs during auto-complete
> ----------------------------------
>
> Key: FORGE-1875
> URL: https://issues.jboss.org/browse/FORGE-1875
> Project: Forge
> Issue Type: Bug
> Components: UI - Shell
> Affects Versions: 2.6.0.Final
> Environment: JBDS 8 Beta 2, Mac OS X Mavericks 10.9.3, Oracle JDK 1.8.0_05
> Reporter: Vineet Reynolds
>
> When I TAB out for auto-complete options for JPA entities during scaffold generation, like so:
> {noformat}
> scaffold-generate --provider AngularJS --targets <TAB> com.redhat.sessions.model.
> {noformat}
> then the console hangs after displaying the initial package selection i.e. {{com.redhat.sessions.model.}}.
> The following stacktrace is reported:
> {noformat}
> !ENTRY org.jboss.tools.forge.aesh.core 4 1 2014-06-09 20:44:52.663
> !MESSAGE Error logged from Aesh Core Plugin:
> !STACK 0
> java.lang.Throwable: Unimplemented command: DEVICE_STATUS_REPORT
> at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:11)
> at org.jboss.tools.aesh.core.internal.io.DocumentHandler.handleCommand(DocumentHandler.java:35)
> at org.jboss.tools.aesh.core.internal.io.CommandFilter.filterOutput(CommandFilter.java:34)
> at org.jboss.tools.aesh.core.internal.io.AeshOutputStream.write(AeshOutputStream.java:21)
> at java.io.PrintStream.write(PrintStream.java:480)
> at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
> at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
> at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
> at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
> at java.io.PrintStream.write(PrintStream.java:527)
> at java.io.PrintStream.print(PrintStream.java:669)
> at org.jboss.aesh.console.Console$ConsoleShell.getCursor(Console.java:935)
> at org.jboss.aesh.console.AeshConsoleBuffer.redrawMultipleLines(AeshConsoleBuffer.java:156)
> at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:125)
> at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:114)
> at org.jboss.aesh.console.AeshCompletionHandler.displayCompletion(AeshCompletionHandler.java:218)
> at org.jboss.aesh.console.AeshCompletionHandler.complete(AeshCompletionHandler.java:162)
> at org.jboss.aesh.console.AeshInputProcessor.complete(AeshInputProcessor.java:381)
> at org.jboss.aesh.console.AeshInputProcessor.parseOperation(AeshInputProcessor.java:149)
> at org.jboss.aesh.console.Console.processInternalOperation(Console.java:596)
> at org.jboss.aesh.console.Console.execute(Console.java:586)
> at org.jboss.aesh.console.Console.access$700(Console.java:60)
> at org.jboss.aesh.console.Console$6.run(Console.java:503)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (FORGE-1875) Console hangs during auto-complete
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-1875:
--------------------------------------
Summary: Console hangs during auto-complete
Key: FORGE-1875
URL: https://issues.jboss.org/browse/FORGE-1875
Project: Forge
Issue Type: Bug
Components: UI - Shell
Affects Versions: 2.6.0.Final
Environment: JBDS 8 Beta 2, Mac OS X Mavericks 10.9.3, Oracle JDK 1.8.0_05
Reporter: Vineet Reynolds
When I TAB out for auto-complete options for JPA entities during scaffold generation, like so:
{noformat}
scaffold-generate --provider AngularJS --targets <TAB> com.redhat.sessions.model.
{noformat}
tnen the console hangs after displaying the initial package selection i.e. {{com.redhat.sessions.model.}}.
The following stacktrace is reported:
{noformat}
!ENTRY org.jboss.tools.forge.aesh.core 4 1 2014-06-09 20:44:52.663
!MESSAGE Error logged from Aesh Core Plugin:
!STACK 0
java.lang.Throwable: Unimplemented command: DEVICE_STATUS_REPORT
at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:11)
at org.jboss.tools.aesh.core.internal.io.DocumentHandler.handleCommand(DocumentHandler.java:35)
at org.jboss.tools.aesh.core.internal.io.CommandFilter.filterOutput(CommandFilter.java:34)
at org.jboss.tools.aesh.core.internal.io.AeshOutputStream.write(AeshOutputStream.java:21)
at java.io.PrintStream.write(PrintStream.java:480)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
at java.io.PrintStream.write(PrintStream.java:527)
at java.io.PrintStream.print(PrintStream.java:669)
at org.jboss.aesh.console.Console$ConsoleShell.getCursor(Console.java:935)
at org.jboss.aesh.console.AeshConsoleBuffer.redrawMultipleLines(AeshConsoleBuffer.java:156)
at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:125)
at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:114)
at org.jboss.aesh.console.AeshCompletionHandler.displayCompletion(AeshCompletionHandler.java:218)
at org.jboss.aesh.console.AeshCompletionHandler.complete(AeshCompletionHandler.java:162)
at org.jboss.aesh.console.AeshInputProcessor.complete(AeshInputProcessor.java:381)
at org.jboss.aesh.console.AeshInputProcessor.parseOperation(AeshInputProcessor.java:149)
at org.jboss.aesh.console.Console.processInternalOperation(Console.java:596)
at org.jboss.aesh.console.Console.execute(Console.java:586)
at org.jboss.aesh.console.Console.access$700(Console.java:60)
at org.jboss.aesh.console.Console$6.run(Console.java:503)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (FORGE-1802) Console hangs when running an invalid script
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1802?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1802:
------------------------------------------
I can't reproduce it anymore since George fixed the CCE
> Console hangs when running an invalid script
> --------------------------------------------
>
> Key: FORGE-1802
> URL: https://issues.jboss.org/browse/FORGE-1802
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.5.0.Final
> Reporter: Antonio Goncalves
> Priority: Critical
> Fix For: 2.x Future
>
>
> I am executing a script (with the {{run}} command) and the console hanged and stopped working completely (I had to kill the process). I realized that there is an error in the script (missing {{;}} at the end of line {{--named ISBN}}).
> Take the following script, and save it on a {{hangs.fsh}} file
> {code}
> # ##################### #
> # Creates a new project #
> # ##################### #
> project-new --named cdbookstore --topLevelPackage org.agoncal.training.javaee6adv --type war --finalName cdbookstore ;
> # Setup the persistence unit in persistence.xml
> # ############
> jpa-setup --persistenceUnitName cdbookstorePU ;
> # ######################## #
> # Creates the domain model #
> # ######################## #
> # ISBN constraint
> # ############
> constraint-new-annotation --named ISBN
> # Genre entity
> # ############
> jpa-new-entity --named Genre ;
> jpa-new-field --named name --length 100 ;
> {code}
> Now, execute the script, and see the error message :
> {code}
> [temp]$ run hangs.fsh
> project-new --named cdbookstore --topLevelPackage org.agoncal.training.javaee6adv --type war --finalName cdbookstore ;
> ***SUCCESS*** Project named 'cdbookstore' has been created.
> [cdbookstore]$ jpa-setup --persistenceUnitName cdbookstorePU ;
> ***SUCCESS*** Persistence (JPA) is installed.
> [cdbookstore]$ constraint-new-annotation --named ISBN
> ***SUCCESS*** Bean Validation Constraint Annotations org.agoncal.training.javaee6adv.constraints.ISBN was created
> [ISBN.java]$ jpa-new-entity --named Genre ;
> Exception when parsing/running: jpa-new-entity --named Genre , org.jboss.forge.roaster.model.impl.JavaAnnotationImpl cannot be cast to org.jboss.forge.roaster.model.MemberHolder
> [ISBN.java]$
> {code}
> At this point, I can't interact with the console and need to kill the process.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (FORGE-1861) Having a cp command like in Forge 1.x
by Daniel Cunha (JIRA)
[ https://issues.jboss.org/browse/FORGE-1861?page=com.atlassian.jira.plugin... ]
Daniel Cunha reassigned FORGE-1861:
-----------------------------------
Assignee: Daniel Cunha
> Having a cp command like in Forge 1.x
> -------------------------------------
>
> Key: FORGE-1861
> URL: https://issues.jboss.org/browse/FORGE-1861
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.6.0.Final
> Reporter: Antonio Goncalves
> Assignee: Daniel Cunha
> Fix For: 2.x Future
>
>
> It would be good to have a {{cp}} command like in Forge 1.x
> {code}
> [no project] bin $ help cp
> [cp] - Copy a file or directory
> [OPTIONS]
> [Arg #1] - source - no help text available
> [Arg #2] - target - no help text available
> [no project] bin $ exit
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (FORGE-1802) Console hangs when running an invalid script
by Daniel Cunha (JIRA)
[ https://issues.jboss.org/browse/FORGE-1802?page=com.atlassian.jira.plugin... ]
Daniel Cunha commented on FORGE-1802:
-------------------------------------
What criteria to validate the script?
> Console hangs when running an invalid script
> --------------------------------------------
>
> Key: FORGE-1802
> URL: https://issues.jboss.org/browse/FORGE-1802
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.5.0.Final
> Reporter: Antonio Goncalves
> Priority: Critical
> Fix For: 2.x Future
>
>
> I am executing a script (with the {{run}} command) and the console hanged and stopped working completely (I had to kill the process). I realized that there is an error in the script (missing {{;}} at the end of line {{--named ISBN}}).
> Take the following script, and save it on a {{hangs.fsh}} file
> {code}
> # ##################### #
> # Creates a new project #
> # ##################### #
> project-new --named cdbookstore --topLevelPackage org.agoncal.training.javaee6adv --type war --finalName cdbookstore ;
> # Setup the persistence unit in persistence.xml
> # ############
> jpa-setup --persistenceUnitName cdbookstorePU ;
> # ######################## #
> # Creates the domain model #
> # ######################## #
> # ISBN constraint
> # ############
> constraint-new-annotation --named ISBN
> # Genre entity
> # ############
> jpa-new-entity --named Genre ;
> jpa-new-field --named name --length 100 ;
> {code}
> Now, execute the script, and see the error message :
> {code}
> [temp]$ run hangs.fsh
> project-new --named cdbookstore --topLevelPackage org.agoncal.training.javaee6adv --type war --finalName cdbookstore ;
> ***SUCCESS*** Project named 'cdbookstore' has been created.
> [cdbookstore]$ jpa-setup --persistenceUnitName cdbookstorePU ;
> ***SUCCESS*** Persistence (JPA) is installed.
> [cdbookstore]$ constraint-new-annotation --named ISBN
> ***SUCCESS*** Bean Validation Constraint Annotations org.agoncal.training.javaee6adv.constraints.ISBN was created
> [ISBN.java]$ jpa-new-entity --named Genre ;
> Exception when parsing/running: jpa-new-entity --named Genre , org.jboss.forge.roaster.model.impl.JavaAnnotationImpl cannot be cast to org.jboss.forge.roaster.model.MemberHolder
> [ISBN.java]$
> {code}
> At this point, I can't interact with the console and need to kill the process.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (FORGE-1622) It would be good if Aesh had access to export variables
by Daniel Cunha (JIRA)
[ https://issues.jboss.org/browse/FORGE-1622?page=com.atlassian.jira.plugin... ]
Daniel Cunha edited comment on FORGE-1622 at 6/7/14 6:36 PM:
-------------------------------------------------------------
fixed in Aesh 0.56-SNAPSHOT.
https://github.com/aeshell/aesh/pull/74
https://github.com/aeshell/aesh/pull/79
It's need set ExportUsesSystemEnvironment as true. As well:
settings.setExportUsesSystemEnvironment(true);
{code}
SettingsBuilder newSettings = new SettingsBuilder(settings)
.historyFile(history)
.aliasFile(alias)
.exportFile(export)
.setExportUsesSystemEnvironment(true)
.interruptHook(new ForgeInterruptHook(registry));
{code}
was (Author: danielcunha):
fixed in Aesh 0.56-SNAPSHOT.
https://github.com/aeshell/aesh/pull/74
https://github.com/aeshell/aesh/pull/79
It's need set ExportUsesSystemEnvironment as true. As well:
settings.setExportUsesSystemEnvironment(true);
{code}
SettingsBuilder newSettings = new SettingsBuilder(settings)
.historyFile(history)
.aliasFile(alias)
.exportFile(export)
.setExportUsesSystemEnvironment(true)
.interruptHook(new ForgeInterruptHook(registry));
{/code}
> It would be good if Aesh had access to export variables
> -------------------------------------------------------
>
> Key: FORGE-1622
> URL: https://issues.jboss.org/browse/FORGE-1622
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.1.1.Final
> Reporter: Antonio Goncalves
> Assignee: Daniel Cunha
> Priority: Minor
> Fix For: 2.x Future
>
>
> This would be a "nice to have" feature from the shell command line.
> I'm under OS X and I have a set of variables that I've exported. As an example, all my code is under {{$CODE_HOME}}. It would be good if I code {{cd $CODE_HOME}} when I'm in Aesh :
> {code}
> ~$ cd $CODE_HOME // Under OS X
> ~/Documents/Code$ forge // Entering Forge
> _____
> | ___|__ _ __ __ _ ___
> | |_ / _ \| `__/ _` |/ _ \ \\
> | _| (_) | | | (_| | __/ //
> |_| \___/|_| \__, |\___|
> |___/
> JBoss Forge, version [ 2.1.1.Final ] - JBoss, by Red Hat, Inc.
> [Code]$ cd ~
> [antoniombp]$ cd $CODE_HOME // Good if it goes to the right directory
> [antoniombp]$ echo $CODE_HOME // Doesn't have access to the exported variable
> [antoniombp]$
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months