Forge Hack Night, 2nd ed.
by Ivan St. Ivanov
Hi folks,
With Forge 2 coming really soon, I think that it is time for our second
Forge Hack Night. I still remember the first one: it was at the same time
fun and success.
Now I guess that a good theme for our next event could be Forge 1 plugins
migration to Forge 2. It would be valuable for us, non-core contributors,
to develop our first addons while having Lincoln, George, Koen or Vineet in
the IRC channel. It would also be good for Forge to have a blast of good
old plugins migrated.
What do you think?
Cheers,
Ivan
11 years, 10 months
Re: [forge-dev] Forge 2.0.0.CR2 Released
by Antonio Goncalves
>
> Hum.... I've downloaded Forge, removed all the addons, and when I run
> Forge, it installs and downloads CR1 artifacts, not CR2 :
>
>
> Installation request for [org.jboss.forge.addon:core,2.0.0.CR1] will:
> Deploy: [org.jboss.forge.addon:addons,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:addon-manager-spi,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:addon-manager,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:scaffold-spi,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:scaffold-faces,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:scaffold,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:database-tools,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:dev-tools-java,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:configuration,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:shell-spi,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:shell,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:parser-java,2.0.0.CR1]
> Deploy: [org.jboss.forge.furnace.container:simple,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:text,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:projects,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:templates-spi,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:templates,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:javaee,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:dependencies,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:resources,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:parser-xml,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:maven,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:convert,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:environment,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:ui-spi,2.0.0.CR1]
> Deploy: [org.jboss.forge.furnace.container:cdi,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:facets,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:ui,2.0.0.CR1]
> Deploy: [org.jboss.forge.addon:core,2.0.0.CR1]
>
> Confirm installation [Y/n]? Y
> Downloading:
> http://repo1.maven.org/maven2/org/jboss/forge/addon/addons/2.0.0.CR1/addo...
> Downloading:
> http://repo1.maven.org/maven2/org/jboss/forge/addon/addons-api/2.0.0.CR1/...
> Downloading:
> http://repo1.maven.org/maven2/org/jboss/forge/addon/addons-impl/2.0.0.CR1...
> Downloading:
> http://repo1.maven.org/maven2/org/jboss/forge/furnace/container/cdi/2.0.0...
> Downloading:
> http://repo1.maven.org/maven2/org/jboss/forge/addon/ui/2.0.0.CR1/ui-2.0.0...
> Downloaded:
> http://repo1.maven.org/maven2/org/jboss/forge/furnace/container/cdi/2.0.0... KB at 38.5 KB/sec)
> Downloading:
> http://repo1.maven.org/maven2/org/jboss/forge/addon/maven/2.0.0.CR1/maven...
> Downloaded:
> http://repo1.maven.org/maven2/org/jboss/forge/addon/addons/2.0.0.CR1/addo... KB at 36.6 KB/sec)
> Downloading:
> http://repo1.maven.org/maven2/org/jboss/forge/addon/projects/2.0.0.CR1/pr...
> Downloaded:
> http://repo1.maven.org/maven2/org/jboss/forge/addon/ui/2.0.0.CR1/ui-2.0.0... KB at 25.1 KB/sec)
> Downloading:
> http://repo1.maven.org/maven2/org/jboss/forge/addon/javaee/2.0.0.CR1/java...
> Downloaded:
> http://repo1.maven.org/maven2/org/jboss/forge/addon/maven/2.0.0.CR1/maven... KB at 48.5 KB/sec)
>
>
> The version is CR2 :
>
> [Forge]$ version
> JBoss Forge, version [ 2.0.0.CR2 ] - JBoss, by Red Hat, Inc. [
> http://jboss.org/forge ]
>
> But I don't see any of the new commands such as project-remove-dependency :
>
> [Forge]$ project-new
> --named --finalName --topLevelPackage --buildSystem --targetLocation
> --type --version
>
> Are you sure CR2 contains the rights addons ?
>
>
> 2014-01-28 Lincoln Baxter, III <lincolnbaxter(a)gmail.com>
>
> Please try it out and check for bugs! We are very close to final! Just one
>> day away :)
>>
>> http://forge.jboss.org/news/2014/01/28/post-forge-2.html
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>
--
--
Antonio Goncalves (antonio.goncalves(a)gmail.com)
Software architect
Web site : www.antoniogoncalves.org
Blog: agoncal.wordpress.com
Feed: feeds2.feedburner.com/AntonioGoncalves
Paris JUG leader : www.parisjug.org
LinkedIn: www.linkedin.com/in/agoncal
11 years, 10 months
Meeting minutes 2014-01-29
by Lincoln Baxter, III
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2014/forge.20...
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2014/forge.20...
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2014/forge.20...
Meeting summary
---------------
* Agenda (lincolnthree, 15:58:36)
* Forge Hack Night (lincolnthree, 15:58:44)
* Remaining issues for Forge 2 Final (lincolnthree, 15:58:51)
* Build issues (lincolnthree, 16:00:00)
* Forge Hack Night (lincolnthree, 16:00:57)
* Forge Build Issues (lincolnthree, 16:12:23)
* Forge 2 Hack night invitation is scheduled for Feb, 17th (gastaldi,
16:13:37)
* Remaining issues for Forge 2 Final (lincolnthree, 16:33:38)
* LINK: https://issues.jboss.org/browse/FORGE-1521 (agoncal,
16:57:35)
* LINK: https://issues.jboss.org/browse/FORGE-1522 (agoncal,
17:01:39)
* LINK: https://issues.jboss.org/browse/FORGE-1493 (lincolnthree,
17:09:28)
* LINK: https://issues.jboss.org/browse/FORGE-1461 (lincolnthree,
17:10:07)
* LINK: https://issues.jboss.org/browse/FORGE-1432 will try to fix one
more time before we release, but might have to wait for 2.0.1
(lincolnthree, 17:10:37)
* LINK: https://issues.jboss.org/browse/FORGE-1479 (lincolnthree,
17:11:39)
* LINK: https://issues.jboss.org/browse/FORGE-1451 (agoncal,
17:14:43)
* LINK: https://issues.jboss.org/browse/FORGE-1453 (agoncal,
17:14:51)
* LINK: https://github.com/forge/core/pull/369 (gastaldi, 17:32:18)
Meeting ended at 17:45:59 UTC.
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
11 years, 10 months
Fwd: Forge 2 core tests
by Ivan St. Ivanov
---------- Forwarded message ----------
From: George Gastaldi <ggastald(a)redhat.com>
Date: Thu, Jan 9, 2014 at 11:58 PM
Subject: Re: Forge 2 core tests
To: "Ivan St. Ivanov" <ivan.st.ivanov(a)gmail.com>
Hum, this may be due to file locking issues perhaps. Lincoln is pushing
some changes in Furnace, so it's worth building it too before building core.
Btw forge -i core installs the latest released version (NOT the snapshot).
You must use run forge -i org.jboss.forge.addon:core,2.0.0-SNAPSHOT instead
Em 09/01/2014, às 19:43, "Ivan St. Ivanov" <ivan.st.ivanov(a)gmail.com>
escreveu:
Hey George,
Here is what I tried:
1) I activated the profile that points to the snapshots repository
2) I run mvn clean install -DskipTests on all the core
3) I deleted the ~/.forge/addons directory
4) I run forge --install core
5) I ran forge and executed addon-list. It worked fine
6) I ran maven clean install in core/addon-manager. The test failed again
I noticed that inside the target directory there are two furnacexxxxxxx
directories. I looked inside and found that they are both lacking the
addon-manager addon. So I think that this may be the reason why the
addon-list command timed out?
Cheers,
Ivan
On Thu, Jan 9, 2014 at 12:20 AM, Ivan St. Ivanov
<ivan.st.ivanov(a)gmail.com>wrote:
> Isn't it weird? In order to test the addon-manager addon, you have to
> first have it installed in ~\.forge\addons?
>
>
> On Thu, Jan 9, 2014 at 12:14 AM, George Gastaldi <ggastald(a)redhat.com>wrote:
>
>> It should be inside this directory with a name like the maven coordinates
>>
>> Em 08/01/2014, às 20:11, "Ivan St. Ivanov" <ivan.st.ivanov(a)gmail.com>
>> escreveu:
>>
>> Ah, so it takes it from ~/forge/addons?
>>
>>
>> On Thu, Jan 9, 2014 at 12:10 AM, George Gastaldi <ggastald(a)redhat.com>wrote:
>>
>>> It belongs to the addons project afaik.
>>>
>>> Run a mvn clean install, go to dist/target, unzip the file and run forge
>>> -i org.jboss.forge.addon:core,2.0.0-SNAPSHOT
>>> The
>>>
>>> Em 08/01/2014, às 20:08, "Ivan St. Ivanov" <ivan.st.ivanov(a)gmail.com>
>>> escreveu:
>>>
>>> Hmm, there is no such command addon-list in my forge installation, that
>>> is why the command fails. Most probably the command was recently added, as
>>> I see it in Eclipse.
>>>
>>> AddonListCommandTest has declared an addon dependency
>>> to org.jboss.forge.addon:addon-manager. Where does it take it from?
>>>
>>>
>>> On Wed, Jan 8, 2014 at 11:53 PM, George Gastaldi <ggastald(a)redhat.com>wrote:
>>>
>>>> This looks like a bug in the shell impl or aesh itself. Try running the
>>>> "addon-list" command in a running Forge 2 instance to check the output
>>>>
>>>> > Em 08/01/2014, às 19:46, "Ivan St. Ivanov" <ivan.st.ivanov(a)gmail.com>
>>>> escreveu:
>>>> >
>>>> > Hi George,
>>>> >
>>>> > As I promised you, I ran the Forge 2 core tests. Initially the maven
>>>> impl tests failed, because my settings.xml pointed to the snapshots
>>>> repository, while the test was trying to access artifacts from version
>>>> 2.0.0.Alpha3, which can be found in the releases repository. After changing
>>>> the repo to releases, the test passed.
>>>> >
>>>> > Next, I got a failure in AddonListCommandTest::testAddonListCommand.
>>>> The reason is timeout: 10 seconds are not enough for the test to pass. Do
>>>> you know how I can look for the reason?
>>>> >
>>>> > Thanks,
>>>> > Ivan
>>>>
>>>
>>>
>>
>
11 years, 10 months
Help create new type of forge project
by Rafael Pestano
Hi guys,
I've created a new type of project in my forge plugin, also created a
specific locator for it. After my project is found by
ProjectFactory#findProjectRecursively() it tries to register every possible
facet:
if (project != null) {
registerFacets(project);
}
in registerFacet we have:
Set<Class<? extends Facet>> facets = facetFactory.getFacetTypes();
for (Class<? extends Facet> facet : facets)
{
registerSingleFacet(project, facet);
}
and i got Facet not found exception(The requested facet of type
[org.jboss.forge.project.facets.DependencyFacet] was not found.), here is
the stacktrace:
***ERROR*** Exception encountered: (type "set VERBOSE false" to disable
stack traces)
org.jboss.forge.project.facets.FacetNotFoundException: The requested facet
of type [org.jboss.forge.project.facets.DependencyFacet] was not found. The
facet is not installed.
at
org.jboss.forge.project.BaseProject.getFacet(BaseProject.java:103)
at
br.ufrgs.rmpestano.intrabundle.model.OSGiProject.getFacet(OSGiProject.java:35)
at
org.jboss.forge.spec.javaee.BaseJavaEEFacet.isInstalled(BaseJavaEEFacet.java:62)
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.findProjectRecursively(ProjectFactory.java:117)
at
org.jboss.forge.shell.project.ProjectInitializer.doInit(ProjectInitializer.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
is it normal behavior of Forge(try to install all available facets) or i
did something wrong?
The project type i've created is not maven based so hence dependency facet
must no be installed.
the project can be found here:
https://github.com/rmpestano/intrabundle
BundlePluginTest reproduces my issue.
thanks in advance.
--
<http://www.advancedit.com.br/>Att,
Rafael M. Pestano
Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
Graduando em Ciência da Computação UFRGS
http://conventionsframework.org <http://conventions.github.io/home/>
http://rpestano.wordpress.com/
@realpestano
11 years, 11 months
Obtaining project name in persistence provider
by Ivan St. Ivanov
Hi folks,
I am working on https://issues.jboss.org/browse/FORGE-1443. It's not a big
deal, it's a matter of adding a few lines to the JavaEEDefaultProvider
class.
One of the requirements is that the create and drop scripts should bear the
name of the project: <projectName>Creade.ddl and <projectName>Drop.ddl. I
wonder is there a way to pass that somehow to the persistence provider?
Thanks,
Ivan
11 years, 11 months