You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Hazem Saleh <ha...@apache.org> on 2008/07/01 09:16:08 UTC
An error during build
Hi Team,
Is there anyone that faces this issue during building Tomahawk ?
*java.lang.NoSuchMethodError:
org.codehaus.plexus.util.FileUtils.getDefaultExclud
es()[Ljava/lang/String;
at
org.codehaus.plexus.components.io.fileselectors.IncludeExcludeFileSel
ector.setExcludes(IncludeExcludeFileSelector.java:131)
at
org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.AbstractDe
pendencyMojo.unpack(AbstractDependencyMojo.java:251)
at
org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
.unpackArtifact(UnpackMojo.java:207)
at
org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
.execute(UnpackMojo.java:180)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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)
*
Thanks!
--
Hazem Ahmed Saleh Ahmed
http://www.jroller.com/page/HazemBlog
Re: An error during build
Posted by Hazem Saleh <ha...@apache.org>.
Thanks Matzew, I will try Maven 2.0.4.
On Tue, Jul 1, 2008 at 11:26 AM, Matthias Wessendorf <ma...@apache.org>
wrote:
> I noticed this error a while ago, when building Trinidad.
> This is one of the typical random build issues, which you can't foresee
> when using maven ,-)
>
> I guess you run with a very recent maven, right?
> I think using 2.0.4 this will not show up, but this switch
> causes other issues, since some plugins require 2.0.6 or greater
>
> Another option is to "patch" the FileUtils in question on your computer.
> Find the one that doesn't have this method, and replace the JAR by one
> that actually has the "right" signature. Yes... this is a very ugly
> workaround...
>
> -Matthias
>
> On Tue, Jul 1, 2008 at 9:16 AM, Hazem Saleh <ha...@apache.org> wrote:
> > Hi Team,
> >
> > Is there anyone that faces this issue during building Tomahawk ?
> >
> > java.lang.NoSuchMethodError:
> > org.codehaus.plexus.util.FileUtils.getDefaultExclud
> > es()[Ljava/lang/String;
> > at
> > org.codehaus.plexus.components.io.fileselectors.IncludeExcludeFileSel
> > ector.setExcludes(IncludeExcludeFileSelector.java:131)
> > at
> > org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.AbstractDe
> > pendencyMojo.unpack(AbstractDependencyMojo.java:251)
> > at
> > org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
> > .unpackArtifact(UnpackMojo.java:207)
> > at
> > org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
> > .execute(UnpackMojo.java:180)
> > at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> > nManager.java:443)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> > ultLifecycleExecutor.java:539)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> > fecycle(DefaultLifecycleExecutor.java:480)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> > ltLifecycleExecutor.java:459)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> > dleFailures(DefaultLifecycleExecutor.java:311)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> > ts(DefaultLifecycleExecutor.java:278)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> > fecycleExecutor.java:143)
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> > java:39)
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> > sorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > 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)
> >
> >
> > Thanks!
> > --
> > Hazem Ahmed Saleh Ahmed
> > http://www.jroller.com/page/HazemBlog
>
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> mail: matzew-at-apache-dot-org
>
--
Hazem Ahmed Saleh Ahmed
http://www.jroller.com/page/HazemBlog
Re: An error during build
Posted by Matthias Wessendorf <ma...@apache.org>.
ah, thanks
it is good that maven is not the source of issue here.
Well, this time ;-)
On Tue, Jul 1, 2008 at 12:32 PM, Hazem Saleh <ha...@apache.org> wrote:
> It runs successfully too after I upgraded my maven version.
> This means that the root cause of the problem was because of the core12 :).
>
> On Tue, Jul 1, 2008 at 1:21 PM, Hazem Saleh <ha...@apache.org> wrote:
>>
>> ok I will try and tell u the result.
>>
>> On Tue, Jul 1, 2008 at 1:19 PM, Matthias Wessendorf <ma...@apache.org>
>> wrote:
>>>
>>> On Tue, Jul 1, 2008 at 12:01 PM, Hazem Saleh <ha...@apache.org> wrote:
>>> > I downgraded maven to 2.0.4 and removed the core12 from the (pom.xml)
>>> > file.
>>>
>>> do you mind to try with your old version ?
>>>
>>> -M
>>>
>>> > It now works great!
>>> >
>>> > On Tue, Jul 1, 2008 at 12:56 PM, Matthias Wessendorf
>>> > <ma...@apache.org>
>>> > wrote:
>>> >>
>>> >> On Tue, Jul 1, 2008 at 11:55 AM, Hazem Saleh <ha...@apache.org>
>>> >> wrote:
>>> >> > Thank you Simon and Matzew for your great tips.
>>> >> > It works now fine with me.
>>> >>
>>> >> what happened ?
>>> >>
>>> >> -M
>>> >>
>>> >> >
>>> >> > On Tue, Jul 1, 2008 at 11:42 AM, simon.kitching@chello.at
>>> >> > <si...@chello.at> wrote:
>>> >> >>
>>> >> >> Hi Hazem,
>>> >> >>
>>> >> >> I've just rebuilt tomahawk and had no problem. Well, after I edited
>>> >> >> the
>>> >> >> pom.xml and sandbox/pom.xml to comment out the "core12" stuff which
>>> >> >> doesn't
>>> >> >> compile.
>>> >> >>
>>> >> >> Note that maven does not support multiple concurrent instances
>>> >> >> accessing
>>> >> >> the same local maven repository. So you cannot run mvn in two
>>> >> >> windows
>>> >> >> at the
>>> >> >> same time. If you were doing this when the error message was shown,
>>> >> >> try
>>> >> >> again with just one instance running.
>>> >> >>
>>> >> >> And maven does occasionally get a corrupted local repository
>>> >> >> (possibly
>>> >> >> due
>>> >> >> to accidentally running multiple concurrent instances, or using
>>> >> >> ctrl-c
>>> >> >> at
>>> >> >> the wrong moment). Try renaming ~/.m2/repository so it gets a fresh
>>> >> >> copy.
>>> >> >>
>>> >> >> If that doesn't work, then I'm out of ideas. As I said, it works
>>> >> >> for me
>>> >> >> (mvn 2.0.9 on linux).
>>> >> >>
>>> >> >> Cheers, Simon
>>> >> >>
>>> >> >> Matthias Wessendorf schrieb:
>>> >> >>>
>>> >> >>> I noticed this error a while ago, when building Trinidad.
>>> >> >>> This is one of the typical random build issues, which you can't
>>> >> >>> foresee
>>> >> >>> when using maven ,-)
>>> >> >>>
>>> >> >>> I guess you run with a very recent maven, right?
>>> >> >>> I think using 2.0.4 this will not show up, but this switch
>>> >> >>> causes other issues, since some plugins require 2.0.6 or greater
>>> >> >>>
>>> >> >>> Another option is to "patch" the FileUtils in question on your
>>> >> >>> computer.
>>> >> >>> Find the one that doesn't have this method, and replace the JAR by
>>> >> >>> one
>>> >> >>> that actually has the "right" signature. Yes... this is a very
>>> >> >>> ugly
>>> >> >>> workaround...
>>> >> >>>
>>> >> >>> -Matthias
>>> >> >>>
>>> >> >>> On Tue, Jul 1, 2008 at 9:16 AM, Hazem Saleh <ha...@apache.org>
>>> >> >>> wrote:
>>> >> >>>
>>> >> >>>>
>>> >> >>>> Hi Team,
>>> >> >>>>
>>> >> >>>> Is there anyone that faces this issue during building Tomahawk ?
>>> >> >>>>
>>> >> >>>> java.lang.NoSuchMethodError:
>>> >> >>>> org.codehaus.plexus.util.FileUtils.getDefaultExclud
>>> >> >>>> es()[Ljava/lang/String;
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>> org.codehaus.plexus.components.io.fileselectors.IncludeExcludeFileSel
>>> >> >>>> ector.setExcludes(IncludeExcludeFileSelector.java:131)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.AbstractDe
>>> >> >>>> pendencyMojo.unpack(AbstractDependencyMojo.java:251)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
>>> >> >>>> .unpackArtifact(UnpackMojo.java:207)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
>>> >> >>>> .execute(UnpackMojo.java:180)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>>> >> >>>> nManager.java:443)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>> >> >>>> ultLifecycleExecutor.java:539)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>>> >> >>>> fecycle(DefaultLifecycleExecutor.java:480)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>>> >> >>>> ltLifecycleExecutor.java:459)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>>> >> >>>> dleFailures(DefaultLifecycleExecutor.java:311)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>>> >> >>>> ts(DefaultLifecycleExecutor.java:278)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>>> >> >>>> fecycleExecutor.java:143)
>>> >> >>>> at
>>> >> >>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>>> >> >>>> at
>>> >> >>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>>> >> >>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>>> >> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> >> >>>> Method)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>>> >> >>>> java:39)
>>> >> >>>> at
>>> >> >>>>
>>> >> >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>>> >> >>>> sorImpl.java:25)
>>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>> >> >>>> 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)
>>> >> >>>>
>>> >> >>>>
>>> >> >>>> Thanks!
>>> >> >>>> --
>>> >> >>>> Hazem Ahmed Saleh Ahmed
>>> >> >>>> http://www.jroller.com/page/HazemBlog
>>> >> >>>>
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Hazem Ahmed Saleh Ahmed
>>> >> > http://www.jroller.com/page/HazemBlog
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Matthias Wessendorf
>>> >>
>>> >> further stuff:
>>> >> blog: http://matthiaswessendorf.wordpress.com/
>>> >> sessions: http://www.slideshare.net/mwessendorf
>>> >> mail: matzew-at-apache-dot-org
>>> >
>>> >
>>> >
>>> > --
>>> > Hazem Ahmed Saleh Ahmed
>>> > http://www.jroller.com/page/HazemBlog
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> further stuff:
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> mail: matzew-at-apache-dot-org
>>
>>
>>
>> --
>> Hazem Ahmed Saleh Ahmed
>> http://www.jroller.com/page/HazemBlog
>
>
> --
> Hazem Ahmed Saleh Ahmed
> http://www.jroller.com/page/HazemBlog
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
Re: An error during build
Posted by Hazem Saleh <ha...@apache.org>.
It runs successfully too after I upgraded my maven version.
This means that the root cause of the problem was because of the core12 :).
On Tue, Jul 1, 2008 at 1:21 PM, Hazem Saleh <ha...@apache.org> wrote:
> ok I will try and tell u the result.
>
>
> On Tue, Jul 1, 2008 at 1:19 PM, Matthias Wessendorf <ma...@apache.org>
> wrote:
>
>> On Tue, Jul 1, 2008 at 12:01 PM, Hazem Saleh <ha...@apache.org> wrote:
>> > I downgraded maven to 2.0.4 and removed the core12 from the (pom.xml)
>> file.
>>
>> do you mind to try with your old version ?
>>
>> -M
>>
>> > It now works great!
>> >
>> > On Tue, Jul 1, 2008 at 12:56 PM, Matthias Wessendorf <matzew@apache.org
>> >
>> > wrote:
>> >>
>> >> On Tue, Jul 1, 2008 at 11:55 AM, Hazem Saleh <ha...@apache.org>
>> wrote:
>> >> > Thank you Simon and Matzew for your great tips.
>> >> > It works now fine with me.
>> >>
>> >> what happened ?
>> >>
>> >> -M
>> >>
>> >> >
>> >> > On Tue, Jul 1, 2008 at 11:42 AM, simon.kitching@chello.at
>> >> > <si...@chello.at> wrote:
>> >> >>
>> >> >> Hi Hazem,
>> >> >>
>> >> >> I've just rebuilt tomahawk and had no problem. Well, after I edited
>> the
>> >> >> pom.xml and sandbox/pom.xml to comment out the "core12" stuff which
>> >> >> doesn't
>> >> >> compile.
>> >> >>
>> >> >> Note that maven does not support multiple concurrent instances
>> >> >> accessing
>> >> >> the same local maven repository. So you cannot run mvn in two
>> windows
>> >> >> at the
>> >> >> same time. If you were doing this when the error message was shown,
>> try
>> >> >> again with just one instance running.
>> >> >>
>> >> >> And maven does occasionally get a corrupted local repository
>> (possibly
>> >> >> due
>> >> >> to accidentally running multiple concurrent instances, or using
>> ctrl-c
>> >> >> at
>> >> >> the wrong moment). Try renaming ~/.m2/repository so it gets a fresh
>> >> >> copy.
>> >> >>
>> >> >> If that doesn't work, then I'm out of ideas. As I said, it works for
>> me
>> >> >> (mvn 2.0.9 on linux).
>> >> >>
>> >> >> Cheers, Simon
>> >> >>
>> >> >> Matthias Wessendorf schrieb:
>> >> >>>
>> >> >>> I noticed this error a while ago, when building Trinidad.
>> >> >>> This is one of the typical random build issues, which you can't
>> >> >>> foresee
>> >> >>> when using maven ,-)
>> >> >>>
>> >> >>> I guess you run with a very recent maven, right?
>> >> >>> I think using 2.0.4 this will not show up, but this switch
>> >> >>> causes other issues, since some plugins require 2.0.6 or greater
>> >> >>>
>> >> >>> Another option is to "patch" the FileUtils in question on your
>> >> >>> computer.
>> >> >>> Find the one that doesn't have this method, and replace the JAR by
>> one
>> >> >>> that actually has the "right" signature. Yes... this is a very ugly
>> >> >>> workaround...
>> >> >>>
>> >> >>> -Matthias
>> >> >>>
>> >> >>> On Tue, Jul 1, 2008 at 9:16 AM, Hazem Saleh <ha...@apache.org>
>> wrote:
>> >> >>>
>> >> >>>>
>> >> >>>> Hi Team,
>> >> >>>>
>> >> >>>> Is there anyone that faces this issue during building Tomahawk ?
>> >> >>>>
>> >> >>>> java.lang.NoSuchMethodError:
>> >> >>>> org.codehaus.plexus.util.FileUtils.getDefaultExclud
>> >> >>>> es()[Ljava/lang/String;
>> >> >>>> at
>> >> >>>>
>> org.codehaus.plexus.components.io.fileselectors.IncludeExcludeFileSel
>> >> >>>> ector.setExcludes(IncludeExcludeFileSelector.java:131)
>> >> >>>> at
>> >> >>>>
>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.AbstractDe
>> >> >>>> pendencyMojo.unpack(AbstractDependencyMojo.java:251)
>> >> >>>> at
>> >> >>>>
>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
>> >> >>>> .unpackArtifact(UnpackMojo.java:207)
>> >> >>>> at
>> >> >>>>
>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
>> >> >>>> .execute(UnpackMojo.java:180)
>> >> >>>> at
>> >> >>>>
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>> >> >>>> nManager.java:443)
>> >> >>>> at
>> >> >>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >> >>>> ultLifecycleExecutor.java:539)
>> >> >>>> at
>> >> >>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> >> >>>> fecycle(DefaultLifecycleExecutor.java:480)
>> >> >>>> at
>> >> >>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> >> >>>> ltLifecycleExecutor.java:459)
>> >> >>>> at
>> >> >>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> >> >>>> dleFailures(DefaultLifecycleExecutor.java:311)
>> >> >>>> at
>> >> >>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> >> >>>> ts(DefaultLifecycleExecutor.java:278)
>> >> >>>> at
>> >> >>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> >> >>>> fecycleExecutor.java:143)
>> >> >>>> at
>> >> >>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>> >> >>>> at
>> >> >>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>> >> >>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>> >> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> >> >>>> at
>> >> >>>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >> >>>> java:39)
>> >> >>>> at
>> >> >>>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> >> >>>> sorImpl.java:25)
>> >> >>>> at java.lang.reflect.Method.invoke(Method.java:585)
>> >> >>>> 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)
>> >> >>>>
>> >> >>>>
>> >> >>>> Thanks!
>> >> >>>> --
>> >> >>>> Hazem Ahmed Saleh Ahmed
>> >> >>>> http://www.jroller.com/page/HazemBlog
>> >> >>>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Hazem Ahmed Saleh Ahmed
>> >> > http://www.jroller.com/page/HazemBlog
>> >>
>> >>
>> >>
>> >> --
>> >> Matthias Wessendorf
>> >>
>> >> further stuff:
>> >> blog: http://matthiaswessendorf.wordpress.com/
>> >> sessions: http://www.slideshare.net/mwessendorf
>> >> mail: matzew-at-apache-dot-org
>> >
>> >
>> >
>> > --
>> > Hazem Ahmed Saleh Ahmed
>> > http://www.jroller.com/page/HazemBlog
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> further stuff:
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> mail: matzew-at-apache-dot-org
>>
>
>
>
> --
> Hazem Ahmed Saleh Ahmed
> http://www.jroller.com/page/HazemBlog
>
--
Hazem Ahmed Saleh Ahmed
http://www.jroller.com/page/HazemBlog
Re: An error during build
Posted by Hazem Saleh <ha...@apache.org>.
ok I will try and tell u the result.
On Tue, Jul 1, 2008 at 1:19 PM, Matthias Wessendorf <ma...@apache.org>
wrote:
> On Tue, Jul 1, 2008 at 12:01 PM, Hazem Saleh <ha...@apache.org> wrote:
> > I downgraded maven to 2.0.4 and removed the core12 from the (pom.xml)
> file.
>
> do you mind to try with your old version ?
>
> -M
>
> > It now works great!
> >
> > On Tue, Jul 1, 2008 at 12:56 PM, Matthias Wessendorf <ma...@apache.org>
> > wrote:
> >>
> >> On Tue, Jul 1, 2008 at 11:55 AM, Hazem Saleh <ha...@apache.org> wrote:
> >> > Thank you Simon and Matzew for your great tips.
> >> > It works now fine with me.
> >>
> >> what happened ?
> >>
> >> -M
> >>
> >> >
> >> > On Tue, Jul 1, 2008 at 11:42 AM, simon.kitching@chello.at
> >> > <si...@chello.at> wrote:
> >> >>
> >> >> Hi Hazem,
> >> >>
> >> >> I've just rebuilt tomahawk and had no problem. Well, after I edited
> the
> >> >> pom.xml and sandbox/pom.xml to comment out the "core12" stuff which
> >> >> doesn't
> >> >> compile.
> >> >>
> >> >> Note that maven does not support multiple concurrent instances
> >> >> accessing
> >> >> the same local maven repository. So you cannot run mvn in two windows
> >> >> at the
> >> >> same time. If you were doing this when the error message was shown,
> try
> >> >> again with just one instance running.
> >> >>
> >> >> And maven does occasionally get a corrupted local repository
> (possibly
> >> >> due
> >> >> to accidentally running multiple concurrent instances, or using
> ctrl-c
> >> >> at
> >> >> the wrong moment). Try renaming ~/.m2/repository so it gets a fresh
> >> >> copy.
> >> >>
> >> >> If that doesn't work, then I'm out of ideas. As I said, it works for
> me
> >> >> (mvn 2.0.9 on linux).
> >> >>
> >> >> Cheers, Simon
> >> >>
> >> >> Matthias Wessendorf schrieb:
> >> >>>
> >> >>> I noticed this error a while ago, when building Trinidad.
> >> >>> This is one of the typical random build issues, which you can't
> >> >>> foresee
> >> >>> when using maven ,-)
> >> >>>
> >> >>> I guess you run with a very recent maven, right?
> >> >>> I think using 2.0.4 this will not show up, but this switch
> >> >>> causes other issues, since some plugins require 2.0.6 or greater
> >> >>>
> >> >>> Another option is to "patch" the FileUtils in question on your
> >> >>> computer.
> >> >>> Find the one that doesn't have this method, and replace the JAR by
> one
> >> >>> that actually has the "right" signature. Yes... this is a very ugly
> >> >>> workaround...
> >> >>>
> >> >>> -Matthias
> >> >>>
> >> >>> On Tue, Jul 1, 2008 at 9:16 AM, Hazem Saleh <ha...@apache.org>
> wrote:
> >> >>>
> >> >>>>
> >> >>>> Hi Team,
> >> >>>>
> >> >>>> Is there anyone that faces this issue during building Tomahawk ?
> >> >>>>
> >> >>>> java.lang.NoSuchMethodError:
> >> >>>> org.codehaus.plexus.util.FileUtils.getDefaultExclud
> >> >>>> es()[Ljava/lang/String;
> >> >>>> at
> >> >>>>
> org.codehaus.plexus.components.io.fileselectors.IncludeExcludeFileSel
> >> >>>> ector.setExcludes(IncludeExcludeFileSelector.java:131)
> >> >>>> at
> >> >>>>
> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.AbstractDe
> >> >>>> pendencyMojo.unpack(AbstractDependencyMojo.java:251)
> >> >>>> at
> >> >>>>
> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
> >> >>>> .unpackArtifact(UnpackMojo.java:207)
> >> >>>> at
> >> >>>>
> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
> >> >>>> .execute(UnpackMojo.java:180)
> >> >>>> at
> >> >>>>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> >> >>>> nManager.java:443)
> >> >>>> at
> >> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> >>>> ultLifecycleExecutor.java:539)
> >> >>>> at
> >> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> >> >>>> fecycle(DefaultLifecycleExecutor.java:480)
> >> >>>> at
> >> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> >> >>>> ltLifecycleExecutor.java:459)
> >> >>>> at
> >> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> >> >>>> dleFailures(DefaultLifecycleExecutor.java:311)
> >> >>>> at
> >> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> >> >>>> ts(DefaultLifecycleExecutor.java:278)
> >> >>>> at
> >> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> >> >>>> fecycleExecutor.java:143)
> >> >>>> at
> >> >>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> >> >>>> at
> >> >>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> >> >>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> >> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> >> >>>> at
> >> >>>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >> >>>> java:39)
> >> >>>> at
> >> >>>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >> >>>> sorImpl.java:25)
> >> >>>> at java.lang.reflect.Method.invoke(Method.java:585)
> >> >>>> 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)
> >> >>>>
> >> >>>>
> >> >>>> Thanks!
> >> >>>> --
> >> >>>> Hazem Ahmed Saleh Ahmed
> >> >>>> http://www.jroller.com/page/HazemBlog
> >> >>>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Hazem Ahmed Saleh Ahmed
> >> > http://www.jroller.com/page/HazemBlog
> >>
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> further stuff:
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> sessions: http://www.slideshare.net/mwessendorf
> >> mail: matzew-at-apache-dot-org
> >
> >
> >
> > --
> > Hazem Ahmed Saleh Ahmed
> > http://www.jroller.com/page/HazemBlog
>
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> mail: matzew-at-apache-dot-org
>
--
Hazem Ahmed Saleh Ahmed
http://www.jroller.com/page/HazemBlog
Re: An error during build
Posted by Matthias Wessendorf <ma...@apache.org>.
On Tue, Jul 1, 2008 at 12:01 PM, Hazem Saleh <ha...@apache.org> wrote:
> I downgraded maven to 2.0.4 and removed the core12 from the (pom.xml) file.
do you mind to try with your old version ?
-M
> It now works great!
>
> On Tue, Jul 1, 2008 at 12:56 PM, Matthias Wessendorf <ma...@apache.org>
> wrote:
>>
>> On Tue, Jul 1, 2008 at 11:55 AM, Hazem Saleh <ha...@apache.org> wrote:
>> > Thank you Simon and Matzew for your great tips.
>> > It works now fine with me.
>>
>> what happened ?
>>
>> -M
>>
>> >
>> > On Tue, Jul 1, 2008 at 11:42 AM, simon.kitching@chello.at
>> > <si...@chello.at> wrote:
>> >>
>> >> Hi Hazem,
>> >>
>> >> I've just rebuilt tomahawk and had no problem. Well, after I edited the
>> >> pom.xml and sandbox/pom.xml to comment out the "core12" stuff which
>> >> doesn't
>> >> compile.
>> >>
>> >> Note that maven does not support multiple concurrent instances
>> >> accessing
>> >> the same local maven repository. So you cannot run mvn in two windows
>> >> at the
>> >> same time. If you were doing this when the error message was shown, try
>> >> again with just one instance running.
>> >>
>> >> And maven does occasionally get a corrupted local repository (possibly
>> >> due
>> >> to accidentally running multiple concurrent instances, or using ctrl-c
>> >> at
>> >> the wrong moment). Try renaming ~/.m2/repository so it gets a fresh
>> >> copy.
>> >>
>> >> If that doesn't work, then I'm out of ideas. As I said, it works for me
>> >> (mvn 2.0.9 on linux).
>> >>
>> >> Cheers, Simon
>> >>
>> >> Matthias Wessendorf schrieb:
>> >>>
>> >>> I noticed this error a while ago, when building Trinidad.
>> >>> This is one of the typical random build issues, which you can't
>> >>> foresee
>> >>> when using maven ,-)
>> >>>
>> >>> I guess you run with a very recent maven, right?
>> >>> I think using 2.0.4 this will not show up, but this switch
>> >>> causes other issues, since some plugins require 2.0.6 or greater
>> >>>
>> >>> Another option is to "patch" the FileUtils in question on your
>> >>> computer.
>> >>> Find the one that doesn't have this method, and replace the JAR by one
>> >>> that actually has the "right" signature. Yes... this is a very ugly
>> >>> workaround...
>> >>>
>> >>> -Matthias
>> >>>
>> >>> On Tue, Jul 1, 2008 at 9:16 AM, Hazem Saleh <ha...@apache.org> wrote:
>> >>>
>> >>>>
>> >>>> Hi Team,
>> >>>>
>> >>>> Is there anyone that faces this issue during building Tomahawk ?
>> >>>>
>> >>>> java.lang.NoSuchMethodError:
>> >>>> org.codehaus.plexus.util.FileUtils.getDefaultExclud
>> >>>> es()[Ljava/lang/String;
>> >>>> at
>> >>>> org.codehaus.plexus.components.io.fileselectors.IncludeExcludeFileSel
>> >>>> ector.setExcludes(IncludeExcludeFileSelector.java:131)
>> >>>> at
>> >>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.AbstractDe
>> >>>> pendencyMojo.unpack(AbstractDependencyMojo.java:251)
>> >>>> at
>> >>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
>> >>>> .unpackArtifact(UnpackMojo.java:207)
>> >>>> at
>> >>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
>> >>>> .execute(UnpackMojo.java:180)
>> >>>> at
>> >>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>> >>>> nManager.java:443)
>> >>>> at
>> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> >>>> ultLifecycleExecutor.java:539)
>> >>>> at
>> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> >>>> fecycle(DefaultLifecycleExecutor.java:480)
>> >>>> at
>> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> >>>> ltLifecycleExecutor.java:459)
>> >>>> at
>> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> >>>> dleFailures(DefaultLifecycleExecutor.java:311)
>> >>>> at
>> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> >>>> ts(DefaultLifecycleExecutor.java:278)
>> >>>> at
>> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> >>>> fecycleExecutor.java:143)
>> >>>> at
>> >>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>> >>>> at
>> >>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>> >>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >>>> at
>> >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >>>> java:39)
>> >>>> at
>> >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> >>>> sorImpl.java:25)
>> >>>> at java.lang.reflect.Method.invoke(Method.java:585)
>> >>>> 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)
>> >>>>
>> >>>>
>> >>>> Thanks!
>> >>>> --
>> >>>> Hazem Ahmed Saleh Ahmed
>> >>>> http://www.jroller.com/page/HazemBlog
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>
>> >
>> >
>> >
>> > --
>> > Hazem Ahmed Saleh Ahmed
>> > http://www.jroller.com/page/HazemBlog
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> further stuff:
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> mail: matzew-at-apache-dot-org
>
>
>
> --
> Hazem Ahmed Saleh Ahmed
> http://www.jroller.com/page/HazemBlog
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
Re: An error during build
Posted by Hazem Saleh <ha...@apache.org>.
I downgraded maven to 2.0.4 and removed the core12 from the (pom.xml) file.
It now works great!
On Tue, Jul 1, 2008 at 12:56 PM, Matthias Wessendorf <ma...@apache.org>
wrote:
> On Tue, Jul 1, 2008 at 11:55 AM, Hazem Saleh <ha...@apache.org> wrote:
> > Thank you Simon and Matzew for your great tips.
> > It works now fine with me.
>
> what happened ?
>
> -M
>
> >
> > On Tue, Jul 1, 2008 at 11:42 AM, simon.kitching@chello.at
> > <si...@chello.at> wrote:
> >>
> >> Hi Hazem,
> >>
> >> I've just rebuilt tomahawk and had no problem. Well, after I edited the
> >> pom.xml and sandbox/pom.xml to comment out the "core12" stuff which
> doesn't
> >> compile.
> >>
> >> Note that maven does not support multiple concurrent instances accessing
> >> the same local maven repository. So you cannot run mvn in two windows at
> the
> >> same time. If you were doing this when the error message was shown, try
> >> again with just one instance running.
> >>
> >> And maven does occasionally get a corrupted local repository (possibly
> due
> >> to accidentally running multiple concurrent instances, or using ctrl-c
> at
> >> the wrong moment). Try renaming ~/.m2/repository so it gets a fresh
> copy.
> >>
> >> If that doesn't work, then I'm out of ideas. As I said, it works for me
> >> (mvn 2.0.9 on linux).
> >>
> >> Cheers, Simon
> >>
> >> Matthias Wessendorf schrieb:
> >>>
> >>> I noticed this error a while ago, when building Trinidad.
> >>> This is one of the typical random build issues, which you can't foresee
> >>> when using maven ,-)
> >>>
> >>> I guess you run with a very recent maven, right?
> >>> I think using 2.0.4 this will not show up, but this switch
> >>> causes other issues, since some plugins require 2.0.6 or greater
> >>>
> >>> Another option is to "patch" the FileUtils in question on your
> computer.
> >>> Find the one that doesn't have this method, and replace the JAR by one
> >>> that actually has the "right" signature. Yes... this is a very ugly
> >>> workaround...
> >>>
> >>> -Matthias
> >>>
> >>> On Tue, Jul 1, 2008 at 9:16 AM, Hazem Saleh <ha...@apache.org> wrote:
> >>>
> >>>>
> >>>> Hi Team,
> >>>>
> >>>> Is there anyone that faces this issue during building Tomahawk ?
> >>>>
> >>>> java.lang.NoSuchMethodError:
> >>>> org.codehaus.plexus.util.FileUtils.getDefaultExclud
> >>>> es()[Ljava/lang/String;
> >>>> at
> >>>> org.codehaus.plexus.components.io.fileselectors.IncludeExcludeFileSel
> >>>> ector.setExcludes(IncludeExcludeFileSelector.java:131)
> >>>> at
> >>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.AbstractDe
> >>>> pendencyMojo.unpack(AbstractDependencyMojo.java:251)
> >>>> at
> >>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
> >>>> .unpackArtifact(UnpackMojo.java:207)
> >>>> at
> >>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
> >>>> .execute(UnpackMojo.java:180)
> >>>> at
> >>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> >>>> nManager.java:443)
> >>>> at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >>>> ultLifecycleExecutor.java:539)
> >>>> at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> >>>> fecycle(DefaultLifecycleExecutor.java:480)
> >>>> at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> >>>> ltLifecycleExecutor.java:459)
> >>>> at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> >>>> dleFailures(DefaultLifecycleExecutor.java:311)
> >>>> at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> >>>> ts(DefaultLifecycleExecutor.java:278)
> >>>> at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> >>>> fecycleExecutor.java:143)
> >>>> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> >>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> >>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>>> at
> >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >>>> java:39)
> >>>> at
> >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >>>> sorImpl.java:25)
> >>>> at java.lang.reflect.Method.invoke(Method.java:585)
> >>>> 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)
> >>>>
> >>>>
> >>>> Thanks!
> >>>> --
> >>>> Hazem Ahmed Saleh Ahmed
> >>>> http://www.jroller.com/page/HazemBlog
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>
> >
> >
> >
> > --
> > Hazem Ahmed Saleh Ahmed
> > http://www.jroller.com/page/HazemBlog
>
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> mail: matzew-at-apache-dot-org
>
--
Hazem Ahmed Saleh Ahmed
http://www.jroller.com/page/HazemBlog
Re: An error during build
Posted by Matthias Wessendorf <ma...@apache.org>.
On Tue, Jul 1, 2008 at 11:55 AM, Hazem Saleh <ha...@apache.org> wrote:
> Thank you Simon and Matzew for your great tips.
> It works now fine with me.
what happened ?
-M
>
> On Tue, Jul 1, 2008 at 11:42 AM, simon.kitching@chello.at
> <si...@chello.at> wrote:
>>
>> Hi Hazem,
>>
>> I've just rebuilt tomahawk and had no problem. Well, after I edited the
>> pom.xml and sandbox/pom.xml to comment out the "core12" stuff which doesn't
>> compile.
>>
>> Note that maven does not support multiple concurrent instances accessing
>> the same local maven repository. So you cannot run mvn in two windows at the
>> same time. If you were doing this when the error message was shown, try
>> again with just one instance running.
>>
>> And maven does occasionally get a corrupted local repository (possibly due
>> to accidentally running multiple concurrent instances, or using ctrl-c at
>> the wrong moment). Try renaming ~/.m2/repository so it gets a fresh copy.
>>
>> If that doesn't work, then I'm out of ideas. As I said, it works for me
>> (mvn 2.0.9 on linux).
>>
>> Cheers, Simon
>>
>> Matthias Wessendorf schrieb:
>>>
>>> I noticed this error a while ago, when building Trinidad.
>>> This is one of the typical random build issues, which you can't foresee
>>> when using maven ,-)
>>>
>>> I guess you run with a very recent maven, right?
>>> I think using 2.0.4 this will not show up, but this switch
>>> causes other issues, since some plugins require 2.0.6 or greater
>>>
>>> Another option is to "patch" the FileUtils in question on your computer.
>>> Find the one that doesn't have this method, and replace the JAR by one
>>> that actually has the "right" signature. Yes... this is a very ugly
>>> workaround...
>>>
>>> -Matthias
>>>
>>> On Tue, Jul 1, 2008 at 9:16 AM, Hazem Saleh <ha...@apache.org> wrote:
>>>
>>>>
>>>> Hi Team,
>>>>
>>>> Is there anyone that faces this issue during building Tomahawk ?
>>>>
>>>> java.lang.NoSuchMethodError:
>>>> org.codehaus.plexus.util.FileUtils.getDefaultExclud
>>>> es()[Ljava/lang/String;
>>>> at
>>>> org.codehaus.plexus.components.io.fileselectors.IncludeExcludeFileSel
>>>> ector.setExcludes(IncludeExcludeFileSelector.java:131)
>>>> at
>>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.AbstractDe
>>>> pendencyMojo.unpack(AbstractDependencyMojo.java:251)
>>>> at
>>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
>>>> .unpackArtifact(UnpackMojo.java:207)
>>>> at
>>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
>>>> .execute(UnpackMojo.java:180)
>>>> at
>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>>>> nManager.java:443)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>>> ultLifecycleExecutor.java:539)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>>>> fecycle(DefaultLifecycleExecutor.java:480)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>>>> ltLifecycleExecutor.java:459)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>>>> dleFailures(DefaultLifecycleExecutor.java:311)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>>>> ts(DefaultLifecycleExecutor.java:278)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>>>> fecycleExecutor.java:143)
>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>>>> java:39)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>>>> sorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>>> 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)
>>>>
>>>>
>>>> Thanks!
>>>> --
>>>> Hazem Ahmed Saleh Ahmed
>>>> http://www.jroller.com/page/HazemBlog
>>>>
>>>
>>>
>>>
>>>
>>
>
>
>
> --
> Hazem Ahmed Saleh Ahmed
> http://www.jroller.com/page/HazemBlog
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
Re: An error during build
Posted by Hazem Saleh <ha...@apache.org>.
Thank you Simon and Matzew for your great tips.
It works now fine with me.
On Tue, Jul 1, 2008 at 11:42 AM, simon.kitching@chello.at <
simon.kitching@chello.at> wrote:
> Hi Hazem,
>
> I've just rebuilt tomahawk and had no problem. Well, after I edited the
> pom.xml and sandbox/pom.xml to comment out the "core12" stuff which doesn't
> compile.
>
> Note that maven does not support multiple concurrent instances accessing
> the same local maven repository. So you cannot run mvn in two windows at the
> same time. If you were doing this when the error message was shown, try
> again with just one instance running.
>
> And maven does occasionally get a corrupted local repository (possibly due
> to accidentally running multiple concurrent instances, or using ctrl-c at
> the wrong moment). Try renaming ~/.m2/repository so it gets a fresh copy.
>
> If that doesn't work, then I'm out of ideas. As I said, it works for me
> (mvn 2.0.9 on linux).
>
> Cheers, Simon
>
> Matthias Wessendorf schrieb:
>
> I noticed this error a while ago, when building Trinidad.
>> This is one of the typical random build issues, which you can't foresee
>> when using maven ,-)
>>
>> I guess you run with a very recent maven, right?
>> I think using 2.0.4 this will not show up, but this switch
>> causes other issues, since some plugins require 2.0.6 or greater
>>
>> Another option is to "patch" the FileUtils in question on your computer.
>> Find the one that doesn't have this method, and replace the JAR by one
>> that actually has the "right" signature. Yes... this is a very ugly
>> workaround...
>>
>> -Matthias
>>
>> On Tue, Jul 1, 2008 at 9:16 AM, Hazem Saleh <ha...@apache.org> wrote:
>>
>>
>>> Hi Team,
>>>
>>> Is there anyone that faces this issue during building Tomahawk ?
>>>
>>> java.lang.NoSuchMethodError:
>>> org.codehaus.plexus.util.FileUtils.getDefaultExclud
>>> es()[Ljava/lang/String;
>>> at
>>> org.codehaus.plexus.components.io.fileselectors.IncludeExcludeFileSel
>>> ector.setExcludes(IncludeExcludeFileSelector.java:131)
>>> at
>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.AbstractDe
>>> pendencyMojo.unpack(AbstractDependencyMojo.java:251)
>>> at
>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
>>> .unpackArtifact(UnpackMojo.java:207)
>>> at
>>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
>>> .execute(UnpackMojo.java:180)
>>> at
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>>> nManager.java:443)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>> ultLifecycleExecutor.java:539)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>>> fecycle(DefaultLifecycleExecutor.java:480)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>>> ltLifecycleExecutor.java:459)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>>> dleFailures(DefaultLifecycleExecutor.java:311)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>>> ts(DefaultLifecycleExecutor.java:278)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>>> fecycleExecutor.java:143)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>>> java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>>> sorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>> 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)
>>>
>>>
>>> Thanks!
>>> --
>>> Hazem Ahmed Saleh Ahmed
>>> http://www.jroller.com/page/HazemBlog
>>>
>>>
>>
>>
>>
>>
>>
>
>
--
Hazem Ahmed Saleh Ahmed
http://www.jroller.com/page/HazemBlog
Re: An error during build
Posted by "simon.kitching@chello.at" <si...@chello.at>.
Hi Hazem,
I've just rebuilt tomahawk and had no problem. Well, after I edited the
pom.xml and sandbox/pom.xml to comment out the "core12" stuff which
doesn't compile.
Note that maven does not support multiple concurrent instances accessing
the same local maven repository. So you cannot run mvn in two windows at
the same time. If you were doing this when the error message was shown,
try again with just one instance running.
And maven does occasionally get a corrupted local repository (possibly
due to accidentally running multiple concurrent instances, or using
ctrl-c at the wrong moment). Try renaming ~/.m2/repository so it gets a
fresh copy.
If that doesn't work, then I'm out of ideas. As I said, it works for me
(mvn 2.0.9 on linux).
Cheers, Simon
Matthias Wessendorf schrieb:
> I noticed this error a while ago, when building Trinidad.
> This is one of the typical random build issues, which you can't foresee
> when using maven ,-)
>
> I guess you run with a very recent maven, right?
> I think using 2.0.4 this will not show up, but this switch
> causes other issues, since some plugins require 2.0.6 or greater
>
> Another option is to "patch" the FileUtils in question on your computer.
> Find the one that doesn't have this method, and replace the JAR by one
> that actually has the "right" signature. Yes... this is a very ugly
> workaround...
>
> -Matthias
>
> On Tue, Jul 1, 2008 at 9:16 AM, Hazem Saleh <ha...@apache.org> wrote:
>
>> Hi Team,
>>
>> Is there anyone that faces this issue during building Tomahawk ?
>>
>> java.lang.NoSuchMethodError:
>> org.codehaus.plexus.util.FileUtils.getDefaultExclud
>> es()[Ljava/lang/String;
>> at
>> org.codehaus.plexus.components.io.fileselectors.IncludeExcludeFileSel
>> ector.setExcludes(IncludeExcludeFileSelector.java:131)
>> at
>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.AbstractDe
>> pendencyMojo.unpack(AbstractDependencyMojo.java:251)
>> at
>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
>> .unpackArtifact(UnpackMojo.java:207)
>> at
>> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
>> .execute(UnpackMojo.java:180)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>> nManager.java:443)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> ultLifecycleExecutor.java:539)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> fecycle(DefaultLifecycleExecutor.java:480)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> ltLifecycleExecutor.java:459)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> dleFailures(DefaultLifecycleExecutor.java:311)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> ts(DefaultLifecycleExecutor.java:278)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> fecycleExecutor.java:143)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> sorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> 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)
>>
>>
>> Thanks!
>> --
>> Hazem Ahmed Saleh Ahmed
>> http://www.jroller.com/page/HazemBlog
>>
>
>
>
>
Re: An error during build
Posted by Matthias Wessendorf <ma...@apache.org>.
I noticed this error a while ago, when building Trinidad.
This is one of the typical random build issues, which you can't foresee
when using maven ,-)
I guess you run with a very recent maven, right?
I think using 2.0.4 this will not show up, but this switch
causes other issues, since some plugins require 2.0.6 or greater
Another option is to "patch" the FileUtils in question on your computer.
Find the one that doesn't have this method, and replace the JAR by one
that actually has the "right" signature. Yes... this is a very ugly
workaround...
-Matthias
On Tue, Jul 1, 2008 at 9:16 AM, Hazem Saleh <ha...@apache.org> wrote:
> Hi Team,
>
> Is there anyone that faces this issue during building Tomahawk ?
>
> java.lang.NoSuchMethodError:
> org.codehaus.plexus.util.FileUtils.getDefaultExclud
> es()[Ljava/lang/String;
> at
> org.codehaus.plexus.components.io.fileselectors.IncludeExcludeFileSel
> ector.setExcludes(IncludeExcludeFileSelector.java:131)
> at
> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.AbstractDe
> pendencyMojo.unpack(AbstractDependencyMojo.java:251)
> at
> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
> .unpackArtifact(UnpackMojo.java:207)
> at
> org.apache.myfaces.buildtools.maven2.plugin.builder.unpack.UnpackMojo
> .execute(UnpackMojo.java:180)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> 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)
>
>
> Thanks!
> --
> Hazem Ahmed Saleh Ahmed
> http://www.jroller.com/page/HazemBlog
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org