Re: Maven Eclipse error

AFAIK there is no fix to prevent eclipse from failing to download files sometimes--seems to do this regularly with big download batches. >From the command line, `cd && mvn dependency:go-offline` Right-click your project in eclipse -> Maven -> Update Update it On Fri, Aug 2, 2019 at 3:01 PM Lak

Maven Eclipse error

Hi Team, I'm trying to create a maven java project and while configuring the pom.xml file I could able to see the below errors: Please try to help me to resolve the issues. Error1: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from https://repo.maven.apache.org/mav

Re: Some Maven Eclipse Questions

These questions are better suited for the m2e mailing list. https://dev.eclipse.org/mailman/listinfo/m2e-users /Anders (mobile) On Dec 11, 2015 06:16, "Sony Antony" wrote: > 1. Noticed that even when I use the EMBEDDED maven inside m2e, it is > creating a new JVM - different from the JVM running

Some Maven Eclipse Questions

1. Noticed that even when I use the EMBEDDED maven inside m2e, it is creating a new JVM - different from the JVM running Eclipse - for maven install ( even for cleam ). Is this always the case ? ( Im trying to see if this happened because of some issues with my setup ) 2. I have a multip project.

[RESULT] [VOTE] Retire Maven Eclipse Plugin / Donation to Mojohaus

several issues with the maven-eclipse-plugin. It will take quite some time to fix these issues, but is it worth maintaining it here? Nowadays the Maven support for Eclipse is good and stable. The maven-eclipse-plugin has a lot of integration tests which should be rewritten, because it always

[ANN] Apache Maven Eclipse Plugin 2.10 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Eclipse Plugin, version 2.10 This plugin is used to generate Eclipse IDE files (*.classpath, *.project, *.wtpmodules and the .settings folder) for use with a project - if the M2E Eclipse-Plugin does not fit you. This

Re: M2Eclipse vs. maven-eclipse-plugin: which is preferred?

official stance about whether M2Eclipse or maven-eclipse-plugin is preferred way of importing Maven projects into Eclipse? I thought M2Eclipse was the blessed way, but I cannot find anything "official" online. Only that the maven-eclipse-plugin hasn't been updated for a while, but tha

Re: M2Eclipse vs. maven-eclipse-plugin: which is preferred?

There is nothing official from the Maven itself. There used to be competing Maven Eclipse integration from different people here, and there has always been the command line generation vs IDE integration. So there is no officially blessed integration from the Maven project proper. Also note

Re: M2Eclipse vs. maven-eclipse-plugin: which is preferred?

On 9 May 2014 18:49, Thomas Broyer wrote: > Hi all, > > Does the Apache Maven Project/Community has an official stance about > whether M2Eclipse or maven-eclipse-plugin is preferred way of importing > Maven projects into Eclipse? > > I thought M2Eclipse was the blessed w

M2Eclipse vs. maven-eclipse-plugin: which is preferred?

Hi all, Does the Apache Maven Project/Community has an official stance about whether M2Eclipse or maven-eclipse-plugin is preferred way of importing Maven projects into Eclipse? I thought M2Eclipse was the blessed way, but I cannot find anything "official" online. Only that the mav

Re: maven-eclipse-plugin - configure source and output-folders

On Oct 4, 2013, at 5:18 PM, Andreas Dolk wrote: > Hi all, > > we have a rather complex project structure with a lot of projects and a > couple of code generators that produce java classes for production and > test. The challenge now is to configure the build files so that a mvn > eclipse:eclip

Re: maven-eclipse-plugin - configure source and output-folders

Hi Andreas, Andreas Dolk wrote: > Hi all, > > we have a rather complex project structure with a lot of projects and a > couple of code generators that produce java classes for production and > test. The challenge now is to configure the build files so that a mvn > eclipse:eclipse run will create

Re: maven-eclipse-plugin - configure source and output-folders

