[JBoss JIRA] (FORGE-2190) Addon: New UI Command throws java.lang.IllegalArgumentException: Invalid identifier : >< on empty class name
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2190?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2190.
----------------------------------
Resolution: Done
> Addon: New UI Command throws java.lang.IllegalArgumentException: Invalid identifier : >< on empty class name
> ------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-2190
> URL: https://issues.jboss.org/browse/FORGE-2190
> Project: Forge
> Issue Type: Bug
> Components: Addon Development
> Affects Versions: 2.13.1.Final
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 2.13.2.Final
>
>
> {code}
> java.lang.IllegalArgumentException: Invalid identifier : ><
> at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:195)
> at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:2202)
> at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setName(AbstractJavaSource.java:450)
> at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setName(AbstractJavaSource.java:56)
> at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.buildJavaSource(AbstractJavaSourceCommand.java:188)
> at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.classExists(AbstractJavaSourceCommand.java:162)
> at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.access$100(AbstractJavaSourceCommand.java:58)
> at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:100)
> at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:92)
> at org.jboss.forge.furnace.util.Callables.call(Callables.java:43)
> at org.jboss.forge.addon.ui.impl.input.AbstractInputComponent.isEnabled(AbstractInputComponent.java:98)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (FORGE-2190) Addon: New UI Command throws java.lang.IllegalArgumentException: Invalid identifier : >< on empty class name
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2190?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2190:
-----------------------------------
Description:
{code}
java.lang.IllegalArgumentException: Invalid identifier : ><
at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:195)
at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:2202)
at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setName(AbstractJavaSource.java:450)
at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setName(AbstractJavaSource.java:56)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.buildJavaSource(AbstractJavaSourceCommand.java:188)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.classExists(AbstractJavaSourceCommand.java:162)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.access$100(AbstractJavaSourceCommand.java:58)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:100)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:92)
at org.jboss.forge.furnace.util.Callables.call(Callables.java:43)
at org.jboss.forge.addon.ui.impl.input.AbstractInputComponent.isEnabled(AbstractInputComponent.java:98)
{code}
was:
java.lang.IllegalArgumentException: Invalid identifier : ><
at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:195)
at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:2202)
at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setName(AbstractJavaSource.java:450)
at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setName(AbstractJavaSource.java:56)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.buildJavaSource(AbstractJavaSourceCommand.java:188)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.classExists(AbstractJavaSourceCommand.java:162)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.access$100(AbstractJavaSourceCommand.java:58)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:100)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:92)
at org.jboss.forge.furnace.util.Callables.call(Callables.java:43)
at org.jboss.forge.addon.ui.impl.input.AbstractInputComponent.isEnabled(AbstractInputComponent.java:98)
> Addon: New UI Command throws java.lang.IllegalArgumentException: Invalid identifier : >< on empty class name
> ------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-2190
> URL: https://issues.jboss.org/browse/FORGE-2190
> Project: Forge
> Issue Type: Bug
> Components: Addon Development
> Affects Versions: 2.13.1.Final
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 2.13.2.Final
>
>
> {code}
> java.lang.IllegalArgumentException: Invalid identifier : ><
> at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:195)
> at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:2202)
> at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setName(AbstractJavaSource.java:450)
> at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setName(AbstractJavaSource.java:56)
> at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.buildJavaSource(AbstractJavaSourceCommand.java:188)
> at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.classExists(AbstractJavaSourceCommand.java:162)
> at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.access$100(AbstractJavaSourceCommand.java:58)
> at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:100)
> at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:92)
> at org.jboss.forge.furnace.util.Callables.call(Callables.java:43)
> at org.jboss.forge.addon.ui.impl.input.AbstractInputComponent.isEnabled(AbstractInputComponent.java:98)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (FORGE-2190) Addon: New UI Command throws java.lang.IllegalArgumentException: Invalid identifier : >< on empty class name
by George Gastaldi (JIRA)
George Gastaldi created FORGE-2190:
--------------------------------------
Summary: Addon: New UI Command throws java.lang.IllegalArgumentException: Invalid identifier : >< on empty class name
Key: FORGE-2190
URL: https://issues.jboss.org/browse/FORGE-2190
Project: Forge
Issue Type: Bug
Components: Addon Development
Affects Versions: 2.13.1.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Fix For: 2.13.2.Final
java.lang.IllegalArgumentException: Invalid identifier : ><
at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:195)
at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:2202)
at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setName(AbstractJavaSource.java:450)
at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setName(AbstractJavaSource.java:56)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.buildJavaSource(AbstractJavaSourceCommand.java:188)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.classExists(AbstractJavaSourceCommand.java:162)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.access$100(AbstractJavaSourceCommand.java:58)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:100)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:92)
at org.jboss.forge.furnace.util.Callables.call(Callables.java:43)
at org.jboss.forge.addon.ui.impl.input.AbstractInputComponent.isEnabled(AbstractInputComponent.java:98)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (FORGE-2189) Custom Addon cannot be run, jandex not found
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2189?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-2189:
----------------------------------------
It looks like some conflict with Weld's dependencies. Can you paste2.org your pom.xml?
> Custom Addon cannot be run, jandex not found
> --------------------------------------------
>
> Key: FORGE-2189
> URL: https://issues.jboss.org/browse/FORGE-2189
> Project: Forge
> Issue Type: Bug
> Components: Addon Development
> Affects Versions: 2.13.1.Final
> Environment: JBoss Dev studio
> W7 64, Java 1.7, forge 2.13.1
> Reporter: Jerome B
>
> My custom addon builds successfully BUT log fills with error
> The cause would be
> Caused by: java.lang.NoClassDefFoundError: org/jboss/jandex/Indexer
> at org.jboss.weld.environment.se.discovery.url.JandexEnabledFileSystemURLHandler.<init>(JandexEnabledFileSystemURLHandler.java:35)
> ... 19 more
> It still happens although I added the dependency
> <dependency>
> <groupId>org.jboss</groupId>
> <artifactId>jandex</artifactId>
> <version>1.2.2.Final</version>
> <scope>runtime</scope>
> </dependency>
> I even tried with
> <dependency>
> <groupId>org.jboss.weld.se</groupId>
> <artifactId>weld-se</artifactId>
> <version>2.2.8.Final</version>
> </dependency>
> Without luck.
> First time I see this error when writing addons
> My addon uses a lot of reflection to discover annotations on fields and methods. I wonder what triggers the use of jandex
> The full stack is
> 18:38:44,078 INFO [org.jboss.forge.furnace.impl.addons.AddonRunnable] (fr.employer.addons:ADDONS213,1.0.2-SNAPSHOT) > Starting container [fr.employer.addons:ADDONS213,1.0.2-SNAPSHOT] [C:\Users\jerome.b\.forge\addons]
> 18:38:44,088 SEVERE [org.jboss.forge.furnace.impl.addons.AddonRunnable] (fr.employer.addons:ADDONS213,1.0.2-SNAPSHOT) Failed to start addon [fr.employer.addons:ADDONS213,1.0.2-SNAPSHOT] with classloader [ModuleClassLoader for Module "fr.employer.addons.ADDONS213:1.0.2-SNAPSHOT_2677a771-c4eb-4323-8ef7-1608cdad2915" from AddonModuleLoader]: java.lang.IllegalStateException: Unable to instantiate org.jboss.weld.environment.se.discovery.url.JandexEnabledFileSystemURLHandler using parameters: [org.jboss.weld.bootstrap.WeldBootstrap@3546eaec]
> at org.jboss.weld.environment.se.util.SEReflections.newInstance(SEReflections.java:85)
> at org.jboss.weld.environment.se.discovery.url.URLScanner.scan(URLScanner.java:81)
> at org.jboss.weld.environment.se.discovery.url.DiscoveryStrategy.discoverArchives(DiscoveryStrategy.java:52)
> at org.jboss.weld.environment.se.Weld.createDeployment(Weld.java:202)
> at org.jboss.forge.furnace.container.cdi.weld.ModularWeld.createDeployment(ModularWeld.java:41)
> at org.jboss.weld.environment.se.Weld.initialize(Weld.java:127)
> at org.jboss.forge.furnace.container.cdi.lifecycle.WeldAddonLifecycleProvider.start(WeldAddonLifecycleProvider.java:77)
> at org.jboss.forge.furnace.impl.addons.AddonRunnable$2.call(AddonRunnable.java:92) [furnace-2.13.1.Final.jar:2.13.1.Final]
> at org.jboss.forge.furnace.impl.addons.AddonRunnable$2.call(AddonRunnable.java:86) [furnace-2.13.1.Final.jar:2.13.1.Final]
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) [furnace-api-2.13.1.Final.jar:2.13.1.Final]
> at org.jboss.forge.furnace.impl.addons.AddonRunnable.run(AddonRunnable.java:85) [furnace-2.13.1.Final.jar:2.13.1.Final]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_40]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedConstructorAccessor493.newInstance(Unknown Source) [:1.7.0_40]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_40]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_40]
> at org.jboss.weld.environment.se.util.SEReflections.newInstance(SEReflections.java:83)
> ... 15 more
> Caused by: java.lang.NoClassDefFoundError: org/jboss/jandex/Indexer
> at org.jboss.weld.environment.se.discovery.url.JandexEnabledFileSystemURLHandler.<init>(JandexEnabledFileSystemURLHandler.java:35)
> ... 19 more
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (FORGE-2189) Custom Addon cannot be run, jandex not found
by Jerome B (JIRA)
Jerome B created FORGE-2189:
-------------------------------
Summary: Custom Addon cannot be run, jandex not found
Key: FORGE-2189
URL: https://issues.jboss.org/browse/FORGE-2189
Project: Forge
Issue Type: Bug
Components: Addon Development
Affects Versions: 2.13.1.Final
Environment: JBoss Dev studio
W7 64, Java 1.7, forge 2.13.1
Reporter: Jerome B
My custom addon builds successfully BUT log fills with error
The cause would be
Caused by: java.lang.NoClassDefFoundError: org/jboss/jandex/Indexer
at org.jboss.weld.environment.se.discovery.url.JandexEnabledFileSystemURLHandler.<init>(JandexEnabledFileSystemURLHandler.java:35)
... 19 more
It still happens although I added the dependency
<dependency>
<groupId>org.jboss</groupId>
<artifactId>jandex</artifactId>
<version>1.2.2.Final</version>
<scope>runtime</scope>
</dependency>
I even tried with
<dependency>
<groupId>org.jboss.weld.se</groupId>
<artifactId>weld-se</artifactId>
<version>2.2.8.Final</version>
</dependency>
Without luck.
First time I see this error when writing addons
My addon uses a lot of reflection to discover annotations on fields and methods. I wonder what triggers the use of jandex
The full stack is
18:38:44,078 INFO [org.jboss.forge.furnace.impl.addons.AddonRunnable] (fr.employer.addons:ADDONS213,1.0.2-SNAPSHOT) > Starting container [fr.employer.addons:ADDONS213,1.0.2-SNAPSHOT] [C:\Users\jerome.b\.forge\addons]
18:38:44,088 SEVERE [org.jboss.forge.furnace.impl.addons.AddonRunnable] (fr.employer.addons:ADDONS213,1.0.2-SNAPSHOT) Failed to start addon [fr.employer.addons:ADDONS213,1.0.2-SNAPSHOT] with classloader [ModuleClassLoader for Module "fr.employer.addons.ADDONS213:1.0.2-SNAPSHOT_2677a771-c4eb-4323-8ef7-1608cdad2915" from AddonModuleLoader]: java.lang.IllegalStateException: Unable to instantiate org.jboss.weld.environment.se.discovery.url.JandexEnabledFileSystemURLHandler using parameters: [org.jboss.weld.bootstrap.WeldBootstrap@3546eaec]
at org.jboss.weld.environment.se.util.SEReflections.newInstance(SEReflections.java:85)
at org.jboss.weld.environment.se.discovery.url.URLScanner.scan(URLScanner.java:81)
at org.jboss.weld.environment.se.discovery.url.DiscoveryStrategy.discoverArchives(DiscoveryStrategy.java:52)
at org.jboss.weld.environment.se.Weld.createDeployment(Weld.java:202)
at org.jboss.forge.furnace.container.cdi.weld.ModularWeld.createDeployment(ModularWeld.java:41)
at org.jboss.weld.environment.se.Weld.initialize(Weld.java:127)
at org.jboss.forge.furnace.container.cdi.lifecycle.WeldAddonLifecycleProvider.start(WeldAddonLifecycleProvider.java:77)
at org.jboss.forge.furnace.impl.addons.AddonRunnable$2.call(AddonRunnable.java:92) [furnace-2.13.1.Final.jar:2.13.1.Final]
at org.jboss.forge.furnace.impl.addons.AddonRunnable$2.call(AddonRunnable.java:86) [furnace-2.13.1.Final.jar:2.13.1.Final]
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) [furnace-api-2.13.1.Final.jar:2.13.1.Final]
at org.jboss.forge.furnace.impl.addons.AddonRunnable.run(AddonRunnable.java:85) [furnace-2.13.1.Final.jar:2.13.1.Final]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_40]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_40]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedConstructorAccessor493.newInstance(Unknown Source) [:1.7.0_40]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_40]
at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_40]
at org.jboss.weld.environment.se.util.SEReflections.newInstance(SEReflections.java:83)
... 15 more
Caused by: java.lang.NoClassDefFoundError: org/jboss/jandex/Indexer
at org.jboss.weld.environment.se.discovery.url.JandexEnabledFileSystemURLHandler.<init>(JandexEnabledFileSystemURLHandler.java:35)
... 19 more
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (FORGE-2188) Improve addon dev page of documentation/website
by Jerome B (JIRA)
Jerome B created FORGE-2188:
-------------------------------
Summary: Improve addon dev page of documentation/website
Key: FORGE-2188
URL: https://issues.jboss.org/browse/FORGE-2188
Project: Forge
Issue Type: Enhancement
Components: Documentation
Affects Versions: 2.13.1.Final
Reporter: Jerome B
In page http://forge.jboss.org/document/develop-an-addon
Elaborate a description of the workflow of developping an addon (tools to use, launch order when relevant).
* which is the 'best' way (shell console ? eclipse's forge console ?)
* how to find the same CLI version of Forge that DevStudio is using ? (link to page of older distribs)
* Point out that using different versions in eclipse & shell console can lead to issues (addon listed by addon-list but not proposed by shell completion)
* how to start the 'remote' debugging
* what to do if it hangs (delete .forge, delete .m2 what else ?)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (FORGE-2187) furnace-maven-plugin fails to resolve from local or remote multiple repositories
by Lincoln Baxter III (JIRA)
Lincoln Baxter III created FORGE-2187:
-----------------------------------------
Summary: furnace-maven-plugin fails to resolve from local or remote multiple repositories
Key: FORGE-2187
URL: https://issues.jboss.org/browse/FORGE-2187
Project: Forge
Issue Type: Feature Request
Components: Addon Manager, Build Tools - Maven
Affects Versions: 2.13.1.Final
Reporter: Lincoln Baxter III
{code}
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12:31 min
[INFO] Finished at: 2015-01-16T03:26:39-05:00
[INFO] Final Memory: 63M/375M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jboss.forge.furnace:furnace-maven-plugin:2.13.1.Final:addon-install (deploy-addons) on project windup-distribution: Execution deploy-addons of goal org.jboss.forge.furnace:furnace-maven-plugin:2.13.1.Final:addon-install failed: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact org.ocpsoft.rewrite:rewrite-impl:jar:3.0.0-20150113.202358-11 in jboss-community-repository (http://localhost:8081/artifactory/jboss-community) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :windup-distribution
Build step 'Invoke top-level Maven targets' marked build as failure
IRC notifier plugin: Sending notification to: #windup
Sending e-mails to: jesse.sightler(a)gmail.com
Finished: FAILURE
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (FORGE-2185) archetype-list - Command has no documentation and lists nothing
by Claus Ibsen (JIRA)
Claus Ibsen created FORGE-2185:
----------------------------------
Summary: archetype-list - Command has no documentation and lists nothing
Key: FORGE-2185
URL: https://issues.jboss.org/browse/FORGE-2185
Project: Forge
Issue Type: Bug
Affects Versions: 2.13.0.Final
Reporter: Claus Ibsen
Priority: Minor
In forge 2.13.0 I type
{code}
archetype-list
{code}
and it prints nothing.
The man page for this command does not show any documentation what it does, and how to use it.
{code}
NAME
archetype-list -- Maven
SYNOPSIS
archetype-list [-]
DESCRIPTION
* --named*
RESOURCES
forge: <http://forge.jboss.org/>
COPYING
Copyright 2015 Red Hat, Inc. and/or its affiliates.
Licensed under the Eclipse Public License version 1.0, available at http://www.eclipse.org/legal/epl-v10.html
{code}
Also I wonder as a 3rd party plugin provider, can you install custom archetypes that this command can list?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months