We have to document it. It's due to the workspace configuration parameter.
workspace is now recognized by the eclipse:eclipse goal to find others
projects :
http://jira.codehaus.org/browse/MECLIPSE-344
it should define where is your eclipse workspace.
Why did you use it with ${basedir}?
I'll see
Do you know if there are plans to include MECLIPSE-79 in 2.5? I believe
that it's the most voted for issue and it has a patch attached.
http://jira.codehaus.org/browse/MECLIPSE-79
Or does anyone know why it's applied?
Thanks for your time,
Jim
On 1/31/08, Arnaud HERITIER [EMAIL PROTECTED]
I have workspace${basedir}/workspace to point to the top directory
of my multi module project.
This element used to be recognizable ONLY by
add-maven-repo/configure-workspace mojos.
however, in 2.5 eclipse goal now also recorgizes it at well. Perhaps
eclipse:eclipse goal should have a different
There's something I don't understand.
The workspace parameter used in eclipse:configure-workspace and in
eclipse:add-maven-repo (which now deprecated by configure-workspace) has to
point to your workspace directory of eclipse. Not your project directory ?
Generally this parameter is defined in
On Jan 31, 2008 12:30 PM, Arnaud HERITIER [EMAIL PROTECTED] wrote:
There's something I don't understand.
The workspace parameter used in eclipse:configure-workspace and in
eclipse:add-maven-repo (which now deprecated by configure-workspace) has to
point to your workspace directory of eclipse.
We effectively resolved all issues with a greater priority ;-)
I will have a look at it to see if it's easy to add with a test case (and if
it doesn't break something).
Arnaud
On Jan 31, 2008 9:00 PM, Jim Sellers [EMAIL PROTECTED] wrote:
Do you know if there are plans to include MECLIPSE-79 in
I didn't see this usage to have the eclipse workspace in the root directory
of your project. But why not ;-)
Effectively, in your case you call configure-workspace only in this
directory and not in sub-modules.
In all cases it's not normal that a bad workspace directory break the
eclipse:eclipse
Arnaud, please don't loose this one
http://jira.codehaus.org/browse/MECLIPSE-316 :)
There is also a minor RAD issue coming, I'll put it in JIRA in a few...
Siarhei
Yes I understand when you have only one project.
But you have only one level of modules or eclipse accept to have its
projects in several levels of subdirectories (for example root/a/b/pom.xml)
?
Arnaud
On Jan 31, 2008 11:06 PM, Dan Tran [EMAIL PROTECTED] wrote:
Thanks, In fact my use case is
Thanks, In fact my use case is a good one. I have a team of 20
developers on the same project, same eclispe workspace
configuration ( ie same code style setup), and the workspace
configuration is at the sameplace for all developers ( which is at the
root pom level).
This works out great. ( no
If it is an environment variable it should be ${env.AF_CLASSPATH} ??
Did you try ?
Arnaud
On Jan 30, 2008 11:49 PM, 8 [EMAIL PROTECTED] wrote:
I have the following in my pom.xml:
dependency
groupIdoracle.apps/groupId
artifactIdoracle.apps.all/artifactId
Hi Arnaud,
Thanks for the info. I tried that, too. Unfortunately, that didn't work
either. Again, both ${AF_CLASSPATH} and ${env.AF_CLASSPATH} work from the
command line.
Arnaud HERITIER wrote:
If it is an environment variable it should be ${env.AF_CLASSPATH} ??
Did you try ?
Arnaud
Oops, I forgot to post the Eclipse error displayed:
Required library cannot denote external folder: 'C:\oracle\apps' for project
'MyProgram'
Obviously, c:\oracle\apps points to a class folder... hmm.
Arnaud HERITIER wrote:
If it is an environment variable it should be ${env.AF_CLASSPATH}
Can you perhaps jar up the classes in that path, and then specify the
full jar name, or even better check it into your local Maven repo
cache using install:install-file?
Wayne
On 1/30/08, 8 [EMAIL PROTECTED] wrote:
Oops, I forgot to post the Eclipse error displayed:
Required library
Unfortunately, the class folder contains over 100,000 .class files (typical
Oracle fat)... and since jars can only contain 65K files, this will not
work (I'm using Java 5). I guess I can put it in two or more jar files, but
that's pretty messy. Also, that still doesn't address why this doesn't
geirgp wrote:
I have 2 projects tied together by a main project which has packaging
pom and both the other projects as modules. directory layout is as
..and .project and .classpath files are generated for each of the
(maven)projects individually The main project's classpath does not
We use archiva 1.0.
I've checked the external repositories, they're ok. And I already
encountered this situation (external repository down) but it was
impacting mvn install too, not only mvn eclipse:eclipse.
I recently thought about this possibility and so configured archiva to
remember
Erratum :
I configured archiva to remembers errors on remote repositories but how
can we do the same for local ones ?
Julien CARSIQUE a crit:
We use archiva 1.0.
I've checked the external repositories, they're ok. And I already
encountered this situation (external repository down) but
With which version of archiva is it ?
With a version 1.0 (I didn't test with 1.0) I have a similar problem for 2
reasons :
- Some external repositories proxied by archiva were down and each time
archiva tried to download a missing artifact it waited the http timeout
(probably 1min) to try another
mvn eclipse:clean eclipse:eclipse has just finished
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 134 minutes 34 seconds
[INFO] Finished at: Thu Dec 20 18:14:35 CET 2007
[INFO] Final Memory: 66M/254M
134 minutes to
Hi,
I've fixed MECLIPSE-316, can you have a look please?
Siarhei
On 11/26/07, Arnaud HERITIER [EMAIL PROTECTED] wrote:
Hi users,
For several days now I tried to clean up a little bit issues recorded in
Jira.
For the next version of the plugin we have already the following issues
Thanks for the info.
Is there no support for same feature on a per-project basis ?
2007/11/15, Dan Tran [EMAIL PROTECTED]:
it is in 2.5-SNAPSHOT and in the new configure-workspace's mojo. You
will need to build the site your self to see the doc
-D
On Nov 14, 2007 11:53 PM, nicolas de
it is in 2.5-SNAPSHOT and in the new configure-workspace's mojo. You
will need to build the site your self to see the doc
-D
On Nov 14, 2007 11:53 PM, nicolas de loof [EMAIL PROTECTED] wrote:
I'v found some POMs that use maven-eclipse-plugin 2.5-SNAPSHOT with
workspaceCodeStylesURL
I can't
It is possible this configuration is not currently available in the
plugin -- I don't need that myself, and I haven't looked at the code,
so I'm not sure myself.
If it is not, I expect the code would be relatively trivial to add
yourself, and contribute back via a patch. I'd encourage you to take
In eclipse 3.3, it's WTP 2.0 which is bundled (but which isn't yet
supported by the eclipse plugin (AFAIK).
The R7 is a very old release.
You can try with the wtpversion=1.5 to see if eclipse succeed to
upgrade the settings.
cheers
Arnaud
On 23/08/07, thebugslayer [EMAIL PROTECTED] wrote:
Hi
Thanks for explaining Arnaud.
It works when using version 1.5 then do QuickFix.
-Z
On 8/23/07, Arnaud HERITIER [EMAIL PROTECTED] wrote:
In eclipse 3.3, it's WTP 2.0 which is bundled (but which isn't yet
supported by the eclipse plugin (AFAIK).
The R7 is a very old release.
You can try with
Hi,
I have a similar problem...
Added a dependency to my PDE project run mvn eclipse:clean
eclipse:eclipse and only the .project file is generated (without those
linkedResources!). The .classpath file is not generated at all!!!
Moreover, running mvn install on the project fails because the
On Mon, June 11, 2007 5:45 pm, Adrian Herscu wrote:
I have a similar problem...
Added a dependency to my PDE project run mvn eclipse:clean
eclipse:eclipse and only the .project file is generated (without those
linkedResources!). The .classpath file is not generated at all!!!
Moreover,
On 6/11/07, Graham Leggett [EMAIL PROTECTED] wrote:
On Mon, June 11, 2007 5:45 pm, Adrian Herscu wrote:
I have a similar problem...
Added a dependency to my PDE project run mvn eclipse:clean
eclipse:eclipse and only the .project file is generated (without those
linkedResources!). The
Hi Graham,
Upgraded to 2.4-SNAPSHOT solved the missing .classpath issue :-)
Besides the .classpath issue, the eclipse:eclipse also does some bad
changes to the OSGI manifest file. It tries to guess the right bundle
name from the maven artifactId and version, but it gets it wrong (labels
are
Tom Huybrechts wrote:
Generating PDE projects is much different from ordinary projects. PDE
handles the classpath and interproject dependencies itself. Maven
should never generate these, and certainly not try to link to a jar in
the local repository. For external dependencies, you should think
Graham Leggett wrote:
I am trying to get the eclipse plugin to generate an eclipse config that
can be built using PDE (via the maven-pde-plugin).
To do this, the packaging type needs to be zip. However - when this is
the case, the eclipse plugin refuses to write a .classpath file, and my
Hi,
Maven Eclipse plugin does not allow to configure Project name which is
very
much required or at least generated project name should use group id also
in
the eclipse project name as artifact id doesn't remain unique across
different group.
Is this a question or just a complaint about a
Hi Barrie, I understand about create a separate resource module that
can be shared.
Let me ask a quick question though. You mention you don't use a flat
structure. This isn't a flat structure as far as i can tell...it is
hierarchical.
It's my understanding that a flat structure puts both
On 4/17/07, Davis Ford [EMAIL PROTECTED] wrote:
Hi Barrie, I understand about create a separate resource module that
can be shared.
Let me ask a quick question though. You mention you don't use a flat
structure. This isn't a flat structure as far as i can tell...it is
hierarchical.
Fair
Davis Ford wrote:
[ .. ]
The .classpath file for the guide-ide-eclipse-site project contains this:
classpathentry kind=src path=D:/temp/guide-ide-eclipse/conf
excluding=**/*.java/
This seems completely reasonable, and the directory does exist, but
eclipse cannot build the projectwhy?
It says: Project child is missing required source folder: 'D:/temp/parent/conf'
Try the steps to reproduce it..easy to reproduce.
I think perhaps it has more to do with the eclipse jdt core. Can it
handle absolute paths? I've tried editing the .classpath file
manually to make it a relative
Hi, it appears that in order for eclipse to see relative path links
like this, an entry needs to be made to the .project file with the
linkeResources tag. If you manually add a src folder in eclipse, this
is the change it makes in .project.
Is there some way to cause the maven-eclipse-plugin to
On 4/17/07, Davis Ford [EMAIL PROTECTED] wrote:
Hi, it appears that in order for eclipse to see relative path links
like this, an entry needs to be made to the .project file with the
linkeResources tag. If you manually add a src folder in eclipse, this
is the change it makes in .project.
Is
Srepfler Srgjan schrieb:
When you say parent project are you referring to a multi module
project? What would the equivalent of it be under eclipse, I mean it's
not a project with a java nature, what is it? Also if such a feature
would need to be implemented I believe the only way to achieve
Srepfler Srgjan wrote:
this was my original question that eclipse:eclipse only generates
project files for each of the modules but not for the parent project.
So I guess this would be a really nice feature.
Regards,
Ingo
When you say parent project are you referring to a multi module
Hi Steven,
this was my original question that eclipse:eclipse only generates
project files for each of the modules but not for the parent project. So
I guess this would be a really nice feature.
Regards,
Ingo
Steven Coco schrieb:
This is good news. But I think it's not as easy for me as
Ingo Düppe wrote:
Hi Steven,
this was my original question that eclipse:eclipse only generates
project files for each of the modules but not for the parent project.
So I guess this would be a really nice feature.
Regards,
Ingo
When you say parent project are you referring to a multi module
This is good news. But I think it's not as easy for me as for you!!
Well it is really straight forward. I just have my maven 2.0
multi-modules project as a eclipse project.
After I ran mvn eclipse:eclipse I imported the nested projects through
the standard project import by pointing into my
The new upcoming Eclipse Version 3.2 (Callisto) does support nested
projects. So there is no need for any workaround to get nested project
structure into eclipse.
I can configure it manually and it works. Also there are no nested
src-folders. It only ends up with two projects that will use
On 5/12/06, Ingo Düppe [EMAIL PROTECTED] wrote:
The new upcoming Eclipse Version 3.2 (Callisto) does support nested
projects. So there is no need for any workaround to get nested project
structure into eclipse.
I am interested in that feature. Perhaps others are as well. Could you
please drop
Well it is really straight forward. I just have my maven 2.0
multi-modules project as a eclipse project.
After I ran mvn eclipse:eclipse I imported the nested projects through
the standard project import by pointing into my multi-modules project.
In older Version you got an error because of
Hello,
I use the eclipse plug in to generate the .classpath and .project files.
These work fine for all my submodules, but it doesn't generate these
files for the top module.
How can I generate a .classpath file for the top project that contains
all source-folders and dependencies of the
Filing a JIRA issue is the best way to go about getting something changes/added.
On 6/10/05, Haryon [EMAIL PROTECTED] wrote:
I'm using maven-eclipse-plugin 1.9, but we have a slightly different
way of using jar sources. We use a plugin that packs the src and put
them into the repository under
If you say dependency...typetld/type.../dependency in the POM (and
put the files in the tlds subdirectory on the repository), the eclipse
plugin won't generate the .classpath references. (I do this all the time.)
Dan Greening, Ph.D. CEO BigTribe http://dan.greening.name/contact.htm
See the documentation for the plugin:
http://maven.apache.org/reference/plugins/eclipse/properties.html
The section below the table of properties describes exactly how to add
dependencies from another project.
-Original Message-
From: Joe Shomphe [mailto:[EMAIL PROTECTED]
Sent:
I attached the patch to the issue.
-Original Message-
From: Eric Pugh [mailto:[EMAIL PROTECTED]
Sent: Monday, June 28, 2004 4:35 PM
To: Maven Users List
Subject: RE: Maven eclipse plugin
Sure.. There have been some changes to try and decouple
plugins from each
other
Sure.. There have been some changes to try and decouple plugins from each
other.. A while back it seemed like every plugin had a very tight
dependency on every other plugin!
Eric
-Original Message-
From: STRAYER, JON (SBCSI) [mailto:[EMAIL PROTECTED]
Sent: Monday, June 28, 2004
Hi there,
On Wednesday 26 May 2004 17:29, Al Robertson wrote:
I had a problem with the maven eclipse:generate-classpath as well.
With me, it is due to having 2 or 3 src folders.
Specifying src/java and src/test/java generated
Using both goals - eclipse:generate-project and
incrementally.
This seems like something everyone would have run into, so I wonder what I
am doing differently. Any ideas?
- Original Message -
From: Heritier Arnaud [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 8:38 AM
Subject: RE : Maven eclipse
]
To
Maven Users List [EMAIL PROTECTED]
cc
Subject
Re: Maven eclipse plugin question re: source folder
My project is already imported into eclipse using maven eclipse, and
it's
working ok. As I do new development, I add dependencies to the project.xml
file and need to update my
the
source tree into Java packages. Running maven eclipse no longer upsets it.
- Original Message -
From: Heritier Arnaud [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 8:38 AM
Subject: RE : Maven eclipse plugin question re: source folder
Why do you call
Stefan,
im not sure about this ajde problem (since you indicate that it is
already present), however the main issue here is the api changes
introduced with the M5 release. mevenide now supports M4 (in cvs at
least) but not M5 yet.
last, about the ajde dependency version : it is not required
Hi,
im not sure about this ajde problem (since you indicate that it is
already present), however the main issue here is the api changes
introduced with the M5 release. mevenide now supports M4 (in cvs at
least) but not M5 yet.
You know what was changed? I can do a patch with a tiny hint
Stefan Groschupf wrote:
im not sure about this ajde problem (since you indicate that it is
already present), however the main issue here is the api changes
introduced with the M5 release. mevenide now supports M4 (in cvs at
least) but not M5 yet.
You know what was changed? I can do a patch
201 - 260 of 260 matches
Mail list logo
