pgrade of the plugin-parent I faced 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
rew
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
/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 maven-eclipse-plugin hasn't been updated for a while
On 9 May 2014 18:49, Thomas Broyer t.bro...@gmail.com 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 way, but I
that M2Eclipse and the maven-eclipse-plugin are not compatible. In
M2E it specifically looks for project files created with the
maven-eclipse-plugin and disables them.
On May 9, 2014, at 2:19 AM, Thomas Broyer t.bro...@gmail.com wrote:
Hi all,
Does the Apache Maven Project/Community has
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 maven-eclipse
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 all
On Oct 4, 2013, at 5:18 PM, Andreas Dolk andreas.dolk.mo...@googlemail.com
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
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
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
Hi!
I have a source directory structure like below (1).
I have maven project that compiles uses include in the pom.xml and all builds
OK. When I run mvn eclipse:eclipse in same directory I do not get a usable
Eclipse project. The classes dir after compilation looks like (2). I suggest
that in
Thanks for suggestions, Barrie and Wayne! I will have a look at
maven-eclipse-plugin source code later.
To clarify,
source1.5/source corresponds to javac -source option and to ECJ
org.eclipse.jdt.core.compiler.source setting
target1.6/target corresponds to javac -target option and to ECJ
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/display/JENKINS/Building
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 somehow
to add this feature
):
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
probably need to scratch your own itch.
Pull down the source
of this:
org.eclipse.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 specific
configuration of the plugin, thus it does not currently exist
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
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
On Sat, Mar 3, 2012 at 6:28 AM, Markku Saarela markku.saar...@iki.fi 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
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
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 resources
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 need to set your maven properly but it works fine unless I don't
understand your issue.
Only way to do
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 they
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
remote
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 remote application debugging? But still this does not
prevent unit
jar-with-dependencies
/descriptorRef
/descriptorRefs
/configuration
/execution
/executions
/plugin
/plugins
/pluginManagement
/build
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
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
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
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 the docs and do some fiddling.
-
To unsubscribe, e-mail: users-unsubscr
classpathContainerorg.eclipse.jst.j2ee.internal.web.container/classpathContainer
is not right???
wtpapplicationxmltrue/wtpapplicationxml 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 baerr
I have a webapp project under eclipse by my colleage. So it has WEB-INF/lib
directory
and dependcy packages are put in by my colleage.
Now I have create a pom file for the project. But import the maven project
, I also need to configurate the classpath for it through
project --properties--Java
Thanks Barrie!
2011/11/18 Barrie Treloar baerr...@gmail.com:
On Fri, Nov 18, 2011 at 6:19 AM, Gabriel Belingueres
belingue...@gmail.com wrote:
Hi!
I usually use the maven eclipse plugin (v2.8) using the
downloadSources and downloadJavadocs properties, however I added some
runtime scoped
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
On Fri, Nov 18, 2011 at 6:19 AM, Gabriel Belingueres
belingue...@gmail.com 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
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 baerr...@gmail.com wrote:
Does anyone actually use pde mode in maven-eclipse-plugin?
The support looks pretty
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:
, Barrie Treloarbaerr...@gmail.com 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
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 felix for doing this stuff.
EclipseOSGiManifestWriter
On Wed, Sep 28, 2011 at 11:40 AM, Stephen Coy st...@resolvesw.com 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
We're building bundles with the following build configuration:
packagingbundle/packaging
build
extensions
extension
groupIdorg.apache.felix/groupId
artifactIdorg.osgi.core/artifactId
version1.2.0/version
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
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-Eclipse-Plugin
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 psyn...@yahoo.com wrote:
I
On Thu, Jul 14, 2011 at 3:09 AM, Jeff MAURY jeffma...@jeffmaury.com 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
Eclipse plugin to add specific
natures when eclipse:eclipse is run.
Groovy support in maven-eclipse-plugin may not be complete.
You are welcome to provide patches with test cases to fix this.
I can see from the IT pom that there are no Groovy natures installed.
But when you run mvn compile
On Thu, Jun 30, 2011 at 12:45 AM, Sebastian Goldt sd...@cam.ac.uk 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
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
On Thu, Jun 30, 2011 at 4:43 PM, Guillaume Polet
guillaume.po...@gmail.com 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...
-
\maven\maven-eclipse-plugin\target\test-classes\projects\groovy
,
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\groovy\target\test-classes
[DEBUG] testOutput after toRelative : target/test-classes
[DEBUG] Processing resource dir:
D:\ide\maven\maven-eclipse-plugin\target\test-classes
On Thu, Jun 30, 2011 at 09:13, Guillaume Polet guillaume.po...@gmail.comwrote:
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
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 anything
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
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
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
Does anyone know a way to remove the M2_REPO classpath variable that was
added using
mvn -Declipse.workspace=pathtoworkspace 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
Does anyone know a way to remove the M2_REPO classpath variable that was
added using
mvn -Declipse.workspace=pathtoworkspace 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
: 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=pathtoworkspace eclipse:configure-workspace?
I don't know how (or even if) you can do this with the Eclipse
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
-
To unsubscribe, e-mail: users-unsubscr
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 using m2eclipse, you *CAN NOT* use maven-eclipse-plugin,
hence it being removed in 2.8
[del]
Just wondering why support
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
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
: 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 Maven
On Mon, Dec 6, 2010 at 10:39 AM, Brian Topping topp...@codehaus.org 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
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
On Mon, Dec 6, 2010 at 12:51 AM, Asmann, Roland roland.asm...@adesso.at 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
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 no active development for adding wtp 3.x support
:
On Mon, Dec 6, 2010 at 12:51 AM, Asmann, Rolandroland.asm...@adesso.at 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
(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
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/main/java
add an include pattern. Default maven filters out java files.
Martijn
On Sun, Nov 7, 2010 at 11:26 AM, James Ring s...@jdns.org 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
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 request.
An alternative:
http://maven.apache.org/plugins/maven-eclipse-plugin
On Sat, Oct 30, 2010 at 2:34 AM, john.vint johnvin...@gmail.com 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.
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, e-mail: users-unsubscr
for some interested developer to take over the
maven-eclipse-plugin? Isn't this an open source community?
Martijn
On Wed, Oct 27, 2010 at 7:28 PM, Wayne Fay wayne...@gmail.com wrote:
When I run eclipse:eclipse the project name in the .project file will be the
artifactId (by default) despite
for some interested developer to take over the
maven-eclipse-plugin? Isn't this an open source community?
It is hard to get enthusiastic about maintaining old software that has
been replaced by better stuff that is free.
Get Eclipse/STS and you have a much more current supported set of code
On Thu, Oct 28, 2010 at 2:54 PM, Ron Wheeler
rwhee...@artifact-software.com 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
.
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?
It is hard to get enthusiastic about maintaining old software that has been
replaced by better stuff
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?
Martijn
On Wed, Oct 27, 2010 at 7:28 PM, Wayne Fay wayne
it and share it, then 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
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 perceived
2010/10/28 Wayne Fay wayne...@gmail.com:
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:
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
On 28/10/2010 9:35 AM, Martijn Dashorst wrote:
On Thu, Oct 28, 2010 at 2:54 PM, Ron Wheeler
rwhee...@artifact-software.com 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
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
all settings that you set up in Eclipse
unless you also set them up in your pom via configuration:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
This causes a problem when eclipse tries to build new projects workspace
because the eclipse workspace project is one thing
completely different.
How come the maven-eclipse-plugin will never resolve the workspace project
name to the .project project name. Or even offer a flag like
useEclipseProjectNametrue/useEclipseProjectName to override the original
functionality?
--
View this message in context:
http://maven.40175.n5
]
mi...@misha-d630:~/tmp$
This line:
Couldn't find a version in [3.2.1-R32x_v20060717, 3.2.100-v20070522,
3.3.0-v20100503] to match range [3.3.0,4.0.0)
seems like a bug in maven-eclipse-plugin? Clearly 3.3.0-v20100503] does
I read the instructions on
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
but they didn't quite work for me in a maven multi-module project.
Are there any useful links or working examples for such a setup out there?
Thank you all in advance!
Moritz
the builder run, changing resourcer
requires maven-eclipse-plugin.
Or maybe I am making something wrong.
On Wed, Jun 16, 2010 at 9:18 PM, Wayne Fay wayne...@gmail.com wrote:
Actually, m-e-p does not create any .project while M2Eclipse import both
of
them... and the multi-module is useless and 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 builder run, changing resourcer
requires maven-eclipse-plugin.
Or maybe I am making
On Tue, Jun 15, 2010 at 12:04 PM, Daniele Dellafiore ilde...@gmail.com 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
both of
them... and the multi-module is useless and I will just delete it.
On Wed, Jun 16, 2010 at 5:14 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
On Tue, Jun 15, 2010 at 12:04 PM, Daniele Dellafiore ilde...@gmail.com
wrote:
I have patched maven-eclipse-plugin to create an eclipse
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
Hi everyone.
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 me.
In case, I can work on it and submit a patch.
I
On Thu, Mar 11, 2010 at 6:39 PM, Pascal Kesseli
pascal_kess...@hotmail.comwrote:
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:
plugin
groupIdorg.apache.maven.plugins/groupId
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:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.8/version
/resources/directory
targetPathch/hsr/ifs/flexclipse/resources/targetPath
/resource
/resources
...
/build
my resources are copied to target/main instead to
target/main/ch/hsr/ifs/flexclipse/resources when using the configuration
generated by the maven-eclipse-plugin
Oh, duh. Thanks.
On Mon, Mar 1, 2010 at 7:16 PM, Barrie Treloar baerr...@gmail.com wrote:
On Tue, Mar 2, 2010 at 7:05 AM, Benson Margulies bimargul...@gmail.com
wrote:
I'm on Windows, running mvn from cygwin, using the maven-eclipse-plugin.
I
construct a file URL that works fine in IE
I'm on Windows, running mvn from cygwin, using the maven-eclipse-plugin. I
construct a file URL that works fine in IE and firefox, but fails in maven:
[INFO] Unable to read file:
file://C:/cygwin2/home/benson/wst/BasisCodeFormatter.xml
Anyone have a suggestion?
On Tue, Mar 2, 2010 at 7:05 AM, Benson Margulies bimargul...@gmail.com wrote:
I'm on Windows, running mvn from cygwin, using the maven-eclipse-plugin. I
construct a file URL that works fine in IE and firefox, but fails in maven:
[INFO] Unable to read file:
file://C:/cygwin2/home/benson/wst
1 - 100 of 539 matches
Mail list logo
