[JBoss JIRA] (FORGE-1227) Facet classloading problem
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1227?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1227:
-------------------------------------------
:) I will personally do everything I can to make sure your migration goes smoothly.
> Facet classloading problem
> --------------------------
>
> Key: FORGE-1227
> URL: https://issues.jboss.org/browse/FORGE-1227
> Project: Forge
> Issue Type: Bug
> Components: Build Tools - Maven
> Affects Versions: 1.4.1.Final
> Reporter: Lennart Jörelid
> Priority: Blocker
> Fix For: 1.x Future
>
>
> I am a bit puzzled about a Forge behaviour I can not seem to understand. There seems to be a difference in the line
>
> {code:java}
> final Project topReactor = projectFactory.createProject(rootDirectory,DependencyFacet.class, MetadataFacet.class, MavenPluginFacet.class);
> {code}
>
> 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?
>
> {code}
> 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)
> ...
> {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
11 years, 3 months
[JBoss JIRA] (FORGE-1227) Facet classloading problem
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1227?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III closed FORGE-1227.
-------------------------------------
Resolution: Won't Fix
Sadness. Forge 1 :( Closing issue. But JOY! Forge 2!
> Facet classloading problem
> --------------------------
>
> Key: FORGE-1227
> URL: https://issues.jboss.org/browse/FORGE-1227
> Project: Forge
> Issue Type: Bug
> Components: Build Tools - Maven
> Affects Versions: 1.4.1.Final
> Reporter: Lennart Jörelid
> Priority: Blocker
> Fix For: 1.x Future
>
>
> I am a bit puzzled about a Forge behaviour I can not seem to understand. There seems to be a difference in the line
>
> {code:java}
> final Project topReactor = projectFactory.createProject(rootDirectory,DependencyFacet.class, MetadataFacet.class, MavenPluginFacet.class);
> {code}
>
> 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?
>
> {code}
> 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)
> ...
> {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
11 years, 3 months
[JBoss JIRA] (FORGE-1227) Facet classloading problem
by Lennart Jörelid (JIRA)
[ https://issues.jboss.org/browse/FORGE-1227?page=com.atlassian.jira.plugin... ]
Lennart Jörelid commented on FORGE-1227:
----------------------------------------
Fair; I will make the Forge 2.0 transition roughly in the end of next week.
:)
> Facet classloading problem
> --------------------------
>
> Key: FORGE-1227
> URL: https://issues.jboss.org/browse/FORGE-1227
> Project: Forge
> Issue Type: Bug
> Components: Build Tools - Maven
> Affects Versions: 1.4.1.Final
> Reporter: Lennart Jörelid
> Priority: Blocker
> Fix For: 1.x Future
>
>
> I am a bit puzzled about a Forge behaviour I can not seem to understand. There seems to be a difference in the line
>
> {code:java}
> final Project topReactor = projectFactory.createProject(rootDirectory,DependencyFacet.class, MetadataFacet.class, MavenPluginFacet.class);
> {code}
>
> 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?
>
> {code}
> 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)
> ...
> {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
11 years, 3 months
[JBoss JIRA] (FORGE-1227) Facet classloading problem
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1227?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1227:
-------------------------------------------
Hey Lennart,
I honestly can't say that we are going to get to the root cause of this issue :( IMO, the best solution is to fix the architecture for which this is causing a problem, and that's what we're doing with Forge 2.
I'm really sorry but I think that based on how complex this issue is likely to be, our time is better spent getting Forge 2 out for you faster.
Have you had a chance to try it yet?
~Lincoln
> Facet classloading problem
> --------------------------
>
> Key: FORGE-1227
> URL: https://issues.jboss.org/browse/FORGE-1227
> Project: Forge
> Issue Type: Bug
> Components: Build Tools - Maven
> Affects Versions: 1.4.1.Final
> Reporter: Lennart Jörelid
> Priority: Blocker
> Fix For: 1.x Future
>
>
> I am a bit puzzled about a Forge behaviour I can not seem to understand. There seems to be a difference in the line
>
> {code:java}
> final Project topReactor = projectFactory.createProject(rootDirectory,DependencyFacet.class, MetadataFacet.class, MavenPluginFacet.class);
> {code}
>
> 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?
>
> {code}
> 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)
> ...
> {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
11 years, 3 months
[JBoss JIRA] (FORGEPLUGINS-141) Improvements to Forge 2 Generate Entities Command
by Lincoln Baxter III (JIRA)
Lincoln Baxter III created FORGEPLUGINS-141:
-----------------------------------------------
Summary: Improvements to Forge 2 Generate Entities Command
Key: FORGEPLUGINS-141
URL: https://issues.jboss.org/browse/FORGEPLUGINS-141
Project: Forge Plugins
Issue Type: Enhancement
Components: Hibernate Tools Plugin
Reporter: Lincoln Baxter III
Assignee: Koen Aers
1. On the first page, when no existing connection profile is selected, an Info message could be displayed, stating that a profile may be created on the next step.
2. On the second page, connection settings should be verified against the configured database, and either a warning or error should be displayed if connection could not be established.
If the connection was successful, Validation info message ("Database connection successful.") should be displayed.
If the connection was unsuccessful, Validation error or warning message ("Database connection failed.") should be displayed.
If an error is displayed rather than a warning, then a checkbox "Proceed with un-verified connection" could be selected to bypass the error, but I think a warning may be more appropriate than a hard stop.
--
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, 3 months
[JBoss JIRA] (FORGE-1227) Facet classloading problem
by Lennart Jörelid (JIRA)
[ https://issues.jboss.org/browse/FORGE-1227?page=com.atlassian.jira.plugin... ]
Lennart Jörelid updated FORGE-1227:
-----------------------------------
Priority: Blocker (was: Major)
> Facet classloading problem
> --------------------------
>
> Key: FORGE-1227
> URL: https://issues.jboss.org/browse/FORGE-1227
> Project: Forge
> Issue Type: Bug
> Components: Build Tools - Maven
> Affects Versions: 1.4.1.Final
> Reporter: Lennart Jörelid
> Priority: Blocker
> Fix For: 1.x Future
>
>
> I am a bit puzzled about a Forge behaviour I can not seem to understand. There seems to be a difference in the line
>
> {code:java}
> final Project topReactor = projectFactory.createProject(rootDirectory,DependencyFacet.class, MetadataFacet.class, MavenPluginFacet.class);
> {code}
>
> 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?
>
> {code}
> 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)
> ...
> {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
11 years, 3 months
[JBoss JIRA] (FORGE-1030) Support multi-module Forge plugins
by Lennart Jörelid (JIRA)
[ https://issues.jboss.org/browse/FORGE-1030?page=com.atlassian.jira.plugin... ]
Lennart Jörelid commented on FORGE-1030:
----------------------------------------
Actually, this thing still fails on 1.4.1.Final on a JBoss forge-internal exception.
> Support multi-module Forge plugins
> ----------------------------------
>
> Key: FORGE-1030
> URL: https://issues.jboss.org/browse/FORGE-1030
> Project: Forge
> Issue Type: Bug
> Components: Documentation, Plugin API, Plugin Repository
> Affects Versions: 1.3.3.Final, 1.4.0.Final
> Reporter: Lennart Jörelid
> Assignee: George Gastaldi
> Priority: Blocker
> Fix For: 1.4.1.Final
>
> Attachments: forge_1030_codeAnalysis.png
>
>
> It seems that Forge really needs better support for the default Maven
> development process. In repository.yaml, Forge plugins are defined by giving
> a Maven project GAV for the project holding the forge plugin definitions, as well as the GitHub repository holding the plugin source.
> Yet, Forge seems to ignore the Maven GAV information given in repository.yaml when checking out and building the plugin locally.
> This is a rather nasty bug, which in its current state effectively prevents anyone from using a multi-module build for their plugins (and it is also undocumented).
> An example is shown below:
> {code}
> [no project] Nazgul $ forge install-plugin nazgul
> ***INFO*** Preparing to install plugin: nazgul
> ***INFO*** Checking out plugin source files to [/var/folders/6g/9n7r543d2bv9n2qjvnvf_hsh0000gn/T/forgetemp6186363544408555570] via 'git'
> ***INFO*** Switching to branch/tag [refs/heads/1.3.3.Final]
> ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N]
> {code}
> While this analysis by Forge is incorrect (the Maven GAV given in the repository.yaml is indeed a project which holds plugins), it gets worse after installation:
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] nazgul-forge-parent ............................... SUCCESS [7.921s]
> [INFO] nazgul-forge-api-parent ........................... SUCCESS [4.345s]
> [INFO] nazgul-forge-model-parent ......................... SUCCESS [1.274s]
> [INFO] nazgul-forge-reactor .............................. SUCCESS [0.847s]
> [INFO] nazgul-forge-poms-reactor ......................... SUCCESS [0.058s]
> [INFO] nazgul-forge-analyzer-api ......................... SUCCESS [5.562s]
> [INFO] nazgul-forge-analyzer-impl-nazgul ................. SUCCESS [1.666s]
> [INFO] nazgul-forge-analyzer-reactor ..................... SUCCESS [0.020s]
> [INFO] nazgul-forge-factory-model ........................ SUCCESS [2.434s]
> [INFO] nazgul-forge-factory-api .......................... SUCCESS [7.634s]
> [INFO] nazgul-forge-factory-impl-nazgul .................. SUCCESS [2.724s]
> [INFO] nazgul-forge-factory-reactor ...................... SUCCESS [0.032s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 36.580s
> [INFO] Finished at: Mon Jul 22 07:46:48 CEST 2013
> [INFO] Final Memory: 49M/247M
> [INFO] ------------------------------------------------------------------------
> ***INFO*** Cleaning up temp workspace [/var/folders/6g/9n7r543d2bv9n2qjvnvf_hsh0000gn/T/forgetemp6186363544408555570]
> Deleted /var/folders/6g/9n7r543d2bv9n2qjvnvf_hsh0000gn/T/forgetemp6186363544408555570
> ***ERROR*** Exception encountered: Build artifact [nazgul-forge-reactor-1.0.1-SNAPSHOT.pom] is missing and cannot be installed. Please resolve build errors and try again. (type "set VERBOSE true" to enable stack traces)
> {code}
> So ...
> # The repository.yaml includes a full Maven GAV to the project which holds Forge plugins.
> # Forge uses repository.yaml to download the source from GitHub and build it
> # Forge ignores the Maven GAV given in repository.yaml, and simply uses the root reactor project to inspect and attempt to install the plugins.
> To fix this bug, Forge needs to find the project given within the repository.yaml within the downloaded reactor and install the plugins from *that* project.
--
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, 3 months