Eclipse WTP changes targets for the 1.0 version

[Srepfler Srgjan <sr...@lnksystem.com>]

I'm reposting a peace of this conversation that I've picked up on the 
eclipse.wtp newsgroup, perhaps it'll be usefull to the 
maven-eclipse-plugin developers.
For the people that don't know eclipse 3.1 can't handle multiple 
classpaths per project and 3.2 should address that issue. On the other 
hand WTP 1.0 is targeted for 3.1 and 1.5 for 3.2
At least that's what how I've understood the issue.
So perhaps the plugin should have a small change for WTP 1.0 and let's 
hope 1.5 will bring better things.

David Williams wrote:
 >
 > There's been various notes and discussion on "the developers" mailing
 > lists, but I wanted
 > to be sure the wider community was also aware of some general changes
 > and issues that
 > might effect your migration from projects based on WTP 0.7 to projects
 > based on WTP 1.0.
 > Sorry if this is repeating things, but wanted to be sure it was widely
 > announced ahead of time.
 > These notes apply to WTP M9 as well as the final release of WTP 1.0.
 >
 > First, the biggest functionaly change. After much debate and
 > investigation, it was decided that we
 > could never well support multiple modules per project, so we removed
 > this capability in 1.0.
 > While I think it was not easy to create multiple modules per project in
 > 0.7, and we hope
 > not many people did, ... if you did, then when
 > you move to WTP 1.0, you may have some special migration steps. Let us
 > know (here or open
 > bugs you find) if you find issues here.
 >
 > And, we did want to reassure everyone we are well aware of this
 > requirement, and are confident
 > in our ability to avoid these "one way" traps in the next release (1.0
 > to 1.5).
 >
 > You should be able to do early tests migrating your projects with our
 > latest I-build, see
 > 
http://download.eclipse.org/webtools/downloads/drops/I-I200511162235-200511162235/ 

 >
 >
 > If nothing else, hopefully this "early" notice will allow you to
 > schedule a time
 > your whole team can move up to WTP 1.0 (which is still scheduled for
 > 12/16).
 >
 > As always, let us know if there are questions or problems ... and, as
 > always, test early, test
 > often, and open bugs as you find them.

Me:

 > Perhaps this is something that goes out of the discussion at hand but 
I'd like to put it on the table none the less. If anyone follows the 
development of maven 2 and the way it handles projects (for instance it 
can handle a project defined in a xml file and have the three modules 
(ear, war, ejbjar) beneath it's directory structure inheriting 
dependencies and various other stuff).
 > How do you see this change in module handling, will it affect 
positively or negatively for teams that would like their projects to be 
managed by maven2?
 > For anyone that doesn't know it, maven2 has a plugin that once run 
creates some eclipse artifacts and it's folder structure can then be 
imported in a eclipse workspace. I have seen that they are working on it 
and it even creates a file .wtpmodules
 > I would very much appreciate if the WTP team would dedicate some time 
in helping this community and I believe that just like ant was something 
that helped java (IDE's were in the stone age until they started using 
it), maven and now maven2 can help a lot on project management.
 > Please, this is a serious issue.

Darryl L. Miles wrote:

 >
 > My understanding is that the WTP team are not saying never.  Just they
 > can't provide a workable solution for 1.0 until the single classpath per
 > project issue can be handled by the Eclipse, Java Development Team.
 >
 > We all want the feature, its just not deliverable for 1.0.
 >
 > I guess when the feature first went in it was not clear that the single
 > classpath issue exists or was a problem.  If you think about it another
 > way maven2 and ANT have build.xml and in there you can configure
 > different classpaths per sub-project/task with eclipse you cant do this
 > right now.
 >
 > I'm very sure the JDT would appreciate another pair of hands and eyes on
 > the task.
 >
 >
 >> For anyone that doesn't know it, maven2 has a plugin that once run
 >> creates some eclipse artifacts and it's folder structure can then be
 >> imported in a eclipse workspace. I have seen that they are working on
 >> it and it even creates a file .wtpmodules
 >
 >
 > This file has moved to .settings/.component.  maven2 should not throw
 > away this work, _MAYBE_ for WTP1.5 they can bring it out again.
 >
 >
 > Darryl


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org