Re: [forge-dev] [seam-dev] seam 3 plugins
by Lincoln Baxter, III
Hey guys, what was the outcome of this discussion in the meeting?
If we are centralizing these, we can start today - just let me know and I
will create the repository. Actually I think this makes a lot of sense from
a Seam-user's point of view. Plugins are small and this will prevent a lot
of re-work on the plugin authoring side. (Things like Ken's Seam-Bom
plugin.)
~Lincoln
On Wed, May 25, 2011 at 4:59 PM, José Rodolfo Carrijo de Freitas <
jose.freitas(a)softplan.com.br> wrote:
> +1
>
>
>
> *De:* seam-dev-bounces(a)lists.jboss.org [mailto:
> seam-dev-bounces(a)lists.jboss.org] *Em nome de *George Gastaldi
>
> *Enviada em:* quarta-feira, 25 de maio de 2011 17:55
> *Para:* Dan Allen
> *Cc:* Seam Mailing List; forge-dev List
> *Assunto:* Re: [seam-dev] [forge-dev] seam 3 plugins
>
>
>
> That would be something to discuss now on the seam dev irc meeting
>
>
> Em 25/05/2011, às 17:53, Dan Allen <dan.j.allen(a)gmail.com> escreveu:
>
> Adding seam-dev.
>
> On Wed, May 25, 2011 at 16:50, Paul Bakker <paul.bakker.nl(a)gmail.com>
> wrote:
>
> Hey all,
>
>
>
> Just a thought. Should we create one large plugin project for the Seam 3
> related plugins? Now we split them per Seam3 module. This is nice on a
> development perspective, but not as nice for an end user because you need to
> install 10 different plugins in Forge... So we should either think about a
> packaging mechanism that keeps the code split in different projects on
> github, but still be able to install them in a single command or just put
> them all together in one project.
>
> What are your thoughts?
>
>
>
> Paul
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
>
> --
>
> Dan Allen
>
> Principal Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://www.google.com/profiles/dan.j.allen#about
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
>
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
12 years, 11 months
Re: [forge-dev] [seam-dev] seam 3 plugins
by George Gastaldi
That would be something to discuss now on the seam dev irc meeting
Em 25/05/2011, às 17:53, Dan Allen <dan.j.allen(a)gmail.com> escreveu:
Adding seam-dev.
On Wed, May 25, 2011 at 16:50, Paul Bakker <paul.bakker.nl(a)gmail.com> wrote:
> Hey all,
>
> Just a thought. Should we create one large plugin project for the Seam 3
> related plugins? Now we split them per Seam3 module. This is nice on a
> development perspective, but not as nice for an end user because you need to
> install 10 different plugins in Forge... So we should either think about a
> packaging mechanism that keeps the code split in different projects on
> github, but still be able to install them in a single command or just put
> them all together in one project.
> What are your thoughts?
>
> Paul
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
12 years, 11 months
seam 3 plugins
by Paul Bakker
Hey all,
Just a thought. Should we create one large plugin project for the Seam 3
related plugins? Now we split them per Seam3 module. This is nice on a
development perspective, but not as nice for an end user because you need to
install 10 different plugins in Forge... So we should either think about a
packaging mechanism that keeps the code split in different projects on
github, but still be able to install them in a single command or just put
them all together in one project.
What are your thoughts?
Paul
12 years, 11 months
plugins not recognized any more
by Paul Bakker
Hi all,
With the latest sources plugins are not recognized as plugins any more. When
I use a source-plugin Forge will say:
The project does not appear to be a Forge Plugin Project, install anyway?
[y/N]
After choosing y, everthing just works fine. Something broken in a recent
commit I guess?
Paul
12 years, 11 months
[JBoss JIRA] Created: (SEAMFORGE-189) Field#isType(Class<?> type) method should check if class is part of java.lang package
by Kevin Pollet (JIRA)
Field#isType(Class<?> type) method should check if class is part of java.lang package
-------------------------------------------------------------------------------------
Key: SEAMFORGE-189
URL: https://issues.jboss.org/browse/SEAMFORGE-189
Project: Seam Forge
Issue Type: Bug
Components: Parsers / File Manipulation
Affects Versions: 1.0.0.Alpha3
Reporter: Kevin Pollet
Priority: Critical
Currently, {{Field#isType(Class<?> type)}} method checks if there is an import for the given type (only in some case). If the given class represents a wrapper type like {{Boolean}} this will cause the following test to fail (the java.lang import is not needed):
{code}
JavaClass fooClass = create(JavaClass.class)
.setPackage("com.test")
.setName("Foo");
Field<JavaClass> property = fooClass.addField("private Boolean bar;");
assertTrue(property.isType(Boolean.class));
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months