How to choose which Java EE version ?
by Antonio Goncalves
Hi all,
I've realized that I wrote on the forum (
https://community.jboss.org/thread/231843), but maybe the development ML
would have been more appropriate. Here are some thoughts and questions
about "how to ask Forge to generate a Java EE 6 or Java EE 7 application" :
----------------------------
Java EE 7 is out... and one day will come Java EE 8, 9 and so on. So we
should be able to ask JBoss Forge to either generate a Java EE 6 or 7
application... and if we want to be more precise, you could even go into
choosing from Java EE 6, Web Profile 6, Java EE 7 and a Web Profile 7
application. But how to choose a version with JBoss Forge ?
Today, with JBoss Forge 1.x, you create a project with a CLI without giving
any version indication :
1. new-project --named app1 --topLevelPackage org.app1 --type war
Then, when you setup your project, you give Forge some hints :
1.
persistence setup --provider ECLIPSELINK --container GLASSFISH_3
--named testPU ;
2. validation setup --provider HIBERNATE_VALIDATOR ;
If the idea is to use Forge to create Java EE applications running in a
container (and not just in standalone Java SE), the CLI to create a project
misses some information, and the setup is redundant. I would think of
something like :
1.
new-project --named app1 (...) --version JAVAEE_7 --container GLASSFISH
2.
new-project --named app1 (...) --version JAVAEE_6 --container GLASSFISH
3.
new-project --named app1 (...) --version JAVAEE_WEBPROFILE_6
--container GLASSFISH
4.
new-project --named app1 (...) --version JAVAEE_WEBPROFILE_7
--container GLASSFISH
Note that I didn't put the version of GlassFish because the version of Java
EE implies the version of GlassFish (eg. Java EE 6 == GlassFish 3, Java EE
7 == GlassFish 4). But note that you could also specify the container if
needed (e.g. generate a Java EE 6 app running on GlassFish 4)
1.
new-project --named app1 (...) --version JAVAEE_6 --container GLASSFISH_4
And, of course, the following would be illegal (GF 3 cannot run a Java EE 7
app) :
1.
new-project --named app1 (...) --version JAVAEE_7 --container GLASSFISH_3
On this comment<https://issues.jboss.org/browse/FORGE-1067?focusedCommentId=12794855&page...>,
Lincoln says that the application should only depend on Java EE APIs. So I
think the pom.xml should only contain one of the following dependency
(depending on the version of Java EE 7) :
1. <dependency>
2. <groupId>javax</groupId>
3. <artifactId>javaee-api</artifactId>
4. <version>7.0</version>
5. </dependency>
6. <dependency>
7. <groupId>javax</groupId>
8. <artifactId>javaee-api</artifactId>
9. <version>6.0</version>
10. </dependency>
11. <dependency>
12. <groupId>javax</groupId>
13. <artifactId>javaee-web-api</artifactId>
14. <version>7.0</version>
15. </dependency>
16. <dependency>
17. <groupId>javax</groupId>
18. <artifactId>javaee-web-api</artifactId>
19. <version>6.0</version>
20. </dependency>
You do not need any extra dependency if you want an application to depend
only on Java EE. So that means the following commands can also be changed
from :
1.
persistence setup --provider ECLIPSELINK --container GLASSFISH_3
--named testPU ;
2. validation setup --provider HIBERNATE_VALIDATOR ;
to
1. persistence setup --named testPU ;
2. validation setup ;
No need to specify the provider. That's because you will use the JPA/Bean
Validation/... default implementation of the container (GlassFish uses
EclipseLink, JBoss uses Hibernate...). And to ease the configuration and
portability, this means that you don't need the <provider> element in the
persistence.xml :
1. <?xml version="1.0" encoding="UTF-8" standalone="no"?>
2. <persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi=
"http://www.w3.org/2001/XMLSchema-instance" version="2.0"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
3. <persistence-unit name="javaone2013PU" transaction-type="JTA">
4. <provider>org.eclipse.persistence.jpa.PersistenceProvider</
provider>
5. (...)
6. </persistence-unit>
7. </persistence>
Nor do you use the <default-provider> element in the validation.xml (and so
on).
I think the Java EE version should be specified when the project is
created, and then all the setups would use the default container
implementation.
--
Antonio Goncalves
Software architect and Java Champion
Web site <http://www.antoniogoncalves.org/> |
Twitter<http://twitter.com/agoncal>
| LinkedIn <http://www.linkedin.com/in/agoncal> | Paris
JUG<http://www.parisjug.org/>
| Devoxx France <http://www.devoxx.fr/>
12 years, 8 months
Fwd: Git tools
by George Gastaldi
The configuration looks ok. I may be missing something
George Gastaldi | Senior Software Engineer
JBoss Forge Team
Red Hat
-------- Original Message --------
Subject: Git tools
Date: Mon, 9 Sep 2013 18:34:05 +0300
From: Ivan St. Ivanov <ivan.st.ivanov(a)gmail.com>
To: George Gastaldi <ggastald(a)redhat.com>
Hey Gastaldi,
I have attached an archive of the git-tools addon together with a small
change in the parent pom (the jgit version).
As I wrote in the chat, I get the following error ATM:
SEVERE: Failed to start addon
[org.jboss.forge.addon:git-tools,2.0.0-SNAPSHOT] with classloader
[ModuleClassLoader for Module
"org.jboss.forge.addon.git-tools:2.0.0-SNAPSHOT_384942ba-8666-45c0-ae26-3c918c8f6b29"
from AddonModuleLoader]
org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
dependencies for type [GitIgnoreConfig] with qualifiers [@Default] at
injection point [[BackedAnnotatedField] @Inject private
org.jboss.forge.addon.git.facet.GitIgnoreFacetImpl.config]
at
org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:405)
at
org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:327)
at
org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:178)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:209)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:521)
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:507)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:482)
at
org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:538)
at
org.jboss.weld.bootstrap.api.helpers.ForwardingBootstrap.validateBeans(ForwardingBootstrap.java:75)
at org.jboss.weld.environment.se.Weld.initialize(Weld.java:144)
at
org.jboss.forge.furnace.container.cdi.lifecycle.WeldAddonLifecycleProvider.start(WeldAddonLifecycleProvider.java:59)
at
org.jboss.forge.furnace.impl.addons.AddonRunnable$1.call(AddonRunnable.java:77)
at
org.jboss.forge.furnace.impl.addons.AddonRunnable$1.call(AddonRunnable.java:71)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
at
org.jboss.forge.furnace.impl.addons.AddonRunnable.run(AddonRunnable.java:70)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Thanks,
Ivan
12 years, 9 months
Strange forge behaviour?
by Lennart Jörelid
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(a)jguru.se
| URL: www.jguru.se
| Phone
| (skype): jgurueurope
| (intl): +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+
12 years, 10 months
Add means of defining constraint for Length on String
by Robb Greathouse
Hi,
Was trying to change the length on String from the VarChar(255). In Hibernate this can be done by specifying @Length(max=350) (for example.
However, there is no "constraint Length --onProperty xxx --max 350" available in Forge.
Using "constraint Max" causes forge to have a conversion error when attempting to insert string data.
Robb Greathouse
Partner Enablement
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
12 years, 10 months
JAXB unmarshalling in forge plugin
by Luca Masini
Hi guys, I'm developing a plugin where I need to unmarshal some beans using
JAXB.
The parsing works great outside forge, but when I try to execute the same
code inside a plugin I got this Exception:
javax.xml.bind.JAXBException
- with linked exception:
[java.lang.ClassNotFoundException:
com.sun.xml.internal.bind.v2.ContextFactory from [Module
"it.xxxxxxx.forge.prova-plugin:1.0.0-SNAPSHOT-c1d512df-2daa-4ebe-ae7a-154e102bb88d"
from local module loader @15aaf0b3 (roots:
/Applications/sviluppo/jboss/forge-distribution-1.4.0.Final/modules,/Users/ictlm1/.forge/plugins,/Users/ictlm1/Documents/progetti/forge)]]
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:187)
at javax.xml.bind.ContextFinder.find(ContextFinder.java:376)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522)
at it.xxx.forge.parser.Parser.parse(Parser.java:17)
at
it.xxx.forge.forge.CreateEntitiesPlugin.parse(CreateEntitiesPlugin.java:19)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.forge.shell.command.Execution.perform(Execution.java:160)
...
...
Caused by: java.lang.ClassNotFoundException:
com.sun.xml.internal.bind.v2.ContextFactory from [Module
"it.esselunga.forge.prova-plugin:1.0.0-SNAPSHOT-c1d512df-2daa-4ebe-ae7a-154e102bb88d"
from local module loader @15aaf0b3 (roots:
/Applications/sviluppo/jboss/forge-distribution-1.4.0.Final/modules,/Users/ictlm1/.forge/plugins,/Users/ictlm1/Documents/progetti/forge)]
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:481)
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:185)
... 41 more
ContextFactory is part of rt.jar with is bundled with the JDK, how can I
tell the ModuleClassLoader to let me load it ??
Thank you.
--
****************************************
http://www.lucamasini.net
http://twitter.com/lmasini
http://www.linkedin.com/pub/luca-masini/7/10/2b9
****************************************
12 years, 10 months
Forge console UX improvement
by George Gastaldi
Hello all,
I found http://finalterm.org as a nice terminal evolution. Wonder if we can do something like that in Forge 2+ console (the context menu and the clickable links)?
Best Regards,
George Gastaldi
12 years, 10 months
Re: [forge-dev] forge-dev Digest, Vol 33, Issue 10
by Valmir Justo
Hi Gastaldi,
So, I have been write a article using JBoss Forge, and, one situation
propose is "How the Jboss Forge is very simple to create same projects,
Faces, AngularJS, Spring, etc."
In this case, i test the angularJS and don't have problem.
I understand which the Scaffold of Spring is not maintained by RedHat,
however the framework have a big acceptance in the market.
Tks for reply
Best Regards!
Valmir Justo
On Thu, Sep 5, 2013 at 8:27 AM, <forge-dev-request(a)lists.jboss.org> wrote:
> Send forge-dev mailing list submissions to
> forge-dev(a)lists.jboss.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.jboss.org/mailman/listinfo/forge-dev
> or, via email, send a message with subject or body 'help' to
> forge-dev-request(a)lists.jboss.org
>
> You can reach the person managing the list at
> forge-dev-owner(a)lists.jboss.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of forge-dev digest..."
>
>
> Today's Topics:
>
> 1. [Scaffold Spring Problem] (Valmir Justo)
> 2. Re: [Scaffold Spring Problem] (George Gastaldi)
> 3. Fwd: [Scaffold Spring Problem] (Valmir Justo)
> 4. Re: Checking in on Gradle Addon (Max Rydahl Andersen)
> 5. Re: Checking in on Gradle Addon (Lincoln Baxter, III)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 4 Sep 2013 15:47:17 -0300
> From: Valmir Justo <justoeu(a)gmail.com>
> Subject: [forge-dev] [Scaffold Spring Problem]
> To: forge-dev(a)lists.jboss.org
> Message-ID:
> <
> CANEMeo4nTDe-w6ghe7RDASeLJSh6FhFnkX8L6FUbbnxXF_ce5g(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> My name is Valmir. I have been using the JBoss forge the 3 months ago.
> I started the simple project, new-project, persistence setup, scaffold
> --Type spring etc.
>
> However, I have tried use the scaffold spring and when i execute the
> command-line scaffold from-entity 'name Entity' and receive the
> printStackTrace:
>
> Exception encountered:
> org.metawidget.util.simple.StringUtils.isCapitalized(Ljava/lang/String;)Z
> (type "set VERBOSE true" to enable stack traces).
>
> Set the VERBOSE mode,
>
> java.lang.NoSuchMethodError:
> org.metawidget.util.simple.StringUtils.isCapitalized(Ljava/lang/String;)Z
>
> at
>
> org.jboss.forge.scaffold.spring.metawidget.inspector.propertystyle.ForgePropertyStyle.isGetter(ForgePropertyStyle.java:250)
>
> at
>
> org.jboss.forge.scaffold.spring.metawidget.inspector.propertystyle.ForgePropertyStyle.lookupGetters(ForgePropertyStyle.java:198)
>
> at
>
> org.jboss.forge.scaffold.spring.metawidget.inspector.propertystyle.ForgePropertyStyle.inspectProperties(ForgePropertyStyle.java:151)
>
> at
>
> org.metawidget.inspector.impl.propertystyle.BasePropertyStyle.getUncachedTraits(BasePropertyStyle.java:172)
>
> at
>
> org.metawidget.inspector.impl.BaseTraitStyle.getTraits(BaseTraitStyle.java:126)
>
> I look for the internet but without success.
>
> Could help me?
>
> Tks
>
> Best regards.
>
> Valmir Justo
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/forge-dev/attachments/20130904/06f3b439/...
>
> ------------------------------
>
> Message: 2
> Date: Wed, 04 Sep 2013 15:53:17 -0300
> From: George Gastaldi <ggastald(a)redhat.com>
> Subject: Re: [forge-dev] [Scaffold Spring Problem]
> To: forge-dev(a)lists.jboss.org
> Message-ID: <5227819D.2010504(a)redhat.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Justo,
>
> It looks like that the Spring Scaffold is using an older version of
> Metawidget. Afaik, this plugin is not maintained by RedHat and it's from
> the community.
>
> Have you tried the angularjs scaffold? Is so much better, well-tested
> and very mobile friendly. Install it by typing: forge install angularjs
>
> Best Regards !
>
> George Gastaldi
>
> On 09/04/2013 03:47 PM, Valmir Justo wrote:
> > Hi,
> >
> > My name is Valmir. I have been using the JBoss forge the 3 months ago.
> > I started the simple project, new-project, persistence setup, scaffold
> > --Type spring etc.
> >
> > However, I have tried use the scaffold spring and when i execute the
> > command-line scaffold from-entity 'name Entity' and receive the
> > printStackTrace:
> >
> > Exception encountered:
> > org.metawidget.util.simple.StringUtils.isCapitalized(Ljava/lang/String;)Z
> > (type "set VERBOSE true" to enable stack traces).
> >
> > Set the VERBOSE mode,
> >
> > java.lang.NoSuchMethodError:
> > org.metawidget.util.simple.StringUtils.isCapitalized(Ljava/lang/String;)Z
> >
> > at
> >
> org.jboss.forge.scaffold.spring.metawidget.inspector.propertystyle.ForgePropertyStyle.isGetter(ForgePropertyStyle.java:250)
> >
> > at
> >
> org.jboss.forge.scaffold.spring.metawidget.inspector.propertystyle.ForgePropertyStyle.lookupGetters(ForgePropertyStyle.java:198)
> >
> > at
> >
> org.jboss.forge.scaffold.spring.metawidget.inspector.propertystyle.ForgePropertyStyle.inspectProperties(ForgePropertyStyle.java:151)
> >
> > at
> >
> org.metawidget.inspector.impl.propertystyle.BasePropertyStyle.getUncachedTraits(BasePropertyStyle.java:172)
> >
> > at
> >
> org.metawidget.inspector.impl.BaseTraitStyle.getTraits(BaseTraitStyle.java:126)
> >
> > I look for the internet but without success.
> >
> > Could help me?
> >
> > Tks
> >
> > Best regards.
> >
> > Valmir Justo
> >
> >
> >
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/forge-dev/attachments/20130904/bd390617/...
>
> ------------------------------
>
> Message: 3
> Date: Wed, 4 Sep 2013 16:02:34 -0300
> From: Valmir Justo <justoeu(a)gmail.com>
> Subject: [forge-dev] Fwd: [Scaffold Spring Problem]
> To: forge-dev <forge-dev(a)lists.jboss.org>
> Message-ID:
> <CANEMeo7WimWeEnNsRPPvOEuCiNXFOS1=
> 0+i1PkwpSQRCrF0azQ(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> My name is Valmir. I have been using the JBoss forge the 3 months ago.
> I started the simple project, new-project, persistence setup, scaffold
> --Type spring etc.
>
> However, I have tried use the scaffold spring and when i execute the
> command-line scaffold from-entity 'name Entity' and receive the
> printStackTrace:
>
> Exception encountered:
> org.metawidget.util.simple.StringUtils.isCapitalized(Ljava/lang/String;)Z
> (type "set VERBOSE true" to enable stack traces).
>
> Set the VERBOSE mode,
>
> java.lang.NoSuchMethodError:
> org.metawidget.util.simple.StringUtils.isCapitalized(Ljava/lang/String;)Z
>
> at
>
> org.jboss.forge.scaffold.spring.metawidget.inspector.propertystyle.ForgePropertyStyle.isGetter(ForgePropertyStyle.java:250)
>
> at
>
> org.jboss.forge.scaffold.spring.metawidget.inspector.propertystyle.ForgePropertyStyle.lookupGetters(ForgePropertyStyle.java:198)
>
> at
>
> org.jboss.forge.scaffold.spring.metawidget.inspector.propertystyle.ForgePropertyStyle.inspectProperties(ForgePropertyStyle.java:151)
>
> at
>
> org.metawidget.inspector.impl.propertystyle.BasePropertyStyle.getUncachedTraits(BasePropertyStyle.java:172)
>
> at
>
> org.metawidget.inspector.impl.BaseTraitStyle.getTraits(BaseTraitStyle.java:126)
>
> I look for the internet but without success.
>
> Could help me?
>
> Tks
>
> Best regards.
>
> Valmir Justo
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/forge-dev/attachments/20130904/08d0d750/...
>
> ------------------------------
>
> Message: 4
> Date: Thu, 5 Sep 2013 09:33:27 +0200
> From: Max Rydahl Andersen <manderse(a)redhat.com>
> Subject: Re: [forge-dev] Checking in on Gradle Addon
> To: forge-dev List <forge-dev(a)lists.jboss.org>
> Message-ID: <20130905073327.GP62519(a)slowbeard.local>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> On Wed, Sep 04, 2013 at 12:22:09PM -0400, Lincoln Baxter, III wrote:
> >I was unable to install that for some reason. "Functionality is no longer
> >available."
>
> where did you get that message ?
>
> one way to get it is:
> http://marketplace.eclipse.org/content/gradle-integration-eclipse#.UigzrL...
>
> /max
>
> >
> >On Wed, Sep 4, 2013 at 12:19 PM, Max Andersen <manderse(a)redhat.com>
> wrote:
> >
> >> Doesn't the eclipse plugin for Gradle do this automatically and better
> by
> >> now ?
> >>
> >> /max (sent from my phone)
> >>
> >>
> >> On 04/09/2013, at 18.13, "Lincoln Baxter, III" <lincolnbaxter(a)gmail.com
> >
> >> wrote:
> >>
> >> Hey Adam,
> >>
> >> Seems like things have been a bit quiet, but I've been reviewing the
> Forge
> >> Gradle Addon, and it's looking good! I've reproduced the dependency
> >> resolution issue you ran in to, but I'm not exactly sure where the error
> >> lies. Looking in to it.
> >>
> >> You asked what to work on next. And I think that if you have finished
> all
> >> of the core/required functionality, it might be interesting to add a
> Forge
> >> UICommand/UIWizard to set up this eclipse config:
> >>
> >> http://www.gradle.org/docs/current/userguide/eclipse_plugin.html
> >>
> >> That should make it easier for people to import Gradle projects into
> >> eclipse. Do you think this has value?
> >>
> >> Alternatively, have you tested the scenario where a user attempts to use
> >> an existing Gradle project with Forge? It does not appear that this is
> >> tested yet, so that might be useful to explore. I believe this may
> raise a
> >> few new issues like, "Should we modify the user's gradle.build script in
> >> order to support Forge operations?" and "How should we ask them?"
> >>
> >> It's possible that you could simply create a temporary build descriptor
> >> with the required forge library, execute that, then delete it. Or
> perhaps a
> >> new command in Forge to "Make a gradle project editable by forge."
> >>
> >> Thoughts?
> >>
> >> --
> >> Lincoln Baxter, III
> >> http://ocpsoft.org
> >> "Simpler is better."
> >>
> >> _______________________________________________
> >> forge-dev mailing list
> >> forge-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/forge-dev
> >>
> >>
> >> _______________________________________________
> >> forge-dev mailing list
> >> forge-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/forge-dev
> >>
> >
> >
> >
> >--
> >Lincoln Baxter, III
> >http://ocpsoft.org
> >"Simpler is better."
>
> >_______________________________________________
> >forge-dev mailing list
> >forge-dev(a)lists.jboss.org
> >https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 5 Sep 2013 07:27:04 -0400
> From: "Lincoln Baxter, III" <lincolnbaxter(a)gmail.com>
> Subject: Re: [forge-dev] Checking in on Gradle Addon
> To: forge-dev List <forge-dev(a)lists.jboss.org>
> Message-ID:
> <
> CAEp_U4G20C_tSm7HyuY0owcD5-SyftWUqOPLLVBGuKML3625tQ(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> >From the eclipse marketplace :)
>
> ---
> Lincoln Baxter's Droid
> http://ocpsoft.org
> "Keep it Simple"
> On Sep 5, 2013 4:27 AM, "Max Rydahl Andersen" <manderse(a)redhat.com> wrote:
>
> > On Wed, Sep 04, 2013 at 12:22:09PM -0400, Lincoln Baxter, III wrote:
> > >I was unable to install that for some reason. "Functionality is no
> longer
> > >available."
> >
> > where did you get that message ?
> >
> > one way to get it is:
> >
> http://marketplace.eclipse.org/content/gradle-integration-eclipse#.UigzrL...
> >
> > /max
> >
> > >
> > >On Wed, Sep 4, 2013 at 12:19 PM, Max Andersen <manderse(a)redhat.com>
> > wrote:
> > >
> > >> Doesn't the eclipse plugin for Gradle do this automatically and better
> > by
> > >> now ?
> > >>
> > >> /max (sent from my phone)
> > >>
> > >>
> > >> On 04/09/2013, at 18.13, "Lincoln Baxter, III" <
> lincolnbaxter(a)gmail.com
> > >
> > >> wrote:
> > >>
> > >> Hey Adam,
> > >>
> > >> Seems like things have been a bit quiet, but I've been reviewing the
> > Forge
> > >> Gradle Addon, and it's looking good! I've reproduced the dependency
> > >> resolution issue you ran in to, but I'm not exactly sure where the
> error
> > >> lies. Looking in to it.
> > >>
> > >> You asked what to work on next. And I think that if you have finished
> > all
> > >> of the core/required functionality, it might be interesting to add a
> > Forge
> > >> UICommand/UIWizard to set up this eclipse config:
> > >>
> > >> http://www.gradle.org/docs/current/userguide/eclipse_plugin.html
> > >>
> > >> That should make it easier for people to import Gradle projects into
> > >> eclipse. Do you think this has value?
> > >>
> > >> Alternatively, have you tested the scenario where a user attempts to
> use
> > >> an existing Gradle project with Forge? It does not appear that this is
> > >> tested yet, so that might be useful to explore. I believe this may
> > raise a
> > >> few new issues like, "Should we modify the user's gradle.build script
> in
> > >> order to support Forge operations?" and "How should we ask them?"
> > >>
> > >> It's possible that you could simply create a temporary build
> descriptor
> > >> with the required forge library, execute that, then delete it. Or
> > perhaps a
> > >> new command in Forge to "Make a gradle project editable by forge."
> > >>
> > >> Thoughts?
> > >>
> > >> --
> > >> Lincoln Baxter, III
> > >> http://ocpsoft.org
> > >> "Simpler is better."
> > >>
> > >> _______________________________________________
> > >> forge-dev mailing list
> > >> forge-dev(a)lists.jboss.org
> > >> https://lists.jboss.org/mailman/listinfo/forge-dev
> > >>
> > >>
> > >> _______________________________________________
> > >> forge-dev mailing list
> > >> forge-dev(a)lists.jboss.org
> > >> https://lists.jboss.org/mailman/listinfo/forge-dev
> > >>
> > >
> > >
> > >
> > >--
> > >Lincoln Baxter, III
> > >http://ocpsoft.org
> > >"Simpler is better."
> >
> > >_______________________________________________
> > >forge-dev mailing list
> > >forge-dev(a)lists.jboss.org
> > >https://lists.jboss.org/mailman/listinfo/forge-dev
> >
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/forge-dev/attachments/20130905/947d3311/...
>
> ------------------------------
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
> End of forge-dev Digest, Vol 33, Issue 10
> *****************************************
>
12 years, 10 months
