Thank you for your insight into the future. Well, then the best
solution will be removing all references to maven-eclipse-plugin from
pom.xml and relaying on M2Eclipse. It clears all my concerns about this,
thanks again.
Martin
On 15.3.2010 18:07, Jason van Zyl wrote:
Just a note so that fo
Just a note so that folks know what's coming. The maven-eclipse-plugin will not
work with M2Eclipse anymore. If M2Eclipse sees projects generated with the
maven-eclipse-plugin it won't import them. M2Eclipse works by creating the
necessary projects files by inspecting the POM and doesn't expect
Hi,
after some by-hand editing of configuration files, that have been
mentioned here, it works.
But when I try to run eclipse:eclipse goal of maven-eclipse-plugin
again, it breaks and I have
to revert changes. We can live with that :)
Martin
On 15.3.2010 17:23, Michel Pawlak wrote:
Hi
I h
right WTP setup for multi modules configuration with
> "project
> dependencies" and shared resources? Or is there any documentation for file
> org.eclipse.wst.common.component?
>
> I'm going little bit crazy... thank God debugging with Jetty works like
> a charm,
&g
t;
> I have tried same except "eclipse:eclipse" instead of "eclipse:m2eclipse"
> which didn't work for me also :(
>
> My humble findings are summarized in other message in this thread:
> http://old.nabble.com/Maven-and-WTP-integration-td27403219.html#a27405
Tried but with very same poor result. As far as I understand, this function
checkouts project tree from SVN and creates .project and .classpath and
other necessary files for Eclipse. In my case there are these files in
SVN and I'm successfully using Eclipse for development of this project.
I am ab
Hi Manuel,
I have tried same except "eclipse:eclipse" instead of "eclipse:m2eclipse"
which didn't work for me also :(
My humble findings are summarized in other message in this thread:
http://old.nabble.com/Maven-and-WTP-integration-td27403219.html#a27405004
Please, co
2010/2/2 Martin Schayna :
> Maybe "Checkout as Maven" in m2eclipse plugin can do some
> magic project configuration if original project is not mavenized
It works well *especially* with mavenized projects. It creates one
project per module, along with the project for the pom.
BTW did you try it?
A
We are using Subversion, but WTP support has nothing to do with Subversion,
in my opinion. Maybe "Checkout as Maven" in m2eclipse plugin can do some
magic project configuration if original project is not mavenized, but we
have
mavenized project and need only add some WTP support (i.e. ability to
2010/2/1 Martin Schayna :
> run Eclipse,
> convert WTP configuration (Ctrl+1 QuickFix),
> add Maven dependecies to WTP (Ctrl+1 QuickFix),
Why all of this stuff? Does not your "Checkout as Maven project" work?
If you do it in the POM project, it should download and create all
subprojects automatica
Eclipse Platform 3.5.1
Eclipse WST/JST 3.1.1
m2eclipse 0.9.9 (but very same with stable 0.9.8)
Maven 2.0.9
Java 1.6.0_14
When I try to append WTP support into war application project by this
$ mvn -Dwtpversion=2.0 eclipse:m2eclipse
and then:
run Eclipse,
convert WTP configuration (Ctrl+1 Quick
Hi Martin,
My setup is similar to yours. Enter each appN folder and type this:
mvn -Dwtpversion=2.0 eclipse:m2eclipse
Is what I did and it works for me.
2010/2/1 Martin Schayna
> Hi all,
>
> we have pretty large project, successfully "mavenized" with Maven 2,
> split into several module proje
2010/2/1 Martin Schayna :
> we have pretty large project, successfully "mavenized" with Maven 2,
> split into several module projects under one parent pom. We are using
> m2eclipse plugin in Eclipse 3.5.
What version? I am a happy user of the 0.9.9 development version, it
seems that versions prior
Hi all,
we have pretty large project, successfully "mavenized" with Maven 2,
split into several module projects under one parent pom. We are using
m2eclipse plugin in Eclipse 3.5.
Project tree looks like:
parent/ (pom project)
+-- lib-core/ (jar project)
+-- lib-web/ (jar project, wi
14 matches
Mail list logo