> test. The challenge now is to configure the build files so that a mvn > eclipse:eclipse run will create all required source folders and set the > correct output folders, for example: Are you aware of m2e and other options for using Maven in Eclipse? I'm just not convinced you will get what you w

maven-eclipse-plugin - configure source and output-folders

Hi all, we have a rather complex project structure with a lot of projects and a couple of code generators that produce java classes for production and test. The challenge now is to configure the build files so that a mvn eclipse:eclipse run will create all required source folders and set the corre

maven-eclipse-plugin generates wrong eclipse project

general maven-eclipse-pluging would like to accept any maven project that is accepted by maven. Is there anyone who can advice about it?  1) +---gen |   \---com |       \---HybridJava |           \---Sample |                   A.java +---src |   \---com |       \---HybridJava |           \---Sample

Re: JDT compiler compliance level as a parameter for eclipse:eclipse target of maven-eclipse-plugin

Thanks for suggestions, Barrie and Wayne! I will have a look at maven-eclipse-plugin source code later. To clarify, 1.5 corresponds to javac "-source" option and to ECJ "org.eclipse.jdt.core.compiler.source" setting 1.6 corresponds to javac "-

Re: JDT compiler compliance level as a parameter for eclipse:eclipse target of maven-eclipse-plugin

e.jdt.core.compiler.compliance=1.5 >>> I get this (look at the compliance): >>> org.eclipse.jdt.core.compiler.compliance=1.6 >>> but didn't find a way to configure maven-eclipse-plugin. >> >> Most likely you are the first person to want this specifi

Re: JDT compiler compliance level as a parameter for eclipse:eclipse target of maven-eclipse-plugin

(look at the compliance): >> org.eclipse.jdt.core.compiler.compliance=1.6 >> but didn't find a way to configure maven-eclipse-plugin. > > Most likely you are the first person to want this specific > configuration of the plugin, thus it does not currently exist. You'll > probab

Re: JDT compiler compliance level as a parameter for eclipse:eclipse target of maven-eclipse-plugin

but didn't find a way to configure maven-eclipse-plugin. Most likely you are the first person to want this specific configuration of the plugin, thus it does not currently exist. You'll probably need to scratch your own itch. Pull down the source code for maven-eclipse-plugin, tweak it

JDT compiler compliance level as a parameter for eclipse:eclipse target of maven-eclipse-plugin

n.targetPlatform=1.5 eclipse.preferences.version=1 org.eclipse.jdt.core.compiler.source=1.5 org.eclipse.jdt.core.compiler.compliance=1.6 but didn't find a way to configure maven-eclipse-plugin. Has anybody else experienced this problem? Can you suggest any ideas? [1] https://wiki.jenkins-ci.org

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

On Sat, Mar 3, 2012 at 6:28 AM, Markku Saarela wrote: > Our releases do not have any configuration files in artifact's, instead > manifest classpaths has directory name to point directory that has those > files. We use separate build to assembly different configurations into > different environmen

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

My day job company is assosiate member of Eclipse so of course Eclipse is tool to use. Markku On 2.3.2012 18:14, Wayne Fay wrote: You don't understand how Eclipse IDE works. Eclipse does not have different classpaths for testing and actual runtime. So Eclipse basic design is faulty. There is b

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

My day job company is associate member of Eclipse so of course Eclipse is tool to use. Markku On 2.3.2012 18:14, Wayne Fay wrote: You don't understand how Eclipse IDE works. Eclipse does not have different classpaths for testing and actual runtime. So Eclipse basic design is faulty. There is b

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

e true true jar-with-dependencies Ron On 02/03/2012 2:00 PM, Markku Saarela wrote: In multi-module project i hit the same problem with m2e and maven-eclipse-plugin. Are you saying not to import multi-module projects into Eclipse, instead every module separately? Or you do

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

ingle true true jar-with-dependencies Ron On 02/03/2012 2:00 PM, Markku Saarela wrote: In multi-module project i hit the same problem with m2e and maven-eclipse-plugin. Are you saying not to import multi-module projects into Eclipse, instead

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

