8 Replies Latest reply on Mar 25, 2008 10:56 AM by scabanovich

Request guidance on upgrading from JBoss Tool 2.0 GA to 2.0.

chris.simons Mar 18, 2008 9:09 AM

Moving from Exadel Studio Pro to JBoss Tool 2.0 GA was quite an accomplishment. JBoss Tools 2.0.1 GA looks to have a huge number of fixes and new features and we would like to start working with this new version as soon as possible.

Before I commit to this process, does anyone have best practices for upgrading? If anyone has already done the upgrade, I'd really like to know if there are any "gotcha's" or caveats that I should be aware of.

Thanks very much.

1. Re: Request guidance on upgrading from JBoss Tool 2.0 GA to

erimag Mar 18, 2008 9:24 AM (in response to chris.simons)

just works for me so far... (updated via the update site). Haven't done any extensive testing though...
Actions
2. Re: Request guidance on upgrading from JBoss Tool 2.0 GA to

chris.simons Mar 18, 2008 3:00 PM (in response to chris.simons)

I guess I'll just have to give it a shot then.

I hope this fixes the .xst.xml file problem we have!
Actions
3. Re: Request guidance on upgrading from JBoss Tool 2.0 GA to

maxandersen Mar 18, 2008 7:32 PM (in response to chris.simons)

what is .xst.xml file problems ? Any jira link ?
Actions
4. Re: Request guidance on upgrading from JBoss Tool 2.0 GA to

chris.simons Mar 19, 2008 10:01 AM (in response to chris.simons)

Max,

I believe so - in fact I think I put the issue in myself. Let me go take a look at JIRA.
Actions
5. Re: Request guidance on upgrading from JBoss Tool 2.0 GA to

chris.simons Mar 19, 2008 10:17 AM (in response to chris.simons)

Looks like it was completed! I must have missed it in the release notes.

http://jira.jboss.org/jira/browse/JBIDE-1658

I would ask, however, what we should do with our existing org.jboss.tools.jst.web.xml project files. We've been doing a bit of modifying for these each time we branch or check out an existing project since the file likes to mess up our JSF settings if Eclipse doesn't like what it sees. Once we upgrade, should we remove this file all together?
Actions
6. Re: Request guidance on upgrading from JBoss Tool 2.0 GA to

maxandersen Mar 25, 2008 10:09 AM (in response to chris.simons)

I think it can be deleted, i'll ask slava to comment on this thread.
Actions
7. Re: Request guidance on upgrading from JBoss Tool 2.0 GA to

maxandersen Mar 25, 2008 10:10 AM (in response to chris.simons)

note: the fix for this file is not in any release yet - it is a work inprogress for JBossTools 2.1.x
Actions
8. Re: Request guidance on upgrading from JBoss Tool 2.0 GA to

scabanovich Mar 25, 2008 10:56 AM (in response to chris.simons)

> what we should do with our existing
> org.jboss.tools.jst.web.xml project files

Before JBoss Tools 2.0.1, if this file gets wrong because of wrong absolute paths, the solution was to remove it, remove line org.jboss.tools.jsf.jsfnature in .project file, restart Eclipse and execute "JBoss Tools/Add JSF Capabilities..." on project node in Package Explorer.

In JBoss Tools 2.0.1 one can remove the file and restart Eclipse without editing .project, the nature is removed automatically. Executing "JBoss Tools/Add JSF Capabilities..." is still needed, and file org.jboss.tools.jst.web.xml will be created with correct paths.

In JBoss Tools 2.1.x, file org.jboss.tools.jst.web.xml is not needed and will not be created, but as long as it exists in an old project, it will be used. If it is wrong, just remove it.
Actions

Go to original post