that includes Eclipse 3.3.1.1 and WTP
>> 2.0.1
>> >>>>>
>> >>>>> any Idea ?
>> >>>>>
>> >>>>> Thanks
>> >>>>> Yann.
>> >>>>
>> -
Ok, thanks a lot for your feedback.
I'll try to fix it before the release of the 2.5
Arnaud
On Dec 5, 2007 8:51 PM, Yann Albou <[EMAIL PROTECTED]> wrote:
>
> So I did others tests using each times new Eclipse workspace:
>
> 1) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin
> v
So I did others tests using each times new Eclipse workspace:
1) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin
version 2.5-SNAPSHOT => I get the same behaviour in EUROPA
2) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin
version 2.4 => I get the same beh
Did you define the M2_REPO variable (in Eclipse)?
Yann Albou wrote:
> Is someone facing the same issue ?
> Yann.
>
> Yann Albou a écrit :
>> Hello,
>>
>> After generating my eclipse projects with "mvn -Dwtpversion=2.0
>> eclipse:eclipse" and importing these projects into an europa
>> workspace
Can you create a little test case and open an issue please ?
I didn't yet found this problem but it's perhaps a bug in one change I made
to add the support of WTP 2.0.
Another test that you can do :
- generates WTP settings for version 1.5
- import your project into eclipse (it should convert them
I just tried with the latest snapshot and I get the same behaviour.
I see these warnings during import.
on the Warning it exists a "Quick fix" that says :"Mark the associated
raw classpath entry as a publish/export dependency". So I execued it
And then I get an error that says "Invalid classpath
Do you get the same from getting the latest snapshot instead of the trunk?
Where do you see this waring? During import or after import in the problems
view?
On 12/4/07, Yann Albou <[EMAIL PROTECTED]> wrote:
>
> Is someone facing the same issue ?
> Yann.
>
> Yann Albou a écrit :
> > Hello,
> >
> >
Is someone facing the same issue ?
Yann.
Yann Albou a écrit :
Hello,
After generating my eclipse projects with "mvn -Dwtpversion=2.0
eclipse:eclipse" and importing these projects into an europa workspace I
get the following Warning:
"Claspath entry
M2_REPO/commons-logging/commons-logging/1
Hello,
After generating my eclipse projects with "mvn -Dwtpversion=2.0
eclipse:eclipse" and importing these projects into an europa workspace I
get the following Warning:
"Claspath entry
M2_REPO/commons-logging/commons-logging/1.0.4/commons-loggin-1.0.4.jar
will not be exported or published
It's a problem on the rar plugin that doesn't have an artifact handler
descriptor.
The eclipse plugin look at the handler to define if it's a java project or not, and without this
handler, the language of rar project is defined by default to "none" instead of
"jar".
Please file an issue.
Emma
the maven-eclipse-plugin?
--
View this message in context:
http://www.nabble.com/-M2--Eclipse-plugin-will-not-generate-project-descriptor-for-RAR-artifacts--tf3575551s177.html#a9991405
Sent from the Maven - Users mailing list archive at
Hi
Just double-click on the version you want, and it will add it in. Kind of
confusing with other version in grey, but works.
Hermod
-Opprinnelig melding-
Fra: Marouane Amraoui [mailto:[EMAIL PROTECTED]
Sendt: 14. mars 2007 13:06
Til: users@maven.apache.org
Emne: M2 Eclipse Plugin
Hallo
from what i understand maven identifies its dependencies by groupId and
artifactId, the version itself seems to relevant to retrieval of the jar
file only.
maybe you could manually add that dependency into the pom.xml?
Marouane Amraoui schrieb:
Hi.
the fileX-1.0.jar d
Hi.
the fileX-1.0.jar depends to fileY-2.3.jar
my application depends to fileX-1.0 and fileY-2.4.
I added dependency for my application to fileX-1.0.jar success.
Using the Add dependecy tools on the pom file I can't add dependency for my
application to fileY-2.4 because is with
Hello,
is there a way to specify the project dependencies between some
artifacts of a J2EE application in pom.xml ?
In my application, I have a war which depends of some JARS and I d like
to specify this depencency with the eclipse plugin
Is it possible ?
Thanks for your help!
Regards,
Ale
hi Daniel ,
thanks so much for your reply.
today, I also come across the some solution blogged by Matt Riable at 2004 :-D
http://raibledesigns.com/page/rd?anchor=eclipse_tips
~manchi
On 2006-10-17 04:13:43 +0800, Daniel Serodio <[EMAIL PROTECTED]> said:
Man-Chi Leung wrote:
hi,
after I did
. Oktober 2006 06:31
An: users@maven.apache.org
Betreff: [M2] eclipse plugin ?
Hey all,
wich m2 eclipse plugIn's do you know and use?
http://mevenide.codehaus.org/release/eclipse/update/site.xml seems to
be only for maven1 ?!
---
/update/site.xml seems to
> be only for maven1 ?!
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://ww
Hey all,
wich m2 eclipse plugIn's do you know and use?
http://mevenide.codehaus.org/release/eclipse/update/site.xml seems to
be only for maven1 ?!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMA
Man-Chi Leung wrote:
> hi,
>
> after I did "mvn eclipse:eclipse" and got the project imported to
> eclipse
>
> I found a very long list of jar showing in eclipse's Package Explorer.
>
> however, not all the jars that i am actually programming for , i
> believe , they are simply the dependencies o
Maven2 has so called transitive dependencies, e.g. if you add hibernate.jar
dependency, Maven will automatically add some "extra" dependencies (Jar
files) which hibernate consists of.
--
View this message in context:
http://www.nabble.com/-m2--eclipse-plugin---too-many-jar-showing-
Man-Chi Leung wrote on Tuesday, October 03, 2006 4:36 AM:
> hi,
>
> after I did "mvn eclipse:eclipse" and got the project
> imported to eclipse
>
> I found a very long list of jar showing in eclipse's Package Explorer.
>
> however, not all the jars that i am actually programming for , i
> bel
hi,
after I did "mvn eclipse:eclipse" and got the project imported to eclipse
I found a very long list of jar showing in eclipse's Package Explorer.
however, not all the jars that i am actually programming for , i
believe , they are simply the dependencies of dependencies.
in eclipse plugi
10:20
Aan: Maven Users List
Onderwerp: Re: [m2] Eclipse plugin does not seem to make references for
packaging "sar"
That's because addedToClasspath = false in the components.xml for
jboss-sar
see
https://svn.mojo.codehaus.org/mojo/trunk/mojo/mojo-sandbox/jboss-sar-mav
en-plugin/src
o). However the Maven reactor build remains broken preventing me to
> compile/install/deploy an ear with sar components.
>
>
> -Original Message -
> From: Peschier J. (Jeroen)
> Sent: vrijdag 7 april 2006 17:07
> To: Maven Users List
> Subject: [m2] Eclipse plugin does
From: Peschier J. (Jeroen)
Sent: vrijdag 7 april 2006 17:07
To: Maven Users List
Subject: [m2] Eclipse plugin does not seem to make references for
packaging "sar"
I have some projects that depend on projects with packaging "sar". I
observe the following behaviour:
- Running
I have some projects that depend on projects with packaging "sar". I
observe the following behaviour:
- Running eclipse:eclipse from the parent POM, project references to
dependencies with packaging jar and ejb are made. However the project
references for sar projects seem to be omitted.
- Runnin
On 3/29/06, Nicolas De Loof <[EMAIL PROTECTED]> wrote:
>
>
>
> I'm using a maven-proxy, but it doesn't seem to keep in cache failed
> request.
>
>
Maven-proxy has a configuration property to enable caching of failures:
repo.www-ibiblio-org.cache.failures=true
I've never checked if it works...
I'm using eclipse source-download facility and it's great to get sources
or javadoc attached in Eclipse classpath.
Now my project uses oracle JDBC driver and some IBM classes, and I would
like to mark those dependencies so that eclipse plugin doesn't try to
get sources : it checks ibiblio an
Our web project has a custom tag library for one of the sub-projects and the
Eclipse Sysdeo Tomcat plugin doesn't handle it well if it's included directly
as a project link instead of as a jar from the M2_REPO. Since it's otherwise
useful to have project links that the eclipse plugin generates,
Hi,
I'm trying to use the M2 Eclipse Plugin but running into a strange problem:
running mvn compile from the command line works fine (no errors), running
the compile target through the M2 plugin as an external tool just like the
flash demo shows results in the following:
Hi!
Given I might find some time I would like to implement the possibility
to add arguments to the buildcommands.
I would like to archive this by allowing to add a CDATA section to every
buildcommand in pom.xml.
So in the end it should look like this:
org.eclipse.ui.externaltools.ExternalT
Before have a look on the workaround :
http://jira.codehaus.org/browse/MECLIPSE-3
- Olivier
-Message d'origine-
De : Du,Guo [mailto:[EMAIL PROTECTED]
Envoyé : mardi 14 mars 2006 11:06
À : Maven Users List
Objet : Re: [m2] eclipse-plugin how to reference other projects in a
multi-m
List"
Sent: Tuesday, March 14, 2006 7:59 AM
Subject: [m2] eclipse-plugin how to reference other projects in a
multi-module project?
Hi,
I have set up a reactor/multi-module project as follows.
Parent (pom project)
+ A
+ B (depends on A)
+ C (depends on B)
+ D (depends
Hi,
I have set up a reactor/multi-module project as follows.
Parent (pom project)
+ A
+ B (depends on A)
+ C (depends on B)
+ D (depends on A, C)
(A,B,C,D are the modules).
When I run eclipse:eclipse goal the project dependencies are not setup
in project's .classpath file. Coul
Hi,
I have set up a reactor/multi-module project as follows.
Parent (pom project)
+ A
+ B (depends on A)
+ C (depends on B)
+ D (depends on A, C)
(A,B,C,D are the modules).
When I run eclipse:eclipse goal the project dependencies are not setup
in project's .classpath file. Could
>Have you tried version 0.0.5 of the plugin? It works for me on Mac OSX
>10.4.4.
Ahh! Thanks! What a difference +0.0.1 makes. Its compiling now. I have
some jar ordering problems on the classpath that I don't have when I run
from the command line, but I think I can handle that problem.
-Scot
site.
>
>
> Tom.
>
> 2006/2/14, Scott M Mcclements <[EMAIL PROTECTED]>:
>> My question is about the differences between the M2 Eclipse Plugin and the
>> plain old command line M2 version. What advantages does the plugin
>> provide? I checked out a project (A
Tom.
2006/2/14, Scott M Mcclements <[EMAIL PROTECTED]>:
> My question is about the differences between the M2 Eclipse Plugin and the
> plain old command line M2 version. What advantages does the plugin
> provide? I checked out a project (Apache Tusqany) into my eclipse
> workspa
My question is about the differences between the M2 Eclipse Plugin and the
plain old command line M2 version. What advantages does the plugin
provide? I checked out a project (Apache Tusqany) into my eclipse
workspace. I have the M2 plugin installed - on the console I see:
2/13/06 8:13:53 PM
This is definitely a possibility. You'll find the IDE won't let you
edit the sources that was downloaded, but when it comes to checking it
out there are a few options.
1) we are planning something like "workspaces" in a future version
that will let you bootstrap projects and lay them out in your
f
I am exploring a development scenario using M2 within an IDE and would
like some thoughts on it.
The use case is a follows:
Given a multi module build with 2 modules, A and B. B has a declared
dependency on A. My repository has a snapshot of A as well as a
corresponding source jar.
A
Hi,
I've been using m2 and maven-eclipse-plugin for some time for developing
EJB3 apps. I've found it useful to have POM type projects responsible
for managing my ear build, in a structure something like:
mymodule
+- mymodule-build-config (type: POM)
+- mymodule-ear (type: ear)
+
John,
You can add an "m2 build" configuration to your list of builders.
Kees
On 2/2/06, John Fallows <[EMAIL PROTECTED]> wrote:
> Folks,
>
> I've recently started playing around with the M2 Eclipse plugin - very cool
> stuff!
>
> Just wondering, apa
Folks,
I've recently started playing around with the M2 Eclipse plugin - very cool
stuff!
Just wondering, apart from managing the libraries and neat repository
searching, does M2 Eclipse plugin also implement an Eclipse Builder that
would make sure all sources and resources are generated b
When you have a project using a code generator plugin, how can we add the
generated sources in the list of eclipse source directory?
This problematic was seemingly handled in Mavane 1.x (As I read on
http://maven.apache.org/maven-1.x/reference/plugins/eclipse/), but there is
no similar thing
Hi,
mvn eclipse:eclipse always killed my servlet container configuration in
Eclipse, now I know why.
For wtp you must set the following plugin configurations:
org.eclipse.jst.server.core.container/org.eclipse.jst.server.tomcat.runtimeTarget/Apache
Tomcat v5.0
org.eclipse.jst.j2ee.internal.
The Eclipse and Site plugins are both still marked as beta. They are
very close to a release.
After that, no beta plugins will be released into the main repository,
so you won't have to worry about the automated update aspect.
Additionally, you can lock your projects to particular versions of
plug
Meant to say:
"Would be nice to hear from the Maven team on this topic"
On 11/4/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote:
>
> Would be nice to hea
>
> On 11/4/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote:
> >
> > Agreed. I think care should be taken with plugins that get automatical
Would be nice to hea
On 11/4/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote:
>
> Agreed. I think care should be taken with plugins that get automatically
> updated as this has already created many unpleasant surprises. I think by
> default only "stable" versions should be distributed as part of
Agreed. I think care should be taken with plugins that get automatically
updated as this has already created many unpleasant surprises. I think by
default only "stable" versions should be distributed as part of the Maven
core. Something like xxx-2.0-beta-2 doesn't belong in a production
environment
ok, then something must be wrong on my side because i had to declare
the M2_REPO classpath variable to point to my local repository to get
rid of the errors. here is my eclipse classpath file
where i set M2_REPO to point to
"C:/Work/Mainten
Hi Anuerin,
I think you are wrong :-)
This is clearly a (btw, blocking) bug in the Eclipse plugin. I find it odd
that this isn't detected before this version was released, especially give
that M2 is communicated as "production ready". This along with the site
plugin that generates a nullpointer m
hi,
doesnt M2_REPO supposed to resolve to the user's local repository?
if that is the case and assuming the local repository is
"c:\repository" then the final path will be
"c:\repository/C:/dev/Java/jdk1.5.0_04/jre/../lib/tools.jar" which i
think is already invalid.
i am a new maven user
+1 on this
2005/11/3, Thomas Van de Velde <[EMAIL PROTECTED]>:
> Hi,
>
> When generating the Eclipse classpath, I am getting this:
>
> path="M2_REPO/C:/dev/Java/jdk1.5.0_04/jre/../lib/tools.jar"/
>
> This used to work a couple of days ago and now all of a sudden I get this
> error.
>
> Thomas
>
>
Hi,
When generating the Eclipse classpath, I am getting this:
I posted: http://jira.codehaus.org/browse/MNG-1332 This has a quick
patch that enables the eclipse plugin to work for .wtpmodules.
Check out maven-eclipse-plugin out of svn into eclipse. apply the
patch and then from the command line issue 'mvn install
-DupdateReleaseInfo=true.
Have fun.
have no
> > clue about
> > the difference between so-called reactor projects and 'normal'
> > projects.
> >
> > Cheers,
> > Franck
> >
> > -Original Message-
> > From: Brian Bonner [mailto:[EMAIL PROTECTED]
> > Sent: dins
ence between so-called reactor projects and 'normal' projects.
>
> Cheers,
> Franck
>
> -Original Message-----
> From: Brian Bonner [mailto:[EMAIL PROTECTED]
> Sent: dinsdag 25 oktober 2005 18:41
> To: Maven Users List
> Subject: Re: m2 eclipse plugin wtp
projects and 'normal'
projects.
Cheers,
Franck
-Original Message-
From: Brian Bonner [mailto:[EMAIL PROTECTED]
Sent: dinsdag 25 oktober 2005 18:41
To: Maven Users List
Subject: Re: m2 eclipse plugin wtpmodules dependencies to artifacts
I should have added:
of EclipseWtpmodules
tually have no clue about
the difference between so-called reactor projects and 'normal' projects.
Cheers,
Franck
-Original Message-
From: Brian Bonner [mailto:[EMAIL PROTECTED]
Sent: dinsdag 25 oktober 2005 18:41
To: Maven Users List
Subject: Re: m2 eclipse plugin wtpmodules d
I should have added:
of EclipseWtpmodulesWriter.
On 10/25/05, Brian Bonner <[EMAIL PROTECTED]> wrote:
> Looking for the same thing :) II looked at the maven-eclipse-plugin
> source and it looks like it should pull these artifacts (check out the
> addDependency() method).
>
> Anyone have a sugges
Looking for the same thing :) II looked at the maven-eclipse-plugin
source and it looks like it should pull these artifacts (check out the
addDependency() method).
Anyone have a suggestion on this?
On 10/24/05, Franck de Bruijn <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
>
> I'm trying out maven 2 and t
Hi,
I'm trying out maven 2 and the eclipse plugin in combination with Eclipse
WTP.
Everything works fine, although I do not manage to generate the 'dependent
modules' section in the .wtpmodules file, like below:
uses
The 'wb-resource' se
MNG-578, MNG-1078
On 10/12/05, Antonio PAROLINI <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Anybody knows what is the status of this bug ? I haven't seen anything
> on jira on this.
>
> I face the same probleme, since I which to use a "POM" dependency type
> in Eclipse. And it's still a Maven2 undoc
Hello,
Anybody knows what is the status of this bug ? I haven't seen anything
on jira on this.
I face the same probleme, since I which to use a "POM" dependency type
in Eclipse. And it's still a Maven2 undocumented feature by the way.
Very best regards,
Antonio
>>> [EMAIL PROTECTED] 10/03 10:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sounds like a bug in the maven-eclipse-plugin...can you file a jira at
http://jira.codehaus.org/Browse/MNG and make sure you specify it as
being a problem with the eclipse plugin? It should be in the modules list.
Thanks,
john
Daniel Krisher wrote:
I have a set of 'third-party' jars that are all part of a library
developed in-house. Most of the projects I work on use all of the
jars from this library, so I put together a simple POM that depends on
all of them. I then add this POM as a dependency of my project:
...
...
This is an issue that was pointed out on this mailinglist in 2003 on maven 1.0
and eclipse:
When I run "maven eclipse", it generates the .classpath file with the
following entry:
whereas when I create a project in Eclipse, a reference to JRE_LIB is
written as:
With the former se
Thanks for the info - looking forward to updated plugin ;)
Did an experiment in eclipse: created a project with 2 src folders
containing com.acme.Foo and com.acme.Bar respectively. Then switched
to the Java Browser perspective and clicked on MyApp and sure enough
I saw the package hierarchy
On Wed, 14 Sep 2005, Ashley Williams wrote:
Hi,
> Just been playing around with eclipse projects. I see that
> eclipse:eclipse makes a separate project for each pom, whilst
> retaining the option to add project references if you want to.
> Wouldn't it make more sense though, for eclipse:eclipse t
Just been playing around with eclipse projects. I see that
eclipse:eclipse makes a separate project for each pom, whilst
retaining the option to add project references if you want to.
Wouldn't it make more sense though, for eclipse:eclipse to add a new
source folder under an existing eclips
Thanks, yes I managed to work out how to work locally on maven code -
simple since they are all maven projects. Excellent!
Whether or not the eclipse plugin has bugs, I think my problem is
actually how to persuade Eclipse to work with my file structure,
because from what I can tell, you are
Hi guys
I need to customize the dir where test reports are placed, does any body
know how?
One more, how can I reference to the src dir from maven.xml, the property
does not work...
Help please
thanks
Lucas
-
To unsubscribe, e-
On Fri, 2 Sep 2005, Ashley Williams wrote:
Hi,
first on your previous mail (one of them anyway): a local fix
is easy, if you have the plugin checked out and your m2 is
beta-1-SNAPSHOT. Just fix it and run m2 install.
> Ok I get four different types of behaviour in eclipse depending on
> what tex
Ok I get four different types of behaviour in eclipse depending on
what text I put in sourceDirectory after running eclipse:eclipse
- StringIndexOutOfBoundsException
running eclipse:eclipse
. - sources in default package,
dependency libs are ther
/ - no package, no dependcy libs,
java fi
Actually forget my last comment I've just seen that eclipse:eclipse
fails in the same way in the following method:
private static String toRelative( File basedir, String
absolutePath )
{
String relative;
if ( absolutePath.startsWith( basedir.getAbsolutePath() ) )
Ok the latest maven seems to work despite the build exception and
happily I was able to run the eclipse:eclipse goal successfully.
However when I open the project in eclipse the files appear under the
(default package) node which means eclipse red crosses everywhere.
This despite the fact t
Oh happy day - not!
Just had a glance at my console only to see the pasted text below -
is this going to be a build breaker? I'm using Java 5 by default, is
this a mistake?? Also Mac OS X doesn't appear to have a tools.jar file.
COPY AND PASTE...
Running maven-core integration tests ...
On Fri, Sep 02, 2005 at 03:34:59PM +0100, Ashley Williams wrote:
> Don't understand what you're saying the problem is, but will the fix
> be quick, i.e. 10 minutes?? If so then I don't mind waiting...
Try now.
--
Trygve
signature.asc
Description: Digital signature
Don't understand what you're saying the problem is, but will the fix
be quick, i.e. 10 minutes?? If so then I don't mind waiting...
On 2 Sep 2005, at 15:31, Trygve Laugstøl wrote:
On Fri, Sep 02, 2005 at 03:27:04PM +0100, Ashley Williams wrote:
Build has failed - it's never easy is it!
On Fri, Sep 02, 2005 at 03:27:04PM +0100, Ashley Williams wrote:
> Build has failed - it's never easy is it!
Sorry about that, I'm fixing that any second now. It got past our CI as
only do a clean build once per night.
You can download the latest Maven 2 snapshot from [1].
[1]: http://maven.zone
Build has failed - it's never easy is it!
I made sure M2_HOME points to a non existent directory and added
nonexistentdirectory/bin to my PATH. then I ran the script and
eventually got this:
Building project in /Users/develop/projects/Burns/maven-components/
maven-artifact-manager ...
---
On Fri, Sep 02, 2005 at 03:08:30PM +0100, Ashley Williams wrote:
> No that didn't work either. In fact I tried a large nonsense string
> too and that also resulted in the very same exception, which
> surprised me. I've just downloaded the maven source code so I'll
> check if I still get the s
No that didn't work either. In fact I tried a large nonsense string
too and that also resulted in the very same exception, which
surprised me. I've just downloaded the maven source code so I'll
check if I still get the same behaviour.
On 2 Sep 2005, at 14:52, Trygve Laugstøl wrote:
On Fri
On Fri, Sep 02, 2005 at 02:47:35PM +0100, Ashley Williams wrote:
> Hi, I'm trying to configure my source directory to be the current
> directory like so:
>
> attempt 1:
>
>
>
> attempt 2:
>
> /
Try ".".
>
> which works fine. The problem is when I subsequently run the
> eclip
Hi, I'm trying to configure my source directory to be the current
directory like so:
attempt 1:
attempt 2:
/
which works fine. The problem is when I subsequently run the
eclipse:eclipse goal, which in both cases results in the following
exception:
java.lang.StringIndexOut
> -Original Message-
> From: John Casey [mailto:[EMAIL PROTECTED]
> Sent: samedi 9 avril 2005 00:31
> To: Maven Users List
> Subject: Re: Maven 2
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Just letting you know that the maven-eclipse-plugin for Maven 2.0 is
> deployed to ib
88 matches
Mail list logo
