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

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

We're building bundles with the following build configuration: bundle org.apache.felix org.osgi.core 1.2.0 org.apache.feli

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

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 surface it looks like you're either using p2 dependencies or maven

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

+1 Having fewer partial implementations to confuse folks is always better IMO. On 9/27/11 2:08 AM, 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. On Fri, Sep 23, 2011 at 8:01 AM, Barr

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 basic and there

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 plugin to add specific >> na

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 support in maven-ec

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 essentially have

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

I essentially have the same problem. I am just getting started with Groovy for this project. Environment: Ubuntu 11.04 Eclipse 3.7 Groovy Eclipse plugin 2.5.1 Maven 2.2.1 Following the instructions in the Groovy Eclipse Plugin page (http://groovy.codehaus.org/Groovy-Eclipse+compiler+plug

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 : > >> Hi all, >> >> today, I run int

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: [del] > My project in question contains both tests and main source code in java as > well as in groovy, so I have the four folders src/main/java, > src/main/groovy, src/test/java and src/test/groovy which are added to the > project with the

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 project. It seem

Re: maven eclipse plugin

On Mon, Apr 18, 2011 at 11:48 PM, 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 If you are talking about m2e, this is

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

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

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

On 05/12/2010 7:09 PM, 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 the IDE plugin for

Re: maven-eclipse-plugin

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 the IDE plugin for Maven is better than the Maven plugin for

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 lists the versions availa

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

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 a person is working on two dif

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

> 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 a person is working on two different version (two releases b

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 plu

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

Wrong person. I was not the person claiming that patches were not being deployed. Ron On 28/10/2010 9:36 AM, Benson Margulies wrote: Ron, 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 site: Last Publ

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

We're not stopping you from taking it. Put it in Github and hack away. On Oct 28, 2010, at 5:13 AM, Martijn Dashorst wrote: > So how does one get ownership of the plugin? I've contributed 2 > patches with an implied promise that they would be included when the > failing ITs on Barrie's workspace

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

Ron, 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 site: Last Published: 2010-02-25 | Version: 2.8 If someone posts a patch, I don't think there/s much evidence that it will be ignored. --benson On

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

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 plugin fails miserably with our maven project setu

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

On 28/10/2010 5:13 AM, Martijn Dashorst wrote: So how does one get ownership of the plugin? I've contributed 2 patches with an implied promise that they would be included when the failing ITs on Barrie's workspace were resolved. Unfortunately that is the last of it. I guess that you could take a

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

So how does one get ownership of the plugin? I've contributed 2 patches with an implied promise that they would be included when the failing ITs on 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

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

On 27/10/2010 1:28 PM, Wayne Fay wrote: When I run eclipse:eclipse the project name in the .project file will be the artifactId (by default) despite the eclipse project name being something different. Yes, this is how m-e-p works. The .project file is overwritten by m-e-p and so you will lose al

Re: maven-eclipse-plugin and POM packaging projects

you can right click on one of the project root folders, select the maven item and one of the sub-menu items will do what you want -S On 17 June 2010 12:28, Daniele Dellafiore wrote: > M2Eclipse does some things fine but not all. > > Use case: > > pom A define a resource folder > I have in eclip

Re: maven-eclipse-plugin and POM packaging projects

M2Eclipse does some things fine but not all. Use case: pom A define a resource folder I have in eclipse, imported with M2E, project A and B, the latter inherit from A. Change the resource folder in A from eclipse, save. Nothing change in eclipse. So while changing a dep in the pom make the buil

Re: maven-eclipse-plugin and POM packaging projects

> Actually, m-e-p does not create any .project while M2Eclipse import both of > them... and the multi-module is useless and I will just delete it. IMO you are better off just switching over to m2eclipse full time instead of continuing to fight with m-e-p. Wayne --

Re: maven-eclipse-plugin and POM packaging projects

Mixed feeling for me. MultiModule pom project aren't to be imported as a project, I do agree. But parent kind of pom project, I would like to see them imported. Problem is that there is no way in maven to make a distinction. Actually, m-e-p does not create any .project while M2Eclipse import both

Re: maven-eclipse-plugin and POM packaging projects

On Tue, Jun 15, 2010 at 12:04 PM, Daniele Dellafiore wrote: > I have "patched" maven-eclipse-plugin to create an eclipse project also for > projects with "pom" packaging type. > I was wondering if this was a bug or a feature and if someone is interested > in the plugin behaving this way other than

Re: [maven-eclipse-plugin] Spring dependencies omitted

On Thu, Mar 11, 2010 at 6:39 PM, Pascal Kesseli wrote: > Hi everyone > > Being a typical maven fan, I tried to manage our eclipse plugins using > maven. To do so, I configured the maven-eclipse-plugin as follows: > > >org.apache.maven.plugins >maven-eclipse-plugin >2.8 >

Re: maven-eclipse-plugin configuration for pom packaging

On Fri, Nov 6, 2009 at 7:34 AM, james.w.jackson wrote: > In the end it was a pyrrhic victory.  I was hoping to use the eclipse > Import...->Existing Projects into Workspace, but it stops recursing once it > finds a folder with a .project file--which is not terribly useful for a > multi-module proj

Re: maven-eclipse-plugin configuration for pom packaging

If you checkout your project from your revision control system via eclipse, it should already be available as a project. Otherwise, you have to cheat to get it into eclipse. File > New Project General > Project Specify "Project name" Uncheck "Use default location" Browse to where the top level pr

Re: maven-eclipse-plugin configuration for pom packaging

I was afraid of that. I eventually manhandled the plugin in my pom.xml files that had pom packaging to get the .project files, but it doesn't feel right: org.apache.maven.plugins maven-eclipse-plugin jar In the end it was a pyrrhic victory. I was hoping to use the

Re: maven-eclipse-plugin configuration for pom packaging

The plugin doesn't support it. I think there's a an issue already opened about that. You can vote for it. It is supported by m2eclipse or Q4E. Cheers, Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Thu, Nov 5, 2009 at 5:39 PM,

Re: maven-eclipse-plugin and src/main/webapp with Eclipse

On Sat, Oct 24, 2009 at 1:58 AM, Vincent F wrote: > > OK, thanks everyone for these additional infos. I may stick with WTP > organisation then (using /WebContent/ instead of /src/main/webapp/) just for > convenience in Eclipse. You should be able to use /src/main/webapp thats what the file .setti

Re: maven-eclipse-plugin and src/main/webapp with Eclipse

OK, thanks everyone for these additional infos. I may stick with WTP organisation then (using /WebContent/ instead of /src/main/webapp/) just for convenience in Eclipse. -- Vincent baerrach wrote: > > On Fri, Oct 23, 2009 at 10:50 AM, Benson Margulies > wrote: >> An Eclipse project type, or

Re: maven-eclipse-plugin and src/main/webapp with Eclipse

On Fri, Oct 23, 2009 at 10:50 AM, Benson Margulies wrote: > An Eclipse project type, or perspective, can decide to show the tree any way > it likes. The default Java perspective shows all folders as ordinary folders > except source folders. It hauls source folders to the top of the project, > give

Re: maven-eclipse-plugin and src/main/webapp with Eclipse

An Eclipse project type, or perspective, can decide to show the tree any way it likes. The default Java perspective shows all folders as ordinary folders except source folders. It hauls source folders to the top of the project, gives them a special icon, and labels them with the full pathname (e.g.

Re: maven-eclipse-plugin and src/main/webapp with Eclipse

On Fri, Oct 23, 2009 at 6:31 AM, Vincent F wrote: > > My plugin configuration is the following > > >      org.apache.maven.plugins >      maven-eclipse-plugin >      2.7 >         >             war >             false >             2.0 >             true >         > > > So as you can see, pack

Re: maven-eclipse-plugin and src/main/webapp with Eclipse

My plugin configuration is the following org.apache.maven.plugins maven-eclipse-plugin 2.7 war false 2.0 true So as you can see, packaging is "war" but /src/main/webapp is not added as a source. In the .c

RE: maven-eclipse-plugin and src/main/webapp with Eclipse

Also, if you use WTP in Eclipse, it will work this way. I'd guess that if you would get it to work, Eclipse would probably build incorrect WAR-files because it would include the contents of that folder as both resources and as real web-application. So, just get used to it, it isn't broken and ther

Re: maven-eclipse-plugin and src/main/webapp with Eclipse

On Thu, Oct 22, 2009 at 9:37 AM, Vincent F wrote: > > Thanks for your answer. I'm going to be very picky here, but is there a way > to have the src/main/webapp folder " folded as one in Eclipse, just like the > src/main/java and src/main/resources are ? Can you please post how you are running ecl

RE: maven-eclipse-plugin and src/main/webapp with Eclipse

Thanks for your answer. I'm going to be very picky here, but is there a way to have the src/main/webapp folder " folded as one in Eclipse, just like the src/main/java and src/main/resources are ? Vincent justinedelson wrote: > > It doesn't really make sense for src/main/webapp to be a source

RE: maven-eclipse-plugin and src/main/webapp with Eclipse

It doesn't really make sense for src/main/webapp to be a source folder - it doesn't contain compilable source files. Justin -Original Message- From: Vincent F [mailto:vincent.fu...@sgcib.com] Sent: Wednesday, October 21, 2009 1:22 PM To: users@maven.apache.org Subject: maven-eclipse-plu

Re: maven-eclipse-plugin issue

Did you check the plugin documentation? http://maven.apache.org/plugins/maven-eclipse-plugin/examples/ajdt-projects.html AspectJ needs more than just the dependencies for the eclipse .project to work. You need 1.5 See the above link as you may also need to configure

RE: maven eclipse plugin and wtp

aire >> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la >> copie de ceci est interdite. Ce message sert à l'information seulement et >> n'aura pas n'importe quel effet légalement obligatoire. Étant donné que >> les email

RE: maven eclipse plugin and wtp

ulation, nous ne > pouvons accepter aucune responsabilité pour le contenu fourni. > > > > >> Date: Tue, 4 Aug 2009 09:39:17 -0400 >> Subject: Re: maven eclipse plugin and wtp >> From: w...@wantii.com >> To: users@maven.apache.org >> >> On Tu

Re: maven eclipse plugin and wtp

On Tue, Aug 4, 2009 at 9:56 AM, Martin Gainty wrote: > > m2 is the better solution if you need to debug > curious as to what term CI means? > CI = continuous integration... Things like Hudson, Bamboo, Continuum. -Wes -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring,

RE: maven eclipse plugin and wtp

ur le contenu fourni. > Date: Tue, 4 Aug 2009 09:39:17 -0400 > Subject: Re: maven eclipse plugin and wtp > From: w...@wantii.com > To: users@maven.apache.org > > On Tue, Aug 4, 2009 at 9:27 AM, > massive.boisson wrote: > > > > Hi, I have a maven project (that

Re: maven eclipse plugin and wtp

On Tue, Aug 4, 2009 at 9:27 AM, massive.boisson wrote: > > Hi, I have a maven project (that is web project by its nature) and I want to > run it in eclipse as WTP project. > > I found command (on > http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html): > mvn -Dwtpversion=R7 eclipse:eclipse

Re: maven eclipse plugin and wtp

Sorry that came out wrong, I know I cannot do -Dwtpversion=3.1, but I am wondering what are my alternatives. It seems there should be a new new way to do this, and I cannot find it. Or maybe 2.0 works as good as 3.1 Thanks -MB massive.boisson wrote: > > As current wtp version is 3.1, can I

Re: maven-eclipse-plugin: how to specify custom compiler settings?

On Wed, Jul 15, 2009 at 12:17 PM, Dirk Olmes wrote: > Hi, > > I'm trying to nail down some compiler settings for a project. Those are > stored in .settings/org.eclipse.jdt.core.prefs, e.g. > > org.eclipse.jdt.core.compiler.problem.autoboxing=warning > > A quick look in the m-e-p's source makes me t

Re: [maven-eclipse-plugin]: MECLIPSE-548 requires attention

We asked several times to test the 2.7-SNAPSHOT before the release and we had no feedback about this issue which wasn't solved. Thus I don't know if it impacts so many projects.We'll try to fix it in 2.8, but I don't know in how many weeks/monthes, we'll be able to do it Cheers Cheers, Arnaud

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

Ok a 2.7 is being built and voting has started. If you would like to participate in testing please see "Guide to testing staged releases": http://maven.apache.org/guides/development/guide-testing-releases.html And the nabble archive of the vote at http://www.nabble.com/-VOTE--Release-Maven-Eclips

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

We also tested it with an AspectJ project, and that works as well. Martijn On Fri, May 29, 2009 at 10:09 AM, Martijn Dashorst wrote: > Works great! Thanks Barrie!!! > > Here's the log entry for my run: > > macbookpro:myproject dashorst$ mvn eclipse:eclipse > [INFO] Scanning for projects... > [IN

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

Works great! Thanks Barrie!!! Here's the log entry for my run: macbookpro:myproject dashorst$ mvn eclipse:eclipse [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'eclipse'. Downloading: http://repository/artifactory/repo/org/apache/maven/plugins/maven-eclipse-

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

I just deployed it in the snapshots repo. It's numbered : 2.7-20090529.071922-5Thx for your hard work Barrie. Cheers Arnaud On Fri, May 29, 2009 at 6:05 AM, Barrie Treloar wrote: > On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst > wrote: > > On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst wrote: > On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar wrote: >> I went quickly hacking an existing IT test to include the resources >> definition you provided and some debugging output (as ERROR so I could >> see it) > > Great! > >> So src/mai

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar wrote: > I went quickly hacking an existing IT test to include the resources > definition you provided and some debugging output (as ERROR so I could > see it) Great! > So src/main/resources is correctly on the resources list. > The problem is tha

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

On Wed, May 27, 2009 at 5:17 PM, Martijn Dashorst wrote: > http://wicket.apache.org/quickstart.html > > Select for example Wicket 1.3.6 > I went quickly hacking an existing IT test to include the resources definition you provided and some debugging output (as ERROR so I could see it) [ERROR] Res

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

http://wicket.apache.org/quickstart.html Select for example Wicket 1.3.6 Martijn On Wed, May 27, 2009 at 8:44 AM, Barrie Treloar wrote: > On Wed, May 27, 2009 at 3:58 PM, Martijn Dashorst > wrote: >> With Wicket, we have Page.html, Page.properties, Page.properties_ru, >> Page.js, Page.css, Pag

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

On Wed, May 27, 2009 at 3:58 PM, Martijn Dashorst wrote: > With Wicket, we have Page.html, Page.properties, Page.properties_ru, > Page.js, Page.css, Page.younameit next to the Java files. This has > been the official way to work with Wicket, and was 100% supported by > maven by defining src/main/j

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

On Wed, May 27, 2009 at 1:17 AM, Barrie Treloar wrote: > On Tue, May 26, 2009 at 11:03 PM, Martijn Dashorst > wrote: >> In my opinion  MECLIPSE-443 is a very bad idea. Should every plugin be >> configured so that the resources available in src/main/java are >> treated as classpath entries? > > It

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

Hi Arnaud, Sorry, my bad -- missed reading those changes. I re-tested it and it works fine with the inclusions setting, but I agree with Martijn that MECLIPSE-443 is not the best way to go. Thanks again, Ari Arnaud HERITIER wrote: > > Hi Ari, > Thanks for your feedback. > > Did you follow t

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

Martijn Dashorst wrote: > Yes, and I've been burned by m2eclipse, and haven't heard loving > reports from co-workers about q4e either. Not installing any of them > anytime soon. The same here. I'd rather maintain a fork of the m-e-p that does exactly what I want than installing one of the eclipse

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

Well, here's one for q4e. Ever since they implemented the incremental builder, I haven't had any issues with it and it's been fast enough for me (got 30 or so linked Eclipse projects on my workspace). Kalle On Tue, May 26, 2009 at 7:35 AM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: >

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

On Tue, May 26, 2009 at 11:03 PM, Martijn Dashorst wrote: > In my opinion  MECLIPSE-443 is a very bad idea. Should every plugin be > configured so that the resources available in src/main/java are > treated as classpath entries? It was my understanding that if you had resources in src/main/java t

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

Yes, and I've been burned by m2eclipse, and haven't heard loving reports from co-workers about q4e either. Not installing any of them anytime soon. Martijn On Tue, May 26, 2009 at 4:09 PM, Arnaud HERITIER wrote: > Did you try to use m2eclipse or q4e ?They'll be the future. > > maven-eclipse-plug

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

Did you try to use m2eclipse or q4e ?They'll be the future. maven-eclipse-plugin will probably die under its own weight. There are too many use cases and testing coverage isn't conclusive because we only checks what we generate and not that we are able to import/use it in eclipse . We have really

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

In my opinion MECLIPSE-443 is a very bad idea. Should every plugin be configured so that the resources available in src/main/java are treated as classpath entries? According to me the eclipse plugin should take the part of the pom into account, rather than invent yet another way of specifying whe

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

Hi Ari, Thanks for your feedback. Did you follow this doc to setup your eclipse project : http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html ?? Arnaud On Tue, May 26, 2009 at 2:29 AM, ari.meyer wrote: > > Hi Arnaud,

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

Hi Arnaud, I just tested with maven-eclipse-plugin-2.7-20090427.230850-4.jar and I'm getting the same error when using Wicket: org.apache.wicket.markup.MarkupNotFoundException: Markup not found. Reverting again back to 2.5.1, everything worked properly. Best regards, Ari Arnaud HERITIER wrot

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

Anything else? Should we start the release process again then? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

I agree. I find that developer moan about *any* change, but within a week or 2 they don't want it changed back. Personally if the src folders that show up in eclipse change from a group of src folders followed by a group of test folders to alternating test / src / test / src, I would find that mo

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

The recent release 2.6 of the maven-eclipse-plugin created many problems for all of those who had/wanted to store non-java files under src/*/java (which is required for wicket, ajdt, and probably others usecases). Even we have many integration tests in this plugin we didn't noti

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

How is doing the m2eclipse/q4e plugins (these are now for me references on how to integrate eclipse and maven). Arnaud On Wed, Apr 29, 2009 at 11:50 AM, Jörg Schaible wrote: > Hi Barrie, > > Barrie Treloar wrote at Mittwoch, 29. April 2009 09:03: > > > On Wed, Apr 29, 2009 at 4:13 PM, Jörg Schaib

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

Hi Barrie, Barrie Treloar wrote at Mittwoch, 29. April 2009 09:03: > On Wed, Apr 29, 2009 at 4:13 PM, Jörg Schaible > wrote: >> Arnaud HERITIER wrote at Donnerstag, 16. April 2009 10:42: >> >>> Hi Community, >>> The recent release 2.6 of the maven-eclipse-plugin created many problems >>> for all

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

On Wed, Apr 29, 2009 at 4:13 PM, Jörg Schaible wrote: > Arnaud HERITIER wrote at Donnerstag, 16. April 2009 10:42: > >> Hi Community, >>   The recent release 2.6 of the maven-eclipse-plugin created many problems >> for all of those who had/wanted to store non-java files under src/*/java >> (which

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

Arnaud HERITIER wrote at Donnerstag, 16. April 2009 10:42: > Hi Community, > The recent release 2.6 of the maven-eclipse-plugin created many problems > for all of those who had/wanted to store non-java files under src/*/java > (which is required for wicket, ajdt, and probably others usecases). >

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

thx for this feedbackI deployed a new snapshot : 2.7-20090427.230850-4 It includes the fixe for MECLIPSE-455 : Invalid dependent module archive name for EJB artifact * * Cheers Arnaud On Tue, Apr 21, 2009 at 2:15 PM, Martijn Dashorst < martijn.dasho.

Re: maven eclipse plugin problem with ejb projects

hi Steffen, Thx a lot. I'll apply it soon (I'll try this WE) cheers Arnaud On Fri, Apr 24, 2009 at 2:24 AM, Steffen Grunwald < steffen.grunw...@gmail.com> wrote: > Hello Arnaud, > > > Can you also provide an integration test to validate the issue ? > > If you give me ne, I'll apply them on

Re: maven eclipse plugin problem with ejb projects

Hello Arnaud, > Can you also provide an integration test to validate the issue ? > If you give me ne, I'll apply them on 2.7 Great. There you go. I attached the testcase to [1]. Thanks, Steffen [1] http://jira.codehaus.org/browse/MECLIPSE-455 ---

Re: maven eclipse plugin problem with ejb projects

I just reviewed it.Thx for your help. Can you also provide an integration test to validate the issue ? If you give me ne, I'll apply them on 2.7 Cheers, Thx On Thu, Apr 23, 2009 at 1:03 PM, Steffen Grunwald < steffen.grunw...@gmail.com> wrote: > Hello, > > I'm facing an issue mentioned in bug [1

  1   2   3   >