You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Joe Bohn <jo...@earthlink.net> on 2006/08/23 19:53:24 UTC
building eclipse projects with M2 build
The cwiki inidicates that we can build projects for eclipse using the m2
build with the following command:
mvn -o eclipse:eclipse
However, when I attempt to do this I get the error below. Has anybody
been successful in building the eclipse projects using M2?
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does
not exist or no valid version could be found
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or no
valid version could be f
ound
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:381)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by:
org.apache.maven.plugin.version.PluginVersionNotFoundException: The
plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or
no valid
version could be found
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:225)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:158)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
... 14 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 8 seconds
[INFO] Finished at: Wed Aug 23 13:51:13 EDT 2006
[INFO] Final Memory: 19M/37M
Re: building eclipse projects with M2 build
Posted by Joe Bohn <jo...@earthlink.net>.
Thanks Jeff. That did the trick for me too!!!
Joe
Jeff Genender wrote:
> Joe,
>
> Delete your ~/.m2/repository/org/apache/maven/plugins directory. The
> error you encountered usually means you have a corrupted meta tags.
> This solution usually does teh trick for me.
>
> Jeff
>
> Joe Bohn wrote:
>
>>Thanks Ian. I did attempt to run it both on-line as well as off-line.
>> Either way I get the same result. Do you see something different?
>>
>>Joe
>>
>>
>>ian.d.stewart@jpmchase.com wrote:
>>
>>>The -o switch tells mvn not to attempt to download any plugins or
>>>dependencies, using only whatever is in your local repository. If
>>>this is
>>>your first time running the eclipse:eclipse goal then the necessary
>>>plugin
>>>won't be present.
>>>
>>>Try running 'mvn eclipse:eclipse' (i.e., no '-o' switch).
>>>
>>>
>>>HTH,
>>>Ian
>>>
>>>It's better to be hated for who you are
>>>than loved for who you're not
>>>
>>>Ian D. Stewart
>>>Distributed Computing Engineer II
>>>DSS eCommerce Engineering
>>>JPMorganChase Global Technology Infrastructure
>>>Phone: (614) 244-2564
>>>
>>>
>>>
>>> Joe
>>>Bohn
>>><joe.bohn@earthli
>>>
>>>nk.net> To
>>> Geronimo
>>>Dev 08/23/2006 01:53
>>><de...@geronimo.apache.org>
>>>PM cc
>>>
>>>
>>>Subject Please respond to building eclipse
>>>projects with M2 dev@geronimo.apac
>>>build
>>>he.org
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>The cwiki inidicates that we can build projects for eclipse using the m2
>>>build with the following command:
>>>
>>>mvn -o eclipse:eclipse
>>>
>>>However, when I attempt to do this I get the error below. Has anybody
>>>been successful in building the eclipse projects using M2?
>>>
>>>
>>>[INFO] Searching repository for plugin with prefix: 'eclipse'.
>>>[INFO]
>>>------------------------------------------------------------------------
>>>[ERROR] BUILD ERROR
>>>[INFO]
>>>------------------------------------------------------------------------
>>>[INFO] The plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does
>>>not exist or no valid version could be found
>>>[INFO]
>>>------------------------------------------------------------------------
>>>[INFO] Trace
>>>org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
>>>'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or no
>>>valid version could be f
>>>ound
>>> at
>>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281)
>>>
>>>
>>> at
>>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517)
>>>
>>>
>>> at
>>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:381)
>>>
>>>
>>> at
>>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
>>>
>>>
>>> at
>>>org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>
>>>
>>> at
>>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:324)
>>> at
>>>org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>> at
>>>org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>Caused by:
>>>org.apache.maven.plugin.version.PluginVersionNotFoundException: The
>>>plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or
>>>no valid
>>> version could be found
>>> at
>>>org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:225)
>>>
>>>
>>> at
>>>org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
>>>
>>>
>>> at
>>>org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:158)
>>>
>>>
>>> at
>>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
>>>
>>>
>>> ... 14 more
>>>[INFO]
>>>------------------------------------------------------------------------
>>>[INFO] Total time: 8 seconds
>>>[INFO] Finished at: Wed Aug 23 13:51:13 EDT 2006
>>>[INFO] Final Memory: 19M/37M
>>>
>>>
>>>
>>>-----------------------------------------
>>>This transmission may contain information that is privileged,
>>>confidential, legally privileged, and/or exempt from disclosure
>>>under applicable law. If you are not the intended recipient, you
>>>are hereby notified that any disclosure, copying, distribution, or
>>>use of the information contained herein (including any reliance
>>>thereon) is STRICTLY PROHIBITED. Although this transmission and
>>>any attachments are believed to be free of any virus or other
>>>defect that might affect any computer system into which it is
>>>received and opened, it is the responsibility of the recipient to
>>>ensure that it is virus free and no responsibility is accepted by
>>>JPMorgan Chase & Co., its subsidiaries and affiliates, as
>>>applicable, for any loss or damage arising in any way from its use.
>>>If you received this transmission in error, please immediately
>>>contact the sender and destroy the material in its entirety,
>>>whether in electronic or hard copy format. Thank you.
>>>
>>>
>>>
>
>
>
Re: building eclipse projects with M2 build
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 8/23/06, Bill Dudney <bd...@apache.org> wrote:
> Hey Jacek,
>
> When its happened to me its been because the pom or jar only
> partially download or some other such bad behavior. Since this simple
> fix makes it work I've not looked any further. I don't see anyway the
> bootstrap could be causing this since the bootstrap is simply
> deleting the .m2/repository directory and then invoking maven.
Doh! I should've been looked at the code yourself. I've just done it
and you're right! Sorry for bothering and thanks for clarification.
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
Re: building eclipse projects with M2 build
Posted by Bill Dudney <bd...@apache.org>.
Hey Jacek,
When its happened to me its been because the pom or jar only
partially download or some other such bad behavior. Since this simple
fix makes it work I've not looked any further. I don't see anyway the
bootstrap could be causing this since the bootstrap is simply
deleting the .m2/repository directory and then invoking maven.
TTFN,
-bd-
On Aug 23, 2006, at 1:28 PM, Jacek Laskowski wrote:
> On 8/23/06, Jeff Genender <jg...@apache.org> wrote:
>> Joe,
>>
>> Delete your ~/.m2/repository/org/apache/maven/plugins directory. The
>> error you encountered usually means you have a corrupted meta tags.
>> This solution usually does teh trick for me.
>
> It did for me, too, but it's weird. I think it may have happened every
> time bootstrap.sh is used. It's just a wild guess, but it happened to
> me once I had built Geronimo with the new build procedure. I think we
> need to check it out before we rule it out as a possible cause.
>
> Is there anyone who has never built Geronimo before and has been
> wondering when exactly give it a shot? It's time now! ;-)
>
> Jacek
>
> --
> Jacek Laskowski
> http://www.laskowski.net.pl
Re: building eclipse projects with M2 build
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 8/23/06, Jeff Genender <jg...@apache.org> wrote:
> Joe,
>
> Delete your ~/.m2/repository/org/apache/maven/plugins directory. The
> error you encountered usually means you have a corrupted meta tags.
> This solution usually does teh trick for me.
It did for me, too, but it's weird. I think it may have happened every
time bootstrap.sh is used. It's just a wild guess, but it happened to
me once I had built Geronimo with the new build procedure. I think we
need to check it out before we rule it out as a possible cause.
Is there anyone who has never built Geronimo before and has been
wondering when exactly give it a shot? It's time now! ;-)
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
Re: building eclipse projects with M2 build
Posted by Jeff Genender <jg...@apache.org>.
Joe,
Delete your ~/.m2/repository/org/apache/maven/plugins directory. The
error you encountered usually means you have a corrupted meta tags.
This solution usually does teh trick for me.
Jeff
Joe Bohn wrote:
> Thanks Ian. I did attempt to run it both on-line as well as off-line.
> Either way I get the same result. Do you see something different?
>
> Joe
>
>
> ian.d.stewart@jpmchase.com wrote:
>> The -o switch tells mvn not to attempt to download any plugins or
>> dependencies, using only whatever is in your local repository. If
>> this is
>> your first time running the eclipse:eclipse goal then the necessary
>> plugin
>> won't be present.
>>
>> Try running 'mvn eclipse:eclipse' (i.e., no '-o' switch).
>>
>>
>> HTH,
>> Ian
>>
>> It's better to be hated for who you are
>> than loved for who you're not
>>
>> Ian D. Stewart
>> Distributed Computing Engineer II
>> DSS eCommerce Engineering
>> JPMorganChase Global Technology Infrastructure
>> Phone: (614) 244-2564
>>
>>
>>
>> Joe
>> Bohn
>> <joe.bohn@earthli
>>
>> nk.net> To
>> Geronimo
>> Dev 08/23/2006 01:53
>> <de...@geronimo.apache.org>
>> PM cc
>>
>>
>> Subject Please respond to building eclipse
>> projects with M2 dev@geronimo.apac
>> build
>> he.org
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> The cwiki inidicates that we can build projects for eclipse using the m2
>> build with the following command:
>>
>> mvn -o eclipse:eclipse
>>
>> However, when I attempt to do this I get the error below. Has anybody
>> been successful in building the eclipse projects using M2?
>>
>>
>> [INFO] Searching repository for plugin with prefix: 'eclipse'.
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] The plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does
>> not exist or no valid version could be found
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
>> 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or no
>> valid version could be f
>> ound
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281)
>>
>>
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517)
>>
>>
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:381)
>>
>>
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
>>
>>
>> at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>
>>
>> at java.lang.reflect.Method.invoke(Method.java:324)
>> at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> Caused by:
>> org.apache.maven.plugin.version.PluginVersionNotFoundException: The
>> plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or
>> no valid
>> version could be found
>> at
>> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:225)
>>
>>
>> at
>> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
>>
>>
>> at
>> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:158)
>>
>>
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
>>
>>
>> ... 14 more
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 8 seconds
>> [INFO] Finished at: Wed Aug 23 13:51:13 EDT 2006
>> [INFO] Final Memory: 19M/37M
>>
>>
>>
>> -----------------------------------------
>> This transmission may contain information that is privileged,
>> confidential, legally privileged, and/or exempt from disclosure
>> under applicable law. If you are not the intended recipient, you
>> are hereby notified that any disclosure, copying, distribution, or
>> use of the information contained herein (including any reliance
>> thereon) is STRICTLY PROHIBITED. Although this transmission and
>> any attachments are believed to be free of any virus or other
>> defect that might affect any computer system into which it is
>> received and opened, it is the responsibility of the recipient to
>> ensure that it is virus free and no responsibility is accepted by
>> JPMorgan Chase & Co., its subsidiaries and affiliates, as
>> applicable, for any loss or damage arising in any way from its use.
>> If you received this transmission in error, please immediately
>> contact the sender and destroy the material in its entirety,
>> whether in electronic or hard copy format. Thank you.
>>
>>
>>
Re: building eclipse projects with M2 build
Posted by Joe Bohn <jo...@earthlink.net>.
Thanks Ian. I did attempt to run it both on-line as well as off-line.
Either way I get the same result. Do you see something different?
Joe
ian.d.stewart@jpmchase.com wrote:
> The -o switch tells mvn not to attempt to download any plugins or
> dependencies, using only whatever is in your local repository. If this is
> your first time running the eclipse:eclipse goal then the necessary plugin
> won't be present.
>
> Try running 'mvn eclipse:eclipse' (i.e., no '-o' switch).
>
>
> HTH,
> Ian
>
> It's better to be hated for who you are
> than loved for who you're not
>
> Ian D. Stewart
> Distributed Computing Engineer II
> DSS eCommerce Engineering
> JPMorganChase Global Technology Infrastructure
> Phone: (614) 244-2564
>
>
>
> Joe Bohn
> <joe.bohn@earthli
> nk.net> To
> Geronimo Dev
> 08/23/2006 01:53 <de...@geronimo.apache.org>
> PM cc
>
> Subject
> Please respond to building eclipse projects with M2
> dev@geronimo.apac build
> he.org
>
>
>
>
>
>
>
>
>
> The cwiki inidicates that we can build projects for eclipse using the m2
> build with the following command:
>
> mvn -o eclipse:eclipse
>
> However, when I attempt to do this I get the error below. Has anybody
> been successful in building the eclipse projects using M2?
>
>
> [INFO] Searching repository for plugin with prefix: 'eclipse'.
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] The plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does
> not exist or no valid version could be found
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
> 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or no
> valid version could be f
> ound
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:381)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by:
> org.apache.maven.plugin.version.PluginVersionNotFoundException: The
> plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or
> no valid
> version could be found
> at
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:225)
>
> at
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
>
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:158)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
>
> ... 14 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 8 seconds
> [INFO] Finished at: Wed Aug 23 13:51:13 EDT 2006
> [INFO] Final Memory: 19M/37M
>
>
>
> -----------------------------------------
> This transmission may contain information that is privileged,
> confidential, legally privileged, and/or exempt from disclosure
> under applicable law. If you are not the intended recipient, you
> are hereby notified that any disclosure, copying, distribution, or
> use of the information contained herein (including any reliance
> thereon) is STRICTLY PROHIBITED. Although this transmission and
> any attachments are believed to be free of any virus or other
> defect that might affect any computer system into which it is
> received and opened, it is the responsibility of the recipient to
> ensure that it is virus free and no responsibility is accepted by
> JPMorgan Chase & Co., its subsidiaries and affiliates, as
> applicable, for any loss or damage arising in any way from its use.
> If you received this transmission in error, please immediately
> contact the sender and destroy the material in its entirety,
> whether in electronic or hard copy format. Thank you.
>
>
>
Re: building eclipse projects with M2 build
Posted by ia...@jpmchase.com.
The -o switch tells mvn not to attempt to download any plugins or
dependencies, using only whatever is in your local repository. If this is
your first time running the eclipse:eclipse goal then the necessary plugin
won't be present.
Try running 'mvn eclipse:eclipse' (i.e., no '-o' switch).
HTH,
Ian
It's better to be hated for who you are
than loved for who you're not
Ian D. Stewart
Distributed Computing Engineer II
DSS eCommerce Engineering
JPMorganChase Global Technology Infrastructure
Phone: (614) 244-2564
Joe Bohn
<joe.bohn@earthli
nk.net> To
Geronimo Dev
08/23/2006 01:53 <de...@geronimo.apache.org>
PM cc
Subject
Please respond to building eclipse projects with M2
dev@geronimo.apac build
he.org
The cwiki inidicates that we can build projects for eclipse using the m2
build with the following command:
mvn -o eclipse:eclipse
However, when I attempt to do this I get the error below. Has anybody
been successful in building the eclipse projects using M2?
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does
not exist or no valid version could be found
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or no
valid version could be f
ound
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:381)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by:
org.apache.maven.plugin.version.PluginVersionNotFoundException: The
plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or
no valid
version could be found
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:225)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:158)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
... 14 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 8 seconds
[INFO] Finished at: Wed Aug 23 13:51:13 EDT 2006
[INFO] Final Memory: 19M/37M
-----------------------------------------
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and
any attachments are believed to be free of any virus or other
defect that might affect any computer system into which it is
received and opened, it is the responsibility of the recipient to
ensure that it is virus free and no responsibility is accepted by
JPMorgan Chase & Co., its subsidiaries and affiliates, as
applicable, for any loss or damage arising in any way from its use.
If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.
Re: building eclipse projects with M2 build
Posted by Joe Bohn <jo...@earthlink.net>.
Thanks Anita. The issue was that the plugin maven eclipse plugin had
somehow been corrupted. Removing the plugins from the repo and then
doing an online build resolved the problem.
Now, I just have to figure out how to get eclipse setup for maven 2 with
the new structure (where we no longer have an expanded server under
assemblies when the build is finished). I assume somebody must have
already blazed this path. Would somebody be willing to post some
directions on cwiki for this? I'd be glad to verify them or document
what I learn (but I may just use IDEA instead since I just got a license
for that).
Joe
anita kulshreshtha wrote:
> Joe,
> I had used this command for creating the packaging-plugin project
> for eclipse 2 months ago. Have you tried using:
> mvn eclipse:eclipse
>
> Thanks
> Anita
>
> --- Joe Bohn <jo...@earthlink.net> wrote:
>
>
>>The cwiki inidicates that we can build projects for eclipse using the
>>m2
>>build with the following command:
>>
>>mvn -o eclipse:eclipse
>>
>>However, when I attempt to do this I get the error below. Has
>>anybody
>>been successful in building the eclipse projects using M2?
>>
>>
>>[INFO] Searching repository for plugin with prefix: 'eclipse'.
>>[INFO]
>>
>
> ------------------------------------------------------------------------
>
>>[ERROR] BUILD ERROR
>>[INFO]
>>
>
> ------------------------------------------------------------------------
>
>>[INFO] The plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
>>does
>>not exist or no valid version could be found
>>[INFO]
>>
>
> ------------------------------------------------------------------------
>
>>[INFO] Trace
>>org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
>>'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or no
>>valid version could be f
>>ound
>> at
>>
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281)
>
>> at
>>
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517)
>
>> at
>>
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:381)
>
>> at
>>
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
>
>> at
>>org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>> at
>>org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>Method)
>> at
>>
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
>> at
>>
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
>> at java.lang.reflect.Method.invoke(Method.java:324)
>> at
>>org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> at
>>org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> at
>>org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>Caused by:
>>org.apache.maven.plugin.version.PluginVersionNotFoundException: The
>>plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist
>>or
>>no valid
>> version could be found
>> at
>>
>
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:225)
>
>> at
>>
>
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
>
>> at
>>
>
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:158)
>
>> at
>>
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
>
>> ... 14 more
>>[INFO]
>>
>
> ------------------------------------------------------------------------
>
>>[INFO] Total time: 8 seconds
>>[INFO] Finished at: Wed Aug 23 13:51:13 EDT 2006
>>[INFO] Final Memory: 19M/37M
>>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
Re: building eclipse projects with M2 build
Posted by anita kulshreshtha <a_...@yahoo.com>.
Joe,
I had used this command for creating the packaging-plugin project
for eclipse 2 months ago. Have you tried using:
mvn eclipse:eclipse
Thanks
Anita
--- Joe Bohn <jo...@earthlink.net> wrote:
> The cwiki inidicates that we can build projects for eclipse using the
> m2
> build with the following command:
>
> mvn -o eclipse:eclipse
>
> However, when I attempt to do this I get the error below. Has
> anybody
> been successful in building the eclipse projects using M2?
>
>
> [INFO] Searching repository for plugin with prefix: 'eclipse'.
> [INFO]
>
------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
>
------------------------------------------------------------------------
> [INFO] The plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
> does
> not exist or no valid version could be found
> [INFO]
>
------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
> 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or no
> valid version could be f
> ound
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:381)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at
> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by:
> org.apache.maven.plugin.version.PluginVersionNotFoundException: The
> plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist
> or
> no valid
> version could be found
> at
>
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:225)
> at
>
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
> at
>
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:158)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
> ... 14 more
> [INFO]
>
------------------------------------------------------------------------
> [INFO] Total time: 8 seconds
> [INFO] Finished at: Wed Aug 23 13:51:13 EDT 2006
> [INFO] Final Memory: 19M/37M
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com