What is expected of JBoss Seam 2.3 for JBoss Tools
by Daniel Hinojosa
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
13 years, 10 months
Drools Evaluating Rules
by Sasivarnan Manickam
Hi there,
As per my understanding after inserting the facts the drools rule engine
will match the rules with the facts and agenda will be set. In this case
it check all the things and finally setting the agenda.. Is ther any way we
can control this and check only what we need. Waiting for the reply at the
earliest.
Thanks
13 years, 10 months
Brainstorming: Target Platform for developers too
by Mickael Istria
Hi all,
As you may know, we leverage Target Platform (TP) at build-time to set
up a build path. A TP is basically a list of dependencies we allow for
build to perform. TP are also usable at dev-time in PDE and guarantees
what you can depend on when you write a plugin. For example, if you
depend on something that is not part of your TP, you'll see some errors
for unresolved bundles.
The next step for this Target Platforms would the *you, developers, use
these target platforms in PDE*. Then we would all ensure we depend on
the same stuff at dev-time and build-time, and it would prevent some
synchronization errors between what you require, and what the TP contain.
You can use TP by importing them into your workspace (checkout
build/target-platform folder), and then enable them with Window >
Preferences > Plugin Development > Target Platform. We already
identified some pitfalls with current TP, but we'll work on making them
more usable for developers. Please report your ideas in JIRA on how to
improve target platforms so that you could use them too. Here are some
first ideas, please contribute to these ideas and raise new ones.
https://issues.jboss.org/browse/JBIDE-11688
https://issues.jboss.org/browse/JBIDE-11689
https://issues.jboss.org/browse/JBIDE-11690
Thanks,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
13 years, 10 months
