On Sat, Dec 19, 2009 at 9:48 AM, Benson Margulies bimargul...@gmail.com wrote:
The eclipse plugin forces the compiler source version to 1.4 for maven
plugins. I'm building a maven plugin that I want to require 1.5. Is
there a way to tell the eclipse plugin to stop harassing me?
Did you check
I did.
On Sun, Dec 20, 2009 at 5:26 PM, Barrie Treloar baerr...@gmail.com wrote:
On Sat, Dec 19, 2009 at 9:48 AM, Benson Margulies bimargul...@gmail.com
wrote:
The eclipse plugin forces the compiler source version to 1.4 for maven
plugins. I'm building a maven plugin that I want to require
On Sun, Dec 20, 2009 at 5:26 PM, Barrie Treloar baerr...@gmail.com wrote:
On Sat, Dec 19, 2009 at 9:48 AM, Benson Margulies bimargul...@gmail.com
wrote:
The eclipse plugin forces the compiler source version to 1.4 for maven
plugins. I'm building a maven plugin that I want to require 1.5
:
On Sun, Dec 20, 2009 at 5:26 PM, Barrie Treloar baerr...@gmail.com wrote:
On Sat, Dec 19, 2009 at 9:48 AM, Benson Margulies bimargul...@gmail.com
wrote:
The eclipse plugin forces the compiler source version to 1.4 for maven
plugins. I'm building a maven plugin that I want to require 1.5
The eclipse plugin forces the compiler source version to 1.4 for maven
plugins. I'm building a maven plugin that I want to require 1.5. Is
there a way to tell the eclipse plugin to stop harassing me?
-
To unsubscribe, e-mail
MessageI have installed
m2eclipse, and tried to execute this command: mvn
eclipse:eclipse
Then I got this
error: The plugin 'org.apache.com.plugins:maven-eclipse-plugin' does not exist
or no valid version could be found
What is
wrong
'org.apache.com.plugins:maven-eclipse-plugin' does not exist
or no valid version could be found
What is
wrong?
_
De nieuwe Windows 7: vind de juiste pc voor jou. Meer informatie.
http://windows.microsoft.com/shop
--
Become a Wicket expert, learn from
, james.w.jackson
james.w.jack...@baesystems.com wrote:
I'm using maven 2.2.1 and maven-eclipse-plugin 2.7 with a multi-module
project.
When I run 'mvn eclipse:eclipse' in the multi-module project, it doesn't
generate .project eclipse files for the projects that are marked as
packagingpom
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:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
configuration
packagingjar
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 project
useful for a
multi-module projects with many component and sub-component parent poms.
p.s. I missed this.
See http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html
Right towards the bottom is this
Note, you have to delete the .project-file of your parent project
before. The result
On Sat, Oct 24, 2009 at 1:58 AM, Vincent F vincent.fu...@sgcib.com 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
with
the irritating folder location. Unless you want to write your own Eclipse
plugin that rearranged the display in this case.
Thanks Benson, not working with WTP myself, this was exactly what I
wanted to explain to Vincent
My plugin configuration is the following
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.7/version
configuration
packagingwar/packaging
useProjectReferencesfalse/useProjectReferences
On Fri, Oct 23, 2009 at 6:31 AM, Vincent F vincent.fu...@sgcib.com wrote:
My plugin configuration is the following
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.7/version
configuration
packagingwar
with
the irritating folder location. Unless you want to write your own Eclipse
plugin that rearranged the display in this case.
On Thu, Oct 22, 2009 at 6:21 PM, Barrie Treloar baerr...@gmail.com wrote:
On Fri, Oct 23, 2009 at 6:31 AM, Vincent F vincent.fu...@sgcib.com
wrote:
My plugin configuration
WTP, and
telling eclipse:eclipse to write configuration for WTP, you are stuck with
the irritating folder location. Unless you want to write your own Eclipse
plugin that rearranged the display in this case.
Thanks Benson, not working with WTP myself, this was exactly what I
wanted to explain
Hi,
I'm trying to move my current project structure to Maven Standard Directory
Layout, so that everything I had in /WebContent is now in src/main/webapp .
It works fine for the packaging.
However, when using maven-eclipse-plugin 2.7 to update my Eclipse project
and configuration files, I
-plugin and src/main/webapp with Eclipse
Hi,
I'm trying to move my current project structure to Maven Standard
Directory Layout, so that everything I had in /WebContent is now in
src/main/webapp .
It works fine for the packaging.
However, when using maven-eclipse-plugin 2.7 to update my Eclipse
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-plugin and src/main/webapp with Eclipse
Hi,
I'm
you are running eclipse:eclipse?
I suspect that you are not enabling wtp support.
Have you read
http://maven.apache.org/plugins/maven-eclipse-plugin/examples/multi-module-projects.html
I can see from the eclipse plugins code that if packaging = war then
a source directory is added.
The default
@maven.apache.org
Subject: maven-eclipse-plugin and src/main/webapp with Eclipse
Hi,
I'm trying to move my current project structure to Maven Standard
Directory Layout, so that everything I had in /WebContent is now in
src/main/webapp .
It works fine for the packaging.
However, when using
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
configuration
ajdtVersion1.5/ajdtVersion
/configuration
See
Hi
i have a problem with the maven-eclipse-plugin.
my projects pom.xml look like this
project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=
http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd
Hi,
I've got an Eclipse plugin, which I'd like to build using Maven. Is
there any plugin, archetype or something else, which could help me to
start?
Thanks,
Jochen
--
Base64 decoding, 300% faster than sun.misc.BASE64Decoder:
http://archive.netbsd.se/?ml=commons-deva=2008-05t=7522166
On 11-Aug-09, at 11:43 PM, Jochen Wiedmann wrote:
Hi,
I've got an Eclipse plugin, which I'd like to build using Maven. Is
there any plugin, archetype or something else, which could help me to
start?
Tycho: https://docs.sonatype.org/display/M2ECLIPSE/Tycho+project+overview
Tycho is what we
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
Where wtpversion can be R7, 1.0, 1.5, 2.0 or none (default
use
mvn -Dwtpversion=3.1 eclipse:eclipse
--
View this message in context:
http://www.nabble.com/maven-eclipse-plugin-and-wtp-tp24808685p24808760.html
Sent from the Maven - Users mailing list archive at Nabble.com
On Tue, Aug 4, 2009 at 9:27 AM,
massive.boissonmassive.bois...@gmail.com 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
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.boissonmassive.bois...@gmail.com wrote:
Hi, I have a maven project (that is web project by its nature) and I want to
run it in eclipse
On Tue, Aug 4, 2009 at 9:56 AM, Martin Gaintymgai...@hotmail.com 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?
Thank you guys,
I do need to debug.
It was not obvious at all to me how to import existing java web maven
project into eclipse wtp project using m2 eclipse plugin. And I tried to
figure it out.
Do you have a hint or two?
Thanks
-MB
mgainty wrote:
m2 is the better solution if you need
m2 eclipse plugin. And I tried to
figure it out.
Do you have a hint or two?
Thanks
-MB
mgainty wrote:
m2 is the better solution if you need to debug
curious as to what term CI means?
Martin
Ask about software clunker upgrade program
On Wed, Jul 15, 2009 at 12:17 PM, Dirk Olmesd...@xanthippe.ping.de 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
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 think that there is
currently no easy way to augment the
This is not the functionality I described. What you describe already
works in 2.5, as it is the multimodule functionality. What I described
is that you can check out Wicket into your workspace, and start
hacking on your own Wicket application, where the
maven-eclipse-plugin:2.7 will find
on your own Wicket application, where the
maven-eclipse-plugin:2.7 will find the wicket projects and link them
as a project instead of a jar dependency.
I dont think what you are discussing is what they are discussing.
I think the term link was used to mean selecting the project
:
This is not the functionality I described. What you describe already
works in 2.5, as it is the multimodule functionality. What I described
is that you can check out Wicket into your workspace, and start
hacking on your own Wicket application, where the
maven-eclipse-plugin:2.7 will find the wicket
On Thu, Jun 18, 2009 at 7:42 PM, Daniele Dellafioreilde...@gmail.com wrote:
this is exactly what I understood.
I have, in the same folder, two projects, A and B. A uses B as dependancy.
I expect that when I mvn eclipse:eclipse A it uses B as a link, in eclipse,
rather than pointing to the jar
Hi everyone.
I read here:
http://martijndashorst.com/blog/2009/05/29/maven-eclipse-plugin-woes-fixed/
that eclipse maven plugin 2.7 has a new feature such as such as
searching your workspace for projects that are snapshot dependencies,
and adding a project link instead of a jar dependency..
How
, if you have a dependency on MySubModuleLib, it
doesn't seem to link it. If you like to MyMaterLib, it would.
HTH
Jim
On Wed, Jun 17, 2009 at 12:25 PM, Daniele Dellafiore ilde...@gmail.comwrote:
Hi everyone.
I read here:
http://martijndashorst.com/blog/2009/05/29/maven-eclipse-plugin-woes-fixed
On Thu, Jun 18, 2009 at 6:05 AM, Jim Sellersjim.sell...@gmail.com wrote:
I've found that it only works if your other projects:
1) have the same parent and you run the maven command from the parent
They should be able to have different parents.
2) the other project is at the top level of your
MECLIPSE-548 is a showstopper for many projects that would otherwise use
maven-eclipse-plugin. I suspect many projects using the plugin are now
pinned to 2.5. This issue is marked as Critical priority, has six votes
and four watchers. Can anyone take at look at this issue? If you do not
intend
# Arnaud Héritier
# http://blog.aheritier.net
On Tue, Jun 16, 2009 at 8:08 AM, Ben Caradoc-Davies
ben.caradoc-dav...@csiro.au wrote:
MECLIPSE-548 is a showstopper for many projects that would otherwise use
maven-eclipse-plugin. I suspect many projects using the plugin are now
pinned to 2.5
The Maven team is pleased to announce the release of the Maven Eclipse
Plugin, version 2.7
This 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/
You should specify
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-Eclipse
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 baerr...@gmail.com wrote:
On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
On Wed,
-plugin/2.7-SNAPSHOT/maven-eclipse-plugin-2.7-20090529.071922-5.pom
9K downloaded
Downloading:
http://repository/artifactory/repo/org/apache/maven/plugins/maven-eclipse-plugin/2.7-SNAPSHOT/maven-eclipse-plugin-2.7-20090529.071922-5.jar
203K downloaded
[INFO
for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
Downloading:
http://repository/artifactory/repo/org/apache/maven/plugins/maven-eclipse-plugin/2.7-SNAPSHOT/maven-eclipse-plugin-2.7-20090529.071922-5.pom
9K downloaded
Downloading:
http://repository/artifactory
On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar baerr...@gmail.com wrote:
I went quickly hacking an existing IT test to include the resources
definition you provided and some debugging output (as ERROR so I
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 ari.me...@gmail.com wrote:
Hi Arnaud,
I just tested with maven
as maven behaves: see above...
According to me the eclipse plugin
should take the resources part of the pom into account, rather than
invent yet another way of specifying where resources live.
The plugin takes it diirectly from the in memory copy of the pom via
project.getBuild().getResources
On Wed, May 27, 2009 at 3:58 PM, Martijn Dashorst
martijn.dasho...@gmail.com 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
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 baerr...@gmail.com wrote:
On Wed, May 27, 2009 at 3:58 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
With Wicket, we have Page.html, Page.properties,
could
see it)
[ERROR] Resources = [Resource {targetPath: null, filtering: false,
FileSet {directory:
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\project-53-MECLIPSE-551\src\main\java,
PatternSet [includes: {**/*}, excludes: {**/*.java, **/*.sample}]}}]
[DEBUG] Processing resource
On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar baerr...@gmail.com 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
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 ari.me...@gmail.com
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 resources part of the pom into account, rather than
invent yet another way
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
.
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 few developpers involved in it and the darkness
resources in src/main/java
that Maven would not package these.
They must be in src/main/resources.
What is wrong with configuring your ide to behave how Maven behaves?
This will stop you having moments where it works in Eclipse but Maven fails.
According to me the eclipse plugin
should take
.
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 few developpers involved in it and the darkness
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
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
the ajdtVersion to none
(see [1])
[1]
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#ajdtVersion
- Henry
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h
Hi, I've been using mvn for a lot of years now, but I've just
encountered a bizarre issue that I have no explanation for.
I am having trouble with the following dependencies
dependency
groupIdaspectj/groupId
artifactIdaspectjrt/artifactId
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
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
On Wed, Apr 29, 2009 at 4:13 PM, Jörg Schaible joerg.schai...@gmx.de 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
Hi Barrie,
Barrie Treloar wrote at Mittwoch, 29. April 2009 09:03:
On Wed, Apr 29, 2009 at 4:13 PM, Jörg Schaible joerg.schai...@gmx.de
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
PM, Jörg Schaible joerg.schai...@gmx.de
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
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 notice this
issue
actually looking for the types / resources. ;-)
Jim
On Wed, Apr 29, 2009 at 6:02 AM, Dirk Olmes d...@xanthippe.ping.de wrote:
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
:
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).
Even we have many integration tests in this plugin we
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 2.7
Hello,
I'm facing an issue mentioned in bug [1] and [2] that causes a wrong
extension in the eclipse .settings files. This problem still exists in
the 2.6 release.
I submitted a patch quite a while ago and would like to know, if there
are some plans to commit the patch or fix the problem in
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]
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
Hi, I just enabled all snapshots for plugins, and a side effect of
this was to pull down
org.apache.maven.plugins:maven-eclipse-plugin:2.7-SNAPSHOT version of
eclipse plugin.
Now, my project breaks in eclipse b/c it sets the JDK to be (I think)
the system default (which is JDK 1.5), but my maven
That's why we suggest locking down your plugin versions in your poms.
Then you'll have controll over which ones you get as snapshots.
See here for more info:
http://www.sonatype.com/people/2008/04/maven-209-released/
The eclipse plugin does not seem to be one that has a default in the
super
On Fri, Apr 24, 2009 at 11:41 AM, Davis Ford
davisf...@zenoconsulting.biz wrote:
Hi, I just enabled all snapshots for plugins, and a side effect of
this was to pull down
org.apache.maven.plugins:maven-eclipse-plugin:2.7-SNAPSHOT version of
eclipse plugin.
Now, my project breaks in eclipse b
, Davis Ford
davisf...@zenoconsulting.biz wrote:
Hi, I just enabled all snapshots for plugins, and a side effect of
this was to pull down
org.apache.maven.plugins:maven-eclipse-plugin:2.7-SNAPSHOT version of
eclipse plugin.
Now, my project breaks in eclipse b/c it sets the JDK to be (I think
On Fri, Apr 24, 2009 at 12:37 PM, Davis Ford
davisf...@zenoconsulting.biz wrote:
My apologies Barrie...this is the con entry:
classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/
User error. Somehow my eclipse default JDK/JRE setting got switched
back to JDK 5. When I
On Thu, Apr 16, 2009 at 10:42 AM, Arnaud HERITIER aherit...@gmail.comwrote:
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
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 notice this
issue because our testcases
Ping ??Nobody wants to test it ?
Without your help, will never be able to produce a plugin which replies to
your needs.
Cheers,
Arnaud
On Thu, Apr 16, 2009 at 10:42 AM, Arnaud HERITIER aherit...@gmail.comwrote:
Hi Community,
The recent release 2.6 of the maven-eclipse-plugin created many
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).
Even we have many integration tests in this plugin we didn't
branches of a
project in the same workspace)
On Mon, Apr 13, 2009 at 7:09 PM, Stephen Duncan Jr stephen.dun...@gmail.com
wrote:
Amongst several other surprising changes in the 2.6 release of the
maven-eclipse-plugin, I'd like to explain on one change caused some
confusion for myself and other
Amongst several other surprising changes in the 2.6 release of the
maven-eclipse-plugin, I'd like to explain on one change caused some
confusion for myself and other members of my development team. I'm not sure
it's really a bug, or exactly what feature enhancement to file, so I'm
hoping
I think this is intentional to be aligned with the classpath order
that maven sets up when running tests.
See http://jira.codehaus.org/browse/MECLIPSE-318
On Mon, Apr 6, 2009 at 11:07 AM, Martin Gilday martin.li...@imap.cc wrote:
I am running Maven 2.1.0 and 2.6 of the eclipse plugin. For some
HI All
Any idea how do i add additional line to the generated .classpath.
The line is an additional source directory , classpathentry kind=src
path=src/main/java-gen/
I have looked a little in the plugin page and didnt find anything that fits
my needs.
Thanks in advance.
Roman
I am running Maven 2.1.0 and 2.6 of the eclipse plugin. For some reason
after running an eclipse:eclipse on both new and existing projects I am
now getting src/test/java and resources appearing above src/main/java
and resources. This is happening for all developers using our corporate
POM
tests.
See http://jira.codehaus.org/browse/MECLIPSE-318
On Mon, Apr 6, 2009 at 11:07 AM, Martin Gilday martin.li...@imap.cc
wrote:
I am running Maven 2.1.0 and 2.6 of the eclipse plugin. For some reason
after running an eclipse:eclipse on both new and existing projects I am
now getting
On Mon, Apr 6, 2009 at 9:17 PM, Roman Kournjaev kournj...@gmail.com wrote:
HI All
Any idea how do i add additional line to the generated .classpath.
The line is an additional source directory , classpathentry kind=src
path=src/main/java-gen/
I have looked a little in the plugin page and
Hi all,
I have a maven EAR application within RAD in which I used the
Maven-eclipse-plugin version 2.5.1 to integrate with the IDE and run on WAS
6.1 .
I recently upgraded the plugin from 2.5.1 to 2.6 and after issuing an
eclipse:eclipse command on the project, the project's facets disappear
dear，although the maven throws exception when i ran the cmd mvn clean
eclipse:clean eclipse:eclipse -Declipse.addVersionToProjectName=true with
the log i have shown in my last send email,
but the maven eclipse(version) plugin generated my project actually
successfully while i have
not change the
On Thu, Apr 2, 2009 at 4:03 PM, linchongsu sulinchong1...@gmail.com wrote:
hi,dear
i found i can't run mvn clean eclipse:clean eclipse:eclipse
-Declipse.addVersionToProjectName=true all right with version 2.6
If you can provide a small repeatable test case then raise a JIRA and
we can look
oh, all right, but i think ,i should inspect the cmd
-Declipse.addVersionToProjectName=true more carefully.what's more, when i
comes to use version 2.6, my eclipse's workspace does not run as well as
before.
The follow is the log:
[WARNING] could not read workspace
org.codehaus.plexus.util.xml.pull.XmlPullParserException: only whitespace
content allowed before start tag and not \u9518 (position: START_DOCUMENT
\u9518 looks like international character sets.
Not sure why it isn't whitespace.
Same thing, try to make small test case and raise a JIRA.
If
Using maven 2.0.10, I ran into the maven-eclipse-plugin 2.6 bug fix
that excludes anything not Java from being on the classpath. I didn't
upgrade my eclipse plugin, and thought that as of 2.0.8 the root pom
specifies stable plugins for each release. Apparently,
maven-eclipse-plugin is not amongst
201 - 300 of 1126 matches
Mail list logo
