[jbosside-dev] Fwd: [wtp-dev] hibernatedoclet
by Rob Stryker
Thought I'd forward this in case no one saw it.
---------- Forwarded message ----------
From: jeusdi <cabrejcr(a)terra.es>
Date: Sep 12, 2006 7:19 AM
Subject: [wtp-dev] hibernatedoclet
To: wtp-dev(a)eclipse.org
Hello, I'm using eclipse + WTP and I want to add hibernate capabilities to
my
projec. I wanted to do it using xdoclet, concretelly hibernatedoclet.
However When I see it xdoclet configuration, WTP only detects or shows me
websoclet and ejbdoclet, but in my XDoclet Home directory, I have all
libraries, concretelly xdoclet-hibernate-module-1.2.3.jar. So, How I can add
hibernatedoclet into my eclipse + WTP configuration section?
Thanks for all in adcvanced
--
View this message in context:
http://www.nabble.com/hibernatedoclet-tf2258254.html#a6264026
Sent from the Eclipse WTP - general forum at Nabble.com.
_______________________________________________
wtp-dev mailing list
wtp-dev(a)eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev
17 years, 7 months
Fwd: [jbosside-dev] Re: jBPM Designer feature.xml needs to be updated
by Marshall Culpepper
I think you meant to CC jbosside-dev..
---------- Forwarded message ----------
From: Koen Aers <koen.aers(a)jboss.com>
Date: Sep 14, 2006 6:59 AM
Subject: RE: [jbosside-dev] Re: jBPM Designer feature.xml needs to be
updated
To: Marshall Culpepper <marshall.culpepper(a)jboss.com>
I am pretty much OK with doing things the way they should be done, no
problem with that.
Btw, are you talking about the meeting when I was in India? I cannot
remember discussing this, but this might be due to some kind of jetlag ;-).
Anyway, we are in the process of releasing jBPM 3.2 alpha1 so the release
has my number one attention at present. And as I mentioned earlier, the good
way to reuse the tag that Marshall has written would be to bundle it in a
library that resides in the repository to avoid duplication. Or am I wrong
about this?
Regards,
Koen
------------------------------
*From:* marshall.jboss(a)gmail.com [mailto:marshall.jboss@gmail.com] *On
Behalf Of *Marshall Culpepper
*Sent:* woensdag 13 september 2006 22:31
*To:* Max Andersen
*Cc:* Koen Aers; jbosside-dev(a)lists.jboss.org
*Subject:* Re: [jbosside-dev] Re: jBPM Designer feature.xml needs to be
updated
Yes, this is what we decided on our meeting.. we are moving all dependencies
to be included the "right" way, and retrofitting the build system to
calculate feature dependencies based on those entries, instead of counting
on eclipse PDE to auto-bundle things that are listed as <plugin>.
On 9/13/06, Max Rydahl Andersen <max.andersen(a)jboss.com> wrote:
> just to be clear:
>
> Our old/current way of bundling things are *wrong* in context of
> integrating with the rest of
> the eclipse ecosystem. you should only have <plugin> for plugins that is
> actually part of the plugin
> everything else is <import> of either plugin's or feature's.
>
>
>
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBossIDE Team Lead
JBoss, a division of Red Hat
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBossIDE Team Lead
JBoss, a division of Red Hat
17 years, 7 months
[jbosside-dev] Re: jBPM Designer feature.xml needs to be updated
by Marshall Culpepper
It isn't documented yet as it is still pretty new (I just wrote it last
week). You can find the code and definition for the ant task here:
http://fisheye.jboss.com/browse/JBoss/jbosside/releng/org.jboss.ide.eclip...
You'll basically want to look at CalculateFeatureDependenciesTask. This task
by itself only figures out which features and plugins a given feature
"depends on" to run within eclipse based on it's <requires> and <include>
xml tags. There is a macro definition in the common/bundleDependencies.xml
script that wraps this task and does the actual bundling which you can find
here:
http://fisheye.jboss.com/browse/JBoss/jbosside/releng/org.jboss.ide.eclip...
You can see the bundleDependencies macro in use in hibernate tools'
customTargets.xml here:
http://fisheye.jboss.com/browse/JBoss/jbosside/releng/org.jboss.ide.eclip...
It basically looks like:
<bundleDependencies feature="org.hibernate.eclipse.feature" buildDirectory=
"${buildDirectory}"
archivePath="${buildDirectory}/${buildLabel}/HibernateTools-${
hibernate.tools.release}.${versionTag}.zip" />
Keep in mind this will only bundle dependencies which are explicitly
declared under the "Dependencies" tab in the feature.xml or in the "include
features" tab (it will also bundle dependencies of dependencies, etc). I
don't see a reason why you wouldn't be able to use this outside of releng if
you want to use this in your own customTargets.. the code is eclipse
independent.
On 9/12/06, Koen Aers <koen.aers(a)jboss.com> wrote:
>
> Ok now I have finally read this email thread about the feature.xml and I
> am a bit more up to date. But what exactly is the ant task you are talking
> about Marshall? Is this documented somewhere? And do you mean I have to
> include some other dependency to make the jBPM plug-in build work outside
> of JBoss IDE? I am not quite sure that this would simplify things for
> me...
>
> Regards,
> Koen
>
> ------------------------------
> *From:* marshall.jboss(a)gmail.com [mailto:marshall.jboss@gmail.com] *On
> Behalf Of *Marshall Culpepper
> *Sent:* maandag 11 september 2006 21:43
> *To:* Koen Aers; jbosside-dev(a)lists.jboss.org
> *Subject:* jBPM Designer feature.xml needs to be updated
>
> Hey Koen..
>
> When going through builds trying to iron everything out for the new
> bundling task, I noticed that org.jbpm.gd.jpdl.feature still includes
> eclipse plugins listed as <plugin> in the feature.xml. As per our meeting,
> could you remove all of these entries and move them to the "Dependencies"
> tab, or "<requires><import>" ?
>
> --
> Marshall Culpepper
> marshall.culpepper(a)jboss.com
> JBossIDE Team Lead
> JBoss, a division of Red Hat
>
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBossIDE Team Lead
JBoss, a division of Red Hat
17 years, 7 months
[jbosside-dev] CorePlugin with hard branded version id and version comparison ?
by Max Rydahl Andersen
Hi guys,
I just noticed that CorePlugin now has a hard branded version id and
custom version comparison in it ?
May I ask why ?
...and what is wrong with using the versioning in the plugin.xml etc.
instead of a new concept ?
If it is just to get a "release name" why not just put it in the resource
bundle ?
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss a division of Red Hat
max.andersen(a)jboss.com
17 years, 7 months
[jbosside-dev] Fwd: [wtp-dev] Java EE 5 projects support contribution by SAP
by Max Rydahl Andersen
If you haven't noticed...JEE5 support in WTP targeted for WTP 2.0...damn
that is a long wait ;(
/max
------- Forwarded message -------
From: "Raev, Kaloyan" <kaloyan.raev(a)sap.com>
To: wtp-dev(a)eclipse.org
Cc:
Subject: [wtp-dev] Java EE 5 projects support contribution by SAP
Date: Wed, 13 Sep 2006 15:11:53 +0200
Hello,
As you may remember, about two months ago, we suggested to implement
support for Java EE 5 projects in WTP. Bug 149007 [1] was created to
track the request.
Since that time we have gained better in-depth knowledge of the WTP
codebase. We saw that the changes needed are much bigger than we have
expected at the beginning. Because the changes are quite significant for
maintenance release, this led us to the decision to give up the
contribution for the R1.5.x maintenance codeline, but work only for the
R2.0 development codeline.
What we have now is modifications of the WTP plugin that add support for
Java EE 5 project. The support is not still full, but it is on a stage
already working and useful. Features added by the patch follow:
* New version constants for Java EE 5. Version conversion tools
are also updated.
* New facet version for Java EE 5 projects: web 2.5, ejb 3.0,
ear 5, etc.
* New Project wizards are updated to allow creation of Java EE 5
projects.
* Java EE 5 projects are created with deployment descriptors xml
files that refer to the new Java EE 5 xml schemas for validation.
* New icons (showing the newer version) for the deployment
descriptors node in the j2ee navigator view.
* The Xdoclet is disabled for EJB 3.0 projects. This is because
Java 5 annotations are used.
* Import and Export for Java EE 5 projects.
Known limitation:
* Appclient 5 projects are not yet supported.
* Web and Ejb projects still create web.xml and ejb-jar.xml
although this is not required. However this does not conflict with the
Java EE 5 specification.
* The model is not updated to recognize metadata annotations in
the source code. As in J2EE 1.4 project the model only recognizes the
project elements in the deployment descriptor. However, this does not
affect the correct deployment of projects that use metadata annotations.
* The children of deployment descriptor node for EJB 3.0 are
removed. This is to avoid frustration for the user who annotates a bean
and does not see it appearing under the deployment descriptor node in
the j2ee navigator view.
* The Java EE 5 has basic metadata annotations support provided
by JDT tools (without additional WTP features as wizards,
code-completion, etc.).
We have tested the implementation against our SAP-specific runtime
target - the j2ee application server in the SAP NetWeaver platform. We
have not the opportunity to test against other Java EE 5 runtime
targets, because there are not any implemented yet.
We have also run j2ee automatic tests against our implementation. We
also updated the tests where appropriate to test Java EE 5
functionality. Patch will be provided as well.
We think that our changes are good base for adding support for Java EE 5
projects in WTP 2.0. Moreover, they touch some important aspects of the
WTP 2.0 Plan [2]:
* investigate: import a JEE5 project (help wanted)
* investigate: export/publish a JEE5 project (help wanted)
* validate a JEE5 project (help wanted)
I am going to close the feature requests for the R1.5.x contribution and
create a new one for R2.0 with the patch attached there. But first we
want to have discussion with WTP J2EE developers about the topic via
telecon meeting. Is it possible to use the status telecon [3] tomorrow?
I see that it has not been held for the last 2-3 weeks. If not possible,
then may be the pmc call on Tuesday?
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=149007
[2]
http://wiki.eclipse.org/index.php?title=Web_Tools_Requirements_2.0#J2EE_
Standard_Tools
[3] http://www.eclipse.org/webtools/development/status-telecons/
Greetings,
Kaloyan Raev
Senior Developer
NW AS JS TOOLS JEE (BG)
SAP Labs Bulgaria
T +359/2/9157-416
mailto:kaloyan.raev@sap.com
www.sap.com
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss a division of Red Hat
max.andersen(a)jboss.com
17 years, 7 months
[jbosside-dev] Freemarker export?
by Max Rydahl Andersen
Hi Joe,
Are you subscribed to jbosside-dev(a)lists.jboss.org ?
And is it on purpose you started to export="true" freemarker-x.jar from
the freemarker IDE?
what is the purpose of that ? (it can/will confuse e.g. hibernate tools
plugin if two freemarker.jar's are there :)
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss a division of Red Hat
max.andersen(a)jboss.com
17 years, 7 months
[jbosside-dev] jBPM Designer feature.xml needs to be updated
by Marshall Culpepper
Hey Koen..
When going through builds trying to iron everything out for the new bundling
task, I noticed that org.jbpm.gd.jpdl.feature still includes eclipse plugins
listed as <plugin> in the feature.xml. As per our meeting, could you remove
all of these entries and move them to the "Dependencies" tab, or
"<requires><import>" ?
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBossIDE Team Lead
JBoss, a division of Red Hat
17 years, 7 months