In multi-module project i hit the same problem with m2e and maven-eclipse-plugin. Are you saying not to import multi-module projects into Eclipse, instead every module separately? Or you don't use server plugins to deploy application instead you deploy outside Eclipse and use r

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

> You don't understand how Eclipse IDE works. Eclipse does not have different > classpaths for testing and actual runtime. So Eclipse basic design is > faulty. There is bug open since 2008 to provide means to tell Eclipse that ... > Of course NetBeans and IntelliJ has correct way to do things but t

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

work. We do not use maven-eclipse-plug-in. We use the assembly plug-in to build our war files. Perhaps that is the difference. We also deploy to Tomcat which might be a better servlet engine than Glassfish. I am not sure how relevant our experience is to your problem but if I can provide any

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

do things but they are not an option. Markku On 2.3.2012 15:15, Ron Wheeler wrote: On 02/03/2012 1:32 AM, Markku Saarela wrote: Hi, Developing with Eclipse IDE and JavaEE server using maven-eclipse-plugin you have to use profiles, because Eclipse does not isolate test code and test

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

On 02/03/2012 1:32 AM, Markku Saarela wrote: Hi, Developing with Eclipse IDE and JavaEE server using maven-eclipse-plugin you have to use profiles, because Eclipse does not isolate test code and test resources. Eclipse does /src/main/ code /src/test ... test code and resources You

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

Hi, Developing with Eclipse IDE and JavaEE server using maven-eclipse-plugin you have to use profiles, because Eclipse does not isolate test code and test resources. Only way to do it what i have figured out is to have two profiles one for running application in app server and another for

[ANN] Maven Eclipse Plugin 2.9 Released

The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.9 The Maven Eclipse Plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. http://maven.apache.org/plugins/maven-eclipse-plugin/ [Please

Re: Maven eclipse not fully functional

If you can move to the STS version of Eclipse, you might find that these problems go away since it comes ready to go with Maven. Ron On 21/12/2011 8:42 PM, Barrie Treloar wrote: On Thu, Dec 22, 2011 at 11:16 AM, Apache Omega wrote: I'm using the Maven Apache plug in for eclipse because I'm t

Re: Maven eclipse not fully functional

On Thu, Dec 22, 2011 at 11:16 AM, Apache Omega wrote: > I'm using the Maven Apache plug in for eclipse because I'm to new to figure > out the command line method but now that I've switched I'm having problems > again. > my maven plug in is installed but the list for the archetype catalogs are > gr

Maven eclipse not fully functional

ess denied) when I bring up a project and choose run as my m2 eclipse maven options wont pop up please please please tell me how i can fix this -- View this message in context: http://maven.40175.n5.nabble.com/Maven-eclipse-not-fully-functional-tp5093334p5093334.html Sent from the Maven - U

Re: Anyone help me about classpathContainers in maven-eclipse-plugin?

org.eclipse.jst.j2ee.internal.web.container is not right??? true is not right , too?? But I donot get any useful details in http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html 2011/12/20 Barrie Treloar > On Tue, Dec 20, 2011 at 4:45 PM, zuxiong lin > wrote: > > I h

Re: Anyone help me about classpathContainers in maven-eclipse-plugin?

lipse.wst.common.project.facet.core.nature > > > org.eclipse.jdt.launching.JRE_CONTAINER > > org.eclipse.jst.j2ee.internal.web.container > > > > I dont see a WTP specification in your plugin settings. http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html I dont use WTP so you will have to read

Anyone help me about classpathContainers in maven-eclipse-plugin?

t;Java Build Path-->Libraries --> Add Library --> Web App Libraries-->... Why does it still need the classpath ???How do I fix it ? By the way , we use eclipse-jee version 3.7 SR1 like : org.apache.maven.plugins maven-eclipse-plugin 2.8 true true org.eclipse.j

