I'd recommend you to take a look at the Forge 2 Eclipse Plugin, which renders your commands as Eclipse wizards. We do have a shell integration, however we're still working hard on it to make as stable as the Eclipse integration.

Here is the link with instructions on how to run the Forge 2 Eclipse Plugin: https://github.com/forge/core/wiki/Building-Forge-2.0

On 09/24/2013 05:34 PM, Lennart Jörelid wrote:

Will give it a go.

Mind that I am quite unused to the shell interaction structure in Forge2, though, so it may take a few ... uhm ... really silly questions to yourself on my part. Fair?

:)

2013/9/24 George Gastaldi <ggastald@redhat.com>

Great. Btw, do you think it's possible to migrate your plugin to Forge 2?
I wonder if this bug happens in the Forge 2 codebase as well.

On 09/24/2013 05:27 PM, Lennart Jörelid wrote:

Created Jira-1227.

2013/9/24 George Gastaldi <ggastald@redhat.com>

Excellent. It may be worth filing a JIRA bug to keep track of this issue.

On 09/24/2013 05:15 PM, Lennart Jörelid wrote:

Hello George,

Actually just sat down with Lincoln to debug it; turned out to be non-trivial.

Unfortunately, the networking capacity in here is somewhat lacklustre; I don't know if he found decent enough network capacity yet to track it down.

2013/9/24 George Gastaldi <ggastald@redhat.com>

Hi Lennart,

Weird, this looks like some service in the Maven's Plexus Container was not initialized correctly or may be some conflict with the Maven JARs. 
Can you debug forge by following the steps described in http://forge.jboss.org/docs/using/debugging-forge.html to find out what's wrong ?
I couldn't reproduce this issue.

Thanks.

On 09/24/2013 02:40 PM, Lennart Jörelid wrote:

Hello all,

 

I am a bit puzzled about a Forge behaviour I can not seem to understand. There seems to be a difference in the line

 

final Project topReactor = projectFactory.createProject(rootDirectory,DependencyFacet.class, MetadataFacet.class, MavenPluginFacet.class);

 

if you use the "forge install-plugin", compared to if you download the repository 'manually' using Git and execute "forge source-plugin" on the repository.

 

In the latter of these cases, the statement above is executed correctly and the plugin works well. In the former of these cases, however, the  statement above throws an exception as shown below. I interpret this exception as something indicating that one of the Facets in the statement above is not present ... but since I cannot provoke this state when building the plugin locally (as is typical for debugging), I am at a loss to finding the cause. Is the statement above fundamentally wrong? Or should something be preceeding it to secure that the given Facets are present?

 

java.util.NoSuchElementException

  at org.sonatype.guice.bean.locators.LocatedBeans$Itr.next(LocatedBeans.java:184)

  at org.sonatype.guice.bean.locators.LocatedBeans$Itr.next(LocatedBeans.java:124)

  at org.sonatype.guice.plexus.locators.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:64)

  at org.sonatype.guice.plexus.locators.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:52)

  at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:243)

  at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:235)

  at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:229)

  at org.jboss.forge.maven.facets.MavenContainer.lookup(MavenContainer.java:214)

  at org.jboss.forge.maven.facets.MavenContainer.getBuildingRequest(MavenContainer.java:86)

  at org.jboss.forge.maven.facets.MavenContainer.getRequest(MavenContainer.java:68)

  at org.jboss.forge.maven.facets.MavenContainer$Proxy$_$$_WeldClientProxy.getRequest(MavenContainer$Proxy$_$$_WeldClientProxy.java)

  at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:90)

  at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:338)

  at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:394)

  at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:172)

  at org.jboss.forge.spec.javaee.BaseJavaEEFacet.isInstalled(BaseJavaEEFacet.java:64)

  at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153)

  at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208)

  at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186)

  at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178)

  at org.jboss.forge.project.services.ProjectFactory.createProject(ProjectFactory.java:146)

  at se.jguru.nazgul.forge.factory.api.AbstractNewNazgulFrameworkProjectPlugin.makeNazgulStyleProjectStructure(AbstractNewNazgulFrameworkProjectPlugin.java:253)

It seems - in the middle of the stack trace - that the BaseJavaEEFacet is required, but I can't seem to find a dependency/requirement for it in any of the given Facets. What am I missing?

--
+==============================+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: lj@jguru.se
| URL:   www.jguru.se
| Phone
| (skype):    jgurueurope
| (intl):     +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+

_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev

_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev

--

--
+==============================+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: lj@jguru.se
| URL:   www.jguru.se
| Phone
| (skype):    jgurueurope
| (intl):     +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+

_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev

_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev

--

--
+==============================+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: lj@jguru.se
| URL:   www.jguru.se
| Phone
| (skype):    jgurueurope
| (intl):     +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+

_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev

_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev

--

--
+==============================+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: lj@jguru.se
| URL:   www.jguru.se
| Phone
| (skype):    jgurueurope
| (intl):     +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+

_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev

_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev