A co-worker tested it, and found it not working. He'll comment later.
Martijn
On Tue, Apr 21, 2009 at 12:20 AM, Arnaud HERITIER aherit...@gmail.com wrote:
Ping ??Nobody wants to test it ?
Without your help, will never be able to produce a plugin which replies to
your needs.
Cheers,
Arnaud
The co-worker reported back that the plugin works as advertised
(latest snapshot)
Martijn
On Tue, Apr 21, 2009 at 10:27 AM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
A co-worker tested it, and found it not working. He'll comment later.
Martijn
On Tue, Apr 21, 2009 at 12:20 AM,
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 Stephen,
Thx a lot for this feedback. I don't remember when and why we did these
changes but I understand your problem. It seems that the autodiscovery of
projects dependencies in the workspace is activated by default. I think that
this feature should be deativated by default (First issue to
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
Added http://jira.codehaus.org/browse/MECLIPSE-538.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Can you confirm that
src/main/aspect
should be
including=**/*.java|**/*.aj
instead of just
including=**/*.aj
Thanks
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
On Fri, Mar 27, 2009 at 12:19 PM, Barrie Treloar baerr...@gmail.com wrote:
Can you confirm that
src/main/aspect
should be
including=**/*.java|**/*.aj
instead of just
including=**/*.aj
Thanks
Ok after googling, I can find more than one project that has java
files in src/main/aspect.
On Fri, Mar 27, 2009 at 12:23 PM, Barrie Treloar baerr...@gmail.com wrote:
On Fri, Mar 27, 2009 at 12:19 PM, Barrie Treloar baerr...@gmail.com wrote:
Can you confirm that
src/main/aspect
should be
including=**/*.java|**/*.aj
instead of just
including=**/*.aj
Thanks
Ok after
Hi,
I've not used aspectj so I'm just guessing what you are trying to do.
Can you explain why you want non-java files on the classpath?
I haven't used AspectJ for myself, but AFAIK .aj files are the sources
for AspectJ. They must be included in the classpath so that the
AspectJ compiler
On Tue, Mar 24, 2009 at 11:58 PM, jb-perso j...@defard.com wrote:
Hi,
I have a problem with eclipse plugin 1.6-SNAPSHOT. When i generate eclipse
project (eclipse : eclipse), this version add **/*.java pattern for source
dir :
classpathentry kind=src path=src/main/java including=**/*.java
None of the project-ajdt test projects actually have source so I need
a working project to build a test against.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
maven-compiler-plugin
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
---
Todd Thiessen
-Original Message-
From: Daniele Dellafiore
That is easy, I am talking about all the others:
org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning
org.eclipse.jdt.core.compiler.problem.autoboxing=warning
org.eclipse.jdt.core.compiler.problem.deprecation=warning
-Original Message-
From: Daniele Dellafiore [mailto:ilde...@gmail.com]
Sent: Wednesday, March 04, 2009 9:19 AM
To: Maven Users List
Subject: Re: [maven-eclipse-plugin] Define compiler options in POM
That is easy, I am talking about all the others
:19 AM
To: Maven Users List
Subject: Re: [maven-eclipse-plugin] Define compiler options in POM
That is easy, I am talking about all the others:
org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning
org.eclipse.jdt.core.compiler.problem.autoboxing=warning
...
---
Todd Thiessen
-Original Message-
From: Daniele Dellafiore [mailto:ilde...@gmail.com]
Sent: Wednesday, March 04, 2009 9:19 AM
To: Maven Users List
Subject: Re: [maven-eclipse-plugin] Define compiler options in POM
That is easy, I am talking about all the others
://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
-Original Message-
From: Daniele Dellafiore [mailto:ilde...@gmail.com]
Sent: Wednesday, March 04, 2009 8:31 AM
To: Maven Users List
Subject: Re: [maven-eclipse-plugin] Define compiler options in POM
On Wed, Mar 4, 2009 at 3:24
: 04 March 2009 14:19
To: Maven Users List
Subject: Re: [maven-eclipse-plugin] Define compiler options in POM
That is easy, I am talking about all the others:
org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning
org.eclipse.jdt.core.compiler.problem.autoboxing=warning
He wants to have different settings per project though.
---
Todd Thiessen
-Original Message-
From: Nord, James [mailto:jn...@nds.com]
Sent: Wednesday, March 04, 2009 11:35 AM
To: Maven Users List
Subject: RE: [maven-eclipse-plugin] Define compiler options in POM
Can you
- Show quoted text -
Subject: RE: [maven-eclipse-plugin] Define compiler options in POM
Can you not change the eclipse worksapce settings instead of
the per project ones.
Then when the settings get clobbered you will still be using
the defaults - but the defaults are what you wanted
Dmitri,
It really doesn't matter if you create projects from the command line of
from inside Eclipse. However being inside Eclipse gives additional
advantages from directly using corresponding tools APIs, such as WTP ones,
so it is more compliant and does not require to reverse engineer WTP
Roland Bali wrote:
Hi,
I would like to add the following to my .classpath when running
eclipse:eclipse. How can I do this?
classpathentry kind=src path=fixtures/
Use the build-helper plugin [1] to add the fixtures directory to your
sources. The maven-eclipse-plugin will pick it up when
Thanks Dirk!
The plugin solved my problem.
/Roland
On Fri, Feb 20, 2009 at 11:20 AM, Dirk Olmes d...@xanthippe.ping.de wrote:
Roland Bali wrote:
Hi,
I would like to add the following to my .classpath when running
eclipse:eclipse. How can I do this?
classpathentry kind=src
we are developing in distributed team. each team member can choose IDE
he(she) likes. So the maven is our project format. I have choosed Eclipse
for me ;) Now i try to integerate maven project in eclipse posibly seamless
and i don't want to miss eclipse convinience features.
2009/2/16 Arnaud
Hi!
On 16 Feb 2009, Dmitri Ilyin wrote:
i wanted to use maven-eclipse-plugin with Eclipse 3.4. After short tries i
have found out that it only support WTP 1.5. The actual version of Eclipse
WTP is 3.x
After that i find that the last version of plugin is 10 month old.
Accoring to a mail
hi,
thanks Martin.
Can you provide an email here? or where can i find it?
Do you know which WTP version will be supported?
regards
Dmitri
2009/2/16 Martin Höller mar...@xss.co.at
Hi!
On 16 Feb 2009, Dmitri Ilyin wrote:
i wanted to use maven-eclipse-plugin with Eclipse 3.4. After short
http://lmgtfy.com/?q=maven+eclipse+plugin+next+release
On 16 Feb 2009, Dmitri Ilyin wrote:
hi,
thanks Martin.
Can you provide an email here? or where can i find it?
Do you know which WTP version will be supported?
regards
Dmitri
2009/2/16 Martin Höller mar...@xss.co.at
Hi!
http://m2eclipse.sonatype.org/
On 16-Feb-09, at 8:49 AM, Dmitri Ilyin wrote:
Hallo,
i wanted to use maven-eclipse-plugin with Eclipse 3.4. After short
tries i
have found out that it only support WTP 1.5. The actual version of
Eclipse
WTP is 3.x
After that i find that the last version
well, this is an eclipse plugin, i need maven plugin.
2009/2/16 Jason van Zyl jvan...@sonatype.com
http://m2eclipse.sonatype.org/
[mailto:ilyin.dmi...@googlemail.com]
Envoyé : lundi 16 février 2009 16:54
À : Maven Users List
Objet : Re: maven-eclipse-plugin
well, this is an eclipse plugin, i need maven plugin.
2009/2/16 Jason van Zyl jvan...@sonatype.com
http://m2eclipse.sonatype.org/
On 16-Feb-09, at 8:49 AM, Dmitri
it where to look for the config
files.
Does this sound adequate? What is your particular requirement?
Cheers,
Jonathan Winterflood
-Message d'origine-
De : Dmitri Ilyin [mailto:ilyin.dmi...@googlemail.com]
Envoyé : lundi 16 février 2009 16:54
À : Maven Users List
Objet : Re: maven
why a plugin in eclipse to support maven doesn't fit your needs ?
Arnaud
2009/2/16 Dmitri Ilyin ilyin.dmi...@googlemail.com
well, this is an eclipse plugin, i need maven plugin.
2009/2/16 Jason van Zyl jvan...@sonatype.com
http://m2eclipse.sonatype.org/
--
Arnaud
I don't know for Dmitri but for me it doesn't support war overlays :)
Best regards,
Siarhei Dudzin
On Mon, Feb 16, 2009 at 10:58 PM, Arnaud HERITIER aherit...@gmail.comwrote:
why a plugin in eclipse to support maven doesn't fit your needs ?
Arnaud
2009/2/16 Dmitri Ilyin
yes, thus your problem is the lack of support on some maven/eclipse
features. And not because you don't want to use it. I suppose you'll take it
as soon as it'll have those missing features.
Arnaud
On Mon, Feb 16, 2009 at 11:32 PM, Siarhei Dudzin
siarhei.dud...@gmail.comwrote:
I don't know for
Sure, I *am* using it :) just not everywhere...
Speaking of which, I can't install it:
Update operation has failed
Error retrieving plugins/org.eclipse.draw2d_3.4.1.v20080910-1351.jar.
[Server returned HTTP response code: 404 Not Found for URL:
Hi,
I have raised a JIRA : http://jira.codehaus.org/browse/MECLIPSE-515
Thank you!
Barrie Treloar baerr...@gmail.com
17.12.2008 21:53
Bitte antworten an
Maven Users List users@maven.apache.org
An
Maven Users List users@maven.apache.org
Kopie
Thema
Re: maven-eclipse-plugin generates bad
My Directory-Stucture looks following:
D:\
- Projekte
- Maven
-maven-user-list
- maven-project-dir
- existing-src-dir
I need to add the Sources in existing-src-dir to the pom in
maven-project-dir.
I think you might want to move the maven-project-dir stuff up into
Can you raise a JIRA with a test case please?
On Wed, Dec 17, 2008 at 10:04 PM, thomas.rosend...@bg-phoenics.de wrote:
Hi,
I want to migrate some existing projects to maven.
My Directory-Stucture looks following:
D:\
- Projekte
- Maven
-maven-user-list
- maven-project-dir
2008/9/19 Tomek Maciejewski [EMAIL PROTECTED]:
...
classpathContainers
classpathContainerorg.elipse.mtj.JavaMEContainer/Sun
Java(TM) Wireless Toolkit 2.5.2 for
CLDC/DefaultColorPhone/classpathContainer
/classpathContainers
Hello,
On Wed, 17 Sep 2008 15:13:31 +0200, Lars Fischer [EMAIL PROTECTED]
mail.org said:
I use the maven-eclipse-plugin with the goal install-plugins to
create an eclipse target-platform containing my bundle-dependencies.
Is is also possible to get the sources of these dependencies into
this
Hello,
On Fri, 19 Sep 2008 08:24:09 +0200, Lars Fischer
I use the maven-eclipse-plugin with the goal install-plugins to
create an eclipse target-platform containing my bundle-dependencies.
Is is also possible to get the sources of these dependencies into
this platform-folder following
Hi Mirko,
did you find a solution?
I´m also using maven-eclipse-plugin, version 2.4 having the same
problem
The test-sources.jar isn´t generated into the .classpath files
Thanx, Torsten
Hi Chris,
Thanks a lot for your feedback.
Can you open an issue in Jira. We'll try to fix this issue in the next
release. I think we have several others issues about facet issues.
Arnaud
On Wed, May 14, 2008 at 8:42 AM, [EMAIL PROTECTED] wrote:
Hi All.
Using V2.5.1 of the
Done.
http://jira.codehaus.org/browse/MECLIPSE-449
However, this leads me to another question.
We can specify the classpath container entries, fine, and that works.
However, doesn't this conflict with the dependencies section (which in
turn generates the .classpath entries which will result
I had to fix the project testcase #10
Indeed, we have a tricky thing here: While file:${M2_REPO} will expand to
a proper URI on Unix, it won't on Windows which would rather need
file:/${M2_REPO}.
I added some hackery to AbstractEclipsePluginTestCase.assertFileEquals() to
fix the URI read from
Salman Moghal wrote:
Hello Salman!
Finally, I've got it working, almost! So, I want to share it...it's gonna be
a bit long, though! I just explain the steps how it's working over here.
I've been using Subclipse with the newly released M2 Plugin (Version 0.9.0).
Actually, the old M2
I don't think releasing anything with failing tests a good idea no matter
whether the problem is with the test or with the plugin.
Siarhei
On Fri, Mar 14, 2008 at 11:07 AM, Benjamin Bentmann
[EMAIL PROTECTED] wrote:
I had to fix the project testcase #10
Indeed, we have a tricky thing
Benjamin,
The fix is good.
I can't reproduce your problem but I had it a long time ago. There's an
issue open for it. After the 2.5 I'll try to completly refactor the plugin
and I'll use xmlUnit to compare xml files instead of using line per line
checks.
It's time to release !!! ;-)
Arnaud
Hi,
we found http://jira.codehaus.org/browse/MECLIPSE-399 here which is quite
annoying,
but should be an easy fix. Is there still a chance getting this into the
upcoming release? :-}
Regards,
Benjamin
no issue found using the latest snapshot with our current devopment
env. , looking
If you produce a complete patch (code, doc, test) before this evening
;-)
Arnaud
On Thu, Mar 13, 2008 at 4:01 PM, nabcos [EMAIL PROTECTED] wrote:
Hi,
we found http://jira.codehaus.org/browse/MECLIPSE-399 here which is quite
annoying,
but should be an easy fix. Is there still a chance
If you produce a complete patch (code, doc, test) before this evening
;-)
Well, the patch ist attached
(http://jira.codehaus.org/secure/attachment/33142/javadoc-file-uri.patch),
it is changing one line, and the current junit-test does not even follow the
execution path down that road...
If you produce a complete patch (code, doc, test) before this evening
Patch has been extended with unit test, please give it a try.
As for the doc: What exactly are you expecting? I mean, the plugin
configuration did not change, the issue is just about complying with the URL
spec.
Thanks nabcos and benjamin,
I'll apply it before to launch the vote.
In this case the documentation isn't necessary because it is a bug fix,
but I prefer to always ask for it ;-)
Thnaks
Arnaud
On Thu, Mar 13, 2008 at 7:38 PM, Benjamin Bentmann
[EMAIL PROTECTED] wrote:
If you produce a
Benjamin,I applied your patch but I had to change a little bit the test case
to pass it on MacOS and I had to fix the project testcase #10
Can you test the build of the plugin and the plugin iself please ?
It's too late now to launch the release. It will be for tomorrow.
cheers
On Fri, Mar 14,
Hello!
I've got RAD7, maven-eclipse-plugin 2.5-Snapshot and m2eclipse 0.0.12. I've
been trying for 2 frustrating days to integrate those tools together without
success. Did any body of you guys succeed this task? I reckon that your are
on the same task as I am.
More precisely, there the
Hi again,
here my plugin configuration. Actually, it's the example given by the post
of Salman. I've added new version of the eclipse plugin and uncommented a
part I didn't understand if need it. Though, I tried versioned projects too.
:
plugins
plugin
/plugin
!-- maven-eclipse-plugin --
Regards
--
Salman Moghal
- Original Message -
From: qnob [EMAIL PROTECTED]
To: users@maven.apache.org
Sent: Wednesday, March 12, 2008 12:43 PM
Subject: Re: maven-eclipse-plugin 2.4 versioned projects
Hi again,
here my plugin configuration
I deployed a new SNAPSHOT (maven-eclipse-plugin-2.5-20080309.224617-25) to
fix MECLIPSE-392. It is the last one before the release. I'll launch the
vote this week.
Cheers
Arnaud.
On Fri, Feb 1, 2008 at 1:51 PM, Jim Sellers [EMAIL PROTECTED] wrote:
That's wonderful. Thanks. ;-)
Jim
On
no issue found using the latest snapshot with our current devopment
env. , looking forward to the vote
Thanks,
-D
On Sun, Mar 9, 2008 at 3:55 PM, Arnaud HERITIER [EMAIL PROTECTED] wrote:
I deployed a new SNAPSHOT (maven-eclipse-plugin-2.5-20080309.224617-25) to
fix MECLIPSE-392. It is the
. If it
does there is definitely an issue with command line arguments that should be
(or may already be) in jira.
hth,
- martin
[0]
http://www.nabble.com/Re:-Maven-eclipse-plugin---2.5-SNAPSHOT-to15833826s177.html
--
Martin Höller | [EMAIL PROTECTED]
*x Software + Systeme
Just for the records: I created a JIRA issue for this as I couldn't find
one: http://jira.codehaus.org/browse/MECLIPSE-394
- martin
On Wednesday 05 March 2008 Salgar, Mehmet (external) wrote:
Yep,
You are right when I used the POM configuration everything runs fine.
This is definetely a
Hi,
It's better to ask such question on the mailing list. You should have
replies quickly.
Did you define a wtpversion set to 1.5 in your project's pom or in a
parent ?
There's an issue open somewhere in the core because we noticed that the
command line parameter do not more override the
I've been pouring through maven-eclipse-plugin 2.4 code and realized that
there is potentially a problem with
org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponentWriter class
(line 125), IMHO:
writer.addAttribute( ATTR_DEPLOY_NAME,
config.getProject().getArtifactId() );
It
I've done quite some troubleshooting around RAD6+maven. I would advise to
override the finalName for the artifact so it doesn't have version at the
end.
It's even better if those match the project directory names.
maven-eclipse-plugin 2.5-SNAPSHOT has quite a lot of improvements in RAD6/7
change as outlined earlier.. which I plan on doing today. Any
thoughts on this approach?
Regards
Salman Moghal
- Original Message
From: Siarhei Dudzin [EMAIL PROTECTED]
To: Maven Users List users@maven.apache.org
Sent: Wednesday, February 27, 2008 5:01:44 AM
Subject: Re: maven-eclipse
On Wed, Feb 27, 2008 at 5:37 PM, Salman Moghal [EMAIL PROTECTED] wrote:
Thanks so much for the response. Yes, I agree that it would be ideal if
the name of the generated jar/war/ear file is kept same as the project
directory name -- I believe that's what finalName does as per the docs (?).
Thanks again for the prompt response..
It
is
indeed
as
you
mentioned
finalName.
If
they
don't
want
to
have
final
name
fixed
you
could
probably
somehow
parse
the
ibm-specific
deployment
descriptors.
Because
artifact
names
are
actually
hardcoded
there.
So
if
your
and another task not recorded : to test the plugin with all 2.0.X version to
update the minimum requirement.
Arnaud
On Wed, Feb 27, 2008 at 11:01 AM, Siarhei Dudzin [EMAIL PROTECTED]
wrote:
I've done quite some troubleshooting around RAD6+maven. I would advise to
override the finalName for
: Re: maven-eclipse-plugin 2.4 versioned projec
On
Wed,
Feb
27,
2008
at
5:37
PM,
Salman
Moghal
[EMAIL PROTECTED]
wrote:
Thanks
so
much
for
the
response.
Yes,
I
agree
that
it
would
be
ideal
if
the
name
of
the
generated
jar/war/ear
file
is
kept
same
Sorry to reply to your question with another question, but
does RAD6 really supports WTP 1.5 ?
I was under the impression that RAD7 only supported that version.
-Olivier
On Tue, 2008-02-26 at 12:38 -0800, Salman Moghal wrote:
Hello:
I'm using maven-eclipse-plugin v2.4 to generate WTP 1.5
I think we have several problems with manifest in 2.5-SNAPSHOT :-(
wtpmanifest = true creates several problems.
We noticed this one :
http://jira.codehaus.org/browse/MECLIPSE-389
It can be (or not) related
Arnaud
On Thu, Feb 21, 2008 at 8:20 AM, Martin Höller [EMAIL PROTECTED] wrote:
On
Martin Höller wrote:
No, it's not, it's a WTP 2.0 project. My plugin configuration is as follows:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.5-SNAPSHOT/version
configuration
On Thursday 21 February 2008 wrote Arnaud HERITIER:
I think we have several problems with manifest in 2.5-SNAPSHOT :-(
wtpmanifest = true creates several problems.
We noticed this one :
http://jira.codehaus.org/browse/MECLIPSE-389
It can be (or not) related
It is (at least somehow) related.
On Thursday 21 February 2008 wrote Graham Leggett:
Martin Höller wrote:
No, it's not, it's a WTP 2.0 project. My plugin configuration is as
follows:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
I prefer to have a new issue and a link between them.
You can wait to have it fixed OR you can propose a patch (code+test+doc) to
be sure it will be.
Arnaud
On Thu, Feb 21, 2008 at 10:24 AM, Martin Höller [EMAIL PROTECTED] wrote:
On Thursday 21 February 2008 wrote Arnaud HERITIER:
I think we
On Thursday 21 February 2008 wrote Arnaud HERITIER:
I prefer to have a new issue and a link between them.
Created: http://jira.codehaus.org/browse/MECLIPSE-392
You can wait to have it fixed OR you can propose a patch (code+test+doc)
to be sure it will be.
Currently I'm too busy but maybe
On synchronizing a pde plugin with maven-eclipse-plugin, it looks to me that
Manifest.mf file do get synchronized even though it is in META-INF folder.
Does maven-eclipse-plugin synchronizes it with .classpath or how?
Regards,
Amit
On Fri, Feb 22, 2008 at 1:13 PM, Martin Höller [EMAIL
Martin Höller wrote:
I just noticed that the maven-eclipse-plugin (2.5-SNAPHSOT) writes a
MANIFEST.MF output to src/main/webapp/META-INF when mvn eclipse:eclipse is
called for a web-application.
Is this behaviour intentional? I wouldn't expect maven or any plugin to
write something into
On Wednesday 20 February 2008 wrote Graham Leggett:
Martin Höller wrote:
I just noticed that the maven-eclipse-plugin (2.5-SNAPHSOT) writes a
MANIFEST.MF output to src/main/webapp/META-INF when mvn eclipse:eclipse
is called for a web-application.
Is this behaviour intentional? I
I happen to know a little bit about this (mainly because my colleague created
these options ;-) ).
I believe that version of the plugin hasn't been released yet, although it
could be that a SNAPSHOT-release has been made. If not, check out the latest
sources and build it for yourself, it
Refreshes are configured.
I tried your suggestion, but .. No luck ;)
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 16:39
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
It appears there are still
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 16:06
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
I asked my colleague, it could be that the parameter has changed. He suggests
trying 'eclipse.workspace
,
Pedro
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 16:06
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
I asked my colleague, it could be that the parameter has changed. He
suggests trying
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
I happen to know a little bit about this (mainly because my colleague
created these options ;-) ).
I believe that version of the plugin hasn't been released yet, although it
could be that a SNAPSHOT-release has
, Pedro Manuel wrote:
Refreshes are configured.
I tried your suggestion, but .. No luck ;)
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: jeudi, 7. février 2008 16:39
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution
The best thing to do for this release to happen soon,
is to try the latest SNAPSHOT on your projects an repport any issue !
Nico.
2008/2/5, Siarhei Dudzin [EMAIL PROTECTED]:
IMHO, Arnaud is busy preparing it (which means soon)...
2008/2/5 [EMAIL PROTECTED]:
Hello,
Do you know the
IMHO, Arnaud is busy preparing it (which means soon)...
2008/2/5 [EMAIL PROTECTED]:
Hello,
Do you know the release date of the maven-eclipse-plugin 2.5 ??
Thx
__ [image: JDSS]
*Olivier Lambert* Transversal Team Technique - JDSS CH207 - Tel:
Also see these threads:
http://www.nabble.com/maven-eclipse-plugin-2.5-coming-soon-to15207954s177.html#a15211821
http://www.nabble.com/eclipse:eclipse-different-JDK's-to15086638s177.html#a15097832
hth,
- martin
--
Martin Höller | [EMAIL PROTECTED]
*x Software + Systeme
There is only one issue to finalize :
http://jira.codehaus.org/browse/MECLIPSE-344
Richard van Nieuwenhoven is working on it.
Probably in February but when it's to difficult to define ..
Arnaud
2008/2/5 nicolas de loof [EMAIL PROTECTED]:
The best thing to do for this release to happen soon,
Not sure, we always perform dependency resolution before generating project
files. Besides if the project doesn't compile in the version control this
often means you have much bigger problem. :)
Anyway try mvn process-resources, this seems to run just before compilation
begins and should resolve
We (the dev team) know this annoying bug but we don't have yet found a fix.
I'm not sure we'll be able to fix it for 2.5. Nicolas ?
I'm not sure that there's an issue opened for it. If you can check.
Arnaud
On Feb 1, 2008 9:22 AM, Martin Höller [EMAIL PROTECTED] wrote:
Hi all!
I have an
Hi!
On Thursday 31 January 2008 wrote Arnaud HERITIER:
We fixed a lot of issues for the version 2.5 of the eclipse plugin and
we'll launch the vote to release it in few days.
I'm using it here and it works without problems (beside the one I just
reported).
- martin
--
Martin Höller
On Friday 01 February 2008 wrote Siarhei Dudzin:
Not sure, we always perform dependency resolution before generating
project files. Besides if the project doesn't compile in the version
control this often means you have much bigger problem. :)
You may be right on this one. However, if you have
On Friday 01 February 2008 wrote Arnaud HERITIER:
We (the dev team) know this annoying bug but we don't have yet found a
fix. I'm not sure we'll be able to fix it for 2.5. Nicolas ?
Thanks for clarifying this Arnaud.
I'm not sure that there's an issue opened for it. If you can check.
I
I've tested this patch and applied it with a minor change :
separator for groupId and artifactId is :, as used by other maven plugins
(see maven-assembly-plugin)
Nico.
2008/1/31, Jim Sellers [EMAIL PROTECTED]:
Do you know if there are plans to include MECLIPSE-79 in 2.5? I believe
that it's
You may be right on this one. However, if you have a much bigger project,
you force a new developer to perform a build (which might take a long
time)
before he can start developing.
I understand now. Would publishing snapshots to your own remote repository
work? You could then only generate
On Friday 01 February 2008 wrote Siarhei Dudzin:
You may be right on this one. However, if you have a much bigger
project, you force a new developer to perform a build (which might take
a long time)
before he can start developing.
I understand now. Would publishing snapshots to your own
That's wonderful. Thanks. ;-)
Jim
On 2/1/08, nicolas de loof [EMAIL PROTECTED] wrote:
I've tested this patch and applied it with a minor change :
separator for groupId and artifactId is :, as used by other maven
plugins
(see maven-assembly-plugin)
Nico.
2008/1/31, Jim Sellers [EMAIL
I ran into problem during eclipse:eclipse
here is my configuration
plugin
artifactIdmaven-eclipse-plugin/artifactId
version2.5-SNAPSHOT/version
configuration
workspace${basedir}/workspace
wtpversion1.5/wtpversion
101 - 200 of 260 matches
Mail list logo