Re: Does maven eclipse plugin downloads unnecesary artifacts?

Thanks Barrie! 2011/11/18 Barrie Treloar : > On Fri, Nov 18, 2011 at 6:19 AM, Gabriel Belingueres > wrote: >> Hi! >> >> I usually use the maven eclipse plugin (v2.8) using the >> downloadSources and downloadJavadocs properties, however I added some >> runti

Re: maven eclipse plug-in

I will help :-) What can I do? On Fri, Nov 18, 2011 at 5:01 AM, Barrie Treloar wrote: > On Fri, Nov 18, 2011 at 5:53 AM, Albert de Jongh > wrote: > > I am wondering when 2.9 of this plug-in will be released? I can't figure > > it out from the different JIRA and project web sites. 2.9 fixes s

Re: Does maven eclipse plugin downloads unnecesary artifacts?

On Fri, Nov 18, 2011 at 6:19 AM, Gabriel Belingueres wrote: > Hi! > > I usually use the maven eclipse plugin (v2.8) using the > downloadSources and downloadJavadocs properties, however I added some > runtime scoped dependency but the eclipse plugin downloads the > sources.jar a

Re: maven eclipse plug-in

On Fri, Nov 18, 2011 at 5:53 AM, Albert de Jongh wrote: > I am wondering when 2.9 of this plug-in will be released?  I can't figure > it out from the different JIRA and project web sites.  2.9 fixes some big > issues with classpath ordering which is really making life difficult for us. > (http://j

Does maven eclipse plugin downloads unnecesary artifacts?

Hi! I usually use the maven eclipse plugin (v2.8) using the downloadSources and downloadJavadocs properties, however I added some runtime scoped dependency but the eclipse plugin downloads the sources.jar and javadoc.jar too of that library (also no other dependency depends on that runtime scoped

maven eclipse plug-in

I am wondering when 2.9 of this plug-in will be released? I can't figure it out from the different JIRA and project web sites. 2.9 fixes some big issues with classpath ordering which is really making life difficult for us. (http://jira.codehaus.org/browse/MECLIPSE-388)

Re: maven-eclipse-plugin: pde support and OSGiManifest writer

false maven-eclipse-plugin true false org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType

Re: maven-eclipse-plugin: pde support and OSGiManifest writer

On Wed, Sep 28, 2011 at 11:40 AM, Stephen Coy wrote: > FWIW, we're using pde mode at present. > > We have a largish (~ 40 modules) framework that builds both RCP applications > and web applications. > > I haven't had a chance to figure out how to integrate Tycho into this > arrangement. On the s

Re: maven-eclipse-plugin: pde support and OSGiManifest writer

ependencies or maven dependencies but not both. Thanks, Steve C On 23/09/2011, at 4:01 PM, Barrie Treloar wrote: > Does anyone actually use pde mode in maven-eclipse-plugin? > > The support looks pretty basic and there are other better options like > tycho and

Re: maven-eclipse-plugin: pde support and OSGiManifest writer

01 AM, Barrie Treloar wrote: Does anyone actually use pde mode in maven-eclipse-plugin? The support looks pretty basic and there are other better options like tycho and felix for doing this stuff. EclipseOSGiManifestWriter has been deprecated in favour of felix and I wonder whether its worth keepin

Re: maven-eclipse-plugin: pde support and OSGiManifest writer

Carlos Sanchez wrote: > I guess there wouldn't be any issue removing it adding a warning > pointing to the Felix plugin. > Osgi manifests are better handled there. +1 - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.ap

Re: maven-eclipse-plugin: pde support and OSGiManifest writer

I guess there wouldn't be any issue removing it adding a warning pointing to the Felix plugin. Osgi manifests are better handled there. On Fri, Sep 23, 2011 at 8:01 AM, Barrie Treloar wrote: > Does anyone actually use pde mode in maven-eclipse-plugin? > > The support looks pretty b

maven-eclipse-plugin: pde support and OSGiManifest writer

Does anyone actually use pde mode in maven-eclipse-plugin? The support looks pretty basic and there are other better options like tycho and felix for doing this stuff. EclipseOSGiManifestWriter has been deprecated in favour of felix and I wonder whether its worth keeping the other stuff around

Re: [m2e-users] Maven, Eclipse, Nexus, Perforce, Team City, Oh My!

On 07/08/2011 10:13 PM, Barrie Treloar wrote: On Mon, Aug 8, 2011 at 8:25 AM, Eric Kolotyluk wrote: You're telling me Maven requires an advanced Maven Admin on the team/organization? No-one told me that before. Don't be fooled. Any build system requires this person. You can't expect clueless

Re: [m2e-users] Maven, Eclipse, Nexus, Perforce, Team City, Oh My!

That was an attempt at some humor on my part - obviously a bad attempt :-) Yes, it has become obvious to me now that it takes time to acquire the skill and experience to make the best use of Maven, and now I have 6 months experience. For the time being, I am the Maven Admin. It is also why I a

