8:57 p.m.
I can reproduce your test case using JBoss Tools, wtp 2.0.2 and
webtools' patch.
I have also tested two latest builds and these are the results :
1) It is not possible to reproduce your test case in the build because
the generic JBoss server is missing (the
org.eclipse.jst.server.generic.jboss_1.5.105.v200709061325 directory is
empty).
I don't know if this was done intentionally. If I add this plugin, I can
reproduce your case.
Screenshot buildtest3 shows Max's project deployed with JBoss Tools adapter.
Screenshot buildtest4 shows the same project deployed using the generic
JBoss adapter (when it is added to the build).
2) Features in webtools' patch aren't defined correctly what can cause
different issues in our builds (screenshot buildtest1).
For instance,
The following plugins are contained in the
org.eclipse.jst.web_core.feature feature:
org.eclipse.jst.j2ee version 1.1.106.v200802192030
org.eclipse.jst.jee version 1.0.2.v200802192030
...
The patch adds the org.eclipse.jst.web_core.feature.patch feature (the
new feature) including :
org.eclipse.jst.j2ee version 1.1.107.v200803071930
org.eclipse.jst.jee version 1.0.3.v200803242054
Different features contain the same plugins with different versions. The
result - features can't be loaded correctly.
The correct way to create the patch is increasing the version number of
the org.eclipse.jst.web_core.feature as well as version number of all
dependent features.
Attached is the correct patch that contains the same plugins as the
original webtools's patch (wtp-P-*P20080325024219-20080325024219*.zip)
and the fixed features.
The logic is the same, but there aren't any errors in the features,
plugins are loaded properly, the update manager works correctly (see
screenshoot buildtest2).
3) The org.springframework.ide.eclipse.aop.ui.visualiser and
org.springframework.ide.eclipse.aop.ui.xref plugins aren't loaded
properly because the org.eclipse.contribution.visualiser,
org.eclipse.contribution.xref.ui and org.eclipse.contribution.xref.core
plugins are missing.
I think that these plugins need to be removed or we need to add the AJDT
project that contains the missing plugins.
Snjeza
Rob Stryker wrote:
I've retested six times now. I have no idea what the problem in
the
build is. Nada. I've come to that conclusion.
At least with the official JBDS build.
See, it seems to work with JUST the ONE patch now. For me.
I need someone else to confirm this.
My methodology is as follows:
[rob@localhost wtp2.0.2]$ \
> tar xvzf eclipse-SDK-3.3.2-linux-gtk-x86_64.tar.gz;\
> unzip dtp-sdk_1.5.2_022008.zip;\
> unzip emf-sdo-xsd-SDK-2.3.2.zip;\
> unzip GEF-SDK-3.3.2.zip;\
> unzip wtp-sdk-R-2.0.2-20080223205547.zip
Then press "A" several times for over. This installs the base wtp2.0.2
install.
I create a workspace and use a GENERIC SERVER adapter with Max's test
project which can be found at
https://bugs.eclipse.org/bugs/attachment.cgi?id=98244
Then, in the REGULAR server's view, I make sure to add the project to
the server, and I click the publish icon.
In the server's deploy folder, I execute the following:
[rob@localhost 422GA_deploy]$ unzip -l myseampro99-ear.ear
Archive: myseampro99-ear.ear
Length Date Time Name
-------- ---- ---- ----
0 04-30-08 22:15 META-INF/
106 04-30-08 22:15 META-INF/MANIFEST.MF
455 04-30-08 21:10 META-INF/application.xml
835020 04-30-08 18:18 jboss-seam-nodesc.jar
-------- -------
835581 4 files
Only 4 files published. No good. Close eclipse. rm -rf
myseampro99-ear.ear from the server's deploy folder.
Then, in the eclipse folder I execute:
unzip wtp-P-*P20080325024219-20080325024219*.zip
This is the most recent patch. David Williams *assures* us they are
cumulative.
I then re-run eclipse.
Since the workspace is already set up, we don't need to recreate the
server or anything.
We just go to the server's view, and click "publish". That's it.
In the deploy folder, let's see what's in the ear file:
[rob@localhost 422GA_deploy]$ unzip -l myseampro99-ear.ear
Archive: myseampro99-ear.ear
Length Date Time Name
-------- ---- ---- ----
0 04-30-08 22:19 META-INF/
106 04-30-08 22:19 META-INF/MANIFEST.MF
455 04-30-08 21:10 META-INF/application.xml
835020 04-30-08 18:18 jboss-seam-nodesc.jar
871392 04-30-08 22:19 jboss-seam.jar
-------- -------
1706973 5 files
In short, in my last 7 tests, it works FINE with JUST the one patch!
In other words, I have no idea why the BUILD didn't work.
I strongly suspect we *only* need to use the one patch, and it was
just a bad build?
David Williams assures us of that.
That's all I've got. We'll have to test the next build. But the next
build, unless I can get ahold of Marshall, will have both patches, and
may be broken for that reason.
Someone please try to replicate this with me.
- Rob Stryker
Rob Stryker wrote:
> Max:
>
> The fix was simply that we required both patches in order to make it
> work.
>
> Marshall is on it. I'm going to comment on the eclipse bug.
>
> - Rob
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
