Tim,
There is JIRA issue about RAD7 support.
http://jira.codehaus.org/browse/MNGECLIPSE-653
At very least you can vote on it. Also, issues like "can't see source
folders", or "exceptions on startup" usually leave traces in the Eclipse
error log and we might be able to fix some of those if you attach such
error log to that jira issue (please don't paste long text as comments).
I have to admit that we don't have resources to support RAD7. We do
maintain compatibility with Eclipse 3.2 API, but we don't really test on
Eclipse 3.2 and it is very unlikely that would change. However we will
be glad to accept patches and will be happy to support anyone who would
want to investigate those issues. We will assist with setting up the
development workspace and can provide additional pointers to anyone who
would want to dig into it.
For starters, there are instructions on the wiki on configuring
development environment. See
http://docs.codehaus.org/display/M2ECLIPSE/Configuring+Development+Environment
Note that for Eclipse 3.2 and RAD7 you won't need all m2eclipse
projects in your Eclipse workspace (e.g. skip AJDT, WTP, Subclipse and
Mylyn plugins), i.e. you can close those projects after checking out
code from http://svn.sonatype.org/m2eclipse/trunk
Also note that we are working on adding EAR and EJB support for
m2eclipse 0.9.7. But m2eclipse only support WTP 2.x and 3.x (Eclipse 3.3
and 3.4 accordingly). To support whatever web tools is used by RAD7,
someone would have to implement special project configurator for those
tools (i.e. new Eclipse plugin, similar to existing
org.maven.ide.eclipse.wtp plugin). See some basic documentation on the
wiki at
http://docs.codehaus.org/display/M2ECLIPSE/Extensible+project+configuration+framework
regards,
Eugene
Tim Schwenk wrote:
Hi all,
I am currently working in a large corporate environment where we are
(unfortunately) required to use RAD7 for development. As part of a
continuing process improvement project, I am spearheading the adoption
of Maven2 as our standard build tool. We have so far made fairly good
progress in getting most of our project to build successfully without
major changes, but I am still struggling to come up with a way to
unify things so that we aren't repeating dependency configuration
(among other things) in our pom's and our IDEs.
Up until recently (early August?), I've been using dev releases of
m2eclipse in my copy of RAD 7, and while there were some bugs and
missing features (EAR WTP support mainly), I was pretty happy.
However, somewhere during or around 0.9.5, things began to go haywire.
I get an exception on startup initializing Java tooling, and when I
upgraded to 0.9.6, nothing works at all - can't see any source
folders, can't close projects or enable/disable Maven dependency
management,, etc. Anyway, it's gotten to the point that I simply
can't use m2eclipse anymore with RAD7. Unfortunately, it's unlikely
that we'll get to RAD7.5 anytime in the near future - definitely not
while it's still in beta, and probably not even after it goes GA.
So, my question is, will m2eclipse 1.0 support RAD7, or has it gotten
to the point that this just can't happen? If the plan is to support
RAD7, but there hasn't been enough input from the community, I would
be glad to volunteer at the very least testing and bug reports - maybe
even code, but it would take me a while to get up to speed with
m2eclipse development, and time is one thing that I don't have in
abundance (who does?). If, on the other hand, the assumption is that
anyone who really wants to use m2eclipse will at the very least
upgrade to an Eclipse 3.3 based product, then that's going to leave a
lot of unfortunate developers out in the cold.
I really don't want this to sound like griping, but being forced to
use RAD7 is bad enough, so I'm really hoping someone will be kind
enough to at least provide *something* in the way of Maven integration
for us poor souls. :-) I've already tried substituting vanilla
Eclipse 3.3 for RAD7, but without a proper WAS 6.1 WTP connector, this
is just a no go. I've also tried the maven-eclipse-plugin with RAD7,
but eclipse:rad doesn't seem to do even close to the right thing for
RAD7 - especially when EAR projects are involved.
To wrap up, I would like to say that from what I've seen, under
Eclipse 3.3, the m2eclipse plugin is really starting to look VERY
good! There's been excellent progress over the last six months, and
I'd like thank anyone and everyone who's had a hand in the
development. Job well done!
Thanks,
-Tim Schwenk
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