Re: [m2e-users] Maven, Eclipse, Nexus, Perforce, Team City, Oh My!

On Mon, Aug 8, 2011 at 8:25 AM, Eric Kolotyluk wrote: > You're telling me Maven requires an advanced Maven Admin on the > team/organization? No-one told me that before. Don't be fooled. Any build system requires this person. You can't expect clueless people to be able to run your build systems f

Re: [m2e-users] Maven, Eclipse, Nexus, Perforce, Team City, Oh My!

Cool article. You are correct: Maven has a very steep learning curve. M2E makes it easier only partially, but still requires an advance Maven Admin on the team/organization. I wonder: Was the Sonatype book helpful? When I first started, it didn't exist yet and I had to learn only from another

Re: [m2e-users] Maven, Eclipse, Nexus, Perforce, Team City, Oh My!

e). I know it all seems weird, but after trying many other things in Windows, it was the most simple way I could get things to work. Thanks for asking these questions - it mean I need to explain myself better in the wiki article. I have renamed the article to "Windows, Maven

Maven, Eclipse, Nexus, Perforce, Team City, Oh My!

OK, this is my meager first attempt to give something back to the community... http://docs.codehaus.org/display/MAVENUSER/Maven%2C+Eclipse%2C+Nexus%2C+Perforce%2C+Team+City%2C+Oh+My! Se

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

On Thu, Jul 14, 2011 at 9:07 AM, Barrie Treloar wrote: > On Thu, Jul 14, 2011 at 3:09 AM, Jeff MAURY wrote: >> You probably need to configure your Eclipse project as a Groovy project >> (through a nature I think). >> Please not that you can configure the Maven Eclipse p

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

On Thu, Jul 14, 2011 at 3:09 AM, Jeff MAURY wrote: > You probably need to configure your Eclipse project as a Groovy project > (through a nature I think). > Please not that you can configure the Maven Eclipse plugin to add specific > natures when eclipse:eclipse is run. Groovy supp

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

You probably need to configure your Eclipse project as a Groovy project (through a nature I think). Please not that you can configure the Maven Eclipse plugin to add specific natures when eclipse:eclipse is run. Regards Jeff On Wed, Jul 13, 2011 at 7:26 PM, DaveyBob wrote: > I essentia

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

roovy files ever get compiled to .class files in the output folder. At this point I don't have a clue how to get Eclipse to build these files. I think I'll come at it from the Eclipse side and create a Groovy project. -- View this message in context: http://maven.40175.n5.nabble.com/Maven

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

> On Thu, Jun 30, 2011 at 12:45 AM, Sebastian Goldt wrote: Sebastian, its been five days and no feedback. Have you worked out your problem? Has any of this thread been useful? It would be nice from an archive perspective if you could comment on your resolution so others can avoid this problem i

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

