1:24 p.m.
I got done with a Skype conversation with Alexey Kazakov on how JBoss Tools
will interact with the new Seam 2.3. The points are below. Some further
questions are asked below. Many of you already know most of what is going
on, this email is for clarification, information and to make this process
as public as possible.
* Latest JBT is used with Eclipse 3.7.2 Indigo
* Seam 2.3 uses maven, therefore all dependencies are done through maven
* JBT WILL NOT be using Maven
* JBT only needs the initial seam distribution (zip file with lib) to have
everything it needs to create a seam web project.
* Once JBT has the initial distribution and libraries it can then use that
to create a seam web project.
* If the end user wishes to use JBT, they have to download the
distribution, map it to SEAM_HOME.
* If the end user doesn't wish to use JBT, they can just add dependencies
to their maven pom files, and do what they want.
* If the end user wants to use JBT AND Maven, that will not be supported
currently (Need Verification)
* JBT will expect that the end distribution of Seam will have a lib folder
with required jars, a list of jars, and a seam.sh and seam.bat to run
seam-gen
* Seam 2.3 has a distribution module that creates the final distribution
and uses the assembly plugin to achieve what JBT needs, this is the focus
currently:
https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/distribu...
* JBT will still require seam.bat or seam.sh scripts so it can create
entities and actions and that is already part of the current distribution
https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/distribu...
If this is not correct, please correct since if there is something wrong,
it's because of a lack of understanding on my part.
Hope this is beneficial.
Danno
1:49 p.m.
New subject: [jbosstools-dev] What is expected of JBoss Seam 2.3 for JBoss Tools
See my comments below.
On 05/02/2012 11:24 AM, Daniel Hinojosa wrote:
* Latest JBT is used with Eclipse 3.7.2 Indigo
* Seam 2.3 uses maven, therefore all dependencies are done through maven
* JBT WILL NOT be using Maven
I would say JBoss Tools Seam Wizards (New Project,
Action, Form, etc.)
are not going to use Maven. But JBT has some maven features (seam
support enabled automatically if you import a maven project with seam
dependencies, mavenized seam project examples, etc.)
* JBT only needs the initial seam distribution (zip file with lib)
to
have everything it needs to create a seam web project.
* Once JBT has the initial distribution and libraries it can then use
that to create a seam web project.
* If the end user wishes to use JBT, they have to download the
distribution, map it to SEAM_HOME.
JBT does not use SEAM_HOME at all. We use our
internal settings for
eclipse projects to map it to the seam distribution.
* If the end user doesn't wish to use JBT, they can just add
dependencies to their maven pom files, and do what they want.
Again, JBT can help
here too, but if we are talking about Seam Wizards
then this is correct.
* If the end user wants to use JBT AND Maven, that will not be
supported currently (Need Verification)
Not supported by Seam Wizards. Since they
are seam-gen based. All the
problems we have right now are related to our Seam Wizards. Our seam
maven integration works fine afaik. Just to be clear.
* JBT will expect that the end distribution of Seam will have a lib
folder with required jars, a list of jars, and a seam.sh and seam.bat
to run seam-gen
JBT does not use seam.sh, seam.bat or any scripts directly. We used
them
only during development to mimic its logic. But we still need the lib
folder, the list of jars and templates (xhtmls, xmls, etc) and hope the
scripts won't change much so we won't have to rewrite our wizards
completely.
* Seam 2.3 has a distribution module that creates the final
distribution and uses the assembly plugin to achieve what JBT needs,
this is the focus currently:
https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/distribu...
* JBT will still require seam.bat or seam.sh scripts so it can create
entities and actions and that is already part of the current distribution
https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/distribu...
Again, JBT doesn't use seam scripts. See the previous comment.
If this is not correct, please correct since if there is something
wrong, it's because of a lack of understanding on my part.
Hope this is beneficial.
Danno
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
2:08 p.m.
New subject: [jbosstools-dev] What is expected of JBoss Seam 2.3 for JBoss Tools
Great to know.. Thanks, Alexey
On Wed, May 2, 2012 at 12:49 PM, Alexey Kazakov <akazakov(a)exadel.com> wrote:
See my comments below.
On 05/02/2012 11:24 AM, Daniel Hinojosa wrote:
* Latest JBT is used with Eclipse 3.7.2 Indigo
* Seam 2.3 uses maven, therefore all dependencies are done through maven
* JBT WILL NOT be using Maven
I would say JBoss Tools Seam Wizards (New Project, Action, Form, etc.) are
not going to use Maven. But JBT has some maven features (seam support
enabled automatically if you import a maven project with seam dependencies,
mavenized seam project examples, etc.)
* JBT only needs the initial seam distribution (zip file with lib) to
have everything it needs to create a seam web project.
* Once JBT has the initial distribution and libraries it can then use
that to create a seam web project.
* If the end user wishes to use JBT, they have to download the
distribution, map it to SEAM_HOME.
JBT does not use SEAM_HOME at all. We use our internal settings for
eclipse projects to map it to the seam distribution.
* If the end user doesn't wish to use JBT, they can just add
dependencies to their maven pom files, and do what they want.
Again, JBT can help here too, but if we are talking about Seam Wizards
then this is correct.
* If the end user wants to use JBT AND Maven, that will not be
supported currently (Need Verification)
Not supported by Seam Wizards. Since they are seam-gen based. All the
problems we have right now are related to our Seam Wizards. Our seam maven
integration works fine afaik. Just to be clear.
* JBT will expect that the end distribution of Seam will have a lib
folder with required jars, a list of jars, and a seam.sh and seam.bat to
run seam-gen
JBT does not use seam.sh, seam.bat or any scripts directly. We used them
only during development to mimic its logic. But we still need the lib
folder, the list of jars and templates (xhtmls, xmls, etc) and hope the
scripts won't change much so we won't have to rewrite our wizards
completely.
* Seam 2.3 has a distribution module that creates the final
distribution and uses the assembly plugin to achieve what JBT needs, this
is the focus currently:
https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/distribu...
* JBT will still require seam.bat or seam.sh scripts so it can create
entities and actions and that is already part of the current distribution
https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/distribu...
Again, JBT doesn't use seam scripts. See the previous comment.
If this is not correct, please correct since if there is something
wrong, it's because of a lack of understanding on my part.
Hope this is beneficial.
Danno
_______________________________________________
jbosstools-dev mailing
listjbosstools-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Daniel Hinojosa
Programmer, Instructor, and Consultant
dhinojosa(a)evolutionnext.com
http://www.evolutionnext.com
http://www.abqjug.org
2:15 p.m.
New subject: [jbosstools-dev] What is expected of JBoss Seam 2.3 for JBoss Tools
Dan,
Alexey commented your points/questions fairly well, so I hope you have
clear understanding now ;-)
Just short summary:
1. Distribution assembly is Seam 2 support for ant users and seam-gen.
(Maven users don't care much about distribution files)
2. Seam-gen is command line tool and JBoss Tools wizards mimic only
invocations of these seam-gen command and collects inputs from user to
create Seam projects/components/actions/forms etc.
3. JBoss Tools relies on seam-gen file templates, therefore what we will
update and works in pure seam-gen, it should be used in JBoss Tools
without issues and just works.
On 2.5.2012 20:49, Alexey Kazakov wrote:
See my comments below.
On 05/02/2012 11:24 AM, Daniel Hinojosa wrote:
> * Latest JBT is used with Eclipse 3.7.2 Indigo
> * Seam 2.3 uses maven, therefore all dependencies are done through maven
> * JBT WILL NOT be using Maven
I would say JBoss Tools Seam Wizards (New Project, Action, Form, etc.)
are not going to use Maven. But JBT has some maven features (seam
support enabled automatically if you import a maven project with seam
dependencies, mavenized seam project examples, etc.)
> * JBT only needs the initial seam distribution (zip file with lib) to
> have everything it needs to create a seam web project.
> * Once JBT has the initial distribution and libraries it can then use
> that to create a seam web project.
> * If the end user wishes to use JBT, they have to download the
> distribution, map it to SEAM_HOME.
JBT does not use SEAM_HOME at all. We use our internal settings for
eclipse projects to map it to the seam distribution.
> * If the end user doesn't wish to use JBT, they can just add
> dependencies to their maven pom files, and do what they want.
Again, JBT can help here too, but if we are talking about Seam Wizards
then this is correct.
> * If the end user wants to use JBT AND Maven, that will not be
> supported currently (Need Verification)
Not supported by Seam Wizards. Since they are seam-gen based. All the
problems we have right now are related to our Seam Wizards. Our seam
maven integration works fine afaik. Just to be clear.
> * JBT will expect that the end distribution of Seam will have a lib
> folder with required jars, a list of jars, and a seam.sh and seam.bat
> to run seam-gen
JBT does not use seam.sh, seam.bat or any scripts directly. We used them
only during development to mimic its logic. But we still need the lib
folder, the list of jars and templates (xhtmls, xmls, etc) and hope the
scripts won't change much so we won't have to rewrite our wizards
completely.
> * Seam 2.3 has a distribution module that creates the final
> distribution and uses the assembly plugin to achieve what JBT needs,
> this is the focus currently:
> https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/distribu...
> * JBT will still require seam.bat or seam.sh scripts so it can create
> entities and actions and that is already part of the current distribution
>
https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/distribu...
>
Again, JBT doesn't use seam scripts. See the previous comment.
>
>
> If this is not correct, please correct since if there is something
> wrong, it's because of a lack of understanding on my part.
>
> Hope this is beneficial.
>
> Danno
>
>
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Marek Novotny
--
JBoss Seam and WFK Productization Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
Email: mnovotny(a)redhat.com
Office phone: +420 532 294 287, ext. 82-62 087
mobile: +420 608 509 230
4414
days inactive
4414
days old
3 comments
3 participants
participants (3)
-
Alexey Kazakov -
Daniel Hinojosa -
Marek Novotny