On Thu, Jun 30, 2011 at 09:13, Guillaume Polet wrote: > It's an M2Eclipse problem. I think you should rather user their ML. > > No, he's using the maven-eclipse-plugin. Not m2eclipse. /Anders > -- > Guillaume > > Le 29/06/2011 17:15, Sebastian Goldt a écrit :

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

So it should run build-helper to attach the groovy directories. I can see in the debug logs [DEBUG] testOutput toRelativeAndFixSeparator D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\groovy , D:\ide\maven\maven-eclipse-plugin\target\test-c

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

On Thu, Jun 30, 2011 at 4:43 PM, Guillaume Polet wrote: > It's an M2Eclipse problem. I think you should rather user their ML. [del] >>    mvn eclipse:eclipse He's not using m2e. I'm looking into it... - To unsubscribe, e-mail:

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

It's an M2Eclipse problem. I think you should rather user their ML. -- Guillaume Le 29/06/2011 17:15, Sebastian Goldt a écrit : Hi all, today, I run into some problems with the Maven Eclipse Plugin 2.8 using Maven 3.0.3 on an Ubuntu 11.04 while setting up a mixed Java / Groovy projec

Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

Hi all, today, I run into some problems with the Maven Eclipse Plugin 2.8 using Maven 3.0.3 on an Ubuntu 11.04 while setting up a mixed Java / Groovy project. It seems as if the eclipse plugin doesn't include all source code folders in the generated .project file. I haven't found anyth

Re: maven-eclipse-plugin:to-maven

s I appreciate very much, working with Maven, Eclipse and M2E > is "sources at your fingertips". > Occasionally I am using a debugger ;~) > > And that is also the reason for my suggestion to improve > maven-eclipse-plugin: I have noticed, that the to-maven goal of the > mav

maven-eclipse-plugin:to-maven

Hi, First: Thanks! I am using Maven since years and my enthusiasm is still growing, on an already very high level. Very fine work, great software, makes software development a pleasure. On of the things I appreciate very much, working with Maven, Eclipse and M2E is "sources at

Re: Maven/Eclipse - Failed to read artifact descriptor

Hello, Regarding m2e, you should probably ask in m2e ml (see http://eclipse.org/m2e/support/ ) 2011/5/3 Cuong Luu : > Hi, > I'm am trying to use Eclipse M2 plugin to manage my project dependencies. > This is what I have done thus far. > > 1) Used mvn deploy:deploy file to deploy third-party jars t

Maven/Eclipse - Failed to read artifact descriptor

Hi, I'm am trying to use Eclipse M2 plugin to manage my project dependencies. This is what I have done thus far. 1) Used mvn deploy:deploy file to deploy third-party jars to a specific repository, e.g. third-party 2) Used mvn deploy to deploy my project (with POM) to a specific repository, e.g re

Re: maven eclipse plugin

g about m2e, this isn't the correct mailing list. If you are talking about maven-eclipse-plugin then: * Coding Styles: http://maven.apache.org/plugins/maven-eclipse-plugin/examples/load-code-styles.html * Checkstyle: http://maven.apache.org/plugins/maven-eclipse-plugin/examples/configure-chec

Re: maven eclipse plugin

On 18/04/2011 10:18 AM, Fernando Wermus wrote: Hi all, I am trying to set up code styles, work space and so on, but it doesn't work. Does anybody know if maven plug in eclipse is working for these kind of set up? I am using eclipse helios thanks in advance You might want to move to the STS

maven eclipse plugin

Hi all, I am trying to set up code styles, work space and so on, but it doesn't work. Does anybody know if maven plug in eclipse is working for these kind of set up? I am using eclipse helios thanks in advance

RE: Maven Eclipse Plugin - how to remove M2_REPO classpath variable

s List Subject: Re: Maven Eclipse Plugin - how to remove M2_REPO classpath variable > Does anyone know a way to remove the M2_REPO classpath variable that was > added using > > mvn -Declipse.workspace= eclipse:configure-workspace? I don't know how (or even if) you can do this with

Re: Maven Eclipse Plugin - how to remove M2_REPO classpath variable

> Does anyone know a way to remove the M2_REPO classpath variable that was > added using > >  mvn -Declipse.workspace= eclipse:configure-workspace? I don't know how (or even if) you can do this with the Eclipse plugin, but nothing is stopping you from doing it manually by editing the dot files (.c

Maven Eclipse Plugin - how to remove M2_REPO classpath variable

Does anyone know a way to remove the M2_REPO classpath variable that was added using mvn -Declipse.workspace= eclipse:configure-workspace? (I'm created another workspace and would like to clean up the first workspace.) I've tried running mvn eclipse:clean before re-running eclipse:configur

Re: Missing goal eclipse:m2eclipse in version 2.8 of the Maven Eclipse plugin

plugin to create .classpath >>> files that refer to MAVEN2_CLASSPATH_CONTAINER and to add Maven nature and >>> build command to the .project files without touching the corresponding poms? >> >> You don't, you use m2eclipse directly. >> If you are

Re: Missing goal eclipse:m2eclipse in version 2.8 of the Maven Eclipse plugin

re and >> build command to the .project files without touching the corresponding poms? > > You don't, you use m2eclipse directly. > If you are using m2eclipse, you *CAN NOT* use maven-eclipse-plugin, > hence it being removed in 2.8 > > ---

Re: Missing goal eclipse:m2eclipse in version 2.8 of the Maven Eclipse plugin

;t, you use m2eclipse directly. If you are using m2eclipse, you *CAN NOT* use maven-eclipse-plugin, hence it being removed in 2.8 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org

RE: Missing goal eclipse:m2eclipse in version 2.8 of the Maven Eclipse plugin

From: Stefan Eder [mailto:stefan.e...@ebuconnect.de] Sent: 16 December 2010 11:09 To: users@maven.apache.org Subject: Missing goal eclipse:m2eclipse in version 2.8 of the Maven Eclipse plugin Hi, since quite a while I am using Maven and Eclipse together with the Eclipse plugin for Maven and the

Missing goal eclipse:m2eclipse in version 2.8 of the Maven Eclipse plugin

Hi, since quite a while I am using Maven and Eclipse together with the Eclipse plugin for Maven and the Maven plugin for Eclipse. And it is just great. But in the version 2.8 of the Eclipse plugin for Maven I am (hardly) missing the goal m2eclipse. How can I tell the version 2.8 of the Ec

Re: maven-eclipse-plugin

On Mon, Dec 6, 2010 at 10:39 AM, Brian Topping wrote: > On a related note, can anyone summarize what the best way of maintaining > eclipse projects from Maven is?  I use IDEA, and the best way from there is > IDEA itself, not with the IDEA plugin for Maven. > > Is the same true for Eclipse that

Re: maven-eclipse-plugin

Mon, Dec 6, 2010 at 12:51 AM, Asmann, Roland wrote: Hi all, Does anybody know in which version the support for wtp 2.x was added? Not really, you'd have to trawl through the code base to see for sure. http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html lists the versions avai

Re: maven-eclipse-plugin

support for wtp 2.x was added? > > Not really, you'd have to trawl through the code base to see for sure. > http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html lists > the versions available > >> And when will support for wtp 3.x be added? > > There is

Re: maven-eclipse-plugin

On Mon, Dec 6, 2010 at 12:51 AM, Asmann, Roland wrote: > Hi all, > > Does anybody know in which version the support for wtp 2.x was added? Not really, you'd have to trawl through the code base to see for sure. http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html list

maven-eclipse-plugin

Hi all, Does anybody know in which version the support for wtp 2.x was added? And when will support for wtp 3.x be added? Thanks! -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 219

Re: adding java sources to classpath with maven-eclipse-plugin

add an include pattern. Default maven filters out java files. Martijn On Sun, Nov 7, 2010 at 11:26 AM, James Ring wrote: > (Please CC me on replies, I am not subscribed to this list) > > Hi there, > > I have a GWT project which programatically starts a DevMode shell. The > problem I have is that

Re: adding java sources to classpath with maven-eclipse-plugin

James Ring wrote: > (Please CC me on replies, I am not subscribed to this list) > > Hi there, > > I have a GWT project which programatically starts a DevMode shell. The > problem I have is that GWT needs access to the Java source code in the > classpath at runtime. I have tried adding my src/mai

adding java sources to classpath with maven-eclipse-plugin

(Please CC me on replies, I am not subscribed to this list) Hi there, I have a GWT project which programatically starts a DevMode shell. The problem I have is that GWT needs access to the Java source code in the classpath at runtime. I have tried adding my src/main/java directory to the resources

Re: maven-eclipse-plugin Does not resolve workspace project name

t; Lets assume a person is working on two different version (two releases > being > developed in parallel). They will both have the same artifact ID but > eclipse forces a different project name. I don't think asking m-e-p to > offer this functionality is really an isnane reque

Re: maven-eclipse-plugin Does not resolve workspace project name

On Sat, Oct 30, 2010 at 2:34 AM, john.vint wrote: > > >> This is not m-e-p's problem. Stop renaming your projects if you want >> to use m-e-p and use it to regenerate the .project files. Keep the >> name as the artifactId, or change the artifactId in the pom to meet >> your needs. > > Lets assume

Re: maven-eclipse-plugin Does not resolve workspace project name

View this message in context: http://maven.40175.n5.nabble.com/maven-eclipse-plugin-Does-not-resolve-workspace-project-name-tp3237890p3242262.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe,

Re: maven-eclipse-plugin Does not resolve workspace project name

Yup, it's in ASF svn, and if the project isn't willing to own it, they should attic it. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-eclipse-plugin Does not resolve workspace project name

On 28/10/2010 9:35 AM, Martijn Dashorst wrote: On Thu, Oct 28, 2010 at 2:54 PM, Ron Wheeler wrote: It is hard to get enthusiastic about maintaining old software that has been replaced by better stuff that is free. maven-eclipse-plugin works roughly 100% of the time here, but the m2eclipse

Re: maven-eclipse-plugin Does not resolve workspace project name

I agree, there are many plugins that Maven developers just don't look after and they should be ejected and taken out of the org.maven.plugins name space. Anything there people assume are maintained which simply is not the case. On Oct 28, 2010, at 10:58 AM, Antonio Petrelli wrote: > 2010/10/28

Re: maven-eclipse-plugin Does not resolve workspace project name

2010/10/28 Wayne Fay : So how does one get ownership of the plugin? I've contributed 2 > > This is open source so no one is stopping you from creating a fork. Sorry to jump in but, in the Apache Committers' FAQ I read: http://www.apache.org/dev/committers.html#committer-responsibilities App

Re: maven-eclipse-plugin Does not resolve workspace project name

> m-e-p works better than M2ECLIPSE in many cases. Further, you have no > proof here that I can see that the m-e-p is dead. To quote the plugin I am the one who said "for all intents, m-e-p is dead" based entirely on JIRA activity and releases, as well as the existence of newer (and largely percei

Re: maven-eclipse-plugin Does not resolve workspace project name

en you probably want to get the Maven group to cooperate. If you are the only user/developer, you are off to the races. Why the constant commercials for the m2eclipse plugin? Instead why not ask for some interested developer to take over the maven-eclipse-plugin? Isn't this an open source commun

Re: maven-eclipse-plugin Does not resolve workspace project name

Barrie's workspace were resolved. Unfortunately that is > the last of it. > > Why the constant commercials for the m2eclipse plugin? Instead why not > ask for some interested developer to take over the > maven-eclipse-plugin? Isn't this an open source community? >

  1   2   3   4   5   6   7   8   >